council

Download

council@icann.org

December 2021

20 participants
52 discussions

Re: [council] [gnso-secs] Motion RE: Transfer Policy Review PDP for December 2021 GNSO Council Meeting
by Devan Reed Dec. 1, 2021

Dec. 1, 2021

Dear Greg, We have posted the motion on the 16 December wiki page, found here: https://community.icann.org/x/hQWlCg In addition, the project change form will be posted shortly to the GNSO Correspondence page here: https://gnso.icann.org/en/council/correspondence/2021 Thank you. Kind regards, Devan From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "DiBiase, Gregory via Gnso-secs" <gnso-secs(a)icann.org> Reply-To: "DiBiase, Gregory" <dibiase(a)amazon.com> Date: Wednesday, December 1, 2021 at 3:42 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Motion RE: Transfer Policy Review PDP for December 2021 GNSO Council Meeting Dear Councilors, I am submitting one motion to be considered in the December 2021 meeting: 1. Approval of a Project Change Request (PCR) to Update Charter Topics Considered in Phase 1 of the Transfer Policy Review (TPR) Policy Development Process (PDP) Motion and related documents are attached. Thanks, Greg DiBiase

1 0

FW: SubPro Update #3: First Call with GDS
by philippe.fouquart＠orange.com Dec. 1, 2021

Dec. 1, 2021

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(a)jjnsolutions.com> Sent: Wednesday, December 1, 2021 3:48 AM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com>; Sebastien(a)registry.godaddy Cc: SubPro ODP Mailman List <subpro-odp(a)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(a)icann.org<mailto:subpro-odp@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: 1. 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. 1. 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. 1. 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:image003.png@01D7E698.9A7008D0] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@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.

1 0