November 2021 - council - lists.icann.org

FW: [gnso-chairs] Board liaisons to GNSOs Registration Data Accuracy Team
by philippe.fouquart＠orange.com 18 Nov '21

18 Nov '21

Dear Councilors, Please note the following correspondence from Maarten Botterman regarding the appointment of Becky Burr and Harald Alvestrand as Board liaisons to the accuracy scoping team. Regards, Philippe Orange Restricted From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> On Behalf Of maarten.botterman--- via Gnso-chairs Sent: Thursday, November 18, 2021 7:05 PM To: Gnso-chairs(a)icann.org; Gnso-secs(a)icann.org Cc: 'Secretary' <secretary(a)icann.org>; harald.alvestrand(a)board.icann.org; becky.burr(a)board.icann.org; 'Board Ops Team' <board-ops-team(a)icann.org> Subject: [gnso-chairs] Board liaisons to GNSOs Registration Data Accuracy Team Dear Philippe, I'm writing to notify you that the ICANN Board has selected two members of the Board to serve as liaisons to the GNSO Registration Data Accuracy Scoping Team. They are Becky Burr and Harald Alvestrand (alternate); and you may already be in communication with them in this regard. This email serves as official notification of their appointments. The Board liaisons will share on a regular basis any input the Board may have that will inform the GNSO Registration Data Accuracy Scoping Team deliberations and ongoing work. Thank you, Maarten Botterman Chair, ICANN Board of Directors _________________________________________________________________________________________________________________________ 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] Thursday, 18 November 2021 | TODAY: SSAD ODP Webinar
by Julie Bisland 18 Nov '21

