January 2024 - council - lists.icann.org

Pre-ICANN79 GNSO Council Webinar
by ICANN Policy Calendar 23 Jan '24

23 Jan '24

Meeting: Pre-ICANN79 GNSO Council Webinar Date/time: Monday, 26 February 2024 at 21:00 UTC for 60 minutes Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Visit the Wiki Agenda page: https://community.icann.org/x/lICtEQ Check your time zone: http://tinyurl.com/3y4sa69w GNSO Council members are expected to join and will be panelists. Questions will be taken from GNSO Council only. Observers are welcome and will be in listen-only mode. Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call, gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Please click the link below to join the webinar: https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09 Passcode: f!Ym9!npfN If joining Zoom via Zoom App the following will be required: Webinar ID: 922 8356 5389 Passcode: 6981311025 Or One tap mobile : +13462487799,,92283565389#,,,,*6981311025# US (Houston) +16699006833,,92283565389#,,,,*6981311025# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/adGHfYeA3T [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/adGHfYeA3T__;!!PtGJab4!5…>

1 0

Summary of ICANN78 informal meeting re: PPSAI
by Caitlin Tubergen 23 Jan '24

23 Jan '24

SENT ON BEHALF OF KAREN LENTZ Dear Councilors, At the last call, Susan asked about notes from the informal discussion held with interested PPSAI IRT members at ICANN79. For reference, here is where we highlighted this in the GDS session<https://static.sched.com/hosted_files/icann78/0d/slides-GDS-GNSO%20meeting%…> with the Council during the Hamburg meeting and the PPSAI IRT mailing list<https://mm.icann.org/pipermail/gdd-gnso-ppsai-impl/2023-October/000960.html>. The discussion took place on 25 October 2023. NB, these are rough notes of an informal discussion and are not represented as comprehensive. Dennis reviewed the history and how we got to this point, and asked for people’s thoughts on going forward. Responses included the following: * Wanting to be sure we have a clear understanding of the impact of EPDP Ph 1 (Registration Data), also Phase 2a. – factual basis. Should also take into account how contracted parties implement Ph1. * Law, industry, tools have all changed - recognition that some of the recommendations may no longer apply; look for what remains relevant. Some parts are possibly duplicative or no longer needed. * May make sense to start IRT from the point of implementing the PDP recommendations, not from where left off on previous implementation. * Recognition of level of effort, not trivial – building accreditation system. * How to take into account RDRS work. * How to involve the GNSO Council. Could raise now or if staff could triage the recommendations into buckets – Council could consider after looking at that. Don’t want to start IRT if they already know they will be sending things back to Council. * P/P services could voluntarily submit to RDRS – not mutually exclusive with Council work * Will need a high-level view on whether the 2016 policy recommendations are now fit for purpose – can they be implemented in a legally compliant way. Avoid investing resources if policy does not serve present reality. * Data Processing Agreement aspect to this as well. * Interest to participate in next steps. No decisions were made at the meeting. Staff took the action to continue to review and update the analysis from 2021 and provide to the Council, highlighting anything that may have changed. As noted at the Council meeting, we are ultimately looking at developing a proposed work plan for taking up the implementation work this year, and will provide additional updates as that progresses. This would of course be dependent on whether there are questions that the Council wishes to take up or discuss further. Best regards, Karen

2 1

Action Items - GNSO Council meeting 18 January 2024
by Terri Agnew 22 Jan '24

22 Jan '24

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday, 18 January 2024. 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 Recommendations Report for GNSO Guidance Process (“GGP”) for Applicant Support Action Items: The GNSO Secretariat will transmit the Recommendations Report for GNSO Guidance Process (“GGP”) for Applicant Support to the ICANN Board and communicate the GNSO Council’s approval of the report. Recommendations Report for EPDP on Internationalized Domain Names Phase 1 Final Report Action Items: The GNSO Secretariat will transmit the Recommendations Report for EPDP on Internationalized Domain Names Phase 1 Final Report to the ICANN Board and communicate the GNSO Council’s approval of the report. Item 5: COUNCIL DISCUSSION - Communications Small Team Follow-up Conversation Action Items: Communications Small Team to update its report based on feedback received and distribute to the GNSO Council for review. Item 6: COUNCIL DISCUSSION - Council Engagement with PDP Working Group Chairs Action Items: Staff to call for volunteers to form a Small Team to draft a list of questions to pose to PDP Working Group chairs during the next webinar; volunteers during the meeting: Nacho Amadoz and Jeff Neuman. Item 8: ANY OTHER BUSINESS - 8.1 Update on ICANN79 planning and GNSO Draft schedule Action Items: Staff to publish a revised GNSO Draft schedule for ICANN79. 8.3 Update on Diacritic Study Request Action Items: Leadership and staff to develop a draft request for Council to review. 8.4 Update on PPSAI Implementation (GDS will provide update) Action Items: Staff to circulate the notes from the informal PPSAI IRT meeting from ICANN78. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Action needed | Call for Volunteers | SPIRT Charter Drafting Team | Due by 05 February 2024
by Terri Agnew 22 Jan '24

