<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Melissa and all,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">My responses are in <font color="#b45f06">burnt sienna</font> below.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 1, 2023 at 2:36 PM Melissa Peters Allgood <<a href="mailto:melissa.allgood@icann.org">melissa.allgood@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-823895533145792219">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_-823895533145792219WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif">Hello all,
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif">First, I’d like to thank each of you for your hard work yesterday. Your willingness to hear one another and find a compromise was on full display. I recognize that many of you
don’t love where your work landed, but you worked hard to find a path that all can live with. Truly the MSM at work.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif">Below you will find our attempt to capture the agreement in principle that was reached.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p style="margin:0in"><b><i><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Definitions</span></i></b><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"> - Staff proposed agreement in principle based on 31 May
call:<u></u><u></u></span></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"><u></u> <u></u></span></p>
<ul style="margin-top:0in" type="disc">
<li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif;color:black">For purposes of the Facilitated Dialogue on Closed Generic gTLDs, it was necessary for the group to have a shared understanding of concepts relevant to closed generic gTLDs. Bearing in
mind relevant definitions found in the Base gTLD Registry Agreement, Section 2.9(c) (“Affiliate”) and Specification 11, Section 3(d) (“Generic String”), the group agreed not to change any existing definitions, but acknowledged that there are likely other entities
beyond “Affiliates” that would benefit from exclusive operation of a closed generic gTLD with the registry. A future policy group should consider incorporating this concept in its work. </span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span>
<ul style="margin-top:0in" type="circle">
<li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif;color:black">For purposes of this discussion, the group views a “closed generic gTLD” as a “gTLD with exclusive registry access”, understood to be a gTLD string that is a generic word or term under
which domains are registered exclusively by the registry operator, its affiliates, and possibly other relevant entities as determined by subsequent policy work.</span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></li></ul>
</li></ul>
<p style="margin-right:0in;margin-bottom:0in;margin-left:1in;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif;color:black"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:lime">Please respond if you can live with this compromise. If you cannot, please offer a detailed way forward.</span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u></span></p></div></div></div></blockquote><div><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#b45f06">I cannot live with this, nor does it seem like much of a compromise. I am fine with leaving the contractual definition of "Affiliate" intact, but it is too narrow for our purposes. Leaving everything beyond capital-A "Affiliates" out of the mix, other than a vague and squishy "<span style="font-family:Arial,sans-serif;font-size:14.6667px">and possibly other relevant entities as determined by subsequent policy work" misses the point. I agree with Alan G. that we don't want to get bogged down with drafting minutiae, but we need to leave sufficient instructions so our intent is clear. Similarly, stating that "</span><span style="font-family:Arial,sans-serif;font-size:14.6667px">A future policy group <span style="background-color:rgb(255,255,0)">should consider</span> incorporating this concept in its work" is far too weak. This is a necessary concept, as many of our examples have demonstrated. Here's how I would redraft the bullets (though I tend to agree with Jeff that the second bullet may be surplusage, redundant, repetitive and adds nothing new):</span></font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:14.6667px"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><ul type="disc" style="margin-bottom:0in;font-family:Arial,Helvetica,sans-serif;margin-top:0in"><li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><font color="#b45f06"><span style="font-size:11pt;font-family:Arial,sans-serif">For purposes of the Facilitated Dialogue on Closed Generic gTLDs, it was necessary for the group to have a shared understanding of concepts relevant to closed generic gTLDs. The group recognized the existing definitions found in the Base gTLD Registry Agreement, including Section 2.9(c) (“Affiliate”) and Specification 11, Section 3(d) (“Generic String”). The group agreed that there are other several relationships and entities beyond the narrow definition of “Affiliates” that must be included as potential registrants in a Closed Generic gTLD, depending on the operational model of the gTLD. Specifically, the group identified (a) members of a trade association, where the trade association is the registry operator, (b) independent chapters that are members of a larger federation or organization (e.g., Red Cross, Big Brothers & Big SIsters), where that federation/organization [or a third party?] is the registry operator, (c) members of a consortium of similar organizations, where the consortium or a third party is the registry operator . The policy group that takes up the Closed Generics issue may identify additional relationships and entities. </span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></font><ul type="circle" style="margin-bottom:0in;margin-top:0in"><li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><span style="font-size:11pt;font-family:Arial,sans-serif"><font color="#b45f06">For purposes of this discussion, the group views a “closed generic gTLD” as a “gTLD with exclusive registry access”, understood to be a gTLD string that is a generic word or term under which domains are registered exclusively by the registry operator, its affiliates, and other relevant entities including those above as well as others determined by subsequent policy work.</font></span></li></ul></li></ul></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-823895533145792219"><div lang="EN-US" style="overflow-wrap: break-word;"><div class="m_-823895533145792219WordSection1"><p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p style="margin:0in"><b><i><span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Public Comment</span></i></b><span style="font-size:11pt;font-family:Arial,sans-serif;color:black"> – staff proposed agreement in principle based on 31
May call:<u></u><u></u></span></p>
<p style="margin:0in"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<ul style="margin-top:0in" type="disc">
<li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Applications for closed generics gTLDs should be subject to the same Public Comment period as all other gTLD applications. However, given that closed generic gTLDs are uniquely impactful
to the public interest, the group acknowledges there should be more time dedicated to their Public Comments if the number of these applications is considerable. If there are more than 10 closed generic gTLD applications, then the Public Comment period will
be extended automatically for 60 days solely for closed generic gTLD application comments. This does not replace ICANN’s discretion to extend the Public Comment period for all applications, and the 60-day extension will apply to the full length of the Public
Comment period (extended or otherwise). </span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span>
<ul style="margin-top:0in" type="circle">
<li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif;color:black">In line with Implementation Guidance 13.6 from the
</span><span style="font-size:11pt;font-family:Arial,sans-serif"><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf" target="_blank"><span style="color:rgb(17,85,204)">New gTLD Subsequent Procedures
Final Report</span><span style="color:black;text-decoration:none"> </span></a>(pg. 244), this implementation should enable the public to easily identify and obtain information about applications for closed generic gTLDs. The group agrees that there must be
a centralized space where prospective commenters can go to understand the rules for closed generic gTLDs and view the applications themselves. <u></u><u></u></span></li><li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline">
<span style="font-size:11pt;font-family:Arial,sans-serif;color:black">Note: In arriving at this compromise approach to Public Comment, the group acknowledges the unique nature inherent to closed generic gTLDs, as well as the need for sufficient time for
meaningful Public Comments, and the public’s need to readily find all relevant information about closed generic gTLD applications.</span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></li></ul>
</li></ul>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif;color:black;background:lime">Please respond if you can live with this compromise. If you cannot, please offer a detailed way forward.</span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <span class="gmail_default" style="font-family:verdana,sans-serif"><font color="#b45f06">This also misses the mark and does not provide anything close to the result being sought by a significant portion of the group. As such, I can't live with this either. What is needed is not merely the possibility of the hope of the potential of an extension of the initial "reveal day" triggered comments period. What is needed is a firm commitment to a greater opportunity to comment -- in the form of a second comment period for Closed Generics, to occur after GAC Early Warnings. </font></span></span></p></div></div></div></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-823895533145792219"><div lang="EN-US" style="overflow-wrap: break-word;"><div class="m_-823895533145792219WordSection1"><p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><span class="gmail_default" style="font-family:verdana,sans-serif"><font color="#b45f06">The number of Closed Generics is not really relevant to whether a second period is needed (or even the extension of the first period) -- unless we have hundreds of Closed Generics, in which case even more time may be needed. The issue is not primarily that commenting organizations need time to sort through a plethora of applications; rather, the issue is that commenting organizations will need more time than is granted to consider whether and how to comment on the one, two or a few Closed Generic applications that will be relevant to it/them, to build awareness of the relevant application(s) and get buy-in from potential participants in a comment, and then to develop, write, circulate to what might be a substantial group of co-authors, get back comments, revise, recirculate, and finalize the comments. Underlying this is a belief that comments on Closed Generics are more like to come from organizations, associations, and groups of like-minded entities based on the very nature of the Closed Generic gTLD. That is why this treatment is critical and why it is sought.</font></span></span></p></div></div></div></blockquote><div><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#b45f06">Proposed revisions:</font></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="color:rgb(180,95,6)"></span><br></div><ul type="disc" style="margin-bottom:0in;margin-top:0in"><li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><font color="#b45f06"><span style="font-size:11pt;font-family:Arial,sans-serif">Applications for closed generics gTLDs <span class="gmail_default" style="font-family:verdana,sans-serif">will</span> be subject to the same Public Comment period as all other gTLD applications. However, given that closed generic gTLDs are uniquely impactful to the public interest<span class="gmail_default" style="font-family:verdana,sans-serif"> and to the interests of multiple entities that may identify with a string</span>, the group acknowledges there should be more time dedicated to their Public Comments. <span class="gmail_default" style="font-family:verdana,sans-serif">T</span>he Public Comment period will <span class="gmail_default" style="font-family:verdana,sans-serif">supplemented by an additional </span>60 day<span class="gmail_default" style="font-family:verdana,sans-serif"> comment period </span>solely for closed generic gTLD application comments<span class="gmail_default" style="font-family:verdana,sans-serif">, to commence upon the submission of Early Warnings by the GAC and its members</span>. This does not replace ICANN’s discretion to extend the Public Comment period for all applications, and the 60-day extension will apply to the full length of the Public Comment period (extended or otherwise). </span><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u><u></u></span></font><ul type="circle" style="margin-bottom:0in;margin-top:0in"><li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><font color="#b45f06"><span style="font-size:11pt;font-family:Arial,sans-serif">In line with Implementation Guidance 13.6 from the </span><span style="font-size:11pt;font-family:Arial,sans-serif"><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/final-report-newgtld-subsequent-procedures-pdp-02feb21-en.pdf" target="_blank">New gTLD Subsequent Procedures Final Report<span style="text-decoration-line:none"> </span></a>(pg. 244), this implementation should enable the public to easily identify and obtain information about applications for closed generic gTLDs. The group agrees that there must be a centralized space where prospective commenters can go to understand the rules for closed generic gTLDs and view the applications themselves. <u></u><u></u></span></font></li><li style="margin-top:0in;margin-bottom:0in;vertical-align:baseline"><span style="font-size:11pt;font-family:Arial,sans-serif"><font color="#b45f06">Note: In arriving at this compromise approach to Public Comment, the group acknowledges the unique nature inherent to closed generic gTLDs, as well as the need for sufficient time for meaningful Public Comments, and the public’s need to readily find all relevant information about closed generic gTLD applications.</font></span></li></ul></li></ul><div><span class="gmail_default" style="font-family:verdana,sans-serif"></span> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg-823895533145792219"><div lang="EN-US" style="overflow-wrap: break-word;"><div class="m_-823895533145792219WordSection1"><p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Arial,sans-serif">To do:<u></u><u></u></span></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="m_-823895533145792219MsoListParagraphCxSpFirst" style="margin-left:0in">
<span style="font-size:11pt;font-family:Arial,sans-serif">Respond to the proposed approach for Definition and Public Comment above<u></u><u></u></span></li><li class="m_-823895533145792219MsoListParagraphCxSpLast" style="margin-left:0in">
<span style="font-size:11pt;font-family:Arial,sans-serif">Review the Closed Generics Framework v4 document (s) –
<a href="https://docs.google.com/document/d/1nEy2mQm01ITo-ovxgIVQ0kNIpLqPV4bqVxTKgZb15vQ/edit" target="_blank">
Edits Tracked</a> and/or <a href="https://docs.google.com/document/d/1InSBpBSW-j2aVwsk59t-Hs2LfAhuEKNfiwkFoi3SYxU/edit" target="_blank">
Clean</a><u></u><u></u></span></li></ol>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Arial,sans-serif">Agenda for 5 June 2023 at 12:30 UTC:<u></u><u></u></span></b></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="m_-823895533145792219MsoListParagraphCxSpFirst" style="margin-left:0in">
<span style="font-size:11pt;font-family:Arial,sans-serif">Finalize Definition and Public Comment<u></u><u></u></span></li><li class="m_-823895533145792219MsoListParagraphCxSpMiddle" style="margin-left:0in">
<span style="font-size:11pt;font-family:Arial,sans-serif">Review preliminary framework (Closed Generics Framework v4)<u></u><u></u></span></li><li class="m_-823895533145792219MsoListParagraphCxSpMiddle" style="margin-left:0in">
<span style="font-size:11pt;font-family:Arial,sans-serif">Final call to determine if the group can live with the preliminary framework document (Items 1 & 2)<u></u><u></u></span></li><li class="m_-823895533145792219MsoListParagraphCxSpLast" style="margin-left:0in">
<span style="font-size:11pt;font-family:Arial,sans-serif">Discuss Closed Generics sessions at ICANN77<u></u><u></u></span></li></ol>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif">As always, my sincere thanks for all your hard work.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Arial,sans-serif">Melissa<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black"> </span><span style="font-size:11pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">Melissa Peters Allgood</span><span style="font-size:11pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">Conflict Resolution Specialist</span><span style="font-size:11pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">Internet Corporation for Assigned Names and Numbers (ICANN)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">Telephone: +1 202 570 7240<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black"><a href="http://www.icann.org" target="_blank"><span style="color:rgb(5,99,193)">www.icann.org</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;color:black"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:black"> </span><u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
gnso-gac-closed-generics mailing list<br>
<a href="mailto:gnso-gac-closed-generics@icann.org" target="_blank">gnso-gac-closed-generics@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics</a><br>
<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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">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.</div></blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><font face="BlinkMacSystemFont, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif" color="#0b5394"><b>Greg Shatan</b></font><div><font face="BlinkMacSystemFont, -apple-system, Segoe UI, Roboto, Helvetica, Arial, sans-serif" color="#0b5394"><b>Chair, NARALO</b></font></div></div></div></div>