<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Thanks for asking.<br>
As a new participant I’ve been wondering that myself…<o:p></o:p></p>
<p class="MsoNormal">If we’re considering not just the applicant guidebook but the final effective implementation, are we including things like ICANN Advisories as well?<br>
Elaine<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> on behalf of Alan Greenberg <alan.greenberg@mcgill.ca><br>
<b>Date: </b>Friday, September 27, 2019 at 12:36 AM<br>
<b>To: </b>Kathy Kleiman <kathy@kathykleiman.com>, "gnso-newgtld-wg@icann.org" <gnso-newgtld-wg@icann.org><br>
<b>Subject: </b>[EXTERNAL] Re: [Gnso-newgtld-wg] Resolving Objection Proceedings with Mandatory PICs<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">My understanding is that the Baseline that we are working to is not the Applicant Guidebook but the final effective implementation including Board actions, so Voluntary PICS, (which predated Mandatory PICS) are there unless we have agreement
to change them.<br>
<br>
JEFF/CHERYL: Can you confirm exactly what our baseline is?<br>
<br>
Alan<br>
<br>
At 26/09/2019 06:39 PM, Kathy Kleiman wrote:<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">All,<br>
<br>
Mandatory PICS are unchanging. You can't resolve an Objection with a Mandatory PIC. It would require a Voluntary PIC -- which has become a misnomer, and a complete garbage can of everything applicants wanted to throw into the kitchen sink. There are longstanding
objections to "voluntary PICs" from the Noncommercial Stakeholder Group, Electronic Frontier Foundation and the Public Interest Community (as we discussed many times). There is no high-level agreement on including them -- and they were not part of the Round
1 rules. <br>
<br>
We agreed in last week's call that you could *amend the application* to settle an Objection. That puts the private Objection settlement out for fuller and fairer review -- which is fair. Changes to public portion of applications would be subject to public
comment -- and hopefully notification to all who have filed comments and therefore are likely interested in following changes to that application. Publication and public notice on significant changes to applications (with public comment) to settle an Objection
<b>was </b>done in Round 1. <br>
<br>
But there was no question that there is a <u>high level Disagreement to settling disputes with changes to PICs -- because mandatory PICs are fixed and unchanging.
</u>This high level Disagreement was raised in every Objections call until last night.
<i>Surely we are not saying that if you miss one discussion in the dead of night, you have waived all previous objections?
</i><br>
<br>
I'm assuming GAC objections were the topic at issue here -- and can settled with changes to the application itself. Many, many changes to public portions of applications were made in response to the GAC in Round 1.
<i><br>
</i><br>
Best, Kathy<br>
<br>
Kathryn Kleiman, American University Washington College of Law<br>
<br>
<br>
On 9/26/2019 6:13 PM, Aikman-Scalese, Anne wrote:<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt"><img width="31" height="31" style="width:.3229in;height:.3229in" id="_x0000_i1028" src="cid:image001.jpg@01D57512.469971A0" alt="[]"><a name="_GoBack"></a> <br>
Regarding the last call and the possible high level agreement on resolving Objection proceedings with mandatory PICs, it’s important to note that there is no private right of action to enforce a PIC. The current PIC Dispute Resolution procedure – PICDRP (see
attached) provides for various steps to be taken in resolving the PIC complaint and if unresolved, ICANN at its SOLE discrestion, can invoke a a Staning Panel or undertake a compliance investigation.<br>
<br>
So the points I am raising here are:<br>
<br>
(1) Proceeding on the report of a PIC violation rests in the sole discretion of ICANN<br>
(2) The expense of the Compliance investigation and/or Standing Panel is an expense of ICANN.<br>
<br>
Accordingly, it may be appropriate to consider adopting a private right of action (rather than forcing the expense on ICANN) in connection with the enforcement of mandatory PICs adopted for purposes of resolving an Objection proceeding.<br>
<br>
In fact, the PICDRP originally contained a provision allowing the enforcement issue to be taken to a third party provider. However, that draft did not survive.<br>
<br>
Anne<br>
<br>
<br>
<b>Anne E. Aikman-Scalese<br>
</b>Of Counsel<br>
520.629.4428 office<br>
520.879.4725 fax<br>
<a href="mailto:AAikman@lrrc.com">AAikman@lrrc.com</a><br>
_____________________________<br>
<img border="0" width="115" height="46" style="width:1.1979in;height:.4791in" id="_x0000_i1027" src="cid:7.1.0.9.2.20190927001342.09916580@mcgill.ca.4" alt="[]"><br>
Lewis Roca Rothgerber Christie LLP<br>
One South Church Avenue, Suite 2000<br>
Tucson, Arizona 85701-1611<br>
<a href="http://lrrc.com/">lrrc.com</a><br>
<img border="0" width="120" height="39" style="width:1.25in;height:.4062in" id="_x0000_i1026" src="cid:7.1.0.9.2.20190927001342.09916580@mcgill.ca.5" alt="[]"><br>
Because what matters<br>
to you, matters to us.™<br>
<br>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
<br>
<br>
</span><o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-newgtld-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg"><o:p></o:p></a></pre>
<pre><span class="MsoHyperlink"><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a></span><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>By submitting your personal data, you consent to the processing of your<o:p></o:p></pre>
<pre>personal data for purposes of subscribing to this mailing list accordance<o:p></o:p></pre>
<pre>with the ICANN Privacy Policy<o:p></o:p></pre>
<pre>(<a href="https://www.icann.org/privacy/policy"><o:p></o:p></a></pre>
<pre><span class="MsoHyperlink"><a href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a></span>) and the website Terms of<o:p></o:p></pre>
<pre>Service<o:p></o:p></pre>
<pre>(<a href="https://www.icann.org/privacy/tos"><o:p></o:p></a></pre>
<pre><span class="MsoHyperlink"><a href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a></span>). You can visit the Mailman link<o:p></o:p></pre>
<pre>above to change your membership status or configuration, including<o:p></o:p></pre>
<pre>unsubscribing, setting digest-style delivery or disabling delivery<o:p></o:p></pre>
<pre>altogether (e.g., for a vacation), and so on.<o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><br>
<br>
_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
Gnso-newgtld-wg@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy"> https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos"> https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></p>
</blockquote>
</div>
</body>
</html>