[56350] in North American Network Operators' Group

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

Re: BGP to doom us all

daemon@ATHENA.MIT.EDU (Rafi Sadowsky)
Tue Mar 4 05:04:42 2003

Date: Tue, 4 Mar 2003 12:03:29 +0200 (IST)
From: Rafi Sadowsky <rafi-nanog@meron.openu.ac.il>
To: Michael.Dillon@radianz.com
Cc: nanog@merit.edu
In-Reply-To: <OF6005DF5C.BC6FD278-ON80256CDF.0033740D-80256CDF.0033D27C@radianz.com>
Errors-To: owner-nanog-outgoing@merit.edu


## On 2003-03-04 09:26 -0000 Michael.Dillon@radianz.com typed:

> 
> > Uhhhh.... it's nice to be able to change routing information in a
> > timely fashion without needing intensive therapy afterward.  The
> > idea isn't inherently bad, but I'd not want the current ARIN
> > acting as a route registry.
> 
> How would you feel about ARIN being the root of a registry hierarchy that 
> works similar to the DNS?

 I hope you meant IANA as the root of the registry ?
ARIN is (just ;-) a RIR just like RIPE or APNIC  

>> In that case, ARIN would not necessarily hold 
> the route information, they would just be at the top of the search 
> hierarchy just like the root name servers are at the top of the DNS 
> hierarchy. ARIN would authoritatively identify the leaseholder of an 
> address block and give you a pointer to that leaseholder's LDAP server 
> where you could query for whatever info they have available. This could 
> include route registry info.
> 
> --Michael Dillon


-- 
	Rafi
> 
> 
> 
> 
> 



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