I have no problem with this private indentifying information being held by ICAAN or any other responsible party in case situations like this arise. However I don't see the added value in this regard of having this information made public to anyone. If a problem like this occurs, cannot ICANN or other entities involved trace the information? For example, I once was receiving threatening emails and the police got involved and worked with Yahoo to identify the person, who never disclosed his identity.

Randy

----- Original Message ----- From: "Vicky Staubly" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, October 11, 2007 5:09 PM
Subject: Re: [CGUYS] GoDaddy's registration agreement - speaking of priv


On Thu, 11 Oct 2007, Randy wrote:
The GoDaddy guy said all that is required is a legitimate address; doesn't have to be your personal address. I would give a legitimate street address. If you can tell me what legitimate societal purpose is served by ICANN not only having my home address and other personal information but having this available in a public registry, available for sale, then I'll consider putting down my home address or paying the extra cost to keep these private (effectively more than doubling the domain registration cost if using the GoDaddy privacy option).

About 10 years ago, my web server was broken into by some hooligans in
(I think Sweden). I saw several connection attempts from some IP addresses
in Sweden and England. I was able to look up the domain to which these
IP addresses belonged (a University in England, and some ISP in Sweden).
By looking up the owners of the domain, I was able to let the admin in
England know that their system had been broken into, and let the ISP
in Sweden know that some of their customers were breaking the law.

--
Vicky Staubly       http://www.steeds.com/vicky/        [EMAIL PROTECTED]


************************************************************************
* ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in  <==
* ==> the body of an email & send 'em to: [EMAIL PROTECTED] <==
* Join the list: SUBSCRIBE COMPUTERGUYS-L Your Name
* Too much mail? Try Daily Digests command: SET COMPUTERGUYS-L DIGEST
* Tired of the List? Unsubscribe command: SIGNOFF COMPUTERGUYS-L
* New address? From OLD address send: CHANGE COMPUTERGUYS-L YourNewAddress
* Need more help? Send mail to: [EMAIL PROTECTED]
************************************************************************
* List archive at www.mail-archive.com/[email protected]/
* RSS at www.mail-archive.com/[email protected]/maillist.xml
* Messages bearing the header "X-No-Archive: yes" will not be archived
************************************************************************


--
No virus found in this incoming message.
Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.14.8/1064 - Release Date: 10/11/2007 3:09 PM




************************************************************************
* ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in  <==
* ==> the body of an email & send 'em to: [EMAIL PROTECTED] <==
* Join the list: SUBSCRIBE COMPUTERGUYS-L Your Name
* Too much mail? Try Daily Digests command: SET COMPUTERGUYS-L DIGEST
* Tired of the List? Unsubscribe command: SIGNOFF COMPUTERGUYS-L
* New address? From OLD address send: CHANGE COMPUTERGUYS-L YourNewAddress
* Need more help? Send mail to: [EMAIL PROTECTED]
************************************************************************
* List archive at www.mail-archive.com/[email protected]/
* RSS at www.mail-archive.com/[email protected]/maillist.xml
* Messages bearing the header "X-No-Archive: yes" will not be archived
************************************************************************

Reply via email to