<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: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;}
/* 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;}
span.EmailStyle17
{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="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">Let’s remember why we are having this conversation.
<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">Thick Whois is a consensus policy. And the registrars, through this implementation process, are giving themselves eighteen months (from the date the registry
production system opens – a year from now) to achieve compliance with that policy. I agree that at that point (February 2019 under the current timetable), failure to provide the required data to the registry will be a matter of contract compliance under
the RAA (though I would contest that it becomes “public at that point”). <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">The question we are discussing is whether there are any incentives that can be created so that registrars will provide the required data to the registry within
a period of less than 18 months. Incentives can be positive or negative. Making public the extent to which each registrar is providing the required data on existing registrations, at some point during the 18-month period, certainly could provide some incentive.
The reaction below (and others on this thread) demonstrate pretty clearly that a registrar would not wish to appear on a public list that shows a relatively low percentage of registrations for which the data has been provided to the registry. I would call
that an incentive for the registrar to move faster toward full achievement of thick Whois than it might otherwise do. That is how a negative incentive works --- if you don’t do X, then you suffer some detriment. In this case that detriment takes the form,
to use Rob’s term, of “naming and shaming.” It does not take the form of contract compliance action, because that does not apply until the 18 months have elapsed.
<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 it may be of no immediate value to the registrar to have this information made public. Value to the registrar is not what we are talking about here.
We are talking about whether making this information public will give registrars an incentive to come into compliance faster than they are required to do (under the deadline they have set for themselves through this group). Accelerated compliance would benefit
the credibility of ICANN and of the multi-stakeholder model, both of which are losing credibility the longer this implementation process drags on. It could benefit competition, which is another way of saying it could benefit those registrars who move relatively
faster toward thick Whois. It would benefit transparency. And it would benefit the public (ultimately it was the benefit to the public that motivated ICANN to adopt this consensus policy in the first place). But no, it would not benefit the registrar that
is simply aiming for compliance at the end of 18 months. <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">What I am drawing from this thread is that the registrars in this group do not want to see any incentives provided for them to do their jobs faster than the
18 months they have decided on as the deadline for doing the job. This is disappointing but certainly not surprising. It is a perfectly legitimate position for registrars to take based on their own self-interest, but it gives short shrift to the other interests
noted above, including competition, transparency, and the credibility of the multi-stakeholder model.
<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 would certainly welcome any other suggestions for incentives – positive or negative – to encourage registrars to complete their role in achieving thick Whois
in less than 18 months. <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">Steve Metalitz
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#88162E"><o:p> </o:p></span></b></p>
</div>
<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>Jody Kolker<br>
<b>Sent:</b> Friday, August 12, 2016 6:51 AM<br>
<b>To:</b> Rob Golding; gnso-impl-thickwhois-rt@icann.org<br>
<b>Subject:</b> Re: [Gnso-impl-thickwhois-rt] Open Item 7b - Coordination/Incentive for Registrars Migration to Thick<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">+1.<br>
<br>
Thanks,<br>
Jody Kolker<br>
319-294-3933 (office)<br>
319-329-9805 (mobile) Please contact my direct supervisor Charles Beadnall (<a href="mailto:cbeadnall@godaddy.com">cbeadnall@godaddy.com</a>) with any feedback.<br>
<br>
This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original
and any copy of this message and its attachments.<br>
<br>
-----Original Message-----<br>
From: <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>] On Behalf Of Rob Golding<br>
Sent: Friday, August 12, 2016 5:22 AM<br>
To: <a href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</a><br>
Subject: Re: [Gnso-impl-thickwhois-rt] Open Item 7b - Coordination/Incentive for Registrars Migration to Thick<br>
<br>
Hi<br>
<br>
I cannot see a single valid reason why any form of unnecessary "naming and shaming" relating to a work-in-progress could benefit anyone - verisign producing a X% completed report is fine, but no details need to be "public" relating to any individual registrar.<br>
<br>
If the deadlines are not met, that'll be a compliance issue, and public at that point<br>
<br>
If the deadline has not yet been reached, there is no benefit to providing fuel for a fire that din't need to be lit and serves no useful purpose<br>
<br>
The Registrant (ultimately the only party that matters) isn't asking for this policy, isn't (obviously) benefited by the policy, and publicising sensitive corporate data about their chosen registrar could well be seen as doing demnstrable harm<br>
<br>
Rob<br>
--<br>
Rob Golding <a href="mailto:rob.golding@astutium.com">rob.golding@astutium.com</a><br>
Astutium Ltd, Number One Poultry, London. EC2R 8JR<br>
<br>
* domains * hosting * vps * servers * cloud * backups * _______________________________________________<br>
Gnso-impl-thickwhois-rt mailing list<br>
<a href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><br>
_______________________________________________<br>
Gnso-impl-thickwhois-rt mailing list<br>
<a href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><o:p></o:p></p>
</div>
</body>
</html>