<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>On David Conrad’s point about the need for authorization introducing latency issues, etc., - valid point. On the other hand, if we were to recommend doing away with that step, how do we ensure that an incumbent operator has appropriate notice and an opportunity
to contest revocation/redelegation/transfers?</div>
<div><br>
</div>
<div>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; "><span style="font-size: 9pt; font-family: Arial, sans-serif;">J. Beckwith Burr<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; "><b><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Neustar, Inc. /</span></b><span style="font-size: 9pt; font-family: Arial, sans-serif;"> Deputy
General Counsel and Chief Privacy Officer<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; "><span style="font-size: 9pt; font-family: Arial, sans-serif;">1775 Pennsylvania Avenue NW, Washington, DC 20006<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; "><span style="font-size: 9pt; font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Office</span><span style="font-size: 9pt; font-family: Arial, sans-serif;">: + 1.202.533.2932 <span style="color: rgb(6, 134, 88); "> Mobile</span>:
+1.202.352.6367 <span style="color: rgb(6, 134, 88); ">/ <a href="mailto:becky.burr@neustar.biz" style="color: purple; ">becky.burr@neustar.biz</a> / www.neustar.biz</span></span></p>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Greg Shatan <<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, November 4, 2014 at 9:11 AM<br>
<span style="font-weight:bold">To: </span>Robert Guerra <<a href="mailto:rguerra@privaterra.org">rguerra@privaterra.org</a>><br>
<span style="font-weight:bold">Cc: </span>RFP3 <<a href="mailto:cwg-rfp3@icann.org">cwg-rfp3@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CWG-RFP3] Coordination of Subgroup 3<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Milton,
<div><br>
</div>
<div>I was not falling prey to anything; I am taking into account the division of work email circulated by our Co-Chair with regard to our subgroup, specifically Item "B" (see below). In our subgroup, we need to account for transitioning this aspect of NTIA's
role, even if a possible post-transition option is abolishing that element of the NTIA's role. Since this is part of our assigned task, I think it is important to keep it in mind as an Objective.</div>
<div><br>
</div>
<div>Greg</div>
<div><br>
</div>
<div>---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Lise Fuhr</b> <span dir="ltr"><<a href="mailto:lise.fuhr@difo.dk">lise.fuhr@difo.dk</a>></span><br>
Date: Thu, Oct 30, 2014 at 3:12 PM<br>
Subject: [CWG-Stewardship] Work break down RFPIII<br>
To: <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<br>
<br>
<div lang="EN-GB" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Dear All, <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The objective is to finalize the work breakdown structure at our next meeting.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">An issue arose at our meeting today:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><u></u><span style="font-size: 10pt; color: rgb(31, 73, 125);">·<span style="font-size: 7pt; font-family: 'Times New Roman';"> </span></span><u></u>Breaking up CWG-RFP3 into 3A and 3B as presented<span style="color:rgb(31,73,125)">:<br>
<br>
</span>A. Contract Manager for the IANA Functions contractor<br>
B. Root Zone Management.<br>
<span style="color:rgb(31,73,125)"><br>
</span>Although there were some objections on the list prior to the call there were none voiced during the call and I concluded that we should keep this separation at least until our next meeting. The main reason for this is that the SSAC68 report identifies
two very distinct functions performed by the NTIA in IANA Functions oversight and accountability and this group is in charge of identifying how to best transition both.<span style="color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal">If you have any comments please post these to the list prior to our next meeting on November 4.<u></u><u></u></p>
<div>
<p class="MsoNormal">Thank You<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Best regards.<span class=""><font color="#888888"><u></u><u></u></font></span></p>
<span class=""><font color="#888888">
<p class="MsoNormal">Lise<u></u><u></u></p>
</font></span></div>
</div>
</div>
<br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Dstewardship&d=AAMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=1neaAuBbYr8wN6tDq4uJTOIR6c2psQy5xx96cFoOHIo&s=d_xl3ZTAbhFtLGMi4mNxty2bSpfFzquRmgRIaVIN-xI&e=" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Nov 4, 2014 at 8:33 AM, Robert Guerra <span dir="ltr">
<<a href="mailto:rguerra@privaterra.org" target="_blank">rguerra@privaterra.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">David,
<div><br>
</div>
<div>You and Milton raise some important points, that being:</div>
<div><br>
</div>
<div>- RZF need to be reviewed for technical accuracy</div>
<div>- An authorizer process step exists now . In a post NTIA solution, something similar is needed. There is a need to evaluate if a single or multiple authorizers are needed as well as cost that might entail.</div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>robert</div>
</font></span>
<div><br>
<div>
<blockquote type="cite">
<div>
<div class="h5">
<div>On Nov 4, 2014, at 3:45 AM, David Conrad <<a href="mailto:david.conrad@icann.org" target="_blank">david.conrad@icann.org</a>> wrote:</div>
<br>
</div>
</div>
<div>
<div>
<div class="h5"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Hi,</span>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<br>
<div>
<div>On Nov 3, 2014, at 7:41 PM, Milton L Mueller <<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailto-3Amueller-40syr.edu&d=AAMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=1neaAuBbYr8wN6tDq4uJTOIR6c2psQy5xx96cFoOHIo&s=zskmfP9dPD5PK8veRgSxv5LPL-E20-wDVGxtgkAd1SI&e=" style="color:purple;text-decoration:underline" target="_blank">mueller@syr.edu</a>>
wrote:</div>
<blockquote type="cite">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">You may be falling prey to a common misconception – the idea that NTIA authority over RZF actually ensured the technical accuracy of RZ file changes. It didn’t. The Commerce
Department staff member who reviewed the changes was not a DNS expert.<span> </span></span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
True.</div>
<div><br>
<blockquote type="cite">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">NTIA was there to make sure that the RZF changes were _<i>authorized</i>_ and it did that primarily to ensure antitrust immunity to Verisign.<span> </span></span></div>
</div>
</div>
</blockquote>
<div><br>
</div>
Hadn't heard that one before (not saying it isn't true, just that I hadn't heard it).</div>
<div><br>
</div>
<div>My understanding is that by the terms of (I believe) amendment 11 of the (now) NTIA/Verisign cooperative agreement, Verisign is not permitted to modify the root zone without explicit permission by NTIA. NTIA authorizes those changes by verifying ICANN
has followed documented policy/conformance to the IANA Functions contract in processing root zone change requests. It is probably worth noting NTIA has never not authorized a change.</div>
<div><br>
<blockquote type="cite">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Ergo, I don’t think you need a “final check” of any and every RZ change, so much as you need serious recourse if someone makes an unauthorized change. I think we can trust
the registries to tell us if the changes are inaccurate.</span></div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
Indeed. Speaking as someone charged with implementation, it turns out that the authorization requirement adds a non-trivial amount of complexity, fragility, and latency to the root zone management system. Given, by definition, all changes to the root zone
are public and any missteps would generate a vast array of negative repercussions, the community may wish to consider whether the complexity, fragility, and latency costs outweigh the benefits.</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<br>
</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
Further, if the community does decide they wish to keep the authorization function, a number of questions quickly arise: exactly what does the community want to replace the authorization performed by NTIA with? Does the community want a single authorizer or
multiple authorizers? If multiple, how many? What exactly would those authorizers authorize? How would they be chosen? Would they expect to be paid for the authorization service? Etc.</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<br>
</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
Regards,</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
-drc</div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
(ICANN CTO, but speaking only for myself. Really.)</div>
</div>
</div>
<span class=""><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Cwg-rfp3
mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="mailto:Cwg-rfp3@icann.org" target="_blank">Cwg-rfp3@icann.org</a></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Drfp3&d=AAMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=1neaAuBbYr8wN6tDq4uJTOIR6c2psQy5xx96cFoOHIo&s=oskxyKnnH_JGwHr6GYcA-vUV2N0T7OETibZ8NmksR3k&e=" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-rfp3</a></span></span></div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
Cwg-rfp3 mailing list<br>
<a href="mailto:Cwg-rfp3@icann.org">Cwg-rfp3@icann.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_cwg-2Drfp3&d=AAMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=1neaAuBbYr8wN6tDq4uJTOIR6c2psQy5xx96cFoOHIo&s=oskxyKnnH_JGwHr6GYcA-vUV2N0T7OETibZ8NmksR3k&e=" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-rfp3</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>