<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=us-ascii">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{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;}
/* List Definitions */
@list l0
{mso-list-id:1278290797;
mso-list-type:hybrid;
mso-list-template-ids:-1611114582 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Thanks Alan.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A couple of comments.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">The Board asked us to provide our view as a Working Group on the PICs on a number of items, including enforceability. And that is what we state in the report; namely, that it is enforceable.
If the Board disagrees, it could either (a) send it back, or (b) implement our view through an amendment through a bylaw amendment. This can be done at the IRT stage. We are literally on Content Freeze day and we are not comfortable adding a recommendation
that the bylaws be changed.<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">The statement “To the extent that existing PICs are used as PICs (or RVCs) in subsequent rounds, these are specifically grandfathered…..” does refer to the clause references. The
statement does not say “tidbits of the PICs” or “concepts of the PICs”, etc. It literally states that to the extent that existing PICs are used. The plain meaning of that text certainly means the PICs as they are currently written. That said, clarifying
it to state (in bracketed text):<o:p></o:p></li><ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level2 lfo1">“<i>To the extent that existing PICs are used as PICs (or RVCs) in subsequent rounds
<span style="color:red">[without material variation]</span>, these are specifically grandfathered into the current Bylaws mission.”</i><o:p></o:p></li></ol>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">A dispute panel needs to be approved by the relevant parties. So, if there is a PIC as a result of a settlement between 2 parties, then the 2 parties would “prearrange” for a dispute
provider. We should not assume that those parties will (or will not) select a reputable party.<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">For PICs that rely on ICANN to “enforce”; namely those that a Registry makes to satisfy GAC Advice, or an ALAC Objection, etc., then it will be up to ICANN and the registry to pick
a dispute provider and put that into the Agreement. Again, we should not be assuming that the registry and ICANN will pick anything other than a reputable provider.<o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoNormal">I hope that makes sense.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoTableGrid" border="1" cellspacing="0" cellpadding="0" style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td width="192" valign="bottom" style="width:144.3pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0in"><img width="178" height="81" style="width:1.8489in;height:.8437in" id="Picture_x0020_1" src="cid:image003.png@01D6D454.EC617680"></span><o:p></o:p></p>
</td>
<td width="173" valign="bottom" style="width:129.95pt;border:none;border-top:solid #06175F 3.0pt;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">E:
</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><a href="mailto:jeff@jjnsolutions.com"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">jeff@jjnsolutions.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">http://jjnsolutions.com</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Alan Greenberg<br>
<b>Sent:</b> Wednesday, December 16, 2020 11:25 PM<br>
<b>To:</b> New gTLD SubPro <gnso-newgtld-wg@icann.org><br>
<b>Subject:</b> [Gnso-newgtld-wg] PIC/RVC Enforcement<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Prior to the last meeting, I sent a message giving my reasons for not being comfortable with ICANN's ability to enforce PIC/RVCs and particularly those that may involve content.<br>
<br>
It was suggested that I review the current redline draft to see if it does not address my concerns.<br>
<br>
I have done so, and I note that it does not address my concerns and in fact gave rise to a related issue that I had not previously noticed.<br>
<br>
1. I still have concern that there is nothing in the recommendations that forces a registry to select a reputable panel to address potential violations of PICs/RVCs, and there is nothing that requires it to pay for such services. The recommendations rely solely
on the PICDRP, a process that can only be initiated if the party filing the DRP can show material harm from the violation.
<br>
<br>
<b><span style="font-size:13.5pt">It must not be necessary to show harm to ensure that contracts can be adhered to. Moreover, there should not be a substantive cost for ensuring that such contracts are honored. If an body external to ICANN must be used to address
contract compliance, such a requirement must be explcitly required in the contract and we cannot rely on implementation to ensure that.<br>
<br>
</span></b>2. I am not at all convinced that the statement (a) on page 45 is correct:
<i><span style="color:blue">"To the extent that existing PICs are used as PICs (or RVCs) in subsequent rounds, these are specifically ?grandfathered? into the current Bylaws mission."<br>
<br>
</span></i>I presume that this is based on a reading of Bylaws clause 1.1(d)(ii)(A)(2)
<i><span style="color:blue">"any registry agreement or registrar accreditation agreement not encompassed by (1) above to the extent its terms do not vary materially from the form of registry agreement or registrar accreditation agreement that existed on 1 October
2016"<br>
<br>
</span></i>Saying that a contract that is "does not vary materially" is not the same as saying you can extract tidbits from it and those tidbits remain valid.<br>
<br>
Even if my reading is incorrect, it demonstrates that we are making many assumptions leading to the belief that PIC/RVCs will be enforceable. All of those assumptions may prove to be valid, and that is just fine. But *IF* they are not all valid, then the entire
concept of enforceable commitments collapses.<br>
<br>
<b><span style="font-size:13.5pt">We must make an explicit recommendation saying that if it turns out that there is a problem enforcing PIC/RVC, the Board must take action to remedy the problem and such action might need to include Bylaw amendment.<br>
<br>
</span></b>Alan<br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>