<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all, <br>
<br>
Registrars should not be moved into a position that they have to
explain operational, commercial and technical decisions to the
public on why they are not migrating right away or why it is taking
X amount of time. Before we know it spins out of control, seems a
phishing site is nowadays good enough to crash companies stock value
into the ground.
<a class="moz-txt-link-freetext" href="http://www.slate.com/blogs/moneybox/2015/07/14/twitter_stock_pops_after_fake_bloomberg_report_of_acquisition_offer.html">http://www.slate.com/blogs/moneybox/2015/07/14/twitter_stock_pops_after_fake_bloomberg_report_of_acquisition_offer.html</a><br>
<br>
For me a general progress bar is enough for the total of registrars.
If there is reason to worry based on that progress then involved
parties can zoom in and check with the individual registrars to see
what is up and then act on the information if required. <br>
In my opinion this is transparent enough. <br>
<br>
Theo <br>
<br>
<br>
<div class="moz-cite-prefix">On 11-8-2016 17:56, Chris Pelling
wrote:<br>
</div>
<blockquote
cite="mid:2018808482.83455.1470930998420.JavaMail.zimbra@netearth.net"
type="cite">
<div style="font-family: Arial; font-size: 12pt; color: #000000">
<div>Hi Steve, </div>
<div><br data-mce-bogus="1">
</div>
<div>I am still not overly happy about the "registrar" being
named. Anything over and the simple basic numbers of the
"TLD" like Roger suggested is not needed in my honest opionon
and will simply be used as a stick against a registrar.</div>
<div><br data-mce-bogus="1">
</div>
<div>Only ICANN can swing the stick, as per the RAA contract
between those 2 parties. I am lucky in that the platform we
use will simply do it automatically, some other registrar may
not be as lucky and ousting them in a public forum is not the
best way to make someone do something, whereas ICANN flexing
its compliance muscles generally gets things moving :)</div>
<div><br>
</div>
<div data-marker="__SIG_PRE__">Kind regards,<br>
<br>
Chris</div>
<br>
<hr id="zwchr" data-marker="__DIVIDER__">
<div data-marker="__HEADERS__"><b>From: </b>"Steven Metalitz"
<a class="moz-txt-link-rfc2396E" href="mailto:met@msk.com"><met@msk.com></a><br>
<b>To: </b>"chris" <a class="moz-txt-link-rfc2396E" href="mailto:chris@netearth.net"><chris@netearth.net></a><br>
<b>Cc: </b>"theo geurts" <a class="moz-txt-link-rfc2396E" href="mailto:gtheo@xs4all.nl"><gtheo@xs4all.nl></a>, "Roger D
Carney" <a class="moz-txt-link-rfc2396E" href="mailto:rcarney@godaddy.com"><rcarney@godaddy.com></a>,
<a class="moz-txt-link-abbreviated" href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Sent: </b>Thursday, 11 August, 2016 15:27:41<br>
<b>Subject: </b>RE: [Gnso-impl-thickwhois-rt] Open Item 7b -
Coordination/Incentive for Registrars Migration to Thick<br>
</div>
<br>
<div data-marker="__QUOTED_TEXT__">
<style><!--
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
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;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
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";
        color:black;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Times New Roman","serif";
        color:#1F497D;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle23
        {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 l0
        {mso-list-id:479230644;
        mso-list-template-ids:1078247980;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:</style>
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chris,
to be clear, I think I agree with you about percentages
--- “ as of X date, Registrar Y has migrated ZZ% of its
.com registrations to thick.” I don’t think it is
necessary to make the number of registrations public. </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E"><img
id="_x0000_i1028"
src="cid:part1.7C45D601.85A2BC7D@xs4all.nl"
alt="image001" height="41" width="124"></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Steven
J. Metalitz
</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">|<b>
</b></span><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Partner,
through his professional corporation</span></b></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">T:
202.355.7902
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">|</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><a
moz-do-not-send="true" href="mailto:met@msk.com"
target="_blank"><span style="color:black">met@msk.com</span></a></span><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E"></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#88162E">Mitchell
Silberberg & Knupp</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"></span><b><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:#88162E">LLP</span></b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">|</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
<b><a moz-do-not-send="true"
href="http://www.msk.com/" target="_blank"><span
style="color:#84162E">www.msk.com</span></a></b></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">1818
N Street NW, 8th Floor, Washington, DC 20036</span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span
data-mce-style="text-decoration: underline;"
style="text-decoration: underline;"><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:gray">THE
INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS
INTENDED ONLY FOR THE PERSONAL AND CONFIDENTIAL
USE OF THE DESIGNATED RECIPIENTS.</span></span></b><b><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:gray">
THIS MESSAGE MAY BE AN ATTORNEY-CLIENT
COMMUNICATION, AND AS SUCH IS PRIVILEGED AND
CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT
AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT
ANY REVIEW, USE, DISSEMINATION, FORWARDING OR
COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED.
PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR
TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL
ATTACHMENTS FROM YOUR SYSTEM. THANK YOU.</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:gray"></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </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";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Chris Pelling [<a class="moz-txt-link-freetext" href="mailto:chris@netearth.net">mailto:chris@netearth.net</a>]
<br>
<b>Sent:</b> Thursday, August 11, 2016 10:22 AM<br>
<b>To:</b> Metalitz, Steven<br>
<b>Cc:</b> theo geurts; Roger D Carney;
<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] Open
Item 7b - Coordination/Incentive for Registrars
Migration to Thick</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">HI
Steve,</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">I
am sorry Steve but I still disagree with you. If it
was to be a percentage of total domains per TLD and
how many have migrated from thin to thick then fine,
but, I for one would not want company confidential
information to be public, to me the exact number of
domains in a TLD is company confidential
information.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">Nor
within the RAA does it state I have to publicly
provide this information.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">It
would be similar to me asking you Steve how many
clients you have and based on percentages please
specify how many are 1-50 employees, 51-250
employees etc etc</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">However,
if it were total domains in the given TLD, say
120,000,000 and 36% have migrated to far from thin
to thick - I would be happier with that idea.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif"">Kind
regards,<br>
<br>
Chris</span></p>
</div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""> </span></p>
<div class="MsoNormal" style="text-align:center"
align="center"><span
style="font-family:"Arial","sans-serif"">
<hr id="zwchr" align="center" size="2" width="100%">
</span></div>
<div>
<p class="MsoNormal"><b><span
style="font-family:"Arial","sans-serif"">From:
</span>
</b><span
style="font-family:"Arial","sans-serif"">"Steven
Metalitz" <<a moz-do-not-send="true"
href="mailto:met@msk.com" target="_blank">met@msk.com</a>><br>
<b>To: </b>"theo geurts" <<a
moz-do-not-send="true"
href="mailto:gtheo@xs4all.nl" target="_blank">gtheo@xs4all.nl</a>>,
"Roger D Carney" <<a moz-do-not-send="true"
href="mailto:rcarney@godaddy.com" target="_blank">rcarney@godaddy.com</a>>,
<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org"
target="_blank">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Sent: </b>Thursday, 11 August, 2016 14:46:28<br>
<b>Subject: </b>Re: [Gnso-impl-thickwhois-rt] Open
Item 7b - Coordination/Incentive for Registrars
Migration to Thick</span></p>
</div>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""> </span></p>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Why
would we want these numbers [or at least
percentages] to be public? I can think of three
reasons.
</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First,
and most relevant to the question of incentives,
Theo’s e-mail demonstrates that making the
percentages public provides an incentive for
accelerating implementation. The higher the
percentage, the less the risk of the click-bait
scenario being directed against your registrar
business.
</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Second,
outside the bubble of this IRT, there are people
wondering why thick Whois seems to have disappeared
into a black hole more than 2.5 years after the
Board unanimously adopted the consensus policy, and
whether the vaunted multi-stakeholder process can
really deliver results. Providing a publicly
accessible and understandable metric could help to
restore some of the credibility ICANN and its
contracted parties have lost in this process. </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Third,
good old fashioned accountability and transparency.
I thought those were supposed to be the watchwords
of the way ICANN operates. </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E"><img
id="_x0000_i1026"
src="cid:part1.7C45D601.85A2BC7D@xs4all.nl"
alt="image001" height="41" border="0"
width="124"></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Steven
J. Metalitz
</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">|<b>
</b></span><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Partner,
through his professional corporation</span></b></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">T:
202.355.7902 |
<a moz-do-not-send="true"
href="mailto:met@msk.com" target="_blank"><span
style="color:black">met@msk.com</span></a></span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#88162E">Mitchell
Silberberg & Knupp</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"></span><b><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:#88162E">LLP</span></b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">|</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
<b><a moz-do-not-send="true"
href="http://www.msk.com/" target="_blank"><span
style="color:#84162E">www.msk.com</span></a></b></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">1818
N Street NW, 8th Floor, Washington, DC 20036</span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span
data-mce-style="text-decoration: underline;"
style="text-decoration: underline;"><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:gray">THE
INFORMATION CONTAINED IN THIS E-MAIL MESSAGE
IS INTENDED ONLY FOR THE PERSONAL AND
CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS.</span></span></b><b><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:gray">
THIS MESSAGE MAY BE AN ATTORNEY-CLIENT
COMMUNICATION, AND AS SUCH IS PRIVILEGED AND
CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS
NOT AN INTENDED RECIPIENT, YOU ARE HEREBY
NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION,
FORWARDING OR COPYING OF THIS MESSAGE IS
STRICTLY PROHIBITED. PLEASE NOTIFY US
IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND
DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS
FROM YOUR SYSTEM. THANK YOU.</span></b></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </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";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
theo geurts [<a moz-do-not-send="true"
href="mailto:gtheo@xs4all.nl" target="_blank">mailto:gtheo@xs4all.nl</a>]
<br>
<b>Sent:</b> Wednesday, August 10, 2016 2:51 PM<br>
<b>To:</b> Metalitz, Steven; 'Roger D Carney'; <a
moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org"
target="_blank">
gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-impl-thickwhois-rt]
Open Item 7b - Coordination/Incentive for
Registrars Migration to Thick</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I
agree with Roger.<br>
<br>
I am not sure if I agree with Steve. The suggestion
bout the progress expressed in percentages is fine,
but why would we want these numbers be public?
<br>
<br>
Beside some domain bloggers creating click-bait
headlines, like :"will registrar X make the deadline
or will they be de-accredited? Transfer your domains
now!". I currently do not see why they should be made
public, though I am open input.<br>
<br>
Thanks, <br>
<br>
Theo <br>
<br>
<br>
</p>
<div>
<p class="MsoNormal">On 10-8-2016 20:06, Metalitz,
Steven wrote:</p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
agree with Roger that weekly and consolidated
reporting would be a good idea. Would it be
feasible to also provide as a denominator the
total number of registrations sponsored by that
registrar in the registries in question, so that
progress could be expressed in percentage terms?
These numbers should also be made public
periodically.
</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E"><img
id="Picture_x0020_1"
src="cid:part1.7C45D601.85A2BC7D@xs4all.nl"
alt="image001" height="41" border="0"
width="124"></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Steven
J. Metalitz
</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">|<b>
</b></span><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E">Partner,
through his professional corporation</span></b></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">T:
202.355.7902 |
<a moz-do-not-send="true"
href="mailto:met@msk.com" target="_blank"><span
style="color:black">met@msk.com</span></a></span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#88162E">Mitchell
Silberberg & Knupp</span></b><b><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:#88162E">LLP</span></b><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">|</span><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#84162E">
<b><a moz-do-not-send="true"
href="http://www.msk.com/" target="_blank"><span
style="color:#84162E">www.msk.com</span></a></b></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">1818
N Street NW, 8th Floor, Washington, DC 20036</span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span
data-mce-style="text-decoration: underline;"
style="text-decoration: underline;"><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:gray">THE
INFORMATION CONTAINED IN THIS E-MAIL MESSAGE
IS INTENDED ONLY FOR THE PERSONAL AND
CONFIDENTIAL USE OF THE DESIGNATED
RECIPIENTS.</span></span></b><b><span
style="font-size:8.0pt;font-family:"Calibri","sans-serif";color:gray">
THIS MESSAGE MAY BE AN ATTORNEY-CLIENT
COMMUNICATION, AND AS SUCH IS PRIVILEGED AND
CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS
NOT AN INTENDED RECIPIENT, YOU ARE HEREBY
NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION,
FORWARDING OR COPYING OF THIS MESSAGE IS
STRICTLY PROHIBITED. PLEASE NOTIFY US
IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND
DELETE THE ORIGINAL MESSAGE AND ALL
ATTACHMENTS FROM YOUR SYSTEM. THANK YOU.</span></b></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </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"">
<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org"
target="_blank">gnso-impl-thickwhois-rt-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org"
target="_blank">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>]
<b>On Behalf Of </b>Roger D Carney<br>
<b>Sent:</b> Wednesday, August 10, 2016 12:24
PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org"
target="_blank">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-impl-thickwhois-rt]
Open Item 7b - Coordination/Incentive for
Registrars Migration to Thick</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1F497D">Good
Morning,</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The
migration data path should be left to the
registrars discretion and not necessarily based on
renewal dates. I would propose that starting at
the beginning of the transition, Verisign can
provide a weekly list of thin registrations to
each registrar (and possibly ICANN) of domains
that do not have contacts assigned and maybe a
consolidated report showing Registrar progression.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The
reduced validation rules need to apply until all
registrations are thick.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Post
transition, if domain has no ROIDs the domain is
auto-deleted at the domain expiration date
automatically by the Registry.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Post
transition completion date, ICANN will revoke your
Registrar Accreditation 90 days after transition
if you are not making noticeable progress on
remaining thin registrations.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks</span></p>
<p class="MsoNormal"><span style="color:#1F497D">Roger</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </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 moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org"
target="_blank">gnso-impl-thickwhois-rt-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org"
target="_blank">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>]
<b>On Behalf Of </b>Fabien Betremieux<br>
<b>Sent:</b> Monday, August 08, 2016 4:47 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org"
target="_blank">gnso-impl-thickwhois-rt@icann.org</a><br>
<b>Subject:</b> [Gnso-impl-thickwhois-rt] Open
Item 7b - Coordination/Incentive for
Registrars Migration to Thick</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Dear
IRT Members,</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">As
Staff is working on drafting the implementation
plan, including potential measures that could be
implemented or suggested to facilitate and
encourage Registrars to complete the migration
of registration data from thin to thick, we
would like to pick IRT members brains about the
type of measures they believe would or would not
be effective for themselves and others .</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">To
date, several ideas have been floated in IRT
discussions:</span></p>
</div>
<ul type="disc">
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
<span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Using
renewal date of a registration as a pacing
mechanism to migrate registration data</span></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
<span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Setting
up financial incentives plans similar to what
some ccTLDs have done to promote the adoption of
DNSSEC</span></li>
<li class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0
level1 lfo1">
<span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Not
replicating the migration in batch implemented
during the migration of .ORG from thin to thick</span></li>
</ul>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Can
you think of other effective (or non effective)
measures ?</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks
in advance for your discussion of this topic.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Best
Regards</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Fabien</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </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:11.0pt;font-family:"Calibri","sans-serif"">From:
</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><<a
moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org"
target="_blank">gnso-impl-thickwhois-rt-bounces@icann.org</a>>
on behalf of theo geurts <<a
moz-do-not-send="true"
href="mailto:gtheo@xs4all.nl" target="_blank">gtheo@xs4all.nl</a>><br>
<b>Date: </b>Monday, June 20, 2016 at 5:32 PM<br>
<b>To: </b>"<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org"
target="_blank">gnso-impl-thickwhois-rt@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt@icann.org"
target="_blank">gnso-impl-thickwhois-rt@icann.org</a>><br>
<b>Subject: </b>Re: [Gnso-impl-thickwhois-rt]
Updated Scorecard of Transition Implementation
Path Discussions</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks.
Fabien,<br>
<br>
I think it is wise that the comment from Steve
Metalitz on the last call is also reflected in
7B. That once the PDP is sent to the
Registrars with an effective date becomes an
obligation for Registrars to comply with.<br>
<br>
This itself does not solve the issue, but it
does raise the question how ICANN Compliance
is gonna deal with this and how it could
possibly affect the timeline. The dynamics
being different compared to .ORG.
<br>
<br>
Let me explain my thinking here. Assume in a
worst case scenario that we are passed the end
date of the migration (18 months). The end
result is 200 Registrars did not migrate the
data. Compliance kicks in. They need to deal
with 200 Registrars mediation is 6
months(complete guess). Total migration time
24 months. <br>
<br>
Do we need to factor this in? Does it add
anything?<br>
<br>
How compliance will deal with this is outside
the scope of the IRT in my opinion. Though
Maguy and her team might want to start
thinking about this.
<br>
<br>
Best, <br>
<br>
Theo Geurts<br>
<br>
<br>
<br>
</span></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">On
20-6-2016 16:36, Fabien Betremieux wrote:</span></p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Dear
IRT Members,</span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">In
advance of our meeting planned
tomorrow, please find attached our
updated scorecard (in clean and
redline versions) per discussion in
last week’s meeting and over the
mailing list since then.</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">We
will use the clean version to guide
our discussion tomorrow. In the
meantime, please let me know if you
would like to propose edits to the
scorecard.</span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thank
you for your attention</span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">-- </span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Fabien
Betremieux</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Sr.
Registry Services & Engagement
Manager</span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Global
Domains Division, ICANN</span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""><br>
<br>
<br>
<br>
<br>
</span></p>
<pre>_______________________________________________</pre>
<pre>Gnso-impl-thickwhois-rt mailing list</pre>
<pre><a moz-do-not-send="true" href="mailto:Gnso-impl-thickwhois-rt@icann.org" target="_blank">Gnso-impl-thickwhois-rt@icann.org</a><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></pre>
</blockquote>
<p class="MsoNormal"><span
style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
</p>
<pre>_______________________________________________</pre>
<pre>Gnso-impl-thickwhois-rt mailing list</pre>
<pre><a moz-do-not-send="true" href="mailto:Gnso-impl-thickwhois-rt@icann.org" target="_blank">Gnso-impl-thickwhois-rt@icann.org</a></pre>
<pre><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></pre>
</blockquote>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span
style="font-family:"Arial","sans-serif""><br>
_______________________________________________<br>
Gnso-impl-thickwhois-rt mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org"
target="_blank">Gnso-impl-thickwhois-rt@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt"
target="_blank">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a></span></p>
</div>
</div>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>