<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;">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></body></html>