RE: [ga] WHOIS accuracy, and name deletions

["Abel Wisman" <abel@able-towers.com>]

We are forgetting a few things here:

Domains that have invalid data sometimes (often) Are registered with a
"faulty" credit card.
They are only used for a short period of time, usually no longer then a
few weeks.
Furthermore in the suggested method I could easily take out bunches of
domains (again with "faulty cc data") and block the domains for any
extended period.

And not in the least:

When registering a domain you enter a legal agreement, not giving the
correct data is definitely against the law, whether you like what they
do with the data or not, that is a separate case all together.


However what everyone seems to ignore:
If a domain is registered and paid for by cc (the most ?) then a valid
data set should already be available, checked and counterchecked for
security and charge-backs.

Having a check at that level means that there will be a lot less invalid
whois fields.

The remainder can easily fall under any kind of policy whereby I support
that notification should be done according to a set of agreed upon
rules, and accounting for mail delivery to anywhere on earth.

Kind regards

Abel


-----Original Message-----
From: owner-discuss-list@opensrs.org
[mailto:owner-discuss-list@opensrs.org] On Behalf Of Marc Schneiders
Sent: 08 January 2003 12:25
To: Srikanth Narra
Cc: discuss-list@opensrs.org; ga@dnso.org
Subject: Re: [ga] WHOIS accuracy, and name deletions


I very much agree with the position outlined below. I would rather have
a voluntary WHOIS (meaning you can be in there with the data you want,
except perhaps some bare minimum for TECHNICAL contact, say email
address), but I guess the power of the Intellectual Property People is
too big to achieve that. So let's make it easy then for all of us. And
fair.

On Wed, 8 Jan 2003, at 00:17 [=GMT-0500], Srikanth Narra wrote:

> Deleting a domain because of inaccurate WHOIS record is not right. 
> Someone paid for it. If the registrar didn't have problem accepting 
> the money - they or someone else should not invent causes to delete 
> it.
>
> I can not comprehend and am yet to hear a single legitimate reason or 
> benefit that comes from a domain being deleted because of an 
> inaccurate WHOIS record. If its current policy then its wrong policy 
> and should be changed.
>
> Even in (extreme) cases like say spamming or malicious virus attacks, 
> etc. from a domain with inaccurate WHOIS record. I don't see any 
> reason for the domain to be deleted. The domain marked be marked and 
> left disabled.
>
> Adding and displaying a few fields
>
> a. Status - [Disabled]
> b. Reason - [Spam /Court order?]
> c. Whom to contact to Enable - [Registrar contact info]
>
> along with/to WHOIS record should take care of providing concrete 
> notice and issues arising from trying to reach the registrant with no 
> irreversible harm done.
>
> If the entity behind the domain is genuine - they will contact sooner 
> or later. Else the domain allowed to die its natural death in 
> continued Disable stage AFTER its time runs out. A check can be 
> enforced at the time of renewal for the MARKED domains to ensure the 
> WHOIS record is right.
>
> Between this and existing established law, procedure and channels to 
> take things to next step - I can not think of any issues that can not 
> be handled.
>
> An organization, society or a civilization is only
>
> as robust as rights that exist within it for all parties and as 
> honorable as the fairness, the extent and the manner in which such 
> rights are enforced.
>
> I am hoping there is still some sense of honor and some resemblance of

> fairplay left.
>
> Sri
>
>
> --
> This message was passed to you via the ga@dnso.org list.
> Send mail to majordomo@dnso.org to unsubscribe
> ("unsubscribe ga" in the body of the message).
> Archives at http://www.dnso.org/archives.html
>

--
This message was passed to you via the ga@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html