November 2022 - council - lists.icann.org

FW: [gnso-chairs] Update on SubPro ODP and Policy Question Set #6
by Aikman-Scalese, Anne Nov. 28, 2022

Nov. 28, 2022

Please see below from Jeff. He says my changes have been incorporated into the Council’s Response to Question Set # 6. STEVE – could you please post the final Google link and a Word doc to the Council list for final “non-objection” approval by Council members? (I understand Leadership will determine the deadline for non-objection.) Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image003.png@01D90312.6814D270] From: Jeff Neuman <jeff(a)jjnsolutions.com> Sent: Monday, November 28, 2022 8:16 AM To: Aikman-Scalese, Anne <AAikman(a)lewisroca.com>; Steve Chan <steve.chan(a)icann.org>; Sebastien(a)registry.godaddy; dibiase(a)amazon.com; john.mcelwaine(a)nelsonmullins.com Subject: RE: [gnso-chairs] Update on SubPro ODP and Policy Question Set #6 [EXTERNAL] ________________________________ [Removed the Council as that is beyond my posting privileges as the liaison] Thanks Anne. These have now been incorporated into the draft<https://docs.google.com/document/d/18C6Vulnv6V0Akyq3IeehWuSGg1TAHCYJEBGXHrA…>. Council Leadership – How long should we keep this open for comment so that I can submit it to ICANN’s ODP Team? Sincerely, Jeff [cid:image001.png@01D90312.6814D270] 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: Aikman-Scalese, Anne <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>> Sent: Wednesday, November 23, 2022 3:08 PM To: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>; Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>; COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Cc: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Subject: RE: [gnso-chairs] Update on SubPro ODP and Policy Question Set #6 Importance: High Thanks Steve and Jeff, for the drafting and the further explanation. As an active participant on Sub Pro and given that the small team will not be convened for this Council response to Question Set #6, I have some suggested changes for consideration by the full Council which I believe are important procedurally. Those changes are shown in purple in the attached document and pasted again below. I summarize the reasons for the changes here: 1. Council should affirm Org’s stated understanding that if Implementation Guidance must be varied, Org should specify the “valid reasons” (language from the Sub Pro Final Report) and should consult with the IRT regarding appropriate alternatives. 1. The Org’s question regarding Recommendation 17.12 in relation to the Applicant Support program presents a special case due to the initiation of the GNSO Guidance Process on Applicant Support. I think we need to say that in that case, variations to Implementation Guidance should be the subject of consultations with the Applicant Support Guidance Team. 1. In cases where the IRT is not yet formed and no GNSO Guidance Process (or other process outlined in the GNSO Operating Procedures) has been initiated, org should specify the reasons for recommending a variation to the Implementation Guidance and should seek the opinion of Council, e.g. via the procedures applicable to the GNSO Input process. (Presumably the last case could theoretically happen after Board review of the Operational Design Assessment.) I believe the changes below and in the attached draft preserve the appropriate role for Council in connection with Implementation as provided in the PDP Manual and in the GNSO Guidance Process. This will be particularly important in relation to the development of the Applicant Support program as the Guidance Process proceeds. The recommended changes are pasted below and shown in the attached draft. It is good to know (as Steve said yesterday) that there would not be any sort of “hold-up” in the expected date for the org’s delivery of the Operational Design Assessment based on the requested response to Question Set #6. This is an important topic and may require discussion at the Council level in our December meeting. (Thank you, Jeff, for offering to review this in December.) If required, I am noting a formal objection to the initial draft without the suggested changes. (Jeff said this doesn’t go on the Council’s agenda unless a Councilor objects so I am trying to follow the rules.) AEAS Proposed Changes to the Response to Sub Pro ODP Question Set #6 The Council agrees with your understanding that “if something cannot be implemented exactly as specified in Implementation Guidance, the org would be expected to describe its efforts and rationale for such cases, and to work with the IRT to implement an alternative in line with the purpose behind the recommended action”. In relation to the GNSO Initiated Applicant Support Guidance Process that has been launched in response to the question posed by the ODP, the Council believes that alternatives to the specified Implementation Guidance should be addressed in the context of that GNSO Guidance Process and would expect the org to work with the Applicant Support Guidance Team to address any required changes to Implementation Guidance. In short, implementation guidance remains a strong recommendation as opposed to a requirement. As referenced in the Preamble to the Sub Pro Final Report, ICANN should specify any “circumstances where there may be valid reasons not to take such guidance exactly as described…” In such circumstances, Council believes that consultation with the IRT, the Guidance Process Team, or the Council itself (e.g. via a request for GNSO Input) is in order prior to the adoption of alternatives to the specified Implementation Guidance. In all cases, the implementation should be accomplished in a manner that achieves the objectives laid out in the implementation guidance even if the mechanism of implementation differs slightly from that contained in the final report. Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image003.png@01D90312.6814D270] From: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>> Sent: Tuesday, November 22, 2022 2:50 PM To: Aikman-Scalese, Anne <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>>; Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>; COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Cc: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Subject: Re: [gnso-chairs] Update on SubPro ODP and Policy Question Set #6 [EXTERNAL] ________________________________ Hi Anne, I see your response came in before I completed this response. Just noting that I’ve seen it already, but think the response below should still hopefully be helpful. Hi Anne, Let me try and answer your question. The SubPro ODP Team has an understanding of how implementation guidance should be treated, which in their words is, “a strongly recommended action and that if in some circumstances there may be valid reasons not to take such guidance exactly as described, this would remain consistent with the Final Report.” This understanding comes from the Final Report preamble and was reinforced by previous ODP question/answers. There is specific phrasing for a handful of recommendations where the SubPro ODP Team wants to validate that their understanding of implementation guidance, pasted above, still holds true. The reason they are asking is because the recommendation language (i.e., “must”) cites the implementation guidance in the recommendation language itself, potentially creating a relationship requirement between the recommendation and embedded implementation guidance. I’ve highlighted an example of the language that is causing the potential ambiguity, where it can be construed that the implementation guidance in these specific instances, must be fulfilled precisely “as detailed” in order to meet the requirements of the recommendation. * Recommendation 17.12: ICANN org must develop a plan for funding the Applicant Support Program, as detailed in the Implementation Guidelines below. Here is a link to Jeff’s draft responses, where you can see that he validates the SubPro ODP Team understanding of implementation guidance, which holds for these specific recommendations: https://docs.google.com/document/d/18C6Vulnv6V0Akyq3IeehWuSGg1TAHCYJEBGXHrA…. As requested, the draft responses are attached in Word. Hopefully this provides a bit of clarity and I certainly welcome Jeff, as well as Councilors, to weigh in. Best, Steve From: Gnso-chairs <gnso-chairs-bounces(a)icann.org<mailto:gnso-chairs-bounces@icann.org>> on behalf of "Aikman-Scalese, Anne via Gnso-chairs" <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Reply-To: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>> Date: Tuesday, November 15, 2022 at 9:04 AM To: "Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>" <Sebastien(a)registry.godaddy<mailto:Sebastien@registry.godaddy>>, "COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>>, GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Cc: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Subject: Re: [gnso-chairs] Update on SubPro ODP and Policy Question Set #6 Thanks Sebastien. JEFF – I am a bit confused by the examples presented in Question Set 6 from the Sub Pro ODP team. The examples are all labelled “Recommendation” and all include the word “must” which has a defined meaning in the Sub Pro Final Report. The Implementation Guidance does not generally include the word “must”. That word was used consistently in connection with Recommendations and Question Set 6 appears to be reciting “must” Recommendations but treating them as Implementation Guidance. Could you please clarify the question being asked in Question Set 6? (I have previously volunteered to join that Sub Pro small team.) Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image005.png@01D90312.6814D270] From: council <council-bounces(a)gnso.icann.org<mailto:council-bounces@gnso.icann.org>> On Behalf Of Sebastien--- via council Sent: Saturday, November 12, 2022 3:10 AM To: COUNCIL(a)GNSO.ICANN.ORG<mailto:COUNCIL@GNSO.ICANN.ORG>; gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>; GNSO-Chairs <gnso-chairs(a)icann.org<mailto:gnso-chairs@icann.org>> Subject: [council] FW: Update on SubPro ODP and Policy Question Set #6 [EXTERNAL] ________________________________ Dear Council Colleagues, Please find below our Council Liaison to the SubPro ODP’s latest updates. Thank you Jeff for providing these. Please review them ahead of our meeting on 17 November (or 16 depending on time zones). Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_615475152] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Date: Thursday, 10 November 2022 at 10:30 pm To: john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> <john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com>>, dibiase(a)amazon.com<mailto:dibiase@amazon.com> <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>, Sebastien Ducos <sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>> Cc: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>, SubPro ODP Mailman List <subpro-odp(a)icann.org<mailto:subpro-odp@icann.org>> Subject: Update on SubPro ODP and Policy Question Set #6 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@. Dear Council Leadership, Can you please post this on the GNSO Council List? This afternoon I had my November call with the ICANN Org SubPro Team led by Karen Lentz. Here is the latest update: 1. On Schedule. During that call, ICANN org confirmed that they are in fact on schedule to deliver the Operational Design Assessment the week of December 12th. The team met its deadline for “pens down” which was yesterday and the document is undergoing internal review. In addition, they are working on an executive summary. 1. Updated Assumptions. On November 8th, ICANN posted a new Assumptions document (https://www.icann.org/en/system/files/files/draft-assumptions-subsequent-pr… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…>) which contains all of the previous assumptions (in grey) as well some new ones (not in grey). 1. GNSO Council Briefing on ODA. The ICANN org ODP team would like to set up a call with the Council the week of December 5th to give the Council a preview of the assessment like they did for the SSAD ODA. They will also go over their expectations on timing, and an input mechanism for feedback on the ODA. Like the SSAD ODA, there will not be a formal public comment period, but there may be opportunities for Q&A and potentially providing our own input to the Board. 1. Community Webinar on ODA. After the ODA is released the week of the 12th, ICANN is planning on conducting a webinar for the community to discuss the assessment. It will be open to anyone interested in the program. 1. Final (?) Question Set. The ICANN SubPro ODP Team has posted an additional question that they would like us to respond to regarding the role of Implementation Guidance where a Recommendation incorporates by reference such Implementation guidance. They have confirmed that the ODA release is not dependent on the timing of our response to Question Set 6 provided that their view in that question is consistent with ours (which I believe is). I have copied the question and am working on a proposed response in the following Google Document. https://docs.google.com/document/d/18C6Vulnv6V0Akyq3IeehWuSGg1TAHCYJEBGXHrA… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> 1. Council SPS Planning. We discussed other activities that will need to occur after the ODA is delivered to the Board including the commencement of two (2) IRPs once the ICANN Board approves the recommendations. The Final Report Recommendations include one IRT for Applicant Support and a second IRT for everything else. We believe it is a good idea to discuss this at the Council SPS in December which involves a discussion of the work in the coming year for the Council. Please let me know if you have any questions or you would like me to go over any of this as AOB during the Council meeting on the 17th. Sincerely, Jeffrey J. Neuman GNSO Liaison to SubPro [cid:image007.png@01D90312.6814D270] 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 [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> From: Michael Karakash <michael.karakash(a)icann.org<mailto:michael.karakash@icann.org>> Sent: Thursday, November 10, 2022 2:53 PM To: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; SubPro ODP Mailman List <subpro-odp(a)icann.org<mailto:subpro-odp@icann.org>> Subject: Policy Question Set #6 Hi Jeff, It was great connecting on today’s call to discuss the latest ODP-related developments. As noted, we recently drafted a new Policy Question Set (#6) focused on the topic of Implementation Guidance that I am attaching to this email. Please don’t hesitate to reach out if you have questions or need any clarification. Thank you! Best, Michael ________________________________ 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.

