<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;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
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;}
--></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">
<div class="WordSection1">
<p class="MsoNormal">Thanks Alan. I want to draw your attention to the letter that Cheryl and I sent to the Board to clarify this very matter:
<a href="https://www.icann.org/en/system/files/correspondence/langdon-orr-neuman-to-botterman-20aug20-en.pdf">
https://www.icann.org/en/system/files/correspondence/langdon-orr-neuman-to-botterman-20aug20-en.pdf</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">More specifically, the letter states:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“With respect to the issue of “closed generics”, the Working Group has been unable to reach agreement on whether closed generics should be allowed, not allowed, or if allowed, under what conditions. We take note of the Board’s July 27,
2015 letter to the GNSO where it states: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><i>As a result, the NGPC requests that the GNSO specifically include the issue of exclusive registry access for generic strings serving a public interest goal as part of the policy work it is planning to initiate on subsequent rounds of
the New gTLD Program. <o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Working Group spent considerable time discussing whether this meant that the ICANN Board resolved that all future closed generics must serve a public interest goal if they were to be allowed, or whether it was just attempting to understand
the GNSO’s thoughts on closed generics in general. We would like to understand the Board’s view on the topic of closed generics as it would help guide our future discussions. The Working Group has also published three recent proposals on the future treatment
of Close Generics. Although none of these have been endorsed by the Working Group, we would like to understand whether any of these proposals at a high level are heading in a direction in line with the Board’s views.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hopefully, we will get some clarification from the Board’s response to our letter.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><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 border="0" width="178" height="81" style="width:1.8489in;height:.8437in" id="Picture_x0020_1" src="cid:image001.png@01D68C38.67546650"></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, September 16, 2020 2:20 PM<br>
<b>To:</b> New gTLD SubPro <gnso-newgtld-wg@icann.org><br>
<b>Subject:</b> [Gnso-newgtld-wg] Comment on "The Case for Delegating Closed Generics"<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">While preparing a presentation for At-Large on Closed Generics, I noted something that I think needs to be considered going forward.<br>
<br>
In the Pritz, Trachtenberg and Rodenbaugh proposal "The Case for Delegating Closed Generics" advocating the unrestricted delegation of closed generics, the following statement is made in relation to the Board action in response to GAC Advice:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i>The Board consequently decided to halt the processing of applications for ?closed generics? for the current round, and sought additional policy recommendations from the GNSO on how closed generics should be treated
in subsequent rounds.</i> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">That is not accurate as a critical part of the Board resolution is omitted. The exact wording was:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><i>NGPC requests that the GNSO specifically include the issue of exclusive registry access for generic strings serving a public interest goal as part of the policy work it is planning to initiate on subsequent rounds
of the New gTLD Program, and inform the Board on a regular basis with regards to the progress on the issue.</i>
<o:p></o:p></p>
<p class="MsoNormal"><b>The key missing phrase is that the GNSO Council was instructed to initiate policy work for exclusive registry access for generic strings SERVING A PUBLIC INTEREST.<br>
<br>
</b>I understand the authors' belief that a test for the public interest is not possible or practical, but that does not remove the clear requirement in the charge the Board gave to the GNSO Council.
<br>
<br>
Regardless of my personal views on the issue of closed generics, I do not believe that the PDP can or should make a recommendation that is not aligned with the Board's instructions to the GNSO.
<br>
<br>
Alan<o:p></o:p></p>
</div>
</body>
</html>