[33230] 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 14:23:08 2001

From: bmanning@vacation.karoshi.com
Message-Id: <200101041853.SAA05689@vacation.karoshi.com>
To: mark-list@mentovai.com (Mark Mentovai)
Date: Thu, 4 Jan 2001 18:53:52 +0000 (UCT)
Cc: ppml@arin.net, bet@rahul.net (Bennett Todd), nanog@merit.edu,
	ginny@arin.net
In-Reply-To: <Pine.GSO.4.31.0101041329010.17633-100000@pine.ggn.net> from "Mark Mentovai" at Jan 04, 2001 01:56:51 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu


> Finally, the ability to submit assignment and allocation information via
> rwhois seems like a license for inconsistency.  Rwhois was a great idea that
> never took off.  It would be interesting if this information could be
> provided by splintering off a new DNS class (or at least some new RR types.)
> Has anyone ever considered this?
> 
> Mark
> 

rWhois is still a great idea, however the learning curve is a bit steep.
It is possible to dump RPSL data into the DNS and use the inverse tree
to track assignments & allocations.  It can even be used to track 
prefered announcing parties. (being able to track proxy aggregations
fairly easily.) Varients on these types of proposals were made in the
old RIDEwg in the IETF (prox 2 years ago) and there was a NANOG presentation
on using the data in the DNS to authenticate routing announcements. Twas
a bit extreme.

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.

--bill


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