<div dir="auto"><div>FYI</div><div><br></div><div data-smartmail="gmail_signature">Remain blessed, <br>Tomslin</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Devan Reed via council</strong> <span dir="auto"><<a href="mailto:council@icann.org">council@icann.org</a>></span><br>Date: Sat, 3 May 2025, 05:08<br>Subject: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 15 May 2025<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>>, <a href="mailto:liaison6c@icann.org">liaison6c@icann.org</a> <<a href="mailto:liaison6c@icann.org">liaison6c@icann.org</a>><br>Cc: GNSO-Secs <<a href="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a>><br></div><br><br>
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="m_-4864273215111111698WordSection1">
<p class="MsoNormal"><span style="color:black">Dear all,<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span style="color:black">Please find below the agenda for the GNSO Council Meeting on 15 May 2025 at 05:00 UTC. This will be posted on the<span class="m_-4864273215111111698apple-converted-space"> </span><a href="https://icann-community.atlassian.net/wiki/x/GKafBg" target="_blank" rel="noreferrer">agenda wiki
page </a>shortly.<u></u><u></u></span></p>
<p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px">
<span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Thank you.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Kind regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black">Devan<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black;background:white">Policy Team Supporting the GNSO</span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin-right:0in;margin-bottom:6.0pt;margin-left:0in">
<b><span style="font-size:23.0pt;color:black">GNSO Council Agenda 15 May 2025</span></b><u></u><u></u></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://icann-community.atlassian.net/wiki/x/0KefBg" target="_blank" rel="noreferrer"><span style="color:#1155cc">https://icann-community.atlassian.net/wiki/x/0KefBg</span></a><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black"> </span><u></u><u></u></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" rel="noreferrer"><span style="color:#1155cc"> GNSO Operating Procedures</span></a><span style="color:black">
v3.5, updated on 15 March 2023.</span><u></u><u></u></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 style="color:black;margin-top:0in;margin-bottom:0in;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 style="color:black;margin-top:0in;margin-bottom:0in;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 class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black"> GNSO Council meeting on Thursday, 15 May 2025 at 05:00 UTC:
</span><a href="https://tinyurl.com/knke3w" target="_blank" rel="noreferrer"><span style="color:#1155cc">https://tinyurl.com/knke3w</span></a><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">22:00 Los Angeles(Wednesday); 01:00 Washington DC; 06:00 London; 07:00 Paris; 08:00 Moscow; 15:00 Melbourne</span><u></u><u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black"> </span></b><u></u><u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">GNSO Council Meeting Remote Participation:<span style="background:white">
</span></span><span style="color:blue"><a href="https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1" target="_blank" rel="noreferrer">https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1</a></span></b><u></u><u></u></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><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">___________________________________</span><u></u><u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 1: Administrative Matters (5 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black">1.1 - Roll Call</span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black">1.2 - Updates to Statements of Interest</span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black">1.3 - Review / Amend Agenda</span><u></u><u></u></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><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black"><a href="https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso-council-12mar25-en.pdf" target="_blank" rel="noreferrer"><span style="color:#1155cc">Minutes</span></a> of the GNSO Council Meeting on 12 March
2025 were posted on 01 April 2025</span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black"><a href="https://gnso.icann.org/sites/default/files/policy/2025/transcript/transcript-gnso-council-10apr25-en.pdf" target="_blank" rel="noreferrer"><span style="color:#1155cc">Minutes</span></a> of the GNSO Council Meeting on
10 April 2025 were posted on 24 April 2025</span><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 2: Opening Remarks / Review of Projects & Action List (5 minutes)</span></b><u></u><u></u></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" rel="noreferrer"><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" rel="noreferrer"><span style="color:#172b4d">
</span><span style="color:#0052cc">Action Item List. </span></a></span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black"> </span><u></u><u></u></p>
<p style="margin:0in;background:white"><b><span style="color:black">Item 3: Consent Agenda (5 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:#172b4d;margin-top:8.0pt;margin-bottom:0in;background:white;vertical-align:baseline">
<span style="color:black">Aspirational Statement</span><span style="font-size:10.5pt;font-family:Roboto"><u></u><u></u></span></li></ul>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in;background:white">
<b><span style="color:black">Item 4: COUNCIL VOTE - Deferral of the Next Steps of Phase Two of the Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP)</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#79726c;background:white">
</span><b><span style="color:black">for an Additional Six Months (20 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:#292a2e">The</span><span style="font-size:10.5pt;font-family:"Helvetica Neue";color:#292a2e">
</span><span style="color:black">Review of All Rights Protection Mechanisms (RPMs) in All New gTLDs Policy Development Process (PDP) was chartered to be conducted in two phases: Phase One focused on a review of all the RPMs that were developed for the 2012
New gTLD Program, and Phase Two will focus on issues identified in respect of the Uniform Dispute Resolution Policy (UDRP).</span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black">Following the ICANN Board’s approval of the Phase 1 recommendations in January 2022, the GNSO Council discussed delaying Phase Two of the RPMs PDP until the completion of key milestones for the
Implementation Review Team, once launched. The Phase One IRT was launched in December 2022 with a projected end date of December 2024. During its meeting on
<a href="https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/111103308/Final+Proposed+Agenda+2023-02-16" target="_blank" rel="noreferrer">
<span style="color:#1155cc">16 February 2023</span></a>, the GNSO Council agreed to defer next steps on the RPMs PDP Phase Two for 18 months.</span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black">In October 2024, GNSO support staff advised the GNSO Council leadership of staff estimates that the implementation of RPMs Phase One would be delayed until the third quarter of 2025. In light
of this, the Council voted to defer the next steps on Phase Two for an additional six months. Following the direction of the Councilors who reviewed the progress to date, the Council is voting to defer the consideration of next steps for Phase 2 for an additional
six months. </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">4.1 - Introduction of Topic (Susan Payne, GNSO Councilor) </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">4.2 - Council Vote (voting threshold: simple majority)</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">4.3 - Next Steps</span><u></u><u></u></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 DISCUSSION - Han Script Character gTLDs (Recommendation 3.17) (20 minutes) </span></b><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black">The New gTLD Subsequent Procedures (SubPro) PDP provided Recommendation 25.4 (approved by the ICANN Board) to allow single character gTLDs for ideographic scripts in the next round,
<b>provided that they do not introduce confusion risks that rise above commonplace similarities.</b> The IDNs EPDP Phase 1 Final Report put forth important additional detail and limitations on 25.4, prescribing that the single character gTLDs
<u>be limited to the Han script</u> and that <b>applications must not be accepted until relevant guidelines are developed and put in place by the Chinese, Japanese, and Korean (CJK) Generation Panels (GPs).
</b>Alternatively, the IDN EPDP concluded that if the CJK GPs determine that additional guidelines beyond the RZ-LGR are not needed, then the single character applications should proceed.</span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black">The matter was put out for public comment by the CJK Generation Panels. Although the CJK GPs
</span><a href="https://www.icann.org/en/system/files/files/proposed-han-script-single-character-gtld-considerations-27jun24-en.pdf" target="_blank" rel="noreferrer"><span style="color:#1155cc">stated</span></a><span style="color:black"> that the work done in the Root Zone Label Generation
Rules (</span><a href="https://www.icann.org/resources/pages/root-zone-lgr-2015-06-21-en" target="_blank" rel="noreferrer"><span style="color:#1155cc">RZ-LGRs</span></a><span style="color:black">) sufficiently addresses the concerns around the risk of confusion for single character Han script
gTLDs, the majority of the </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" rel="noreferrer"><span style="color:#1155cc">public comments</span></a><span style="color:black">
on the CJK GPs’ statements opposed moving forward. Some commenters from the Chinese community expressed concerns about the lack of alignment with China’s linguistic laws and regulations, the complexities of Chinese character ideographs, and end-user confusion
due to multiple meanings of many single characters. One such comment received from a co-Chair of the CGP argues that the CGP should not be and was not involved in "risk of confusion" policy considerations related to single Han characters as TLDs. Many of the
comments call for further community work prior to proceeding. Similar concerns were received through the
</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" rel="noreferrer"><span style="color:#1155cc">public comment</span></a><span style="color:black"> on
the relevant draft AGB sections.</span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black">This public comment was discussed with the Sub Pro IRT IDN Sub-Track which referred the matter to the main SubPro IRT. The main SubPro IRT was asked by ICANN staff whether Recommendation 25.4 should be modified as not implementable
or whether the issue should be reviewed with Council for possible further work. It was agreed that the Liaisons should raise this with Council for direction on next steps. A
</span><a href="https://lists.icann.org/hyperkitty/list/council@icann.org/message/GLJ5RIOKH3I3FS5P6NE2Y4IGUTV5I4B7/" target="_blank" rel="noreferrer"><span style="color:#1155cc">background document</span></a><span style="color:black"> prepared by Lars Hoffmann was shared with the Council on
December 9.</span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black">The Council Liaisons to the IRT suggesting referring the issue to a GNSO Guidance Process (GGP) to determine the guidance necessary to allow Han single characters to proceed, with an acknowledgement that the GGP could well determine
that Recommendation 25.4 and IDN EPDP recommendation 3.17 as approved may not be implementable. Due to time constraints, and the fact that both the SubPro and IDNs recommendations were conditional, the Liaisons believe that the recommended GGP process should
not hold up the next round. During Council deliberations, some Councilors suggested an Expert Working Group (EWG), as an alternative to the GGP. Staff provided an update to the Council during its April meeting where an additional mechanism was identified
- the External Expert Advice (EEA) process as captured in Article 13 of the ICANN Bylaws.</span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black"> Following the Council’s April meeting, GNSO support staff provided an analysis of the potential options to address this issue, the GGP,the EWG, and the EEA. </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">Here, the Council will discuss the next steps for Han Script Character gTLDs. </span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:black">5.1 - Introduction of Topic<span style="background:white"> (Greg DiBiase, GNSO Chair)</span></span><u></u><u></u></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><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:black">5.3 - Next Steps</span><u></u><u></u></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 - Council Alignment on the Future of Reviews (30 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:#fefefe"><span style="color:#333333">ICANN created Specific Reviews in 2009 as a way to measure how it was meeting its commitments in four specific areas: Accountability and Transparency; Security, Stability, and Resiliency of
the Domain Name System; Registration Directory Service; and Competition, Consumer Trust, and Consumer Choice. These reviews were incorporated into ICANN's Bylaws in 2016.</span><u></u><u></u></p>
<p style="margin:0in;background:#fefefe"><span style="color:#333333">Specific Reviews are led by community review teams and operate according to
</span><span style="color:black"><a href="https://www.icann.org/resources/pages/governance/bylaws-en#article4.6" target="_blank" rel="noreferrer"><span style="color:#047bc1">Section 4.6</span></a></span><span style="color:#333333"> of the ICANN Bylaws and the Operating Standards for Specific
Reviews. Upon completion of a review, the Board assesses the results and considers recommendations accordingly. </span><u></u><u></u></p>
<p style="margin:0in;background:#fefefe"><span style="color:#333333">With exception of the Competition, Consumer Trust and Consumer Choice review that is conducted “After a New gTLD Round has been in operation for one year”, Specific Reviews are conducted “no
less frequently than every five years”, measured from the date the previous review effort was convened.</span><u></u><u></u></p>
<p style="margin:0in;background:#fefefe"><span style="color:#333333;background:white">The Accountability and Transparency Review Team 3 (ATRT3) recommended the establishment of a new Specific Review, the Holistic Review, to examine the continuous improvement,
effectiveness, and accountability of the ICANN community structures as well as the collaboration among them. A
</span><span style="color:black"><a href="https://community.icann.org/display/PHR" target="_blank" rel="noreferrer"><span style="color:#0098d5;background:white">Pilot Holistic Review Team</span></a></span><span style="color:#333333;background:white"> was convened to develop the guidelines
and methodologies for the future Holistic Review, recommended by the ATRT3. </span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:.25in;margin-left:0in;background:#fefefe">
<span style="color:black">Following an introduction of the topic, the Council will discuss the potential options going forward, including:</span><u></u><u></u></p>
<ul style="margin-top:0in" type="disc">
<li style="color:black;margin-top:0in;margin-bottom:0in;background:#fefefe;vertical-align:baseline">
Status Quo: Continue on the current path, kick off ATRT4 and bifurcate out the Pilot Holistic Review (structural review) and the Continuing Improvement process.<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:0in;background:#fefefe;vertical-align:baseline">
Change Option 1: Repurpose ATRT4 to have it undertake the structural review, and as a result wind down the Pilot Holistic Review (with the Continuing Improvement process independent and functioning).<u></u><u></u></li><li style="color:black;margin-top:0in;margin-bottom:.25in;background:#fefefe;vertical-align:baseline">
Change Option 2: Suspend all reviews and kick off a Review of Reviews to determine what reviews are necessary at this time (including a structural review).<u></u><u></u></li></ul>
<p style="margin:0in;background:#fefefe"><span style="color:black">Here, the Council will consider these options and determine which, if any, is most supported by councilors. </span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black">6.1 - Introduction of Topic (<span style="background:white">Paul McGrady, GNSO Councilor</span>) </span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black">6.2 - Council Discussion</span><u></u><u></u></p>
<p style="margin-right:0in;margin-bottom:0in;margin-left:0in">
<span style="color:black">6.3 - Next Steps</span><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in"><b><span style="color:black">Item 7: COUNCIL UPDATE: Subsequent Procedures Implementation Review Team on Recommendation 36.4 (20 minutes)</span></b><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:#292a2e">On 16 March 2023, the ICANN Board
</span><span style="color:black"><a href="https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-action-16mar23-en.pdf" target="_blank" rel="noreferrer"><span style="color:#1155cc">adopted</span></a></span><span style="color:#292a2e">, et al., Recommendation 36.4 of the Subsequent
Procedures PDP. </span><u></u><u></u></p>
<p style="margin:0in;background:white"><span style="color:#292a2e">Recommendation 36.4 provides: ICANN must add a contractual provision stating that the registry operator will not engage in fraudulent or deceptive practices. In the event that ICANN receives
an order from a court that a registry has engaged in fraudulent or deceptive practices, ICANN may issue a notice of breach for such practices and allow the registry to cure such breach in accordance with the Registry Agreement. Further, in the event that there
is a credible allegation by any third party of fraudulent or deceptive practices, other than as set forth in above, ICANN may, at its discretion, either commence dispute resolution actions under the Registry Agreement (Currently Article 5 of the Registry Agreement),
or appoint a panel under the PICDRP. For the purposes of a credible claim of fraudulent or deceptive practices the reporter (as defined by the PICDRP) must only specifically state the grounds of the alleged non-compliance, but not that it personally has been
harmed as a result of the registry operator’s act or omission.</span><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p style="margin:0in;background:white"><span style="color:#292a2e">Here, the Council liaisons to the SubPro Implementation Review Team would like to discuss concerns regarding the proposed implementation of Recommendation 36.4. </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">7.1 - Introduction of Topic (Anne Aikman-Scalese and Susan Payne, Council Liaisons to SubPro IRT) </span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">7.2 - Council Discussion</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">7.3 - Next Steps</span><u></u><u></u></p>
<p style="margin:0in;background:white"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><b><span style="color:black">Item 8: Any Other Business (15 minutes)</span></b><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.1 - ICANN83 Planning</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.2 - ccNSO and GAC Liaison updates</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.3 - Whois Implementation Advisory Group update</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.4 - Registration Data Request Service (RDRS) Standing Committee Report - open question of public comment</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="color:black">8.5 - Chair update</span><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p style="margin:0in"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"> </span><span style="color:black">_______________________________</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))</span><u></u><u></u></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" rel="noreferrer"><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><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)</span><u></u><u></u></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" rel="noreferrer"><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><u></u><u></u></p>
<p style="margin:0in"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:black"> </span><u></u><u></u></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><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Local time between March and November in the NORTHERN hemisphere</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">See </span><a href="https://www.timeanddate.com/time/change/" target="_blank" rel="noreferrer"><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><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">----------------------------------------------------------------------------</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">California, USA (PDT) UTC-7 22:00 (Wednesday)</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">San José, Costa Rica (CST) UTC-6 23:00 (Wednesday)</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">New York/Washington DC, USA (EDT) UTC-4 01:00</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Buenos Aires, Argentina (ART) UTC-3 02:00</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:00</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Paris, France (CEST) UTC+2 07:00</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Moscow, Russia (MSK) UTC+3 08:00</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Singapore (SGT) UTC+8 13:00</span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">Melbourne, Australia (AEST) UTC+10 15:00 </span><u></u><u></u></p>
<p style="margin:0in"><span style="color:black">----------------------------------------------------------------------</span><u></u><u></u></p>
<p class="MsoNormal"><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" rel="noreferrer"><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/knke3w" target="_blank" rel="noreferrer"><span style="color:#1155cc">https://tinyurl.com/knke3w</span></a><u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
council mailing list -- <a href="mailto:council@icann.org" target="_blank" rel="noreferrer">council@icann.org</a><br>
To unsubscribe send an email to <a href="mailto:council-leave@icann.org" target="_blank" rel="noreferrer">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 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 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>