<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=us-ascii">
<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:"Times New Roman","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";}
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:"Times New Roman","serif";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{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;}
/* List Definitions */
@list l0
{mso-list-id:573121772;
mso-list-template-ids:1668304470;}
@list l0:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:579683149;
mso-list-template-ids:1800581892;}
@list l2
{mso-list-id:815486627;
mso-list-template-ids:-142342638;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:1075857255;
mso-list-template-ids:78032226;}
@list l3:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:1682585732;
mso-list-template-ids:78032226;}
@list l4:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5
{mso-list-id:1997100052;
mso-list-template-ids:-1651191336;}
@list l6
{mso-list-id:2053647318;
mso-list-template-ids:-697912676;}
@list l6:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hello All,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree with Roger and would just like to include the
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#00B050">following</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Jennifer Gore<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";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>Roger D Carney<br>
<b>Sent:</b> Monday, May 09, 2016 11:44 AM<br>
<b>To:</b> gnso-impl-thickwhois-rt@icann.org<br>
<b>Subject:</b> Re: [Gnso-impl-thickwhois-rt] Transition - Your Input on Open Questions - Due Mon. 9 May<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#5B9BD5">Good Morning,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l4 level1 lfo3">What would the a bulk transfer be under option 2 (proposal that registries do not impose checks or validation parameters on the registration data being transitioned from thin to thick) ?<o:p></o:p></li></ol>
<ol style="margin-top:0in" start="1" type="1">
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#5B9BD5;mso-list:l3 level2 lfo6">[RDC] I think that having two options would be best, a file option and a dedicated EPP connection(s) option.<span style="color:#1F497D">
</span><span style="color:#00B050">File Option should have defined specifications i.e. format, size,etc (JGore)</span><o:p></o:p></li></ul>
</ol>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l4 level1 lfo3">How can we minimize the amount of “throw away code” ?
<o:p></o:p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#5B9BD5;mso-list:l4 level2 lfo3">[RDC] Allowing bulk through dedicated EPP connection will reuse the create and update code paths.<span style="color:#1F497D">
</span><span style="color:#00B050">If Registries would agree on a uniformed SDK that would be appreciated (JGore)</span><o:p></o:p></li></ul>
</li><li class="MsoNormal" style="mso-list:l4 level1 lfo3">Should there be a minimal set of validation parameters ? For example: Numerical/Alphanumerical/UTF8 constraints on phone fields, requirement to provide Contact ID and Auth Info, a maximum length of fields
<o:p></o:p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#5B9BD5;mso-list:l4 level2 lfo3">[RDC] Max length, contact id, auth info.<span style="color:#1F497D">
</span><span style="color:#00B050">Minimum length (JGore)</span><o:p></o:p></li></ul>
</li><li class="MsoNormal" style="mso-list:l4 level1 lfo3">Should we aim to synchronize implementation of the new and existing registrations tracks ?
<o:p></o:p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#00B050;mso-list:l4 level2 lfo3"><span style="color:#5B9BD5">[RDC] I think that we should keep these going down separate paths, mitigating any possible delay in one path from the other path.
</span>Keep them separate. Focus on New Registrations first (JGore)<o:p></o:p></li></ul>
</li><li class="MsoNormal" style="mso-list:l4 level1 lfo3">Once data is migrated, what rules should apply ? Should new and existing registrations be treated differently based on their creation date and the applicable RAA ?
<o:p></o:p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#5B9BD5;mso-list:l4 level2 lfo3">[RDC] New and existing should be treated differently. Current rules (ICANN and Registry policies) should only apply to existing registration contacts once the contact update date is greater
than the transition date, exception on transfers see below.<span style="color:#1F497D">
</span><o:p></o:p></li></ul>
</li><li class="MsoNormal" style="mso-list:l4 level1 lfo3">Is the potential impact of option 2 on future transfers of registration acceptable ?
<o:p></o:p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#00B050;mso-list:l4 level2 lfo3"><span style="color:#5B9BD5">[RDC] Yes, same experience as today, except that it should improve over time. There will be bad contacts on transfers and this should be allowed. This data will
cleanse organically over time.</span><span style="color:#1F497D"> </span>Do not prohibit the transfer if data contact information is incorrect or not complete (JGore).
<o:p></o:p></li></ul>
</li></ol>
<p class="MsoNormal"><span style="color:#5B9BD5"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#5B9BD5"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#5B9BD5">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#5B9BD5">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"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a> [<a 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, May 05, 2016 6:46 AM<br>
<b>To:</b> <a href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Subject:</b> [Gnso-impl-thickwhois-rt] Transition - Your Input on Open Questions - Due Mon. 9 May<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Dear IRT members,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">In preparation for our next IRT meeting on Tue. 10 May, during which we would like to focus our discussion on the implementation of the transition from thin to
thick, we would like to gather your thoughts on the open questions below.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">A you may recall, these questions emanate from prior discussions on the mailing list regarding proposals for the transition of existing registration from thin
to thick. For more background, please refer our presentation earlier this week (available at: <a href="https://community.icann.org/display/TWCPI/IRT+Meetings">https://community.icann.org/display/TWCPI/IRT+Meetings</a>).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Open questions :<o:p></o:p></span></p>
</div>
<div>
<ol start="1" type="1">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo10">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">What would the a bulk transfer be under option 2 (proposal that registries do not impose checks or validation parameters on the registration data being transitioned from thin to thick) ?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo10">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">How can we minimize the amount of “throw away code” ?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo10">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Should there be a minimal set of validation parameters ? For example: Numerical/Alphanumerical/UTF8 contraints on phone fields, requirement to provide Contact ID and Auth Info, a maximum length
of fields<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo10">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Should we aim to synchronize implementation of the new and existing registrations tracks ?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo10">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Once data is migrated, what rules should apply ? Should new and existing registrations be treated differently based on their creation date and the applicable RAA ?<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l6 level1 lfo10">
<span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Is the potential impact of option 2 on future transfers of registration acceptable ?<o:p></o:p></span></li></ol>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Please provide your input in response to this email by Mon. 9 May COB in your time zone.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Best Regards<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">-- <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Fabien Betremieux<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Sr. Registry Services & Engagement Manager<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Global Domains Division, ICANN<o:p></o:p></span></p>
</div>
</body>
</html>