November 2022 - council - lists.icann.org

Meeting Invite: ODA GNSO Council Specific Webinar | Wednesday, 07 December 2022
by Devan Reed 18 Nov '22

18 Nov '22

Dear all, Please see the details below for the ODA GNSO Council Specific Webinar taking place on Wednesday, 07 December 2022 at 20:00 UTC for 90 minutes. Wiki Page: https://community.icann.org/x/NoQ-DQ For other time zones: https://tinyurl.com/a34faa2v GNSO Council members will be panelists. Observers are welcome and will be in a read-only and listen-only mode. Please click the link below to join the webinar: https://icann.zoom.us/j/99137131881?pwd=dVp4Yzl4VVhBSmR4V2NwbEI0UTJoZz09 Passcode: 34$6yx$x#6 Audio only: Webinar ID: 991 3713 1881 Passcode: 5745543305 International numbers available: https://icann.zoom.us/u/aenqPMbYMu Thank you. Kind regards, Devan Devan Reed Policy Development Support - TEMP Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&…> [cidimage001.png(a)01D4E0C6.320C4B80]

1 0

ODA GNSO Council Specific Webinar
by ICANN Policy Calendar 18 Nov '22

18 Nov '22

Meeting: ODA GNSO Council Specific Webinar Date/Time: 07 December 2022 at 20:00 UTC for 90 minutes Wiki Page: https://community.icann.org/x/NoQ-DQ For other time zones: https://tinyurl.com/a34faa2v GNSO Council members will be panelists. Observers are welcome and will be in a read-only and listen-only mode. Please click the link below to join the webinar: https://icann.zoom.us/j/99137131881?pwd=dVp4Yzl4VVhBSmR4V2NwbEI0UTJoZz09 Passcode: 34$6yx$x#6 Audio only: Webinar ID: 991 3713 1881 Passcode: 5745543305 International numbers available: https://icann.zoom.us/u/aenqPMbYMu

1 0

Meeting invitation | ICANN Grant Program Implementation Update Webinar | Thursday, 01 December 2022
by Devan Reed 17 Nov '22

17 Nov '22

Dear all, Please find below the call details for the ICANN Grant Program Implementation Update Webinar on Thursday, 01 December 2022 at 15:00 UTC for 60 minutes. This invitation serves as a calendar placeholder for the councilors who are interested in attending. GNSO Councilor attendance is NOT required. Wiki space: https://community.icann.org/x/l4QFDQ Zoom Link for the call: https://icann.zoom.us/j/91672296247?pwd=UUIraWZ3TDBiYzFxYzRuaVpwdWdrZz09 Meeting ID: 916 7229 6247 | Passcode: Ku?Rf0bfME One tap mobile +16699006833,,91672296247#,,,,*2817137489# US (San Jose) +13462487799,,91672296247#,,,,*2817137489# US (Houston) To Dial by Phone: Find your local number: https://icann.zoom.us/u/aCz5e02at Meeting ID: 916 7229 6247 | Passcode: 2817137489 If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Thank you. Kind regards, Devan

1 0

ICANN Grant Program Implementation Update Webinar
by ICANN Policy Calendar 17 Nov '22

17 Nov '22

Meeting: ICANN Grant Program Implementation Update Webinar Date/Time: Thursday, 01 December 2022 at 15:00 UTC for 60 minutes This invitation serves as a calendar placeholder for the councilors who are interested in attending. GNSO Councilor attendance is NOT required. Wiki space: https://community.icann.org/x/l4QFDQ Zoom Link for the call: https://icann.zoom.us/j/91672296247?pwd=UUIraWZ3TDBiYzFxYzRuaVpwdWdrZz09 Meeting ID: 916 7229 6247 | Passcode: Ku?Rf0bfME One tap mobile +16699006833,,91672296247#,,,,*2817137489# US (San Jose) +13462487799,,91672296247#,,,,*2817137489# US (Houston) To Dial by Phone: Find your local number: https://icann.zoom.us/u/aCz5e02at Meeting ID: 916 7229 6247 | Passcode: 2817137489 If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>

1 0

FYI: [Ext] Register for the ICANN Grant Program Implementation Update Webinar!
by Devan Reed 17 Nov '22

17 Nov '22

