<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.EmailStyle17
{font-family:"Calibri",sans-serif;
color:windowtext}
.MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div dir="auto">Dear Councilors,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Please find Jeff's update on the SubPro odp. Note also the question on the impact of the SSAD Lite work on the SubPro odp. There will be an agenda item on our May call on this report.</div>
<div dir="auto">Regards,</div>
<div dir="auto"><br>
</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><br>
</div>
<div>-------- Message d'origine --------</div>
<div>De : Jeff Neuman <jeff@jjnsolutions.com> </div>
<div>Date : 04/05/2022 18:04 (GMT+01:00) </div>
<div>À : FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com>, "Sebastien@registry.godaddy" <sebastien@registry.godaddy>, "Tomslin Samme-Nlar (mesumbeslin@gmail.com)" <mesumbeslin@gmail.com>
</div>
<div>Cc : Steve Chan <steve.chan@icann.org>, SubPro ODP Mailman List <subpro-odp@icann.org>
</div>
<div>Objet : SubPro Update - May 4, 2022 (SSAD LITE WILL DELAY SUBPRO ODP) </div>
<div><br>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Dear GNSO Council Leadership,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Please find below my SubPro update from a call I had with the SubPro ODP Team at the end of next week. Can you please forward to the Council List?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Please note that we really need to discuss #1 below to make sure that the Council understands and agrees with whether to move ahead with
<u>SSAD Lite</u> prior to completing the SubPro ODP. Doing so will cause substantial delay to the SubPro ODP according to ICANN Org.</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 the SubPro ODP</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">At the end of last week, the SubPro ODP Team had its monthly meeting with the GNSO Council Liaison and we covered the following topics:</p>
<p class="MsoNormal"> </p>
<ol start="1" type="1" style="margin-top:0in">
<li class="MsoListParagraph" style="margin-left:0in"><u>Impact of SSAD Lite Work:</u> The Council is considering asking ICANN Org to do some work designing an SSAD Lite and presenting that to the community.
<b><span style="color:red">The SubPro ODP Team has explained that doing so will cause
<u>at least 6 weeks delay in the SubPro ODP.</u> </span></b>Therefore, the Council needs to consider whether that work should be done and if so whether that should be done before or after the completion of the SubPro ODP.
<i><u>This is only for designing the SSAD Lite</u>. If the Council wants it built after the design, then that could be
<u>months more delay</u> for the SubPro ODP.</i></li></ol>
<p class="MsoListParagraph"> </p>
<ol start="2" type="1" style="margin-top:0in">
<li class="MsoListParagraph" style="margin-left:0in"><u>ICANN 74:</u> </li></ol>
<p class="MsoListParagraph"> </p>
<ol start="2" type="1" style="margin-top:0in">
<ol start="1" type="a" style="margin-top:0in">
<li class="MsoListParagraph" style="margin-left:0in">According to the ICANN ODP team, the SO/AC team that works on the agenda for the meeting rejected the proposal made by the SubPro ODP team to have a policy meeting that focused primarily on SubPro. We are
still unclear if that means that there will be no ODP sessions at ICANN 74 or whether there may be 1.
</li><li class="MsoListParagraph" style="margin-left:0in">There will be a SubPro meeting during the Prep Week for ICANN 74. Because this will be near the mid point of the ODP, we will try to make this session interactive (as much as a prep week session will be),
but the goal is to not make it an update session where the entire time is spent updating the community on what has been done and whats left to do, but rather to focus on substantive issues (TBD).</li><li class="MsoListParagraph" style="margin-left:0in">The SubPro ODP Team wants to let each of the SGs and Cs know that they are available to have sessions with those groups (as well as ACs) during ICANN 74 should any of them want to schedule that in their sessions.</li></ol>
</ol>
<p class="MsoListParagraph"><u><span style="text-decoration:none"> </span></u></p>
<ol start="3" type="1" style="margin-top:0in">
<li class="MsoListParagraph" style="margin-left:0in"><u>Question Set #3</u>:
<ol start="1" type="a" style="margin-top:0in">
<li class="MsoListParagraph" style="margin-left:0in">On April 11, 2022, Question Set #3 was sent to the Council for its comments. Shortly thereafter I provided draft answers to the questions and sent them out to the Council (found
<a href="https://docs.google.com/document/d/1OtddNIUaAitHiJPE8pBTBcirTaDjyzPkcZY6BJmJxzg/edit?usp=sharing">
here</a>). This is a reminder to please give your input into the proposed responses.</li><li class="MsoListParagraph" style="margin-left:0in">Although there has been a comment in the draft responses to the ICANN SubPro ODP Team (who has access to the Google Doc), I formally submitted the comment in the form of a clarifying question today (May 4<sup>th</sup>)
about the meaning of the final question in Question Set #3.</li></ol>
</li></ol>
<p class="MsoListParagraph" style="margin-left:1.0in"> </p>
<ol start="4" type="1" style="margin-top:0in">
<li class="MsoListParagraph" style="margin-left:0in"><u>Question Set #4</u>: According to the ICANN ODP Team, we are going to shortly get ODP Set #4 which will be lengthy, but will hopefully be one of the last question sets as the ODP Is moving forward in
its work.</li></ol>
<p class="MsoListParagraph"> </p>
<ol start="5" type="1" style="margin-top:0in">
<li class="MsoListParagraph" style="margin-left:0in"><u>Timeline to Completion</u>: At this point there is nothing to believe that the work will not be completed on time,
<u>BUT</u> to the extent that any further work needs to be done on SSAD Lite, this will push the ODP back by at least 6 weeks. See #1.<u></u></li></ol>
<p class="MsoListParagraph"><u><span style="text-decoration:none"> </span></u></p>
<p class="MsoNormal">If at all possible, I would like to add an agenda item on SubPro ODP for the next Council meeting so that we can discuss the impact of the SSAD Lite on the SubPro ODP and what the Council wants to prioritize.</p>
<p class="MsoNormal"><br>
Sincerely,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Jeff</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<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" id="Picture_x0020_2" src="cid:image001.png@01D85F92.A81BD590" style="width:1.8518in; height:.8425in"></span></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"></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"></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"></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"></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></span></p>
<p class="MsoNormal" style="text-align:justify"><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>
</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>