<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:736392613;
mso-list-template-ids:849911620;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1411078665;
mso-list-template-ids:-1566930342;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:2047945895;
mso-list-template-ids:1992215180;}
@list l2:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Here’s the Policy Calendar for the BC Open meeting at 10:45 local time on 13-Jun at ICANN 77 (also in attachment “policy calendar.pdf”)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-right:.5in;layout-grid-mode:char"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-right:.5in"><b><span style="font-size:12.0pt;color:black">Channel 1. BC participation in ICANN Public Comment process:</span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">On 12-Jun we will file the attached comment on the
</span><a href="https://www.icann.org/en/public-comment/proceeding/bylaws-amendments-and-documents-to-implement-the-nomcom2-review-17-04-2023"><span style="font-size:12.0pt">NomCom2 Review</span></a><span style="font-size:12.0pt">, thanks to Tola and Lawrence
for the attached comment.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">On 31-May we US Government’s NTIA
</span><a href="https://www.ntia.doc.gov/sites/default/files/publications/ustld_whois_federal_register_notice_5.1.23.pdf" title="https://www.ntia.doc.gov/sites/default/files/publications/ustld_whois_federal_register_notice_5.1.23.pdf"><span style="font-size:12.0pt">proposal
for new restrictions on .US WHOIS access</span></a><span style="font-size:12.0pt">. The reason is to harmonize .US policy with GDPR-imposed limits on WHOIS in other TLDs. Thanks to Mason Cole for drafting.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">On 25-May we
</span><a href="https://cbu.memberclicks.net/assets/docs/positions-statements/2023/2023_05May_25_BC%20comment%20on%20.NET%20renewal.pdf"><span style="font-size:12.0pt">commented</span></a><span style="font-size:12.0pt"> on
<span style="color:#212121">the </span></span><a href="https://www.icann.org/en/public-comment/proceeding/proposed-renewal-of-the-registry-agreement-for-net-13-04-2023"><span style="font-size:12.0pt">proposed renewal of the .NET registry agreement</span></a><span style="font-size:12.0pt;color:#212121">.
Thanks to Margie, Zak, and Steve for drafting. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">Selected </span></b><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments&d=DwMF-g&c=XRWvQHnpdBDRh-yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=eKUxmgsVmOm8t0ie_17sBbRQFRMaduKLJTinJPAvqdE&m=o1SLHX1vEYfZll6yBO9E5SreRFCCNjqdZtU0P9FiqYs&s=_xntw_JLqOIYVKJSg-pBJpPEW53zw0kQVPHoTYP3la4&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments&d=DwMF-g&c=XRWvQHnpdBDRh-yzrHjqLpXuHNC_9nanQc6pPG_SpT0&r=eKUxmgsVmOm8t0ie_17sBbRQFRMaduKLJTinJPAvqdE&m=o1SLHX1vEYfZll6yBO9E5SreRFCCNjqdZtU0P9FiqYs&s=_xntw_JLqOIYVKJSg-pBJ"><b><span style="font-size:12.0pt">ICANN
Public Comments</span></b></a><b><span style="font-size:12.0pt;color:black"> and other opportunities for the BC to comment: </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">1. Phase 1 Initial Report on the Internationalized Domain Names (IDN) EPDP (</span><a href="https://www.icann.org/en/public-comment/proceeding/phase-1-initial-report-on-the-internationalized-domain-names-epdp-24-04-2023"><span style="font-size:12.0pt">comment
page</span></a><span style="font-size:12.0pt">). Comments close 19-Jun.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt">The PDP WG seeks input on
</span><a href="https://itp.cdn.icann.org/en/files/internationalized-domain-names-idn/phase-1-initial-report-internationalized-domain-names-expedited-policy-development-process-24-04-2023-en.pdf"><span style="font-size:12.0pt">prelim recommendations</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt;color:#212121;background:yellow">Thanks to Ching Chiao for drafting our comment.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt;color:#212121;background:yellow">Steve circulated Ching’s draft on 29-May, incl Ching’s report from the ICANN webinar, and discussion of prior BC positions.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt;color:#212121;background:yellow">Let’s discuss any remaining edits
</span><span style="font-size:12.0pt;color:black;background:yellow">at</span><span style="font-size:12.0pt;color:#212121;background:yellow"> our
</span><span style="font-size:12.0pt;color:black;background:yellow">13</span><span style="font-size:12.0pt;color:#212121;background:yellow">-Jun
</span><span style="font-size:12.0pt;color:black;background:yellow">meeting</span><span style="font-size:12.0pt;color:#212121;background:yellow">.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">2. ISPCP constituency charter amendments (</span><a href="https://www.icann.org/en/public-comment/proceeding/ispcp-constituency-charter-amendments-09-05-2023"><span style="font-size:12.0pt">comments
page</span></a><span style="font-size:12.0pt">). Comments close 26-Jun.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">See their proposed
</span><a href="https://itp.cdn.icann.org/en/files/policy-development/amended-ispcp-constituency-charter-09-05-2023-en.pdf"><span style="font-size:12.0pt">amended charter</span></a><span style="font-size:12.0pt">.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;background:yellow;mso-highlight:yellow">Thanks to Zak for drafting the attached BC comment</span><span style="font-size:12.0pt">.<span style="color:#212121;background:yellow"> Let’s
discuss at our </span><span style="color:black;background:yellow">13</span><span style="color:#212121;background:yellow">-Jun
</span><span style="color:black;background:yellow">meeting</span></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">3. PTI/IANA Governance Proposal. (</span><a href="https://www.icann.org/en/public-comment/proceeding/pti-iana-governance-proposal-16-05-2023"><span style="font-size:12.0pt">comments
page</span></a><span style="font-size:12.0pt">). Comments close 5-Jul. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">PTI Bylaws amendments include:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Modify timing for initial delivery of PTI Operating Plan & Budget, to a 90-day window.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Moving PTI from a 4-year strategic planning cycle to a 5-year strategic planning cycle, to align with ICANN’s 5-year strategic planning.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">In Nov-2022 we
</span><a href="https://cbu.memberclicks.net/assets/docs/positions-statements/2022/2022_11November_16_BC%20Comment%20on%20RDAP%20Amendment%20RAA%20and%20RyA.pdf"><span style="font-size:12.0pt">commented</span></a><span style="font-size:12.0pt"> on the FY2024
PTI budget, thanks to Crystal Ondo, Rajiv Prasad, and Margie Milam.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;background:yellow;mso-highlight:yellow">Thanks to Rajiv for volunteering to draft this BC comment</span><span style="font-size:12.0pt">.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">4. </span>
<a href="https://www.icann.org/en/public-comment/proceeding/amendments-base-gtld-ra-raa-modify-dns-abuse-contract-obligations-29-05-2023"><span style="font-size:12.0pt">Amendments to the Base gTLD RA and RAA to Modify DNS Abuse Contract Obligations</span></a><span style="font-size:12.0pt">.
Comments close 13-Jul. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">These draft agreements were </span><a href="https://www.icann.org/en/announcements/details/amendments-to-the-base-gtld-ra-and-raa-to-modify-dns-abuse-contract-obligations-29-05-2023-en" title="https://www.icann.org/en/announcements/details/amendments-to-the-base-gtld-ra-and-raa-to-modify-dns-abuse-contract-obligations-29-05-2023-en"><span style="font-size:12.0pt">published</span></a><span style="font-size:12.0pt"> last
week, incl this new obligation for Registrars: </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">“When Registrar has actionable evidence that a Registered Name sponsored by Registrar is being used for DNS Abuse, Registrar must promptly take the appropriate mitigation action(s)
that are reasonably necessary to stop, or otherwise disrupt, the Registered Name from being used for DNS Abuse. Action(s) may vary depending on the circumstances, taking into account the cause and severity of the harm from the DNS Abuse and the possibility
of associated collateral damage.”</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;background:yellow;mso-highlight:yellow">We need volunteer(s) to draft a BC comment</span><span style="font-size:12.0pt">,
<span style="background:yellow;mso-highlight:yellow">and we should discuss during ICANN77.</span></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">5. See
<a href="https://community.icann.org/display/GFDOCG/Draft+Framework+for+Closed+Generic+gTLDs?preview=/244944418/244944420/Draft%20Framework%20for%20Closed%20Generic%20gTLDs.pdf">
Draft Framework</a> for closed generic gTLDs. Comments will close 15-Jul and </span>
<span lang="EN-GB" style="font-size:12.0pt">we expect a(n) (E)PDP.</span><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">GNSO, GAC, and ALAC drafted “a workable framework to identify and handle closed generic applications for the immediate next round of new gTLDs”. The framework discussion will focus
on options other than the two endpoint positions (i.e. no closed generics at all; closed generics without restrictions)
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;color:black">Prior BC positions on closed generic go back to our comments during the 2012 round of gTLD expansion. To summarize:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><b><span style="font-size:12.0pt;color:black">The BC would be concerned about consumer deception and competitor exclusion if a single competitor in an industry manages a closed TLD where the TLD string is closely
identified with the industry. </span></b><b><span style="font-size:12.0pt"> </span>
</b><span style="font-size:12.0pt;color:black">For example, </span><span style="font-size:12.0pt">say<span style="color:black"> a travel company or a hotel chain run</span>s<span style="color:black"> <b>.HOTELS</b> as a closed TLD -- not allowing competitors
to register second level names, while also controlling content on domains such as search.hotels, eco.hotels, family.hotels, best.hotels, cheap.hotels, luxury.hotels, etc. It’s easy to see how the TLD owner could bias content and search results on those consumer
information sites, without consumers being fully aware.<o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt"> <span style="background:yellow;mso-highlight:yellow">The draft includes this principle, relevant to prior BC position:<o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt;background:yellow;mso-highlight:yellow">“Purpose og gTLD must not be to solely exclude other parties from using the gTLD or to serve the applicant’s own commercial interests”</span><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">On 25-May Council discussed the </span><a href="https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-policy-vehicle-closed-generics-15may23.pdf"><span style="font-size:12.0pt">draft
scope</span></a><span style="font-size:12.0pt"> of subsequent policy work to inform preparation of the timeline for this work.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">6. NIS2, followed closely by Andrew Bennett, Nik Lagergren, and Marie Pattullo.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">In The Hague we talked with </span><a href="https://en.wikipedia.org/wiki/Bart_Groothuis" title="https://en.wikipedia.org/wiki/Bart_Groothuis"><span style="font-size:12.0pt">MEP Bart
Groothuis</span></a><span style="font-size:12.0pt"> about NIS2 and next steps.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><a href="https://www.europarl.europa.eu/doceo/document/A-9-2021-0313-AM-281-281_EN.pdf" title="https://www.europarl.europa.eu/doceo/document/A-9-2021-0313-AM-281-281_EN.pdf"><span style="font-size:12.0pt">NIS2 final
text</span></a><span style="font-size:12.0pt"> approved by European Parliament on 10-Nov, and by Council on 28-Nov.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">final text
</span><a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L:2022:333:FULL&from=EN"><span style="font-size:12.0pt">published on 27-Dec</span></a><span style="font-size:12.0pt"> (p.82), giving 21-months for Member States to transpose into national
law.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">BC will advocate for strong transposition by Member States.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">Channel 2. Support for discussion and votes of our representatives on GNSO Council</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Marie Pattullo and Mark Datysgeld are our GNSO Councilors. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Previous Council meeting was 25-May. See . </span><a href="https://community.icann.org/x/yoBXDg"><span style="font-size:12.0pt">Agenda</span></a><span style="font-size:12.0pt">,
</span><a href="https://icann.zoom.us/rec/play/9Xe19OH79-nipAAgK39Fem3ghqWjneuD2DDB-rlfazStiWX8GU6dSyDcKVd4QfbSja0k1sYpYP1L6sRb.cEL8cVPmawdTMSwy"><span style="font-size:12.0pt">Audio Recording</span></a><span style="font-size:12.0pt">,
</span><a href="https://gnso.icann.org/sites/default/files/policy/2023/transcript/transcript-gnso-council-20apr23-en.pdf"><span style="font-size:12.0pt">Transcript</span></a><span style="font-size:12.0pt">,
</span><a href="https://icann.zoom.us/rec/share/7pSQ37mSB5wGz8-msQS2PDpzhQ6VdJQISm2SYmWKwfFMWFM_Z6FdMsFiipNyIV-E.J55mm5SBjoZJS9d9?startTime=1684990882000"><span style="font-size:12.0pt">Zoom recording</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">Council did not vote on any resolutions.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">Council discussed ICANN Board </span><a href="https://www.icann.org/en/system/files/correspondence/sinha-to-ducos-26apr23-en.pdf"><span style="font-size:12.0pt">request for</span></a><span style="font-size:12.0pt"> GNSO
Council views on the issue of NomCom rebalancing. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">The ICANN community has been discussing the issue of rebalancing the NomCom for over 10 years, and the ICANN Board resolved to engage with the ICANN community to better understand
community views on the rebalancing.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Specifically, the Board is seeking input on the following questions:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt">What does it mean to have a balanced NomCom at a point in time? For example, what criteria would you apply to measure or assess whether the NomCom is balanced? And further, how can one test whether or not
the NomCom is balanced?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt">Do you support the view that the current composition of the NomCom needs to be rebalanced? Please explain why or why not.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt">How frequently does the balance need to be measured or assessed?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt">How do you suggest that the NomCom’s composition be rebalanced?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt">Who should conduct this work, and how should it be conducted?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span style="mso-list:Ignore">6.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt">How would your community group prioritize consideration of this issue within your planning efforts? </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Here, the Council will discuss the questions from the Board and determine whether it would like to provide input.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">Council discussed the </span><a href="https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-policy-vehicle-closed-generics-15may23.pdf"><span style="font-size:12.0pt">draft
scope</span></a><span style="font-size:12.0pt"> of subsequent policy work on closed generics in next round.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">Council received an update from EPDP Phase 2 small team on progress defining the </span><a href="https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-proposed-success-15may23-en.pdf"><span style="font-size:12.0pt">success
criteria of the RDRS.</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;background:yellow;mso-highlight:yellow">Next Council meeting is 14-Jun at ICANN 77
<span style="color:black">at 17:45</span> UTC</span><span style="font-size:12.0pt">/ 13:45 Washington time. </span><a href="https://community.icann.org/x/zIBXDg"><span style="font-size:12.0pt">Agenda</span></a><span style="font-size:12.0pt"> includes:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt">Item 3: Motion to Commemorate
<span style="background:yellow;mso-highlight:yellow">Pam Little</span></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt">Item 4: Timelines for SubPro. Council will acknowledge the work plans and timelines for:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">the pending recommendations,
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">IDNs EPDP Phase 2, and
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">closed generics EPDP</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt">Item 5: DNS Abuse small team discussion</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt">Item 6: Discuss Whois Accuracy scoping team recommendations.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="font-size:12.0pt">Item 7: we’ll have another go at the
</span><a href="https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2023-06-14"><span style="font-size:12.0pt">GNSO Town Hall experiment</span></a><span style="font-size:12.0pt">.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt">It’s an
<span style="background:yellow;mso-highlight:yellow">opportunity to raise any topic or input on GNSO work.</span> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt">In addition, Council wants to hear
<span style="background:yellow;mso-highlight:yellow">how to address the recent trend of attrition in GNSO Working Group participation</span> - a topic that was also discussed during the recent GNSO Policy Webinar. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <span style="color:#172B4D;background:white"> </span></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <span style="color:black">Other Council activities:</span></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt;color:#212121">1. <b>Transfer Policy Working Group</b>. (Zak Muscovitch and Arinola Akinyemi).
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt;color:#212121">Working Group looking at Early Input on these topics: (see
</span><a href="https://cbu.memberclicks.net/assets/docs/positions-statements/2023/2023_04April_18_COMMENTS%20ON%20Transfer%20Policy%20Review%20PDP%20-%20Request%20for%20Early%20Input%20on%20Group%202%20Topics.pdf"><span style="font-size:12.0pt">BC input</span></a><span style="font-size:12.0pt;color:#212121">)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in;mso-list:l2 level1 lfo4">
<![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt;color:#212121">Transfer Emergency Action Contact (TEAC) </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in;mso-list:l2 level1 lfo4">
<![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt;color:#212121">Transfer Dispute Resolution Policy (TDRP)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in;mso-list:l2 level1 lfo4">
<![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt;color:#212121">ICANN-approved Transfers </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in;mso-list:l2 level1 lfo4">
<![if !supportLists]><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span><![endif]><span style="font-size:12.0pt;color:#212121">Items raised in the Expedited Policy Development Process Recommendation 27, Wave 1 Report</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.75in"><span style="font-size:12.0pt;color:#212121">Working Group is deliberating a
<b>transfer reversal policy</b> proposed by a WG member (See</span><span lang="EN-CA" style="font-size:12.0pt;color:#212121"> </span><a href="https://docs.google.com/document/d/1Mq-Zu-fTdu4xrI1h1YPB1ITGRTxAp2gKzef7cTkgnNg/edit" title="https://docs.google.com/document/d/1Mq-Zu-fTdu4xrI1h1YPB1ITGRTxAp2gKzef7cTkgnNg/edit"><span lang="EN-CA" style="font-size:12.0pt;color:#0078D7">Transfer
Reversal Gap Analysis</span></a><span lang="EN-CA" style="font-size:12.0pt;color:#212121">).</span><span lang="EN-CA" style="font-size:12.0pt"><br>
<br>
</span><span style="font-size:12.0pt">The latest Transfer Policy issue is a registrant-initiated transfer dispute mechanism. There has been considerable resistance to even the WG recommending in its report, that GNSO consider establishing a PDP to evaluate
the feasibility of this despite us and the At Large forcefully making the case. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">2. <b>
<span style="color:black">GNSO Guidance Process (GGP). </span></b><span style="color:black">(Lawrence Olawale-Roberts).<b>
</b><span class="apple-converted-space"> See</span></span> </span><a href="https://community.icann.org/display/GGPGIRFAS/GNSO+Guidance+Process+%28GGP%29+Initiation+Request+for+Applicant+Support+Home" title="https://community.icann.org/display/GGPGIRFAS/GNSO+Guidance+Process+%28GGP%29+Initiation+Request+for+Applicant+Support+Home"><span style="font-size:12.0pt;color:#0078D7">main
wiki page</span></a><span style="font-size:12.0pt">, </span><a href="https://community.icann.org/display/GGPGIRFAS/Members+and+Mailing+List" title="https://community.icann.org/display/GGPGIRFAS/Members+and+Mailing+List"><span style="font-size:12.0pt;color:#0078D7">Members
and Alternates</span></a><span style="font-size:12.0pt">. <span style="color:black">
BC member Segunfunmi Olajide is an observer.</span></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">3. DNS Abuse small team.
<span style="color:black">Mark Datysgeld serves as co-lead.</span></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;color:#212121">CPH representatives met with ICANN Org for negotiations on RAA and RyA amendments to address DNS Abuse. (</span><a href="https://www.icann.org/en/system/files/correspondence/costerton-to-heineman-15jan23-en.pdf" title="https://www.icann.org/en/system/files/correspondence/costerton-to-heineman-15jan23-en.pdf"><span style="font-size:12.0pt;color:#0078D7">Sally’s
letter</span></a><span style="font-size:12.0pt;color:#212121">). To inform that negotiation, Mason drafted and sent<span class="apple-converted-space"> </span></span><a href="https://www.icann.org/en/system/files/correspondence/cole-et-al-to-sinha-costerton-20jan23-en.pdf" title="https://www.icann.org/en/system/files/correspondence/cole-et-al-to-sinha-costerton-20jan23-en.pdf"><span style="font-size:12.0pt;color:#0078D7">this
letter</span></a><span class="apple-converted-space"><span style="font-size:12.0pt;color:#212121"> </span></span><span style="font-size:12.0pt;color:#212121">from BC, IPC, and ALAC on 23-Jan</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">On 27-Mar the Board
</span><a href="https://www.icann.org/en/system/files/correspondence/sinha-to-cole-et-al-27mar23-en.pdf"><span style="font-size:12.0pt">responded</span></a><span style="font-size:12.0pt"> to
</span><a href="https://www.icann.org/en/system/files/correspondence/cole-et-al-to-sinha-costerton-20jan23-en.pdf"><span style="font-size:12.0pt">our 23-Jan letter</span></a><span style="font-size:12.0pt">.<br>
On 29-May, new draft agreements were </span><a href="https://www.icann.org/en/announcements/details/amendments-to-the-base-gtld-ra-and-raa-to-modify-dns-abuse-contract-obligations-29-05-2023-en" title="https://www.icann.org/en/announcements/details/amendments-to-the-base-gtld-ra-and-raa-to-modify-dns-abuse-contract-obligations-29-05-2023-en"><span style="font-size:12.0pt">published</span></a><span style="font-size:12.0pt"> for
public comment.<br>
<br>
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">4. <b>
Registrant Data Request System </b>(RDRS), formerly known as SSAD Light</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">BC and IPC voted No on building SSAD, because we did not see value unless there was significantly likelihood of getting disclosures when we requested with legitimate purposes.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;color:#212121">Steve is on </span><a href="https://community.icann.org/pages/viewpage.action?pageId=186779415" title="https://community.icann.org/pages/viewpage.action?pageId=186779415"><span style="font-size:12.0pt;color:#0078D7">Council
small team</span></a><span style="font-size:12.0pt;color:#212121"> on </span><a href="https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf" title="https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf"><span style="font-size:12.0pt;color:#0078D7">SSAD
ODA</span></a><span style="font-size:12.0pt;color:#212121">, to review a“ticketing system” without obligations for use or for disclosure.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;color:#212121">On 13-Sep ICANN staff released a </span><a href="https://www.icann.org/en/system/files/files/whois-disclosure-system-design-paper-13sep22-en.pdf" title="https://www.icann.org/en/system/files/files/whois-disclosure-system-design-paper-13sep22-en.pdf"><span style="font-size:12.0pt;color:#0078D7">design
paper</span></a><span style="font-size:12.0pt;color:#212121">. Highlights:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt;color:#212121">ICANN org says development over nine months; development and two-year maintenance would be $100,000</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.75in;text-indent:-.25in;mso-list:l1 level1 lfo6">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:#212121">It does not include accreditation of the requestors</span><span style="font-size:12.0pt">; N<span style="color:#212121">o fees to the requestor. </span></span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.75in;text-indent:-.25in;mso-list:l1 level1 lfo6">
<![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:#212121">There is no obligation for automated processing of requests by contracted parties. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;color:#212121"> See </span><a href="https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-17nov22-en.pdf" title="https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-17nov22-en.pdf"><span style="font-size:12.0pt;color:#0078D7">Council’s
17-Nov letter to the Board</span></a><span style="font-size:12.0pt;color:#212121">. In Feb-2023 Board </span><a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-27-02-2023-en" title="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-27-02-2023-en"><span style="font-size:12.0pt;color:#0078D7">directed</span></a><span style="font-size:12.0pt;color:#212121"> ICANN
org to develop the System.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt;color:#212121"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">On 11-Mar-2023 the small team held a session in Cancun to hear about progress from Org’s development team. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">The system is now named Registration Data Request Service</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Steve asked for the data model, up-front. To include images of screenshots submitted with requests. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Suggested batch request feature from vendors like AppDetex and Fairwinds</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Steve said: Usage has 2 dimensions:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:2.0in"><span style="font-size:12.0pt">Quantity of requests & responses</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:2.0in"><span style="font-size:12.0pt">Quality of requests & responses (origin, reason, detail, registrar, domain name, etc.)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">Becky said board wants to know what we hope to learn from this experiment.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><i><span style="font-size:12.0pt">Will we learn what we need to determine next steps? Is SSAD fit-for-purpose?</span></i><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><i><span style="font-size:12.0pt">Did this make it easier for users to submit requests and for registrars to process those requests?</span></i><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">On 19-Apr staff released their data model, which does include the detail the BC requested.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">But Steve objected to staff statement that it would not make detailed results available for our analysis, noting t<span style="color:#212121">he</span><span style="color:black"> </span></span><a href="https://www.icann.org/en/system/files/files/whois-disclosure-system-design-paper-13sep22-en.pdf" title="https://www.icann.org/en/system/files/files/whois-disclosure-system-design-paper-13sep22-en.pdf"><span style="font-size:12.0pt;color:#0563C1">design
paper</span></a><span style="font-size:12.0pt;color:black"> and </span><a href="https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos-to-gnso-council-07nov22-en.pdf" title="https://gnso.icann.org/sites/default/files/policy/2022/correspondence/ducos-to-gnso-council-07nov22-en.pdf"><span style="font-size:12.0pt;color:#0563C1">addendum</span></a><span style="font-size:12.0pt;color:black"> indicate
access to data, even for non-participating registrars</span><span style="font-size:12.0pt">.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">On 7-May small team call,
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Steve lamented staff reversing their commitment to make data available. Staff and RrSG said they assumed “data” was just the reported aggregates and metrics.<br>
Steve said the BC will look at reasons for disclosure denial, and compare those reasons to the new legal basis given in NIS2</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">Steve Crocker said researchers will want to do
<b>reverse lookups</b>. Should be among success criteria. Sarah Wyld said that’s out of scope
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">On 15-May call, Sara Wyld said:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt">“If the data is “protected” (via P/P service) then only P/P data will be sent in response to the RDRS request. This is the same data as is available publicly. If the underlying data
is required, that needs due process (warrant, subpoena, etc) and is not part of the RDRS at all. Due process requests are outside the scope of the RDRS, as is disclosure of data underlying a P/P service”</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt"> On May 16 and 17 ICANN held
</span><a href="https://www.icann.org/en/announcements/details/icann-to-showcase-early-development-of-the-registration-data-request-service-01-05-2023-en"><span style="font-size:12.0pt">webinars on the RDRS</span></a><span style="font-size:12.0pt">. Demo
was good. They are very far along with this.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">On 25-May Council received an update from EPDP Phase 2 small team on progress defining the </span><a href="https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-rdrs-proposed-success-15may23-en.pdf"><span style="font-size:12.0pt">success
criteria of the RDRS.</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt"> 5. Subsequent Rounds of gTLD expansion (SubPro)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">There will be an Implementation Review Team (IRT) for SubPro.
<br>
We need volunteers to represent the BC, naming one representative and one alternate.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">Thanks to Imran Hossen for volunteering as BC rep. And thanks to Ching Chiao for volunteering as alternate.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:12.0pt">6. </span>
<a href="https://docs.google.com/document/d/1WvDU-dmKXF1LY0iXJCWes0B6_JilEWcA/edit."><b><span style="font-size:12.0pt;background:yellow;mso-highlight:yellow">Statement of Interest (SOI) exemption proposal</span></b></a><span style="font-size:12.0pt;background:yellow;mso-highlight:yellow">:</span><span style="font-size:12.0pt">
(see </span><a href="https://community.icann.org/download/attachments/240617757/CCOICI%20-%20Exemption%20overview%20-%209%20May%202023.pdf?version=1&modificationDate=1685949398075&api=v2" title="https://community.icann.org/download/attachments/240617757/CCOICI%20-%20Exemption%20overview%20-%209%20May%202023.pdf?version=1&modificationDate=1685949398075&api=v2"><span style="font-size:12.0pt">slides</span></a><span style="font-size:12.0pt">).</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">The CCOICI found 0.03% members were using the exemption. This limited use led to conclusion that the requests for removal of the exemption language did not seem to be in response
to a current issue but potential future situations. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:12.0pt">CCOICI also noted that tightening of the exemption language, by providing further specificity as to what qualifies as a ‘representative’ may have even further reduced its use in these
efforts. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">Channel 3. Supporting discussion/voting on matters before the Commercial Stakeholders Group (CSG)</span></b><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:12.0pt;color:black">Tim Smith is the CSG Liaison for the BC. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">Board Seat 14</span></b><span style="font-size:12.0pt">. CSG and NCSG ExComm will meet Thursday morning discuss common interests and to build a better understanding of each other’s priorities. This will
pave way for broader discussion on Board seat 14 and future candidacies. </span>
<span lang="EN-CA" style="font-size:12.0pt"> </span><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">IFR Representative. </span>
</b><span style="font-size:12.0pt">In April, the ICANN Office of the Chief Technology Officer (OCTO) notified CSG ExComm of a
<a href="https://www.icann.org/en/system/files/correspondence/bryce-to-reynoso-et-al-06apr23-en.pdf" title="https://www.icann.org/en/system/files/correspondence/bryce-to-reynoso-et-al-06apr23-en.pdf">
Request for Appointment of Members and Liaisons to the Second IANA Naming Function Review (IFR)</a>
<b><o:p></o:p></b></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">The IFR is an accountability mechanism required by ICANN’s Bylaws to ensure that Public Technical Identifiers (PTI) meets the needs and expectations of its naming customers. The IFR team is mandated to review
PTI's performance of the IANA naming function against the requirements set forth in the IANA Naming Function Contract and the IANA Naming Function Statement of Work.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Required is one representative to be appointed by CSG. There has been no discussion on this within the CSG ExComm. If anybody is interested, please let me know and I’ll put a name forward.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">DEADLINE: Friday, 30 June 2023 at 17:00 UTC<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">Meetings at ICANN 77:<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:12.0pt">CSG Membership – Wednesday, 14 June 2023 at 19:30 UTC<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">CPH and CSG Membership – Thursday, 15 June 2023 at 17:45 UTC<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="layout-grid-mode:char"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
</div>
</body>
</html>