April 2022 - council - lists.icann.org

FW: [gnso-chairs] Letter from Bruna Santos to Philippe Fouquart - NCSG Response to the Board's Proposal for a Council-GAC dialogue on Closed Generics
by philippe.fouquart＠orange.com April 14, 2022

April 14, 2022

Dear Councilors, Please see the NCSG letter to Council below. I suppose people may not have the time to read it in detail before our call but our NCSG colleagues may want to refer to this during our discussion item on closed generics. As a side note I'm having difficulty with the attachment (the scanned text seems truncated on my end) but assuming it's just me, I prefer to share. Regards, Philippe -------- Message d'origine -------- De : Bruna Martins dos Santos via Gnso-chairs <gnso-chairs(a)icann.org> Date : 14/04/2022 13:29 (GMT+01:00) À : gnso-chairs(a)icann.org Cc : 陳曼茹 Manju Chen <manju(a)nii.org.tw>, Kathy Kleiman <kathy(a)kathykleiman.com>, Andrea Glandon <andrea.glandon(a)icann.org>, ncsg-pc <ncsg-pc(a)lists.ncsg.is> Objet : Re: [gnso-chairs] Letter from Bruna Santos to Philippe Fouquart - NCSG Response to the Board's Proposal for a Council-GAC dialogue on Closed Generics Resending the version of the letter in PDF format. Best, Bruna Santos On Thu, Apr 14, 2022 at 1:04 PM Bruna Martins dos Santos <bruna.mrtns(a)gmail.com<mailto:bruna.mrtns@gmail.com>> wrote: Dear Philippe, Sebastien and Tomslin, I hope this email finds you well. Please find attached NCSGs letter in response to the Board's Proposal for a GNSO Council & GAC dialogue on Closed Generics, to yours and GNSO council appreciation. We trust that this communication will provide the council with the current concerns shared by our part of the community and represents some of the internal discussions hosted at NCSG about the Board's recommendation of a dialogue with the GAC. We look forward to continuing our conversations with the GNSO Council and the ICANN Board regarding the Closed Generics. -- Bruna Martins dos Santos German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation<https://www.humboldt-foundation.de/> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin für Sozialforschung (WZB)<https://wzb.eu/en> Member | Coalizão Direitos na Rede<https://direitosnarede.org.br/> Chair | Non-Commercial Stakeholder Group at ICANN<https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg> Co-Coordinator | Internet Governance Caucus <https://igcaucus.org/> Twitter: @boomartins<https://twitter.com/boomartins> // Skype: bruna.martinsantos bruna.martinsdossantos(a)wzb.eu<mailto:bruna.martinsdossantos@wzb.eu> and bruna.mrtns(a)gmail.com<mailto:bruna.mrtns@gmail.com> -- Bruna Martins dos Santos German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation<https://www.humboldt-foundation.de/> Visiting Researcher (Gastwissenschaftlerin) | Wissenschaftszentrum Berlin für Sozialforschung (WZB)<https://wzb.eu/en> Member | Coalizão Direitos na Rede<https://direitosnarede.org.br/> Chair | Non-Commercial Stakeholder Group at ICANN<https://gnso.icann.org/en/about/stakeholders-constituencies/ncsg> Co-Coordinator | Internet Governance Caucus <https://igcaucus.org/> Twitter: @boomartins<https://twitter.com/boomartins> // Skype: bruna.martinsantos bruna.martinsdossantos(a)wzb.eu<mailto:bruna.martinsdossantos@wzb.eu> and bruna.mrtns(a)gmail.com<mailto:bruna.mrtns@gmail.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.

3 3

GNSO Council Absence Notification Form: Marie Pattullo
by GNSO Council via ICANN April 14, 2022

April 14, 2022

