<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="plaintext" style="white-space: normal;"><p dir="auto">Anne,</p>
<p dir="auto">Great notes in your support for your question. I believe we should consider on our perspective on how NCAP does or does not address those questions.</p>
<p dir="auto">With respect your specific question about the bullet point on the slide, I can tell you what I had in mind at the time, which has evolved a bit with your question.</p>
<p dir="auto">Originally, I was imagining there would be a well-defined step in the Application Process (which is defined by the Applicant Guidebook - hence the bullet) for name collision assessment. Currently, we’re imagining the overall name collision assessment process as several sub-steps, which in my early model would have all been inserted at some specific point in time determined by the SubPro process. That’s how it started.</p>
<p dir="auto">Reading your expansion of why you were asking the question convinces me we should consider if NCAP is a single step in the application process, or if the steps as we are developing them could be separated into different places in the application process. I’m not yet convinced we have to say anything about this, but I do think it’s an important question to discuss so we can confirm if there is something to say or not.</p>
<p dir="auto">Jim</p>
<br><br><p dir="auto">On 15 Feb 2022, at 18:14, Aikman-Scalese, Anne wrote:</p>
</div><blockquote class="embedded" style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><div id="DC6CB07A-E583-42F5-A733-4F4FA9C8178B">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1" style="page: WordSection1;">
<p class="MsoNormal"><span style="color:#1F497D">Many thanks, Jennifer. And thanks to Jim and Matt for all your hard work on this. Question to the Co-Chairs re the Workflow:</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">With respect to the Workflow Document, and as a member of the (now inactive) Sub Pro Working Group, I am wondering about the reference to Sub Pro in the last portion of the slide highlighted below:</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:18.0pt;font-family:ArialMT;color:black">2. Application submission</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:18.0pt;font-family:ArialMT;color:black">● Technical package with name collision analysis must be included</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:18.0pt;font-family:ArialMT;color:black">○ Only if name collisions present?</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:18.0pt;font-family:ArialMT;color:black">○ Draft mitigation plan?</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:18.0pt;font-family:ArialMT;color:black">○ Draft remediation plan?</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:18.0pt;font-family:ArialMT;color:black">○ Trending data?</span></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:18.0pt;font-family:Arial-ItalicMT;color:black;background:yellow;mso-highlight:yellow">● Subsequent procedures and applicant guidebook process drives at this point</span></i></p>
<p class="MsoNormal" style="text-autospace:none"><i><span style="font-size:18.0pt;font-family:Arial-ItalicMT;color:black;background:yellow;mso-highlight:yellow">○ Out of scope for discussion group</span></i></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:ArialMT;color:#595959">8</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The reason for my question is that the Sub Pro Final Report says</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoListParagraph" style="mso-style-priority: 34; margin-top: 0in; margin-right: 0in; margin-bottom: 0in; margin-left: .5in; margin-bottom: .0001pt; font-size: 11.0pt; font-family: 'Calibri',sans-serif; text-indent: -.25in; mso-list: l3 level1 lfo4;"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman""> </span></span></span> <![endif]><span style="color:#1F497D">ICANN should develop a DO NOT APPLY list based on unacceptable name collision risk. (The NCAP DG appears to have a workflow process designed to measure the risk but no process for applying a particular standard that would undergird such a DO NOT APPLY list. Arguably the SSAC itself is best positioned to do this.) It seems to me that this is a decision that the Board itself cannot make without advice from the SSAC and a recommendation from the Board’s Technical Committee.</span></p>
<p class="MsoListParagraph" style="mso-style-priority: 34; margin-top: 0in; margin-right: 0in; margin-bottom: 0in; margin-left: .5in; margin-bottom: .0001pt; font-size: 11.0pt; font-family: 'Calibri',sans-serif;"><span style="color:#1F497D"> </span></p>
<p class="MsoListParagraph" style="mso-style-priority: 34; margin-top: 0in; margin-right: 0in; margin-bottom: 0in; margin-left: .5in; margin-bottom: .0001pt; font-size: 11.0pt; font-family: 'Calibri',sans-serif; text-indent: -.25in; mso-list: l3 level1 lfo4;"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman""> </span></span></span> <![endif]><span style="color:#1F497D">The Sub Pro Final Report says that If NCAP creates a new Name Collision Framework that is ultimately adopted by the Board, then that will apply during the next round. However, the Sub Pro Final Report also says that if no new Name Collision Framework is adopted by the Board pursuant to an NCAP (and presumably an SSAC) recommendation, then the Board should apply the old 2012 round version of 90-day Controlled Interruption. As I understand it, the initial Controlled Interruption test would only be the first step in the Workflow analysis. Sub Pro IRT cannot develop additional processes and standards to determine whether or not to take the analysis to the next step, i.e. Enhanced Controlled Interruption. That would definitely be beyond the scope of a Sub Pro IRT. In fact, I think the Operational Design Phase (ODP) Document notes this Name Collision area as an issue that must be resolved. (Others are likely more familiar than I with the ODP work plan for the next round.)</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">So it seems to me that either the DG or the SSAC will need to work on the following:</span></p>
<p class="MsoListParagraph" style="mso-style-priority: 34; margin-top: 0in; margin-right: 0in; margin-bottom: 0in; margin-left: .5in; margin-bottom: .0001pt; font-size: 11.0pt; font-family: 'Calibri',sans-serif; text-indent: -.25in; mso-list: l0 level1 lfo6;"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">A.<span style="font:7.0pt "Times New Roman""> </span></span></span> <![endif]><span style="color:#1F497D">A measure of Impact (volume and diversity) that merits a DO NOT APPLY rating and saves everyone time and money before the heavy administrative process kicks in.</span></p>
<p class="MsoListParagraph" style="mso-style-priority: 34; margin-top: 0in; margin-right: 0in; margin-bottom: 0in; margin-left: .5in; margin-bottom: .0001pt; font-size: 11.0pt; font-family: 'Calibri',sans-serif; text-indent: -.25in; mso-list: l0 level1 lfo6;"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">B.<span style="font:7.0pt "Times New Roman""> </span></span></span> <![endif]><span style="color:#1F497D">A standard of Impact (volume and diversity) that applies at the point of Application Submitted and after the initial Controlled Interruption Assessment. These standards would be used to judge whether or not to move on to Enhanced Controlled Interruption.</span></p>
<p class="MsoNormal" style="margin-left:.25in"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">In the Workflow, the decision to move to Enhanced Controlled Interruption in the Workflow appears to be handled at the ICANN Org Technical Review Team level, but how will that Team know what standard to apply to jump to the next level of “Enhanced Controlled Interruption” if the SSAC does not make a recommendation in this regard? And indeed, even if some standard is developed for that purpose, what is the standard that will apply at the next step after Enhanced Controlled Interruption is conducted? Will an ICANN Technical Review Team be making a specific recommendation to the Board on a case-by-case basis? Will that recommendation go first to the Board’s Technical committee that will then make a recommendation to the Board?</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">It Looks as though we, as a Discussion Group, are developing a great Workflow process, but that it will be almost impossible to apply without real guidelines/standards by which to judge the Impact (volume and diversity). So far, we don’t have an actual new “Name Collision Framework”. The Subsequent Procedures Final Report requires deference to a new NCAP Name Collision Framework, but if a more specific Framework is not adopted by the Board, the Sub Pro Final Report yields a recommendation to adopt the same 90-day Controlled Interruption procedure that applied in the 2012 round. (If that occurs, all our work as a DG is for naught.)</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">It’s very difficult for me to see how the Board can adopt the new Workflow as a Name Collision Framework to apply to the next round without specific standards being recommended for analysis of Impact for each phase of the Workflow. Perhaps those standards are best developed at the level of SSAC, but if that is the case, I think we should acknowledge that now within the DG. SSAC is much better suited to establish standards for Impact that should be applied to each step of the Workflow Process. It seems to me that only by the development of such standards will the Board be in a position to adopt a new Name Collision Framework for the next round.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Looking forward to others’ observations on these points…</span></p>
<p class="MsoNormal"><span style="color:#1F497D">Anne</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:106%"><b><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Anne E. Aikman-Scalese</span></b></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:106%"><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Of Counsel</span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:40%"><span style="font-size:10.0pt;line-height:40%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><img width="17" height="7" style="width:.177in;height:.0729in" id="Picture_x0020_2" src="cid:image002.png@01D82287.143D9860"></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:106%"><span style="font-size:10.0pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><a href="mailto:AAikman@lewisroca.com" target="_new" title="Email User"><span style="color:#323232">AAikman@lewisroca.com</span></a></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:.25in;line-height:106%"><span style="font-size:10.0pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:#323232">D. 520.629.4428</span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:106%"><span style="font-size:10.0pt;line-height:106%;font-family:"Trebuchet MS",sans-serif;color:#1F497D"><img border="0" width="160" height="22" style="width:1.6666in;height:.2291in" id="Picture_x0020_1" src="cid:image003.png@01D82284.79E15E70"></span></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> NCAP-Discuss <ncap-discuss-bounces@icann.org> <b>On Behalf Of</b> Jennifer Bryce<br>
<b>Sent:</b> Tuesday, February 15, 2022 3:07 AM<br>
<b>To:</b> ncap-discuss@icann.org<br>
<b>Subject:</b> [NCAP-Discuss] NCAP DG agenda: 16 February 2022</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><strong><span lang="EN-GB" style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center"></div>
</div>
<p class="MsoNormal"><span lang="EN-GB">Dear NCAP DG members,</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">Here is the agenda for the next DG meeting, scheduled for Wednesday 16 February @ 19:00 UTC.</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<ol style="margin-bottom: 0in; margin-top: 0in;" start="1" type="1">
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><span lang="EN-GB">Welcome and roll call – Jim/Matt</span></li>
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><span lang="EN-GB">Update from the Technical Investigator – Casey</span></li>
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><span lang="EN-GB">Project status and restatement of summary of action items and decisions made from last meeting (see <a href="https://docs.google.com/spreadsheets/d/1DE5lcOqFujazdw4_x5ii9vcBnsoskAUJnBee_HaVHn8/edit#gid=418882614">tracker here</a>) – Jennifer</span></li>
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><span lang="EN-GB">Continue discussion on Terminology section (Section 1.3) of the <a href="https://docs.google.com/document/d/1oPmy0MVRcqkjOzh-OvJRMomYc76TYxvQSXjbEG8LV9w/edit#heading=h.msjt9drdk9ji">Google doc</a> (see PDF attached), beginning with legacy controlled interruption vs. enhanced controlled interruption – Heather</span></li>
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><span lang="EN-GB">Consensus of Workflow (see PDF attached) – Jim</span></li>
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><span lang="EN-GB">Summary of action items and decisions made – Jennifer</span></li>
<li class="MsoNormal" style="mso-list:l4 level1 lfo3"><span lang="EN-GB">AOB</span></li>
</ol>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">Best,<br>
Jennifer</span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="mso-fareast-language:EN-GB">-- </span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#A6A6A6">Jennifer Bryce</span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Project Manager, Office of the Chief Technology Officer (OCTO)</span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Internet Corporation for Assigned Names and Numbers (ICANN)</span></p>
<p class="MsoNormal"><span style="color:#A6A6A6"> </span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Skype: jennifer.bryce.icann</span></p>
<p class="MsoNormal"><span style="color:#A6A6A6">Email: <a href="mailto:jennifer.bryce@icann.org">jennifer.bryce@icann.org</a></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
</div>
<br>
<hr>
<font face="Arial" color="gray" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.<br></font>
</div></div></blockquote>
<div class="plaintext" style="white-space: normal;">
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><p dir="auto">_______________________________________________
<br>
NCAP-Discuss mailing list
<br>
NCAP-Discuss@icann.org
<br>
<a href="https://mm.icann.org/mailman/listinfo/ncap-discuss" style="color: #777777;">https://mm.icann.org/mailman/listinfo/ncap-discuss</a></p>
<p dir="auto">_______________________________________________
<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" style="color: #777777;">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" style="color: #777777;">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.</p>
</blockquote></div>
</div></body>
</html>