<html>
<body>
At 09:10 AM 3/31/2004, Larry Erlich wrote:<br>
<blockquote type=cite class=cite cite>>From a Network Solutions email
that<br>
I just received:<br><br>
--ICANN requires personal contact information associated<br>
--with a domain name registration be made available for<br>
--anyone to view on the web in a public WHOIS database. <br>
--<br>
--With our Private Registration service you will get alternate<br>
--contact information for your domain name registrations.<br>
--The contact information you want to keep private is kept<br>
--out of the public WHOIS database.<br>
--
<br>
<font color="#FF0000">--Our introductory price of $5 per year per domain
name is<br>
--expiring soon. So add Private Registration to your domain<br>
--name registrations today.</font><br><br>
It seems that there is a conflict of interest in<br>
the discussion about whois as a few registrars that are<br>
participating also offer "private" registrations. As such<br>
it is obvious that they would probably prefer to<br>
have all whois information as public as possible<br>
so that they can continue to sell the<br>
private registrations. Nothing wrong<br>
with that, but would those registrars that<br>
have private registrations care to identify<br>
themselves?<br><br>
<br>
Larry Erlich<br><br>
<a href="http://www.domainregistry.com/" eudora="autourl">http://www.DomainRegistry.com</a><br><br>
<br><br>
<br>
Tim Ruiz wrote:<br>
> <br>
> Paul,<br>
> <br>
> I agree with Ross' comments below for the most part.<br>
> <br>
> By severely restricted, I meant that it should only be used to
facilitate<br>
> transfers, and only then until something better is decided on. I was
not<br>
> arguing anything about the data collected or displayed.<br>
> <br>
> But regarding that, I don't see a need for, or agree with, any
change to the<br>
> data collected or displayed, at least based on any of the arguments
or<br>
> reasoning that I've seen or heard to date.<br>
> <br>
> Also, I am only talking about direct access to port 43. I see no
problem<br>
> with, and am not recommending any change to, the Web based access to
Whois<br>
> as long we can continue to protect it from scripting or high volume
access.<br>
> <br>
> Tim<br>
> <br>
> -----Original Message-----<br>
> From: Ross Wm. Rader
[<a href="mailto:ross@tucows.com" eudora="autourl">mailto:ross@tucows.com</a>]<br>
> Sent: Tuesday, March 30, 2004 8:44 PM<br>
> To: Paul Stahura<br>
> Cc: Tim Ruiz; registrars@dnso.org<br>
> Subject: Re: [registrars] FW: [dow1tf] TR: IPC constituency
statement for<br>
> Whois TF1<br>
> <br>
> On 3/30/2004 9:13 PM Paul Stahura noted that:<br>
> <br>
> > What happens with thick registries?<br>
> > .com and .net will switch to EPP, and who knows, probably thick
EPP.<br>
> > Do we get to choose "b allow registrars to manage the
service as they see<br>
> > fit" by not providing them with the whois
information?<br>
> <br>
> I think this is almost a separate conversation, but my preference
would<br>
> be to evaluate the utility of the thick registry model before we
permit<br>
> the creation of any more. Based on the testbed experience, I'm
not<br>
> convinced that centralizing customer data in this way without
getting<br>
> the guarantees we all need from a legal perspective is necessarily
a<br>
> wise thing moving forward.<br>
> <br>
> To the point as it relates to this policy - registrars shouldn't
be<br>
> obligated to provide the data to any party that can't guarantee that
the<br>
> data will be treated in a manner consistent with the policies
and<br>
> legislation under which it was collected.<br>
> <br>
> > Are you proposing we be allowed to not give the info to
anyone?<br>
> <br>
> That would be one potential implementation. Or just to parties that
we<br>
> have a relationship with. Or just to parties that acts a brokers
between<br>
> registrars and potential licensee's or...<br>
> <br>
> --<br>
> <br>
>
-rwr<br>
> <br>
>
"Don't be too timid and squeamish about your actions.<br>
>
All life is an experiment.<br>
>
The more experiments you make the better."<br>
>
- Ralph Waldo Emerson<br>
> <br>
> Got Blog?
<a href="http://www.blogware.com/" eudora="autourl">http://www.blogware.com</a><br>
> My Blogware:
<a href="http://www.byte.org/" eudora="autourl">http://www.byte.org</a></blockquote></body>
</html>