Full Name of Officer: Steve DelBianco Officer Email Address: sdelbianco(a)netchoice.org Date Prepared: 14 April 2022 GNSO Organization: Business Constituency Officer Position or Title: Vice chair for policy coordination Name of Absent Councilor: Marie Pattullo Voting Remedy: Temporary Alternate Temporary Alternate Information Reason(s) for or condition(s) leading to the remedy: Marie is not able to join the meeting Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: All business before the council on 14-Apr-2022 Date upon which the remedy will expire or terminate: 15 April 2022 Full Name of Councilor's Temporary Alternate: [Note: if not already published and available, a short bio and Statement/Disclosure of Interest should be prepared by the Temporary Alternate and delivered to the GNSO Secretariat in advance of any discussion or voting scheduled to take place]. Steve DelBianco Temporary Alternate Email Address: sdelbianco(a)netchoice.org By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0

Update: Please read: Upcoming GNSO Council meeting prep 14 April 2022 at 13:00 UTC
by Nathalie Peregrine April 13, 2022

April 13, 2022

Dear all, The slides for item 5, Overview of the EPDP on Specific Curative Rights Protections for IGOs Final Report, have been posted to the GNSO Council agenda page<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…>, but also attached to this email for your review. Thank you, Kind regards, Nathalie From: council <council-bounces(a)gnso.icann.org> on behalf of "council(a)gnso.icann.org" <council(a)gnso.icann.org> Reply to: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Wednesday, 13 April 2022 at 11:47 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Please read: Upcoming GNSO Council meeting prep 14 April 2022 at 13:00 UTC Dear all, A few reminders of prep for the Council meeting 14 April 2022 at 13:00 UTC, this week: 1. Please review the new GNSO Council meeting Cheat Sheet <https://urldefense.com/v3/__https:/docs.google.com/document/d/1lQ9fqEjD-inZ…> in order to help you prepare for the session and also provide your input in suggestion mode. 1. All documents mentioned on the Council agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> are listed on the Document wiki page<https://community.icann.org/display/gnsocouncilmeetings/Documents+2022-04-14> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/download/attachments/150178775/GNSO_Council_Pro…> and the Project List<https://community.icann.org/download/attachments/150178773/GNSO_Council_Pro…> which have been updated for this month’s Council meeting. 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. Thank you! Kind regards, Nathalie

1 0

**REMINDER** Meeting Invitation | GNSO Council Meeting | Thursday, 14 April 2022 at 13:00 UTC
by Julie Bisland April 13, 2022

April 13, 2022

Dear all, The GNSO Council meeting is scheduled on Thursday, 14 April 2022 at 13:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/9xQiCw Check your time zone: https://tinyurl.com/mwkm43zr [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/mwkm43zr__;!!PtGJab4!rNgw1IY…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92399217049?pwd=WU1GZmlaOTh6NzJ1NndkRVF0MnJEUT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92399217049?pwd=WU1GZmla…> If joining Zoom via Zoom App the following will be required: Webinar ID: 923 9921 7049 Passcode: Y&N1.Y7E%^ One tap mobile : US: +19294362866,,92399217049#,,,,*4890633693# or +13017158592,,92399217049#,,,,*4890633693# If you are joining via audio only: Dial(for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 923 9921 7049 Passcode: 4890633693 International numbers available: https://icann.zoom.us/u/abnZisZ3XE [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/abnZisZ3XE__;!!PtGJab4!r…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/_RQiCw> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

Please read: Upcoming GNSO Council meeting prep 14 April 2022 at 13:00 UTC
by Nathalie Peregrine April 13, 2022

April 13, 2022

