[CWG-RFP3] Coordination of Subgroup 3

Burr, Becky Becky.Burr at neustar.biz
Tue Nov 4 17:56:13 UTC 2014


You should post that to the group – we were wondering how this took place

J. Beckwith Burr
Neustar, Inc. / Deputy General Counsel and Chief Privacy Officer
1775 Pennsylvania Avenue NW, Washington, DC 20006
Office: + 1.202.533.2932  Mobile:  +1.202.352.6367  / becky.burr at neustar.biz<mailto:becky.burr at neustar.biz> / www.neustar.biz

From: David Conrad <david.conrad at icann.org<mailto:david.conrad at icann.org>>
Date: Tuesday, November 4, 2014 at 12:50 PM
To: Becky Burr <becky.burr at neustar.biz<mailto:becky.burr at neustar.biz>>
Cc: RFP3 <cwg-rfp3 at icann.org<mailto:cwg-rfp3 at icann.org>>
Subject: Re: [CWG-RFP3] Coordination of Subgroup 3

Becky,

On Nov 4, 2014, at 6:50 AM, Burr, Becky <Becky.Burr at neustar.biz<mailto:Becky.Burr at neustar.biz>> wrote:
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?

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.

Regards,
-drc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cwg-rfp3/attachments/20141104/4528c8cf/attachment.html>


More information about the Cwg-rfp3 mailing list