[75495] in North American Network Operators' Group

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

RE: The Cidr Report

daemon@ATHENA.MIT.EDU (Randy Bush)
Sat Nov 13 19:39:37 2004

From: Randy Bush <randy@psg.com>
Date: Sat, 13 Nov 2004 16:38:29 -0800
To: Geoff Huston <cidr-report@potaroo.net>
Cc: "Roldan, Brad" <broldan@Covad.COM>,
	"Christopher L. Morrow" <christopher.morrow@mci.com>,
	<nanog@merit.edu>, <eof-list@ripe.net>, <apops@apops.net>,
	<routing-wg@ripe.net>, <afnog@afnog.org>, <swinog@swinog.ch>
Errors-To: owner-nanog-outgoing@merit.edu


> Interestingly enough what Covad appears to be saying is:
> 
> If we had a way to announce two things
> 
> 1 - here are the advertisements for covering aggregates for Covad
> 
> AND
> 
> 2 - do not believe any more specifics for these address blocks, as they are 
> NOT part of Covad's routing policy for these prefixes
> 
> then we would not be seeing this unfortunate case of unauthorized route 
> leakage being resolved in a way that seems to have unfortunate bgp 
> implications in terms of more specifics appearing.
> 
> So its an interesting question. How could Covad achieve a routing policy 
> announcement of the form as stated in 2 above?

register the covering prefixes in the irr and folk should filter.
folk who don't filter are welcome to the results.  i encourage my
competitors not to filter.

randy


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