March 2022 - council - lists.icann.org

An additional issue for AOB at our next meeting
by Flip Petillion 09 Mar '22

09 Mar '22

Dear All: I propose that we put the following issue as an AOB on the agenda of our next meeting. The incident that generated the letter from the Deputy Prime Minister, Minister of Digital Transformation of Ukraine, and the response by G. Marby, raises questions on ICANN’s role at the occasion of certain Internet activities in conflict situations. There is more to this than the question of restricting access to the Internet, the need to act neutral and within ICANN’s core mission. The questions cover a broad scope of legal and ethical considerations that may need to be fully explored. Above all, the security and stability of the Internet and the systems reliant upon it are at risk. The question is: how does ICANN ensure the openness (including accessibility) of the Internet in conflict situations and how does ICANN manage the impact on the security and stability of the Internet? In my humble opinion, this calls for a thorough impact analysis and policies that effectively map, identify and combat forms of abuse as warranted by overarching global security concerns. Ultimately, this approach may set more realistic expectations in the Community. I have not been able to discuss this at the IPC and, hence, the IPC has not been able to express a position on this subject, yet. But I think the discussion is timely. I propose that the GNSO councilors go back to their SGCs and inform the GNSO council if they wish to ask council to consider the impact analysis that I am referring to above. Best regards, Flip Flip Petillion fpetillion(a)petillion.law<mailto:fpetillion@petillion.law> +32484652653 www.petillion.law<http://www.petillion.law> [id:image001.png@01D3691D.DA7539C0]<https://www.petillion.law/> Attorneys – Advocaten – Avocats

2 2

On today, please read ! GNSO Council meeting & Joint GNSO/ALAC Session
by Nathalie Peregrine 09 Mar '22

09 Mar '22

Dear all, The GNSO Council meeting as well as the joint GNSO & ALAC meeting are taking place today. Please ensure to: * Sign in with your FULL NAME. If you haven’t, and notice once you’re logged into today’s webinar room, you will need to log out and back in again. Failure to do so may result in removal from the room. * Join early for the soundcheck if you intend to speak. * When you speak ensure you have ALL notifications turned off and are using a headset. * Have the soundcheck text to hand: “Hello, my name is ______________ and I am participating during this session in a speaking role. I am testing my audio and my speaking pace to confirm whether all language service providers are able to hear me clearly. If you would like me to repeat this test, please let me know. Thank you.” * Remember this call will be interpreted, please state your name, speak slowly and loudly. KEY POINTS TO REMEMBER: * Email and calendar invitations will not be sent out for ICANN73 sessions. * Refer to the How to Get Organized email circulated<https://mm.icann.org/pipermail/council/2022-February/025439.html> on the GNSO Council mailing list and attached to this email for your convenience. * You will need to register to the ICANN73 website [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/iIoxWhSuDevyDaBS…> and download the sessions you are interested in to your individual calendars. ICANN73 SESSIONS WHERE COUNCILOR ATTENDANCE IS HIGHLY ENCOURAGED: 1. GNSO Council meeting Wednesday 9 March 2022 at 12:30 local time (16:30 UTC) 1. Joint GNSO & ALAC session Wednesday 9 March 2022 at 16:30 local time (20:30 UTC) 1. GNSO Council Wrap Up Thursday 10 March 2022 at 10:30 local time (14:30 UTC) ADDITIONAL SESSIONS OF INTEREST TO COUNCILORS: * Wednesday 9 March: Plenary Session: Evolving the DNS Abuse Conversation * Thursday 10 March: Discussion Forum on Geopolitical Legislative and Regulatory Developments, followed by the ICANN Public Forum and the ICANN Public Board Meeting. Please reach out the gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> should you run into any issues. Kind regards, Nathalie

1 0

Reminder: ICANN Zoom room requirements: Zoom Logins: First & Last Name/ Surname Only
by Nathalie Peregrine 09 Mar '22

09 Mar '22

Dear all, To ensure transparency of participation in ICANN’s multistakeholder model, please remember to sign in to Zoom sessions using your full name (e.g. First Name + Last Name/Surname). If you are in a session using the webinar format, you will need to first exit the Zoom room prior to rejoining. Please reach out to your support staff if you have any difficulties joining a Zoom session. To rename in a regular Zoom room: 1. Join the meeting. 2. Tap Participants. 3. Hover over your name on the participants list. 4. Click More. 5. Click Rename. 6. Enter the name you desire then click Rename. 7. Your name has now been changed within the meeting. To rename in a webinar Zoom room: 1. BEFORE entering the meeting, and during the login phase, update your Zoom name here: [cid:image001.png@01D83300.B8213430] 1. If you forget to do so, you can always log out of the webinar Zoom room and edit your name upon re-entering. Please contact your support staff if you run into any issues. Thank you! Kind regards, Nathalie

