[27504] in North American Network Operators' Group
Re: whois broke again?
daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Mon Feb 21 16:43:34 2000
From: bmanning@vacation.karoshi.com
Message-Id: <200002212216.OAA12623@vacation.karoshi.com>
To: sean@donelan.com (Sean Donelan)
Date: Mon, 21 Feb 2000 14:16:28 -0800 (PST)
Cc: nanog@merit.edu
In-Reply-To: <20000221212134.8540.cpmta@c004.sfo.cp.net> from "Sean Donelan" at Feb 21, 2000 01:21:34 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
>
> On Mon, 21 February 2000, bmanning@vacation.karoshi.com wrote:
> > Yes there are interesting scoping issues. Yes there are concerns wrt
> > evil people and tolerent applications. But this tactic clearly puts the
> > onus on the people in control of the useage, not some centralized repository.
>
> That sounds great, except the time when WHOIS is most important is when
> the contact has totally screwed up their site and can't be reached by any
> in-band network. The nice thing about WHOIS is it tends to be out-of-band
> with respect to most screw-ups. The notable exception is when NSI screws-up.
See DNS slaves w/ long timeouts. :)
>
> The open question is why can RIPE get people to put good data in their database,
> and NSI can't manage to keep the little correct data they have uncorrupted?
'cause change control is tied up in legalities?
'cause the databases are too large/centralized?
... :)
>
>
>