Dear all, A few reminders of prep for the Council meeting 14 April 2022 at 13:00 UTC, this week: 1. Please review the new GNSO Council meeting Cheat Sheet <https://urldefense.com/v3/__https:/docs.google.com/document/d/1lQ9fqEjD-inZ…> in order to help you prepare for the session and also provide your input in suggestion mode. 1. All documents mentioned on the Council agenda<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> are listed on the Document wiki page<https://community.icann.org/display/gnsocouncilmeetings/Documents+2022-04-14> for easy referral. If there are any topics you would like to see appear on future Council agendas, please do not hesitate to add them to the Council Topics Google doc. <https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> 1. Please consult the Project Management Portfolio<https://community.icann.org/pages/viewpage.action?pageId=150178769>, in particular the Action Decision Radar<https://community.icann.org/download/attachments/150178775/GNSO_Council_Pro…> and the Project List<https://community.icann.org/download/attachments/150178773/GNSO_Council_Pro…> which have been updated for this month’s Council meeting. 1. If you fear you may run into connectivity issues or may not make it on the call, please have an officer of your SG/C fill in the Council Absence Notification form<https://www.icann.org/forms/gnso_notification>. Thank you! Kind regards, Nathalie

1 0

FW: SubPro ODP: Policy Question Set #3
by philippe.fouquart＠orange.com April 11, 2022

April 11, 2022