1 0

Re: [council] [gnso-secs] Motion to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items
by Terri Agnew 09 Mar '22

09 Mar '22

Hi Philippe, Thank you ever so much. This will be noted on the motions wiki page<https://community.icann.org/x/2NMGCw> shortly. Kindest regards, Terri From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "philippe.fouquart--- via Gnso-secs" <gnso-secs(a)icann.org> Reply-To: "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com> Date: Wednesday, March 9, 2022 at 6:57 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org>, Tomslin Samme-Nlar <mesumbeslin(a)gmail.com> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [gnso-secs] [council] Motion to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items Hi Tomslin, everyone, Happy to second this motion. Regards, Philippe Orange Restricted From: council <council-bounces(a)gnso.icann.org> On Behalf Of philippe.fouquart--- via council Sent: Monday, February 28, 2022 12:23 PM To: council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: Re: [council] Motion to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items Dear Councilors, Further to Tomslin’s submission, a couple of notes on the approach we’re taking for this here: * This proposed extension of the CCOICI’s remit to include WS2 items materializes the proposal discussed at our last council call, so that this approach can be “socialized” with your respective SG/Cs - and be further discussed if necessary * In that spirit, feel free to request taking this out of the consent agenda if you consider having some discussion on the motion is important, * If this approach with the CCOICI is not considered fit for purpose, please elaborate on what alternative path these WS2 related items should take. Thank you, Philippe From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Tomslin Samme-Nlar via council Sent: Sunday, February 27, 2022 1:27 PM To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] Motion to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items Dear Councilors, Please find attached a motion to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items, to be considered at the GNSO Council meeting on Wednesday, 09 March 2022 at 16:30 UTC. Regards, Tomslin Orange Restricted _________________________________________________________________________________________________________________________ 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

Motion to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items
by Tomslin Samme-Nlar 09 Mar '22

09 Mar '22

Dear Councilors, Please find attached a motion to extend the GNSO Framework for Continuous Improvement Pilot Project by adding implementation of specific WS2 items, to be considered at the GNSO Council meeting on Wednesday, 09 March 2022 at 16:30 UTC. Regards, Tomslin

3 3

ICANN Zoom room requirements: Zoom Logins: First & Last Name/ Surname Only
by Nathalie Peregrine 08 Mar '22

08 Mar '22

Dear all, To ensure transparency of participation in ICANN’s multistakeholder model, please remember to sign in to Zoom sessions using your full name (e.g. First Name + Last Name/Surname). If you are in a session using the webinar format, you will need to first exit the Zoom room prior to rejoining. Please reach out to your support staff if you have any difficulties joining a Zoom session. To rename in a regular Zoom room: 1. Join the meeting. 2. Tap Participants. 3. Hover over your name on the participants list. 4. Click More. 5. Click Rename. 6. Enter the name you desire then click Rename. 7. Your name has now been changed within the meeting. To rename in a webinar Zoom room: 1. BEFORE entering the meeting, and during the login phase, update your Zoom name here: [cid:image001.png@01D83300.B8213430] 1. If you forget to do so, you can always log out of the webinar Zoom room and edit your name upon re-entering. Please contact your support staff if you run into any issues. Thank you! Kind regards, Nathalie

1 0

FW: Upcoming session and updates
by philippe.fouquart＠orange.com 08 Mar '22

08 Mar '22

