April 2022 - council - lists.icann.org

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

20 Oct '22

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

1 4

Final Report of the EPDP Curative Rights for IGOs
by John McElwaine 15 Jun '22

15 Jun '22

Dear GNSO Councilors, I am forwarding herewith the Final Report of the Expedited Policy Development Process on Specific Curative Rights Protections for International Governmental Organizations (IGOs) and a Motion for approval of the five (5) final EPDP recommendations as documented in the EPDP team's Final Report. Please note that it is my understand that the Council will not vote on this motion this month, but this topic will be on the agenda to explain the report's final recommendations. If anyone has any questions, please do not hesitate to reach out. Kind regards, John [https://www.nelsonmullins.com/img/ecard-logo-125.png] JOHN C. MCELWAINE PARTNER john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> LIBERTY CENTER | SUITE 600 151 MEETING STREET | CHARLESTON, SC 29401 T 843.534.4302 F 843.722.8700 101 CONSTITUTION AVENUE, NW | SUITE 900 WASHINGTON, D.C., 20001 T 202.689.2939 F 202.689.2860 NELSONMULLINS.COM<https://www.nelsonmullins.com> VCARD<https://www.nelsonmullins.com/people/john-mcelwaine/vcard> VIEW BIO<https://www.nelsonmullins.com/people/john-mcelwaine> Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message.

4 9

Council ST on closed generics: call for additional volunteers &
by philippe.fouquart＠orange.com 04 May '22

04 May '22

Dear Councilors, Under agenda item 7 of the 14 April 2022 GNSO Council meeting, it was agreed that we would seek additional volunteers to participate in the Council small team focused on closed generics. You will recall that this group currently has a relatively small number of team members (three Councilors, the GNSO liaison to the GAC, and the ALAC liaison to the GNSO). Now that Council has provided an initial response<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/fouqu…> to the Board that it is willing to pursue next steps on a facilitated dialogue, the expanded small group will work to provide suggestions to Council about how the proposed facilitated dialogue could be carried out, namely the conditions, parameters, and methodology for the dialogue, including potential desired attributes for a facilitator. These small team suggestions are intended to form the basis for initial discussions with the GAC to identify a mutually agreeable foundation for the facilitated dialogue. If you are interested in joining the small group effort, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

Meeting Invitation | Modifying gTLD Consensus Policies with ICANN Org, GNSO Council and SG/C Chairs | Wednesday, 04 May 2022 at 13:00 UTC
by Terri Agnew 04 May '22

04 May '22

Dear all, The Modifying gTLD Consensus Policies with ICANN Org, GNSO Council and SG/C Chairs is scheduled on Wednesday, 04 May 2022 at 13:00 UTC for 90 minutes. 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…> Check your time zone: https://tinyurl.com/s9bznnp6 Please notify the GNSO Secretariat in advance if a dial out call is needed, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92367136025?pwd=U0c1dERHZ1FZT2g2Vzgzem9oRnZzdz09 Passcode: j41+?PYCmD One tap mobile : US: +13126266799,,92367136025#,,,,*2738479768# or +19294362866,,92367136025#,,,,*2738479768# Webinar ID: 923 6713 6025 Passcode: 2738479768 International numbers available: https://icann.zoom.us/u/adOEQ06SWh Observers are welcome to join, they will be in a read-only and listen-only mode. Thank you. Kind Regards, Terri

3 3

Document and Motion deadline | Monday, 09 May 2022 at 23:59 UTC for GNSO Council Meeting 19 May 2022 at 20:00 UTC
by Terri Agnew 29 Apr '22

29 Apr '22

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

1 0

FW: [Ext] Thursday, 28 April 2022 | EXTENDED-CLOSES TOMORROW: Root Zone Update Process Study
by Julie Bisland 28 Apr '22

28 Apr '22

FYI From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Thursday, April 28, 2022 at 10:17 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] Thursday, 28 April 2022 | EXTENDED-CLOSES TOMORROW: Root Zone Update Process Study [https://r20.rs6.net/on.jsp?ca=2287584c-5e8f-416e-bff6-a424e984d9a6&a=112202…] Thursday, 28 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=0012GTCD6jtsvoIwcfd…> Table of Contents ICANN74 · TOMORROW:Translation/Print Deadlines · Internet Reimbursement Program · Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Information Sharing · NEW: ICANN Thanks You for a Successful Inaugural Asia Pacific DNS Forum 2022 · NEW: ICANN Completes New Audit Confirming Proper Controls in Place for IANA Function · NEXT WEEK: Request for Input - GNSO Statement of Interest · REMINDER: Call for Expressions of Interest: ICANN 2023 NomCom Chair and Chair-Elect · REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May Public Comment · EXTENDED-CLOSES TOMORROW: Root Zone Update Process Study · Root Zone Label Generation Rules Version 5 (RZ-LGR-5) ICANN74 Resources Translation/Print Deadlines TOMORROW: 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, 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 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>. Internet Reimbursement Program Application Opens: Monday, 02 May 2022 Application Deadline: Friday, 27 May 2022 Program details are available here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…>. The ICANN Pandemic Internet Access Reimbursement Program aims to facilitate the active participation in ICANN Public Meetings Meeting for certain community members with limited Internet capacity by offering financial assistance to increase their Internet bandwidth during the meeting. 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=0012GTCD6jtsvoIwcfd…> 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=0012GTCD6jtsvoIwcfd…> 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=0012GTCD6jtsvoIwcfd…>Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…>. Information Sharing NEW: ICANN Thanks You for a Successful Inaugural Asia Pacific DNS Forum 2022 We've successfully launched the inaugural Asia Pacific (APAC) Domain Name System (DNS) Forum from 30 March to 1 April 2022. As mentioned in my previous blog [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…>, the goals for this Forum were to bring stakeholders from the region together to exchange information, share views, and collaborate to address the upcoming challenges and opportunities for the DNS. I'm happy to report that we've met all of these goals. I would also like to share the way forward for the APAC DNS Forum. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…> NEW: ICANN Completes New Audit Confirming Proper Controls in Place for IANA Function ICANN has completed another year of audits of the key systems used to deliver the Internet Assigned Numbers Authority (IANA) functions. The accounting firm RSM US LLP conducted a Service Organization Control (SOC) 2 audit of the Registry Assignment and Maintenance Systems (RAMS) and a Service Organization Control (SOC) 3 audit of root zone Domain Name System Security Extensions (DNSSEC) services for the 12-month periods ending 30 September 2021 and 30 November 2021. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…> NEXT WEEK: 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=0012GTCD6jtsvoIwcfd…> by Wednesday, 4 May. Your input will be much appreciated! REMINDER: Call for Expressions of Interest: ICANN 2023 NomCom Chair and Chair-Elect ICANN org seeks Expressions of Interest for the chair and chair-elect of the 2023 Nominating Committee (NomCom). Expressions of Interest, which will be maintained as confidential, should be sent to NomComChair2023(a)icann.org<mailto:NomComChair2023@icann.org> by no later than Monday, 9 May 2022. A suggested form for submitting an Expression of Interest is available here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…>. 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=0012GTCD6jtsvoIwcfd…> Public Comment EXTENDED-CLOSES TOMORROW: Root Zone Update Process Study [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…> Open for Submissions Date: Monday, 14 March 2022 Closed for Submissions Date: Friday, 29 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=0012GTCD6jtsvoIwcfd…> 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=0012GTCD6jtsvoIwcfd…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…>. Volume 4, Issue 32 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…> | Next Issue: Monday, 02 May 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=0012GTCD6jtsvoIwcfd…>

1 0

Re: [council] Draft letter to the Board on closed generics dialogue
by philippe.fouquart＠orange.com 27 Apr '22

27 Apr '22

Hi everyone, To wrap-up this up now we have passed the deadline: having seen no concern with having the reference, we will get this v6 sent to the Board hopefully in time for their workshop. Thanks everyone for taking the time to review and chime in in such a short amount of time. Regards, Philippe From: FOUQUART Philippe INNOV/NET Sent: Tuesday, April 26, 2022 5:28 PM To: 'McGrady, Jr., Paul D.' <PMcGrady(a)taftlaw.com>; Stephanie E Perrin <stephanie.perrin(a)mail.utoronto.ca>; council(a)gnso.icann.org Cc: GNSO Secs <gnso-secs(a)icann.org> Subject: RE: [council] Draft letter to the Board on closed generics dialogue Thanks Paul. Hi everyone, To your first point (and Stefanie’s): both Manju’s suggestions have already been included in the draft text circulated earlier today, after Manju’s suggestions. See here<https://mm.icann.org/pipermail/council/2022-April/025616.html>. So from there, let’s deal with the inclusion of the reference: 1. Either it’s good as is ie no reference and the NCSG liaise directly as they see fit (v5 attached) 2. we add that reference in hyperlink - and remove the reference to the intent. (v6, attached) My personal preference would be to go for 2 for the sake of simplicity, mindful that’s this remains NCSG correspondence anyway. Jeff in his capacity as GAC liaison expressed some concerns regarding the characterization of GAC advice, hence the initial removal. So… Question to the list: any councilor opposed to 2, ie keeping that reference in that letter? (v6) * Absent of concern from councilor(s) by tomorrow, the agreed version will be that v6 (with the reference/pointer) * If there are concern from councilor(s), it will be v5. Thanks. Philippe Orange Restricted From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of McGrady, Jr., Paul D. via council Sent: Tuesday, April 26, 2022 4:35 PM To: Stephanie E Perrin <stephanie.perrin(a)mail.utoronto.ca<mailto:stephanie.perrin@mail.utoronto.ca>>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] Draft letter to the Board on closed generics dialogue +1 Stephanie. Phillipe, I see no harm in including the following sentence that Manju suggests: “While the Council is willing to pursue these next steps, it is important to note that Non-Commercial Stakeholders Group expressed its opposition to the approach.” I also believe there is no harm in linking to the NCSG’s letter such that they do not believe they have to deal directly with the Board on this. The content at the link is clearly branded NCSG and I don’t think any Board member will believe that what the NCSG has to say in its letter is coming from the Council given the context of the Council’s letter and the branding of the NCSG’s letter. We can’t be in the business of editing C’s & SG’s communications, but we should be in the business of noting them and passing them along in a way that is distinct from the Council’s own voice. With all respect and personal affection, the only significant objection to this link has come from the Council’s liaison to the GAC. We have sitting Councilors asking for it and, I hope my memory is correct, no sitting Councilors objecting to it (sorry if I got that wrong, but I can say with certainty that there is no overwhelming surge against including the link). Can we please deescalate all of this by including the link as originally requested? It can be hyperlinked to “expressed its opposition” in the proposed sentence above. Then perhaps the NCSG will no longer feel the need for “The NCSG will communicate directly to the Board regarding the rationale of their opposition.” Stephanie & Manju, does that work for you? Best, Paul From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Stephanie E Perrin via council Sent: Tuesday, April 26, 2022 8:38 AM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] Draft letter to the Board on closed generics dialogue [EXTERNAL MESSAGE] Strongly support Manju's clarification. Folks, you do not have to support our view, you just have to support our right to express it clearly. Stephanie Perrin On 2022-04-25 9:19 p.m., 陳曼茹 Manju Chen via council wrote: Hi all, I'm not sure which version we're checking now, but I want to point out that the version I see, where it says 'the NCSG expressed its opposition to the conversation between the Council and the GAC on this subject' is inaccurate. As we have repeatedly stated, it's not the subject of the dialogue we oppose, but the approach initiated by the Board. I strongly opposed the edits as it mischaracterize NCSG's position and reasons for objection. I would suggest we just keep the sentence as it was, better if we add a line of clarification: While the Council is willing to pursue these next steps, it is important to note that Non-Commercial Stakeholders Group expressed its opposition to the approach. The NCSG will communicate directly to the Board regarding the rationale of their opposition. Many thanks, Manju On Tue, Apr 26, 2022 at 7:40 AM Justine Chew via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Philippe, Thank you for taking on board my suggestion -- what you have included in your version 4 at the end of para 3 works for me. Best, Justine On Tue, 26 Apr 2022 at 00:45, <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> wrote: Thanks Paul, you might indeed, you might :) I have the same impression of there being nothing controversial in these changes, but they provide useful context, hence the suggested inclusion. I should have said shorter, in fact, rather than concise. Best, Philippe Orange Restricted From: McGrady, Jr., Paul D. <PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com>> Sent: Monday, April 25, 2022 6:31 PM To: FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>>; Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: RE: [council] Draft letter to the Board on closed generics dialogue Thanks Phillippe. Since Justine didn’t express what the ALAC did not like about my proposed enhancements, and since being concise means “brief but comprehensive”, might I cheekily suggest that my very modest changes resulted in the more concise version since I really do believe that some of the framing in your initial draft didn’t contain all of the necessary information needed for the Board to understand where we are coming from on this. Nothing I included should be controversial. Best, Paul From: philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com> <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Sent: Monday, April 25, 2022 11:24 AM To: Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>; McGrady, Jr., Paul D. <PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: RE: [council] Draft letter to the Board on closed generics dialogue [EXTERNAL MESSAGE] [responding to Justine’s email that followed Paul’s] Dear Councilors, Paul’s suggestions seem to be essentially quoting the letter and framing paper - however, if like Justine below, some councilors would consider that context to be unnecessary or restrictive, let the list know, (and if so, for ease of editing and given the time constraint we’d revert back to the previous - more concise - version) @Justine<mailto:justine.chew.icann@gmail.com> I’ve slightly reworded your other suggestion to make it sound less one-directional, at the risk of stating the obvious. Hope that’ll work. Thank you. Philippe From: Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>> Sent: Monday, April 25, 2022 10:36 AM To: McGrady, Jr., Paul D. <PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com>>; FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: Re: [council] Draft letter to the Board on closed generics dialogue Hello Paul, I think the simpler version 2 of the draft reply with amendments as proposed by Philippe regarding references to (a) NCSG's letter and (b) "modalities" is sufficient for the present purposes. Hello Philippe, My 3rd point was a suggestion to indicate that Council is undertaking some thinking for the dialogue, so, perhaps something along the lines of the following could be considered? While I won't insist on it, I think it's useful to provide some context on the timing of this response. It is on that basis that the Council is willing to pursue next steps for the facilitated dialogue, subject to mutual agreement with the GAC on the conditions which the Council is preparing to propose for that dialogue. Thanks, Justine On Sat, 23 Apr 2022 at 04:11, McGrady, Jr., Paul D. <PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com>> wrote: Thanks Philippe, Kurt, Justine, and Jeff. Dear All: I’m happy with the NCSG’s letter being attached, or not, but I do think it is important to at least call it out since we don’t want to give the misimpression that the Council is completely unified on this topic. I for one have a great deal of sympathy with the idea that GAC advice should not restart policy work in the GNSO, but rather the Board needs to figure out how to implement (via IRT) both the completed policy Recommendations and the GAC advice in the next version of the Applicant Guidebook (like they did with much of the GAC advice that rolled in after the policy work was done for the first round). Hopefully something will come out of this dialogue that helps in that process. As for the letter itself, I think we could just as easily say “Dear Board, of course we are happy to talk with the GAC about their concerns. We will reach out to them and get it set up.” But, we do like our letters here in ICANNland, so my marked up version (based off the last version sent by Philippe) is attached. If we are going to frame the issues, instead of just a quick “we are on it” response, I think a tiny bit of more detail of how we got here makes sense. Hopefully my proposed changes (which are in red on my screen) will be viewed as friendly amendments, which is the spirit in which they are offered. Thank all! Best, Paul Taft / Paul D. McGrady, Jr. Partner PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com> Dir: 312.836.4094 | Cell: 312.882.5020 Tel: 312.527.4000 | Fax: 312.754.2354 111 E. Wacker Drive, Suite 2800 Chicago, Illinois 60601-3713 Download vCard<http://www.taftlaw.com/vcard/PMcGrady@taftlaw.com> taftlaw.com<http://www.taftlaw.com> This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. Orange Restricted From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of philippe.fouquart--- via council Sent: Friday, April 22, 2022 1:57 PM To: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Cc: GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Draft letter to the Board on closed generics dialogue [EXTERNAL MESSAGE] Kurt, Justine, Jeff, thanks for the inputs. On 1) and reference to the NCSG’s letter: The reference is on record with the minutes, and can also be found in the Council list archive, I don’t think there’s any risk this goes unnoticed, I’d suggest we simply say While the Council is willing to pursue these next steps, it is important to note that Non-Commercial Stakeholders Group expressed its opposition to the approach. Manju (since it is you who spoke on this during our call): would you be fine with this? On 2) and modalities, I’d suggest we go for Jeff’s edits and simply say in the second paragraph: The Council is appreciative of the ICANN Board’s attention to GNSO related matters and is willing to pursue next steps for the facilitated dialogue, subject to mutual agreement with the GAC on the conditions for that dialogue. Ironically, in French, the equivalent of ‘modalities’ has a sense of a series of menial tasks that the authors would consider a) quite straightforward and b) as a result, generally not worth doing by themselves. Neither of which would probably be true here I think. It seems 2) alleviates the need to elaborate as, Justine, you suggested with your 3rd point but let us know if it doesn’t work. As attached with diff marks. Regards, Philippe From: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Sent: Friday, April 22, 2022 3:48 PM To: Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: [council] Draft letter to the Board on closed generics dialogue I strongly urge that the letter from the NCSG is not included with this letter. As Justine states, there are some mischaracterizations in that letter and as far as I am aware the rest of the Council does not agree with the opinions expressed by the NCSG. You can indicate that the NCSG opposed the meeting in the letter without any attachments. If you include the NCSG letter, would you consider adding letters from the other SGs and Cs that are in support of the meeting? I believe the best way is to note the NCSG’s disagreement, but not attach anything. And with respect to the word “modalities”, it is an unnecessary word. A “modality” is a condition is it not? So I would just state: “….that the Council is willing to pursue next steps for the facilitated dialogue, subject to mutual agreement with the GAC on the conditions for that dialogue.” [cid:image001.png@01D85A71.41918610] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Justine Chew via council Sent: Thursday, April 21, 2022 8:12 PM To: Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; Philippe Fouquart <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Draft letter to the Board on closed generics dialogue Hello Philippe, Kurt, 1. I agree with Kurt on the NCSG letter, and if it were to be included, I think we should at least address the assertion that "GAC has been silent since 2013 on the matter of Closed Generics" as called out by Jeff as a mis-characterization of the GAC on the part of NCSG. 2. I understand the word "modalities" to mean "ways of doing something", but if there's a better word to address Kurt's concerns then by all means, let's consider that. 3. Would it be feasible to add to the end of the second paragraph, a suggestion that "the conditions and modalities for that dialogue" will be forthcoming? That would indicate that Council is giving thought to those and will continue to do so (hence allowing for the Closed Generics small team leeway to do its work). Thanks for considering. Kind regards, Justine On Fri, 22 Apr 2022 at 06:54, Kurt Pritz via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Hi Philippe: Two comments: 1. If the NCSG has requested that reference to their comment should be included it in the letter, then we should include it. If not, you might ask if they want that (and if they do, include it). I don’t think it adds value at this point - but will add value as we get into the meeting set-up, the discussion scope, and the actions taken with any recommendations that come out of the meeting. 2. I personally recommend that we avoid the use of the term ‘modalities.’ I don’t know what it means and, if participating in a group tasked with identifying them, I wouldn’t know what they are. I right clicked on the word and found that Microsoft knows of no synonyms. I looked it up in a popular online dictionary and came up with: - the quality or state of being modal; a modal quality or attribute; - the classification of logical propositions according to their asserting or denying the possibility, impossibility, contingency, or necessity of their content; - one of the main avenues of sensation (such as vision); - a usually physical therapeutic agency Not getting the sense from there, I looked for its use in a sentence and found: "Ineluctable modality of the visible: at least that if no more, thought through my eyes.” The New Yorker, 7 Feb. 2022 That did not help me understand the definition but did tell me a lot about the kind of people that use the word. I understand the word is commonly used in governmental settings but we needn’t adopt the custom if it is not clarifying or helpful. Slightly more seriously, when we meet among ourselves and with the GAC, we should all understand the target and “modalities” seems too broad. It would be helpful for me (maybe it is just me) to replace the word with commonly spoken terms or to parenthetically define it. Thanks for listening, Kurt On Apr 22, 2022, at 3:32 AM, philippe.fouquart--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, Please find attached for you review a draft response letter to the ICANN Board on closed generics. It intends to capture the conclusions of our discussion during the Council call last week. We would like to have it ready for the Board workshop next week, so please have a look before April 27th 1200 UTC (Wednesday) Thanks. Regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. <Closed Generics_Council to ICANN Board - 20 April 2022.docx>_______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ 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. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Re: [council] Draft letter to the Board on closed generics dialogue
by philippe.fouquart＠orange.com 27 Apr '22

27 Apr '22

[responding to Justine's email that followed Paul's] Dear Councilors, Paul's suggestions seem to be essentially quoting the letter and framing paper - however, if like Justine below, some councilors would consider that context to be unnecessary or restrictive, let the list know, (and if so, for ease of editing and given the time constraint we'd revert back to the previous - more concise - version) @Justine<mailto:justine.chew.icann@gmail.com> I've slightly reworded your other suggestion to make it sound less one-directional, at the risk of stating the obvious. Hope that'll work. Thank you. Philippe From: Justine Chew <justine.chew.icann(a)gmail.com> Sent: Monday, April 25, 2022 10:36 AM To: McGrady, Jr., Paul D. <PMcGrady(a)taftlaw.com>; FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com> Cc: Jeff Neuman <jeff(a)jjnsolutions.com>; Kurt Pritz <kurt(a)kjpritz.com>; GNSO Secs <gnso-secs(a)icann.org> Subject: Re: [council] Draft letter to the Board on closed generics dialogue Hello Paul, I think the simpler version 2 of the draft reply with amendments as proposed by Philippe regarding references to (a) NCSG's letter and (b) "modalities" is sufficient for the present purposes. Hello Philippe, My 3rd point was a suggestion to indicate that Council is undertaking some thinking for the dialogue, so, perhaps something along the lines of the following could be considered? While I won't insist on it, I think it's useful to provide some context on the timing of this response. It is on that basis that the Council is willing to pursue next steps for the facilitated dialogue, subject to mutual agreement with the GAC on the conditions which the Council is preparing to propose for that dialogue. Thanks, Justine On Sat, 23 Apr 2022 at 04:11, McGrady, Jr., Paul D. <PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com>> wrote: Thanks Philippe, Kurt, Justine, and Jeff. Dear All: I'm happy with the NCSG's letter being attached, or not, but I do think it is important to at least call it out since we don't want to give the misimpression that the Council is completely unified on this topic. I for one have a great deal of sympathy with the idea that GAC advice should not restart policy work in the GNSO, but rather the Board needs to figure out how to implement (via IRT) both the completed policy Recommendations and the GAC advice in the next version of the Applicant Guidebook (like they did with much of the GAC advice that rolled in after the policy work was done for the first round). Hopefully something will come out of this dialogue that helps in that process. As for the letter itself, I think we could just as easily say "Dear Board, of course we are happy to talk with the GAC about their concerns. We will reach out to them and get it set up." But, we do like our letters here in ICANNland, so my marked up version (based off the last version sent by Philippe) is attached. If we are going to frame the issues, instead of just a quick "we are on it" response, I think a tiny bit of more detail of how we got here makes sense. Hopefully my proposed changes (which are in red on my screen) will be viewed as friendly amendments, which is the spirit in which they are offered. Thank all! Best, Paul Taft / Paul D. McGrady, Jr. Partner PMcGrady(a)taftlaw.com<mailto:PMcGrady@taftlaw.com> Dir: 312.836.4094 | Cell: 312.882.5020 Tel: 312.527.4000 | Fax: 312.754.2354 111 E. Wacker Drive, Suite 2800 Chicago, Illinois 60601-3713 Download vCard<http://www.taftlaw.com/vcard/PMcGrady@taftlaw.com> taftlaw.com<http://www.taftlaw.com> This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments. Orange Restricted From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of philippe.fouquart--- via council Sent: Friday, April 22, 2022 1:57 PM To: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>> Cc: GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Draft letter to the Board on closed generics dialogue [EXTERNAL MESSAGE] Kurt, Justine, Jeff, thanks for the inputs. On 1) and reference to the NCSG's letter: The reference is on record with the minutes, and can also be found in the Council list archive, I don't think there's any risk this goes unnoticed, I'd suggest we simply say While the Council is willing to pursue these next steps, it is important to note that Non-Commercial Stakeholders Group expressed its opposition to the approach. Manju (since it is you who spoke on this during our call): would you be fine with this? On 2) and modalities, I'd suggest we go for Jeff's edits and simply say in the second paragraph: The Council is appreciative of the ICANN Board's attention to GNSO related matters and is willing to pursue next steps for the facilitated dialogue, subject to mutual agreement with the GAC on the conditions for that dialogue. Ironically, in French, the equivalent of 'modalities' has a sense of a series of menial tasks that the authors would consider a) quite straightforward and b) as a result, generally not worth doing by themselves. Neither of which would probably be true here I think. It seems 2) alleviates the need to elaborate as, Justine, you suggested with your 3rd point but let us know if it doesn't work. As attached with diff marks. Regards, Philippe From: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Sent: Friday, April 22, 2022 3:48 PM To: Justine Chew <justine.chew.icann(a)gmail.com<mailto:justine.chew.icann@gmail.com>>; Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; FOUQUART Philippe INNOV/NET <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: [council] Draft letter to the Board on closed generics dialogue I strongly urge that the letter from the NCSG is not included with this letter. As Justine states, there are some mischaracterizations in that letter and as far as I am aware the rest of the Council does not agree with the opinions expressed by the NCSG. You can indicate that the NCSG opposed the meeting in the letter without any attachments. If you include the NCSG letter, would you consider adding letters from the other SGs and Cs that are in support of the meeting? I believe the best way is to note the NCSG's disagreement, but not attach anything. And with respect to the word "modalities", it is an unnecessary word. A "modality" is a condition is it not? So I would just state: "....that the Council is willing to pursue next steps for the facilitated dialogue, subject to mutual agreement with the GAC on the conditions for that dialogue." [cid:image001.png@01D858C4.05EAAE10] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Justine Chew via council Sent: Thursday, April 21, 2022 8:12 PM To: Kurt Pritz <kurt(a)kjpritz.com<mailto:kurt@kjpritz.com>>; Philippe Fouquart <philippe.fouquart(a)orange.com<mailto:philippe.fouquart@orange.com>> Cc: GNSO Secs <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>; council@gnso icann. org <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Draft letter to the Board on closed generics dialogue Hello Philippe, Kurt, 1. I agree with Kurt on the NCSG letter, and if it were to be included, I think we should at least address the assertion that "GAC has been silent since 2013 on the matter of Closed Generics" as called out by Jeff as a mis-characterization of the GAC on the part of NCSG. 2. I understand the word "modalities" to mean "ways of doing something", but if there's a better word to address Kurt's concerns then by all means, let's consider that. 3. Would it be feasible to add to the end of the second paragraph, a suggestion that "the conditions and modalities for that dialogue" will be forthcoming? That would indicate that Council is giving thought to those and will continue to do so (hence allowing for the Closed Generics small team leeway to do its work). Thanks for considering. Kind regards, Justine On Fri, 22 Apr 2022 at 06:54, Kurt Pritz via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Hi Philippe: Two comments: 1. If the NCSG has requested that reference to their comment should be included it in the letter, then we should include it. If not, you might ask if they want that (and if they do, include it). I don't think it adds value at this point - but will add value as we get into the meeting set-up, the discussion scope, and the actions taken with any recommendations that come out of the meeting. 2. I personally recommend that we avoid the use of the term 'modalities.' I don't know what it means and, if participating in a group tasked with identifying them, I wouldn't know what they are. I right clicked on the word and found that Microsoft knows of no synonyms. I looked it up in a popular online dictionary and came up with: - the quality or state of being modal; a modal quality or attribute; - the classification of logical propositions according to their asserting or denying the possibility, impossibility, contingency, or necessity of their content; - one of the main avenues of sensation (such as vision); - a usually physical therapeutic agency Not getting the sense from there, I looked for its use in a sentence and found: "Ineluctable modality of the visible: at least that if no more, thought through my eyes." The New Yorker, 7 Feb. 2022 That did not help me understand the definition but did tell me a lot about the kind of people that use the word. I understand the word is commonly used in governmental settings but we needn't adopt the custom if it is not clarifying or helpful. Slightly more seriously, when we meet among ourselves and with the GAC, we should all understand the target and "modalities" seems too broad. It would be helpful for me (maybe it is just me) to replace the word with commonly spoken terms or to parenthetically define it. Thanks for listening, Kurt On Apr 22, 2022, at 3:32 AM, philippe.fouquart--- via council <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> wrote: Dear Councilors, Please find attached for you review a draft response letter to the ICANN Board on closed generics. It intends to capture the conclusions of our discussion during the Council call last week. We would like to have it ready for the Board workshop next week, so please have a look before April 27th 1200 UTC (Wednesday) Thanks. Regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. <Closed Generics_Council to ICANN Board - 20 April 2022.docx>_______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ council mailing list council(a)gnso.icann.org<mailto:council@gnso.icann.org> https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

