<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div><div class="plaintext"><p dir="auto">This is a good suggestion to agree on some terminology to describe each of the events separately. Let’s not forget this as we begin to develop some text for our workflow framework.</p>
<p dir="auto">Jim</p>
<br /><p dir="auto">On 8 Dec 2021, at 17:00, Tom Barrett wrote:</p>
</div><blockquote class="embedded"><div id="74AC05B6-7E0E-49A0-9CB7-A9EE24F668C5"><!DOCTYPE html>
<html>
<head>
<meta name="generator" content="HTML Tidy for HTML5 for Apple macOS version 5.8.0">
<title></title>
</head>
<body>
<div dir="ltr"> I have a suggestion regarding the workflow here.
<div><br></div>
<div>My concern is that once a tld has been added to the root, there will be pressure to keep it in the root, while ICANN is negotiating terms with the applicant. This will disadvantage ICANN and potential objectors in certain respects.<br>
<div><br></div>
<div>How about we differentiate between a "temporary delegation" and "approved delegation"?</div>
<div><br></div>
<div>Then we could have an explicit step in the workflow whereby the temporary delegation is terminated and the tld is removed from the root. This would apply even if there is near certainty of the tld being eventually delegated.</div>
</div>
<div><br></div>
<div>Tom</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Dec 8, 2021 at 4:59 PM Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com">AAikman@lewisroca.com</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 lang="EN-US">
<div class="gmail-m_295722578370401479WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Thanks Jim and Jonathan,</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I think this discussion gets to the point that Tom Barrett was trying to make on today’s call – that there should be a technical mechanism for informing a potential applicant of the degree of risk of non-award of the contract at some point before application is made and a large application fee is paid. In other words, if the potential applicant has a way to assess name collision risk as “high”, then the applicant may not waste resources on that particular string. This is consistent with the notion coming out of the Sub Pro Final Report which resulted in a Recommendation to the Board that a DO NOT APPLY list be developed prior to the launch of the next round.</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Otherwise, we are saying “go ahead and develop your business plan and pay your application fee and later if name collision risk is too high and the string can’t be delegated, you might get a partial or total refund.” That seems like something that should be avoided.</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Anne</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></p>
<div>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b> <span style="font-size:11pt;font-family:Calibri,sans-serif">NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" target="_blank">ncap-discuss-bounces@icann.org</a>> <b>On Behalf Of</b> James Galvin<br>
<b>Sent:</b> Wednesday, December 8, 2021 2:33 PM<br>
<b>To:</b> Jothan Frakes <<a href="mailto:jothan@jothan.com" target="_blank">jothan@jothan.com</a>><br>
<b>Cc:</b> NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>><br>
<b>Subject:</b> Re: [NCAP-Discuss] Draft Final Proposed Workflow</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><strong><span style="font-size:9pt;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>
<div>
<div>
<p>An important distinction to make is whether we are using “delegation” in a technical sense or a business sense.</p>
<p>In a technical sense, you are correct. A string must be delegated (be present in the root zone) in order for controlled interruption and enhanced controlled interruption to work. And, if there is an issue created as a result of name collisions then the delegation must be withdrawn.</p>
<p>This is separate and independent from the business decision of deciding to delegate a proposed TLD string to a particular registry operator, which if successful would also require a technical delegation in order for the string “to work”.</p>
<p>The technical delegation is part of the due diligence process. There is no change in predictability to an applicant as compared to the application process as a whole.</p>
<p>Since you mention “applicant” in the context of your question I believe you’re asking about business delegation and that is out of scope for this working group.</p>
<p>Jim</p>
<p class="MsoNormal" style="margin-bottom:12pt"><br>
<br></p>
<p>On 1 Dec 2021, at 14:43, Jothan Frakes wrote:</p>
</div>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div id="gmail-m_2957225783704014797C6CE784-8D1B-4A1A-B27C-B611F55F58AE">
<div>
<p class="MsoNormal">I am concerned an item on about slides 9&10<br>
<br>
"Does not guarantee approval of permanent delegation"<br>
<br>
Is this contemplating a scenario where a TLD would get revoked _after_ it is delegated due to some NC issue? <br>
<br>
It seems there needs to be a horizon of certainty to an applicant as a reasonable expectation.<br>
<br>
<br clear="all"></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><br>
Jothan Frakes<br>
Tel: +1.206-355-0230</p>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On Wed, Dec 1, 2021 at 10:47 AM Aikman-Scalese, Anne <<a href="mailto:AAikman@lewisroca.com" target="_blank">AAikman@lewisroca.com</a>> wrote:</p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Thanks Jim. I may have missed a meeting, but during today's meeting, will you elaborate on the specific differences between "Controlled Interruption" and "Enhanced Controlled Interruption" and why the word, "honeypot", has disappeared from the slides?<br>
Thank you,<br>
Anne<br>
<br>
-----Original Message-----<br>
From: NCAP-Discuss <<a href="mailto:ncap-discuss-bounces@icann.org" target="_blank">ncap-discuss-bounces@icann.org</a>> On Behalf Of James Galvin<br>
Sent: Wednesday, December 1, 2021 9:35 AM<br>
To: NCAP Discussion Group <<a href="mailto:ncap-discuss@icann.org" target="_blank">ncap-discuss@icann.org</a>><br>
Subject: [NCAP-Discuss] Draft Final Proposed Workflow<br>
<br>
[EXTERNAL]<br>
<br>
Attached is a PDF of the slides describing the workflow for those who don’t have ready access to the Shared Drive.<br>
<br>
This is now draft final, which means we will start to progress producing our final work product based on this. We’ll talk more about this today.<br>
<br>
Thanks to all!<br>
<br>
Jim<br>
<br>
________________________________<br>
<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>
_______________________________________________<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" 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" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" 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.</p>
</blockquote>
</div>
</div>
</blockquote>
</div>
</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>
_______________________________________________<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.</blockquote>
</div>
<br clear="all">
<div><br></div>
--<br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr"><font face="arial, helvetica, sans-serif" size="2">Thomas Barrett</font>
<div><font face="arial, helvetica, sans-serif" size="2">President</font></div>
<div><font face="arial, helvetica, sans-serif" size="2">EnCirca, Inc</font></div>
<div><font face="arial, helvetica, sans-serif" size="2">+1.781.942.9975 (office)</font></div>
<div><font face="arial, helvetica, sans-serif" size="2">400 W. Cummings Park, Suite 1725<br></font></div>
<div><font face="arial, helvetica, sans-serif" size="2">Woburn, MA 01801 USA</font></div>
</div>
</div>
</div>
</div>
</body>
</html>
</div></blockquote>
</div></body>
</html>