[33235] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: fwd ppml: ARIN asking about SWIP procedures

daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Thu Jan 4 16:18:25 2001

From: bmanning@vacation.karoshi.com
Message-Id: <200101042050.UAA05857@vacation.karoshi.com>
To: ehall@ehsco.com (Eric A. Hall)
Date: Thu, 4 Jan 2001 20:50:09 +0000 (UCT)
Cc: mark-list@mentovai.com (Mark Mentovai), ppml@arin.net,
	bet@rahul.net (Bennett Todd), nanog@merit.edu, ginny@arin.net
In-Reply-To: <3A54D4A6.89F845D8@ehsco.com> from "Eric A. Hall" at Jan 04, 2001 11:53:10 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu


> 
> > That said, I'll posit that the adoption rate of new DNS code is fairly
> > slow (based on 3 years of study) and so even if some goofy new class or
> > RR type is promoted, it would not get deployed anytime soon.
> 
> All of this stuff (global WHOIS included) really needs to go into LDAP,
> using standardized schemas for the relevant data. Obviously the schema is
> job #1. All of the [g/cc]TLD databases and numbering authoritites really
> should have made this a collective priority a couple of years ago.
> 
> Note that putting the data into LDAP doesn't preclude WHOIS clients from
> talking to a WHOIS server which proxies the LDAP data.
> 
> -- 
> Eric A. Hall                                        http://www.ehsco.com/
> Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/


	LDAP might just have a chance. But it looks alot like the
	x500 stuff from the last decade.  I remain unconvinced.

--bill


home help back first fref pref prev next nref lref last post