ICANN ICANN Email List Archives

[gnso-irtp-b-jun09]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-irtp-b-jun09] For FINAL review - IRTP Part B Final Report - deadline 29 May 2011

  • To: "Marika Konings" <marika.konings@xxxxxxxxx>, <Gnso-irtp-b-jun09@xxxxxxxxx>
  • Subject: RE: [gnso-irtp-b-jun09] For FINAL review - IRTP Part B Final Report - deadline 29 May 2011
  • From: "Steele, Barbara" <BSteele@xxxxxxxxxxxx>
  • Date: Thu, 26 May 2011 16:33:35 -0400

All,

Since we have changed the EAC from Emergency Action Channel to Transfer
Emergency Action Contact, some of the language does not make sense to me
so I am suggesting a few edits for consideration.  

 

Transfer Emergency Action Contact (Append to Section 4)

Registrars will establish a Transfer Emergency Action Contact (TEAC) for
urgent communications relating to transfers. The goal of the TEAC is to
quickly establish a real-time conversation between registrars (in a
language that both parties can understand) in an emergency. Further
actions can then be taken towards a resolution, including initiating
existing (or future) transfer dispute or undo processes.

 

Communications to The TEACs will be reserved for use by ICANN-Accredited
Registrars, gTLD Registry Operators and ICANN Staff. The TEAC point of
contact may be designated as a telephone number or some other real-time
communication channel and will be recorded in, and protected by, the
ICANN RADAR system. 

 

Communications to a A TEAC must be initiated requested in a timely
manner, within a reasonable period of time following the alleged
unauthorized loss of a domain.

 

Messages sent via the TEAC communication channel must generate a
non-automated response by a human representative of the gaining
Registrar. The person or team responding must be capable and authorized
to investigate and address urgent transfer issues. Responses are
required within 4 hours of the initial request, although final
resolution of the incident may take longer.  

 

The losing registrar will report failures to respond to a TEAC
communication requests to ICANN Compliance and the registry operator.
Failure to respond to a TEAC communication request may result in a
transfer-undo in accordance with Section 6 of this policy and may also
result in further action by ICANN, up to and including non-renewal or
termination of accreditation.

 

Both parties will retain correspondence in written or electronic form of
any TEAC communication requests and responses, and share copies of this
documentation with ICANN and the registry operator upon request. This
documentation will be retained in accordance with Section 3.4 of the
Registrar Accreditation Agreement (RAA). Users of the TEAC communication
channel should report non-responsive Registrars to ICANN. Additionally,
ICANN may conduct periodic tests of the Registrar TEAC communication
channel in situations and a manner deemed appropriate to ensure that
registrars are indeed responding to TEAC messages. 

 

(Append to Section 6) 6  iv. Documentation provided by the Registrar of
Record prior to transfer that the Gaining Registrar has not responded to
a message initiated via the TEAC communication channel within the
timeframe specified in Section 4.

In addition, update section 6 to reflect that the registry, in case of a
transfer undo, will reverse the transfer and reset the registrar of
record filed to its original state ('In such case, the transfer will be
reversed and the Registrar of Record field domain name reset to its
original state').

 

Note that Annex E - Charter Question B - Standard Use Cases is still
referencing the ERTP so I expect that these should be updated to the
TEAC.  I believe that this e-mail provides the majority of the feedback
from the RySG but I may receive some additional feedback before COB
tomorrow which I will pass along if received.  Thanks to Marika and the
rest of the WG on all of your efforts to bring this to fruition.  

        
Barbara 

        

 

 

From: owner-gnso-irtp-b-jun09@xxxxxxxxx
[mailto:owner-gnso-irtp-b-jun09@xxxxxxxxx] On Behalf Of Marika Konings
Sent: Thursday, May 26, 2011 4:38 AM
To: Gnso-irtp-b-jun09@xxxxxxxxx
Subject: Re: [gnso-irtp-b-jun09] For FINAL review - IRTP Part B Final
Report - deadline 29 May 2011
Importance: High

 

For your information, you'll find posted on the wiki
(https://community.icann.org/display/gnsoirtpb/For+Review+by+29+May+2011
) an updated version that incorporates the edits and proposals discussed
on the mailing list yesterday. Apart from the attendance sheet, the
report is now complete as far as I can tell. Please share any comments /
edits / suggestions you may have with the mailing list as soon as
possible but no later than COB 29 May 2011.

 

Thanks,

 

Marika

 

From: Marika Konings <marika.konings@xxxxxxxxx>
Date: Wed, 25 May 2011 02:45:35 -0700
To: "Gnso-irtp-b-jun09@xxxxxxxxx" <Gnso-irtp-b-jun09@xxxxxxxxx>
Subject: [gnso-irtp-b-jun09] For FINAL review - IRTP Part B Final Report
- deadline 29 May 2011

 

Dear All,

 

You'll find posted on the wiki
(https://community.icann.org/display/gnsoirtpb/For+Review+by+29+May+2011
) the latest version of the Final Report. This version includes the
changes discussed on our call yesterday (including amongst others:
changing Emergency Action Channel to Transfer Emergency Action Contact;
updated notes to reflect WG discussion and conclusion on 60-day lock
recommendation; updated TEAC FAQ).

 

This version does not include updated language to reflect that the
60-day lock should be considered as part of the Issue Report on 'change
of control' (recommendation #4) as discussed yesterday, which will be
circulated later today on the mailing list for your review and comment
by James / Simonetta. In addition, it does not include any language
Barbara may submit to convey that in the case of a transfer undo
registries will update the registrar of record to its previous state.

 

Apart from the updated recommendation in relation to the 60-day lock
which you will have the opportunity to review separately, the report
notes that all the recommendations listed currently in the report have
the full consensus support from the Working Group.

 

Please review the latest version of the Final Report. You are encouraged
to share any comments/edits/suggestions you may have as soon as possible
but no later than COB 29 May 2011. The objective is to submit this
report to the GNSO Council and for publication on Monday 30 May 2011.

 

With best regards,

 

Marika



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy