[SubPro-ODP] SubPro Update #3: First Call with GDS
McGrady, Paul D.
PMcGrady at taftlaw.com
Wed Dec 1 15:19:06 UTC 2021
Thanks Philippe,
Some thoughts from each in turn:
1. GDS will likely kick off the ODP by sending notice to the ICANN Board in January 2022. This means that the ODP will be expected to be completed by November 2022. Board consideration is expected approximately 3 months from then or February 2023.
This is an update only, so I don’t think we need to respond to it.
2. We need to finalize the process for the Council responding to questions raised by GDS as part of the ODP. My understanding is that Leadership will be proposing the mechanism for us to do so.
I think we can “play this by ear.” If a question is uncontroversial, meaning that it is truly an implementation question that follows from the static policy recommendations sent to the Board from Council, I expect an informal letter will do. Should the question be one that could disrupt the static policy recommendation, e.g. opening closed items where a policy change was recommended by the PDP WG or where a policy change was considered by the PDP WG and no recommendation for change was made, that might result in a need for a more formalistic vote should some members of Council want to disrupt the static policy recommendations Council sent to the Board. Hopefully, that doesn’t happen and let’s be optimistic and assume it won’t; so let’s not overbuild a response structure until the (however unlikely) event that we have to do so actually occurs.
3. The Council needs to decide if it would like the liaison to be included in other ODP areas to provide additional feedback to the Council. Otherwise, information will generally only be related to Questions or clarifications.
My view is that we go along with what Staff wants here because (1) we don’t want to slow things down unnecessarily in a program which already is the posterchild for slowness; and (2) at some point we have to just trust Staff not to wander away from static policy recommendations and/or to raise tricky implementation items with us. In other words, if anything is a close call, I expect Staff will raise it through Jeff. Why create a lot of work for everyone on the non-close calls? Even so, very happy to hear other views on this.
Best to all,
Paul
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.
From: council <council-bounces at gnso.icann.org> On Behalf Of philippe.fouquart--- via council
Sent: Wednesday, December 1, 2021 2:49 AM
To: council at gnso.icann.org
Cc: subpro-odp at icann.org; gnso-secs at icann.org
Subject: [council] FW: SubPro Update #3: First Call with GDS
[EXTERNAL MESSAGE]
Dear Councilors, Please see Jeff’s update on the SubPro ODP, notably on the timeframe and Council’s feedback . (This email is cross-posted to the subpro-odp mailing for transparency - and your reply-to-all would equally be unless you would chose it not to) In particul
Dear Councilors,
Please see Jeff’s update on the SubPro ODP, notably on the timeframe and Council’s feedback . (This email is cross-posted to the subpro-odp mailing for transparency - and your reply-to-all would equally be unless you would chose it not to)
In particular, give some thought to the questions/Action items that Jeff asks on how we would like to frame our input to the ODP through the liaison, how formalised this has to be and how much coverage we would like this to have with regard to the various work tracks.
We will have a discussion item at our next council call.
Thanks.
Philippe
Orange Restricted
From: Jeff Neuman <jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>>
Sent: Wednesday, December 1, 2021 3:48 AM
To: 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: SubPro ODP Mailman List <subpro-odp at icann.org<mailto:subpro-odp at icann.org>>
Subject: SubPro Update #3: First Call with GDS
Dear GNSO Council Leadership,
Please forward this update to the Council at your earliest convenience and please also cc subpro-odp at icann.org<mailto:subpro-odp at icann.org> to keep it on the public record. However, please note that any replies to this e-mail will also be include on the public mailing list as well.
This morning I had my first call with ICANN’s core ODP Team to discuss the status of the ODP, a number of administrative and logistical items, the first set of questions posed (and the process to respond to those questions), and next steps/milestones. The call went well and I appreciated all of the time spent by the GDS ODP Team going through their progress to date. Also, in the future, if you hear the term MILKY WAY, that is the Internal Code Name given to the Subsequent Rounds project within ICANN Org. It covers all of the planning, ODP, implementation, etc. up until the point in which the Application Window opens (if and when approved by the ICANN Board).
Administrative Items:
a. Attendees: The attendees at the first meeting (other than myself) included:
1. Karen Lentz (VP of Policy Research and Stakeholder Programs),
2. Lars Hoffmann (serves on Karen’s team and responsible for a number of ODP areas),
3. Chris Bare (who has been working on “New gTLDs” since the 2012 round and also works on Universal Acceptance and DNS Security and mitigation issues), and
4. Steve Chan (Head of Policy for GNSO activities and also worked with Karen and her team on the previous AGB, and with Chris on operational issues during the 2012 round).
Karen and Steve both expect that there may be additional attendees at future meetings depending on the topics covered, availability, and as more people are brought into the project.
b. Frequency of Meetings: We agreed that like the SSAD ODP, we would try to have a call once a month (or every four weeks). If we need to have it more often because of necessity, then we can choose to do that as well.
c. Transparency:
1. We all expressed our interest in ensuring that there is complete transparency within these calls and with written communications. Therefore, all e-mails (other than those involving logistics of setting up meetings) will be on the SubPro ODP public mailing list. In addition, everything that we discuss (absent extraordinary circumstances) would be reported on by me to the Council.
2. ICANN will also be doing a series of blog updates/posts on numerous items to ensure that the entire community is aware of the progress that is being made on the ODP. Some of those updates may be issue specific as things arise instead of being overall updates on the program
Summary of Ongoing Work on the ODP
a. In general, ICANN is still in the ODP Ramp-up period which includes organizing the dozens of issues into their own internal work tracks and assigning leaders within the organization to cover the applicable areas. For example, there will be a work track covering the financial issues that of course will have a leader from ICANN finance, staffing will have one from HR, etc.
b. Currently, there are a number of work track areas that are still be finalized and are being mapped out against the SubPro Final Outputs. In addition to the above, these areas include overall governance of the program, operational readiness and communications, etc. These work tracks will continue if and when the ICANN Board approves moving forward in the implementation phase.
c. There is a last work track that is dedicated to some of the dependencies on ongoing work in the community or areas which touch all of the others. This includes things like the Base Registry Agreement, IDN Tables and Name Collision (among others)
d. GDS is planning a series of blog posts in the future that will provide updates on the different work tracks and progress made.
ODP Liaison Scope
a. GDS reiterated that the scope of the Liaison in their view is to only deal with Q & A on areas within the Final Outputs and for clarification purposes.
b. We had a short discussion on recent conversations within the Council regarding using the Liaison in a more active way to provide updates to the Council on the progress of the ODP regardless of whether ICANN had any questions. GDS expressed its concern about using the liaison as a vehicle to provide information to the Council that was not being provided to the rest of the community. I reiterated that since all of our communications were being posted to the public mailing list and because the ODP is specifically geared towards the GNSO policy, that I did not see getting more updates for the GNSO as an issue, but understand their concerns.
c. At the end of the day, however, if the Council wants more information through the Liaison, it must be the Council that asks for that information. Otherwise, the current liaison will only get information related to Questions and clarifications. I am happy to do whatever the Council wants me to do on this.
Next Steps / Action Items
1. GDS will likely kick off the ODP by sending notice to the ICANN Board in January 2022. This means that the ODP will be expected to be completed by November 2022. Board consideration is expected approximately 3 months from then or February 2023.
2. We need to finalize the process for the Council responding to questions raised by GDS as part of the ODP. My understanding is that Leadership will be proposing the mechanism for us to do so.
3. The Council needs to decide if it would like the liaison to be included in other ODP areas to provide additional feedback to the Council. Otherwise, information will generally only be related to Questions or clarifications.
****P.S. Please let me know if this is too much information, not enough information, or about what you all expected.
I am happy to expand on these at the Council meeting.
Sincerely,
Jeffrey J. Neuman
[cid:image001.png at 01D7E693.17F98B10]
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/subpro-odp/attachments/20211201/3a5c56ea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9034 bytes
Desc: image001.png
URL: <https://mm.icann.org/pipermail/subpro-odp/attachments/20211201/3a5c56ea/image001.png>
More information about the SubPro-ODP
mailing list