[nc-whois] Re: addition of new fields in WHOIS

["Ram Mohan" <rmohan@afilias.info>]

this response, sent on 6/19 is being resent due to mail server issues

-ram
----- Original Message -----
From: "Ram Mohan" <rmohan@afilias.info>
To: "Thomas Roessler" <roessler@does-not-exist.org>; <nc-whois@dnso.org>
Sent: Wednesday, June 19, 2002 11:52 AM
Subject: Re: [nc-whois] [fwd] Re: [ga] Re: [atlarge-discuss] Re:
[nc-transfer] Re: [ncdnhc-discuss] WLSproposal (from: gkirikos@yahoo.com)


> I always worry when a new field is suggested with a hypothetical "here's
how
> it could (or would) be used" as the justification.
>
> Adding another field means that registrars are going to have to expose it
to
> their clients -- many of whom just leave things as the "default".  The
fact
> of life is that current fields are not validly filled -- I cannot see how
> adding yet another field will avoid this problem.
>
> -ram
> ----- Original Message -----
> From: "Thomas Roessler" <roessler@does-not-exist.org>
> To: <nc-whois@dnso.org>
> Sent: Wednesday, June 19, 2002 3:08 AM
> Subject: [nc-whois] [fwd] Re: [ga] Re: [atlarge-discuss] Re: [nc-transfer]
> Re: [ncdnhc-discuss] WLSproposal (from: gkirikos@yahoo.com)
>
>
> > George suggests an "Accepted-Languages" field for the WHOIS
> > database.  Very good point, I believe.
> > --
> > Thomas Roessler                        <roessler@does-not-exist.org>
> >
> >
> >
> >
> > ----- Forwarded message from George Kirikos <gkirikos@yahoo.com> -----
> >
> > From: George Kirikos <gkirikos@yahoo.com>
> > To: ga@dnso.org
> > Date: Tue, 18 Jun 2002 19:32:19 -0700 (PDT)
> > Subject: Re: [ga] Re: [atlarge-discuss] Re: [nc-transfer] Re:
> [ncdnhc-discuss] WLSproposal
> > X-No-Spam: whitelist
> >
> > Hello,
> >
> > --- "L. Gallegos" <jandl@jandl.com> wrote:
> > > The whois is a dangerous mechanism for those who wish to abuse, and
> > > there
> > > are many who do abuse it - enough to scare me, as I was the one
> > > stalked
> >
> > I'd expressed my thoughts on this topic a couple of months ago, see:
> >
> > http://www.dnso.org/clubpublic/ga/Arc10/msg00399.html
> >
> > I don't think privacy rights should be absolute -- costs and benefits
> > should be weighed. However there's a reasonable compromise, in terms of
> > having a legal representative of the domain listed.
> >
> > > The whois may be necessary for the registry to maintain, but it does
> > > not
> > > have to be published.  If there is abuse, the technical contact can
> > > be
> > > reached.  Email can be forwarded via privacy measures to registrants
> >
> > If the technical contact is held legally responsible for the domain's
> > usage, that's comparable to my own proposal. As long as someone can be
> > reached, to hold one accountable for the domain. Either via redefining
> > an existing contact's role, or creating a new contact, i.e. the "Legal
> > Contact".
> >
> > By the way, I was thinking about the WHOIS issue, and might it be of
> > interest to have a field in the database designating the official
> > language(s) for communications to that entity?? English is the defacto
> > language it seems, but it might be useful when thinking about the
> > future. If one is sending an abuse report to a technical contact/legal
> > contact of a domain, and they don't understand English, one would want
> > to know that in advance, via a WHOIS, to be able to communicate with
> > them.
> >
> > So, for instance, the contact record could read for a typical contact:
> >
> > Homer J. Simpson (homer@fox.com)
> > 742 Evergreen Terrace
> > Springfield, Any State
> > USA 99999
> > 555-555-3223, Fax: xxx-555-3226
> > Language(s) of Correspondence: English, French, Swahili, D'oh!
> >
> > Sincerely,
> >
> > George Kirikos
> > http://www.kirikos.com/
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com
> > --
> > 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
> >
> > ----- End forwarded message -----
> >
>
>