<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>So I joined this IRT, I guess December last year. <br>
</p>
<p>I agree this one has/is taken a long time for reasons I do not
know. I was not part of the WG, so I do not carry much history. <br>
The last few months we made a lot of progress I think. We set a
time line based on several factors and I happen to think I been
driving and pushing this one with several other Registrars. <br>
</p>
<p>Amount of connections, speed of connections, size of Registrar,
that not every Registrar is aware and a ton of other reasons,
including Registrars to do their own legal analysis to see if they
can migrate the data. <br>
</p>
I understand as Steve rightfully pointed out, that this one took way
to long. My first thought is how can we prevent this in the future.
<br>
What I do not understand is why we want to speed things up. With so
many delays we are facing new realities. I think Steve DelBianco
made some good pointers during the Helsinki meeting. Personally I
feel like I am dealing with some old decision made in 2012 and now
it is 2016 and we are facing issues and the IRT can clean it up. <br>
<br>
Wich is okay, and it is not that the system is broken or anything,
but what do we gain from speeding things up, it is like I am missing
something here? Why do we want to shower Registrars with money who
migrate the first week? What do we gain as a community?<br>
<br>
Thanks <br>
<br>
Theo Geurts <br>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 16-8-2016 20:35, Susan Kawaguchi
wrote:<br>
</div>
<blockquote cite="mid:D3D8A964.7C94E%25susank@fb.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div>
<div>I agree with Steve that we should look at incentives to
move the transition of domain name registrations to the
Thick Whois. And I agree that relying on compliance to
enforce after 18 months is not acceptable due to the
compliance team’s collaborative actions with registrars,
simple issues take much longer than they need to take, this
could push the timeline much farther down the road. </div>
<div><br>
</div>
<div>What if ICANN stepped forward and offered a monetary
incentive to move the registrations to Thick Whois within a
much shorter time frame? A small reduction in fees for
example. </div>
<div><br>
</div>
<div>I am sure there are other positive incentives that we
could come up with but if not transparency is always
valuable to the ICANN community as a whole. </div>
<div>
<div>
<div>Susan Kawaguchi</div>
<div>Domain Name Manager </div>
<div>Facebook Legal Dept. </div>
</div>
<div><br>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt;
text-align:left; color:black; 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">
<span style="font-weight:bold">From: </span><<a
moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>>
on behalf of Steven Metalitz <<a moz-do-not-send="true"
href="mailto:met@msk.com">met@msk.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, August
16, 2016 at 11:24 AM<br>
<span style="font-weight:bold">To: </span>'Jody Kolker' <<a
moz-do-not-send="true" href="mailto:jkolker@godaddy.com">jkolker@godaddy.com</a>>,
Rob Golding <<a moz-do-not-send="true"
href="mailto:rob.golding@astutium.com">rob.golding@astutium.com</a>>,
"<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>
<span style="font-weight:bold">Subject: </span>Re:
[Gnso-impl-thickwhois-rt] Open Item 7b -
Coordination/Incentive for Registrars Migration to Thick<br>
</div>
<div><br>
</div>
<div>
<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]-->
<div link="blue" vlink="purple" lang="EN-US">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);">Let’s remember why we are having this
conversation.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);">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: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);">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: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);">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: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);">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: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);">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: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(31, 73,
125);">Steve Metalitz
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size: 11pt;
font-family: Calibri, sans-serif; color: rgb(136,
22, 46);"><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: 10pt;
font-family: Tahoma, sans-serif;">From:</span></b><span
style="font-size: 10pt; font-family: Tahoma,
sans-serif;">
<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>
[<a moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">mailto:gnso-impl-thickwhois-rt-bounces@icann.org</a>]
<b>On Behalf Of </b>Jody Kolker<br>
<b>Sent:</b> Friday, August 12, 2016 6:51 AM<br>
<b>To:</b> Rob Golding; <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> 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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</a>
[<a moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
<a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Dimpl-2Dthickwhois-2Drt&d=DQMF-g&c=5VD0RTtNlTh3ycd41b3MUw&r=gvEx8xF7ynrYQ7wShqEr-w&m=-USHOFzkn_GygoRPoPSoTapiWOHSoOMj4og5OViLRtY&s=Ok10sW4YZh3-Hb9Rp3Pe4yskamjBOP8LWvUEOC9VyLI&e=">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><br>
_______________________________________________<br>
Gnso-impl-thickwhois-rt mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</a><br>
<a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Dimpl-2Dthickwhois-2Drt&d=DQMF-g&c=5VD0RTtNlTh3ycd41b3MUw&r=gvEx8xF7ynrYQ7wShqEr-w&m=-USHOFzkn_GygoRPoPSoTapiWOHSoOMj4og5OViLRtY&s=Ok10sW4YZh3-Hb9Rp3Pe4yskamjBOP8LWvUEOC9VyLI&e=">https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</a><o:p></o:p></p>
</div>
</div>
</div>
</span>
<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>