Re: [gnso-irtp-b-jun09] Emergency Action Channel Proposal

["Michele Neylon :: Blacknight" <michele@xxxxxxxxxxxxx>]

The captcha needs to be non-hackable as well

Mr. Michele Neylon
Blacknight
http://Blacknight.tel

Via iPhone so excuse typos and brevity

On 8 Apr 2011, at 21:38, "Diaz, Paul" <pdiaz@xxxxxxxxxxxxxxxxxxxx> wrote:

> 
> I would like to see the EAC contact data contained in RADAR.  That way, only 
> "authorized" POCs can access it, and ICANN will have a log file of who 
> attempts to gather the info.  
> 
> Also, is there some way for ICANN to also track how long it takes to generate 
> a response?  Perhaps a web form on RADAR (protected by a CAPTCHA) that 
> requires the respondent to log in and note when/how they responded to the EAC 
> request?  My concern is that if all communications are kept outside of 
> ICANN-managed channels it will be very difficult to measure compliance...
> 
> 
> ________________________________________
> From: owner-gnso-irtp-b-jun09@xxxxxxxxx 
> [mailto:owner-gnso-irtp-b-jun09@xxxxxxxxx] On Behalf Of Marika Konings
> Sent: Friday, April 08, 2011 4:08 PM
> To: Gnso-irtp-b-jun09@xxxxxxxxx
> Subject: [gnso-irtp-b-jun09] Emergency Action Channel Proposal
> 
> Dear All,
> 
> You'll find below a first draft of the Emergency Action Channel as prepared 
> by Mikey and James for the WGs consideration. Please review this proposal 
> ahead of next week's call and feel free to share your comments on the mailing 
> list in the meantime.
> 
> With best regards,
> 
> Marika
> 
> ============================
> 
> Emergency Action Channel
>  
> Registrars will establish an Emergency Action Channel (EAC) for urgent 
> communications relating to transfers.  The EAC will be reserved for use by 
> ICANN-Accredited Registrars, gTLD Registry Operators, and ICANN Staff.  The 
> EAC may be a designated as an email address, telephone number, orsome other 
> real-time communication 
>  
> Messages sent via the EAC must generate a non-automated response by a human 
> representative of the Registrar. This human respondent must be capable and 
> authorized to investigate and address urgent transfer issues. Responses are 
> due within 24 hours of the initial request, although final resolution of the 
> incident may take longer.  
>  
> Failure to respond to an EAC request will result in a transfer-undo and may 
> also result in further action by ICANN, up to and including non-renewal or 
> termination of accreditation.
>  
> Both parties should retain documentation of any EAC requests and responses, 
> and share copies of this documentation with ICANN upon request. Users of the 
> EAC should report non-responsive Registrars to ICANN. Additionally, ICANN 
> will conduct periodic tests (at least once per year, but no more than once 
> per quarter) of the Registrar EAC.  
>