[council] SubPro ODP Liaison Status Update #4 - Jan 2022

Mon Jan 10 18:27:38 UTC 2022

Hi again,

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.
https://mm.icann.org/pipermail/council/2021-December/025254.html

Thank you,
Philippe

From: FOUQUART Philippe INNOV/NET <philippe.fouquart at orange.com>
Sent: Monday, January 10, 2022 7:44 AM
To: Michelle DeSmyter via council <council at gnso.icann.org>
Cc: Julie Bisland via Gnso-secs <gnso-secs at icann.org>
Subject: FW: SubPro ODP Liaison Status Update #4 - Jan 2022

Hi everyone,

Please see Jeff's SubPro ODP update.

Regards,
Philippe

-------- Message d'origine --------
De : Jeff Neuman <jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>>
Date : 09/01/2022 19:22 (GMT+01:00)
À : FOUQUART Philippe INNOV/NET <philippe.fouquart at orange.com<mailto:philippe.fouquart at orange.com>>, Tomslin Samme-Nlar <mesumbeslin at gmail.com<mailto:mesumbeslin at gmail.com>>, Sebastien at registry.godaddy<mailto:Sebastien at registry.godaddy>
Cc : Steve Chan <steve.chan at icann.org<mailto:steve.chan at icann.org>>, SubPro ODP Mailman List <subpro-odp at icann.org<mailto:subpro-odp at icann.org>>
Objet : SubPro ODP Liaison Status Update #4 - Jan 2022

Dear GNSO Council Leadership,

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.

If you have any questions or comments, please let me know.

              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 its announcement<https://www.icann.org/en/announcements/details/icann-launches-new-gtld-subsequent-procedures-operational-design-phase-20-12-2021-en> on the formal launch of the New gTLD Subsequent Procedures Operational Design Phase.  As the announcement stated, on December 17, 2021, ICANN org advised the Board<https://www.icann.org/en/system/files/correspondence/swinehart-to-botterman-17dec21-en.pdf> that it was formally commencing the Operational Design Phase as of this month (January 2022).

              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 December 1, 2021 blog post by Karen<https://www.icann.org/en/blogs/details/update-answers-to-questions-related-to-icanns-upcoming-subsequent-procedures-odp-1-12-2021-en>, 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.

              ICANN Org is waiting for the GNSO Council to respond to its Initial Set of questions<https://mm.icann.org/pipermail/subpro-odp/2021-November/000007.html> submitted on November 17, 2021.  At its December GNSO Council meeting, the Council agreed to have all feedback on the responses<https://docs.google.com/document/d/1vpL6xHHVlmm5Q1Q1MuPz8I4ZgthV6EkO58JE4SAOF2Q/edit> 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 20th.   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.

              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 subpro-odp at icann.org<mailto:subpro-odp at icann.org>.  An archive of that mailing list can be found at https://mm.icann.org/pipermail/subpro-odp/.

Sincerely,

Jeffrey J. Neuman
GNSO SubPro Liaison

[cid:image002.png at 01D80658.1FE2DE00]

Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>
http://jjnsolutions.com

_________________________________________________________________________________________________________________________

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/council/attachments/20220110/7ba20710/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 9055 bytes
Desc: image002.png
URL: <https://mm.icann.org/pipermail/council/attachments/20220110/7ba20710/image002-0001.png>