June 2022 - council - lists.icann.org

Confirmation of GNSO Representative on the Empowered Community Administration
by Nathalie Peregrine 20 Oct '22

20 Oct '22

Dear John, Please find the attached a letter with the motion passed at the GNSO Council meeting on 29 November 2018. The Council confirmed the appointment of the GNSO Chair, currently Keith Drazek, representing the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN66. The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 4

Reminder: Document and Motion deadline |Monday, 11 July 2022 at 23:59 UTC for GNSO Council Meeting 21 July 2022 at 05:00 UTC
by Nathalie Peregrine 07 Jul '22

07 Jul '22

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 11 July 2022 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 21 July 2022 at 05:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/AAUVD Thank you. Nathalie

1 1

ICANN74 GAC Communique
by Emily Barabas 05 Jul '22

05 Jul '22

Dear Councilors, The ICANN74 GAC Communique is now available here: https://gac.icann.org/advice/communiques/ICANN74%20GAC%20Communique.pdf Typically, the GNSO Council only prepares a response to the Communique when there is GAC Consensus Advice to the Board included in the document. For ICANN74, there is no Advice. Unless instructed otherwise, the staff team will assume it is not necessary to convene a small group this time around. Kind regards, Emily Emily Barabas Policy Development Support Senior Manager Internet Corporation for Assigned Names and Numbers (ICANN) Phone: +31 (0)6 84507976 www.icann.org<http://www.icann.org/>

3 3

Re: [council] SSAD Light Impact Council - draft response
by philippe.fouquart＠orange.com 01 Jul '22

01 Jul '22

Correction: we did say _tomorrow_ Wednesday 29th cob as deadline for this, not today. Thanks, Philippe Orange Restricted From: FOUQUART Philippe INNOV/NET Sent: Tuesday, June 28, 2022 2:27 PM To: 'kurt kjpritz.com' <kurt(a)kjpritz.com> Cc: council(a)gnso.icann.org; gnso-secs(a)icann.org Subject: RE: [council] SSAD Light Impact Council - draft response Hi Kurt. Thanks for sorting out the order of priorities in the letter, this is helpful. Some of the elements of the first iteration being more records of the discussion, we will see whether there's benefit in bringing some of them back without losing in conciseness or being repetitive. Everyone, please share any other comment you may have by the end of the day, for us to send this later this week. Thanks. Regards, Philippe Orange Restricted From: kurt kjpritz.com <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Sent: Monday, June 27, 2022 10:52 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: council(a)gnso.icann.org<mailto:council@gnso.icann.org>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] SSAD Light Impact Council - draft response Hi Philippe: Thanks for the opportunity to comment on this draft. Please consider the attached and feel free to use some, all or none of it. I have added a brief bit of context at the start as this issue did not arise from the Board-Council interaction but rather came in separately from the staff. I maintained the two main messages: 1. to emphasize the importance of both (SSAD and SubPro) initiatives, and 2. that the Council does not view itself in a position, nor does it consider it the role of the Council, to dictate the allocation of ICANN org resources now that these policy recommendations are with the ICANN Board. There was some re-arranging / re-wording that would render a redline somewhat ineffective but I can produce one. I hope you find this constructive and helpful. Best regards, Kurt On Jun 22, 2022, at 3:22 AM, philippe.fouquart--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, For you review, please find attached a draft letter to the Board regarding the impact of the development of an SSAD Light Design Paper on other ongoing work, including the SubPro ODP. This is intended to capture the conclusions of last week's discussion item. Please provide your comments within a week, by Wednesday 29th COB UTC. Hope all those who could attend the The Hague meeting travelled safe and well back home. 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. <SSAD Light Impact Council Response - upd 16 June 2022.docx>_______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ 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.

6 7

FW: [SOAC-Leaders-ICANNMeeting-Planning] Agenda for the Community Planning Call for ICANN75 - 7 July at 19:00 UTC.
by philippe.fouquart＠orange.com 30 Jun '22

30 Jun '22

