Re: [ga] whois.txt, ala robots.txt, as a standard ?

[Rick Wesson <wessorh@ar.com>]

> On 7 Feb 2003 at 12:01, Dan Steinberg wrote:
>
> > where a teen overdosed on drugs which in a chatroom and on cam. The
> > >victim even mentions WHOIS in the chat logs, as a way to reach his
> > >family or for 911. Tragically, the WHOIS appears to have been
> > >inaccurate (phone number was a phone 555-1234), and the teen died. I've
> > >personally talked a few folks out of suicide online, and in one case had
> > >to rely upon WHOIS to help reach one of their relatives. Others have done
> > >the same, reaching their ISP, etc....when time is of the essence, every
> > >piece of data helps.
>
> This would be a case for law enforcement and data would then be available
> in Karl's scenario.  Law enforcement would have access credentials to
> obtain registration information and the information under those
> circumstances would more likely be accurate since people would not be so
> reluctant to provide it.

who are law enforcement and how do you determine they aren't a stalker?
Any time you want to restrict information, allowing only certified
entities access, one must elaborate what the AAA (access, authorization
and authentication) framework is.

how do I (as a registrar) identify a mexican police, or a Malaysian police
officer? What if the issue with the domain is completely legal in the home
country (selling Nazi memorabilia in the usa) and the registrant lives in
Berlin, how do I identify the German police as a "law enforcement"
official? furthermore why should I give up the information for a situation
when no local law is broken?

These and many simular topics will be discussed at a meeting in DC on the
20-21st of this month. with the FTC.

see: http://www.ftc.gov/opa/2002/12/crossborder.htm

-rick




--
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