<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)">
<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:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{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;}
--></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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Dennis,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thank you for providing the updated redlines of the CL&D and Transition policy documents.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">In the CL&D Policy document the “not to be deployed before date” was removed as agreed to on our last call (being that it occurs in the past). Under Implementation Notes, section 2 explains
the need for the “not to be deployed before date”. That section isn’t needed anymore and should be removed as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">In the Thick Transition policy document section 2.5 references Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”), but it does
not include the “or subsequent amendments thereto” language. In all other instances where the “Base Registry Agreement” is referenced, the “or subsequent amendments thereto” languages is included and I believe it is intended to be included in section 2.5
as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Section 2.4 requires registry operators to support contact operations by 1 Aug 2017 but the main purpose of section 2.4 is to define what we’ve referred to in the IRT as the “reduced validation
rules”. Basically instead of implementing contact support in compliance with RFC5733, the registry operator will only require the “contact:id, contact:postalinfo type, and contact:authinfo” fields. Per our discussions in the IRT this is intended to support
registrars during the backfill period (1 Aug 2017 to 1 Feb 2019). Based on my read of the policy the “reduced validation rules” don’t seem to have an end date. We don’t want them to extend indefinitely making a non RFC compliant implementation permanent.
Unless I’m missing something, I think this section should be tweaked to give an end date for the “reduced validation rules”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Marc Anderson<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;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""> gnso-impl-thickwhois-rt-bounces@icann.org [mailto:gnso-impl-thickwhois-rt-bounces@icann.org]
<b>On Behalf Of </b>Dennis Chang<br>
<b>Sent:</b> Tuesday, January 17, 2017 9:56 PM<br>
<b>To:</b> gnso-impl-thickwhois-rt@icann.org<br>
<b>Subject:</b> [EXTERNAL] [Gnso-impl-thickwhois-rt] Thick Whois Policy Language revisions from the IRT meeting on 17 January 2017<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Thick IRT,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thank you for your participation and support today in reviewing the public comment and decisions made to handle them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As promised, we’ve revised the policy language per our discussion at the meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">For CL&D Policy:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt">The “not to be deployed before date” was removed per the suggestion. For this policy, this is the only change.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt">No change was made for the suggestion to add a “provision for extension to the effective date” as the IRT agreed<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">For Transition Policy:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt">The clause containing “RDAP” was removed from section 2.10. The resulting language is exactly as Francisco provided in the chat which IRT agreed to.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt">Section 2.4 had two changes per the suggestions and agreements by the IRT<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt">a.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt">The word “starting” was changed to “by” to offer flexibility for the Registry Operator to provide support earlier.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt">b.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt"><contact:polstalinfo> was changed to <contact:postalinfo type> to identify the attribute more accurately<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt">Changes to section 2.8 and 2.9 were made to make it more readable. IRT was already in agreement with the intent of the language and this change was only to make it easier to understand.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt">4.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif"">
</span><span style="font-size:11.0pt">Regarding the suggestion to add “Alternative triggers for waivers,” there was no IRT agreement to make the change and therefore no change was made.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">This is considered the final review by the IRT before the publication and the announcement on 1 February 2017 per our plan.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">One more IRT meeting has been added for next Tuesday as you’ve requested.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">However, it can be cancelled if the IRT provides support for these finalized languages to be in alignment with the Policy Recommendation prior to the meeting date.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We look forward to your prompt review and continued support. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">— </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Kind Regards,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Dennis S. Chang</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">GDD Services & Engagement Program Director</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">+1 213 293 7889</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Skype: dennisSchang</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=dqLP1wJqBvDSYLKrSEaAkCi_Kv0Mk5D_d32n29DHCN8&m=a7quZ2sZnzk8sIcEpt-h4uzK3OqlOObfyWmvFNCp3jo&s=8B9VYb62f4Q3iIfshfZXaMKXg1DhtBAL2UVsn9I9S0A&e=">www.icann.org[icann.org]</a>
"One World, One Internet"</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</body>
</html>