FYI [https://r20.rs6.net/on.jsp?ca=8b5510d8-b412-42f2-b7fc-e91b52c214b4&a=112202…] Thursday, 17 November 2022 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> Table of Contents Information Sharing · NEW: Register for the ICANN Grant Program Implementation Update Webinar · NEW: ICANN Publishes IDN Implementation Guidelines Version 4.1 · NEW Press Release: ICANN Investment in Africa Enables Safer, Faster Internet Access Across the Continent · NEW: ICANN77 Fellowship Application Round Now Open · REMINDER: ICANN Calls for Volunteers to Plan for Changing the Root Zone DNSSEC Algorithm · REMINDER: ICANN Launches Fiscal Year 2024 Additional Budget Request Process · REMINDER: Call for Expressions of Interest for Independent Adviser to the ICANN Board Audit Committee · REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members Public Comment · CLOSES TODAY: Draft IANA and PTI FY24 Operating Plan and Budgets · CLOSES FRIDAY: Proposed Amendments to the SLA for the IANA Numbering Services · LAST CALL:Registration Data Consensus Policy for gTLDs · Initial Report on the Second CSC Effectiveness Review Information Sharing NEW: Register for the ICANN Grant Program Implementation Update Webinar The Grant Program will distribute the proceeds from auctions of last resort in the 2012 New Generic Top-Level Domain Program. Once launched, the program will be open to applications from any eligible organization across the world for projects that are supportive of ICANN's mission. The webinar will take place on 1 December 2022 at 15:00 UTC. Please click on this link [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> to attend the webinar. This webinar will be recorded and made available on the community workspace [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> NEW: ICANN Publishes IDN Implementation Guidelines Version 4.1 Today, lCANN published Internationalized Domain Name (IDN) Implementation Guidelines version 4.1 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> after approval [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> by the ICANN Board. Following the guidelines publication, ICANN organization (org) will begin work on their implementation and will communicate the effective date to relevant parties when available. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> NEW: Press Release: ICANN Investment in Africa Enables Safer, Faster Internet Access Across the Continent Internet users in Africa will soon have faster access to services on the Internet and better protection from cyberattacks. The Internet Corporation for Assigned Names and Numbers (ICANN), in cooperation with its regional partners, is deploying a new ICANN Managed Root Server (IMRS) cluster in Nairobi, Kenya. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> NEW: ICANN77 Fellowship Application Round Now Open ICANN is opening the application round for the ICANN Fellowship Program for the ICANN77 Policy Forum. This round is open only to those who have previously completed an ICANN fellowship. The ICANN77 Policy Forum is scheduled for 12–15 June 2023 in Washington, D.C. If ICANN77 is held virtually, the Fellowship Program will also be held virtually. The deadline to apply is 15 December 2022, 23:59 UTC. Successful candidates will be announced on 17 February 2023 on the ICANN website [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> REMINDER: ICANN Calls for Volunteers to Plan for Changing the Root Zone DNSSEC Algorithm ICANN is calling for volunteers to join a design team that will develop a plan for changing the cryptographic algorithm used for the Domain Name System (DNS) root key signing key and zone signing key. Interested in joining this group? Please complete this form [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> and send it to ksk-rollover-soi(a)iana.org<mailto:ksk-rollover-soi@iana.org> before 25 November 2022. IANA expects to announce members of the design team in early January 2023. The team will start work shortly thereafter. More information about the project can be found here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> REMINDER: ICANN Launches Fiscal Year 2024 Additional Budget Request Process The ABR Process reflects potential ICANN community activities that are not already included in the annual ICANN operating plan and budget. The ABR process helps the ICANN Board and ICANN organization (org) better understand and develop resources for present and future ICANN community needs. More information about the FY24 ABR Process can be found on this workspace [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>. ICANN org will host an informational webinar on Thursday, 08 December 2022, at 16:00 UTC. Please register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> REMINDER: Call for Expressions of Interest for Independent Adviser to the ICANN Board Audit Committee The Internet Corporation for Assigned Names and Numbers (ICANN) is seeking expressions of interest to serve as an external Independent Adviser to the ICANN Board Audit Committee. The ICANN Board Audit Committee is seeking to fill this opening as soon as possible. Read this job description [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> for more information on the role and how to apply. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members Supporting Organizations (SOs) and Advisory Committees (ACs) are invited to nominate volunteers to serve as mentors in its Fellowship Program and to serve on the Fellowship Program Selection Committee. There will be a total of seven mentors and seven Selection Committee members, and each group is welcome to nominate one individual for each role. Interested SOs/ACs should select their respective Fellowship Program mentor and Selection Committee representative by 31 January 2023 and notify fellowshipconsultation(a)icann.org<mailto:fellowshipconsultation@icann.org>. Individual self-nominations will not be considered. Public Comment CLOSES TODAY: Draft IANA and PTI FY24 Operating Plan and Budgets [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> Open for submissions date: 15 September 2022 Closed for submissions date: 17 November 2022 CLOSES FRIDAY: Proposed Amendments to the SLA for the IANA Numbering Services [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> Open for submissions date: 13 September 2022 Closed for submissions date: 18 November 2022 LAST CALL: Registration Data Consensus Policy for gTLDs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> Open for submissions date: 24 August 2022 Closed for submissions date: 21 November 2022 Initial Report on the Second CSC Effectiveness Review [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> Open for submissions date: 14 September 2022 Closed for submissions date: 01 December 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>. Volume 4, Issue 84 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…> | Next Issue: Monday, 21 November 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001wMr2IGM-wECSKAGJ…>

1 0

Re: [council] ICANN Grant Program Implementation Update Webinar - 1 December 2022 at 15:00 UTC
by Marika Konings 17 Nov '22

17 Nov '22

Anne, please note that this provision is from the PDP manual which is specific to the GNSO policy development process. The Grant Program is the result of recommendations that were developed by a Cross-Community Working Group, not a PDP. The new gTLD Auction Proceeds CCWG Final Report did note that “The ICANN Board is expected to share the outcome of its consideration with the CCWG Chartering Organizations and, if deemed necessary, involve the Chartering Organizations and/or CCWG implementation team in any deliberations that would benefit from Chartering Organization and/or CCWG implementation team input”. I hope this is helpful. Best regards, Marika From: council <council-bounces(a)gnso.icann.org> on behalf of "Aikman-Scalese, Anne via council" <council(a)gnso.icann.org> Reply to: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com> Date: Thursday, 17 November 2022 at 16:10 To: Emily Barabas <emily.barabas(a)icann.org>, "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy>, Devan Reed <devan.reed(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: Giovanni Seppia <giovanni.seppia(a)icann.org> Subject: Re: [council] ICANN Grant Program Implementation Update Webinar - 1 December 2022 at 15:00 UTC Many thanks, Emily. It would be great if Council members could get a calendar invitation for this December 1 webinar. (Didn’t see a calendar invitation at the linked page.) This might also be a good “guinea pig” topic for the SPS Discussion on the Role of GNSO Council in Implementation of policy as the ICANN Grant Program moves forward. Annex 2 to the Operating Procedures describes that role in Section 14. 14. GNSO Council Role in Implementation Upon a final decision of the Board adopting the GNSO PDP policy, the Board may, as appropriate, give authorization or direction to ICANN staff to work with the GNSO Council to create an implementation plan based upon the implementation recommendations identified in the Final Report, and to implement the policy in as timely a fashion as possible. The GNSO Council must direct the creation of an Implementation Review Team (IRT) to assist staff in developing the implementation details for the policy, unless in exceptional circumstances the GNSO Council determines that an IRT is not required (e.g. if another IRT is already in place that could appropriately deal with the PDP recommendations. However, in such case the membership of the IRT will need to be reviewed to ensure that adequate expertise and representation is present to take on the implementation of the additional PDP recommendations). In its Final Report, the PDP Team should provide recommendations to the GNSO Council on whether an Implementation Review Team should be established and any other recommendations deemed appropriate in relation to such an Implementation Review Team (e.g. composition). ICANN staff should inform the GNSO of its proposed implementation of a new GNSO recommended policy. If the proposed implementation is considered inconsistent with the GNSO recommendations, the GNSO Council may notify the Board and request that the Board review the proposed implementation. Until the Board has considered the GNSO Council request, ICANN staff should refrain from implementing the policy, although it may continue developing the details of the proposed implementation while the Board considers the GNSO Council request. Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8FAA3.18EA2140] From: Emily Barabas <emily.barabas(a)icann.org> Sent: Thursday, November 17, 2022 4:15 AM To: Aikman-Scalese, Anne <AAikman(a)lewisroca.com>; Sebastien(a)registry.godaddy; Devan Reed <devan.reed(a)icann.org>; council(a)gnso.icann.org Cc: Giovanni Seppia <giovanni.seppia(a)icann.org> Subject: ICANN Grant Program Implementation Update Webinar - 1 December 2022 at 15:00 UTC [EXTERNAL] ________________________________ Dear all, The webinar mentioned in my email below will take place on 1 December 2022 at 15:00 UTC. Please see this ICANN Announcement for further details: https://www.icann.org/en/announcements/details/register-for-the-icann-grant…. Kind regards, Emily From: Emily Barabas <emily.barabas(a)icann.org<mailto:emily.barabas@icann.org>> Date: Thursday, 10 November 2022 at 11:14 To: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>>, "Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>" <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>>, Devan Reed <devan.reed(a)icann.org<mailto:devan.reed@icann.org>>, "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Giovanni Seppia <giovanni.seppia(a)icann.org<mailto:giovanni.seppia@icann.org>> Subject: Re: [council] Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC Hi Anne, Thanks for your question regarding the October announcement that ICANN org provided an update to the ICANN Board regarding its development of the Preliminary Design and Implementation Plan for the ICANN Grant Program. It is my understanding that the org team leading this work will soon be announcing a community webinar in which they will present to the community the latest thinking on the preliminary design and implementation plan. The details of the webinar will be circulated widely, including the chartering organizations for the CCWG. The staff support team will continue to share any additional updates with Council as they become available. Kind regards, Emily From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> on behalf of "Aikman-Scalese, Anne via council" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Reply to: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>> Date: Tuesday, 8 November 2022 at 18:30 To: "Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>" <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>>, Devan Reed <devan.reed(a)icann.org<mailto:devan.reed@icann.org>>, "council(a)gnso.icann.org<mailto:council@gnso.icann.org>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: Re: [council] Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC Many thanks, Sebastien. Jeff has covered the ICANN announcement on what ICANN Org is calling “Sub Pro Work Track 6” in a separate email which I have forwarded to the list. As to the “ICANN Grant Program”, I was a participant in the CCWG Auction Proceeds work and ended up being the CSG appointed voting rep on the Final Report when Marilyn Cade stepped down. My specific question re the ICANN Announcement on its new “ICANN Grant Program” was whether the report delivered by Org to the Board in mid-October is available to the community and to the GNSO specifically. One reason for this is that there were different methods of establishing the grant program that were summarized in the Final Report from our CCWG Auction Proceeds. It would be good to know which method was recommended to the Board by ICANN Org taking into account the results of the policy work that was reflected in the Final Report. It would also be good to know whether there is or is not a recommendation for ODP since Xavier had mentioned this was a possibility in one webinar on Auction Proceeds. So I guess you would say this is of interest to the GNSO Council given that it relates to implementation work. And I think there is a transparency interest in making the ICANN Org report to the Board available to the Community. Marika is quite familiar with all the deliberations and may herself have access to this “ICANN Grant Program” report to the Board but my question is whether the Community and Council have access to the report to the Board. That seems to me to be an appropriate topic for Council but since I am new, I wanted to run the topic by Leadership – just saw your answer. Perhaps Marika can shed light on this topic? Thank you! Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image004.png@01D8FAA3.18EA2140] From: Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy> <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>> Sent: Monday, November 7, 2022 1:38 PM To: Aikman-Scalese, Anne <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>>; Devan Reed <devan.reed(a)icann.org<mailto:devan.reed@icann.org>>; council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: Re: Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC [EXTERNAL] ________________________________ Hi Anne, Thank you for your question regarding Sub Pro Work Track 6 Outreach and the Auction Grant Program Report and whether these belong on the Council’s agenda for discussion. In general, items that are included in the agenda, are those that fit within the Council’s role as a manager of the policy development process, and/or items for which the Council is expected to take a decision or action either at that meeting or in the near future. Although the two items you listed are the result of previous actions of the GNSO Council (SubPro PDP and new gTLD Auction Proceeds CCWG), it does not seem that there is any immediate action expected on these topics from a Council perspective. Of course, if you, or other Council members have identified aspects of these issues that you do believe warrant Council attention, it would be good to identify these and share these with the Council so it can be decided whether these should be included in the agenda for an upcoming meeting. I would also like to encourage you and others to make use of the Council mailing list to share information or point to communications that you think the Council should be aware of – not everything may require time on the Council agenda, but it may nevertheless be of interest to share. This may also be a good opportunity to remind Council members of the anticipated topics for upcoming Council meetings google doc (see https://docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0o… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…>) that can be used to suggest topics that you think warrant time on a future Council meeting agenda. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3829097333] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Aikman-Scalese, Anne <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>> Date: Thursday, 3 November 2022 at 8:50 pm To: Devan Reed <devan.reed(a)icann.org<mailto:devan.reed@icann.org>>, council(a)gnso.icann.org<mailto:council@gnso.icann.org> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, Sebastien Ducos <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: RE: Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. HI Sebastien et al, I don’t have experience with what belongs on Council’s agenda for discussion so I want to ask about these two items first before making any suggestions: 1. Sub Pro Work Track 6 Outreach: https://www.icann.org/en/blogs/details/subpro-work-track-6-capacity-develop… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> 1. Auction Proceeds Grant Program Report Delivered to the ICANN Board – is it available to us? https://www.icann.org/ru/blogs/details/icann-org-delivers-icann-grant-progr… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…>. Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image004.png@01D8FAA3.18EA2140] From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Devan Reed via council Sent: Tuesday, November 1, 2022 10:07 AM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC [EXTERNAL] ________________________________ Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 07 November 2022 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 17 November 2022 at 05:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/oQjVD [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> Thank you. Devan ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

2 1

ICANN Grant Program Implementation Update Webinar - 1 December 2022 at 15:00 UTC
by Emily Barabas 17 Nov '22

17 Nov '22

Dear all, The webinar mentioned in my email below will take place on 1 December 2022 at 15:00 UTC. Please see this ICANN Announcement for further details: https://www.icann.org/en/announcements/details/register-for-the-icann-grant…. Kind regards, Emily From: Emily Barabas <emily.barabas(a)icann.org> Date: Thursday, 10 November 2022 at 11:14 To: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com>, "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy>, Devan Reed <devan.reed(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: Giovanni Seppia <giovanni.seppia(a)icann.org> Subject: Re: [council] Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC Hi Anne, Thanks for your question regarding the October announcement that ICANN org provided an update to the ICANN Board regarding its development of the Preliminary Design and Implementation Plan for the ICANN Grant Program. It is my understanding that the org team leading this work will soon be announcing a community webinar in which they will present to the community the latest thinking on the preliminary design and implementation plan. The details of the webinar will be circulated widely, including the chartering organizations for the CCWG. The staff support team will continue to share any additional updates with Council as they become available. Kind regards, Emily From: council <council-bounces(a)gnso.icann.org> on behalf of "Aikman-Scalese, Anne via council" <council(a)gnso.icann.org> Reply to: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com> Date: Tuesday, 8 November 2022 at 18:30 To: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy>, Devan Reed <devan.reed(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: Re: [council] Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC Many thanks, Sebastien. Jeff has covered the ICANN announcement on what ICANN Org is calling “Sub Pro Work Track 6” in a separate email which I have forwarded to the list. As to the “ICANN Grant Program”, I was a participant in the CCWG Auction Proceeds work and ended up being the CSG appointed voting rep on the Final Report when Marilyn Cade stepped down. My specific question re the ICANN Announcement on its new “ICANN Grant Program” was whether the report delivered by Org to the Board in mid-October is available to the community and to the GNSO specifically. One reason for this is that there were different methods of establishing the grant program that were summarized in the Final Report from our CCWG Auction Proceeds. It would be good to know which method was recommended to the Board by ICANN Org taking into account the results of the policy work that was reflected in the Final Report. It would also be good to know whether there is or is not a recommendation for ODP since Xavier had mentioned this was a possibility in one webinar on Auction Proceeds. So I guess you would say this is of interest to the GNSO Council given that it relates to implementation work. And I think there is a transparency interest in making the ICANN Org report to the Board available to the Community. Marika is quite familiar with all the deliberations and may herself have access to this “ICANN Grant Program” report to the Board but my question is whether the Community and Council have access to the report to the Board. That seems to me to be an appropriate topic for Council but since I am new, I wanted to run the topic by Leadership – just saw your answer. Perhaps Marika can shed light on this topic? Thank you! Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8FA7E.23AEC830] From: Sebastien(a)registry.godaddy <Sebastien(a)registry.godaddy> Sent: Monday, November 7, 2022 1:38 PM To: Aikman-Scalese, Anne <AAikman(a)lewisroca.com>; Devan Reed <devan.reed(a)icann.org>; council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: Re: Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC [EXTERNAL] ________________________________ Hi Anne, Thank you for your question regarding Sub Pro Work Track 6 Outreach and the Auction Grant Program Report and whether these belong on the Council’s agenda for discussion. In general, items that are included in the agenda, are those that fit within the Council’s role as a manager of the policy development process, and/or items for which the Council is expected to take a decision or action either at that meeting or in the near future. Although the two items you listed are the result of previous actions of the GNSO Council (SubPro PDP and new gTLD Auction Proceeds CCWG), it does not seem that there is any immediate action expected on these topics from a Council perspective. Of course, if you, or other Council members have identified aspects of these issues that you do believe warrant Council attention, it would be good to identify these and share these with the Council so it can be decided whether these should be included in the agenda for an upcoming meeting. I would also like to encourage you and others to make use of the Council mailing list to share information or point to communications that you think the Council should be aware of – not everything may require time on the Council agenda, but it may nevertheless be of interest to share. This may also be a good opportunity to remind Council members of the anticipated topics for upcoming Council meetings google doc (see https://docs.google.com/document/d/1FSNlAHTjbWAzKcfltI7SWwzXda1NtKxfQ2k-t0o… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…>) that can be used to suggest topics that you think warrant time on a future Council meeting agenda. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3829097333] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Aikman-Scalese, Anne <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>> Date: Thursday, 3 November 2022 at 8:50 pm To: Devan Reed <devan.reed(a)icann.org<mailto:devan.reed@icann.org>>, council(a)gnso.icann.org<mailto:council@gnso.icann.org> <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, Sebastien Ducos <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: RE: Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. HI Sebastien et al, I don’t have experience with what belongs on Council’s agenda for discussion so I want to ask about these two items first before making any suggestions: 1. Sub Pro Work Track 6 Outreach: https://www.icann.org/en/blogs/details/subpro-work-track-6-capacity-develop… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> 1. Auction Proceeds Grant Program Report Delivered to the ICANN Board – is it available to us? https://www.icann.org/ru/blogs/details/icann-org-delivers-icann-grant-progr… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…>. Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8FA7E.23AEC830] From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Devan Reed via council Sent: Tuesday, November 1, 2022 10:07 AM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Subject: [council] Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC [EXTERNAL] ________________________________ Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 07 November 2022 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 17 November 2022 at 05:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/oQjVD [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> Thank you. Devan ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521. ________________________________ This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.

2 1

Re: [council] [Ext] RE: GNSO Council resolutions 17 November 2022
by Nathalie Peregrine 17 Nov '22

17 Nov '22

Dear Susan, Thank you for the question! For all statements associated with a motion vote, the statement text url gets posted on the motion vote recorder (document hyperlinked to “Vote Results” in the recommendations below). It is published on the page of the vote (here page 3) on the row corresponding to the councilor who read out the statement (in this case, you). The statements also get mentioned in the Council meeting minutes which will be circulated next week on the Council mailing list after they have been approved by Council leadership. I hope this helps! Kind regards, Nathalie From: Susan Payne <susan.payne(a)comlaude.com> Date: Thursday, 17 November 2022 at 11:56 To: Nathalie Peregrine <nathalie.peregrine(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Ext] RE: GNSO Council resolutions 17 November 2022 Thanks Nathalie, on the WDS, how does the IPC statement get recorded? I thought it would be associated with the vote, but I’m not so familiar with the procedure yet. Thanks Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01D8FA7F.A92C6840][comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!7ld49dkLcttMLL…> From: council <council-bounces(a)gnso.icann.org> On Behalf Of Nathalie Peregrine via council Sent: 17 November 2022 07:31 To: council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: [council] GNSO Council resolutions 17 November 2022 Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 17 November 2022 which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. 20221117-1 CONSENT AGENDA Motion to Approve the GNSO Council Liaison to the Rights Protection Mechanisms Phase 1 Implementation Review Team Submitted by: Greg DiBiase Seconded by: Sebastien Ducos Whereas, 1. The Internet Corporation for Assigned Names and Numbers (ICANN) organization is seeking volunteers to participate in an Implementation Review Team (IRT) to assist in the implementation of the policy recommendations from the Phase 1 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>work of the Policy Development Process (PDP) Working Group on the Review of All Rights Protection Mechanisms (RPMs) in All Generic Top-Level Domains (gTLDs). 2. The Consensus Policy Implementation Framework<https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf> (CPIF) envisions that ICANN org Global Domains and Strategy (GDS) will seek a liaison to the IRT from the GNSO Council. 3. At its meeting<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> on 20 October 2022 the GNSO Council called for volunteers for the liaison to the RPMs IRT and John McElwaine volunteered. Resolved, 1. The GNSO Council acknowledges John McElwaine as the GNSO Council Liaison to the RPMs IRT. 2. The GNSO Council directs staff on behalf of Council leadership to communicate the results of this motion to the GDS staff. Vote results [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> 20221117-2 CONSENT AGENDA Approval of a Project Change Request from the Internationalized Domain Names Expedited Policy Development Process Submitted by: Farell Folly Second by: Tomslin Samme Nlar Whereas, 1. On 20 May 2021, the GNSO Council voted to initiate the Internationalized Domain Names Expedited Policy Development Process (IDNs-EPDP); 2. The EPDP Team began meeting in August 2021 and has been making substantial progress on its deliberation of charter questions; 3. The EPDP Team has determined that it will facilitate the implementation planning of the New gTLD Subsequent Procedures by bifurcating its work into two phases, with Phase 1 covering topics related to top-level IDN gTLD definition and variant management, and Phase 2 covering issues pertaining to second-level IDN variant management; 4. The EPDP Team has also determined that a timeline extension is required to complete its work due to the diversity and complexity of IDN issues, additional data collection needs, review of ICANN org input for draft recommendations, and public comment-related processes; 5. The EPDP leadership team has submitted a Project Change Request outlining the complete rationale for the substantive changes to the project plan and timeline. RESOLVED, 1. The GNSO Council approves this Project Change Request. 2. The GNSO Council instructs policy support staff to update the IDNs-EPDP Team’s project plan, timeline, and other materials accordingly, and post them on the EPDP wiki project space. Vote results [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> 20221117-3 GNSO Council adoption of EPDP Phase 2 Small Team Addendum to Preliminary Report Submitted by: Sebastien Ducos Seconded by: Thomas Rickert WHEREAS, 1. Following the delivery by ICANN org of the System for Standardized Access/Disclosure (SSAD) Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> (ODA), the GNSO Council formed<https://community.icann.org/x/EgciCw> the EPDP Phase 2 small team which was tasked<https://community.icann.org/x/PAoiCw> to provide the GNSO Council with its feedback on: * Whether the ODA has correctly interpreted the intent of the SSAD recommendations in the proposed implementation; * Whether the ODA has overlooked any key aspects of the SSAD recommendations that should be factored in by the ICANN Board when it considers the recommendations; * Its view on the concerns identified by the ICANN Board and potential options that could be considered, either in the form of changes to the proposed implementation or the policy recommendations themselves, to address these concerns (note, these are expected to be high level suggestions at this stage); * Any other aspects that help inform the Council’s deliberations and consultation with the ICANN Board. 2. The small team delivered its preliminary report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> to the GNSO Council on 4 April 2022. 3. Following its review of the preliminary report, the GNSO Council requested [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> that the ICANN Board direct ICANN org “to proceed with further developing the SSAD Light Design” while pausing the consideration of the SSAD recommendations. 4. ICANN org published the Whois Disclosure System Design Paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-…> on 13 September 2022 and presented it to the small team during its sessions (#1 [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/meetings/wmhLk2gj2…> and #2 [75.schedule.icann.org]<https://urldefense.com/v3/__https:/75.schedule.icann.org/meetings/qm9iHL6Ym…>) at ICANN75. 5. The small team reviewed the Whois Disclosure Design Paper and provided its feedback and recommendations on how to proceed to the GNSO Council on 7 November 2022 in the form of an addendum to its Preliminary Report. 6. The GNSO Council, as the manager of the GNSO policy development process, reviewed and considered the addendum in light of the potential impacts on the SSAD. 7. Although it is not the role of the GNSO Council to approve or not approve moving forward with operational proof of concepts, the Council is supportive of efforts such as this one that can provide additional data to the ICANN Board in deciding whether or not to approve the SSAD recommendations outlined in the EPDP Phase 2 Final Report. RESOLVED, 1. The GNSO Council accepts the EPDP Phase 2 small team findings and recommendations as outlined in the addendum [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>. 2. The GNSO Council requests that the GNSO Secretariat transmits the addendum to the ICANN Board. 3. The GNSO Council confirms that pending the implementation and subsequent running of the Whois Disclosure System for a period of up to two (2) years, the SSAD recommendations should remain paused for consideration by the ICANN Board. 4. The GNSO Council thanks the EPDP Phase 2 small team for its work and requests it to remain available to continue work on this topic as part of the next steps in this process which aims to inform the further consideration of the SSAD recommendations by the ICANN Board. Vote results [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> 20221117-4 Motion - Registration Data Accuracy Scoping Team write up for assignments #1 and #2 recommendations Submitted by: Greg DiBiase Seconded by: Thomas Rickert WHEREAS, 1. The GNSO Council adopted a proposal [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> on 21 October 2020 which recommended that a Scoping Team addresses the effects of GDPR on Registration Data accuracy requirements and the Whois Accuracy Reporting System (ARS), stating, "a scoping team would be tasked to, 'facilitate community understanding of the issue; assist in scoping and defining the issue; gather support for the request of an Issue Report, and/or; serve as a means to gather additional data and/or information before a request [for an Issue Report] is submitted'. 2. On 4 November 2020, GNSO SG/Cs as well as ICANN SO/ACs were informed of the Council's intent to form a Registration Data Accuracy Scoping Team and were requested to indicate if they would be interested in sending representatives to this effort. 3. At the same time, the GNSO Council also requested that ICANN org develop a briefing document that outlines both (i) existing accuracy requirements and programs and (ii) the corresponding impact that GDPR has had on implementing / enforcing these requirements and programs. This briefing paper<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…>was delivered to the Council in February 2021. 4. Following the Council discussion of the ICANN org briefing paper in April 2021, Council leadership put together a first proposal outlining possible instructions to the Registration Data Accuracy Scoping Team. 5. As a result of input that was provided by different Council members on the first proposal, the Council decided at its May 2021 meeting to form a small team to further review and revise the instructions to the scoping team. 6. The small team, consisting of one Council member from each GNSO Stakeholder Group or Constituency, two NomCom appointed Council members and the GNSO Liaison to the GAC (as an observer), submitted its recommendations in relation to the formation as well as the instructions for the Registration Data Accuracy Scoping Team to the Council on9 July 2021<https://mm.icann.org/pipermail/council/2021-July/024851.html> for Council's consideration. 7. The GNSO Council confirmed the formation of the Registration Data Accuracy Scoping Team and its instructions during its meeting on 22 July 2021. 8. The GNSO Council confirmed the Chair for the Scoping Team during its meeting on 23 September 2021. 9. The Scoping Team started its deliberations on 5 October 2021 focusing its efforts on assignments #1 (enforcement and reporting) and #2 (measurement of accuracy). 10. The Scoping Team delivered its write up [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> for assignments #1 and #2 to the GNSO Council on 5 September 2022. 11. The GNSO Council was briefed on the write up and its recommendations during the Council meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/BYAKGwD2U4PMV6Rs…> at ICANN75 and continued its deliberations during its October Council meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/y26ROY5NZSLyfZj1…>. RESOLVED, 1. The GNSO Council adopts recommendation #3 of the write up which recommends 1) pausing the work in relation to proposals that require access to registration data, 2) encouraging ICANN org to proceed with their outreach to the EDPB as well as the Data Protection Impact Assessment in connection with the scenario(s) in which the request and processing of registration data takes place as a matter of urgency, and 3) requests that ICANN org and Contracted Parties finalize the negotiations on the Data Processing Agreement (DPA) as soon as practicable as the absence of a completed DPA may act as a roadblock for policy work before Council. 2. The GNSO Council defers consideration of recommendations #1 and #2 until such time the DPA negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter. 3. Once the DPA negotiations are completed and the feedback referred to at paragraph 2 is received from ICANN org, the GNSO Council will review the formation and instructions<https://community.icann.org/x/QoFaCg> to the Scoping Team to ensure these are still fit for purpose and request the Scoping Team to further consider potential proposals that require access to registration data as well as how these impact the existing recommendations #1 and #2 (e.g. should these still be considered by the GNSO Council for adoption, or in the context of proposals that require access to registration data these may no longer be relevant or a priority?). If, after 6 months from this resolution, the DPA negotiations are not completed and/or the required feedback referred to at paragraph 2 has not been provided by ICANN org, Council will discuss and determine whether or not to continue deferring the consideration of recommendations #1 and #2. 4. Taking into account the delay with which the write up was delivered, as well as some of the challenges that were shared with the Scoping Team’s Chair during his briefing to the Council, Council leadership will reach out informally to Scoping Team members to better understand the issues encountered to help inform the Council’s review of the formation and instructions. 5. Council leadership is requested to send a communication to ICANN org in relation to recommendation #3 (as well as Contracted Parties in relation to the DPA) as well as communicate the Council’s decision to non-GNSO groups participating in this effort (ALAC, GAC and SSAC) as well as the Scoping Team. 6. The GNSO Council thanks Michael Palage, outgoing Chair, and Olga Cavalli, outgoing Council liaison, for their efforts. As part of its review of the formation and instructions to the Scoping Team, the Council will consider next steps for finding new leadership for this effort. Vote results [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> 20221117-5 Motion - DNS Abuse Small Team Report Submitted by: Mark Datysgeld Seconded by: Sebastien Ducos WHEREAS, 1. The GNSO Council recognizes that the topic of DNS abuse is a longstanding topic and the GNSO has undertaken a variety of activities on this topic in the past, including considering which aspects of the subject of registration abuse are within ICANN's mission to address and in particular, which are appropriate for ICANN to establish policies that are binding on gTLD registry operators and ICANN-accredited registrars[1]<https://community.icann.org/display/gnsocouncilmeetings/Motions+2022-11-17#…>. 2. In February 2022, the GNSO Council tasked a small team consisting of Council members to consider what policy efforts, if any, the GNSO Council should consider undertaking to support the efforts already underway in the different parts of the community to tackle DNS abuse. 3. As part of its deliberations, the small team reached out to all GNSO Stakeholder Groups and Constituencies, as well as the At-Large Advisory Committee (ALAC), the Governmental Advisory Committee (GAC), the Security and Stability Advisory Committee (SSAC) and the DNS Abuse Institute asking for input on what problem(s) policy development specifically is needed to mitigate, if any, as well as the expected outcomes if policy development would be undertaken. 4. In considering the external input received, the small team realized that the suggestions provided can generally be allocated to one or more of the following three buckets: * Issues that may benefit from education / communication / outreach; * Issues that may benefit from contractual negotiations between ICANN org and Contracted Parties; and, * Issues that may benefit from GNSO policy development. 5. The small team delivered its report [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>, containing 4 recommendations, to the GNSO Council on 10 October. 6. The GNSO Council received a briefing on the report and its recommendations during its October Council meeting [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/rec/share/y26ROY5NZSLyfZj1…>. RESOLVED, 1. The GNSO Council accepts the recommendations as outlined in the DNS Abuse Small Team report and requests that the leadership of the small team works with Council leadership on developing the respective communications as foreseen under recommendations #2, #3 and #4. 2. In relation to recommendation #1, the Council commits to considering requesting the development of a Preliminary Issue Report on the topic of malicious registrations after the outreach and communication as foreseen under recommendations #2, #3 and #4 have taken place and the Council has had an opportunity to consider the progress made from efforts related to that outreach. If the Council determines that a Preliminary Issue Report is needed, it must be undertaken in a way that avoids overlap and/or duplication of efforts. 3. The GNSO Council thanks the small team for its efforts, as well as the community groups that contributed to it. [1]<https://community.icann.org/display/gnsocouncilmeetings/Motions+2022-11-17#…> Some past work includes: * Registration Abuse Policies WG Final Report from 2010: https://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf [google.com]<https://urldefense.com/v3/__https:/www.google.com/url?q=https:**Agnso.icann…> (some, but not all recommendations adopted) * Staff best practices discussion paper from 2011: https://gnso.icann.org/sites/default/files/filefield_26745/discussion-paper… [google.com]<https://urldefense.com/v3/__https:/www.google.com/url?q=https:**Agnso.icann…> * Uniformity of Contracts to Address Registration Abuse Final Issue Report 2012: https://gnso.icann.org/en/issues/registration-abuse/uofc-final-issue-report… [google.com]<https://urldefense.com/v3/__https:/www.google.com/url?q=https:**Agnso.icann…>(Final Issue Report, but not sufficient support to initiate a PDP at the time) Vote results [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Thank you. Kind regards, Nathalie ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com__;!!PtGJab4!7ld49dkLcttMLLy…>

2 1

GNSO Council resolutions 17 November 2022
by Nathalie Peregrine 17 Nov '22

17 Nov '22

Dear all, Please find below the resolutions from the GNSO Council meeting on Thursday, 17 November 2022 which will be posted shortly on the GNSO Council resolutions <https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/20…> page. 20221117-1 CONSENT AGENDA Motion to Approve the GNSO Council Liaison to the Rights Protection Mechanisms Phase 1 Implementation Review Team Submitted by: Greg DiBiase Seconded by: Sebastien Ducos Whereas, 1. The Internet Corporation for Assigned Names and Numbers (ICANN) organization is seeking volunteers to participate in an Implementation Review Team (IRT) to assist in the implementation of the policy recommendations from the Phase 1<https://gnso.icann.org/sites/default/files/file/field-file-attach/rpm-phase…>work of the Policy Development Process (PDP) Working Group on the Review of All Rights Protection Mechanisms (RPMs) in All Generic Top-Level Domains (gTLDs). 2. The Consensus Policy Implementation Framework<https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf> (CPIF) envisions that ICANN org Global Domains and Strategy (GDS) will seek a liaison to the IRT from the GNSO Council. 3. At its meeting<https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agen…> on 20 October 2022 the GNSO Council called for volunteers for the liaison to the RPMs IRT and John McElwaine volunteered. Resolved, 1. The GNSO Council acknowledges John McElwaine as the GNSO Council Liaison to the RPMs IRT. 2. The GNSO Council directs staff on behalf of Council leadership to communicate the results of this motion to the GDS staff. Vote results<https://gnso.icann.org/sites/default/files/policy/2022/vote-result/gnso-cou…> 20221117-2 CONSENT AGENDA Approval of a Project Change Request from the Internationalized Domain Names Expedited Policy Development Process Submitted by: Farell Folly Second by: Tomslin Samme Nlar Whereas, 1. On 20 May 2021, the GNSO Council voted to initiate the Internationalized Domain Names Expedited Policy Development Process (IDNs-EPDP); 2. The EPDP Team began meeting in August 2021 and has been making substantial progress on its deliberation of charter questions; 3. The EPDP Team has determined that it will facilitate the implementation planning of the New gTLD Subsequent Procedures by bifurcating its work into two phases, with Phase 1 covering topics related to top-level IDN gTLD definition and variant management, and Phase 2 covering issues pertaining to second-level IDN variant management; 4. The EPDP Team has also determined that a timeline extension is required to complete its work due to the diversity and complexity of IDN issues, additional data collection needs, review of ICANN org input for draft recommendations, and public comment-related processes; 5. The EPDP leadership team has submitted a Project Change Request outlining the complete rationale for the substantive changes to the project plan and timeline. RESOLVED, 1. The GNSO Council approves this Project Change Request. 2. The GNSO Council instructs policy support staff to update the IDNs-EPDP Team’s project plan, timeline, and other materials accordingly, and post them on the EPDP wiki project space. Vote results<https://gnso.icann.org/sites/default/files/policy/2022/vote-result/gnso-cou…> 20221117-3 GNSO Council adoption of EPDP Phase 2 Small Team Addendum to Preliminary Report Submitted by: Sebastien Ducos Seconded by: Thomas Rickert WHEREAS, 1. Following the delivery by ICANN org of the System for Standardized Access/Disclosure (SSAD) Operational Design Assessment<https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf> (ODA), the GNSO Council formed<https://community.icann.org/x/EgciCw> the EPDP Phase 2 small team which was tasked<https://community.icann.org/x/PAoiCw> to provide the GNSO Council with its feedback on: * Whether the ODA has correctly interpreted the intent of the SSAD recommendations in the proposed implementation; * Whether the ODA has overlooked any key aspects of the SSAD recommendations that should be factored in by the ICANN Board when it considers the recommendations; * Its view on the concerns identified by the ICANN Board and potential options that could be considered, either in the form of changes to the proposed implementation or the policy recommendations themselves, to address these concerns (note, these are expected to be high level suggestions at this stage); * Any other aspects that help inform the Council’s deliberations and consultation with the ICANN Board. 2. The small team delivered its preliminary report<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…> to the GNSO Council on 4 April 2022. 3. Following its review of the preliminary report, the GNSO Council requested<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/fouqu…> that the ICANN Board direct ICANN org “to proceed with further developing the SSAD Light Design” while pausing the consideration of the SSAD recommendations. 4. ICANN org published the Whois Disclosure System Design Paper<https://www.icann.org/en/system/files/files/whois-disclosure-system-design-…> on 13 September 2022 and presented it to the small team during its sessions (#1<https://75.schedule.icann.org/meetings/wmhLk2gj2Dm6PQaz2> and #2<https://75.schedule.icann.org/meetings/qm9iHL6YmTSpMoJHQ>) at ICANN75. 5. The small team reviewed the Whois Disclosure Design Paper and provided its feedback and recommendations on how to proceed to the GNSO Council on 7 November 2022 in the form of an addendum to its Preliminary Report. 6. The GNSO Council, as the manager of the GNSO policy development process, reviewed and considered the addendum in light of the potential impacts on the SSAD. 7. Although it is not the role of the GNSO Council to approve or not approve moving forward with operational proof of concepts, the Council is supportive of efforts such as this one that can provide additional data to the ICANN Board in deciding whether or not to approve the SSAD recommendations outlined in the EPDP Phase 2 Final Report. RESOLVED, 1. The GNSO Council accepts the EPDP Phase 2 small team findings and recommendations as outlined in the addendum<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos…>. 2. The GNSO Council requests that the GNSO Secretariat transmits the addendum to the ICANN Board. 3. The GNSO Council confirms that pending the implementation and subsequent running of the Whois Disclosure System for a period of up to two (2) years, the SSAD recommendations should remain paused for consideration by the ICANN Board. 4. The GNSO Council thanks the EPDP Phase 2 small team for its work and requests it to remain available to continue work on this topic as part of the next steps in this process which aims to inform the further consideration of the SSAD recommendations by the ICANN Board. Vote results<https://gnso.icann.org/sites/default/files/policy/2022/vote-result/gnso-cou…> 20221117-4 Motion - Registration Data Accuracy Scoping Team write up for assignments #1 and #2 recommendations Submitted by: Greg DiBiase Seconded by: Thomas Rickert WHEREAS, 1. The GNSO Council adopted a proposal<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-2-pr…> on 21 October 2020 which recommended that a Scoping Team addresses the effects of GDPR on Registration Data accuracy requirements and the Whois Accuracy Reporting System (ARS), stating, "a scoping team would be tasked to, 'facilitate community understanding of the issue; assist in scoping and defining the issue; gather support for the request of an Issue Report, and/or; serve as a means to gather additional data and/or information before a request [for an Issue Report] is submitted'. 2. On 4 November 2020, GNSO SG/Cs as well as ICANN SO/ACs were informed of the Council's intent to form a Registration Data Accuracy Scoping Team and were requested to indicate if they would be interested in sending representatives to this effort. 3. At the same time, the GNSO Council also requested that ICANN org develop a briefing document that outlines both (i) existing accuracy requirements and programs and (ii) the corresponding impact that GDPR has had on implementing / enforcing these requirements and programs. This briefing paper<https://www.icann.org/en/system/files/correspondence/swinehart-to-fouquart-…>was delivered to the Council in February 2021. 4. Following the Council discussion of the ICANN org briefing paper in April 2021, Council leadership put together a first proposal outlining possible instructions to the Registration Data Accuracy Scoping Team. 5. As a result of input that was provided by different Council members on the first proposal, the Council decided at its May 2021 meeting to form a small team to further review and revise the instructions to the scoping team. 6. The small team, consisting of one Council member from each GNSO Stakeholder Group or Constituency, two NomCom appointed Council members and the GNSO Liaison to the GAC (as an observer), submitted its recommendations in relation to the formation as well as the instructions for the Registration Data Accuracy Scoping Team to the Council on9 July 2021<https://mm.icann.org/pipermail/council/2021-July/024851.html> for Council's consideration. 7. The GNSO Council confirmed the formation of the Registration Data Accuracy Scoping Team and its instructions during its meeting on 22 July 2021. 8. The GNSO Council confirmed the Chair for the Scoping Team during its meeting on 23 September 2021. 9. The Scoping Team started its deliberations on 5 October 2021 focusing its efforts on assignments #1 (enforcement and reporting) and #2 (measurement of accuracy). 10. The Scoping Team delivered its write up<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/palag…> for assignments #1 and #2 to the GNSO Council on 5 September 2022. 11. The GNSO Council was briefed on the write up and its recommendations during the Council meeting<https://icann.zoom.us/rec/share/BYAKGwD2U4PMV6RsM7XkxW4B4BSKRquymXb8C1Kb_Z5…> at ICANN75 and continued its deliberations during its October Council meeting<https://icann.zoom.us/rec/share/y26ROY5NZSLyfZj1-Nc4ntlPQgP_Ro9J5FcfR--6B_G…>. RESOLVED, 1. The GNSO Council adopts recommendation #3 of the write up which recommends 1) pausing the work in relation to proposals that require access to registration data, 2) encouraging ICANN org to proceed with their outreach to the EDPB as well as the Data Protection Impact Assessment in connection with the scenario(s) in which the request and processing of registration data takes place as a matter of urgency, and 3) requests that ICANN org and Contracted Parties finalize the negotiations on the Data Processing Agreement (DPA) as soon as practicable as the absence of a completed DPA may act as a roadblock for policy work before Council. 2. The GNSO Council defers consideration of recommendations #1 and #2 until such time the DPA negotiations between ICANN org and Contracted Parties have completed and there is feedback from ICANN org on if/how it anticipates the requesting and processing of registration data will be undertaken in the context of measuring accuracy, or for six months, whichever is the shorter. 3. Once the DPA negotiations are completed and the feedback referred to at paragraph 2 is received from ICANN org, the GNSO Council will review the formation and instructions<https://community.icann.org/x/QoFaCg> to the Scoping Team to ensure these are still fit for purpose and request the Scoping Team to further consider potential proposals that require access to registration data as well as how these impact the existing recommendations #1 and #2 (e.g. should these still be considered by the GNSO Council for adoption, or in the context of proposals that require access to registration data these may no longer be relevant or a priority?). If, after 6 months from this resolution, the DPA negotiations are not completed and/or the required feedback referred to at paragraph 2 has not been provided by ICANN org, Council will discuss and determine whether or not to continue deferring the consideration of recommendations #1 and #2. 4. Taking into account the delay with which the write up was delivered, as well as some of the challenges that were shared with the Scoping Team’s Chair during his briefing to the Council, Council leadership will reach out informally to Scoping Team members to better understand the issues encountered to help inform the Council’s review of the formation and instructions. 5. Council leadership is requested to send a communication to ICANN org in relation to recommendation #3 (as well as Contracted Parties in relation to the DPA) as well as communicate the Council’s decision to non-GNSO groups participating in this effort (ALAC, GAC and SSAC) as well as the Scoping Team. 6. The GNSO Council thanks Michael Palage, outgoing Chair, and Olga Cavalli, outgoing Council liaison, for their efforts. As part of its review of the formation and instructions to the Scoping Team, the Council will consider next steps for finding new leadership for this effort. Vote results<https://gnso.icann.org/sites/default/files/policy/2022/vote-result/gnso-cou…> 20221117-5 Motion - DNS Abuse Small Team Report Submitted by: Mark Datysgeld Seconded by: Sebastien Ducos WHEREAS, 1. The GNSO Council recognizes that the topic of DNS abuse is a longstanding topic and the GNSO has undertaken a variety of activities on this topic in the past, including considering which aspects of the subject of registration abuse are within ICANN's mission to address and in particular, which are appropriate for ICANN to establish policies that are binding on gTLD registry operators and ICANN-accredited registrars[1]<https://community.icann.org/display/gnsocouncilmeetings/Motions+2022-11-17#…>. 2. In February 2022, the GNSO Council tasked a small team consisting of Council members to consider what policy efforts, if any, the GNSO Council should consider undertaking to support the efforts already underway in the different parts of the community to tackle DNS abuse. 3. As part of its deliberations, the small team reached out to all GNSO Stakeholder Groups and Constituencies, as well as the At-Large Advisory Committee (ALAC), the Governmental Advisory Committee (GAC), the Security and Stability Advisory Committee (SSAC) and the DNS Abuse Institute asking for input on what problem(s) policy development specifically is needed to mitigate, if any, as well as the expected outcomes if policy development would be undertaken. 4. In considering the external input received, the small team realized that the suggestions provided can generally be allocated to one or more of the following three buckets: * Issues that may benefit from education / communication / outreach; * Issues that may benefit from contractual negotiations between ICANN org and Contracted Parties; and, * Issues that may benefit from GNSO policy development. 5. The small team delivered its report<https://gnso.icann.org/sites/default/files/policy/2022/correspondence/dns-a…>, containing 4 recommendations, to the GNSO Council on 10 October. 6. The GNSO Council received a briefing on the report and its recommendations during its October Council meeting<https://icann.zoom.us/rec/share/y26ROY5NZSLyfZj1-Nc4ntlPQgP_Ro9J5FcfR--6B_G…>. RESOLVED, 1. The GNSO Council accepts the recommendations as outlined in the DNS Abuse Small Team report and requests that the leadership of the small team works with Council leadership on developing the respective communications as foreseen under recommendations #2, #3 and #4. 2. In relation to recommendation #1, the Council commits to considering requesting the development of a Preliminary Issue Report on the topic of malicious registrations after the outreach and communication as foreseen under recommendations #2, #3 and #4 have taken place and the Council has had an opportunity to consider the progress made from efforts related to that outreach. If the Council determines that a Preliminary Issue Report is needed, it must be undertaken in a way that avoids overlap and/or duplication of efforts. 3. The GNSO Council thanks the small team for its efforts, as well as the community groups that contributed to it. [1]<https://community.icann.org/display/gnsocouncilmeetings/Motions+2022-11-17#…> Some past work includes: * Registration Abuse Policies WG Final Report from 2010: https://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf<https://www.google.com/url?q=https://gnso.icann.org/issues/rap/rap-wg-final…> (some, but not all recommendations adopted) * Staff best practices discussion paper from 2011: https://gnso.icann.org/sites/default/files/filefield_26745/discussion-paper…<https://www.google.com/url?q=https://gnso.icann.org/sites/default/files/fil…> * Uniformity of Contracts to Address Registration Abuse Final Issue Report 2012: https://gnso.icann.org/en/issues/registration-abuse/uofc-final-issue-report…<https://www.google.com/url?q=https://gnso.icann.org/en/issues/registration-…>(Final Issue Report, but not sufficient support to initiate a PDP at the time) Vote results<https://gnso.icann.org/sites/default/files/policy/2022/vote-result/gnso-cou…> Thank you. Kind regards, Nathalie

2 1

Recordings & Zoom Chat | GNSO Council meeting | Thursday, 17 November 2022
by Terri Agnew 17 Nov '22

17 Nov '22

Dear all, Please find below the audio recording, zoom recording (audio, visual, rough transcript) and zoom chat of the GNSO Council meeting held on Thursday, 17 November 2022 at 05:00 UTC. Audio only: https://icann.zoom.us/rec/play/EmFhKxFY6fFzmsisYVV2QvzTGUupuYJGaJk76ZydhKTW… Zoom Recording (includes chat, visual and rough transcript). See both tabs on recording page: https://icann.zoom.us/rec/share/oCyxv39dSpcD3DpcLOuwMgYcyiXMf0a7ybwuxAvA1JL… The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page. <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> Thank you. With kind regards, Terri --- Terri Agnew Policy Operations Specialist (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: terri.agnew.icann Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0