<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Hi Joyce, <br>
<br>
You are absolutely correct when it comes to the Registrar
requirements (nailed it 100% correctly)<br>
<br>
However I do not think we as IRT members are within scope to make
these requirements mandatory for this WHOIS migration, and if we
are, we might want to re-consider if we really want to go there. We
are going to open up a can of worms there the size of the empire
state building in my opinion. <br>
<br>
We should follow the RFC and migrate what we got if we got it, even
if they are optional, after all these are our requirements. <br>
<br>
If we need to go hunt down Registrar required data first, that is
optional in the RFC prior to the migration, then I predict we will
not bring this migration to a close within the next 6-10 years. We
are talking data that is older then ICANN and pre EPP, so we can
expect some missing fields here and there, but it has not been a
problem ever, so why make it a requirement ? If the migrated data
has some missing fields that you require for a transfer then simply
contact the Registrar and remind them of the requirements you
mentioned in your email. We are all used to that, or tell them they
need to have a WHOIS server, so business as usual in my opinion. <br>
<br>
The sooner we get this done, the less delay we will face. <br>
<br>
Have a good weekend, or what's left of it ;)<br>
<br>
Theo Geurts <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<span style="color: rgb(130, 130, 130); font-family: Roboto;
font-size: 14px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal; line-height: 18px;
orphans: auto; text-align: left; text-indent: 0px; text-transform:
none; white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important; float:
none; background-color: rgb(243, 243, 243);"><br>
</span>
<div class="moz-cite-prefix">On 12-2-2016 18:16, Joyce Lin wrote:<br>
</div>
<blockquote
cite="mid:42A5B474ADA147FF9078720FE55DB1C1@pdmn8jnwcn10kqp"
type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.23588">
<!--[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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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.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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:#1F497D;}
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="1027" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div>If the address, phone are not required, then ICANN's whois
accuracy compliance programs need to be modified,</div>
<div> </div>
<div><font size="2" face="Verdana"><a moz-do-not-send="true"
href="https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#whois-accuracy">https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#whois-accuracy</a></font></div>
<div>
<dir><font size="5" color="#262626" face="Helvetica-Light"><font
size="5" color="#262626" face="Helvetica-Light"><font
size="5" color="#262626" face="Helvetica-Light">
<p>3.3 <u>Public Access to Data on Registered Names</u>.
During the Term of this Agreement:</p>
</font></font></font></dir>
<font size="5" color="#262626" face="Helvetica-Light"><font
size="5" color="#262626" face="Helvetica-Light"><font
size="5" color="#262626" face="Helvetica-Light">
<p>3.3.1 At its expense, Registrar shall provide an
interactive web page and, with respect to any gTLD
operating a "thin" registry, a port 43 Whois service
(each accessible via both IPv4 and IPv6) providing free
public query-based access to up-to-date (i.e., updated
at least daily) data concerning all active Registered
Names sponsored by Registrar in any gTLD. Until
otherwise specified by a Consensus Policy, such data
shall consist of the following elements as contained in
Registrar's database:</p>
<p>3.3.1.1 The name of the Registered Name;</p>
<p>3.3.1.2 The names of the primary nameserver and
secondary nameserver(s) for the Registered Name;</p>
<p>3.3.1.3 The identity of Registrar (which may be
provided through Registrar's website);</p>
<p>3.3.1.4 The original creation date of the registration;</p>
<p>3.3.1.5 The expiration date of the registration;</p>
<p>3.3.1.6 The name and postal address of the Registered
Name Holder;</p>
<p>3.3.1.7 The name, postal address, e-mail address, voice
telephone number, and (where available) fax number of
the technical contact for the Registered Name; and</p>
<p>3.3.1.8 The name, postal address, e-mail address, voice
telephone number, and (where available) fax number of
the administrative contact for the Registered Name.</p>
</font></font></font></div>
<div> </div>
<div> </div>
<div>Am I misunderstanding the issue?</div>
<div> </div>
<div>Joyce</div>
<div> </div>
<div>----- Original Message ----- </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; BACKGROUND: #e4e4e4; font-color:
black"><b>From:</b> <a moz-do-not-send="true"
title="mcanderson@verisign.com"
href="mailto:mcanderson@verisign.com">Anderson, Marc</a> </div>
<div style="FONT: 10pt arial"><b>To:</b> <a
moz-do-not-send="true" title="rcarney@godaddy.com"
href="mailto:rcarney@godaddy.com">Roger D Carney</a> ; <a
moz-do-not-send="true"
title="gnso-impl-thickwhois-rt@icann.org"
href="mailto:gnso-impl-thickwhois-rt@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a></a>
</div>
<div style="FONT: 10pt arial"><b>Sent:</b> Thursday, February
11, 2016 5:09 PM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> Re:
[Gnso-impl-thickwhois-rt] Thick WhoIs IRT - contactvalidation
rules</div>
<div><br>
</div>
<div class="WordSection1">
<p class="MsoNormal"><span style="COLOR: #1f497d">Hey Roger,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">You raised a
very good point on the required fields. You missed out on
a fairly lively discussion on this topic during today’s
IRT meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">You are
correct in that this document reflects what is listed in
RFC 5733 which defines EPP for contacts. Per that RFC the
address and phone fields are not required so it would be
possible for Registrars to create contacts without passing
that data to the Registry.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">Krista put
this much more eloquently then I will be able to here, but
this does not reflect or impact what Registrars are
required to collect from Registrants or any of their
complete and accurate requirements. It is simply the
field validation rules that I am proposing we implement.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">I think it’s
good that Fabien added this to the agenda for today’s
meeting. Clearly from the call there are differing
opinions on if these fields (specifically Address 1 and
email) should be required by the Registry. I think this
is exactly the type of item the IRT should be discussing
and providing advice to ICANN staff on.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">If the
consensus of the IRT is that Registries should make those
fields mandatory then that is the advice we should provide
to ICANN staff, who are ultimately responsible for
drafting the consensus policy language. My request is
that the consensus policy language makes it clear one way
or another. For example, should it be left to Registry
policy (as the RFC seems to suggest), should those fields
be optional, or should those fields be mandatory.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d">Marc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"><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"> <a class="moz-txt-link-abbreviated" href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>] <b>On
Behalf Of </b>Roger D Carney<br>
<b>Sent:</b> Wednesday, February 03, 2016 5:48 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-impl-thickwhois-rt] Thick
WhoIs IRT - contact validation rules<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt">Good
Afternoon,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt">Thanks
Marc, this will be very helpful.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt">I just
want to confirm that I am reading this information
correctly. As I read this it appears that only Contact ID,
Postal info type, Name, City, Country, Email and Auth Info
(only those required by RFC 5733) are required to create a
contact, meaning that I can have a mostly blank address
block and blank phone, is that correct?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt">Roger<o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY: 'Times New
Roman','serif'; COLOR: #1f497d; FONT-SIZE: 12pt"><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: #e1e1e1 1pt solid;
BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p class="MsoNormal"><b>From:</b> <a
moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a></a>
[<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>]
<b>On Behalf Of </b>Anderson, Marc<br>
<b>Sent:</b> Monday, February 01, 2016 2:54 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Subject:</b> [Gnso-impl-thickwhois-rt] Thick WhoIs
IRT - contact validation rules<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear IRT Members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At the last IRT meeting we discussed that
in order for Registrars to properly assess the amount of
work involved in the backfill of thick data for existing
Registrations, it is necessary to know the fields required
and their validation rules.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Along with providing that information, I
want to make sure everyone has the same understanding of the
difference between a thin Registry and a thick Registry. A
thin domain registration does not have any contacts
associated with it. Currently, a Registrar cannot even
create contacts for the .com or .net Registry.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As part of a transition to thick, the
com/net registry would start supporting contacts by allowing
Registrars to add, modify and delete contacts. A thick
domain registration MUST have a contact ID for each contact
type (Registrant, Admin, Technical and Billing). The same
contact can be re-used across domains and/or contact types.
For example, if a Registrant were to register two domains in
a thick gTLD via the same Registrar, that Registrar could
create one contact and associate that with both domain
registrations or could create two separate contacts, one for
each domain. Either is fine, but I’m calling it out because
it will have an impact on the effort required by Registrars
to backfill thick data for existing registrations. There
are no other differences between a thin and a thick
registration.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I recognize that the Billing contact is
not universally required by all thick Registries. Some
(including Verisign) require it; some allow it as an
optional field and some don’t allow it at all. I don’t
believe this was addressed by the Thick WhoIs PDP working
group so it may be worth consideration by the IRT.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Attached please find a document
containing the contact validation rules that Verisign would
implement to assist Registrars in assessing impacts.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal">Marc Anderson<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table style="WIDTH: 278.25pt" class="MsoNormalTable"
border="0" width="371" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="PADDING-BOTTOM: 0in; PADDING-LEFT: 0in;
PADDING-RIGHT: 0in; PADDING-TOP: 0in" colspan="2">
<p class="MsoNormal"><img id="Picture_x0020_1"
alt="Verisign"
src="cid:part8.04090500.01000208@xs4all.nl"
border="0" height="2" width="371"><span
style="FONT-SIZE: 12pt"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="PADDING-BOTTOM: 15pt; PADDING-LEFT: 0in;
PADDING-RIGHT: 0in; PADDING-TOP: 11.25pt">
<p style="LINE-HEIGHT: 10.5pt" class="MsoNormal"><b><span
style="FONT-FAMILY: 'Helvetica','sans-serif';
COLOR: #006aaa; FONT-SIZE: 9pt">Marc Anderson</span></b><span
style="FONT-FAMILY: 'Helvetica','sans-serif';
COLOR: #6b6d71; FONT-SIZE: 8.5pt"><br>
Product Manager<br>
<a moz-do-not-send="true"
href="mailto:mcanderson@verisign.com">mcanderson@verisign.com</a><br>
<br>
m: 571.521.9943 t: 703.948.3404<br>
12061 Bluemont Way, Reston, VA 20190<br>
<br>
<a moz-do-not-send="true"
href="http://www.verisigninc.com/"><span
style="COLOR: #006aaa; FONT-SIZE: 9pt">VerisignInc.com</span></a>
<o:p></o:p></span></p>
</td>
<td style="PADDING-BOTTOM: 0in; PADDING-LEFT: 0in;
PADDING-RIGHT: 0in; PADDING-TOP: 11.25pt" valign="top">
<p class="MsoNormal"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="Picture_x0020_2" o:spid="_x0000_s1026" type="#_x0000_t75" alt="Verisign™" style='position:absolute;margin-left:10.65pt;margin-top:0;width:54.75pt;height:48pt;z-index:251659264;visibility:visible;mso-wrap-style:square;mso-width-percent:0;mso-height-percent:0;mso-wrap-distance-left:0;mso-wrap-distance-top:0;mso-wrap-distance-right:0;mso-wrap-distance-bottom:0;mso-position-horizontal:right;mso-position-horizontal-relative:text;mso-position-vertical:absolute;mso-position-vertical-relative:line;mso-width-percent:0;mso-height-percent:0;mso-width-relative:page;mso-height-relative:page' o:allowoverlap="f">
<v:imagedata src="cid:image002.gif@01D164EC.4B1FCDD0" o:title="Verisign™" />
<w:wrap type="square"/>
</v:shape><![endif]--><!--[if !vml]--><img alt="Verisign™"
src="cid:part11.04070402.02000600@xs4all.nl"
v:shapes="Picture_x0020_2" align="right"
height="64" width="73"><!--[endif]--><span
style="FONT-SIZE: 12pt"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p> </p>
<hr> _______________________________________________<br>
Gnso-impl-thickwhois-rt mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-impl-thickwhois-rt mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></pre>
</blockquote>
<br>
</body>
</html>