Dear Councillors, Channelling this on Jeff's behalf, including the change of date for the subpro odp session if you hadnt noticed yet. Best, Philippe -------- Message d'origine -------- De : Jeff Neuman <jeff(a)jjnsolutions.com> Date : 03/03/2022 19:35 (GMT+01:00) À : Karen Lentz <karen.lentz(a)icann.org> Cc : SubPro ODP Mailman List <subpro-odp(a)icann.org>, FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>, "Sebastien(a)registry.godaddy" <sebastien(a)registry.godaddy>, "Tomslin Samme-Nlar (mesumbeslin(a)gmail.com)" <mesumbeslin(a)gmail.com>, Steve Chan <steve.chan(a)icann.org> Objet : RE: Upcoming session and updates Thanks Karen! GNSO Council Leadership – Can you please post to the Council list as soon as possible so that everyone has this same information to review. Thanks again for all of this. Sincerely, Jeff Neuman GNSO Council Liaison to SubPro ODP [cid:image001.png@01D82F03.3E891C10] 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: Karen Lentz <karen.lentz(a)icann.org> Sent: Thursday, March 3, 2022 1:30 PM To: Jeff Neuman <jeff(a)jjnsolutions.com> Cc: SubPro ODP Mailman List <subpro-odp(a)icann.org> Subject: Upcoming session and updates Hello Jeff, Prior to our March meeting, and ICANN73, I’m highlighting a few updates here: * We published on Monday the first in a blog post<https://www.icann.org/en/blogs/details/icann-subpro-odp-update-highlighting…> series covering each of the project work tracks; this one looks at Work Track 1, project governance. * In preparation for our Subsequent Procedures Operational Design Phase (SubPro ODP) ICANN73 meeting session<https://73.schedule.icann.org/meetings/GzLD4X2x8wqi5B4dp#/?limit=10&sortByF…>, we’ve posted a draft set of Initial Assumptions<https://www.icann.org/en/system/files/files/initial-assumptions-subsequent-…> that will be the ones we cover during that session. These are posted to our ODP webpage<https://www.icann.org/subpro-odp> and the session page<https://73.schedule.icann.org/meetings/GzLD4X2x8wqi5B4dp> in advance of ICANN73 as an update to the community and to help inform next week’s discussion. * Please note the ICANN73 session date and time has changed to Monday, 7 March @ 16:30 UTC. It is also a longer time slot, so we have more time for the material and for Q&A. Thank you and we look forward to the continuing engagement. Best regards, Karen _________________________________________________________________________________________________________________________ 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.

3 3

On today: additional info please read ! Joint GNSO & ICANN Board Session: PLEASE READ: ICANN73 Sessions - GNSO Council
by Nathalie Peregrine 08 Mar '22

08 Mar '22

Dear all, The joint GNSO & ICANN Board meeting is on in little under an hour. Please ensure to: * Sign in with your FULL NAME. If you haven’t, and notice once you’re logged into today’s webinar room, you will need to log out and back in again. Failure to do so may result in removal from the room. * Join early for the soundcheck if you intend to speak. * When you speak ensure you have ALL notifications turned off and are using a headset. * Have the soundcheck text to hand: “Hello, my name is ______________ and I am participating during this session in a speaking role. I am testing my audio and my speaking pace to confirm whether all language service providers are able to hear me clearly. If you would like me to repeat this test, please let me know. Thank you.” * Remember this call will be interpreted, please state your name, speak slowly and loudly. KEY POINTS TO REMEMBER: * Email and calendar invitations will not be sent out for ICANN73 sessions. * Refer to the How to Get Organized email circulated<https://mm.icann.org/pipermail/council/2022-February/025439.html> on the GNSO Council mailing list and attached to this email for your convenience. * You will need to register to the ICANN73 website [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/iIoxWhSuDevyDaBS…> and download the sessions you are interested in to your individual calendars. ICANN73 SESSIONS WHERE COUNCILOR ATTENDANCE IS HIGHLY ENCOURAGED: 1. Joint GNSO & ICANN Board Session Tuesday 8 March 2022 at 09:00 local time (13:00 UTC) 1. GNSO Council meeting Wednesday 9 March 2022 at 12:30 local time (16:30 UTC) 1. Joint GNSO & ALAC session Wednesday 9 March 2022 at 16:30 local time (20:30 UTC) 1. GNSO Council Wrap Up Thursday 10 March 2022 at 10:30 local time (14:30 UTC) ADDITIONAL SESSIONS OF INTEREST TO COUNCILORS: * Wednesday 9 March: Plenary Session: Evolving the DNS Abuse Conversation * Thursday 10 March: Discussion Forum on Geopolitical Legislative and Regulatory Developments, followed by the ICANN Public Forum and the ICANN Public Board Meeting. Please reach out the gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> should you run into any issues. Kind regards, Nathalie

1 0

Re: [council] [CORRESPONDENCE] Maarten Botterman to Manal Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics
by philippe.fouquart＠orange.com 07 Mar '22

07 Mar '22