Hi everyone, Hope you made it safely back home, it was good to see you in The Hague. In case you’d miss it, just to draw your attention on point 2 of the 75 planning call on whether the 6 day format can be reduced. Given the (already) packed 4 day schedule we had for the policy meeting, I personally think such a reduction would be challenging for the AGM. Regards, Philippe Orange Restricted From: SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning-bounces(a)icann.org> On Behalf Of David Olive via SOAC-Leaders-ICANNMeeting-Planning Sent: Thursday, June 30, 2022 5:43 PM To: SOAC-Leaders-ICANNMeeting-Planning <soac-leaders-icannmeeting-planning(a)icann.org> Cc: soac-chairs(a)icann.org Subject: [SOAC-Leaders-ICANNMeeting-Planning] Agenda for the Community Planning Call for ICANN75 - 7 July at 19:00 UTC. Dear Community Leaders and Representatives: Here is the agenda for the 7 July planning call: 1. Feedback on ICANN74 and post-meeting survey (Sally Costerton & Nick Tommaso) 2. ICANN75 meeting duration: considerations and feedback on whether to maintain a 6-day meeting or reduce its duration (e.g. to 4 days) (Sally Costerton & David Olive) 3. Planning for ICANN75 plenary session(s) (Mary Wong & Tanzanica King) 4. ICANN75 production dates and draft block schedule (Tanzanica King) 5. Any other business (All) Please note agenda item #2 on the duration of the meeting for ICANN75 as your views will be needed. Best regards. Sally Costerton and David Olive Sent from my iPhone David A. Olive Senior Vice President Policy Development Support Managing Director ICANN Washington Office Internet Corporation for Assigned Names and Numbers (ICANN) _________________________________________________________________________________________________________________________ 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

Re: [council] Finalize Question Set 3
by philippe.fouquart＠orange.com 30 Jun '22

30 Jun '22

Hi everyone, Having seen no more inputs to this Question Set #3, we will close the google doc tomorrow and Jeff will respond to the ODP team with these elements. Thanks to those who contributed. Regards, Philippe Orange Restricted From: FOUQUART Philippe INNOV/NET Sent: Tuesday, June 28, 2022 2:44 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>; council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: RE: Finalize Question Set 3 Hi everyone, Following up (belatedly) from our council meeting: last call on our comments on Question Set #3, please have a final look at Council's suggested response at https://docs.google.com/document/d/1OtddNIUaAitHiJPE8pBTBcirTaDjyzPkcZY6BJm… Thank you. Philippe Orange Restricted From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of philippe.fouquart--- via council Sent: Friday, June 3, 2022 7:22 PM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] FW: Finalize Question Set 3 Hi Kurt, everyone, Thanks for your inputs on the ODP Question Set#3, please have a look at Jeff's note below and proposal on how to include them, or not for two of them. Thank you. Regards, Philippe Orange Restricted From: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Sent: Friday, June 3, 2022 4:26 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>>; Tomslin Samme-Nlar (mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>) <mesumbeslin(a)gmail.com<mailto:mesumbeslin@gmail.com>>; Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy> Cc: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Subject: Finalize Question Set 3 Dear Council Leadership, We have everyone until; June 1st to let us know their thought on Question set #3<https://docs.google.com/document/d/1OtddNIUaAitHiJPE8pBTBcirTaDjyzPkcZY6BJm…>. Kurt had a few comments I incorporated. There are 2 comments that I propose not incorporating for the reasons set forth below: 1. The first comment from Kurt is on the substance of the Final Report recommendation and not believing it is implementable. I understand why Kurt feels that way, but the purpose of the ODP Questions are to seek clarity on the recommendations and not our opinion on whether we still like (or don't like) the SubPro Final Report recommendations. That comment is response to Question 3 2. The second comment Kurt makes, which I think is a good recommendation on implementation is just that....implementation. And although I think we would all agree with his comment in response to that part of question 4, this has not been discussed by the Council. And it can be brought up during implementation anyway. Can you please forward this to the Council list and let them know that unless I hear anything by Wednesday, June 8, I will send this off without the comments you currently see in the draft. Thanks. Jeff GNSO Liaison to SubPro ODP [cid:image001.png@01D88CB3.30BA9B00] 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. _________________________________________________________________________________________________________________________ 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

FYI: [Ext] Thursday, 30 June 2022 | DUE TOMORROW: NextGen@ICANN ICANN75 Applications
by Terri Agnew 30 Jun '22

30 Jun '22

FYI: [https://r20.rs6.net/on.jsp?ca=b67c04d9-7734-49af-b061-0fe151b20eca&a=112202…] Thursday, 30 June 2022 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> Table of Contents Information Sharing · TOMORROW: Calling for NextGen@ICANN Applications for ICANN75 · NEW: ICANN Advisory: Chinese Privacy Law's Impact on Data Disclosure Complaints · REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building · REMINDER: Request for Appointment of Members and Liaisons to the CSC · REMINDER: NextGen@ICANN Mentor Program Nominations Public Comment Proceedings · Initial Report on the Transfer Policy Review - Phase 1(a) Information Sharing TOMORROW: Calling for NextGen@ICANN Applications for ICANN75 ICANN is calling for applications [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> for the NextGen@ICANN Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…>. ICANN wants to hear from university students living and studying in the Asia Pacific region who are interested in the future of the Internet and in participating in the ICANN75 Annual Meeting. ICANN75 is scheduled to be held in Kuala Lumpur, Malaysia, from 17 to 22 September 2022. If ICANN75 is held virtually, the NextGen@ICANN Program will also be held virtually. The NextGen@ICANN application window will remain open until Friday, 1 July 2022. Successful candidates will be announced on 15 July 2022 on the ICANN website. For more information about the program and to apply, please visit the NextGen@ICANN website [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> NEW: ICANN Advisory: Chinese Privacy Law's Impact on Data Disclosure Complaints ICANN has published an Advisory [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> on the impact of China's Personal Information Protection Law (PIPL) on complaints pertaining to third-party access to nonpublic generic top-level domain (gTLD) registration data. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> REMINDER: Nomination Period Opens for Dr. Tarek Kamel Award for Capacity Building ICANN opened a one-month nomination [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> period for the Dr. Tarek Kamel Award for Capacity Building. The ICANN Board will evaluate a shortlist of candidates. Please submit nominations via this nomination form [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> by Monday, 25 July 2022, 23:59 UTC. Any additional information in support of nominations or questions about the award process may be submitted via email to kamelaward(a)icann.org<mailto:kamelaward@icann.org>. This year's award recipient will be announced in September 2022 at ICANN75. For more information, please refer to the Dr. Tarek Kamel Award for Capacity Building webpage [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> REMINDER: Request for Appointment of Members and Liaisons to the CSC As of 30 September 2022, several members and liaisons of the Customer Standing Committee (CSC) will complete their term. ICANN org will soon be asking chairs to initiate your respective group's processes to appoint members and liaisons to these seats. While members are required, liaison appointments are optional (albeit strongly encouraged). To ensure that the appointment process is completed in time for the start of the next CSC term, ICANN org will ask to be notified of your appointments by Monday, 1 August 2022. More information will be shared directly via email, including detailed guidance about the process, candidate qualification requirements, and key dates. More information about the CSC can be found here. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> REMINDER: NextGen@ICANN Mentor Program Nominations The nomination period for the NextGen@ICANN Mentor Program is now open. Nominations must be submitted by no later than Monday, 1 August 2022. The community-nominated mentor will be responsible for overseeing the mentor process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…>. Interested community groups should select their respective volunteers and notify Deborah Escalera, deborah.escalera(a)icann.org<mailto:deborah.escalera@icann.org>. Public Comment Initial Report on the Transfer Policy Review - Phase 1(a) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> Open for Submissions Date: Tuesday, 21 June 2022 Closed for Submissions Date: Tuesday, 2 August 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…>. Volume 4, Issue 47 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…> | Next Issue: Monday, 04 July 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001dR2UJh7rGEJRUeso…>

1 0

FW: SSAD Light Impact Council - draft response
by philippe.fouquart＠orange.com 30 Jun '22

30 Jun '22

Dear Councilors, Staff has started preparing a final revision of the letter with the comments received so far. Thanks Kurt, Greg, Manju. In the meantime, please see Jeff’s suggestion below, shared with his permission, to add “preestablished” before “published milestones” as well as the sentence “This letter should not be interpreted as the Council accepting any delays in either of these projects.” We discussed this within leadership and don’t think this is inconsistent with the exchange we have had so far (including Greg’s edits), and useful given the latest exchanges with the ODP team. As a rule, however, we don’t want to add text that has not been circulated. If you think otherwise, please say so by Friday 1700UTC. Thank you. Philippe Orange Restricted From: Jeff Neuman <jeff(a)jjnsolutions.com> Sent: Wednesday, June 29, 2022 11:20 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>; Tomslin Samme-Nlar (mesumbeslin(a)gmail.com) <mesumbeslin(a)gmail.com>; Sebastien(a)registry.godaddy Cc: kurt(a)kjpritz.com Subject: FW: [council] SSAD Light Impact Council - draft response Dear council leadership, I understand there is a desire to send this letter tonight or tomorrow. I just wanted to give you an update on the call I had with the SubPro ODP ICANN team. I am in the process of drafting up my other notes to send a full note to the Council (which I should send around tomorrow or Friday). With respect to the SubPro ODP, there have been no instructions yet to the ODP Team that the SSAD Light work has been approved for them to start working on. Therefore, the ODP Team is still working on their current deadlines. However, if and when there are instructions to proceed with the SSAD ODP Light design, they reminded me that it will be at least a 6 week delay. Although the ODP Team has not yet figured out what delays would actually be caused by the SSAD Light project, they committed to me that they would immediately develop a new timeline for the SubPro ODP letting us know the specific intended delays. The confirmed that if it were just 6 weeks that would be pushing against the December holiday time when ICANN closes down and this may cause the ODA to not be released until Mid-January which would of course result in a 10-week delay. It is also unknown how that would impact their other milestones. For example, I believe there is no ICANN Board Meeting in December so the earliest the ODP Team could brief the Board on the ODA would be January. But they are unsure when the Board Workshop will be (which is the natural place where they intended to update the Board). This could mean that the Board could not be updated until February unless the ICANN Board moved their intended workshop or figured out another time to discuss these. In any case, it puts a vote by the ICANN Board on the GNSO SubPro Policies in March at risk. And of course this will ultimately lead to a decision in September when the SSAD Light proposal is presented on whether to move ahead with the implementation of that and whether the implementation of that will also delay implementation of SubPro. The ICANN ODP team that is not also on the SSAD Light project will continue to work on the SubPro ODP during any delay. I have asked them to present creative ideas on how we can mitigate the impact of any of these delays on future activities. This includes releasing parts of the ODA earlier than others (if that is even possible) or any other ideas to mitigate the delays. I am not a councilor, but as an impacted GNSO member, I believe a sentence must be added to the letter that states :”This letter should not be interpreted as the Council accepting any delays in either of these projects.” I have therefore cc’d Kurt. If you want to send it to the Council, feel free. But when I read the letter in my opinion it very lightly says that they should try to meet published milestones, but we don’t have the expertise to say anything else. I disagree with that…but even if we accept that notion, this letter as drafted basically gives ICANN carte blanche to do whatever they want. Therefore, the added setence states what I believe we expect. Finally, I added the word “Pre-established” before the words published milestones. ICANN can always meet published milestones If they keep publishing new timelines 😉 Its your call on what you want to do, but I think the letter should be stronger on what we expect. Its not our job to organize their resources, yes. But, it is their job to perform. [cid:image001.png@01D88BDB.1CDC7BE0] 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 From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of philippe.fouquart--- via council Sent: Tuesday, June 28, 2022 8:28 AM To: kurt kjpritz.com <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] SSAD Light Impact Council - draft response Hi Kurt. Thanks for sorting out the order of priorities in the letter, this is helpful. Some of the elements of the first iteration being more records of the discussion, we will see whether there’s benefit in bringing some of them back without losing in conciseness or being repetitive. Everyone, please share any other comment you may have by the end of the day, for us to send this later this week. Thanks. Regards, Philippe Orange Restricted From: kurt kjpritz.com <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Sent: Monday, June 27, 2022 10:52 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: council(a)gnso.icann.org<mailto:council@gnso.icann.org>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: [council] SSAD Light Impact Council - draft response Hi Philippe: Thanks for the opportunity to comment on this draft. Please consider the attached and feel free to use some, all or none of it. I have added a brief bit of context at the start as this issue did not arise from the Board-Council interaction but rather came in separately from the staff. I maintained the two main messages: 1. to emphasize the importance of both (SSAD and SubPro) initiatives, and 2. that the Council does not view itself in a position, nor does it consider it the role of the Council, to dictate the allocation of ICANN org resources now that these policy recommendations are with the ICANN Board. There was some re-arranging / re-wording that would render a redline somewhat ineffective but I can produce one. I hope you find this constructive and helpful. Best regards, Kurt On Jun 22, 2022, at 3:22 AM, philippe.fouquart--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, For you review, please find attached a draft letter to the Board regarding the impact of the development of an SSAD Light Design Paper on other ongoing work, including the SubPro ODP. This is intended to capture the conclusions of last week’s discussion item. Please provide your comments within a week, by Wednesday 29th COB UTC. Hope all those who could attend the The Hague meeting travelled safe and well back home. 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. <SSAD Light Impact Council Response - upd 16 June 2022.docx>_______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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

Draft minutes of the GNSO Council meeting 15 June 2022
by Nathalie Peregrine 29 Jun '22

29 Jun '22

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting held on Thursday, 15 June 2022. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 01 July 2022. Thank you. Kind Regards, Nathalie

4 4

Closed generics - cover letter + ST summary
by philippe.fouquart＠orange.com 29 Jun '22

29 Jun '22

Dear Councilors, For your reference, you will find attached the summary and letter that will be sent shortly to Maarten and Manal, to start our dialogue on closed generics. Given the response under 2., we will also make sure ALAC is informed, and I'm sure Justine will help with this. The only addition to the small team's summary is under < Additional Considerations:" at the very end ("in addition..."), which captures the NCSG's statement made during the discussion in The Hague. Thanks to all ST members and to those who provided their inputs during our Council meeting. 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.

2 1