<html xmlns:v="urn:schemas-microsoft-com:vml" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:347175403;
mso-list-template-ids:137923928;}
@list l1
{mso-list-id:1037465450;
mso-list-template-ids:-327262324;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1138642504;
mso-list-type:hybrid;
mso-list-template-ids:1408114970 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.75in;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:5.25in;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7 ;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:5.75in;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:1159153952;
mso-list-template-ids:377144810;}
@list l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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 l3: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;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Here’s the Policy Calendar for the BC OPEN MEETING on 13-Mar (also in attachment “policy calendar.pdf”)<o:p></o:p></p>
<p class="MsoNormal" style="margin-right:.5in;layout-grid-mode:char"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-right:.5in"><b><span style="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">On 28-Feb we <a href="https://itp.cdn.icann.org/public-comment/proceeding/Proposed%20Procedure%20for%20Selecting%20a%20Top-Level%20Domain%20String%20for%20Private%20Use-13-01-2023/submissions/ICANN%20Business%20Constituency%20(BC)/BC%20Comment%20on%20process%20for%20private%20use%20TLDs-28-02-2023.pdf">
commented</a> on <a href="https://itp.cdn.icann.org/en/files/root-system/procedure-selecting-top-level-string-private-use-draft-11-01-2023-en.pdf">Proposed Procedure</a> for Selecting a Top-Level Domain String for
<i>Private Use</i>. (See <a href="https://www.icann.org/en/public-comment/proceeding/proposed-procedure-for-selecting-a-top-level-domain-string-for-private-use-13-01-2023">
comments page</a> and <a href="https://www.icann.org/en/system/files/files/sac-113-en.pdf">
SAC 113</a>, published Sep-2020.). This is about locally-defined domain names that enterprises use to support their applications and infrastructure, where that domain TLD is
<b><i>not</i></b> present in the root zone. “Two examples of private-use TLDs that are well known within the ICANN community are .corp and .home.” Thanks to Rajiv Prasad for drafting.<o:p></o:p></p>
<p class="MsoNormal" style="margin-right:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">On 13-Feb we <a href="https://cbu.memberclicks.net/assets/docs/positions-statements/2023/2023_02February_13_ICANN%20BC%20Comment%20on%20ICANN%20FY24-28%20Op%20Plan%20and%20Budgets.pdf">
commented</a> on the FY24-28 Operating & Financial Plan, FY24 Op plan & budget. (<a href="https://www.icann.org/en/public-comment/proceeding/draft-fy2428-operating-financial-plan-and-draft-fy24-operating-plan-budget-14-12-2022">comments page</a>). Thanks to
Tim Smith for drafting.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="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>ICANN
Public Comments</b></a><b><span style="color:black"> and other opportunities for the BC to comment: </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">1. <a href="https://itp.cdn.icann.org/en/files/additional-reviews/proposed-amendments-to-articles-18-and-19-icann-bylaws-08-03-2023-en.pdf">
proposed ICANN bylaws amendments</a> for the IANA Naming Function Review (<a href="https://www.icann.org/en/public-comment/proceeding/iana-naming-function-review-bylaws-changes-18-04-2023">comments page</a>). Comments close 18-Apr.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">This review was added to ICANN bylaws as part of the IANA transition, to let customers of IANA naming function confirm performance of the IANA Naming Function Contract between ICANN and its affiliate, Public Technical
Identifiers.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">In 2021 the BC <a href="https://cbu.memberclicks.net/assets/docs/positions-statements/2021/2021_03March_22%20BC%20support%20for%20amendment%20to%20IANA%20Naming%20Function%20Contract.pdf">
supported</a> a minor amendment to the IANA contract.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">In 2020 we <a href="https://www.icannbc.org/assets/docs/positions-statements/2020/2020_12December_02%20BC%20comment%20on%20IANA%20Naming%20Function%20Review%20Initial%20Report.pdf">
commented on the first IANA Naming Function Review</a>, thanks to Jimson Olufuye.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="background:yellow;mso-highlight:yellow">Looking for volunteer(s) to draft a BC comment on these bylaw amendments</span>.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">2. NIS2, followed closely by Andrew Bennett, Nik Lagergren, and Marie Pattullo.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><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">NIS2 final text</a> was approved by European
Parliament on 10-Nov, and by Council on 28-Nov.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">That final text <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=OJ:L:2022:333:FULL&from=EN">
published on 27-Dec</a> (p.82), which begins the 21-month period for Member States to transpose into national laws and regulations.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="background:yellow;mso-highlight:yellow">See Caroline’s 12-Mar email regarding NIS2 discussions in Cancun on Saturday.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="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="color:black">Marie Pattullo and Mark Datysgeld are our GNSO Councilors. </span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Previous Council meeting was 16-Feb. See <a href="https://community.icann.org/x/mgjVD">
Agenda</a>, <a href="https://gnso.icann.org/sites/default/files/policy/2023/transcript/transcript-gnso-council-16feb23-en.pdf">
Transcript</a>, <a href="https://icann.zoom.us/rec/share/qYmJbvdD2iftNPPz29ZL3fJUNMO2_e0asCMeWlcTRWlsf0oE01KFc6Ky4y4fAxhK.EGFo5ltQSPOEcTdn?startTime=1676523678000">
Zoom Recording</a>. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Meeting highlights include:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">Unanimously approved <a href="https://gnso.icann.org/sites/default/files/policy/2023/correspondence/novoa-et-al-to-council-et-al-06feb23-en.pdf">
amended charter</a> for Transfer Policy Review PDP and <a href="https://gnso.icann.org/sites/default/files/policy/2023/correspondence/carney-et-al-to-gnso-council-et-al-06feb23-en.pdf">
<span style="color:#0052CC;background:white">Project Change Request</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">Unanimously approved <a href="https://gnso.icann.org/sites/default/files/policy/2023/draft/draft-scbo-charter-24jan23-en.pdf">
revised Charter</a> for the Budget and Operations Townhall (formerly known as the SCBO).<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:black;background:yellow;mso-highlight:yellow">Next Council meeting is
</span><span style="background:yellow;mso-highlight:yellow">15-Mar<span style="color:black"> at </span>18:15 UTC while in Cancun</span>. <a href="https://community.icann.org/display/gnsocouncilmeetings/Final+Proposed+Agenda+2023-3-15">Agenda</a> highlights
include:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Item 4: Vote on adopting Council committee to oversee
<a href="https://gnso.icann.org/sites/default/files/policy/2023/correspondence/chen-to-gnso-council-05jan23-en.pdf">
continuous improvement recommendations</a><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Item 5: Discuss next steps for Expired Domain Deletion Policy and Recovery Policy,
<a href="https://docs.google.com/document/d/1zxxyIsg7HVGtAK7HsaTfw3nMX_zZfY3hUrdiDoaiPa0/edit">
small team recommendation</a>.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Item 6: Discuss GNSO projects that may impact SubPro timeline<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Item 7: Continue discussing SubPro<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Item 8: Discuss next steps for Whois Disclosure System<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">Steve is on <a href="https://community.icann.org/pages/viewpage.action?pageId=186779415">
Council small team</a> on <a href="https://www.icann.org/en/system/files/files/ssad-oda-25jan22-en.pdf">
SSAD ODA</a>, to review a“ticketing system” without obligations for use or for disclosure.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">On 13-Sep ICANN staff released a <a href="https://www.icann.org/en/system/files/files/whois-disclosure-system-design-paper-13sep22-en.pdf">
design paper</a>. Highlights:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">ICANN org says development over nine months; development and two-year maintenance would be $100,000<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:1.25in;mso-list:l2 level1 lfo3"><span style="font-size:12.0pt">It does not include accreditation of the requestors.
</span></li><li class="MsoListParagraph" style="margin-left:1.25in;mso-list:l2 level1 lfo3"><span style="font-size:12.0pt">It does not include a billing function or any fees to the requestor.
</span></li><li class="MsoListParagraph" style="margin-left:1.25in;mso-list:l2 level1 lfo3"><span style="font-size:12.0pt">There is no obligation of automated processing of requests by contracted parties. </span></li></ul>
<p class="MsoNormal" style="margin-left:1.0in">We pushed for <span style="color:black">
logging and reporting of request data</span>, even when the registrar is not currently participating.<o:p></o:p></p>
<p class="MsoNormal"> <span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">The<span style="color:black"> </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="color:#0563C1">design
paper</span></a><span style="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="color:#0563C1">addendum</span></a><span style="color:black"> indicate
access to data, even for non-participating registrars:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="color:black;letter-spacing:.15pt;background:white">"The system will provide reporting on a periodic basis not to exceed the recommended durations. The exact form of the
</span>reporting is to be determined. It is envisioned that eventually the data will be made available through the Open Data platform for public consumption." (p.31)<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:2.0in"><b><span lang="EN-CA" style="color:black"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span lang="EN-CA" style="color:black">Marika (Staff) added this to the </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="color:#0563C1">addendum</span></a><span style="color:black"> at
p.4:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><span lang="EN-CA" style="color:black">“To facilitate the evaluation of the WHOIS Disclosure System, the small team will continue to work with ICANN Org to ensure that the necessary data is available to ensure
the proper evaluation of the Whois Disclosure System, taking into account legal limitations that may exist to share certain information.”</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> See <a href="https://www.icann.org/en/system/files/correspondence/ducos-to-sinha-17nov22-en.pdf">
Council’s 17-Nov letter to the Board</a>. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">On 27-Feb-2023 the Board <a href="https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-special-meeting-of-the-icann-board-27-02-2023-en">directed</a> ICANN org to develop the Whois
Disclosure System within 11 months.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="background:yellow;mso-highlight:yellow">On 11-Mar-2023 the small team held a session in Cancun to hear about progress from Org’s development team.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="background:yellow;mso-highlight:yellow">The system is now named
<b>Registration Data Request Service</b><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="background:yellow;mso-highlight:yellow">Steve asked for the
<b>data model,</b> up-front. To include images of screenshots submitted with requests.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="background:yellow;mso-highlight:yellow">Granularity of reporting can be adjusted later.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="background:yellow;mso-highlight:yellow">Suggested batch request feature from vendors like AppDetex and Fairwinds<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="background:yellow;mso-highlight:yellow"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="background:yellow;mso-highlight:yellow">Steve said: Usage has 2 dimensions:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><span style="background:yellow;mso-highlight:yellow">Quantity of requests and responses<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><span style="background:yellow;mso-highlight:yellow">Quality of requests (origin, reason, detail, registrar, domain name, etc.)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:2.0in"><span style="background:yellow;mso-highlight:yellow"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="background:yellow;mso-highlight:yellow">Staff said they can evolve the data model over time (huh?). Asked us to say what we want reported.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><o:p> </o:p></p>
<p class="MsoNormal"> <span style="color:#172B4D;background:white"> </span><o:p></o:p></p>
<p class="MsoNormal"> <span style="color:black">Other Council activities:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="color:black"> </span> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> 1. <b>Closed Generic gTLD</b>s in the next round.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">following an invitation from the Board, GNSO and GAC will “formulate a workable framework to identify and handle closed generic applications for the immediate next round of new gTLDs”, and in this dialogue we will
be joined by ALAC. The framework discussion will focus on options other than the two endpoint positions (i.e. no closed generics at all; closed generics without restrictions) as per the Board’s Proposed Parameters for Dialogue.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">As discussed on our 14-Nov call, Steve researched prior BC positions on closed generic going back a decade to our comments during the 2012 round of gTLD expansion.</span><span style="font-size:11.0pt;color:black">
</span>See attached email from Steve with the full explanation. <span style="color:black">
To summarize In a sentence, we’d say:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><b><span style="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> </b><span style="color:black">For example, </span>
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.</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">2. <b>Transfer Policy Working Group</b>. (Zak Muscovitch and Arinola Akinyemi).
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Work group evaluated <a href="https://itp.cdn.icann.org/en/files/inter-registrar-transfer-policy-irtp/summary-report-initial-report-transfer-policy-review-phase-1a-30-08-2022-en.pdf">
public comment report</a> on its <a href="https://itp.cdn.icann.org/en/files/inter-registrar-transfer-policy-irtp/transfer-policy-review-initial-report-21-06-2022-en.pdf">
initial report</a>. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#212121;background:yellow;mso-highlight:yellow">Now discussing<span class="apple-converted-space"> </span></span><a href="https://docs.google.com/document/d/1i6tLO_qbSa-ace0BnKaAn7voP1UA1RjYlrRo2ZneZNY/edit?usp=sharing" title="https://docs.google.com/document/d/1i6tLO_qbSa-ace0BnKaAn7voP1UA1RjYlrRo2ZneZNY/edit?usp=sharing"><span style="color:#0078D4;background:yellow;mso-highlight:yellow">Charter
Questions</span></a><span style="color:#212121;background:yellow;mso-highlight:yellow"> related to the Transfer Dispute Resolution Policy (TDRP)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">3. <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"> </span>Work on Applicant Support kicks off on<span class="apple-converted-space"> </span><b>Monday, 21 November at 1500 UTC<span class="apple-converted-space"> </span></b>with
an initial call of the working group.<span class="apple-converted-space"> </span>The<span class="apple-converted-space"> </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">main
wiki pag</a><span style="color:black">e that provides the status and background of the task and the page that lists the<span class="apple-converted-space"> </span></span><a href="https://community.icann.org/display/GGPGIRFAS/Members+and+Mailing+List" title="https://community.icann.org/display/GGPGIRFAS/Members+and+Mailing+List">Members
and Alternates</a><span class="apple-converted-space"><span style="color:black"> </span></span><span style="color:black">are linked within.<span class="apple-converted-space"> </span>Observers will have ability to view member chat and information shared in
the zoom webinar room, but observers will not be able to use chat or raise hands during sessions. BC member Segunfunmi Olajide has signed up as an observer.
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">4. DNS Abuse small team. <span style="color:black">
Mark Datysgeld serves as co-lead.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in">CPH representatives met with ICANN Org for negotiations on RAA and RyA amendments to address DNS Abuse. (<a href="https://www.icann.org/en/system/files/correspondence/costerton-to-heineman-15jan23-en.pdf">Sally’s
letter</a>). To inform that negotiation, Mason drafted and sent <a href="https://www.icann.org/en/system/files/correspondence/cole-et-al-to-sinha-costerton-20jan23-en.pdf">
this letter</a> from BC, IPC, and ALAC on 23-Jan<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black"> </span> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="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="color:black">Tim Smith is the CSG Liaison for the BC. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">See </span><a href="https://icann76.sched.com/">final schedule for ICANN 76 in Cancun</a>,
<span style="color:black">11-Mar thru 16-Mar</span><o:p></o:p></p>
<p class="MsoNormal"><b><o:p> </o:p></b></p>
<p class="MsoNormal"><b>Board Seat 14</b>. CSG ExComm has now offered 2 candidates to NCSG and are awaiting their consideration. Determining the candidate who will be put forward on behalf of the NCPH will likely take us through ICANN 76 and we are hopeful
we can find a common candidate from the two SGs. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CSG is also seeking more ongoing dialogue with NCSG and our ExComm has proposed more regular meetings, even intersessional between ICANN meetings, to discuss our common interests.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>ICANN Board and CSG </b>will meet<b> – Tuesday, March 14, 21:30 UTC (4:30pm)
</b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Additional upcoming meetings<o:p></o:p></p>
<p class="MsoNormal"><b>CPH DNS Abuse Outreach – Monday, March 13, 18:15 UTC (1:15pm)<o:p></o:p></b></p>
<p class="MsoNormal"><b>CSG Membership Meeting – Tuesday, March 14, 15:30 UTC (10:30am)<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;layout-grid-mode:char"><o:p> </o:p></p>
</div>
</body>
</html>