<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Hi Joyce, <br>
<br>
You are right that option two is most likely to put us on a fast
track. Keep in mind however that new registrations will have to
comply with the RAA 2013 WHOIS SPEC. No matter who the Registry is,
or what checks or what RFC they use, you still got to comply with
the RAA 2013. <br>
<br>
This is not factual, but more as an example. We need to make sure
that legacy data and new data are treated different. As there have
been many versions of the RAA with different obligations there. So
new data should be RAA 2013 compliant. <br>
<br>
If I am not making sense, blame it on a 16 hour workday with tons of
meetings. Those meetings suck the energy out of everyone that is
alive. <br>
<br>
Happy to discuss and explore the options at the next call. <br>
<br>
Best, <br>
<br>
Theo <br>
<br>
<div class="moz-cite-prefix">On 7-4-2016 21:33, Joyce Lin wrote:<br>
</div>
<blockquote
cite="mid:71435FABEFD844E0AD9F9F92A502C581@pdmn8jnwcn10kqp"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.23588">
<style>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: SimSun;
}
@font-face {
font-family: SimSun;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: @SimSun;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
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
}
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]-->
<div>Option 2 definitely will expedite the transition. </div>
<div> </div>
<div>I'm not sure if the process I'm thinking would be feasible
and workable, especially on the registries' side.</div>
<div> </div>
<div>1. registrars upload existing registrations data to the
registry and they will all go through because the registry does
not check the existing data integrity,</div>
<div> </div>
<div>2. at certain point after the upload has been completed and
the registry has all the registrations data, new registrations
data will be checked. And if the registration data does not
comply with whatever would be set then, the registration will
fail, and the RNH will be forced to modify the data in order to
successfully register a new domain. Since the data has been
updated at the registry's the previous registrations data of
this RNH will be automatically updated.</div>
<div> </div>
<div>Joyce</div>
<div>007names.com</div>
<div> </div>
<div> </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="met@msk.com" href="mailto:met@msk.com">Metalitz,
Steven</a> </div>
<div style="FONT: 10pt arial"><b>To:</b> <a
moz-do-not-send="true" title="fabien.betremieux@icann.org"
href="mailto:fabien.betremieux@icann.org">'Fabien
Betremieux'</a> ; <a moz-do-not-send="true"
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> Thursday, April 07,
2016 9:49 AM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> Re:
[Gnso-impl-thickwhois-rt] Reminder - Proposal for the
Transition of Existing Registrations from Thin to Thick</div>
<div><br>
</div>
<div class="WordSection1">
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">I
support the recommendation to proceed with option 2. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Steve
Metalitz <o:p></o:p></span></p>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: #88162e; FONT-SIZE:
11pt"><o:p> </o:p></span></b></p>
</div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; 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"> <a moz-do-not-send="true"
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>Fabien Betremieux<br>
<b>Sent:</b> Thursday, April 07, 2016 7:54 AM<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] Reminder -
Proposal for the Transition of Existing Registrations
from Thin to Thick<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Dear
IRT members,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">This
is a friendly reminder that your contribution on this
topic would be appreciated by Friday 8 April COB in your
time zone.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Thank
you for your attention<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt">Best
Regards<o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">-- <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Fabien Betremieux<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Sr. Registry Services & Engagement
Manager<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Global Domains Division, ICANN<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><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:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt">From:
</span></b><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt">Fabien
Betremieux <<a moz-do-not-send="true"
href="mailto:fabien.betremieux@icann.org">fabien.betremieux@icann.org</a>><br>
<b>Date: </b>Tuesday, April 5, 2016 at 12:48 AM<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>"
<<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>Proposal for the Transition of Existing
Registrations from Thin to Thick<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Dear IRT members,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">In our recent conference call, the IRT
discussed the transition of existing
registration from thin to thick. It is our
understanding that two alternative approaches
are emerging:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Option 1 - The registries impose some
checks on the registration data before it can be
accepted<o:p></o:p></span></p>
</div>
<ul type="disc">
<li style="COLOR: black; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto; mso-list: l1 level1
lfo1" class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; FONT-SIZE: 10.5pt">The
initial proposal from the registries for such
checks is based on EPP Standards (RFC 5733),
with subsequent discussion of potential changes
to such checks.<o:p></o:p></span> </li>
<li style="COLOR: black; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto; mso-list: l1 level1
lfo1" class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; FONT-SIZE: 10.5pt">The
main drawback of this approach is that the
transition would likely to last a considerable
amount of time due to:<o:p></o:p></span></li>
</ul>
<ul type="disc">
<ul type="circle">
<li style="COLOR: black; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto; mso-list: l1 level2
lfo1" class="MsoNormal"><span
style="FONT-FAMILY: 'Calibri','sans-serif';
FONT-SIZE: 10.5pt">The need for registrars to
process a very significant amount of data
(collectively) to ensure it would pass the
registries’ checks<o:p></o:p></span> </li>
<li style="COLOR: black; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto; mso-list: l1 level2
lfo1" class="MsoNormal"><span
style="FONT-FAMILY: 'Calibri','sans-serif';
FONT-SIZE: 10.5pt">The need for Staff and the
IRT to gather findings from data analysis by
registrars before they can define a realistic
implementation timeline, which in itself would
delay the definition of the implementation
plan<o:p></o:p></span></li>
</ul>
</ul>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Option 2 - The registries do not impose
any checks on the registration data during the
transition<o:p></o:p></span></p>
</div>
<ul type="disc">
<li style="COLOR: black; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto; mso-list: l0 level1
lfo2" class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; FONT-SIZE: 10.5pt">This
is a proposal emerging from recent discussions,
considering that the Policy Recommendation does
not include data accuracy requirements and
therefore is out of scope for this
implementation<o:p></o:p></span> </li>
<li style="COLOR: black; mso-margin-top-alt: auto;
mso-margin-bottom-alt: auto; mso-list: l0 level1
lfo2" class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; FONT-SIZE: 10.5pt">The
benefit of this approach is that it Is in scope
with the policy recommendations,</span><span
style="FONT-FAMILY: 'Calibri','sans-serif';
FONT-SIZE: 13.5pt"> it reduces the
implementation to a sizable bulk transfer of
data, and</span><span style="FONT-FAMILY:
'Calibri','sans-serif'; FONT-SIZE: 10.5pt"> it creates
an opportunity to possibly synchronize the
transition of new and existing registrations by
defining a single cut-off date after which all
registrations are thick.<o:p></o:p></span></li>
</ul>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Considering the outcome of the IRT’s
meeting with the RrSG in Marrakech, and
considering recent community comments on the
time it is taking to implement the transition
from thin to thick, we would like to propose
that the IRT</span><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
13.5pt"> move forward with Option 2 as we
believe it is the most applicable path forward.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">We would like to gather IRT members
thoughts on our proposal to move forward
with Option 2. Your input would be appreciated by
Friday 8 April COB at the latest, for discussion
during our next IRT meeting, which we are planning
to organize the following week.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Thank you in advance for your
consideration<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="FONT-FAMILY:
'Calibri','sans-serif'; COLOR: black; FONT-SIZE:
10.5pt">Best Regards<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</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>