ICANN/GNSO GNSO Email List Archives

[registrars]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [registrars] FW: [dow1tf] TR: IPC constituency statement for Whois TF1

  • To: "'Paul Stahura'" <stahura@xxxxxxxx>, <registrars@xxxxxxxx>
  • Subject: RE: [registrars] FW: [dow1tf] TR: IPC constituency statement for Whois TF1
  • From: "Tim Ruiz" <tim@xxxxxxxxxxx>
  • Date: Tue, 30 Mar 2004 14:50:38 -0600
  • Importance: Normal
  • In-reply-to: <DA6F8AFB015C544AB4385B5DEBDE1FBB0C1C36@mail.enom.com>
  • Sender: owner-registrars@xxxxxxxxxxxxxx

Paul,

As you know, Go Daddy believes that port 43 should be severely restricted,
if not done away with all together. By severely restricted I do NOT mean
some kind of tiered access. I mean most access to port 43 should be stopped
entirely.

The IP community continues to maintain that it is not a significant source
of spam. That is somewhat self-serving of course, but no can argue that it
is not A source of spam. Most registrars have experienced it first hand, as
have tens of thousands of registrants, if not more. But spam is not the
whole point.

Port 43 IS a serious source of data mining for many purposes, including by
the IP community itself. Mining infringes on the rights of registrants and
others whose contact information is used for any number of unspecified
purposes.

We believe that port 43, at most, should be used ONLY by other registrars
for the purpose of facilitating domain name portability, and only then until
a better solution may be found.

It should not be used as a source of information for ANY other commercial
purpose whatsoever, including the so-called value added products referred to
in the IPC statement.

No one should be allowed to take commercial advantage of a resource entirely
collected, maintained, and funded by another party without compensation.

No one should have unfettered, high speed, high volume access to millions of
pieces of personal data about millions of individuals and businesses without
due process.

Paul, I don't see the point in bandaids. If real changes as described above
cannot be made, then leave it alone for now. At least I know what I'm
dealing with and how to minimize the damage.

Tim


-----Original Message-----
From: owner-registrars@xxxxxxxxxxxxxx
[mailto:owner-registrars@xxxxxxxxxxxxxx] On Behalf Of Paul Stahura
Sent: Monday, March 29, 2004 12:55 PM
To: 'registrars@xxxxxxxx'
Subject: [registrars] FW: [dow1tf] TR: IPC constituency statement for Whois
TF1

Fellow registrars, please find attached the IPC constituency statement.
I will be writing a very rough draft of a statement from us for TF1 and
submitting it to the list shortly.
Paul

-----Original Message-----
From: GNSO SECRETARIAT [mailto:gnso.secretariat@xxxxxxxxxxxxxx] 
Sent: Friday, March 26, 2004 1:57 PM
To: Paul Stahura
Subject: TR: [dow1tf] TR: IPC constituency statement for Whois TF1


Paul,
Please see the IPC statement as well for the registrars!
Kind regards

Glen
-----Message d'origine-----
De : owner-dow1tf@xxxxxxxxxxxxxx [mailto:owner-dow1tf@xxxxxxxxxxxxxx]De
la part de GNSO SECRETARIAT
Envoyé : vendredi 26 mars 2004 22:42
À : 1DOW1tf
Cc : Barbara Roseman
Objet : [dow1tf] TR: IPC constituency statement for Whois TF1



Posted on behalf of:
 Steve Metalitz Envoyé : vendredi 26 mars 2004 19:38


Glen,

Attached please find the IPC's constituency statement regarding Whois Task
Force 1 (data mining).  Thank you in advance for ensuring that it is posted
and circulated appropriately.

Steve Metalitz, Exec. VP, IPC




-






<<< Chronological Index >>>    <<< Thread Index >>>