<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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:blue;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Kurt,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for this. I’m not sure I am understanding your concern. One of the basic tenants that everyone in the SubPro PDP agreed to was that, absent any changes captured in the Recommendations, that the status quo would prevail. All the
letter does is ask for that. I feel better about sticking with the WG’s inability to change the status quo than I do asking the Board to write a policy when the community couldn’t agree to anything, even after two valiant efforts. We tried in the WG, we
couldn’t get there, the status quo should prevail. We tried again at the request of the Board at the SO/AC level, we couldn’t get there, the status quo should prevail. The letter leaves open the possibility of future community work on this but notes there
is no bandwidth or appetite to do so and we don’t want the next round held up. Help me understand you concern about asking the Board to maintain the status quo until/if the community comes up with a policy on these.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Paul<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<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> council <council-bounces@gnso.icann.org> <b>On Behalf Of
</b>kurt kjpritz.com via council<br>
<b>Sent:</b> Thursday, August 10, 2023 3:45 AM<br>
<b>To:</b> John McElwaine <john.mcelwaine@nelsonmullins.com><br>
<b>Cc:</b> GNSO Council <council@gnso.icann.org><br>
<b>Subject:</b> Re: [council] Update on 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"><span style="font-size:10.0pt">Hi John: <br>
<br>
Thanks for taking time to make this detailed report, and also thanks to the well-intentioned people that participated in the effort, in particular, our GNSO representatives. I am not surprised by the outcome. <br>
<br>
I am surprised by the recommendation to pause any release of closed generics to a future round. Such an action would turn the consensus-based policy development process on its head.</span><o:p></o:p></p>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">1. I don’t understand how the SO/AC leaders have the authority to revise the PDP final report recommendation. </span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">The PDP final report (approved by each of the Councillors) stated that the closed generic decision should be left up to the ICANN Board. The final report did not recommend the
conflicting direction that the closed generics ban be continued until a future round.</span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">The Board made an attempt to (re)involve the community by inviting the GAC and GNSO to develop a solution. With that effort closed, we should revert back to the final report recommendations.
We should not change the consensus position developed. Do we think the PDP team would have approved a recommendation to pause closed generics for an additional round? (No.) </span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">We have thoroughly discussed the conditions under which a Council approved final report can be changed (e.g., GGP), and this is not one of them. </span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">2. Continuing the ban on closed generics effectively abandons the consensus policy model of decision making.</span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">The new gTLD policy developments, in 2007-8 and 2016-21 have asked the questions: (1) should there be a round of TLDs and, if yes, (2) what restrictions / conditions should be
in place to address SSR, IP, and competition concerns.</span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">Restrictions and conditions enjoying consensus support were implemented in the program. (An illustrative example is the RPM IRT, whose recommendations were ratified by the community
STI.)</span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">During discussions on closed generics, there were people for barring them, allowing them, and allowing them with restrictions. Pausing any introduction of closed generics essentially
creates a policy advocated by a minority (and in any case not enjoying consensus support). The final report indicated as much.</span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">This result provides an incentive to avoid compromise. Going forward, those wanting to implement an unsupported policy can refuse to compromise through a PDP and subsequent ad-hoc
discussions with the hope that leadership will “give up” and implement unsupported restrictions.<br>
<br>
</span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt">3. The decision to ban closed generics for an additional round contradicts the one step the Board took.</span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal"><span style="font-size:10.0pt">The Board direction to the GAC-GNSO team established guardrails, prohibiting a model that would either ban or provide for the unrestricted release of closed generics. We cannot be sure this is where the Board
will land absent input from the GAC-GNSO effort, but we should not erase the chance that the Board would develop a balanced decision.</span><o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt">Two additional points:</span><o:p></o:p></p>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal"><span style="font-size:10.0pt"><br>
1. I do not believe that deferring the issue to the Board will delay the next round, despite the recent GAC-GNSO detour. The Board has more than a year to make a call. </span><o:p></o:p></p>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p class="MsoNormal"><span style="font-size:10.0pt"><br>
2. I do not believe the Board is exceeding their authority in making the call. The GNSO specifically assigned the task to the Board as part of their policy management responsibility. In any event, the Board established that authority when it paused closed
generics in 2012, contradicting the Council-approved policy. </span><o:p></o:p></p>
</blockquote>
<p class="MsoNormal"><span style="font-size:10.0pt"><br>
If given the opportunity to participate in a discussion on this issue, I would oppose the recommendation that the issue should be paused, and closed generics banned for the reasons stated above. I would support the final report recommendation that the issue
be decided by the Board. </span> <o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt"> <br>
Sincerely,<br>
<br>
Kurt</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 10 Aug 2023, at 7:33 am, John McElwaine via council <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Dear Councilors,<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">As GNSO Council liaison to the ALAC-GAC-GNSO Facilitated Dialogue on Closed Generic gTLDs, I wanted to update you on the latest developments on this project. On 7 July 2023, after discussions amongst themselves that I also participated
in, Sebastien (in his capacity as GNSO Chair), Jonathan Zuck (ALAC Chair) and Nico Caballero (GAC Chair) sent the attached letter to the participants in the dialogue. For reasons set out in the letter, and in response to questions that the dialogue participants
had referred to them (also noted in the letter), the three Chairs have collectively decided that it will be neither necessary to continue with the dialogue to develop a final framework nor initiate further policy development work on this topic.<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">The dialogue participants have discussed the Chairs’ joint letter and agreed to conclude their work as requested, including producing an outcomes report to ensure that the work to date is thoroughly documented. Participants also agreed
to forward the Chairs’ letter to all the commenters that submitted input on the draft framework (viz., Tucows, RySG, BC, ISPCPC, ALAC and GAC), and have invited those commenters that wish to engage with the group to join their next call to clarify any significant
concerns they raised in the feedback they provided.<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">The staff team that is supporting the dialogue is currently preparing a draft outcomes report for the group to review. The group intends for the outcomes report to serve as an introduction and summary of their work, including expressly
clarifying that the draft framework the group published in June 2023 does not reflect agreed outcomes but, rather, was a product of compromise that was reached in the interests of soliciting community feedback on the various elements and points included in
the draft framework. The outcomes report will also include all the community feedback that were submitted in full, links to the group’s community wiki space and other relevant documentation, and the participants’ feedback on the consensus building techniques
and approaches that were used for the dialogue.<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">The group hopes to wrap up its work by September, in line with its previous plan to conclude the dialogue and final framework by end-Q3 2023. I understand that Sebastien, Nico and Jonathan will also be sending a separate communication to
the ICANN Board that reflects the decision they took and, as stated in the letter, expressing the collective view that:<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">(1) closed generic gTLDs should not be viewed as a dependency for the next round;<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">(2) until there is community-developed policy, the Board should maintain the position from the 2012 round (i.e., any applications seeking to impose exclusive registry access for "generic strings" to a single person or entity and/or that
person's or entity's Affiliates (as defined in Section 2.9(c) of the Registry Agreement) should not proceed<b>;</b><span class="apple-converted-space"> </span>and<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">(3) should the community decide in the future to resume the policy discussions, this should be based on the good work that has been done to date in the facilitated dialogue.<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Sebastien and I will be happy to answer any questions you may have on the letter, the Chairs’ decision and the proposed next steps. You may also wish to check in with the representatives that each of your Stakeholder Groups appointed to
the dialogue for further information.<span class="apple-converted-space"> </span><span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Finally, I am sure I speak for all of us when I say that we are very grateful to the dialogue participants and the staff support team for all the hard work and consensus building that resulted in a detailed and substantive, if preliminary,
draft framework. I also hope that the participants’ feedback on the methods and techniques used in the dialogue, as well as other lessons learned from the experience, will provide the GNSO Council and community with useful information that we can put into
practice in future policy discussions.<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">Best regards,<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">John<span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"> <span style="font-size:10.0pt"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;caret-color: rgb(0, 0, 0);font-variant-caps: normal;text-align:start;-webkit-text-stroke-width: 0px;word-spacing:0px">
<strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">Confidentiality Notice</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee,
you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies
of this message.<o:p></o:p></span></p>
<p class="MsoNormal"><Message from ALAC GAC GNSO Chairs to Closed Generics Facilitated Dialogue Participants - FINAL - 5 August 2023 (002).pdf><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
council mailing list<br>
</span><a href="mailto:council@gnso.icann.org"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">council@gnso.icann.org</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
</span><a href="https://mm.icann.org/mailman/listinfo/council"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">https://mm.icann.org/mailman/listinfo/council</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><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 (</span><a href="https://www.icann.org/privacy/policy"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">https://www.icann.org/privacy/policy</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">)
and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">https://www.icann.org/privacy/tos</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">).
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.</span><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div style="border:solid #9C6500 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt" id="footer">
<p class="MsoNormal" style="background:#FFEB9C"><span style="color:black">This email originated from outside the firm. Please use caution.</span><o:p></o:p></p>
</div>
</div>
</body>
</html>