<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div><div class="plaintext"><p dir="auto">An important distinction to make is whether we are using “delegation” in a technical sense or a business sense.</p>
<p dir="auto">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 dir="auto">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 dir="auto">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 dir="auto">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 dir="auto">Jim</p>
<br /><br /><br /><p dir="auto">On 1 Dec 2021, at 14:43, Jothan Frakes wrote:</p>
</div><blockquote class="embedded"><div id="7C6CE784-8D1B-4A1A-B27C-B611F55F58AE"><!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 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">
<div>
<div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr"><br>
Jothan Frakes<br>
Tel: +1.206-355-0230<br>
<br></div>
</div>
</div>
<br></div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Dec 1, 2021 at 10:47 AM 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">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" 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>
</body>
</html>
</div></blockquote>
</div></body>
</html>