<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div dir="auto">Dear Councilors,</div>
<div dir="auto"><br>
</div>
<div dir="auto">On Jeff's behalf, you will find below the update and highlights of the SubPro ODP. Please have a look at both Question Sets #3 and #4. Quoting Jeff here: "For Set # 3, we shoud respond by June 1<sup>st</sup>. For Set #4, we should respond by
the end of ICANN74 if possible."</div>
<div dir="auto"><br>
</div>
<div dir="auto">Note also the related sessions during both prep and 74 weeks, including individual (on demand) sessions with SG/Cs.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards,</div>
<div dir="auto"><br>
</div>
<div id="composer_signature" dir="auto">Philippe
<div dir="auto"><br>
</div>
</div>
<div dir="auto"><br>
</div>
<div><br>
</div>
<div align="left" dir="auto" style="font-size:100%;color:#000000">
<div>-------- Message d'origine --------</div>
<div>De : Jeff Neuman <jeff@jjnsolutions.com> </div>
<div>Date : 26/05/2022 18:36 (GMT+01:00) </div>
<div>À : FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com>, "Tomslin Samme-Nlar (mesumbeslin@gmail.com)" <mesumbeslin@gmail.com>, "Sebastien@registry.godaddy" <sebastien@registry.godaddy>
</div>
<div>Cc : Steve Chan <steve.chan@icann.org> </div>
<div>Objet : Fourth Set of Assumptions and SubPro ODP Update </div>
<div><br>
</div>
</div>
<div class="WordSection1">
<p class="MsoNormal">Dear GNSO Council Leadership,</p>
<p class="MsoNormal"><br>
Can you please forward the following note to the GNSO Council?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Sincerely,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Jeff Neuman</p>
<p class="MsoNormal">GNSO Liaison to SubPro ODP</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">********************************************************</p>
<p class="MsoNormal">Dear GNSO Council,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">On May 25, 2022, we had our monthly SubPro ODP Update with ICANN’s SubPro ODP Team. The following are the major highlights of the update and for upcoming SubPro activities.</p>
<p class="MsoNormal"> </p>
<ol style="margin-top:0in" type="1" start="1">
<li style="margin-left:0in" class="MsoListParagraph">Today, ICANN released its fourth set of Topic Assumptions, which I have attached to this e-mail. The Third set of Assumptions was sent to the Council along with Question Set #4 on May 19, 2022 (See
<a href="https://mm.icann.org/pipermail/council/2022-May/025688.html">https://mm.icann.org/pipermail/council/2022-May/025688.html</a>).</li><li style="margin-left:0in" class="MsoListParagraph">Although this was mentioned in the Community Digest last week I believe, I am including the “Community Status Update” from ICANN’s SubPro ODP Team that marked the halfway point for the ODP as set forth in
the original timeline provided by ICANN.</li><li style="margin-left:0in" class="MsoListParagraph">The SubPro ODP team will hold a Prep Week Session on Tuesday, May 31, 2022 at 21:00 UTC. This will primarily serve as an update from ICANN’s ODP Team on the status of the ODP and to take questions from participants.
The team may also give us some insight as to how they tackle particular issues by running through a specific topic. By discussing that topic, the hope is to give us insight as to how they analyze each of the issues and what information they believe is relevant
to provide to the Board in assessing the costs (in terms of money, resources and time). The example topic is not intended for a discussion on the merits of the particular solution, but rather to discuss the ODP Team approach.</li><li style="margin-left:0in" class="MsoListParagraph">During ICANN74, the first “Plenary Session” entitled “New gTLD Subsequent Procedures – Working Together” will be held on Monday, June 13<sup>th</sup> at 9:00am Local Hague Time (CET). During that session,
the ODP Team will continue to discuss certain subject areas within the ODP to see feedback from the community.</li><li style="margin-left:0in" class="MsoListParagraph">The ICANN ODP Team also wants each C, SG, AC and SO to know that they are going to be available at ICANN 74 to meet with any group that wants to know more about the ODP or that have any questions. Please
reach out to Karen Lentz, Chris Bare or Lars Hoffmann if you would like to schedule a meeting.</li><li style="margin-left:0in" class="MsoListParagraph">The ICANN ODP team also has a scheduled session with the GAC during ICANN74 where they will be going over their role, their history and the New gTLD Program in general. It is intended to inform GAC members,
especially members that are new or are not as familiar with the new gTLD Program.</li></ol>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b><u>Action Items for the Council</u></b></p>
<ol style="margin-top:0in" type="1" start="1">
<li style="margin-left:0in" class="MsoListParagraph">Please review the responses to Question Set #3 (<a href="https://docs.google.com/document/d/1OtddNIUaAitHiJPE8pBTBcirTaDjyzPkcZY6BJmJxzg/edit">https://docs.google.com/document/d/1OtddNIUaAitHiJPE8pBTBcirTaDjyzPkcZY6BJmJxzg/edit</a>).
We need to get this back to the ODP Team by no later than <b>June 1, 2022.</b></li><li style="margin-left:0in" class="MsoListParagraph">Please also review Question Set #4 (<a href="https://docs.google.com/document/d/1EQDDfNprHYWWFvfrPHDe6Pu_bZosXwfVNIsK38lmJvA/edit">https://docs.google.com/document/d/1EQDDfNprHYWWFvfrPHDe6Pu_bZosXwfVNIsK38lmJvA/edit</a>).
There are lots of questions and I am just starting to populate the responses. We have a little longer to complete this, but it would be great to be able to complete this by the end of ICANN74.</li><li style="margin-left:0in" class="MsoListParagraph">Please also review the Assumptions Set #3 and the attached Set #4. Set #3 was sent in April and can be found here (<a href="https://community.icann.org/download/attachments/197264121/SubProODP_TopicAssumptions_2022_04_27.pdf?api=v2">https://community.icann.org/download/attachments/197264121/SubProODP_TopicAssumptions_2022_04_27.pdf?api=v2</a>).
On these assumptions documents, our role is not really to provide comments on the substance of any assumption unless we believe there is any assumption which is inconsistent with the SubPro Final Report. In other words, it is not a general comment period,
but rather a check to make sure the ODP Team “got it right”. <b>For Set # 3, we shoud respond by June 1<sup>st</sup>. For Set #4, we should respond by the end of ICANN74 if possible.</b></li><li style="margin-left:0in" class="MsoListParagraph">If you want to have the ICANN ODP Team visit with your C, SG, AC or SO, please reach out and let them know.</li></ol>
<p class="MsoNormal"><b> </b></p>
<p class="MsoNormal">Please let me know if you have any questions or comments.</p>
<p class="MsoNormal"><b> </b></p>
<p class="MsoNormal">Sincerely,</p>
<p class="MsoNormal"><br>
Jeff Neuman</p>
<p class="MsoNormal">GNSO Liaison to ODP</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b></b></p>
<table border="0" style="border-collapse:collapse" cellpadding="0" cellspacing="0" class="MsoNormalTable">
<tbody>
<tr>
<td style="width:144.3pt; border:none; border-top:solid #06175F 3.0pt; padding:0in 5.4pt 0in 5.4pt" valign="bottom" width="192">
<p style="text-align:justify" class="MsoNormal"><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.8518in; height:.8425in" src="cid:com_samsung_android_email_attachmentprovider_5_124151_RAW_1653583711455" id="Picture_x0020_2" onmouseover="imageMousePointerUpdate(true)" onmouseout="imageMousePointerUpdate(false)" name="com_samsung_android_email_attachmentprovider_5_124151_RAW_1653583711455"></span></p>
</td>
<td style="width:129.95pt; border:none; border-top:solid #06175F 3.0pt; padding:0in 5.4pt 0in 5.4pt" valign="bottom" width="173">
<p style="text-align:justify" class="MsoNormal"><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"></span></p>
<p style="text-align:justify" class="MsoNormal"><span style="font-family:"Arial",sans-serif; color:black">Founder & CEO</span><span style="font-size:12.0pt; font-family:"Times New Roman",serif"></span></p>
<p style="text-align:justify" class="MsoNormal"><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"></span></p>
<p style="text-align:justify" class="MsoNormal"><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"></span></p>
<p style="text-align:justify" class="MsoNormal"><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></span></p>
<p style="text-align:justify" class="MsoNormal"><span style="font-family:"Arial",sans-serif; color:black"><a href="http://jjnsolutions.com"><span style="color:#0563C1">http://jjnsolutions.com</span></a></span><span style="font-size:12.0pt; font-family:"Times New Roman",serif"></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
</div>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>