18 Nov '21

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, November 18, 2021 at 10:00 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 18 November 2021 | TODAY: SSAD ODP Webinar [https://r20.rs6.net/on.jsp?ca=2841ebd8-d920-4fc1-bee7-93c7c5f3722e&a=112202…] Thursday, 18 November 2021 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=001LiD7_1SgRvIuF4RK…> Table of Contents Webinars · TODAY: SSAD ODP Project Update · REMINDER: Register Now: FY23 ABR Process Information Sharing · NEW: ICANN and NARALO Join Forces to Build a More DIgitally Inclusive Internet · NEW: Chair's Blog: Highlights from October ICANN Board Workshop and ICANN72 · NEW: ICANN74 Fellowship Application Round Now Open · REMINDER: Join ICANN's Discussions at the 16th Internet Governance Forum Public Comment · Proposal for Latin Script Root Zone Label Generation Rule · Proposed Revisions to the ICANN Documentary Information Disclosure Policy · REMINDER: ICANN Launches Improved Public Comment Feature Webinars TODAY: SSAD ODP Project Update Webinar ICANN will host a webinar today at 16:00 UTC to provide an update on the System for Standardized Access/Disclosure Operational Design Phase (SSAD ODP). The webinar will be presented in English with interpretation in Arabic, Chinese, French, Russian, and Spanish available through the Adigo dial in line. Video and audio recordings will be published on the SSAD ODP webpage [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…>. Please register in advance for the webinar. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> REMINDER: Register Now: FY23 ABR Process Webinar Registration is now open for the FY23 Additional Budget Request (ABR) Process Webinar that will be held on Tuesday, 30 November 2021 at 16:00 UTC. Register here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Information Sharing NEW: ICANN and NARALO Join Forces to Build a More DIgitally Inclusive Internet ICANN org has partnered with the North American Regional At-Large Organization [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…>(NARALO) and the Universal Acceptance Steering Group (UASG) to host a Universal Acceptance (UA) training series for the North America region in early 2022. The series aims to increase UA awareness across the region and provide an opportunity to engage with technical stakeholders directly. This initiative is part of ICANN's Regional Universal Acceptance Training Program [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> NEW: Chair's Blog: Highlights from October ICANN Board Workshop and ICANN72 The ICANN72 Annual General Meeting concluded with a clear focus of the job ahead. In our interaction with the constituencies over the week, prioritization was a frequent topic. The ICANN community, Board, and organization all have a role to play in how our work is conducted, and transparency in our processes is critical. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> NEW: ICANN74 Fellowship Application Round Now Open ICANN opened the Fellowship Program application round for ICANN74. This round is open only to those who have previously completed an ICANN Fellowship because ICANN74 is a Policy Forum. The meeting is scheduled for 13-16 June 2022 in The Hague, Netherlands. If ICANN74 is held virtually, the Fellowship Program will also be held virtually. The deadline to apply is 15 December 2021, 23:59 UTC. Successful candidates will be announced on 10 February 2022 on the ICANN website. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> REMINDER: Join ICANN's Discussions at the 16th Internet Governance Forum Members of the ICANN community, Board, and organization (org) will participate in the S [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…>ixteenth Annual Meeting of the Internet Governance Forum (IGF) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…>, to be held as a hybrid meeting from 6 to 10 December 2021. Hosted by the government of Poland, this year's overarching theme is: ‎‎"Internet United," conveying that the Internet connects all its users into one community, responsible for its shape and functioning. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Public Comment Proposal for Latin Script Root Zone Label Generation Rules [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Open for Submissions Date: Thursday, 23 September 2021 Closed for Submissions Date: Tuesday, 23 November 2021 Proposed Revisions to the ICANN Documentary Information Disclosure Policy [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Open for Submissions Date: Thursday, 21 October 2021 Closed for Submissions Date: Monday, 06 December 2021 REMINDER: ICANN Launches Improved Public Comment Feature The Information Transparency Initiative (ITI) has reached another important milestone with the release of an improved Public Comment feature. This enhanced feature is part of the ICANN organization's ongoing commitment to increase the findability and transparency of our information. Read more about the improvements! [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…>. Infographic: What is Public Comment? [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Step-by-Step Public Comment Submission Guidelines [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Zoom Replay: Public Comment Submission Training [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Zoom Replay: Public Comment User Experience Demonstration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> Volume 3, Issue 84 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…> | Next Issue: Monday, 22 November 2021 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001LiD7_1SgRvIuF4RK…>

1 0

presentations from ICANN for GNSO meetings
by Maxim Alzoba 18 Nov '21

18 Nov '21

Hello all, I would suggest we ask ICANN staff to provide us with the materials of the future ICANN presentations (slides) for GNSO meetings at least one day in advance of GNSO Council meeting to avoid the situations like we had today where the valuable time was spent to read aloud the slides instead of having a meaningful discussion. I think such request would follow our SPS discussions about productivity and effectiveness. Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (.Moscow)

3 3

Recordings & Zoom chat | GNSO Council Meeting Thursday, 18 November 2021
by Nathalie Peregrine 18 Nov '21

18 Nov '21

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and chat of the GNSO Council Meeting held on Thursday, 18 November 2021. Audio only: https://icann.zoom.us/rec/play/VzY-2XO_H_PHM88HbwlItqqHFgV9GasuBJNdEpuQfqzf… [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/VzY-2XO_H_PHM88Hb…> Zoom Recording (includes chat and visual and rough transcript. To access the rough transcript, select the Audio Transcript tab): https://icann.zoom.us/rec/play/MqRYwQq0JDueDm8w6-zRL7GiCCAKFKX4hgc7qEzIF987… [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/play/MqRYwQq0JDueDm8w6…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar#nov [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> With kind regards, Nathalie

1 0

GNSO Council resolutions 18 November 2021
by Nathalie Peregrine 18 Nov '21

18 Nov '21

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday 18 November 2021 which will be shortly posted on the GNSO Council resolutions [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. 20221118-1 Consent Agenda Motion - Confirmation of GNSO Representative to the Empowered Community Administration Whereas, 1. The GNSO Council confirmed in October 2021 that the GNSO Chair (currently Philippe Fouquart) will represent the GNSO as the Decisional Participant on the Empowered Community (EC) Administration on an interim basis. 2. The GNSO Council leadership team subsequently met to agree who from the Council leadership should perform the role of GNSO representative to the Empowered Community Administration and mutually agreed that Philippe Fouquart would serve in the role. Resolved, 1. The GNSO Council hereby confirms that Philippe Fouquart, GNSO Chair will represent the GNSO as the Decisional Participant on the Empowered Community Administration until the end of his term at ICANN75. 2. The GNSO representative shall act solely as directed by the GNSO Council in accordance with the ICANN Bylaws and other related GNSO Operating Procedures. 3. The GNSO Council requests the GNSO Secretariat to communicate this decision to the ICANN Secretary which will serve as the required written certification from the GNSO Chair designating the individual who shall represent the Decisional Participant on the EC Administration Vote results<https://gnso.icann.org/sites/default/files/policy/2021/vote-result/gnso-cou…> 20221118-2 Consent Agenda Motion to adopt the GNSO Review of the GAC ICANN72 Virtual Annual General Meeting Communiqué for submission to the ICANN Board Whereas, 1. The Governmental Advisory Committee (GAC) advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO Council has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO Council's review of the GAC Communiqué is intended to further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO Resolved, 1. The GNSO Council adopts the GNSO Council Review of the ICANN72 GAC Communiqué (see https://gac.icann.org/advice/communiques/icann72-gac-communique.pdf) and requests that the GNSO Council Chair communicate the GNSO Council Review of the ICANN72 GAC Communiqué to the ICANN Board. 2. The GNSO Council requests that the GNSO Liaison to the GAC also informs the GAC of the communication between the GNSO Council and the ICANN Board. Vote results<https://gnso.icann.org/sites/default/files/policy/2021/vote-result/gnso-cou…> 20221118-3 Motion -Approval of the Revised GNSO Councilor Job Description for the Nominating Committee - WITHDRAWN Whereas, 1. Section 11.3 of the ICANN Bylaws prescribes the number of Council representatives selected from each GNSO Stakeholder Group and three representatives selected by the Nominating Committee. 2. The Contracted Parties House consists of three members from the Registries Stakeholder Group, three members from the Registrars Stakeholder Group, and one voting member appointed by the ICANN Nominating Committee for a total of seven voting members. 3. The Non Contracted Parties House consists of six members from the Commercial Stakeholder Group, six members from the Non-Commercial Stakeholder Group, and one voting member appointed by the ICANN Nominating Committee to that House for a total of thirteen voting members. 4. The Nominating Committee reviews applications and selects candidates, taking into account the criteria or guidance provided by the GNSO Council. 5. The GNSO Council is invited on an annual basis to review the job description and criteria contained in order to better assure that the Nominating Committee selects appointees that is consistent with the intent of the Bylaws in furthering the Council’s roles and responsibilities as the manager of the policy development process of the GNSO. 6. The GNSO Council has elected to make incremental changes to the job description each year when invited. 7. Considering that each GNSO Stakeholder Group and Constituency is represented on the GNSO Council, the role of the Nominating Committee Appointees on the GNSO Council, and the importance of independence and diversity, the Council revised the job description to reflect the traits it is seeking for appointees. Resolved, 1. The GNSO Council approves the revised GNSO Councilor job description<https://gnso.icann.org/sites/default/files/file/field-file-attach/updated-n…> for use by the 2022 Nominating Committee. 2. The GNSO Council requests that the GNSO Secretariat provide the updated job description to the ICANN Org staff supporting the Nominating Committee in a timely manner Vote results<https://gnso.icann.org/sites/default/files/policy/2021/vote-result/gnso-cou…> Thank you. Kind regards, Nathalie

1 0

FW: Question Set #1
by philippe.fouquart＠orange.com 18 Nov '21

18 Nov '21

Dear coucilors, For your consideration for the AOB. Regards Philippe -------- Message d'origine -------- De : Jeff Neuman <jeff(a)jjnsolutions.com> Date : 18/11/2021 00:49 (GMT+01:00) À : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>, Sebastien(a)registry.godaddy, Tomslin Samme-Nlar <mesumbeslin(a)gmail.com> Cc : Steve Chan <steve.chan(a)icann.org> Objet : RE: Question Set #1 All, This Google Doc: https://docs.google.com/document/d/1vpL6xHHVlmm5Q1Q1MuPz8I4ZgthV6EkO58JE4SA… contains my proposed responses for the Council to consider if you can forward on to the Council members. Again, these are my proposed responses after doing a little research and from what I recall. I think I set this document up right giving everyone with the link the ability to make comments but not to change the text without it appearing as redlines. Can you please forward this on to the Council as well? Thanks. Sincerely, Jeff [cid:image001.png@01D7DBE3.C0384010] 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: Jeff Neuman Sent: Wednesday, November 17, 2021 5:16 PM To: philippe.fouquart(a)orange.com; Sebastien(a)registry.godaddy; Tomslin Samme-Nlar <mesumbeslin(a)gmail.com> Cc: Steve Chan <steve.chan(a)icann.org> Subject: FW: Question Set #1 Dear Council Leadership, Please find enclosed the first set of questions/assumptions from ICANN Org that was just sent out and is (or soon will be) published on the SubPro ODP webpage at https://www.icann.org/subpro-odp. Within the next 24 hours, I will send to you all my proposed responses to help the Council provide a timely response to the ICANN Org SubPro ODP team. Can you please forward this to the Council as soon as possible to give you all a heard start on thinking about these questions / assumptions? Sincerely, Jeff [cid:image001.png@01D7DBE3.C0384010] 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<mailto:karen.lentz@icann.org>> Sent: Wednesday, November 17, 2021 4:56 PM To: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Cc: SubPro ODP Mailman List <subpro-odp(a)icann.org<mailto:subpro-odp@icann.org>>; Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Subject: Question Set #1 Dear Jeff, I hope this note finds you well. While, as you know, the Board resolution provided for an approximate 3-month period of internal project organization prior to beginning the substantive work of the Operational Design Phase (ODP), we have in the course of our work already identified some preliminary questions. I wanted to share and convey these questions to you, as GNSO Council Liaison. This set of questions mostly concerns areas where we are trying to reconcile recommendations across topics and looking for confirmation as to whether our assumptions are correct, to ensure the ODP assessment is based on the correct understanding of the recommendations. As the GNSO Council Liaison, we ask that you please relay our understanding to obtain the Council’s verification and/or feedback as appropriate and provide a response when available. Thank you also for completing the scheduling poll for the introductory call in your role as GNSO Council Liaison. As we make progress on the ODP in the coming months, the project team will engage with you if any questions or issues arise regarding the substance or intent of any of the SubPro policy recommendations. In the meantime, please do not hesitate to reach out to the team at subpro-odp(a)icann.org<mailto:subpro-odp@icann.org>. For transparency, our email correspondence is published on our SubPro ODP webpage at https://www.icann.org/subpro-odp. On behalf of the ICANN org SubPro ODP team, thank you for volunteering to support this important process. We look forward to working with you. Thank you Karen = Questions Topic 3: Applications Assessed in Rounds 1. Implementation Guidance 3.4. ICANN org would like to confirm its assumption that the particular terms used [regarding application status] can potentially be changed based upon need during implementation and remain consistent with the Implementation Guidance. 2. Recommendation 3.6. Recommendation 3.6 appears to envision that ICANN org would open an application round, process the applications, and then open another round, while a Competition, Consumer Trust & Consumer Choice (CCT) review on the former would take place concurrently with the latter. Is this assumption correct? If so, how is this intended to interact with the Bylaws provision 4.6(d) which indicates that the CCT Review Team identifies recommendations that “must be implemented before opening subsequent rounds”? Notes * Section 4.6(d) of the Bylaws includes: (ii) After a New gTLD Round has been in operation for one year, the Board shall cause a competition, consumer trust and consumer choice review as specified in this Section 4.6(d) ("CCT Review"). (iii) The review team for the CCT Review ("CCT Review Team") will examine (A) the extent to which the expansion of gTLDs has promoted competition, consumer trust and consumer choice and (B) the effectiveness of the New gTLD Round's application and evaluation process and safeguards put in place to mitigate issues arising from the New gTLD Round. (iv) For each of its recommendations, the CCT Review Team should indicate whether the recommendation, if accepted by the Board, must be implemented before opening subsequent rounds of new generic top-level domain applications periods. * The above section of the Bylaws is expected to be updated by ATRT3 Recommendation 3.2, which provides that “There should be one additional and clearly scoped CCT Review. - It shall start within the two years after the first introduction of the (possible) next round of new gTLDs to the root. - It should be limited to a duration of one year. - Additionally, a framework of data collection must be in place prior to the next round of gTLDs and the availability of all data sets should be confirmed prior to the selection of the review members and must be provided within 30 days of the review being launched." This recommendation has been accepted but is not yet implemented. Topic 9: Registry Voluntary Commitments / Public Interest Commitments 1. Recommendation 9.1. The recommendation notes that “Mandatory Public Interest Commitments (PICs) currently captured in Specification 11 3(a)-(d) of the Registry Agreement must continue to be included in Registry Agreements for gTLDs in subsequent procedures. [...] this recommendation puts existing practice into policy.” Maintaining Spec 11.3 (d) would prohibit closed generics during the immediate next round. Therefore, this recommendation seems to be in contradiction with the outcome of no-agreement that was reached by the SubPro PDP WG on Topic 23: Closed Generics. This appears to be an oversight as the text for Topic 23 states that “Although the Working Group had numerous discussions about this topic, and received extensive comments from the community, including members of the Governmental Advisory Committee, the Working Group was not able to agree on ‘policy advice concerning exclusive generic TLDs.” Is this a correct assumption? Notes * Registry Agreement Specification 11 3(d) specifies that: “Registry Operator of a “Generic String” TLD may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others.” * A similar question was flagged in org’s comments on the Draft Final Report: “ICANN org also notes that Specification 11 3(d) is about prohibiting the use of a TLD in a closed manner. As the PDP WG continues to discuss the issue of closed generic TLDs into the subsequent rounds, we would note that, absent changes, this Recommendation to retain Specification 11 section 3(d) might conflict with the PDP WG’s ultimate Recommendation on the topic of closed generic TLDs.” 1. Recommendation 9.15. The recommendation noted that “the Working Group acknowledges ongoing important work in the community on the topic of DNS abuse and believes that a holistic solution is needed to account for DNS abuse in all gTLDs as opposed to dealing with these recommendations with respect to only the introduction of subsequent new gTLDs. In addition, recommending new requirements that would only apply to the new gTLDs added to the root in subsequent rounds could result in singling out those new gTLDs for disparate treatment in contravention of the ICANN Bylaws. Therefore, this PDP Working Group is not making any recommendations with respect to mitigating domain name abuse other than stating that any such future effort must apply to both existing and new gTLDs (and potentially ccTLDs).” The GNSO Council review of the ICANN71 GAC communique noted that “the Subsequent Procedures and RPM PDPs have addressed many of the issues raised in the CCT Review Team (CCT-RT) Final Report that were referred from the ICANN Board to the GNSO. For the DNS abuse recommendations contained within the CCT-RT Final Report, the GNSO Council is still in the process of determining whether any policy work is needed, and if so, how that work will be carried out.” Are there any further considerations from the GNSO on handling GAC advice on DNS abuse in the next round, or updates on whether such work is planned or will be carried out during the Operational Design Phase, so that this can be factored into our planning and assessment? Topic 27: Applicant Reviews 1. Implementation Guidance 27.16/27.17. Implementation Guidance items 27.16 and 27.17 appear to be inconsistent with one another. The guidance that ICANN “should not evaluate proposed business models" is difficult to reconcile with Implementation Guidance 27.17, which states, “the evaluation should determine whether an applicant will be able to withstand missing revenue goals, exceeding expenses, funding shortfalls, or the inability to manage multiple TLDs in the case of registries that are dependent upon the sale of registrations.” To carry out IG 27.17, which also notes for instance that “....determining the financial wherewithal of an applicant to sustain the maintenance of a TLD may require different criteria for different types of registries; criteria should not be established in a ‘one-size-fits-all’ manner,” there seems to be a need to identify and consider the relevant business model as part of the evaluation. Is this a possible oversight and if not, can you provide additional insight to how these two items should be read? Topic 35: Auctions: Mechanisms of Last Resort / Private Resolution of Contention Sets 1. Recommendation 35.3. The recommendation states that applications must be submitted with bona fide intention to operate, noting that if a string is not delegated within two (2) years of the effective date of the registry agreement, this may be a factor considered by ICANN in determining lack of bona fide intention to operate the gTLD for that applicant. Affirmation 40.2, on TLD Rollout, supports maintaining the timeframes for delegation and contracting used in the 2012 round, namely, 9 months to enter a registry agreement and entry of the TLD into the root zone within 12 months of the effective date of the registry agreement. Our assumption is that the two years is a maximum, such that extensions exceeding that time may be a factor in determining lack of bona fide intention to operate the gTLD, and not that the delegation timeline for all applicants should be extended from one to two years. Is this assumption correct? _________________________________________________________________________________________________________________________ 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

**Starting in 15 minutes | Meeting Invitation | GNSO Council Meeting | Thursday, 18 November 2021 at 06:00 UTC
by Terri Agnew 18 Nov '21

18 Nov '21

**Starting in 15 minutes Dear all, The GNSO Council meeting is scheduled on Thursday, 18 November 2021 at 06: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/ewWlCg Check your time zone: https://tinyurl.com/2h7u6wjz [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2h7u6wjz__;!!PtGJab4!vUnEZYd…> 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 (recommended): https://icann.zoom.us/j/92495986646?pwd=Tk5nQzNkUlBrUDBISkxkL2RUYzFXZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92495986646?pwd=Tk5nQzNk…> If joining Zoom via Zoom App the following will be required: Webinar ID: 924 9598 6646 Password: N#eDJc23% If you are joining via audio only: iPhone one-tap : US: +16699006833,,92495986646#,,,,,,0#,,3257747295# or +19294362866,,92495986646#,,,,,,0#,,3257747295# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 929 436 2866 or +1 253 215 8782 or +1 301 715 8592 or +1 312 626 6799 or +1 346 248 7799 or 877 853 5247 (Toll Free) or 888 788 0099 (Toll Free) Webinar ID: 924 9598 6646 Passcode: 3257747295 International numbers available: https://icann.zoom.us/u/ahyuWF23v [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/ahyuWF23v__;!!PtGJab4!vU…> 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/eQWlCg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

**ON AT THE TOP OF THE HOUR** Meeting Invitation | GNSO Council Meeting | Thursday, 18 November 2021 at 06:00 UTC
by Nathalie Peregrine 18 Nov '21

18 Nov '21

Dear all, The GNSO Council meeting is scheduled on Thursday, 18 November 2021 at 06: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/ewWlCg Check your time zone: https://tinyurl.com/2h7u6wjz [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2h7u6wjz__;!!PtGJab4!vUnEZYd…> 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 (recommended): https://icann.zoom.us/j/92495986646?pwd=Tk5nQzNkUlBrUDBISkxkL2RUYzFXZz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92495986646?pwd=Tk5nQzNk…> If joining Zoom via Zoom App the following will be required: Webinar ID: 924 9598 6646 Password: N#eDJc23% If you are joining via audio only: iPhone one-tap : US: +16699006833,,92495986646#,,,,,,0#,,3257747295# or +19294362866,,92495986646#,,,,,,0#,,3257747295# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 929 436 2866 or +1 253 215 8782 or +1 301 715 8592 or +1 312 626 6799 or +1 346 248 7799 or 877 853 5247 (Toll Free) or 888 788 0099 (Toll Free) Webinar ID: 924 9598 6646 Passcode: 3257747295 International numbers available: https://icann.zoom.us/u/ahyuWF23v [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/ahyuWF23v__;!!PtGJab4!vU…> 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/eQWlCg> referenced in the agenda will be gathered on a Wiki page for convenient and easy access. Thank you. Kind Regards, Terri

1 0

Re: [council] FW: SubPro ODP Liaison Update to GNSO Council
by Steve Chan 18 Nov '21

18 Nov '21

Dear Councilors, I just wanted to let you know that the SubPro ODP mail archive is currently unavailable on the ODP page, but the ICANN org team is working on making sure it is available. Best, Steve From: council <council-bounces(a)gnso.icann.org> on behalf of "philippe.fouquart--- via council" <council(a)gnso.icann.org> Reply-To: "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com> Date: Tuesday, November 16, 2021 at 2:07 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] FW: SubPro ODP Liaison Update to GNSO Council Dear Councillors, Please see Jeff's report as Councils liaison to the SubPro ODP. We can have this as an AOB for our Council call Regards, Philippe -------- Message d'origine -------- De : Jeff Neuman <jeff(a)jjnsolutions.com> Date : 16/11/2021 15:21 (GMT+01:00) À : FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com>, Sebastien(a)registry.godaddy, Tomslin Samme-Nlar <mesumbeslin(a)gmail.com> Cc : Steve Chan <steve.chan(a)icann.org>, subpro-odp(a)icann.org Objet : SubPro ODP Liaison Update to GNSO Council Dear GNSO Council Leadership, Please find below, my first update as the ODP Liaison to the Subsequent Procedures Operational Design Phase (SubPro ODP). Although I understand that I have posting privileges to the Council in my other capacity, I ask that you all forward these updates to the GNSO Council on my behalf. Summary: ICANN Org is still in preparation mode for the SubPro ODP, but we are looking to set up a kickoff call the week of November 29th. An ODP Mailing list has been set up at subpro-odp(a)icann.org<mailto:subpro-odp@icann.org> which is available for anyone to contact the SubPro team and is linked from https://www.icann.org/subpro-odp. More Details: * October 27, 2021: I was notified by the GNSO Council of my appointment as the SubPro ODP Liaison. * November 3, 2021: * I reached out to Karen Lentz, Vice President of Policy Research and Stakeholder Engagements with ICANN Org seeking ICANN Org’s thoughts on setting up a kickoff meeting and asking about ICANN Org’s expectations, frequency of meetings, a mailing list, etc. I also let them know about the discussion that occurred at our wrap up session about the Council’s desire for more transparency in the ODP process above and beyond that currently occurring in the SSAD ODP. * Karen responded the same day letting me know that they were still doing some project organization work which also covered the topics about which I was inquiring. Their working assumption is that we would meet at least once a month (or every 4 weeks), but that this could increase (or decrease) depending on need. Karen said they would be reaching out soon to det up the kick off meeting. * November 8, 2021: * I informed Karen that the document deadline for the Council meeting was approaching and that I thought it would be a good idea in the future to (a) let the Council know by each Council meeting’s document deadline whether there would be a need to add an agenda item for Council meetings, and (b) provide any questions/documents intended to be discussed at the Council meeting by the document deadline. * Karen responded that that made sense for the future, but that ICANN did not believe there were any items to include for the Council meeting on November 18th. * November 15, 2021: Karen reached out to me letting me know that they may have one or more liaison questions coming up soon and that they would work to the December Council meeting due dates. In the meantime, they said they would be sending around a Doodle poll shortly to schedule an introductory meeting the week of November 29th. Please let me know if you have any questions or comments and/or whether you want more or less detail for future updates. In addition, if there are any items that you want me to convey to ICANN Org regarding the ODP, I would be happy to do so. Sincerely, Jeff Neuman SubPro ODP Liaison [cid:image001.png@01D7DB08.B523E9D0] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 1

Re: [council] [Ext] RE: Draft Motion - GNSO Council Review of the GAC Communique
by Nathalie Peregrine 17 Nov '21

17 Nov '21

Thank you Philippe, this is noted and the wiki motion page has been updated. I would like to remind councilors that seconders are missing for the two remaining motions: Confirmation of the GNSO Representative to the Empowered Community Administration and the Approval of the revised GNSO Councilor Job Description for the Nominating Committee. Kind regards, Nathalie From: "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com> Date: Wednesday, 17 November 2021 at 18:10 To: desiree-me <desiree-me(a)protonmail.com>, Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Ext] RE: [council] Draft Motion - GNSO Council Review of the GAC Communique Thanks Nathalie, I would like to second the motion. Regards, Philippe From: council <council-bounces(a)gnso.icann.org> On Behalf Of desiree-me via council Sent: Thursday, November 11, 2021 4:46 PM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Cc: council(a)gnso.icann.org Subject: Re: [council] Draft Motion - GNSO Council Review of the GAC Communique Dear Councilors Please find attached the copy of the Review of the GAC Communique. Kind regards Desiree -- Sent with ProtonMail [protonmail.com]<https://urldefense.com/v3/__https:/protonmail.com/__;!!PtGJab4!q_pIE_SOF6VK…> Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, November 8th, 2021 at 9:29 PM, Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>> wrote: Dear Desiree, Thank you for submitting the placeholder motion for Council to approve the GNSO Council Review of the GAC Communique. It has now been published on the Motions wiki page<https://community.icann.org/display/gnsocouncilmeetings/Motions+2021-11-18> for the Council meeting on the 18 November 2021. Kind regards, Nathalie From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Reply to: desiree-me <desiree-me(a)protonmail.com<mailto:desiree-me@protonmail.com>> Date: Monday, 8 November 2021 at 22:11 To: "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: [council] Draft Motion - GNSO Council Review of the GAC Communique Dear Councilors, Following the GNSO Council small work group call today, please find attached the copy of the Draft Motion for the GNSO Council Review of the GAC Communiqué, to be considered at the GNSO Council meeting on Thursday, 18 November 2021 at 6:00 UTC. Kind regards Desiree -- 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.

2 1