5 9

Draft letter to the Board on closed generics dialogue
by philippe.fouquart＠orange.com 27 Apr '22

27 Apr '22

Dear Councilors, Please find attached for you review a draft response letter to the ICANN Board on closed generics. It intends to capture the conclusions of our discussion during the Council call last week. We would like to have it ready for the Board workshop next week, so please have a look before April 27th 1200 UTC (Wednesday) Thanks. Regards, Philippe _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

6 7

With ics attachment | Meeting Invitation | Modifying gTLD Consensus Policies with ICANN Org, GNSO Council and SG/C Chairs | Wednesday, 04 May 2022 at 13:00 UTC
by Terri Agnew 26 Apr '22

26 Apr '22

With ics attachment Dear all, The Modifying gTLD Consensus Policies with ICANN Org, GNSO Council and SG/C Chairs is scheduled on Wednesday, 04 May 2022 at 13:00 UTC for 90 minutes. 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…> Check your time zone: https://tinyurl.com/s9bznnp6 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/s9bznnp6__;!!PtGJab4!oT9P08z…> Please notify the GNSO Secretariat in advance if a dial out call is needed, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92367136025?pwd=U0c1dERHZ1FZT2g2Vzgzem9oRnZzdz09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/92367136025?pwd=U0c1dERH…> Passcode: j41+?PYCmD One tap mobile : US: +13126266799,,92367136025#,,,,*2738479768# or +19294362866,,92367136025#,,,,*2738479768# Webinar ID: 923 6713 6025 Passcode: 2738479768 International numbers available: https://icann.zoom.us/u/adOEQ06SWh [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/adOEQ06SWh__;!!PtGJab4!o…> Observers are welcome to join, they will be in a read-only and listen-only mode. Thank you. Kind Regards, Terri

1 0