<div dir="ltr">Thanks Jeff. Your point is well-taken, especially since the GAC, in its comments to the Sub Pro Final Report, called out 29.3.<div>Anne</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Anne Aikman-Scalese</div>GNSO Councilor<div>NomCom Non-Voting 2022-2024</div><div><a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 7, 2023 at 8:43 AM Jeff Schmidt via NCAP-Discuss <<a href="mailto:ncap-discuss@icann.org">ncap-discuss@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg8513511946672957002">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_3393621038152160957WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Agree. But since it’s Guidance ICANN needs to either follow it or explain why not. NCAP can’t be slient.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<div id="m_3393621038152160957mail-editor-reference-message-container">
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-bottom:12pt"><b><span style="font-size:12pt;color:black">From:
</span></b><span style="font-size:12pt;color:black">NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" target="_blank">ncap-discuss-bounces@icann.org</a>> on behalf of Rubens Kuhl via NCAP-Discuss <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>><br>
<b>Date: </b>Thursday, September 7, 2023 at 10:12 AM<br>
<b>To: </b><a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a> <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>><br>
<b>Subject: </b>Re: [NCAP-Discuss] "Do Not Apply"<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11pt">Jeff,<u></u><u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">In SubPro lingo, an Implementation Guidance is akin to a SHOULD in BCP 14. So lack of an NCAP position on it won’t make ICANN Org to have to do it… it’s not a MUST. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">That said, there would be no harm in having that specified by NCAP. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">Rubens<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><br>
<br>
<u></u><u></u></span></p>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div>
<p class="MsoNormal"><span style="font-size:11pt">Em 7 de set. de 2023, à(s) 11:52, Jeff Schmidt via NCAP-Discuss <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>> escreveu:<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">Team:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">SubPro said:<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">Implementation Guidance 29.3: To the extent possible, ICANN should seek to identify high-risk strings in advance of opening the Application Submission Period, which should constitute a “Do Not Apply” list.
ICANN should also seek to identify aggravated risk strings in advance of the next application window opening and whether it would require a specific name collision mitigation framework.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">We (NCAP) have talked quite a bit about the difficulties of an a-priori collisions “Do Not Apply” list. I “think” we are all in agreement that such a list cannot be produced, however such assumptions are dangerous.
I looked in Study 1 and the draft of Study 2 and they are both, surprisingly, silent on the NCAP position on “Do Not Apply.”<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">Is there consensus that NCAP will state that a-priori “Do Not Apply" is not possible? If so, this should be included in Study 2. If not, uhm, add it to the discussion list.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt">Thanks!<br>
Jeff<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"> <u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:9pt;font-family:Helvetica">_______________________________________________<br>
NCAP-Discuss mailing list<br>
</span><span style="font-size:11pt"><a href="mailto:NCAP-Discuss@icann.org" target="_blank"><span style="font-size:9pt;font-family:Helvetica">NCAP-Discuss@icann.org</span></a></span><span style="font-size:9pt;font-family:Helvetica"><br>
</span><span style="font-size:11pt"><a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" target="_blank"><span style="font-size:9pt;font-family:Helvetica">https://mm.icann.org/mailman/listinfo/ncap-discuss</span></a></span><span style="font-size:9pt;font-family:Helvetica"><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 (</span><span style="font-size:11pt"><a href="https://www.icann.org/privacy/policy" target="_blank"><span style="font-size:9pt;font-family:Helvetica">https://www.icann.org/privacy/policy</span></a></span><span style="font-size:9pt;font-family:Helvetica">)
and the website Terms of Service (</span><span style="font-size:11pt"><a href="https://www.icann.org/privacy/tos" target="_blank"><span style="font-size:9pt;font-family:Helvetica">https://www.icann.org/privacy/tos</span></a></span><span style="font-size:9pt;font-family:Helvetica">).
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.</span><span style="font-size:11pt"><u></u><u></u></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
NCAP-Discuss mailing list<br>
<a href="mailto:NCAP-Discuss@icann.org" target="_blank">NCAP-Discuss@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/ncap-discuss</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div>