<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23588">
<STYLE>@font-face {
        font-family: Calibri;
}
@font-face {
        font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
        MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
        MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
        MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 12pt
}
A:link {
        COLOR: #0563c1; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
        COLOR: #0563c1; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
        COLOR: #954f72; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
        COLOR: #954f72; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
        MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 12pt; mso-style-priority: 34
}
LI.MsoListParagraph {
        MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 12pt; mso-style-priority: 34
}
DIV.MsoListParagraph {
        MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 12pt; mso-style-priority: 34
}
SPAN.EmailStyle18 {
        FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal
}
SPAN.EmailStyle19 {
        FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle20 {
        FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal
}
SPAN.EmailStyle21 {
        FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
        FONT-SIZE: 10pt; mso-style-type: export-only
}
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 lang=EN-US link=#0563c1 bgColor=white vLink=#954f72>
<DIV>Marc,</DIV>
<DIV> </DIV>
<DIV>Regarding to your point <FONT color=#1f497d>“reduced validation
rules” don’t seem to have an end date....</FONT></DIV>
<DIV><FONT color=#1f497d></FONT> </DIV>
<DIV><FONT color=#1f497d>In the following section for registrar,
doesn't it spell out the end day is Feb. 1, 2019 because we MUST migrate all
required fields of existing domain names?</FONT></DIV>
<DIV><FONT color=#1f497d></FONT> </DIV>
<P style="MARGIN: 10pt 0in 0pt 0.25in; mso-list: l42 level1 lfo2"
class=FakeHeading1><FONT color=#5b9bd5><SPAN
style="FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'Times New Roman'"><STRONG><FONT
size=4>1.</FONT></STRONG><SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN><STRONG><FONT size=4><FONT face=Times>The following requirements
apply to Registrars only:<SPAN
style="FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'Times New Roman'"><o:p></o:p></SPAN></FONT></FONT></STRONG></FONT></P>
<DIV><SPAN
style="FONT-FAMILY: Calibri; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Between
1 August 2017 and 1 February 2019, Registrars MUST migrate to the relevant
Registry Operator all required fields of Existing Domain Names that are
available in the Registrar database that enable the Registry Operator to comply
with WHOIS (available via port 43) and web-based directory services requirements
described in Section 1 of ...</SPAN></DIV>
<DIV><SPAN
style="FONT-FAMILY: Calibri; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN> </DIV>
<DIV><SPAN
style="FONT-FAMILY: Calibri; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN> </DIV>
<DIV><SPAN
style="FONT-FAMILY: Calibri; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Joyce</SPAN></DIV>
<DIV><SPAN
style="FONT-FAMILY: Calibri; FONT-SIZE: 12pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: Calibri; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=mcanderson@verisign.com
href="mailto:mcanderson@verisign.com">Anderson, Marc</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=dennis.chang@icann.org
href="mailto:dennis.chang@icann.org">dennis.chang@icann.org</A> ; <A
title=gnso-impl-thickwhois-rt@icann.org
href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, January 23, 2017 7:03
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Gnso-impl-thickwhois-rt]
Thick Whois Policy Language revisions from the IRT meeting on 17 January
2017</DIV>
<DIV><BR></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-SIZE: 11pt">Dennis,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">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="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">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="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">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="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">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="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">Thank
you,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d; FONT-SIZE: 11pt">Marc
Anderson<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="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">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
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: 11pt">Dear Thick
IRT,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt">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: 11pt">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: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt">For CL&D
Policy:<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">1.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">2.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt">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: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt">For Transition
Policy:<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">1.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">2.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt">Section 2.4 had two changes per the
suggestions and agreements by the IRT<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in; MARGIN-LEFT: 1in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">a.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in; MARGIN-LEFT: 1in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">b.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt"><contact:polstalinfo> was changed
to <contact:postalinfo type> to identify the attribute more
accurately<o:p></o:p></SPAN></P>
<P style="TEXT-INDENT: -0.25in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">3.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt">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 style="TEXT-INDENT: -0.25in" class=MsoListParagraph><SPAN
style="FONT-SIZE: 11pt">4.</SPAN><SPAN
style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 7pt">
</SPAN><SPAN style="FONT-SIZE: 11pt">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: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt">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: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt">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: 11pt">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: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt">We look forward to your
prompt review and continued support. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt"> </SPAN><o:p></o:p></P>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="COLOR: black; FONT-SIZE: 10.5pt">— </SPAN><o:p></o:p></P></DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10.5pt">Kind
Regards,</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10.5pt">Dennis S.
Chang</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10.5pt">GDD Services
& Engagement Program Director</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10.5pt">+1 213 293
7889</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10.5pt">Skype:
dennisSchang</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 10.5pt"><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>
<P>
<HR>
<P></P>_______________________________________________<BR>Gnso-impl-thickwhois-rt
mailing
list<BR>Gnso-impl-thickwhois-rt@icann.org<BR>https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</BLOCKQUOTE></BODY></HTML>