<html 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">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:"Comic Sans MS";
panose-1:3 15 7 2 3 3 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";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
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";}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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:1209803997;
mso-list-template-ids:-867516446;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
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">Taking my chair hat off and putting my RySG hat on, the timing of this seems questionable to many gTLD registries because of all the work that is going on with
RDDS. Implementing RDAP at this stage will not take advantage of any of the advantages of RDAP and instead just perpetuate what happens with the current Whois protocol under RDAP. The RySG is currently considering how to react to this.<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">Chuck<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"><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""> gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Carlton Samuels<br>
<b>Sent:</b> Tuesday, July 26, 2016 10:10 PM<br>
<b>To:</b> RDS WG<br>
<b>Subject:</b> [gnso-rds-pdp-wg] Fwd: New Registration Data Directory Services Requirements for gTLD Registries, Registrars to Take Effect in February 2017<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS"">Rolling, rolling....<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Comic Sans MS"">CAS<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><br>
==============================<br>
Carlton A Samuels<br>
Mobile: 876-818-1799<br>
<i><span style="color:#33CC00">Strategy, Planning, Governance, Assessment & Turnaround</span></i><br>
=============================<o:p></o:p></p>
</div>
</div>
<div>
<div>
<div style="border:solid #CCCCCC 1.0pt;padding:8.0pt 8.0pt 8.0pt 8.0pt">
<div>
<p class="MsoNormal" style="background:white"><span style="font-family:"Arial","sans-serif""><a href="http://www.icann.org/" target="_blank"><span style="text-decoration:none"><img border="0" id="_x0000_i1025" src="https://www.icann.org/sites/default/files/assets/icann-primary-94x94.jpg" alt="ICANN"></span></a><o:p></o:p></span></p>
<h2 style="background:white"><span style="font-family:"Arial","sans-serif"">News Alert<o:p></o:p></span></h2>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:7.5pt;margin-left:0in;background:white">
<span style="font-family:"Arial","sans-serif""><a href="https://www.icann.org/news/announcement-2016-07-26-en" target="_blank">https://www.icann.org/news/announcement-2016-07-26-en</a><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="margin-top:15.0pt;text-align:center;background:white">
<span style="font-family:"Arial","sans-serif"">
<hr size="2" width="100%" align="center">
</span></div>
<h2 style="margin-bottom:0in;margin-bottom:.0001pt;background:white"><span style="font-family:"Arial","sans-serif"">New Registration Data Directory Services Requirements for gTLD Registries, Registrars to Take Effect in February 2017<o:p></o:p></span></h2>
<p style="mso-margin-top-alt:11.25pt;margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;background:white">
<span style="font-family:"Arial","sans-serif"">26 July 2016<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Arial","sans-serif"">ICANN today announced that gTLD contracted parties must update their Registration Data Directory Services (RDDS) by 1 February 2017. Registries and registrars are required to implement
the new <a href="https://www.icann.org/rdap-gtld-profile" target="_blank">Registration Data Access Protocol (RDAP) gTLD Profile</a>. Registries must also implement the data specifications defined in the Registry Registration Data Directory Services
<a href="https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en" target="_blank">
Consistent Labeling and Display Policy</a>.<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Arial","sans-serif"">The RDAP gTLD Profile and the RDDS Consistent Labeling and Display Policy are the products of community efforts to improve the current system used to discover who controls a domain name.
This system comprises data retrieval protocols – WHOIS and a web-based version of WHOIS – and databases controlled by registries and registrars that contain domain registration information.<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Arial","sans-serif"">ICANN has notified contracted parties that they are responsible for modifying their systems within six months. ICANN consulted these parties when defining the new requirements and implementation
plans.<o:p></o:p></span></p>
<h3 style="background:white"><span style="font-family:"Arial","sans-serif"">Background<o:p></o:p></span></h3>
<p style="background:white"><span style="font-family:"Arial","sans-serif"">The Registration Data Access Protocol was developed by the
<a href="https://ietf.org/" target="_blank">Internet Engineering Task Force</a> to eventually replace the WHOIS protocol. This new protocol is superior to WHOIS in terms of data access security, support for international characters, extensibility, and in the
standardization of query, response and error messages. The RDAP gTLD Profile maps ICANN policy and contractual requirements onto technical requirements in order to standardize directory services across gTLD contracted parties.<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Arial","sans-serif"">The RDDS Consistent Labeling and Display Policy is a Consensus Policy developed and adopted in accordance with ICANN Bylaws. The policy is the result of recommendations adopted by the
GNSO Council after the completion of the Thick WHOIS Policy Development Process. The ICANN board adopted these recommendations on 7 February 2014.<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Arial","sans-serif"">The goal of the RDDS Consistent Labeling and Display Policy is to align the way registries and registrars label and display registration data outputs. The policy uses the output specifications
found in the 2013 Registrar Accreditation Agreement as the standard, thus only registries need to update their systems. Changes might include renaming or re-ordering fields and displaying additional data, such as registrar abuse contact information.<o:p></o:p></span></p>
<p style="background:white"><span style="font-family:"Arial","sans-serif"">For more information on these topics, visit:<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1;background:white">
<span style="font-family:"Arial","sans-serif""><a href="https://www.icann.org/rdap-gtld-profile" target="_blank">Registration Data Access Protocol gTLD Profile</a><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1;background:white">
<span style="font-family:"Arial","sans-serif""><a href="https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en" target="_blank">Registry RDDS Consistent Labeling and Display Policy</a><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1;background:white">
<span style="font-family:"Arial","sans-serif""><a href="https://www.icann.org/resources/pages/thick-whois-2016-06-27-en" target="_blank">Thick WHOIS Policy Implementation</a><o:p></o:p></span></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1;background:white">
<span style="font-family:"Arial","sans-serif""><a href="https://www.icann.org/policy/implementation" target="_blank">Policy Implementation at ICANN</a><o:p></o:p></span></li></ul>
<h3 style="background:white"><span style="font-family:"Arial","sans-serif"">About ICANN<o:p></o:p></span></h3>
<p style="background:white"><em><span style="font-family:"Arial","sans-serif"">ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or
a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants
from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers.
For more information please visit: <a href="https://www.icann.org/" target="_blank">
www.icann.org</a>.</span></em><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:white"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>