Hi everyone, Thanks again for your participation in last week's call on EPDP Ph2 SSAD ODP and next steps. The notes are attached, comments welcome - we have a discussion item at our next council call on Thursday. I also reproduced the Ais from the document below. Given the convergence of views on these next steps during the call, my intent would be to proceed asap. Regards, Philippe Action items: 1. Philippe to reach out to ICANN Board to relay expectations in relation to upcoming conversation (starting point to learn about Board perspectives, ODA information will need to be reviewed by Council before any formal position can be taken). 2. Council and EPDP Phase 2 members to put forward suggestions for how/who should review and analyse ODA once this information becomes available. 3. Council to discuss in further detail during the upcoming Council meeting (20 January) the procedural avenues available to the Council as well as possible approach for reviewing ODA. From: FOUQUART Philippe INNOV/NET Sent: Tuesday, January 4, 2022 8:13 PM To: 'council@gnso.icann.org' <council@gnso.icann.org>; 'margiemilam@fb.com' <margiemilam@fb.com>; 'marksv@microsoft.com' <marksv@microsoft.com>; 'brian.king@markmonitor.com' <brian.king@markmonitor.com>; 'karklinsj@gmail.com' <karklinsj@gmail.com>; 'franck_journoud@motionpictures.org' <franck_journoud@motionpictures.org>; 'stefan.filipovic01@gmail.com' <stefan.filipovic01@gmail.com>; 'fasonga@gmail.com' <fasonga@gmail.com>; 'thomas@rickert.law' <thomas@rickert.law>; 'stephanie.perrin@mail.utoronto.ca' <stephanie.perrin@mail.utoronto.ca>; 'milton@gatech.edu' <milton@gatech.edu>; 'julf@julf.com' <julf@julf.com>; 'aelsadr@tucows.com' <aelsadr@tucows.com>; 'volker.greimann@centralnic.com' <volker.greimann@centralnic.com>; 'jbladel@godaddy.com' <jbladel@godaddy.com>; 'matt@brandsight.com' <matt@brandsight.com>; 'mmcross@amazon.com' <mmcross@amazon.com>; 'alan@donuts.email' <alan@donuts.email>; 'mcanderson@verisign.com' <mcanderson@verisign.com>; 'sdelbianco@netchoice.org' <sdelbianco@netchoice.org>; 'bruna.mrtns@gmail.com' <bruna.mrtns@gmail.com>; 'plommer@gmail.com' <plommer@gmail.com>; 'benakin@gmail.com' <benakin@gmail.com>; 'chair@rysg.info' <chair@rysg.info>; 'aheineman@godaddy.com' <aheineman@godaddy.com>; 'mason.cole@appdetex.com' <mason.cole@appdetex.com>; 'lschulman@inta.org' <lschulman@inta.org>; 'Wolf-Ulrich.Knoben@t-online.de' <Wolf-Ulrich.Knoben@t-online.de> Cc: 'gnso-secs@icann.org' <gnso-secs@icann.org>; 'brenda.brewer@icann.org' <brenda.brewer@icann.org>; 'andrea.glandon@icann.org' <andrea.glandon@icann.org>; 'secretariat@rysg.info' <secretariat@rysg.info>; 'secretariat@icannregistrars.org' <secretariat@icannregistrars.org>; 'steve.chan@icann.org' <steve.chan@icann.org>; 'marika.konings@icann.org' <marika.konings@icann.org>; 'Julie.hedlund@icann.org' <Julie.hedlund@icann.org>; 'Berry.cobb@icann.org' <Berry.cobb@icann.org>; 'Mary.wong@icann.org' <Mary.wong@icann.org>; 'Caitlin.rubergen@icann.org' <Caitlin.rubergen@icann.org>; 'Emily.barabas@icann.org' <Emily.barabas@icann.org>; 'Ariel.liang@icann.org' <Ariel.liang@icann.org> Subject: RE: EPDP Ph2 SSAD ODP and next steps Dear Councilors, Dear EPDP Phase 2 members, Dear SG/C Chairs, I trust this finds you all well. Following the informal SSAD ODP update on 20 December, in which representatives from the ICANN Board GDPR Caucus, ICANN org, the GNSO Council and GNSO appointed members of the EPDP Phase 2 team participated, Council leadership has worked with the staff support team on the attached paper which aims to provide a high level outline of the different ideas and suggestions that were made during that meeting. This is intended to serve as a basis for further discussions within the GNSO community for how to prepare for next steps in the consultation with the ICANN Board, which is in the process of being scheduled. To continue our conversation, obtain further input on possible next steps and assess whether there is possible convergence concerning next steps, we would like to schedule another call for the Council and GNSO appointed members of the EPDP Phase 2 on Wednesday 12 January at 6.00 UTC (a calendar invite will follow shortly). Of course, if there are any ideas or suggestions that have not been captured in the paper, or any new ones that have come to mind since our last meeting, please feel free to share these by replying all to this email. And Best Wishes for the New Year. Regards, Philippe From: FOUQUART Philippe INNOV/NET Sent: Friday, December 3, 2021 4:15 PM To: 'council@gnso.icann.org' <council@gnso.icann.org<mailto:council@gnso.icann.org>> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org> Subject: EPDP Ph2 SSAD ODP and next steps Dear Councilors, For those that have attended the recent SSAD ODP Webinars, you may be aware that the SSAD ODP Team is in the process of finalizing its analysis, including its work on the SSAD Cost Model. As a result, the Council requested consultation with the ICANN Board is expected to be scheduled in January 2022. To prepare accordingly for this consultation and possible next steps, Council leadership has worked with the staff support team to put forward the following proposed schedule: * 16 December 2021 at 14.00 UTC - GNSO Council meeting to discuss the approach outlined in this email * 20 December 2021 at 21.00 UTC - Update session on SSAD ODP, including SSAD Cost Model information for Council and GNSO appointed EPDP Team members (closed session) * Between 21 December and January 2022, GNSO Council with input from SG/Cs to prepare for GNSO Council - ICANN Board consultation (e.g. informal conversations, formal meetings, mailing list discussion, small team - to be discussed) * January 2022 (date TBC) - GNSO Council & ICANN Board consultation Although at this stage we do not have any further insight into what the SSAD Cost Model will tell us or how it may, or may not, change the positions on the SSAD recommendations, there are roughly three scenarios that can be anticipated: 1. ICANN Board determines that the adoption of the recommendations is in the best interest of the ICANN community and ICANN and adopts the SSAD recommendations - no further action expected from the GNSO Council at this stage; 2. ICANN Board determines that the adoption of the recommendation is not in the best interest of the ICANN community or ICANN and does not adopt all or part of the recommendations - the GNSO Council will be requested to affirm or modify its recommendations in the form of a "Supplemental Recommendation". 3. The GNSO Council decides to avail itself of section 16 ("Amendments or Modifications of Approved Policies") and agrees to modify or amend the recommendations before the ICANN Board considers the recommendations for approval. To be clear, Council Leadership does not want to get ahead of the discussion and as such, we are not making any kind of prediction about which scenario is most likely, but we would like the Council and SG/Cs to start thinking about these scenarios and consider what is needed to be prepared for the next steps. Our main objective here is to make sure that conversations within the GNSO as well as with the ICANN Board are constructive and effective - it is on all of us to work towards an approach and outcome that we are all willing and able to defend and live with. Please come prepared to share your feedback during the Council meeting on 16 December. Of course, you are encouraged to already start the conversation on the mailing list. Best regards, Philippe _________________________________________________________________________________________________________________________ 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.