<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Team:</div>
<div><br>
</div>
<div>Today we discussed the question of whether or not P/P services should be required to respond to inquiries/reveal requests. I raised the idea that we could use something like the TEAC as a model. Below, I’ve pasted the applicable text from the transfer
policy (IRTP).</div>
<div><br>
</div>
<div>The TEAC model applies to our issues in that:</div>
<ol>
<li>The accredited registrar is required to respond promptly</li><li>There is no guaranteed outcome as a result of the inquiry, and</li><li>There is an understanding that ICANN will sanction registrars who do not respond, as well as registrars abusing TEAC for non-emergencies.</li></ol>
<div>However, as Michele and others point out, the TEAC model falls short of our needs in a few key areas:</div>
<ol>
<li>The TEAC is intended to address time-sensitive inter-registrar transactions, not for the general public to raise complaints.</li><li>Our work would require a more general purpose point of contact for use by third parties, LEA, etc.</li><li>The issues raised will be less time sensitive, reasonable response times would likely be measured in business days rather than hours.</li><li>There would be some penalties for abuse of the contact (e.g. Blocking future requests)</li></ol>
<div><br>
</div>
<div>Thanks—</div>
<div><br>
</div>
<div>J.</div>
<div><br>
</div>
<div>
<hr align="center" size=""3"" width=""95%"">
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<p style="margin: 0px 0px 8px; line-height: 21.749998092651367px; color: rgb(85, 85, 85); font-family: Arial, Heveltica, sans-serif; font-size: 15.454545021057129px; background-color: rgba(255, 255, 255, 0.6);">
Transfer Emergency Action Contact</p>
<p style="margin: 0px 0px 8px; line-height: 21.749998092651367px; color: rgb(85, 85, 85); font-family: Arial, Heveltica, sans-serif; font-size: 15.454545021057129px; background-color: rgba(255, 255, 255, 0.6);">
Registrars will establish a Transfer Emergency Action Contact ("<abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr>") for urgent communications relating to transfers. The goal of the <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> 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.</p>
<p style="margin: 0px 0px 8px; line-height: 21.749998092651367px; color: rgb(85, 85, 85); font-family: Arial, Heveltica, sans-serif; font-size: 15.454545021057129px; background-color: rgba(255, 255, 255, 0.6);">
Communications to TEACs will be reserved for use by ICANN-Accredited Registrars,<abbr title="generic Top Level Domain" style="border-bottom-width: 1px; border-bottom-style: dotted;">gTLD</abbr> Registry Operators and <abbr title="Internet Corporation for Assigned Names and Numbers" style="border-bottom-width: 1px; border-bottom-style: dotted;">ICANN</abbr> Staff.
The <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> 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 <abbr title="Internet Corporation for Assigned Names and Numbers" style="border-bottom-width: 1px; border-bottom-style: dotted;">ICANN</abbr> RADAR system. Communications to a <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> must
be initiated in a timely manner, within a reasonable period of time following the alleged unauthorized loss of a domain.</p>
<p style="margin: 0px 0px 8px; line-height: 21.749998092651367px; color: rgb(85, 85, 85); font-family: Arial, Heveltica, sans-serif; font-size: 15.454545021057129px; background-color: rgba(255, 255, 255, 0.6);">
Messages sent via the <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> 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.</p>
<p style="margin: 0px 0px 8px; line-height: 21.749998092651367px; color: rgb(85, 85, 85); font-family: Arial, Heveltica, sans-serif; font-size: 15.454545021057129px; background-color: rgba(255, 255, 255, 0.6);">
The losing registrar will report failures to respond to a <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> communication to <abbr title="Internet Corporation for Assigned Names and Numbers" style="border-bottom-width: 1px; border-bottom-style: dotted;">ICANN</abbr>Compliance
and the registry operator. Failure to respond to a <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> communication may result in a transfer-undo in accordance with Section 6 of this policy
and may also result in further action by <abbr title="Internet Corporation for Assigned Names and Numbers" style="border-bottom-width: 1px; border-bottom-style: dotted;">ICANN</abbr>, up to and including non-renewal or termination of accreditation.</p>
<p style="margin: 0px 0px 8px; line-height: 21.749998092651367px; color: rgb(85, 85, 85); font-family: Arial, Heveltica, sans-serif; font-size: 15.454545021057129px; background-color: rgba(255, 255, 255, 0.6);">
Both parties will retain correspondence in written or electronic form of any <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr>communication and responses, and share copies of this documentation
with <abbr title="Internet Corporation for Assigned Names and Numbers" style="border-bottom-width: 1px; border-bottom-style: dotted;">ICANN</abbr>and the registry operator upon request. This documentation will be retained in accordance with Section 3.4 of
the Registrar Accreditation Agreement (<abbr title="Registrar Accreditation Agreement" style="border-bottom-width: 1px; border-bottom-style: dotted;">RAA</abbr>). Users of the <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> communication
channel should report non-responsive Registrars to <abbr title="Internet Corporation for Assigned Names and Numbers" style="border-bottom-width: 1px; border-bottom-style: dotted;">ICANN</abbr>. Additionally, <abbr title="Internet Corporation for Assigned Names and Numbers" style="border-bottom-width: 1px; border-bottom-style: dotted;">ICANN</abbr> may
conduct periodic tests of the Registrar <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> communication channel in situations and a manner deemed appropriate to ensure that registrars
are indeed responding to <abbr title="Transfer Emergency Action Contact" style="border-bottom-width: 1px; border-bottom-style: dotted;">TEAC</abbr> messages.</p>
</div>
</body>
</html>