Hi again everyone, Further to our exchange with GAC earlier today and as additional background: Sebastien, Tomslin, Jeff and I had the opportunity to discuss what such a dialogue with GAC might look like, and in a recent conversation with Goran and exchange with Maarten I mentioned that we'd discussed potential guardrail that could facilitate and guide a tighter and more constructive dialogue - at least one that's likely to converge rather than relitigate the same arguments. As a Council, we may want to discuss these and certainly other ideas. I would also note that I anticipate some of that suggested structure will be incorporated into the framing document being prepared by ICANN org and that's referred to in the letter. We should have the opportunity to discuss this either at our Council call or during wrapup. Regards, Philippe From: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Sent: Sunday, March 6, 2022 10:26 PM To: council@gnso icann. org <council(a)gnso.icann.org> Cc: gnso-secs(a)icann.org Subject: FW: [CORRESPONDENCE] Maarten Botterman to Manal Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics Dear Councilors, Please consider the following and attached correspondence from the Board. Regards, Philippe -------- Message d'origine -------- De : Wendy Profit <wendy.profit(a)icann.org<mailto:wendy.profit@icann.org>> Date : 06/03/2022 22:03 (GMT+01:00) À : manal.ismail(a)board.icann.org<mailto:manal.ismail@board.icann.org>, manal(a)tra.gov.eg<mailto:manal@tra.gov.eg>, FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc : Maarten Botterman <maarten.botterman(a)board.icann.org<mailto:maarten.botterman@board.icann.org>>, gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>, GACSTAFF <gac-staff(a)icann.org<mailto:gac-staff@icann.org>>, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>, Board Ops Team <board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>>, Correspondence <Correspondence(a)icann.org<mailto:Correspondence@icann.org>>, Secretary <secretary(a)icann.org<mailto:secretary@icann.org>> Objet : [CORRESPONDENCE] Maarten Botterman to Manal Ismail and Philippe Fouquart - GAC-GNSO Consultation on Closed Generics Dear Manal and Philippe, Please find the attached letter from ICANN Chair Maarten Botterman regarding a proposed formal consultation between the GAC and GNSO Council on how to handle the subject of closed generics in gTLD applications. Thank you and best regards, Wendy Profit ICANN Board Operations Senior Manager 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 _________________________________________________________________________________________________________________________ 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

FW: [GNSO-Accuracy-ST] FYI - Latest Developing Board Guidance on RDS Accuracy
by Marika Konings 07 Mar '22

07 Mar '22

For your information, this is the communication that Manal referenced during the joint GNSO-GAC session. Best regards, Marika From: GNSO-Accuracy-ST <gnso-accuracy-st-bounces(a)icann.org> on behalf of Brian Gutterman <brian.gutterman(a)icann.org> Date: Monday, 7 March 2022 at 18:37 To: "gnso-accuracy-st(a)icann.org" <gnso-accuracy-st(a)icann.org> Subject: [GNSO-Accuracy-ST] FYI - Latest Developing Board Guidance on RDS Accuracy Hi all, FYI As Becky has referenced during our session today, the below was sent to the GAC leadership from Goran yesterday re. some of the latest thinking and discussions of the Board re. registration data accuracy. Best, Brian RE: For GAC Leadership Information – ICANN73 Prep – Latest Board Feedback Planned on Accuracy of Registration Data Dear Manal and GAC Vice-Chairs, As you know, the Board had some productive workshop discussions this weekend regarding continued ICANN org efforts to ensure the accuracy of registration data. As a result of the discussions, further Board guidance has been developed for how to address these issues going forward. The language set forth below has been developed as a guide for further oral discussions the Board may have with community groups during ICANN73. It is likely to be shared Monday during discussions with the GNSO and later in the week during the GAC’s meeting with the ICANN Board. “The ICANN Board first of all would like to highlight its support for continued efforts to ensure the accuracy of registration data. ICANN org continues to advocate for greater clarity from the competent European authorities on several outstanding questions and issues regarding the application of the GDPR to registration data when opportunities arise. The issue of data accuracy is one of the areas that would benefit from greater clarity. In relation to data accuracy, the ICANN Board has requested ICANN org to prepare a number of specific scenarios for which it will consult the EDPB on whether or not ICANN org has a legitimate purpose that is proportionate, i.e., not outweighed by the privacy rights of the individual data subject(s) to request Contracted Parties to provide access to individual records as well as bulk access to registration data in order to review the accuracy of registration data. The ICANN Board is of the view that this clarification will further inform discussions on this topic and will be helpful to address the issue of accuracy, as ICANN org could take further steps like restart the WHOIS ARS. The EC has committed to facilitate ongoing dialogue with the EDPB and European DPAs. We hope the EC will help bring this question to the level of the EDPB. We highlight that the CPs have a responsibility for the accuracy of the data. A Registrant has to provide accurate data to a Contracted Party who has the obligation to confirm that existing accuracy requirements are being met. If a Registrant is found not to meet the obligation to provide accurate data, the registration will be suspended. Furthermore, upon notification by any person of an inaccuracy, including at CPs own initiative, in the contact information associated with a Registered Name sponsored by Registrar, Registrar must take reasonable steps to investigate that claimed inaccuracy. But here is the problem, Registration Data is no longer publicly available which makes it difficult if not impossible to see if the Registrant listed is Mickey Mouse. Even for ICANN org.” Please let me know if I can provide further preparation information for the GAC meeting with the Board later this week. Best, Göran #. #. #

1 0