<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>You should post that to the group – we were wondering how this took place</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>David Conrad <<a href="mailto:david.conrad@icann.org">david.conrad@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, November 4, 2014 at 12:50 PM<br>
<span style="font-weight:bold">To: </span>Becky Burr <<a href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</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 style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Becky,
<div><br>
<div>
<div>On Nov 4, 2014, at 6:50 AM, Burr, Becky <<a href="mailto:Becky.Burr@neustar.biz">Becky.Burr@neustar.biz</a>> wrote:</div>
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; 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>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>The authorization step is _after_ the confirmation of the request by the TLD manager(s). By the time a change request is sent for authorization, all parties involved have already provided explicit consent for the change to be processed.</div>
</div>
<br>
</div>
<div>Regards,</div>
<div>-drc</div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>