[council] TR: SubPro ODP Update 1-24-22

Mon Jan 24 20:06:03 UTC 2022

Dear Councilors,

Please see Jeff's update on the SubPro ODP following our call on Thursday.

Regards,
Philippe

Orange Restricted
De : Jeff Neuman <jeff at jjnsolutions.com>
Envoyé : lundi 24 janvier 2022 15:14
À : FOUQUART Philippe INNOV/NET <philippe.fouquart at orange.com>; Sebastien at registry.godaddy; Tomslin Samme-Nlar (mesumbeslin at gmail.com) <mesumbeslin at gmail.com>
Cc : Steve Chan <steve.chan at icann.org>; SubPro ODP Mailman List <subpro-odp at icann.org>
Objet : SubPro ODP Update 1-24-22

Please forward on to the Council

Dear GNSO Council Leadership,

On Friday, January 21, 2022, I had my third call with Karen Lentz and ICANN's SubPro ODP Team (which also include Steve and Emily from the Policy Team).

As the call occurred the day after the GNSO council meeting, the first part of the agenda covered a discussion about both the answers to Question Set #1 and the desire for the ODP team to provide a high level project plan to the council with monthly updates so that the council can track the progress of the ODP.  The ODP Team understood the request from Council and committed to providing the first high level project plan by the document deadline for the next GNSO Council meeting in February.

We next discussed the ODP team's desire to hold a public session at ICANN 73 in March. Like all requested sessions at ICANN, the OPD Team put in its request for a meeting, but whether that is scheduled is up to the meetings team. It is likely that such a meeting would cover progress against the project plan, a discussion about key assumptions (possible an updated version of _____________), And an interactive question and answer session. The ODP Team intends to publish a second blog post prior to ICANN 73 as well as materials for the ICANN meeting.

Next, Karen provided a recap of the most recent board resolution approving the RPM final report recommendations and the plan to include certain of the recommendations into the work of the SubPro ODP.  Most of the applicable recommendations really just reaffirmed the implementation of those RPMs in the 2012 round.

Finally, I asked whether there were items that could be worked on by the GNSO in parallel with the ODP.  In other words, we know that certain elements of the SubPro recommendations will require work from the community. These include things like: (a) the SPIRT mechanism for reviewing changes to the program, (b) the Pre-evaluation of back-end providers, (c) community outreach and (d) Applicant Support (to name a few.  It was envisioned by the working group that those things would be worked on by implementation review teams (IRTs).  When those recommendations were approved by the working group, there was no concept of an ODP and therefore the working group believed that IRTs would be created within a few months of the Final Report (assuming the Board approved the Recommendations).  Now that there is an ODP, this has delayed any Board approval of the recommendations.  But, this work still needs to be done by the community.  The question I asked Karen to discuss with ICANN leadership is whether the Board could authorize the commencement of work on these subjects by the Community so that we can get a "head start" on that work (rather than waiting a full year until the Board is in a position to approve the recommendations - after the ODP).   Karen said that they would take that issue back.

Our next call is scheduled for February 7th 2022 and I will provide an update shortly after that call. Please let me know if you have any questions or comments.

Sincerely,

Jeff Neuman
GNSO Liaison to SubPro ODP

[cid:image001.png at 01D81166.30F41AB0]

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/20220124/2edeca0f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14416 bytes
Desc: image001.png
URL: <https://mm.icann.org/pipermail/council/attachments/20220124/2edeca0f/image001-0001.png>