1 0

FW: [Ext] ICANN Restarts the Community Regional Outreach Program for FY23
by Nathalie Peregrine Nov. 24, 2022

Nov. 24, 2022

Thursday, 24 November 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=001m9BJWK_hWAT999NK…> Table of Contents Information Sharing · NEW: ICANN Hosts Community Webinar on New gTLD SubPro ODA · NEW: Celebrating ICANN CIO Ashwin Rangan, 2022 ORBIE Award Winner · NEW: ICANN Restarts the Community Regional Outreach Program for FY23 · REMINDER: Register to attend ICANN's Draft ICANN FY24 Plans Informational Webinar · REMINDER: ICANN Calls for Volunteers to Plan for Changing the Root Zone DNSSEC Algorithm · REMINDER: Register for the ICANN Grant Program Implementation Update Webinar · REMINDER: ICANN Launches Fiscal Year 2024 Additional Budget Request Process · REMINDER: Call for SOs/ACs to Nominate Fellowship Program Mentors and Selection Committee Members · REMINDER ICANN77 Fellowship Application Round Now Open Public Comment · Initial Report on the Second CSC Effectiveness Review · EXTENDED: Registration Data Consensus Policy for gTLDs Information Sharing NEW: ICANN Hosts Community Webinar on New gTLD SubPro ODA ICANN will host a community webinar on the Operational Design Assessment (ODA) for the New Generic Top-Level Domain (gTLD) Subsequent Procedures (SubPro) Final Report. The event will take place on Wednesday, 14 December 2022 at 13:00–15:00 and 20:00–22:00 UTC. For those interested in joining the webinar on Wednesday, 14 December 2022 (13:00–15:00 UTC and 20:00–22:00 UTC), please be sure to register in advance for either session, by following this registration link [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> NEW: Celebrating ICANN CIO Ashwin Rangan, 2022 ORBIE Award Winner Ashwin (Ash) Rangan [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…>, Senior Vice President of Engineering and Chief Information Officer (CIO), recently won a 2022 SoCal CIO of the Year ORBIE Award [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…>. The annual ORBIE Awards recognize top tech executives across the United States. This year, the Southern California chapter of the nationwide professional network of CIOs named five winners in the region. Ashwin, who is based in our Los Angeles office, received the Corporate ORBIE for CIOs of organizations with up to $200 million annual revenue. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> NEW: ICANN Restarts the Community Regional Outreach Program for FY23 ICANN organization is restarting the Community Regional Outreach Program (CROP). The Fiscal Year 2023 (FY23) CROP space [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> is now available for use by eligible community groups. FY23 CROP trips will be available starting Monday, 16 January 2023. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> REMINDER: Register to attend ICANN's Draft ICANN FY24 Plans Informational Webinar The Internet Corporation for Assigned Names and Numbers (ICANN) invites the ICANN community to participate in an informational webinar about the Draft FY24-28 Operating and Financial Plan, and Draft FY24 Operating Plan and Budget. Both webinars will present identical information. · 15 December 2022 at 01:00 UTC Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> · 15 December 2022 at 16:00 UTC Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> Read More. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> 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=001m9BJWK_hWAT999NK…> 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=001m9BJWK_hWAT999NK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> REMINDER: 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=001m9BJWK_hWAT999NK…> 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=001m9BJWK_hWAT999NK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> 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=001m9BJWK_hWAT999NK…>. 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=001m9BJWK_hWAT999NK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> 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. REMINDER: 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=001m9BJWK_hWAT999NK…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> Public Comment Initial Report on the Second CSC Effectiveness Review [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> Open for submissions date: 14 September 2022 Closed for submissions date: 01 December 2022 EXTENDED: Registration Data Consensus Policy for gTLDs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> Open for submissions date: 24 August 2022 Closed for submissions date: 05 December 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…>. Volume 4, Issue 86 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> | Next Issue: Monday, 28 November 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe nathalie.peregrine(a)icann.org [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=un&m=00…> Update Profile [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=oo&m=00…> | Constant Contact Data Notice [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> powered by [Image removed by sender. Trusted Email from Constant Contact - Try it FREE today.][r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…> Try email marketing for free today! [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001m9BJWK_hWAT999NK…>

1 0

Re: [council] [gnso-chairs] Update on SubPro ODP and Policy Question Set #6
by Steve Chan Nov. 23, 2022

Nov. 23, 2022

Hi Anne, I see your response came in before I completed this response. Just noting that I’ve seen it already, but think the response below should still hopefully be helpful. Hi Anne, Let me try and answer your question. The SubPro ODP Team has an understanding of how implementation guidance should be treated, which in their words is, “a strongly recommended action and that if in some circumstances there may be valid reasons not to take such guidance exactly as described, this would remain consistent with the Final Report.” This understanding comes from the Final Report preamble and was reinforced by previous ODP question/answers. There is specific phrasing for a handful of recommendations where the SubPro ODP Team wants to validate that their understanding of implementation guidance, pasted above, still holds true. The reason they are asking is because the recommendation language (i.e., “must”) cites the implementation guidance in the recommendation language itself, potentially creating a relationship requirement between the recommendation and embedded implementation guidance. I’ve highlighted an example of the language that is causing the potential ambiguity, where it can be construed that the implementation guidance in these specific instances, must be fulfilled precisely “as detailed” in order to meet the requirements of the recommendation. * Recommendation 17.12: ICANN org must develop a plan for funding the Applicant Support Program, as detailed in the Implementation Guidelines below. Here is a link to Jeff’s draft responses, where you can see that he validates the SubPro ODP Team understanding of implementation guidance, which holds for these specific recommendations: https://docs.google.com/document/d/18C6Vulnv6V0Akyq3IeehWuSGg1TAHCYJEBGXHrA…. As requested, the draft responses are attached in Word. Hopefully this provides a bit of clarity and I certainly welcome Jeff, as well as Councilors, to weigh in. Best, Steve From: Gnso-chairs <gnso-chairs-bounces(a)icann.org> on behalf of "Aikman-Scalese, Anne via Gnso-chairs" <gnso-chairs(a)icann.org> Reply-To: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com> Date: Tuesday, November 15, 2022 at 9:04 AM To: "Sebastien(a)registry.godaddy" <Sebastien(a)registry.godaddy>, "COUNCIL(a)GNSO.ICANN.ORG" <council(a)gnso.icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, GNSO-Chairs <gnso-chairs(a)icann.org> Cc: Jeff Neuman <jeff(a)jjnsolutions.com> Subject: Re: [gnso-chairs] Update on SubPro ODP and Policy Question Set #6 Thanks Sebastien. JEFF – I am a bit confused by the examples presented in Question Set 6 from the Sub Pro ODP team. The examples are all labelled “Recommendation” and all include the word “must” which has a defined meaning in the Sub Pro Final Report. The Implementation Guidance does not generally include the word “must”. That word was used consistently in connection with Recommendations and Question Set 6 appears to be reciting “must” Recommendations but treating them as Implementation Guidance. Could you please clarify the question being asked in Question Set 6? (I have previously volunteered to join that Sub Pro small team.) Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8FE79.4BB0B740] From: council <council-bounces(a)gnso.icann.org> On Behalf Of Sebastien--- via council Sent: Saturday, November 12, 2022 3:10 AM To: COUNCIL(a)GNSO.ICANN.ORG; gnso-secs(a)icann.org; GNSO-Chairs <gnso-chairs(a)icann.org> Subject: [council] FW: Update on SubPro ODP and Policy Question Set #6 [EXTERNAL] ________________________________ Dear Council Colleagues, Please find below our Council Liaison to the SubPro ODP’s latest updates. Thank you Jeff for providing these. Please review them ahead of our meeting on 17 November (or 16 depending on time zones). Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_615475152] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>> Date: Thursday, 10 November 2022 at 10:30 pm To: john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> <john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com>>, dibiase(a)amazon.com<mailto:dibiase@amazon.com> <dibiase(a)amazon.com<mailto:dibiase@amazon.com>>, Sebastien Ducos <sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>> Cc: Steve Chan <steve.chan(a)icann.org<mailto:steve.chan@icann.org>>, SubPro ODP Mailman List <subpro-odp(a)icann.org<mailto:subpro-odp@icann.org>> Subject: Update on SubPro ODP and Policy Question Set #6 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@. Dear Council Leadership, Can you please post this on the GNSO Council List? This afternoon I had my November call with the ICANN Org SubPro Team led by Karen Lentz. Here is the latest update: 1. On Schedule. During that call, ICANN org confirmed that they are in fact on schedule to deliver the Operational Design Assessment the week of December 12th. The team met its deadline for “pens down” which was yesterday and the document is undergoing internal review. In addition, they are working on an executive summary. 1. Updated Assumptions. On November 8th, ICANN posted a new Assumptions document (https://www.icann.org/en/system/files/files/draft-assumptions-subsequent-pr… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…>) which contains all of the previous assumptions (in grey) as well some new ones (not in grey). 1. GNSO Council Briefing on ODA. The ICANN org ODP team would like to set up a call with the Council the week of December 5th to give the Council a preview of the assessment like they did for the SSAD ODA. They will also go over their expectations on timing, and an input mechanism for feedback on the ODA. Like the SSAD ODA, there will not be a formal public comment period, but there may be opportunities for Q&A and potentially providing our own input to the Board. 1. Community Webinar on ODA. After the ODA is released the week of the 12th, ICANN is planning on conducting a webinar for the community to discuss the assessment. It will be open to anyone interested in the program. 1. Final (?) Question Set. The ICANN SubPro ODP Team has posted an additional question that they would like us to respond to regarding the role of Implementation Guidance where a Recommendation incorporates by reference such Implementation guidance. They have confirmed that the ODA release is not dependent on the timing of our response to Question Set 6 provided that their view in that question is consistent with ours (which I believe is). I have copied the question and am working on a proposed response in the following Google Document. https://docs.google.com/document/d/18C6Vulnv6V0Akyq3IeehWuSGg1TAHCYJEBGXHrA… [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> 1. Council SPS Planning. We discussed other activities that will need to occur after the ODA is delivered to the Board including the commencement of two (2) IRPs once the ICANN Board approves the recommendations. The Final Report Recommendations include one IRT for Applicant Support and a second IRT for everything else. We believe it is a good idea to discuss this at the Council SPS in December which involves a discussion of the work in the coming year for the Council. Please let me know if you have any questions or you would like me to go over any of this as AOB during the Council meeting on the 17th. Sincerely, Jeffrey J. Neuman GNSO Liaison to SubPro [cid:image004.png@01D8FE79.4BB0B740] 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 [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> From: Michael Karakash <michael.karakash(a)icann.org<mailto:michael.karakash@icann.org>> Sent: Thursday, November 10, 2022 2:53 PM To: Jeff Neuman <jeff(a)jjnsolutions.com<mailto:jeff@jjnsolutions.com>>; SubPro ODP Mailman List <subpro-odp(a)icann.org<mailto:subpro-odp@icann.org>> Subject: Policy Question Set #6 Hi Jeff, It was great connecting on today’s call to discuss the latest ODP-related developments. As noted, we recently drafted a new Policy Question Set (#6) focused on the topic of Implementation Guidance that I am attaching to this email. Please don’t hesitate to reach out if you have questions or need any clarification. Thank you! Best, Michael ________________________________ 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

Liaison Call with GAC Point of Contact
by Jeff Neuman Nov. 23, 2022

Nov. 23, 2022

Dear GNSO Council Members, The GAC Point of Contact (Jorge Cancio) and I had our monthly call last Friday (November 18, 2022). Below is a summary of our call. 1. As you know, GAC has a new leadership team that will start at the end of the March ICANN Meeting in Cancun. The Leadership team, led by Nicolas Caballero (Paraguay) is getting up to speed on everything and they should be in a good position to take over. A list of the new leadership can be found here: https://gac.icann.org/activity/gac-2022-chair-and-vicechairs-elections 1. The GAC has filed comments on the Holistic Review, The Registration Data protection policy and the RDAP Amendment. The RDAP Amendment comments were delivered late and may not appear in the public comment area on the ICANN website, but will be included in the summary. Comments can be found here: https://gac.icann.org/statement/public/gac-comments-rdap-brda-amendments-16… 1. Tentatively, GNSO Council and GAC are set to have a bilateral at ICANN Cancun on March 15th at 9:00 local time. 1. For the meeting at ICANN, we would like to have discussions not just on areas that we differ, but potentially on areas which we agree and where we can support each other. Perhaps topics like the SubPro ODA/ODP, the SubPro IRT, or even the DPAs between ICANN and the Contracted Parties. We want to make the meetings less adversarial and more about things we can do together. 1. For ICANN 76, the GAC is aiming to have more outreach / capacity building sessions like they did in KL. With all of the GAC member turnover in the past several years, the capacity/outreach sessions talking about some of the basics was really helpful to GAC members and is something that they would like to have on an ongoing basis. This will likely be held on March 11, 2023, in Cancun (Saturday). GAC Leadership may be reaching out to the Council / GNSO on topics. As the Liaison, I volunteered to help the GAC with any GNSO topics and finding people to participate. 1. We are looking at Mid-late February for a GAC Leadership / GNSO Leadership call to discuss agenda for GAC/GNSO Bilateral meeting at ICANN76. Please let me know if you have any questions or would like to discuss this further. Sincerely, Jeff Neuman GNSO Council Liaison to GAC [cid:image001.png@01D8FB31.B08BF080] 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

1 0

FW: Update on SubPro ODP and Policy Question Set #6
by Sebastien＠registry.godaddy Nov. 22, 2022

Nov. 22, 2022

Dear Council Colleagues, Please find below our Council Liaison to the SubPro ODP’s latest updates. Thank you Jeff for providing these. Please review them ahead of our meeting on 17 November (or 16 depending on time zones). Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_615475152] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> From: Jeff Neuman <jeff(a)jjnsolutions.com> Date: Thursday, 10 November 2022 at 10:30 pm To: john.mcelwaine(a)nelsonmullins.com <john.mcelwaine(a)nelsonmullins.com>, dibiase(a)amazon.com <dibiase(a)amazon.com>, Sebastien Ducos <sebastien(a)registry.godaddy> Cc: Steve Chan <steve.chan(a)icann.org>, SubPro ODP Mailman List <subpro-odp(a)icann.org> Subject: Update on SubPro ODP and Policy Question Set #6 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@. Dear Council Leadership, Can you please post this on the GNSO Council List? This afternoon I had my November call with the ICANN Org SubPro Team led by Karen Lentz. Here is the latest update: 1. On Schedule. During that call, ICANN org confirmed that they are in fact on schedule to deliver the Operational Design Assessment the week of December 12th. The team met its deadline for “pens down” which was yesterday and the document is undergoing internal review. In addition, they are working on an executive summary. 1. Updated Assumptions. On November 8th, ICANN posted a new Assumptions document (https://www.icann.org/en/system/files/files/draft-assumptions-subsequent-pr…<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.icann…>) which contains all of the previous assumptions (in grey) as well some new ones (not in grey). 1. GNSO Council Briefing on ODA. The ICANN org ODP team would like to set up a call with the Council the week of December 5th to give the Council a preview of the assessment like they did for the SSAD ODA. They will also go over their expectations on timing, and an input mechanism for feedback on the ODA. Like the SSAD ODA, there will not be a formal public comment period, but there may be opportunities for Q&A and potentially providing our own input to the Board. 1. Community Webinar on ODA. After the ODA is released the week of the 12th, ICANN is planning on conducting a webinar for the community to discuss the assessment. It will be open to anyone interested in the program. 1. Final (?) Question Set. The ICANN SubPro ODP Team has posted an additional question that they would like us to respond to regarding the role of Implementation Guidance where a Recommendation incorporates by reference such Implementation guidance. They have confirmed that the ODA release is not dependent on the timing of our response to Question Set 6 provided that their view in that question is consistent with ours (which I believe is). I have copied the question and am working on a proposed response in the following Google Document. https://docs.google.com/document/d/18C6Vulnv6V0Akyq3IeehWuSGg1TAHCYJEBGXHrA…<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.goog…> 1. Council SPS Planning. We discussed other activities that will need to occur after the ODA is delivered to the Board including the commencement of two (2) IRPs once the ICANN Board approves the recommendations. The Final Report Recommendations include one IRT for Applicant Support and a second IRT for everything else. We believe it is a good idea to discuss this at the Council SPS in December which involves a discussion of the work in the coming year for the Council. Please let me know if you have any questions or you would like me to go over any of this as AOB during the Council meeting on the 17th. Sincerely, Jeffrey J. Neuman GNSO Liaison to SubPro [cid:image001.png@01D8F51D.62A9C6E0] 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<https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjjnsolutio…> From: Michael Karakash <michael.karakash(a)icann.org> Sent: Thursday, November 10, 2022 2:53 PM To: Jeff Neuman <jeff(a)jjnsolutions.com>; SubPro ODP Mailman List <subpro-odp(a)icann.org> Subject: Policy Question Set #6 Hi Jeff, It was great connecting on today’s call to discuss the latest ODP-related developments. As noted, we recently drafted a new Policy Question Set (#6) focused on the topic of Implementation Guidance that I am attaching to this email. Please don’t hesitate to reach out if you have questions or need any clarification. Thank you! Best, Michael

2 2

NomCom - Job Description Review
by Sebastien＠registry.godaddy Nov. 22, 2022

Nov. 22, 2022

Dear GNSO Council colleagues, As occurs on an annual basis, the Nominating Committee (NomCom) has invited the GNSO Council to review the skill-set and GNSO job description that is used both for recruitment and for the NomCom to use in their evaluation process. You can see the 2022 job description here<https://www.icann.org/resources/pages/nomcom2022-positions-2021-12-15-en#gn…>, which was a result of the Council’s review and revisions last year. Council leadership has reviewed the 2022 job description and believe it remains fit for purpose and can again be used in 2023. Our suggestion therefore is to decline making any edits this cycle. If you believe changes are in fact needed, please reply to this message by the end of this week. If changes are needed and are of a substantive nature, we may need to consider establishing a short-live small team. If changes are not needed, we will simply convey that message to the NomCom. Please let us know if you have any questions. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_3281414813] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

2 2

Draft minutes of the GNSO Council meeting 17 November 2022
by Nathalie Peregrine Nov. 21, 2022

Nov. 21, 2022

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting held on Thursday, 17 December 2022. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 01 December 2022. Thank you. Kind Regards, Nathalie

1 0

Action Items - GNSO Council meeting | 17 November 2022
by Nathalie Peregrine Nov. 21, 2022

Nov. 21, 2022

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday 17 November 2022. Please refer to the Action Item page<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> for updates on item completion progress. Please take note of the action items coming out of the Council meeting and the proposed timing for delivering on these actions. Please refer to this page for the recent status updates on the Action items. Please note that actions for all councilors are highlighted below. Item 3: Consent Agenda Acknowledgment of John McElwaine to serve as Council liaison to the Rights Protection Mechanisms (RPMs) Implementation Review Team (IRT) Action Items: Staff on behalf of Council leadership to communicate to GDS staff the GNSO Council’s acknowledgment of John McElwaine to serve as Council liaison to the Rights Protection Mechanisms (RPMs) Implementation Review Team (IRT). Acknowledgment of the Expedited PDP on Internationalized Domain Names (IDNs) Project Change Request (PCR) Action Items: Policy support staff to update the IDNs-EPDP Team’s project plan, timeline, and other materials according to the Project Change Request (PCR), and post them on the EPDP wiki project space. Item 4: COUNCIL VOTE - Whois Disclosure System Next Steps Action Items: 1. The GNSO Secretariat transmits the EPDP Phase 2 small team findings and recommendations as outlined in the addendum to the ICANN Board. 2. On behalf of the GNSO Council the GNSO Secretariat 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. Item 5: COUNCIL VOTE - Registration Data Accuracy Scoping Team - Adoption of Recommendation #3 Action Items: 1. 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. 2. Council leadership to send a communication to ICANN org in relation to the GNSO Council’s adoption of 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. 3. The GNSO Secretariat, on behalf of the GNSO Council, thanks Michael Palage, outgoing Chair, and Olga Cavalli, outgoing Council liaison, for their efforts. 4. 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. 5. Include a placeholder on the meeting agenda for May or June 2023. Item 6: COUNCIL VOTE - DNS Abuse Small Team Report Action Items: 1. The GNSO Secretariat, on behalf of the GNSO Council, thanks the DNS Abuse small team for its efforts, as well as the community groups that contributed to it. 2. Leadership of the small team to work with Council leadership on developing the respective communications as foreseen under recommendations #2, #3 and #4 in the report Item 7: COUNCIL DISCUSSION - Uniform Domain Name Dispute Resolution Policy (UDRP) Review Next Steps Action Items: Staff to request from ICANN GDS staff an estimate as to the duration of the RPMs Phase 1 implementation. Once that is received John McElwaine to send to the Council list the options – deferral for either for 18 months or until the IRT is complete. Item 8: COUNCIL DISCUSSION - Expired Domain Deletion Policy and the Expired Registration Recovery Policy Next Steps Action Items: Council leadership to form a small team to review information provided by ICANN Compliance in view of deciding next steps which could include 1) concluding that no acute issues are present and no Policy Status Report is needed, and that the two policies will be added to the “end” of the pipeline for consideration at a future date, or 2) concluding that there is reason enough to request a PSR to obtain further information on the basis of which the Council can decide whether additional work in the form of policy development or implementation guidance is necessary. . Item 9: COUNCIL DISCUSSION - Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI) - Work Stream 2 (WS2) Action Items: Council members to review WS2 recommendations report and come prepared to consider the report for adoption during the December meeting. Item 11: ANY OTHER BUSINESS 11.1 – New CCOICI Chair Action Items: Staff will produce a motion on behalf of the GNSO Council leadership to acknowledge Manju Chen as CCOICI Chair for the consent agenda of the December 2022 Council meeting. 11.3 - GNSO Nominated Fellowship Program Mentor and Fellowship Selection Committee Member Action Items: Staff on behalf of the GNSO Council leadership to circulate to the Stakeholder Group and Constituency Chairs a call for an expression of interest for the GNSO Nominated Fellowship Program Mentor and Fellowship Selection Committee Member.

1 0

FW: [Ext] NEW: Special Meeting of the ICANN Board, 16 November 2022 Approved Resolutions
by Julie Bisland Nov. 21, 2022

Nov. 21, 2022

FYI - From: ICANN Community Digest <david.olive(a)icann.org> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, November 21, 2022 at 10:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: Special Meeting of the ICANN Board, 16 November 2022 Approved Resolutions [https://r20.rs6.net/on.jsp?ca=604d009f-78d1-4f74-a891-5c0e5cdce490&a=112202…] Monday, 21 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=001MxHc5NR_V2BaMNNR…> Table of Contents Information Sharing · NEW: Special Meeting of the ICANN Board, 16 November 2022 · NEW: Register to attend ICANN's Draft ICANN FY24 Plans Informational Webinar · NEW: Join ICANN at the 17th Annual Meeting of the Internet Governance Forum · REMINDER: ICANN Calls for Volunteers to Plan for Changing the Root Zone DNSSEC Algorithm · REMINDER: Register for the ICANN Grant Program Implementation Update Webinar · 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 · REMINDER ICANN77 Fellowship Application Round Now Open Public Comment · CLOSES TODAY: Registration Data Consensus Policy for gTLDs · Initial Report on the Second CSC Effectiveness Review Information Sharing NEW: Special Meeting of the ICANN Board, 16 November 2022 Please find approved resolutions from the 16 November 2022 Special Meeting of the ICANN Board here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…>. NEW: Register to attend ICANN's Draft ICANN FY24 Plans Informational Webinar The Internet Corporation for Assigned Names and Numbers (ICANN) invites the ICANN community to participate in an informational webinar about the Draft FY24-28 Operating and Financial Plan, and Draft FY24 Operating Plan and Budget. Both webinars will present identical information. · 15 December 2022 at 01:00 UTC Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> · 15 December 2022 at 16:00 UTC Register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> Read More. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> NEW: Join ICANN at the 17th Annual Meeting of the Internet Governance Forum Leaders of the Internet Corporation for Assigned Names and Numbers (ICANN) organization (org) and members of the ICANN community will participate in the 17th Annual Meeting of The Internet Governance Forum [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> (IGF) from 28 November to 2 December 2022. This hybrid meeting will take place in Addis Ababa, Ethiopia, under the theme "Resilient Internet for a Shared Sustainable and Common Future." Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> REMINDER: 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=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…>. 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=001MxHc5NR_V2BaMNNR…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…> 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. REMINDER: 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=001MxHc5NR_V2BaMNNR…>. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> Public Comment CLOSES TODAY: Registration Data Consensus Policy for gTLDs [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…> 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=001MxHc5NR_V2BaMNNR…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…>. Volume 4, Issue 85 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…> | Next Issue: Thursday, 24 November 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001MxHc5NR_V2BaMNNR…>

1 0

Re: [council] [Ext] RE: ICANN Grant Program Implementation Update Webinar - 1 December 2022 at 15:00 UTC
by Marika Konings Nov. 18, 2022

Nov. 18, 2022

This document may provide some further insights into the expected operation of CCWGs: https://gnso.icann.org/sites/default/files/file/field-file-attach/2016-12/u… (A Uniform Framework of Principles and Recommendations for Cross Community Working Groups (CCWG). Note that these principles foresee that if an CCWG IRT is necessary, this should be recommended and communicated to the Chartering Organizations. In the case of the new gTLD Auction Proceeds CCWG, it seems it was left to the Board to indicate whether involvement of a CCWG IRT would be necessary. Best regards, Marika From: "Aikman-Scalese, Anne" <AAikman(a)lewisroca.com> Date: Thursday, 17 November 2022 at 16:42 To: Marika Konings <marika.konings(a)icann.org>, 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: [Ext] RE: [council] ICANN Grant Program Implementation Update Webinar - 1 December 2022 at 15:00 UTC Thanks Marika. For some reason I thought the Chartering Organizations had adopted the procedures specified in the PDP Manual but perhaps I am wrong about that. Could you please share more information regarding your reference to the “CCWG Implementation Team”? Is that a team that is composed outside the GNSO processes? Thank you, Anne Anne E. Aikman-Scalese Of Counsel AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com> D. 520.629.4428 [cid:image002.png@01D8FAA5.4CA43F50] From: Marika Konings <marika.konings(a)icann.org> Sent: Thursday, November 17, 2022 8:39 AM To: Aikman-Scalese, Anne <AAikman(a)lewisroca.com>; Emily Barabas <emily.barabas(a)icann.org>; 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: Re: [council] ICANN Grant Program Implementation Update Webinar - 1 December 2022 at 15:00 UTC [EXTERNAL] ________________________________ 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<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: Thursday, 17 November 2022 at 16:10 To: Emily Barabas <emily.barabas(a)icann.org<mailto:emily.barabas@icann.org>>, "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] 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:image004.png@01D8FAA5.4CA43F50] From: Emily Barabas <emily.barabas(a)icann.org<mailto:emily.barabas@icann.org>> Sent: Thursday, November 17, 2022 4:15 AM To: Aikman-Scalese, Anne <AAikman(a)lewisroca.com<mailto:AAikman@lewisroca.com>>; 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> Cc: Giovanni Seppia <giovanni.seppia(a)icann.org<mailto:giovanni.seppia@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:image006.png@01D8FAA5.4CA43F50] 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:image006.png@01D8FAA5.4CA43F50] 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. ________________________________ 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