RE: [gnso-dow123] Whois Operational Point of Contact

[Tim Ruiz <tim@xxxxxxxxxxx>]

<div>The Go Daddy Group supports this proposal:</div>
<div>&nbsp;</div>
<div>Go Daddy Software, Inc. dba GoDaddy.com</div>
<div>Wild West Domains, Inc.</div>
<div>Blue Razor Domains, Inc.<BR><BR>Tim Ruiz<BR>VP, Domain
Services<BR>The Go Daddy Group, Inc.<BR>Office: 319-294-3940<BR>Fax:
480-247-4516<BR><A
href="mailto:tim@xxxxxxxxxxx";>tim@xxxxxxxxxxx</A><BR><BR><BR></div>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT:
blue 2px solid"><BR>-------- Original Message --------<BR>Subject:
[gnso-dow123] Whois Operational Point of Contact<BR>From: Ross Rader
&lt;ross@xxxxxxxxxx&gt;<BR>Date: Tue, November 29, 2005 12:46 am<BR>To:
registrars@xxxxxxxxxxxxxx<BR>Cc:
gnso-dow123@xxxxxxxxxxxxxx<BR><BR>Registrars,<BR><BR>In Mar del Plata,
a small group of like-minded registrars got together <BR>to discuss
possible solutions to the vexing problem of whois. The basic <BR>issue
that the amount of data that ICANN requires registrars to display
<BR>in the whois is facilitating all sorts of undesirable behaviors
like <BR>renewal scams, data-mining, phishing, identity theft, and so
on.<BR><BR>The result of this discussion is a proposal to rationalize
the whois <BR>data output and implement a new contact type called the
"Operational <BR>Point of Contact" or "oPOC". Complete details can be
found in the <BR>proposal itself which I've posted to my weblog -
<BR>http://code.byte.org/blog/_archives/2005/11/28/1426464.html<BR><BR>We
are currently seeking feedback and support for this document. If you
<BR>have any comments, please drop one of the contributors a note. If
you <BR>would like to formally support this proposal as a signatory,
please drop <BR>me a note saying so.<BR><BR>Thanks in advance, please
let me know if you have any questions.<BR><BR>-ross </BLOCKQUOTE>