<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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="FR" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Hi again,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Apologies for speaking to myself here but as a reminder as you consider this latest update, maybe you would like to give some extra thought
to the framing questions on the SubPro ODDP put forward in December. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><a href="https://mm.icann.org/pipermail/council/2021-December/025254.html">https://mm.icann.org/pipermail/council/2021-December/025254.html</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Philippe<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> FOUQUART Philippe INNOV/NET <philippe.fouquart@orange.com>
<br>
<b>Sent:</b> Monday, January 10, 2022 7:44 AM<br>
<b>To:</b> Michelle DeSmyter via council <council@gnso.icann.org><br>
<b>Cc:</b> Julie Bisland via Gnso-secs <gnso-secs@icann.org><br>
<b>Subject:</b> FW: SubPro ODP Liaison Status Update #4 - Jan 2022<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Hi everyone,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Please see Jeff's SubPro ODP update.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Philippe<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">-------- Message d'origine --------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">De : Jeff Neuman <<a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a>>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Date : 09/01/2022 19:22 (GMT+01:00) <o:p>
</o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">À : FOUQUART Philippe INNOV/NET <<a href="mailto:philippe.fouquart@orange.com">philippe.fouquart@orange.com</a>>, Tomslin Samme-Nlar <<a href="mailto:mesumbeslin@gmail.com">mesumbeslin@gmail.com</a>>,
<a href="mailto:Sebastien@registry.godaddy">Sebastien@registry.godaddy</a> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Cc : Steve Chan <<a href="mailto:steve.chan@icann.org">steve.chan@icann.org</a>>, SubPro ODP Mailman List <<a href="mailto:subpro-odp@icann.org">subpro-odp@icann.org</a>>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US">Objet : SubPro ODP Liaison Status Update #4 - Jan 2022
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">Dear GNSO Council Leadership,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Please fine enclosed my status report on the SubPro ODP for the January 2022 GNSO Council Meeting. I have also copies the SubPro ODP official mailing list, but I would ask that you forward this to the GNSO Council list
on my behalf.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">If you have any questions or comments, please let me know.<o:p></o:p></span></p>
<div style="border:none;border-bottom:dotted windowtext 3.0pt;padding:0cm 0cm 1.0pt 0cm">
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> On December 16, 2021, we had our second SubPro ODP Liaison call with ICANN’s SubPro ODP team. Much of what we covered was subsequently announced by ICANN on December 20, 2021 in
<a href="https://www.icann.org/en/announcements/details/icann-launches-new-gtld-subsequent-procedures-operational-design-phase-20-12-2021-en">
its announcement</a> on the formal launch of the New gTLD Subsequent Procedures Operational Design Phase. As the announcement stated, on December 17, 2021, ICANN org
<a href="https://www.icann.org/en/system/files/correspondence/swinehart-to-botterman-17dec21-en.pdf">
advised the Board</a> that it was formally commencing the Operational Design Phase as of this month (January 2022).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> During the call we spent some time discussing what this actually means – namely, to go from the preparation phase to the actual operational design phase. Over the past three months, ICANN Org has been transitioning
resources (including personnel) from other projects to work on this ODP. In addition, Karen Lentz, who is responsible for the ODP from ICANN’s Global Domain Services group has expanded her team with at least one new hire (perhaps more by this point) to assist
with the project. Chris Bare, an experienced project manager, who has been working on new gTLDs since the last round, has been developing a comprehensive project plan with milestones and deliverables to enable ICANN Org to meet the 10 month ODP timeline.
In addition, as was discussed in the <a href="https://www.icann.org/en/blogs/details/update-answers-to-questions-related-to-icanns-upcoming-subsequent-procedures-odp-1-12-2021-en">
December 1, 2021 blog post by Karen</a>, the ODP has been divided into 12 scoping areas that will involve virtually every division at ICANN, including Finance, HR, Global Engagement, Systems and Tools, and ICANN Procurement (to name a few). Now that the ODP
has been formally kicked off (as of this month), members of each of these teams have been assigned to work with the ODP team so that ICANN will be able to complete the Operational Design.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> ICANN Org is waiting for the GNSO Council to respond to its
<a href="https://mm.icann.org/pipermail/subpro-odp/2021-November/000007.html">Initial Set of questions</a> submitted on November 17, 2021. At its December GNSO Council meeting, the Council agreed to have all
<a href="https://docs.google.com/document/d/1vpL6xHHVlmm5Q1Q1MuPz8I4ZgthV6EkO58JE4SAOF2Q/edit">
feedback on the responses</a> by no later than January 13, 2021. In addition, Council Leadership is finalizing a process to follow as we move forward so that we can respond to ICANN Org’s questions much more quickly than the two months it has taken us to date
to respond. I believe that will be discussed at our Council meeting on January 20<sup>th</sup>. In addition, the Council still needs to decide whether it is happy with the current set of information that it is being provided (through the Liaison), or whether
it is interested in more transparency as discussed during the December GNSO Council meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> The next SubPro ODP Liaison call with ICANN Org is scheduled for January 25, 2022. If you have any comments or questions, please send them to me and to
<a href="mailto:subpro-odp@icann.org">subpro-odp@icann.org</a>. An archive of that mailing list can be found at
<a href="https://mm.icann.org/pipermail/subpro-odp/">https://mm.icann.org/pipermail/subpro-odp/</a>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Sincerely,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><br>
Jeffrey J. Neuman<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">GNSO SubPro Liaison<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></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:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black;border:none windowtext 1.0pt;padding:0cm"><img border="0" width="178" height="81" style="width:1.8541in;height:.8437in" id="Picture_x0020_1" src="cid:image002.png@01D80658.1FE2DE00"></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:0cm 5.4pt 0cm 5.4pt">
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">Jeffrey J. Neuman</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">Founder & CEO</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:#06175F">JJN Solutions, LLC</span><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black">p: +1.202.549.5079</span><o:p></o:p></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><o:p></o:p></p>
<p class="MsoNormal" style="text-align:justify"><span style="font-family:"Arial",sans-serif;color:black"><a href="http://jjnsolutions.com">http://jjnsolutions.com</a></span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="EN-US" style="color:white"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</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>