<<<
Chronological Index
>>> <<<
Thread Index
>>>
[gnso-irtp-b-jun09] Emergency Action Channel Proposal
- To: "Gnso-irtp-b-jun09@xxxxxxxxx" <Gnso-irtp-b-jun09@xxxxxxxxx>
- Subject: [gnso-irtp-b-jun09] Emergency Action Channel Proposal
- From: Marika Konings <marika.konings@xxxxxxxxx>
- Date: Fri, 8 Apr 2011 13:07:34 -0700
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.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|