<!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
style="FONT-FAMILY: Calibri, sans-serif; WORD-WRAP: break-word; COLOR: rgb(0,0,0); FONT-SIZE: 14px; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgColor=#ffffff>
<DIV><FONT size=3 face=Arial>I absolutely do not like or agree with the idea of
offering 'incentive', and specially have ICANN step in for the 'incentive'
program.</FONT></DIV>
<DIV><FONT size=3 face=Arial></FONT> </DIV>
<DIV><FONT size=3 face=Arial>If any registrars fall behind due to technical
issues, I'm sure Verisign will be very willing to help and holding hands
to the finish line even giving extra time to those registrars. Other
than technical issues, the registrars should bear the responsibilities for not
being able or willing to work on the transitions and should be blocked
to any new registrations after having given certain period and
help.</FONT></DIV>
<DIV><FONT size=3 face=Arial></FONT> </DIV>
<DIV><FONT size=3 face=Arial></FONT> </DIV>
<DIV><FONT size=3 face=Arial>I do not see any responsible registrars would
jeopardize their clients' interests or their own business, to say the
very least. Maybe I'm missing something, some points or not
compassionate enough. But, we are making things more complicated than they
should be.</FONT></DIV>
<DIV><FONT size=3 face=Arial></FONT> </DIV>
<DIV><FONT size=3 face=Arial></FONT> </DIV>
<DIV><FONT size=3 face=Arial>Joyce</FONT></DIV>
<DIV><FONT size=3 face=Arial></FONT><FONT size=3 face=Arial></FONT> </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">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=susank@fb.com href="mailto:susank@fb.com">Susan Kawaguchi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=met@msk.com
href="mailto:met@msk.com">Metalitz, Steven</A> ; <A title=jkolker@godaddy.com
href="mailto:jkolker@godaddy.com">'Jody Kolker'</A> ; <A
title=rob.golding@astutium.com href="mailto:rob.golding@astutium.com">Rob
Golding</A> ; <A title=gnso-impl-thickwhois-rt@icann.org
href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, August 16, 2016 2:35
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Gnso-impl-thickwhois-rt]
Open Item 7b - Coordination/Incentive for Registrars Migration to Thick</DIV>
<DIV><BR></DIV>
<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="BORDER-BOTTOM: medium none; TEXT-ALIGN: left; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; FONT-FAMILY: Calibri; COLOR: black; FONT-SIZE: 11pt; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><SPAN
style="FONT-WEIGHT: bold">From: </SPAN><<A
href="mailto:gnso-impl-thickwhois-rt-bounces@icann.org">gnso-impl-thickwhois-rt-bounces@icann.org</A>>
on behalf of Steven Metalitz <<A
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
href="mailto:jkolker@godaddy.com">jkolker@godaddy.com</A>>, Rob Golding
<<A
href="mailto:rob.golding@astutium.com">rob.golding@astutium.com</A>>, "<A
href="mailto:gnso-impl-thickwhois-rt@icann.org">gnso-impl-thickwhois-rt@icann.org</A>"
<<A
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-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
}
</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 lang=EN-US vlink="purple" link="blue">
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">Let’s
remember why we are having this conversation. <O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">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-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">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-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">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-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">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-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">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-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">Steve
Metalitz <O:P></O:P></SPAN></P>
<DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: Calibri, sans-serif; COLOR: rgb(136,22,46); FONT-SIZE: 11pt"><O:P></O:P></SPAN></B></P></DIV>
<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">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>Jody Kolker<BR><B>Sent:</B> Friday, August 12, 2016 6:51
AM<BR><B>To:</B> Rob Golding; <A
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
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://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
href="mailto:Gnso-impl-thickwhois-rt@icann.org">Gnso-impl-thickwhois-rt@icann.org</A><BR><A
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>
<P>
<HR>
<P></P>_______________________________________________<BR>Gnso-impl-thickwhois-rt
mailing
list<BR>Gnso-impl-thickwhois-rt@icann.org<BR>https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt</BLOCKQUOTE></BODY></HTML>