<div dir="ltr"><div>Dear members, </div><div><br></div><div>FYI<br clear="all"></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Warmly,<br></div>Tomslin<div><span style="color:rgb(0,0,0);font-size:12.8px"></span></div><br></div></div></div></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Devan Reed via council</b> <span dir="auto"><<a href="mailto:council@icann.org">council@icann.org</a>></span><br>Date: Tue, 10 Dec 2024 at 08:31<br>Subject: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 19 December 2024<br>To: <a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a> <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>><br>Cc: GNSO-Secs <<a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a>><br></div><br><br><div class="msg-5394474247919558007">
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="m_-5394474247919558007WordSection1">
<p class="MsoNormal">Dear all,</p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Please find below the agenda for the GNSO Council Meeting on 19 December 2024 at 21:00 UTC. This is posted on the
<a href="https://community.icann.org/x/E4DyEg" target="_blank">agenda wiki page</a>.</p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank you!</p>
<p class="MsoNormal">Kind regards,<br>
Devan </p>
<p class="MsoNormal"><span style="color:black;background:white">Policy Team Supporting the GNSO<u></u><u></u></span></p>
<div style="border:none;border-bottom:dotted windowtext 3.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="color:black;background:white"><u></u> <u></u></span></p>
</div>
<p style="margin-right:0in;margin-bottom:6.0pt;margin-left:0in">
<b><span style="font-size:23.0pt;color:black">GNSO Council Agenda 19 December 2024</span></b></p>
<p style="margin:0in"><span style="color:black">Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access:
</span><a href="https://community.icann.org/x/CICeFw" target="_blank"><span style="color:#1155cc">https://community.icann.org/x/CICeFw</span></a><span style="color:black">. </span></p>
<p style="margin:0in"><span style="color:black"> </span></p>
<p style="margin:0in"><span style="color:black">This agenda was established according to the</span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-15mar23-en.pdf" target="_blank"><span style="color:#1155cc"> GNSO Operating Procedures</span></a><span style="color:black">
v3.5, updated on 15 March 2023.</span></p>
<p style="margin:0in"><span style="color:black">For convenience:</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;vertical-align:baseline">
An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda.<u></u><u></u></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda.<u></u><u></u></li></ul>
<p style="margin:0in"><span style="color:black"> </span></p>
<p style="margin:0in"><span style="color:black">GNSO Council meeting on Thursday, 19 December 2024 at 21:00 UTC:
</span><a href="https://tinyurl.com/ybse6rda" target="_blank"><span style="color:#1155cc">https://tinyurl.com/ybse6rda</span></a><span style="color:black"> </span></p>
<p style="margin:0in"><span style="color:black"> </span></p>
<p style="margin:0in"><span style="color:black">13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; 00:00 Moscow (Friday); 08:00 Melbourne (Friday)</span></p>
<p style="margin:0in;background:white"><b><span style="color:black"> </span></b></p>
<p style="margin:0in;background:white"><b><span style="color:black">GNSO Council Meeting Remote Participation:</span><span style="color:blue">
</span></b><span style="color:black"><a href="https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09" target="_blank"><b>https://icann.zoom.us/j/92283565389?pwd=QnlHK1JSbzdiSFFZSjRjamxMTkNGdz09</b></a></span></p>
<p style="margin:0in;background:white"><span style="color:black">Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call.</span></p>
<p style="margin:0in"><span style="color:black">___________________________________</span></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 1: Administrative Matters (5 minutes)</span></b></p>
<p style="margin:0in;background:white"><span style="color:black">1.1 - Roll Call</span></p>
<p style="margin:0in;background:white"><span style="color:black">1.2 - Updates to Statements of Interest</span></p>
<p style="margin:0in;background:white"><span style="color:black">1.3 - Review / Amend Agenda</span></p>
<p style="margin:0in;background:white"><span style="color:black">1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: </span></p>
<p style="margin:0in;background:white"><span style="color:black"><a href="https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso-council-17oct24-en.pdf" target="_blank"><span style="color:#1155cc;background:white">Minutes</span></a><span style="background:white">
of the GNSO Council Meeting on 17 October 2024 were posted on 01 November 2024.</span></span></p>
<p style="margin:0in;background:white"><span style="color:black"><a href="https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso-council-part1-13nov24-en.pdf" target="_blank"><span style="color:#1155cc;background:white">Minutes
</span></a><span style="background:white">(Part 1) </span><a href="https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso-council-part2-13nov24-en.pdf" target="_blank"><span style="color:#1155cc;background:white">Minutes</span></a><span style="background:white">
(Part 2) of the GNSO Council Meeting on 13 November 2024 were posted on 02 December 2024.</span></span></p>
<p style="margin:0in;background:white"><span style="color:black"> </span></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 2: Opening Remarks / Review of Projects & Action List (0 minutes)</span></b></p>
<p style="margin:0in;background:white"><span style="color:black">2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of<a href="https://gnso.icann.org/en/council/project" target="_blank"><span style="color:black">
</span><span style="color:#0052cc">Projects List</span></a></span><u><span style="color:#0052cc">
</span></u><span style="color:#172b4d">and</span><span style="color:black"><a href="https://community.icann.org/x/RgZlAg" target="_blank"><span style="color:#172b4d">
</span><span style="color:#0052cc">Action Item List. </span></a></span></p>
<p style="margin:0in;background:white"><span style="color:black"> </span></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 3: Consent Agenda (5 minutes)</span></b></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;vertical-align:baseline">
GNSO Review of the GAC Communiqué<span style="font-family:"Arial",sans-serif"><u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
Recommendations Report for the Expedited Policy Development Process (EPDP) on Internationalized Domain Names (IDNs) Phase 2 <span style="font-family:"Arial",sans-serif"><u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
Confirmation of GNSO Empowered Community Representative (Tomslin Samme-NIar)<span style="font-family:"Arial",sans-serif"><u></u><u></u></span></li></ul>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in;background:white">
<b><span style="color:black">Item 4: COUNCIL VOTE - Empowered Community Approval Action on Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2 Reconsideration (10 minutes)</span></b></p>
<p style="margin:0in;background:white"><span style="color:black">Pursuant to Section 25.2(e) of the ICANN Bylaws, the ICANN Board approved
<a href="https://itp.cdn.icann.org/en/files/governance/uppdates-to-article-4-icann-grant-program-07-08-2024-en.pdf" target="_blank">
<span style="color:#1155cc">Fundamental Bylaws Amendments to Article 4, Sections 4.2 and 4.3</span></a> of the ICANN Bylaws.</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:#333333">
</span><span style="color:black">The ICANN Board took a series of actions and communications to move forward with the ICANN Grant Program while in some cases, trying to address issues presented by the original language of Recommendation 7, including:</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#333333;background:#fefefe;vertical-align:baseline">
<span style="color:black">26 October 2023 </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-26-10-2023-en" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1155cc">resolutions</span></a></span><span style="color:black">
revisiting the Board's prior approval of Recommendation 7 and directing the development of a more general process for the ICANN community to indicate when ICANN's Accountability Mechanisms should not be available;</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><u></u><u></u></span></li><li class="MsoNormal" style="color:#333333;background:#fefefe;vertical-align:baseline">
<span style="font-size:12.0pt"><a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-21-01-2024-en#section2.d" target="_blank"><span style="font-size:11.0pt;color:#047bc1">21 January 2024 initiation</span></a></span>
<span style="color:black">of a Fundamental Bylaws amendment process setting forth the general process for the ICANN community to limit access to ICANN's Accountability Mechanisms; and,</span><span style="font-size:12.0pt"><u></u><u></u></span></li><li class="MsoNormal" style="color:#333333;margin-bottom:.25in;background:#fefefe;vertical-align:baseline">
<span style="font-size:12.0pt;font-family:"Arial",sans-serif"><a href="https://www.icann.org/files/correspondence/sinha-to-clemente-et-al-02mar24-en.pdf" target="_blank"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#047bc1">2 March 2024 letter</span></a></span><span style="color:black">
to the CCWG-AP’s Chartering Organizations specifying a proposed change to Recommendation 7 to remove a reference to the “Independent Application Assessment Panel” so that Recommendation 7 could better achieve its goal of preserving auction proceeds for grants
instead of funding challenges to decisions on grant applications; and the</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><u></u><u></u></span></li></ul>
<p style="margin:0in;background:#fefefe"><span style="color:black">On 7 August 2024, ICANN opened a</span><span style="color:#333333;background:#fefefe">
</span><span style="color:black"><a href="https://www.icann.org/en/public-comment/proceeding/proposed-fundamental-bylaws-amendments-related-to-grant-program-07-08-2024" target="_blank"><span style="color:#047bc1;background:#fefefe">Public Comment Forum</span></a></span><span style="color:#333333;background:#fefefe">
</span><span style="color:black">on the updated Fundamental Bylaws Proposal, with the proposed amendments being limited and in line with Recommendation 7. Nine submissions were received, and all commenters were supportive of the proposal as posted for Public
Comment. Commenters noted that the updated proposal was better aligned to the intention of Recommendation 7 and was a more appropriate means of implementation than the prior proposal. </span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black">Concurrently, ICANN finalized confirmation with the Chartering Organizations of the CCWG-AP their support or non-objection to the proposal to update Recommendation 7, including confirmation
with the GAC that it too is in a position to support or not object to the updating of Recommendation 7, in light of the Board's acceptance of this alternate path. The Board has formally confirmed its adoption of the updated Recommendation 7 and the respective
Fundamental Bylaws Amendments.</span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black">At ICANN81, ICANN Org held an
<a href="https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-mechanisms" target="_blank">
Empowered Community Approval Action</a> on <a href="https://www.icann.org/en/ec/fundamental-bylaws-amendment-to-accountability-mechanisms" target="_blank">
Fundamental Bylaws Amendments to Article 4 Accountability and Review, 4.2 Reconsideration.</a></span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black"> </span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black">The Fundamental Bylaws Amendments will only become effective if approved by the Empowered Community using the process set forth at
<a href="https://www.icann.org/resources/pages/governance/bylaws-en/#article25" target="_blank">Section 25.2(f)</a> and
<a href="https://www.icann.org/resources/pages/governance/bylaws-en/#annexD" target="_blank">Annex D</a>, Article 1 of the ICANN Bylaws. The convening of the Approval Action Community Forum is part of this process. </span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black"> </span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black">Following the Approval Action Community Forum, the GNSO Stakeholder Groups and Constituencies are asked to provide feedback, opinions or comments on their support for, objection to, or abstention
from the Approval Action under consideration. The GNSO Council must decide and inform the EC Administration of its decision within twenty-one (21) days after the expiration of the Community Forum whether to support, object to, or abstain from the Approval
Action by affirmative vote of a GNSO Supermajority.</span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black"> </span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black">A discussion and vote on the Approval Action is scheduled for this GNSO Council meeting. If more time is needed, a placeholder for an email vote will be scheduled to initiate on Monday, 23 December.</span></p>
<p style="margin:0in;background:#fefefe"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span></p>
<p style="margin:0in;background:#fefefe"><span style="color:black">Here, the Council will vote on the Fundamental Bylaw amendments.</span></p>
<p style="margin:0in;background:white"><span style="color:black">4.1 - Presentation of
<a href="https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-12-19" target="_blank">
<span style="color:#1155cc">Motion</span></a> (Tomslin Samme-NIar, GNSO Council Vice Chair)</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">4.2 - Council Discussion </span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">4.3 - Council Vote (voting threshold: Supermajority)</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 5: COUNCIL VOTE - Charter for Policy Development Process on Latin Script Diacritics (15 minutes)</span></b></p>
<p style="margin:0in;background:white"><span style="color:black">On 13 November 2024, the GNSO Council passed a
<a href="https://gnso.icann.org/en/council/resolutions/2020-current#202405" target="_blank"><span style="color:#1155cc">motion</span></a> to initiate a Policy Development Process (PDP) on requesting Latin Script Diacritics. The objective of the
<a href="https://gnso.icann.org/sites/default/files/policy/2024/draft/preliminary-issue-report-latin-script-diacritics-17jul24-en.pdf" target="_blank">
<span style="color:#1155cc">Preliminary Issue Report</span></a> was for ICANN org to assess all relevant issues related to the GNSO Council request, and, following Community Input during the
<a href="https://www.icann.org/en/public-comment/proceeding/preliminary-issue-report-on-latin-script-diacritics-18-07-2024" target="_blank">
<span style="color:#1155cc">Public Comment</span></a> phase, to recommend a course of action to the GNSO Council. </span></p>
<p style="margin:0in;background:white"><span style="color:black">The PDP will be focused on the circumstance when an ASCII gTLD and the Latin script diacritic version of the gTLD are not variants of each other AND may be found to be visually similar to each
other. The issue is theoretically possible for any existing ASCII or Latin script IDN gTLD pairs, and is essentially infinite for future applied-for ASCII or Latin script IDN gTLDs, where diacritics are involved. The
<a href="https://gnso.icann.org/sites/default/files/policy/2024/draft/final-issue-report-pdp-latin-diacritics-12sep24-en.pdf" target="_blank">
<span style="color:#1155cc">Final Issue Report</span></a> includes a draft charter prepared by ICANN org supporting the GNSO Council. Having discussed the draft charter, the Council determined that edits were needed with respect to, but not limited to, the
membership structure. </span></p>
<p style="margin:0in;background:white"><span style="color:black">Here, the Council will vote on the updated charter.</span></p>
<p style="margin:0in;background:white"><span style="color:black">5.1 - Presentation of
<a href="https://community.icann.org/display/gnsocouncilmeetings/Motions+2024-12-19" target="_blank">
<span style="color:#1155cc">Motion</span></a> (Jennifer Chung) </span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">5.2 - Council Discussion </span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">5.3 - Council Vote (voting threshold: affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House)</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 6: COUNCIL DISCUSSION - EPDP Temporary Specification Phase 1, Recommendation 18 - Urgent Requests (15 minutes) </span></b></p>
<p style="margin:0in;background:white"><span style="color:black">ICANN org convened an Implementation Review Team to assist ICANN in implementing the EPDP on the Temporary Specification
<a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-registration-data-specs-final-20feb19-en.pdf" target="_blank">
<span style="color:#1155cc">Phase 1 Final Report</span></a>, which began meeting in May 2019. ICANN org published the draft Registration Data Policy for</span><span style="color:#172b4d">
</span><span style="color:black"><a href="https://www.icann.org/en/public-comment/proceeding/registration-data-consensus-policy-for-gtlds-24-08-2022" target="_blank"><span style="color:#0052cc">public comment</span></a></span><span style="color:#172b4d">
</span><span style="color:black">on 24 August 2022. Several commenters expressed dissatisfaction with the implementation of Recommendation 18, specifically around the issue of the response timeline for urgent requests. The relevant portion of Recommendation
18 reads, “A separate timeline of [less than X business days] will considered for the response to ‘Urgent’ Reasonable Disclosure Requests, those Requests for which evidence is supplied to show an immediate need for disclosure [time frame to be finalized and
criteria set for Urgent requests during implementation].”</span></p>
<p style="margin:0in;background:white"><span style="color:black">On <a href="https://gnso.icann.org/sites/default/files/policy/2024/correspondence/tsinha-to-dibiase-03june24-en.pdf" target="_blank">
<span style="color:#1155cc">3 June 2024</span></a>, the Board wrote to the GNSO Council, noting concerns with the proposed urgent request timeline of business days as not fit for purpose, as truly urgent requests should be responded to within minutes or hours
rather than business days. Recognizing this, the Board also noted there is no universal mechanism for registrars to authenticate law enforcement entities. The GNSO Council responded on
<a href="https://gnso.icann.org/sites/default/files/policy/2024/correspondence/dibiase-to-sinha-29aug24-en.pdf" target="_blank">
<span style="color:#1155cc">29 August 2024</span></a>, agreeing with the Board’s concerns and suggesting a trilateral meeting between the Board, GNSO Council, and GAC to discuss a potential path forward in light of the concerns. </span></p>
<p style="margin:0in;background:white"><span style="color:black">On <a href="https://gac.icann.org/contentMigrated/gac-follow-up-on-urgent-requests-gac-response-to-board-clarifying-question-and-additional-considerations" target="_blank">
<span style="color:#1155cc">15 October 2024</span></a>, the GAC wrote to the Board, recommending, “[f]or the work on authentication, we would support the establishment of a joint PSWG/CPH task force. For the work on the response time for authenticated requests,
we invite the Board and the GNSO Council to identify an expedited procedure for addressing this workstream. We strongly suggest resuming the work of the IRT, which was halted last summer.”</span></p>
<p style="margin:0in;background:white"><span style="color:black">A trilateral meeting was held on
<a href="https://community.icann.org/display/gnsocouncilmeetings/Dialogue+with+GAC%2C+GNSO+Council%2C+and+Board+on+EPDP+Phase+1+Recommendation+18+%28Urgent+Requests%292024-11-04" target="_blank">
<span style="color:#1155cc">4 November 2024</span></a> and the Board, GAC, and GNSO Council discussed next steps, including potentially resuming discussions with the IRT.</span></p>
<p style="margin:0in;background:white"><span style="color:black">Here, the Council will discuss the GAC’s proposal and determine next steps.</span></p>
<p style="margin:0in;background:white"><span style="color:black">6.1 - Introduction of Topic (Greg DiBiase, GNSO Chair)</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">6.2 - Council Discussion</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">6.3 - Next Steps</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 7: COUNCIL DISCUSSION - Request for Guidance from the New gTLD Subsequent Procedures / IDNs EPDP Phase 1 IRT (10 minutes)</span></b></p>
<p style="margin-right:30.0pt;margin-bottom:0in;margin-left:0in;background:white">
<u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">The New gTLD Subsequent Procedures (SubPro) PDP provided a recommendation to allow single character gTLDs in the next round, which was expanded upon by the IDNs EPDP Phase 1 Final Report. The IDNs EPDP Phase 1
Final Report put forth important detail and limitations on the SubPro recommendation, prescribing that the single character gTLDs be limited to the Han script and that relevant guidelines must be developed and put in place by the Chinese, Japanese, and Korean
(CJK) Generation Panels (GPs).</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">In a </span><a href="https://www.icann.org/en/public-comment/proceeding/seeking-input-on-han-script-single-character-idn-generic-top-level-domains-27-06-2024" target="_blank"><span style="color:#1155cc">public comment</span></a><span style="color:black">
proceeding, the CJK GPs noted their opposition to moving forward with single character Han script gTLDs. And in a subsequent
</span><a href="https://www.icann.org/en/public-comment/proceeding/second-proceeding-for-proposed-language-for-draft-sections-of-the-next-round-applicant-guidebook-10-09-2024" target="_blank"><span style="color:#1155cc">public comment</span></a><span style="color:black"> proceeding
on relevant Applicant Guidebook (AGB) sections, a number of commenters also expressed their opposition. </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">This opposition was discussed with the IDN Sub-Track, a sub-track to the SubPro IRT, where it was agreed to not move forward with single character Han script gTLDs. That decision was then discussed with the main
SubPro IRT, where it was determined that this decision should be shared with the GNSO Council. A write-up was shared with the Council on [date].</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">Here, the Council will be briefed on the tentative decision from the SubPro IRT and to discuss the appropriate next steps, if any.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black"> </span></p>
<p style="margin:0in;background:white"><span style="color:black">7.1 - Introduction of Topic (Anne Aikman-Scalese & Susan Payne, Council co-liaisons to the SubPro IRT) </span></p>
<p style="margin:0in;background:white"><span style="color:black">7.2 - Council Discussion</span></p>
<p style="margin:0in;background:white"><span style="color:black">7.3 - Next Steps</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in"><b><span style="color:black">Item 8: COUNCIL UPDATE: EPDP Temporary Specification Phase 1 - Billing Contact (20 minutes) </span></b></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">During the ICANN81<a href="https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up" target="_blank"><span style="color:black">
</span>GNSO Council Wrap-Up</a>, Thomas Rickert provided an update regarding the implementation of EPDP Temp Spec Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the EPDP Temp Spec Phase 1 Implementation Review Team (IRT). Thomas noted
that the IRT expressed the view that the absence of a reference to billing contact data was a drafting error, and the EPDP Team intended for the collection of billing contact data to be optional and not mandatory.</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">The<a href="https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en" target="_blank"><span style="color:black">
</span>Registration Data Policy</a> was published on 21 February 2024, and the policy has an effective date of 21 August 2025. The<a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-registration-data-specs-final-2-20feb19-en.pdf" target="_blank"><span style="color:black">
</span>EPDP Phase 1 policy recommendations</a> do not reference billing contact data, and the
<a href="https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en" target="_blank">
<span style="color:#1155cc">Registration Data Policy</span></a> also makes no reference to billing contact data.</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">In the interest of transparency, Thomas requested that all Councilors consult with their respective groups to ensure that others are properly informed and agree with the interpretation raised
by the registrars within the IRT. Accordingly, Councilors were asked to consult with their groups on the following questions:</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;background:white;vertical-align:baseline">
Does your group believe that billing contact data was in scope for the EPDP Temp Spec policy development? <u></u><u></u></li><li class="MsoNormal" style="color:black;background:white;vertical-align:baseline">
If yes, does your group believe there was a drafting error in the EPDP Phase 1 Final Report because the intention of the recommendations, by not including a recommendation concerning the collection, escrow, etc of billing contact data was that the collection
and retention of billing contact data should be optional and not mandatory? Note: If, as a matter of ICANN Consensus Policy this was the intended outcome, this interpretation would change current contractual requirements for registrars. <u></u><u></u></li></ol>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">Here, the Council will discuss the above questions and determine next steps.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.1 - Introduction of Topic (Greg DiBiase, GNSO Chair) </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.2 - Council Discussion</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.3 - Next Steps</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><b><span style="color:black">Item 9: COUNCIL UPDATE - 2025 Council Strategic Planning Session (SPS) (10 minutes)</span></b></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">The GNSO Council will hold its annual Strategic Planning Session (SPS) in Washington, DC on 14-15 January 2025. </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">The SPS is a dedicated meeting during which the Council will discuss and identify its priorities and goals for the upcoming year. Council Leadership has been developing the agenda, and has identified, <a href="http://et.al" target="_blank">et.al</a>.,
the following themes for discussion: </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">Overview of the Council’s Role and Remit and the Role of Councilors</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;vertical-align:baseline">
Evolution of the Council’s role in managing PDPs, including improvements derived from previous SPS<span style="font-family:"Arial",sans-serif"><u></u><u></u></span></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
Review of work for the upcoming year (including targeted review of project management tools)<u></u><u></u></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
Consideration of recent projects that did not follow the typical path after Council adoption (e.g., delayed implementation, challenges in implementing recommendations)<u></u><u></u></li><li class="MsoNormal" style="color:black;vertical-align:baseline">
Continuous improvement of the GNSO (board readiness, GNSO Standing Committee on Continuous Improvement (SCCI), Five Year Strategic Plan)<u></u><u></u></li></ul>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">Here, the Council will receive an update from Leadership and Support Staff on SPS planning and important information to know ahead of the SPS. </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">9.1 - Introduction of Topic (Greg DiBiase, GNSO Chair)</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">9.2 - Council Discussion</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">9.3 - Next Steps</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><b><span style="color:black">Item 10: DISCUSSION ITEM - Request for Guidance from the Rights Protection Mechanisms (RPMs) PDP IRT on the Scope of Uniform Rapid Suspension (URS) Recommendation 1 (15 minutes)</span></b></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">There are currently diverging views within the Implementation Review Team (IRT) concerning the implementation of the Uniform Rapid Suspension System (URS) Final Recommendation 1 in the RPM PDP Phase 1 Final Report.
Specifically, there is disagreement regarding the scope of amendments to a complaint filed under the URS after the complainant receives the contact information from the URS Provider. As stated in URS Recommendation 1:</span></p>
<p style="margin:0in"><span style="color:black"> </span></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:.5in">
<i><span style="color:black">The Working Group recommends that URS Rule 3(b), and, where necessary, a URS Provider’s Supplemental Rules be amended to clarify that a Complainant must only be required to insert the publicly-available WHOIS/Registration Data Directory
Service (RDDS) data for the domain name(s) at issue in its initial Complaint. </span></i></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:.5in">
<i><span style="color:black"> </span></i></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:.5in">
<i><span style="color:black">Furthermore, the Working Group recommends that URS Procedure paragraph 3.3 be amended to allow the Complainant to update the Complaint within 2-3 calendar days after the URS Provider provides updated registration data related to
the disputed domain name(s). </span></i></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">The draft language currently proposed by some IRT members to
</span><a href="https://docs.google.com/document/d/1dC3BIYxnIb2zZks1AOnrUNEkQJCzi8EKaCAbGMP1MKo/edit" target="_blank"><span style="color:#1155cc">URS Rule 3(b)</span></a><span style="color:black">, which has sparked disagreement within the IRT, pertains to the text in red
below: </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:.5in">
<i><span style="color:black">“Pursuant to URS Procedure Section 3.3, Complainant shall have the opportunity to file an amended Complaint
</span><span style="color:red">limited to adding additional contact details about the Registrant
</span><span style="color:black">following disclosure of the relevant contact details of the Respondent.”</span></i></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">According to some members of the IRT, the scope of amendments to a complaint should be “limited to adding additional contact details about the Registrant” as this is what was intended by URS Recommendation
1, and as such, this should be stated in the proposed amendment to URS Rule 3(b)(iii). Accordingly, these IRT members believe that the amended filing should be limited to including redacted data about the Registrant in the complaint, as this aligns with the
expedited nature of the proceeding. No additional changes or amendments to the complaint should be allowed. </span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">However, other IRT members raised concerns about the current text in red, noting that URS Recommendation 1 does not impose a limit on the scope of possible amendments to the complaint. These IRT
members pointed out that if new information providing greater clarity to a claim becomes available after the party's identity is revealed, the complainant should be permitted to amend the Complaint to include this information. These IRT members believe that
there doesn't seem to be any substantial harm in allowing the complainant to amend the Complaint beyond just putting in the contact details of the registrant. </span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">A staff review of meeting transcripts suggests that the PDP Working Group did not discuss either expanding or limiting the scope of URS Recommendation 1. For further details on the PDP IRT and
original Working Group discussions, see the background document at <a href="https://gnso.icann.org/sites/default/files/policy/2024/draft/staff-summary-rpm-urs-rec1-en.pdf" target="_blank">
<span style="color:black">https://gnso.icann.org/sites/default/files/policy/2024/draft/staff-summary-rpm-urs-rec1-en.pdf</span></a>.</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">The IRT has not come to agreement and the next step, per the IRT
<a href="https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug16-en.pdf" target="_blank">
<span style="color:#467886">Principles and Guidelines</span></a>, is to raise the issue with the GNSO Council liaison. </span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">Here, the Council will receive an introduction to the topic from the GNSO Council Liaison to the IRT.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">10.1 - Introduction of Topic (Susan Payne, GNSO Council Liaison to the IRT)</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">10.2 - Council Discussion</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">10.3 - Next Steps</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 11: COUNCIL DISCUSSION - GNSO Council PR Officer Update (10 minutes)</span></b></p>
<p style="margin-right:30.0pt;margin-bottom:0in;margin-left:0in;background:white">
<u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">During the GNSO Council Strategic Planning Session (SPS) that was held from 14-16 December 2022, the GNSO Council identified the need to enhance its communication efforts to promote its work and outcomes to a
broader audience, as well as to counterbalance negative stories and misinformation about GNSO policy work that seemed to have gained prominence on social media and industry blogs. </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">A </span><a href="https://community.icann.org/display/gnsocouncilmeetings/Communications+Small+Team" target="_blank"><span style="color:#1155cc">GNSO Council small team</span></a><span style="color:black"> was formed in April
2023 to develop a </span><a href="https://gnso.icann.org/sites/default/files/policy/2024/draft/gnso-council-communications-small-team-final-report-26feb24-en.pdf" target="_blank"><span style="color:#1155cc">strategic communications plan</span></a><span style="color:black">
for the GNSO Council. Within its report, the small team put forward two substantive recommendations for new mechanisms to enhance GNSO Council’s communications practice: 1) appoint a member in the GNSO Council to serve as the “PR officer” to guide / support
policy staff in implementing the communications strategy and proposed improvements; and 2) establish a LinkedIn page for the GNSO Council. </span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">Following the first recommendation, Lawrence Olawale-Roberts agreed to assume the role of PR Officer.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">Here, the Council will hear an update from Lawrence Olawale-Roberts on his work in this role.</span></p>
<p style="margin:0in;background:white"><span style="color:black">11.1 - Introduction of Topic (Lawrence Olawale-Roberts, GNSO Council PR Officer) </span></p>
<p style="margin:0in;background:white"><span style="color:black">11.2 - Council Discussion</span></p>
<p style="margin:0in;background:white"><span style="color:black">11.3 - Next Steps</span></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in"><b><span style="color:black">Item 12: Any Other Business (5 minutes)</span></b></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">12.1 - GNSO Liaison to the GAC update</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">12.2 - ICANN82 - funded travel emails were sent out, please action as past deadline</span></p>
<p style="margin:0in;background:white"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"> </span><span style="color:black">_______________________________</span></p>
<p style="margin:0in"><span style="color:black">Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))</span></p>
<p style="margin:0in"><span style="color:black">See</span><a href="https://www.icann.org/resources/pages/governance/bylaws-en/#article11" target="_blank"><span style="color:black">
</span><span style="color:#1155cc">https://www.icann.org/resources/pages/governance/bylaws-en/#article11</span></a><span style="color:black">.</span></p>
<p style="margin:0in"><span style="color:black">Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)</span></p>
<p style="margin:0in"><span style="color:black">See </span><a href="https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-15mar23-en.pdf" target="_blank"><span style="color:#1155cc">https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-15mar23-en.pdf</span></a><span style="color:black"> </span></p>
<p style="margin:0in"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"> </span></p>
<p style="margin:0in"><b><span style="color:black">References for Coordinated Universal Time of 21:00 UTC</span></b><span style="color:black"> </span></p>
<p style="margin:0in"><span style="color:black">Local time between March and November in the NORTHERN hemisphere</span></p>
<p style="margin:0in"><span style="color:black">See </span><a href="https://www.timeanddate.com/time/change/" target="_blank"><span style="color:#1155cc">https://www.timeanddate.com/time/change/</span></a><span style="color:black"> for Dates for Daylight Saving Time and Clock
Changes</span></p>
<p style="margin:0in"><span style="color:black">----------------------------------------------------------------------------</span></p>
<p style="margin:0in"><span style="color:black">California, USA (PDT) UTC-8 13:00 </span></p>
<p style="margin:0in"><span style="color:black">San José, Costa Rica (CST) UTC-6 15:00 </span></p>
<p style="margin:0in"><span style="color:black">New York/Washington DC, USA (EDT) UTC-5 16:00</span></p>
<p style="margin:0in"><span style="color:black">Buenos Aires, Argentina (ART) UTC-3 18:00</span></p>
<p style="margin:0in"><span style="color:black">Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00</span></p>
<p style="margin:0in"><span style="color:black">Paris, France (CEST) UTC+1 22:00</span></p>
<p style="margin:0in"><span style="color:black">Moscow, Russia (MSK) UTC+3 00:00 (Friday)</span></p>
<p style="margin:0in"><span style="color:black">Singapore (SGT) UTC+8 05:00 (Friday)</span></p>
<p style="margin:0in"><span style="color:black">Melbourne, Australia (AEST) UTC+11 08:00 (Friday)</span></p>
<p style="margin:0in"><span style="color:black">----------------------------------------------------------------------</span></p>
<p style="margin:0in"><span style="font-size:10.5pt;font-family:Roboto;color:#172b4d;background:white">For other places see</span><a href="http://www.timeanddate.com/" target="_blank"><span style="font-size:10.5pt;font-family:Roboto;color:#0052cc;background:white"> http://www.timeanddate.com</span></a><span style="font-size:10.5pt;font-family:Roboto;color:#172b4d;background:white">
and </span><a href="https://tinyurl.com/ybse6rda" target="_blank"><span style="color:#1155cc">https://tinyurl.com/ybse6rda</span></a><span style="color:black">.</span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
council mailing list -- <a href="mailto:council@icann.org" target="_blank">council@icann.org</a><br>
To unsubscribe send an email to <a href="mailto:council-leave@icann.org" target="_blank">council-leave@icann.org</a><br>
<br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</div></div></div>