<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23588"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV>Absolutely, new registrations will comply with whatever the data
requirements or they will fail. And after all domains have been
uploaded to the registry the 'fail' return will apply when an existing RNH tries
to renew or modify a domain and the domain's data does not pass the check, and
the RNH has to update the Contacts in order to have a successful
transaction.</DIV>
<DIV> </DIV>
<DIV>Again, it is just my thinking.</DIV>
<DIV> </DIV>
<DIV>Joyce</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><B>From:</B> <A title=gtheo@xs4all.nl href="mailto:gtheo@xs4all.nl">theo
geurts</A> </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"><B>To:</B> <A
title=gnso-impl-thickwhois-rt@icann.org
href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</A>
; <A title=jlin@007names.com href="mailto:jlin@007names.com">Joyce Lin</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, April 07, 2016 4:13
PM</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><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 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 title=met@msk.com href="mailto:met@msk.com"
moz-do-not-send="true">Metalitz, Steven</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A
title=fabien.betremieux@icann.org
href="mailto:fabien.betremieux@icann.org" moz-do-not-send="true">'Fabien
Betremieux'</A> ; <A title=gnso-impl-thickwhois-rt@icann.org
href="mailto:gnso-impl-thickwhois-rt@icann.org"
moz-do-not-send="true">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
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org"
moz-do-not-send="true">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
href="mailto:gnso-impl-thickwhois-rt@icann.org"
moz-do-not-send="true">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 href="mailto:fabien.betremieux@icann.org"
moz-do-not-send="true">fabien.betremieux@icann.org</A>><BR><B>Date:
</B>Tuesday, April 5, 2016 at 12:48 AM<BR><B>To: </B>"<A
href="mailto:gnso-impl-thickwhois-rt@icann.org"
moz-do-not-send="true">gnso-impl-thickwhois-rt@icann.org</A>" <<A
href="mailto:gnso-impl-thickwhois-rt@icann.org"
moz-do-not-send="true">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
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
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
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></BLOCKQUOTE></BODY></HTML>