<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>Steve & Team:</div>
<div><br>
</div>
<div>Michele covered some of this, but essential there are two key differences:</div>
<div><br>
</div>
<div>* The TEAC is available to a limited audience (Registrars & ICANN) for a limited purpose (Transfer problems). Making this a public-facing contact channel, open for generic complaints, will require sorting/processing/verification of requests. Committing
to a short timeframe is not commercially practical, unless it is an auto-responder (“thank you for contacting us….”), which we were trying to avoid with TEAC.</div>
<div><br>
</div>
<div>* The harms to a registrant whose domain name (and probably entire business) has been hijacked can be measured in minutes or hours. Complaints about a privacy protected domain name may also have associated harms, but the timescale is usually longer, e.g.
5 business days, etc.</div>
<div><br>
</div>
<div>Hope this helps.</div>
<div><br>
</div>
<div>Thanks-</div>
<div><br>
</div>
<div>J.</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Metalitz>, Steven <<a href="mailto:met@msk.com">met@msk.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, May 14, 2014 at 18:57 <br>
<span style="font-weight:bold">To: </span>James Bladel <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, "<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>" <<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: Obligation to Respond to Inquiries<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:762607677;
mso-list-template-ids:732837518;}
@list l1
{mso-list-id:1230993375;
mso-list-template-ids:-177800742;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">James, could you explain the basis for the assertion below that inquiries to accredited p/p/ providers would be less time sensitive than those to
registrars under IRTP? I imagine that sometimes this would be true, sometimes not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">One way to shed light on this might be to explain what constitutes an “emergency” under IRTP. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Steve Metalitz<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">
<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a> [<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>James M. Bladel<br>
<b>Sent:</b> Tuesday, May 13, 2014 12:09 PM<br>
<b>To:</b> <a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br>
<b>Subject:</b> [Gnso-ppsai-pdp-wg] Obligation to Respond to Inquiries<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Team:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">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).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">The TEAC model applies to our issues in that:<o:p></o:p></span></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">The accredited registrar is required to respond promptly<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">There is no guaranteed outcome as a result of the inquiry, and<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">There is an understanding that ICANN will sanction registrars who do not respond, as well as registrars abusing TEAC for non-emergencies.<o:p></o:p></span></li></ol>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">However, as Michele and others point out, the TEAC model falls short of our needs in a few key areas:<o:p></o:p></span></p>
</div>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">The TEAC is intended to address time-sensitive inter-registrar transactions, not for the general public to raise complaints.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">Our work would require a more general purpose point of contact for use by third parties, LEA, etc.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">The issues raised will be less time sensitive, reasonable response times would likely be measured in business days rather than hours.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">There would be some penalties for abuse of the contact (e.g. Blocking future requests)<o:p></o:p></span></li></ol>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thanks—<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">J.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">
<hr size="2" width="100%" align="center">
</span></div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:0in;line-height:16.3pt;background-color:rgba(255, 255, 255, 0.6)">
<span style="font-size: 11.5pt; font-family: Arial, sans-serif; color: rgb(85, 85, 85);">Transfer Emergency Action Contact<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:0in;line-height:16.3pt;background-color:rgba(255, 255, 255, 0.6)">
<span style="font-size: 11.5pt; font-family: Arial, sans-serif; color: rgb(85, 85, 85);">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.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:0in;line-height:16.3pt;background-color:rgba(255, 255, 255, 0.6)">
<span style="font-size: 11.5pt; font-family: Arial, sans-serif; color: rgb(85, 85, 85);">Communications to 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 TEAC must be initiated in a timely manner, within a reasonable period of time following the alleged unauthorized
loss of a domain.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:0in;line-height:16.3pt;background-color:rgba(255, 255, 255, 0.6)">
<span style="font-size: 11.5pt; font-family: Arial, sans-serif; color: rgb(85, 85, 85);">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.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:0in;line-height:16.3pt;background-color:rgba(255, 255, 255, 0.6)">
<span style="font-size: 11.5pt; font-family: Arial, sans-serif; color: rgb(85, 85, 85);">The losing registrar will report failures to respond to a TEAC communication to ICANNCompliance and the registry operator. Failure to respond to a TEAC communication 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.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;margin-left:0in;line-height:16.3pt;background-color:rgba(255, 255, 255, 0.6)">
<span style="font-size: 11.5pt; font-family: Arial, sans-serif; color: rgb(85, 85, 85);">Both parties will retain correspondence in written or electronic form of any TEACcommunication and responses, and share copies of this documentation with ICANNand 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.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</span>
</body>
</html>