Dear Councilors, Please see the ODP Team's questions. Feel free to provide your inputs to the answers, which Jeff will put together. Regards, Philippe -------- Message d'origine -------- De : Jeff Neuman <jeff(a)jjnsolutions.com> Date : 11/04/2022 22:10 (GMT+01:00) À : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>, "Tomslin Samme-Nlar (mesumbeslin(a)gmail.com)" <mesumbeslin(a)gmail.com>, "Sebastien(a)registry.godaddy" <sebastien(a)registry.godaddy> Cc : Steve Chan <steve.chan(a)icann.org> Objet : FW: SubPro ODP: Policy Question Set #3 Dear GNSO Council Leadership, Please find enclosed ODP Question Set #3 from ICANN’s ODP Team. I have not yet read over the questions, but am forwarding this to you right away so that you can get it to the Council List as soon as possible. In line with our process, I have posted this document as a Google Doc found here<https://docs.google.com/document/d/1OtddNIUaAitHiJPE8pBTBcirTaDjyzPkcZY6BJm…>. I will then take a first cut at answers to the questions, but anyone on the Council can weigh in with comments or suggestions. Please let me know if you have any questions. Sincerely, Jeff [cid:image001.png@01D84DBE.4195F020] 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: SubPro-ODP <subpro-odp-bounces(a)icann.org> On Behalf Of Michael Karakash Sent: Monday, April 11, 2022 3:57 PM To: SubPro ODP Mailman List <subpro-odp(a)icann.org> Subject: [SubPro-ODP] SubPro ODP: Policy Question Set #3 Hi Jeff, I hope you are having a productive week. We recently drafted a new Policy Question Set (#3) focused on the topic of String Similarity that I am attaching to this email as well as pasting below. We are looking forward to our call scheduled for later this month and will circulate an agenda closer to the meeting date. Please don’t hesitate to reach out if you have questions or need any clarification before then. Thank you! Best, Michael Karakash SubPro ODP: Policy Question Set 3 - Topic 24: String Similarity 1. Affirmation 24.1: The Working Group affirms Recommendation 2 from the 2007 policy, which states “Strings must not be confusingly similar to an existing top-level domain or a Reserved Name.” Question: Recommendation 2 from 2007 does not allow for exceptions to the ‘confusingly similar’ requirement. In light of the outputs of Topic 24, the ODP will assume 24.1 is an affirmation with modification because the working group is adding new elements to the standard of confusing similarity. Does the Council agree with this assumption? 1. Affirmation 24.2 states: Subject to the recommendations below, the Working Group affirms the standard used in the String Similarity Review from the 2012 round to determine whether an applied-for string is “similar” to any existing TLD, any other applied-for strings, Reserved Names, and in the case of 2-character IDNs, any single character or any 2- character ASCII string. According to Section 2.2.1 of the 2012 Applicant Guidebook, “similar” means “strings so similar that they create a probability of user confusion if more than one of the strings is delegated into the root zone.” In the 2012 round, the String Similarity Panel was tasked with identifying “visual string similarities that would create a probability of user confusion. ”The Working Group affirms the visual standard for determining similarity with the updates included in the recommendations below. Question: Recommendation 24.3 introduces the concept of singular and plural to string similarity, meaning “mouse” and “mice” would now be considered confusingly similar. Therefore, does the Council agree with the ODP’s assumption that Affirmation of 24.2 is an affirmation with modification, meaning that the standard for determining string similarly is visual and, in light of Recommendation 24.3, also grammatical for subsequent rounds of new gTLDs? 1. Recommendation 24.3 states “Applications will not automatically be placed in the same contention set because they appear visually to be a single and plural of one another but have different intended uses.” Question: Does the Council agree with the ODP Team that based on this recommendation, all applications must provide an intended-use RVC? This will allow during subsequent rounds that the intended use of an applied-for string can be compared to the intended use of an existing string to determine whether it passes the string similarity review. 1. Recommendation 24.3 states “Applications will not automatically be placed in the same contention set because they appear visually to be a single and plural of one another but have different intended uses. “ Question: Does the Council agree that based on the wording of 24.3, the intended-use test is only applicable to the possible delegation of singulars/plurals not other visual or grammatical similarities? Meaning that applied for strings .example and .examples might both be delegated if they provide an RVC that indicates different intended use. However, .example (english) and .exemple (french), if determined to be visually similar, will never both be delegated. 1. Recommendation 24.3 states “The Working Group recommends using a dictionary to determine the singular and plural version of the string for the specific language.” Question: Does the Council agree that for each round dictionaries should be updated to the most recently published version and it is only that version that is authoritative for the purposes of accessing string similarity? 1. Recommendation 24.3 speaks only about singular/plural versions of the same word in the same language, not of other grammatical variations of the same word such as gender or conjugation. Question: Does the Council agree with the ODP assumption that only singular/plural versions can both be delegated if the intended use is different, not any other grammatical forms? If the Council agrees, the ODP team believes the following example of .hand below will be applicable for subsequent rounds: .hand and .hands * IF .hand and .hands are both applied-for strings in English THEN they both can be delegated if their intended use is different because they are singular/plural versions of one another. * IF .hand and .hands are both applied for strings in German THEN they would be placed in a contention set ONLY IF they deemed to be visually confusingly similar, and one may be delegated subject to the outcome of the contention set resolution. * IF .hand and .hände are both applied for strings in German THEN they can be delegated if their intended use is different because they are singular/plural of one another. * IF .hand is an applied for English string and .hands is an applied for German string then they would be placed in a contention set ONLY IF they deemed to be visually confusingly similar, and one may be delegated subject to the outcome of the contention set resolution. Question: In light of this, does the Council agree that this will likely require each application to indicate which languages/scripts they intend to use via an RVC and that those languages must always be offered for the life of the TLD? And to allow for future intended use determination, these RVCs will have to be submitted by all strings not just those in contention sets so that applications in future rounds can be assessed against existing RVCs. _________________________________________________________________________________________________________________________ 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: [Ext] Monday, 11 April 2022 | TOMORROW: Webinar on UN and ITU Discussions Affecting the Internet
by Julie Bisland April 11, 2022

April 11, 2022

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, April 11, 2022 at 10:00 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Monday, 11 April 2022 | TOMORROW: Webinar on UN and ITU Discussions Affecting the Internet [https://r20.rs6.net/on.jsp?ca=82f4b698-6e61-40c0-af60-e7c4316a3c45&a=112202…] Monday, 11 April 2022 ICANN Community Digest 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=001Qf8qYDAwNWgAlFrI…> Table of Contents ICANN74 · Translation/Print Deadlines · Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Webinars · NEW: Register to Join: FY22 Board Operational Priorities · TOMORROW: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet Information Sharing · NEW: ICANN Responds to Call for Evidence on EU Toolbox Against Counterfeiting · REMINDER: Request for Input - GNSO Statement of Interest · REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May Public Comment · Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) · Root Zone Update Process Study · Root Zone Label Generation Rules Version 5 (RZ-LGR-5) ICANN74 Resources Translation/Print Deadlines FRIDAY, 29 APRIL 2022: TRANSLATION DEADLINE. If your publication requires translation, please provide the final material(s) by Friday, 29 April. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. FRIDAY, 6 MAY 2022: PRINT DEADLINE ONLY. If you only need your publication printed, meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications, please provide the file to us along with the quantity you want printed and dimensions of the publication by Friday, 6 May. Please send materials to chantelle.doerksen(a)icann.org<mailto:chantelle.doerksen@icann.org>. Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> for ICANN74 (13-16 June 2022) in The Hague, Netherlands is now open. ICANN74 will take place as a hybrid event to accommodate both in-person and virtual participation. While the ICANN74 Policy Forum [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> presents the first opportunity for the community to come together in more than two years, the health and safety of all community members and staff continues to be ICANN's key priority. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…>Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…>. Webinars NEW: Register to Join: FY22 Board Operational Priorities The ICANN community is invited to join the ICANN Board on 14 April 2022 from 20:00–20:30 UTC for its upcoming informational webinar regarding the Board’s Fiscal Year 2022 operational priorities. Please click here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> to register for the webinar. Registration is required to attend. For more information about the ICANN Board, please click here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…>. TOMORROW: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet ICANN has announced that it will hold a webinar on issues impacting the Internet that are being discussed at the United Nations (U.N.) and the International Telecommunication Union (ITU). The event will take place on Tuesday, 12 April 2022 at 20:00 UTC. Please register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> for the webinar. Information Sharing NEW: ICANN Responds to Call for Evidence on EU Toolbox Against Counterfeiting ICANN announced today that on 6 April 2022 the ICANN organization (ICANN org) provided feedback to the Call for Evidence launched by the European Commission (EC) on the European Union's (EU) Toolbox Against Counterfeiting. The EU Toolbox Against Counterfeiting is part of the EC's Intellectual Property (IP) Action Plan [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…>. The initiative seeks to step up the fight against counterfeiting by clarifying the roles and responsibilities of rights holders, intermediaries, and public authorities with respect to mutual cooperation and data sharing. It is especially aimed at enhancing cooperation between parties. Intermediaries are identified as social media platforms, the domain name ecosystem, payment services, and the transport and logistics industries. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> REMINDER: Request for Input - GNSO Statement of Interest The GNSO Council has recently embarked on a review of its Statement of Interest (SOI) requirements to determine whether these are still fit for purpose, and if not, what updates should be considered. To this end, the GNSO SOI Task Force (TF) was formed. As part of its assignment, the TF is reaching out to the ICANN community to solicit input on the current use and experience with SOIs as well as suggestions for possible improvements. We understand that some of you may use the SOI, either in its current form or a modified format, for your own purposes. We would be interested to hear about those experiences as well as any lessons learned that may help inform our recommendations. You are encouraged to share this information with your respective groups. To provide input, please complete the following survey [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> by Wednesday, 4 May at the latest. Your input will be much appreciated! REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May ICANN org's eighth Middle East Domain Name System (DNS) Forum will take place virtually from Monday-Wednesday, 16-18 May 2022 and will offer a closer look at the evolving DNS ecosystem from a technical and policy perspective. It will have a special focus on regional challenges and opportunities for growth. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> Public Comment Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> Open for Submissions Date: Thursday, 03 March 2022 Closed for Submissions Date: Tuesday, 19 April 2022 Root Zone Update Process Study [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> Open for Submissions Date: Monday, 14 March 2022 Closed for Submissions Date: Monday, 25 April 2022 Root Zone Label Generation Rules Version 5 (RZ-LGR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> Open for Submissions Date: Thursday, 24 March 2022 Closed for Submissions Date: Thursday, 05 May 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…>. Volume 4, Issue 27 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…> | Next Issue: Thursday,14 April 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001Qf8qYDAwNWgAlFrI…>

1 0

Meeting Invitation | GNSO Council Meeting | Thursday, 14 April 2022 at 13:00 UTC.
by Terri Agnew April 7, 2022

April 7, 2022

Dear all, The GNSO Council meeting is scheduled on Thursday, 14 April 2022 at 13:00 UTC for 2 hours. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/9xQiCw Check your time zone: https://tinyurl.com/mwkm43zr Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92399217049?pwd=WU1GZmlaOTh6NzJ1NndkRVF0MnJEUT09 If joining Zoom via Zoom App the following will be required: Webinar ID: 923 9921 7049 Passcode: Y&N1.Y7E%^ One tap mobile : US: +19294362866,,92399217049#,,,,*4890633693# or +13017158592,,92399217049#,,,,*4890633693# If you are joining via audio only: Dial(for higher quality, dial a number based on your current location): US: +1 929 436 2866 or +1 301 715 8592 or +1 312 626 6799 or +1 669 900 6833 or +1 253 215 8782 or +1 346 248 7799 or 888 788 0099 (Toll Free) or 833 548 0276 (Toll Free) or 833 548 0282 (Toll Free) or 877 853 5247 (Toll Free) Webinar ID: 923 9921 7049 Passcode: 4890633693 International numbers available: https://icann.zoom.us/u/abnZisZ3XE [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/abnZisZ3XE__;!!PtGJab4!r…> Observers are welcome to join, they will be in a read-only and listen-only mode. Please note that all documents<https://community.icann.org/x/_RQiCw> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

FW: [Ext] Thursday, 7 April 2022 | TOMORROW: ICANN74 Design Deadline
by Julie Bisland April 7, 2022

April 7, 2022

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, April 7, 2022 at 10:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 7 April 2022 | TOMORROW: ICANN74 Design Deadline [https://r20.rs6.net/on.jsp?ca=268f0ec5-d5da-4691-8289-3b5ae8889be9&a=112202…] Thursday, 7 April 2022 ICANN Community Digest 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=001gH6OJDMchvegm3dk…> Table of Contents ICANN74 · Design/Translation/Print Deadlines · Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Webinars · NEXT WEEK: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet Information Sharing · NEW: ICANN Launches the Special Interest Forum on Technology Discussion Platform · NEW: DNSSEC Algorithm Use in 2022 · REMINDER: Request for Input - GNSO Statement of Interest · REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May Public Comment · NEW: Summary Report Published: Name Collision Analysis Project (NCAP) Study 2 Documents · Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) · Root Zone Update Process Study · Root Zone Label Generation Rules Version 5 (RZ-LGR-5) ICANN74 Resources Design/Translation/Print Deadlines TOMORROW: FRIDAY, 8 APRIL 2022: DESIGN DEADLINE. If you require design assistance for your publication, you need to provide all the text, images, layout, and publication type/size requirements (i.e. newsletter vs. 1-pager vs. trifold, etc.). You will receive a maximum of 2 iterations of the publication. Please provide everything by Friday, 8 April. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. FRIDAY, 29 APRIL 2022: TRANSLATION DEADLINE. If your publication requires translation, please provide the final material(s) by Friday, 29 April. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. FRIDAY, 6 MAY 2022: PRINT DEADLINE ONLY. If you only need your publication printed, meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications, please provide the file to us along with the quantity you want printed and dimensions of the publication by Friday, 6 May. Please send materials to chantelle.doerksen(a)icann.org<mailto:chantelle.doerksen@icann.org>. Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> for ICANN74 (13-16 June 2022) in The Hague, Netherlands is now open. ICANN74 will take place as a hybrid event to accommodate both in-person and virtual participation. While the ICANN74 Policy Forum [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> presents the first opportunity for the community to come together in more than two years, the health and safety of all community members and staff continues to be ICANN's key priority. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…>Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…>. Webinars NEXT WEEK: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet ICANN has announced that it will hold a webinar on issues impacting the Internet that are being discussed at the United Nations (U.N.) and the International Telecommunication Union (ITU). The event will take place on Tuesday, 12 April 2022 at 20:00 UTC. Please register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> for the webinar. Information Sharing NEW: ICANN Launches the Special Interest Forum on Technology Discussion Platform ICANN is pleased to announce the launching of a new discussion platform, Special Interest Forum on Technologies (SIFT). The platform will provide the ICANN community a specific place online to discuss thematic and technical issues, and to promote knowledge sharing and discussions on the evolving Identifiers technologies and their impact on ICANN's mission. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> NEW: DNSSEC Algorithm Use in 2022 The ICANN Office of the Chief Technology Office (OCTO) has published OCTO-033: DNSSEC Algorithm Use in 2022. This document gives a brief overview of the algorithms, key sizes, and other options used in DNSKEY records in the DNS near the beginning of 2022. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> REMINDER: Request for Input - GNSO Statement of Interest The GNSO Council has recently embarked on a review of its Statement of Interest (SOI) requirements to determine whether these are still fit for purpose, and if not, what updates should be considered. To this end, the GNSO SOI Task Force (TF) was formed. As part of its assignment, the TF is reaching out to the ICANN community to solicit input on the current use and experience with SOIs as well as suggestions for possible improvements. We understand that some of you may use the SOI, either in its current form or a modified format, for your own purposes. We would be interested to hear about those experiences as well as any lessons learned that may help inform our recommendations. You are encouraged to share this information with your respective groups. To provide input, please complete the following survey [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> by Wednesday, 4 May at the latest. Your input will be much appreciated! REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May ICANN org's eighth Middle East Domain Name System (DNS) Forum will take place virtually from Monday-Wednesday, 16-18 May 2022 and will offer a closer look at the evolving DNS ecosystem from a technical and policy perspective. It will have a special focus on regional challenges and opportunities for growth. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> Public Comment NEW: [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…>Summary Report Published: Name Collision Analysis Project (NCAP) Study 2 Documents [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> Open for Submissions Date: Thursday, 03 March 2022 Closed for Submissions Date: Tuesday, 19 April 2022 Root Zone Update Process Study [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> Open for Submissions Date: Monday, 14 March 2022 Closed for Submissions Date: Monday, 25 April 2022 Root Zone Label Generation Rules Version 5 (RZ-LGR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> Open for Submissions Date: Thursday, 24 March 2022 Closed for Submissions Date: Thursday, 05 May 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…>. Volume 4, Issue 26 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…> | Next Issue: Monday,11 April 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001gH6OJDMchvegm3dk…>

1 0

GNSO Council Absence Notification Form: Marie Pattullo
by GNSO Council via ICANN April 6, 2022

April 6, 2022

Full Name of Officer: Mason Cole Officer Email Address: mason.cole(a)appdetex.com Date Prepared: 6 April 2022 GNSO Organization: Business Constituency Officer Position or Title: Chair Name of Absent Councilor: Marie Pattullo Voting Remedy: Proxy Proxy Information Reason(s) for or condition(s) leading to the remedy: Marie Pattullo is unavailable for the GNSO Council meeting on 14 April 2022. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: All matters before the GNSO Council. Date upon which the remedy will expire or terminate: 15 April 2022 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). Yes Full Name of GNSO Councilor Serving as Voting Proxy: Mark Datysgeld By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy [1], and agree to abide by the website Terms of Service [2]. I Agree [1] https://www.icann.org/privacy/policy [2] https://www.icann.org/privacy/tos

1 0