22 Jan '24

Dear GNSO Council, The Generic Names Supporting Organization (GNSO) Council seeks volunteers to serve on a Drafting Team that will develop a charter for the Standing Predictability Implementation Review Team (SPIRT). The SPIRT will be the body empowered to provide input to the GNSO Council, the ICANN Board, ICANN org, and the ICANN community on unforeseen issues arising for the Next Round of the New gTLD Program after the approval by the ICANN Board of the Applicant Guidebook (AGB). What This Drafting Team Will Do The Drafting Team is expected to develop a draft Charter for the SPIRT, which is a group recommended in the new gTLD Subsequent Procedures Final Report. The Drafting Team’s only task is to develop the draft Charter for the SPIRT, with the Charter being subject to GNSO Council approval. As background and for context, the SPIRT will utilize an output called the Predictability Framework, which will be an output of the implementation effort for New gTLD Subsequent Procedures as developed by ICANN org, in coordination with the Implementation Review Team (IRT). This Drafting Team will NOT be responsible for developing the Predictability Framework, but will be responsible for the limited task of determining how the SPIRT will utilize the Predictability Framework, by preparing the draft Charter. In developing the draft Charter, the Drafting Team will be expected to consider elements such as the composition of the SPIRT, detailing how issues are raised to the SPIRT procedurally, defining operating principles and decision-making, and other important aspects to support the proper functioning of the SPIRT. The New gTLD Subsequent Procedures Final Report included an annex [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> that provides detailed guidance on how the SPIRT should operate. The content included in this annex should serve as the starting point for the Drafting Team in developing the draft Charter, but the Drafting Team may determine that improvements can be made to what is suggested in that annex. The SPIRT Charter is a requirement for establishing the SPIRT. However, the SPIRT and the Predictability Framework are by definition, not intended to operate until the AGB is approved by the ICANN Board. Nevertheless, the Council anticipates that this Drafting Team should be able to complete its work in a timely manner (i.e., no more than 3 months), given the extensive existing details included in the annex. Who Should Join The GNSO Council invites interested parties within the GNSO community (i.e., GNSO's stakeholder groups and constituencies), as well as parties from other Supporting Organizations and Advisory Committees to join the Drafting Team. The GNSO Council asks that volunteers take into account the expected membership criteria for this Drafting Team: · Possess basic knowledge of the New gTLD Program from 2012; · Be familiar with the New gTLD Subsequent Procedures Final Report, especially Topic 2 on Predictability and Annex E on the Predictability Framework; · Be familiar with GNSO Working Group Guidelines [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> and Policy Development Process; · Be available to actively contribute to the discussion and activities of the Drafting Team for the duration of the effort; and, · Update your Statement of Interest in accordance with Section 5 of the GNSO Operating Procedures. How to Join GNSO community members who wish to join the Drafting Team should contact the GNSO Secretariat at gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by 05 February 2024. Background For more information and to better prepare for participation on this Drafting Team, please read Topic 2: Predictability [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…> in the New gTLD Subsequent Procedures Final Report, as well as Annex E [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/file/…>. Thank you. With best regards, Greg DiBiase, GNSO Chair Nacho Amadoz, GNSO Council Vice-Chair Tomslin Samme-Nlar, GNSO Council Vice-Chair On behalf of GNSO Council Leadership

1 0

Volunteer opportunity: Review of webinar questions to WG chairs
by Caitlin Tubergen 22 Jan '24

22 Jan '24

Dear Councilors, During the last Council meeting, the Council discussed the pre-ICANN GNSO Council Policy Webinars. In particular, the Council discussed reviewing the draft questions posed to Working Group Chairs to see if this list needs updating. Both Nacho and Jeff volunteered to review the current list of questions. The work will take place via a collaborative Google doc, with a call scheduled if needed. If you have any interest in joining this review, please respond to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> by Wednesday, 24 January. Kind regards, Caitlin

1 0

Fwd: [FormerMembersCCWG-AP] [Ext] ICANN Grant Program Applicant Guide
by Anne ICANN 22 Jan '24

22 Jan '24

Dear Council Members, Please see below correspondence from Giovanni Seppia re the ICANN Grant Program. Also see my reply in my personal capacity regarding the prohibition on former CCWG Auction Proceeds acting as advisors to Grant Program applicants. (No personal interest in this, just a point of view based on CCWG policy recommendations.) The ICANN Grant Program Guidebook contains a prohibition on former CCWG members acting as advisors to grant program applicants. ICANN Org explains this prohibition based on the policy recommendation that CCWG members cannot apply for grants as per the policy recommendations made by the CCWG. Here is the paragraph from Giovanni Seppia: *"In developing the ICANN Grant Program, the Applicant Guide extends this recommended eligibility exclusion to include a restriction for CCWG-AP members to be eligible for funding for “proposal activities as principals, advisors, or in other roles.” While this removes CCWG-AP members to serve as advisors (paid or unpaid) to applicants within the ICANN Grant Program, this is a necessary and logical extension of the CCWG-AP guidance in furtherance of ICANN’s need to protect against self-dealing." * Below you will see my response to the email from Giovanni. I have no interest in being an advisor to persons seeking iCANN Grants. However, I don't think prohibiting former CCWG Auction Proceeds memberfrom acting in that capacity falls within the CCWG policy recommendations. You will also see the chain of emails from former CCWG members objecting to this prohibition. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso(a)gmail.com ---------- Forwarded message --------- From: Giovanni Seppia <giovanni.seppia(a)icann.org> Date: Fri, Jan 19, 2024 at 12:13 PM Subject: Re: [FormerMembersCCWG-AP] [Ext] ICANN Grant Program Applicant Guide To: Maureen Hilyard <maureen.hilyard(a)gmail.com>, Alan Greenberg < alan.greenberg(a)mcgill.ca>, FormerMembersCCWG-AP(a)icann.org < FormerMembersCCWG-AP(a)icann.org> Dear Maureen, Alan, Vanda, former members of the CCWG-AP, Thanks again for the considerations you shared last week on the former CCWG-AP members list. While we recognize that some ICANN community members that previously served on the Cross-Community Working Group on Auction Proceeds (CCWG-AP) may wish to be more involved in ICANN Grant Program applications than is allowed under the Applicant Guide, ICANN org is not in a position to update eligibility requirements at this time. Throughout the community’s work to deliver recommendations to the Board on Auction Proceeds, ICANN continually reinforced the need to have clear, strong, and appropriate limitations on whether and how those developing the recommendations could benefit from the resulting program. As clearly documented within the CCWG-AP’s Final Report, and as reinforced throughout the CCWG-AP process, CCWG-AP members were aware of the intention that they or their family members would be ineligible to receive grants through their affiliated businesses. The CCWG-AP’s guidance included, in response to Charter Question 2: There must be protections against self-dealing and measures to ensure that decisions are taken without conflict of interest. The following measures are recommended to be considered as part of the implementation process: - Prohibition on auction proceeds being awarded to businesses that are owned in whole or in part by ICANN Board members, executives or staff or their family members and awards that may be used to pay compensation to ICANN Board members, executives or staff or their family members. - Segregation of duties amongst those who develop the requirements and those who assist in the identification of potential recipients. - Prohibition on awards of assistance to businesses owned in whole or in part by the CCWG members (participating in any phase of the CCWG process), their family members, and awards that would be used to pay compensation to CCWG members or their family members. In developing the ICANN Grant Program, the Applicant Guide extends this recommended eligibility exclusion to include a restriction for CCWG-AP members to be eligible for funding for “proposal activities as principals, advisors, or in other roles.” While this removes CCWG-AP members to serve as advisors (paid or unpaid) to applicants within the ICANN Grant Program, this is a necessary and logical extension of the CCWG-AP guidance in furtherance of ICANN’s need to protect against self-dealing. First, ICANN has no meaningful way to confirm or enforce if a CCWG-AP member is serving in a paid or unpaid role with an applicant, and there could be other ways that the member could receive benefit from a successful application than compensation. ICANN has a core obligation to avoid even the potential appearance of self-dealing. Second, the CCWG-AP was not designed to create a pool of ICANN community members who could hold themselves out as providing special knowledge or support to applicants; the CCWG-AP specifically acknowledged a need for segregation between recommendation development and identification of potential applicants. ICANN cannot now change our position to encourage that type of work. While we understand that this limitation has practical impacts on the former members of the CCWG-AP or entities that might be relying on those people for support in the application process, this is an important limitation that preserves the integrity of the ICANN Grant Program and ICANN’s obligations to implement a program free from even the suggestion of self-dealing or conflicts of interest. We remain available to provide you with any further information and/or clarification you may need. Best regards, Giovanni *From: *FormerMembersCCWG-AP <formermembersccwg-ap-bounces(a)icann.org> on behalf of Giovanni Seppia <giovanni.seppia(a)icann.org> *Date: *Friday, 12 January 2024 at 06:34 *To: *Maureen Hilyard <maureen.hilyard(a)gmail.com>, Alan Greenberg < alan.greenberg(a)mcgill.ca> *Cc: *"FormerMembersCCWG-AP(a)icann.org" <FormerMembersCCWG-AP(a)icann.org> *Subject: *Re: [FormerMembersCCWG-AP] [Ext] ICANN Grant Program Applicant Guide Dear Maureen, Alan, Thanks for sharing your further considerations on this eligibility element. Allow me to discuss it internally and come back to you in a timely manner. Best regards, Giovanni *From: *Maureen Hilyard <maureen.hilyard(a)gmail.com> *Date: *Friday, 12 January 2024 at 05:28 *To: *Alan Greenberg <alan.greenberg(a)mcgill.ca> *Cc: *Giovanni Seppia <giovanni.seppia(a)icann.org>, Vanda Scartezini < vanda(a)scartezini.org>, "FormerMembersCCWG-AP(a)icann.org" < FormerMembersCCWG-AP(a)icann.org> *Subject: *Re: [FormerMembersCCWG-AP] [Ext] ICANN Grant Program Applicant Guide Thank you Giovanni for your input into this discussion. I would note that the prohibition appears to apply when a CCWG member owns or partly owns the company that might be making the application for funds. If the CCWG member is also a voluntary member of a not-for-profit organisation that wants to make an application, surely the Applicant Guide does not prevent their being an advisor in a capacity that does not require any payment or reimbursement? All of the participants of the CCWG were acting in a volunteer capacity - many from under-developed regions where advisors for this type of activity are few and far between. Therefore they would be valued members of many organisations and may be asked to participate in this type of advisory role. How does one ensure that they are getting the correct information if they are from organisations that are aware of the nuances of different ICANN application systems? Maureen On Thu, Jan 11, 2024 at 6:01 PM Alan Greenberg <alan.greenberg(a)mcgill.ca> wrote: Thanks Giovanni, Although I honestly cannot recall the prohibition in the CCWG recommendations, it is clearly there. However, I note that the Applicant Guide goes quite far beyond the recommendation by forbidding CCWG participants to act as (unpaid) advisors or in other roles. Alan *From:* FormerMembersCCWG-AP <formermembersccwg-ap-bounces(a)icann.org> *On Behalf Of *Giovanni Seppia *Sent:* Wednesday, January 10, 2024 4:33 PM *To:* Vanda Scartezini <vanda(a)scartezini.org> *Cc:* FormerMembersCCWG-AP(a)icann.org *Subject:* Re: [FormerMembersCCWG-AP] [Ext] ICANN Grant Program Applicant Guide Dear Vanda, Thanks for the nice message on the work that the Grant Program team, with the great support and cooperation of many colleagues, has done to date. With reference to your consideration about members of the CCWG-AP, I have paste below a text that is included in the CCWG-AP Final Report (page 24): “There must be protections against self-dealing and measures to ensure that decisions are taken without conflict of interest. The following measures are recommended to be considered as part of the implementation process: ○ Prohibition on auction proceeds being awarded to businesses that are owned in whole or in part by ICANN Board members, executives or staff or their family members and awards that may be used to pay compensation to ICANN Board members, executives or staff or their family members. ○ Segregation of duties amongst those who develop the requirements and those who assist in the identification of potential recipients. ○ Prohibition on awards of assistance to businesses owned in whole or in part by the CCWG members (participating in any phase of the CCWG process), their family members, and awards that would be used to pay compensation to CCWG members or their family members.” Let me know if this is helpful. Best regards, Giovanni *From: *Vanda Scartezini <vanda(a)scartezini.org> *Date: *Wednesday, 10 January 2024 at 20:29 *To: *Giovanni Seppia <giovanni.seppia(a)icann.org> *Cc: *Xavier Calvez <xavier.calvez(a)icann.org>, " FormerMembersCCWG-AP(a)icann.org" <FormerMembersCCWG-AP(a)icann.org> *Subject: *[Ext] ICANN Grant Program Applicant Guide Dear Giovanni, Xavier, former members First of all, again Happy New year, with huge success to you all. Thank you Giovanni and Xavier for your work on delivering the Grant Program guide book! Appreciate. I would like to raise the following question: Why members of Auction Proceed, who that never been involved with the details of the application guide book are not able to participate? We have worked as volunteers and our work have finished defining the model ICANN could have to manage such Grant program. We didn’t go further in defining any other requirements for the applicants. I am sure I didn’t. The DNS Women group where I am CEO would like to participate due to the kind of activities we perform among women in several countries related to the DNS. Auction Proceed members have dedicated their time to the Auction Proceed Working Group for years and we never have in mind this would be a reason for being excluded from this Program. Will it be the same restriction, for instance for everyone that has been participating in the new gTLD round ?? it was not the case in 2012! I really cannot see any conflict of interest based on the ICANN bylaws that prevent the volunteer members to participate in this new Grant pilot. Of course, if any former member had participated on the definition of this guidebook, then there would be conflict, otherwise, I certainly do not see any conflict and would like to know the reasons this impediment was stated. I appreciate your feedback! Thanks again for this new program !! *Vanda Scartezini * *Polo Consultores Associados * *São Paulo, Brazil* *vanda(a)scartezini.org <vanda(a)scartezini.org>* *Mobile: + 55 11 98181-1464* *From: *FormerMembersCCWG-AP <formermembersccwg-ap-bounces(a)icann.org> on behalf of Giovanni Seppia <giovanni.seppia(a)icann.org> *Date: *Monday, 8 January 2024 at 17:41 *To: *FormerMembersCCWG-AP(a)icann.org <FormerMembersCCWG-AP(a)icann.org> *Subject: *[FormerMembersCCWG-AP] ICANN Grant Program Applicant Guide Dear former members of the CCWG-AP, I would like to inform you that the ICANN Grant Program Applicant Guide has been published at: https://www.icann.org/en/system/files/files/icann-grant-program-applicant-g… The Grant Program webpage has been updated with the Applicant Guide as well as the FAQs and timeline: https://www.icann.org/grant-program-en Kind regards, Giovanni _______________________________________________ FormerMembersCCWG-AP mailing list FormerMembersCCWG-AP(a)icann.org https://mm.icann.org/mailman/listinfo/formermembersccwg-ap _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. _______________________________________________ FormerMembersCCWG-AP mailing list FormerMembersCCWG-AP(a)icann.org https://mm.icann.org/mailman/listinfo/formermembersccwg-ap _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

2 2

Reminder: Input welcome on GNSO Council agenda for 2024 meetings
by Terri Agnew 22 Jan '24

22 Jan '24

Dear councilors, A reminder to all that a Google doc<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> is open for all to add their suggestions and comments to the upcoming GNSO Council meeting agendas. This does not have to be in the form of a full agenda item proposal, simple comments and questions are equally welcome! You are welcome to add to the document<https://urldefense.com/v3/__https:/docs.google.com/document/d/1FSNlAHTjbWAz…> via the comments feature. Thank you! Kind regards, Terri Policy Team Supporting the GNSO

1 0

Document and Motion deadline | Monday, 05 February 2024 at 23:59 UTC for GNSO Council Meeting 15 February 2024 at 21:00 UTC
by Terri Agnew 22 Jan '24

22 Jan '24

Dear all, Reports, motions, and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 05 February 2024 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 15 February 2024 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Motions Wiki at: https://community.icann.org/x/9oAvEQ Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

FW: [Ext] NEW: ICANN Universal Acceptance Update: Support for Internationalized Email Addresses
by Julie Bisland 22 Jan '24

22 Jan '24

FYI: From: ICANN Community Digest <david.olive-icann.org(a)shared1.ccsend.com> Reply-To: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, January 22, 2024 at 10:01 AM To: Julie Bisland <julie.bisland(a)icann.org> Subject: [Ext] NEW: ICANN Universal Acceptance Update: Support for Internationalized Email Addresses [https://r20.rs6.net/on.jsp?ca=f066084f-f246-4a8a-953c-fd5c9095bc61&a=112202…] Monday, 22 January 2024 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN organization Policy Development Support function publishes this twice-weekly digest to help ICANN community groups 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=001-AYf_B2KvAxqi7lr…> Do you have any ideas for improving the ICANN Community Digest? Write to us at policyinfo(a)icann.org!<mailto:policyinfo@icann.org> Table of Contents ICANN79 · FRIDAY: ICANN79 Community Childcare Grants Program: Now Accepting Applications Information Sharing · NEW: EURALO Roundtable on the Registration Data Request Service (RDRS) · NEW: ICANN NCAP Discussion Group Seeks Input on NCAP Study 2 Report · NEW: ICANN Universal Acceptance Update: Support for Internationalized Email Addresses · NEW PUBLICATION: Methodology to Classify Unsolicited Email Threats · THIS WEEK: ICANN Webinars to Provide First RDRS Metrics Report Findings and Gather Feedback · NEXT WEEK: Call for SOs/ACs to Nominate Fellowship Program Mentors Action Items · NEXT WEEK 🔥 ACTION ITEM: Questionnaire for the 20-year review of WSIS implementation · 🔥 ACTION ITEM: Calling for NextGen@ICANN Applications for ICANN80 · 🔥 ACTION ITEM: Apply Now for ICANN Leadership Positions Public Comment · NEW: Draft NCAP Study 2 Report and Responses to Questions Regarding Name Collisions · Draft Final Report of the 2023 Africa Domain Name Industry Study · Draft ICANN FY25 Plans · Draft PTI FY25 Operating Plan and Budget ICANN79 FRIDAY: ICANN79 Community Childcare Grants Program: Now Accepting Applications Grants of up to $750 per family are available for ICANN Public Meeting participants who meet the criteria, are bringing children, and will incur expenses associated with babysitting and/or local childcare services. Deadline: Friday, 26 January 2024, at 23:59 Coordinated Universal Time (UTC). Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…>. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> Information Sharing NEW: EURALO Roundtable on the Registration Data Request Service (RDRS) The roundtable will provide a review of the RDRS service. Speakers will explain how the services works, discuss experiences using the service, provide metrics on usage data of the RDRS, end user understanding and point of view, the At-Large position and broader community’s opinion, and answer any questions and respond to comments and discussion. Date: Tuesday, 30 January at 18:00 UTC Registration and Join Details [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> NEW: ICANN NCAP Discussion Group Seeks Input on NCAP Study 2 Report The Name Collision Analysis Project Discussion Group (NCAP) is seeking input on its draft Study 2 report and responses to a series of questions from the ICANN Board regarding name collisions as outlined in resolution 2017.11.02.30 and reaffirmed in resolution 2021.03.25.13. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> NEW: ICANN Universal Acceptance Update: Support for Internationalized Email Addresses Work is ongoing to ensure all pertinent ICANN internal systems are fully UA-ready. Much of this effort includes collaborating with third-party vendors to update their services. In the broader scope of the UA program, ICANN's priority is to support UA in community-facing services, including ICANN.org, ICANN Account, and the Centralized Zone Data Service, to name a few. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> NEW PUBLICATION: Methodology to Classify Unsolicited Email Threats Spam is typically the largest portion of DNS abuse in the data that is listed by reputation feed providers. Therefore, being able to confidently separate spam as a delivery mechanism of malicious content from other types of content is essential for our work. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> THIS WEEK: ICANN Webinars to Provide First RDRS Metrics Report Findings and Gather Feedback The webinars will be offered at two time slots and you only need to register for one. Both sessions will be presented in English. Click on one of the links below to register. Webinar #1 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> | Wednesday, 24 January 2024 at 00:00 UTC for 60 minutes Webinar #2 [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> | Thursday, 25 January 2024 at 15:00 UTC for 60 minutes Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> NEXT WEEK: Call for SOs/ACs to Nominate Fellowship Program Mentors ICANN invites the Supporting Organizations (SOs) and Advisory Committees (ACs) to nominate volunteers to serve as Fellowship Program Mentors. Each group is welcome to nominate one individual for this role. Individual self-nominations will not be considered. • Mentors generally must plan on a time commitment of approximately 30-40 hours before, during, and immediately after each ICANN Public Meeting. This includes extensive pre-meeting preparation, on-site support for their assigned fellows, and post-meeting reporting. • Mentors will serve a term that includes three consecutive ICANN Public Meetings, beginning with ICANN81 (from ICANN81 - ICANN83 inclusive). • Mentors are expected to follow Fellowship Program guidelines to help ensure consistency in capacity development opportunities for fellows and to help fellows actively participate in ICANN's work. • Mentors will receive travel funding support (if applicable). For more information on the guidelines and expectations, please read about the mentorship program here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…>. Mentors cannot serve on the Selection Committee at the same time they are serving as mentors. Interested SOs/ACs should select their respective Fellowship Program mentor representative by 31 January 2024 and notify ICANN Fellowship Program Manager, Siranush Vardanyan at siranush.vardanyan(a)icann.org. Action Items NEXT WEEK 🔥 ACTION ITEM: Questionnaire for the 20-year review of WSIS implementation Please consider responding to the United Nations Commission on Science and Technology for Development (CTSD) regarding WSIS implementation by 31 January 2024. CSTD Submission form [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> 🔥 ACTION ITEM: Calling for NextGen@ICANN Applications for ICANN80 ICANN wants to hear from university students living and studying in the African region who are interested in the future of the Internet and in participating in the ICANN80 Policy Forum. ICANN80 is scheduled to be held in Kigali, Rwanda, from 10–13 June 2024. Deadline: 23 February 2024 Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> 🔥 ACTION ITEM: Apply Now for ICANN Leadership Positions Selected individuals will have a unique opportunity to work with accomplished colleagues from around the globe to help shape the policy development and technical coordination of the Internet's unique identifiers. Deadline: 15 March 2024 at 23:59 UTC Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> Public Comment NEW: Draft NCAP Study 2 Report and Responses to Questions Regarding Name Collisions [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> Open for Submissions: 19 January 2024 Closed for Submissions: 28 February 2024 Draft Final Report of the 2023 Africa Domain Name Industry Study [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> Open for Submissions: 21 December 2023 Closed for Submissions: 08 February 2024 Draft ICANN FY25 Plans [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> Open for Submissions: 12 December 2023 Closed for Submissions: 12 February 2024 Draft PTI FY25 Operating Plan and Budget [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> Open for Submissions: 12 December 2023 Closed for Submissions: 12 February 2024 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…>. Volume 6, Issue 6 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…> | Next Issue: Thursday, 25 January 2024 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001-AYf_B2KvAxqi7lr…>

1 0

REMINDER - DUE TODAY: For your review - Council Strategic Planning Session Meeting Report
by Caitlin Tubergen 19 Jan '24

19 Jan '24

Dear Councilors, Thank you to those of you who have already provided comments on the SPS Report<https://docs.google.com/document/d/1685l5jXq-NW5SwYFp8FDAzPHM-zy63FZwid8J_4…>. This is a kind reminder that if you would like to provide feedback, the deadline is today, 19 January. Kind regards, Steve, Terri, and Caitlin From: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Thursday, January 11, 2024 at 5:01 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: For your review - Council Strategic Planning Session Meeting Report Dear Councilors, The GNSO Staff Support Team has worked with Council leadership on the Strategic Planning Session (SPS) Meeting Report, which you can find here: https://docs.google.com/document/d/1685l5jXq-NW5SwYFp8FDAzPHM-zy63FZwid8J_4…. The SPS Report includes a number of proposed action items, which the Council reviewed during its meeting in December. Please review the report<https://docs.google.com/document/d/1685l5jXq-NW5SwYFp8FDAzPHM-zy63FZwid8J_4…>, particularly the proposed action items beginning on p. 20, to ensure the action items align with your recollection of the discussions. Please use the comment function to add any suggestions and/or proposed edits. If possible, please provide your input by Friday, January 19. Once the report is finalized, it will be publicly posted. Best regards, Steve, Terri, and Caitlin

1 0