<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
All,<br>
<br>
My brain may still be fuzzy from travel but it seems that dozens of
other online services routinely allow one to contact a party without
the party's name being published. I assume (having not used
them....yet <span class="moz-smiley-s7"><span> :-\ </span></span> )
that the online dating/matchmaking services work that way, as do
lots of other online services. Ability to reach an owner, and
ability to know who the owner is, are two different abilities. If an
owner refused to disclose or respond, that is their right. If they
are being abusive with the domain name, then the registrar is
involved. If it is more serious, then the law is involved. Need this
part be more complicated than that?<br>
<br>
<div class="moz-cite-prefix">On 20/03/2016 7:39 PM, Metalitz, Steven
wrote:<br>
</div>
<blockquote
cite="mid:E5B4A2ED43DFAE4F9E710FA54FEF8F624BB5ABF7@LAEX02.MSK.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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 class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">One
further point to consider in the context of the informative
exchange below. <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">Whether
one likes it or not, whether one wishes it were otherwise or
not, the fact is that over the past 20+ years, many people
have come to rely on registration data not only to
facilitate the functions Andrew outlines below, and not only
to support the business operations of the collectors of the
data (in the gTLD world, the registrars), which was the
thrust of Holly’s original post, but for another purpose:
to access a public record of who has registered which domain
name(s), in order to enable (or at least to facilitate)
contact with that registrant when issues arise regarding the
use of the domain name.
<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">Andrew’s
observation that</span> third party access to registration
data is needed to deal with abuse attributable to particular
registrants covers part of this purpose, but not all of it.
Over the years, and most recently in the Expert Working Group,
ICANN participants have compiled extensive lists of such
purposes for which registration data has been used. This
“public record” characteristic of the only registration data
system that has ever applied to gTLD registrations is an
important factor to bear in mind. It has contributed
significantly to transparency in the DNS and ultimately to
accountability for how domain names are used. Of course,
those benefits to the public have also been accompanied by
costs to the public. Hopefully these can be weighed
objectively. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I fully agree that the fact – and it is a
fact -- that gTLD registration data has always been a public
record does not resolve the question of whether the members of
the public who have historically relied on access to this data
should continue to enjoy the same level of access to it that
they do under the current system. There may be valid and
persuasive reasons for reducing or restricting that level of
access in the future--- optimally, in a way that retains the
public benefits of the current system while reducing the
costs. But it does suggest that if we move to a system in
which the collection of this data is restricted to those
elements that serve a foreseen business purpose for the
collectors (registrars), then there may be significant costs
to the public, which by definition could never, under any
circumstances or conditions, enjoy access to data that was
never collected. This certainly should be a factor in
deciding whether the public interest is best served by such
restrictions on collection.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Steve Metalitz<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"><o:p> </o:p></span></p>
</div>
</blockquote>
< Rest Deleted ><br>
</body>
</html>