<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
{font-family:"Arial Black";
panose-1:2 11 10 4 2 1 2 2 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";}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-family:"Cambria","serif";
color:#243F60;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{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:1231386128;
mso-list-template-ids:1264493124;}
@list l0:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1363942566;
mso-list-template-ids:1630059936;}
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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for laying out so nicely, Jim.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For allocation of reserved names, Neustar prefers Option 2.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For handling of Claims for reserved names with marks in the TMCH, Neustar prefers Option 4 first, but if still required to support Claims, then Option 3.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">--Roy Dykes<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> tmch-tech-bounces@icann.org [mailto:tmch-tech-bounces@icann.org]
<b>On Behalf Of </b>Gould, James<br>
<b>Sent:</b> Wednesday, May 21, 2014 4:23 PM<br>
<b>To:</b> Nic Steinbach; Rubens Kuhl<br>
<b>Cc:</b> tmch-tech@icann.org; gtld-tech@icann.org<br>
<b>Subject:</b> Re: [tmch-tech] RPM Requirement of Supporting Claims Service for Release or Allocation of Reserved Domain Names<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Nic,<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">I agree that finding a consistent / standard approach to this would benefit all participants. There are two problems that need to be addressed for these names,
which include:<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 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Allocation of the reserved names
<o:p></o:p></span></li></ol>
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Should reserved name applications get created and allocated per draft-ietf-eppext-launchphase?
<o:p></o:p></span></li></ol>
</ol>
<ol start="1" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The creation of applications may be mixed with registrations. This is not a launch phase, but a release of a set of domains. For registrars not explicitly participating in the release of the
reserved names, it would be unclear why an application was created over a registration. One mechanism to mitigate this is to require the <launch:create> extension with the “type” attribute set to “application” for the reserved domains. I’m assuming that
the check response would return back unavailable for reserved domains with a reason like “reserved domain” so not to mislead non-participating registrars. <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 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Following the full application state machine, as defined in draft-ietf-eppext-launchphase, may be overkill for releasing a smaller set of names. Registrars may be discouraged from participating
based on the level of complexity associated with the application state machine.<o:p></o:p></span></li></ol>
</ol>
</ol>
<ol start="1" type="1">
<ol start="2" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Should an allocation string / token be used to authorize the registration of a reserved domain name that is made available out-of-band? For example, an auction provider could provide the allocation
string / token to the winner of the auction and the registrar would pass it with the domain create of the reserved domain via either the RFC 5731 authorization info or another EPP extension.
<o:p></o:p></span></li></ol>
</ol>
<ol start="1" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The registries and the registrars would need to support a new mechanism for creating a reserved domain in using the allocation string / token. <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 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">This is simpler than using the application state machine of draft-ietf-eppext-launchphase. <o:p></o:p></span></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Handling the claims service for reserved names that have marks in the TMCH
<o:p></o:p></span></li></ol>
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level2 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">This problem was the point of the initial list posting, where the claims service would need to be re-enabled by registries and participating registrars for use only with the reserved domains
potentially well past the claims launch phase. This assumes that a registry does not run claims indefinitely. Since reserved names would probably not be released all at once, this cycle would have to be repeated many times for each TLD. <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 level2 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The options include:
<o:p></o:p></span></li></ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Registries and participating registrars must fully support the claims service based on the RPM requirements. The registry must re-enable the claims check service, must re-enable the claims acknowledgement
verification, and must re-enable the LORDN interface for a subset of the domain names. The registrars must re-enable the use of the claims check service, must re-enable their interface with the CNIS, and must re-enable passing the claims acknowledgement for
reserved domains that have marks. <o:p></o:p></span></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">This is a great amount of overhead for the registries and the registrars for releasing a set of domain names potentially well past the claims launch period. <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 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">This will discourage registrar participation.<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 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The registries must keep support for claims indefinitely that can be enabled later. <o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="2" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Registries and participating registrars support asynchronous claims acknowledgement out-of-band of EPP.
<o:p></o:p></span></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The registries would allow the creation of reserved domains that will be put in pendingCreate if there is a matching mark. The claims acknowledge would need to be passed to the registry out-of-band
to allocate the domain.<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 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Reserved domains that don’t have matching marks will be immediately allocated, assuming that the registry does not have a pendingCreate model. <o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="3" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">As Roy suggested, require claims service notification from the registries to the TMCH without the front-end claims service requirements. I would loosely define this as “Claims Lite”, where the
TMCH and subsequently ICANN will receive systematic notification of reserved name allocations that have marks. We could consider broadening the notifications to include providing the initial reserved name list, release of the reserved domains, and finally
allocation of all reserved domains. <o:p></o:p></span></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The registrars would not be impacted at all since there is no need to present the claims notice to the registrant, so therefore it will encourage registrar participation. <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 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Registries would need to support a new LORDN-like interface with the TMCH that may require a broader set of systematic notifications for monitoring and visibility by the mark holders and ICANN.
<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 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Registries would not be required to support the claims check service and claims acknowledge validation. <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 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">This could be an alternate approach to what is currently defined in the RPM requirements for the claims service. <o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="4" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level3 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Don’t require support for the claims service for the releasing of reserved names.
<o:p></o:p></span></li></ol>
</ol>
</ol>
<ol start="2" type="1">
<ol start="2" type="1">
<ol start="4" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level4 lfo1">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">The reserved domains will be registered and allocated after the required claims launch period, where other domains registered and allocated during the “open” phase have no equivalent requirement.
<o:p></o:p></span></li></ol>
</ol>
</ol>
</ol>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"> I prefer option 2 for the “Allocation of the reserved names” problem. I prefer option 4 first, followed by option 3, for the “Handling the claims service for
reserved names that have marks in the TMCH” problem. <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>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Are there any other problems or options that need to be considered? Are there any preferences from both registries and registrars? <o:p></o:p></span></p>
</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 class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">-- </span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"> </span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black">JG</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"> </span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"><img width="75" height="66" id="_x0000_i1025" src="cid:image001.png@01CF769B.68608C40"></span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"> </span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#0C1D63">James Gould</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#292A2D">Principal Software Engineer</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#0000DB"><a href="mailto:jgould@verisign.com">jgould@verisign.com</a></span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#292A2D"> </span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#292A2D">703-948-3271 (Office)</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#27292B">12061 Bluemont Way</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#27292B">Reston, VA 20190</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#0C1D63">VerisignInc.com</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</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 style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Nic Steinbach <<a href="mailto:nic@name.com">nic@name.com</a>><br>
<b>Date: </b>Monday, May 19, 2014 at 10:32 AM<br>
<b>To: </b>Rubens Kuhl <<a href="mailto:rubensk@nic.br">rubensk@nic.br</a>><br>
<b>Cc: </b>"<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>" <<a href="mailto:tmch-tech@icann.org">tmch-tech@icann.org</a>>, "<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>" <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br>
<b>Subject: </b>Re: [tmch-tech] RPM Requirement of Supporting Claims Service for Release or Allocation of Reserved Domain Names<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>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">It would be nice to have a standard way of addressing this - supporting claims indefinitely, pursuing an alternate method like the one mentioned by Roy or any
other solution - but I think given the TLD roll out so far standardization across all platforms seems unlikely. A PDP would not have tangible results before some registries would like to pursue this path. I would be surprised if a registry didn't implement
a delayed reserved rollout along these lines this quarter and it will only pick from there.
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Instead registries need to realize the development burdens on registry operators and registrars so that there reserved rollout is as standard as possible and
enticing enough to make these burdens worthwhile. Given the nature of these names - it is certainly possible to make the program enticing. I would guess that as least within a registry operator, the mechanism for addressing both the claims and the validation
piece that goes along with this would be standard. <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">We fully expect to support various models as long as the benefits and requirements are communicated clearly and translate to a sound business decision for all
parties involved. <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">On Mon, May 19, 2014 at 8:03 AM, Rubens Kuhl <<a href="mailto:rubensk@nic.br" target="_blank">rubensk@nic.br</a>> wrote:<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>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Seth,
<o:p></o:p></span></p>
<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">Have you been able to use GDD Portal to get eternal claims service ? It seems to require a fixed date when submitting TLD Startup Info... <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"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Rubens<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"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Em 19/05/2014, à(s) 11:00:000, Seth Goldman <<a href="mailto:sethamin@google.com" target="_blank">sethamin@google.com</a>> escreveu:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br>
<br>
<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">We are planning to offer an eternal claims service on all our TLDs. It's better for trademark holders, plus it's operationally simpler.
<o:p></o:p></span></p>
<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">Seth<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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">On Mon, May 19, 2014 at 7:53 AM, Gould, James <<a href="mailto:JGould@verisign.com" target="_blank">JGould@verisign.com</a>> wrote:<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">According to section 2.4.3 of the Rights Protection Mechanism (RPM) Requirements, it states:<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<div>
<blockquote style="margin-left:30.0pt;margin-right:0in">
<p><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">If Registry Operator reserves a domain name from registration in accordance with Section 2.6 of the Agreement and Specification 5 of the Agreement and thereafter (i) releases for
Allocation or registration such reserved domain name at any time prior to the start date of the Claims Period, such domain name MUST be treated like any other domain name for any applicable Sunrise Period, Limited Registration Period, Launch Program or Claims
Period, or (ii) <b>releases for Allocation or registration such reserved domain name at any time following the start date of the Claims Period, such domain name MUST be subject to the Claims Services (as defined in Section 3) for a period of ninety (90) calendar
days following the date Registry Operator releases such domain name for registration as long as the Trademark Clearinghouse (or any ICANN-designated successor thereto) remains in operation. </b><o:p></o:p></span></p>
</blockquote>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">For registries that plan on releasing domain names after the Claims Period, such as to support the release of premium domain names or 2 character domain names,
they will have to support the Claims Services well past the Claims Period (potentially years). This represents a costly burden to the registries having to indefinitely download the DNL list, support the claims check, validating the domain creates against
the DNL list for a subset of domain names, and support the TMCH LORDN interface. This also represents a costly burden to registrars or discourages registrar participation in supporting the release of reserved domain names. The registrars would need to know
to use the claims check, use the CNIS for presenting the claims notice, and passing the claims acknowledgement indefinitely. <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">Since this is a complex issue impacting registries and registrars, what approaches are being considered? Do the registries and registrars have any issues with
supporting the Claims Service indefinitely? <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">Please respond with your thoughts and concerns.<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">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>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#888888">-- </span><span style="font-family:"Cambria","serif";color:#888888"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#888888"> </span><span style="font-family:"Cambria","serif";color:#888888"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#888888">JG</span><span style="font-family:"Cambria","serif";color:#888888"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#888888"> </span><span style="font-family:"Cambria","serif";color:#888888"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#888888"><3CA91A0B-A6C1-43A5-AC92-8E23C9AD1B74[99].png></span><span style="font-family:"Cambria","serif";color:#888888"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:black"> </span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#0C1D63">James Gould</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#292A2D">Principal Software Engineer</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#0000DB"><a href="mailto:jgould@verisign.com" target="_blank">jgould@verisign.com</a></span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#292A2D"> </span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#292A2D"><a href="tel:703-948-3271" target="_blank">703-948-3271</a> (Office)</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#27292B">12061 Bluemont Way</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#27292B">Reston, VA 20190</span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";color:#0C1D63"><a href="https://urldefense.proofpoint.com/v1/url?u=http://VerisignInc.com&k=lQ50IrZ4n2wmPbDBDzKBYw%3D%3D%0A&r=ltQ01elRBpTiAAu3PBAB%2FCClpNW2eBk%2Fh3quV%2BehdXA%3D%0A&m=5RaoUN3lqPOOppijPcWEvqf78Pw0YZH9KosNrcjsRVU%3D%0A&s=ea1e5226d4fa5ff4a08e3bd862009bf4086bc0da3a2be0624492efbc1e8800ae" target="_blank">VerisignInc.com</a></span><span style="font-family:"Cambria","serif";color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<h5><span style="font-family:"Calibri","sans-serif";color:gray">“This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged,
confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly
prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”
</span><span style="font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></h5>
</div>
</div>
</blockquote>
</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>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><br>
<br clear="all">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</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"><b><i><span style="font-size:10.5pt;font-family:"Arial Black","sans-serif";color:#888888">Nic Steinbach</span></i></b><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#888888">Strategic Relationship Manager<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#888888">209.681.7838<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:#888888"><img border="0" width="96" height="18" id="_x0000_i1026" src="http://name.com/images/email-signature-logo1.jpg"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>