Re: I-D Action: draft-ietf-idr-deprecate-as-set-confed-set-01.txt

On Mon, Nov 04, 2019 at 11:06:15PM +0000, john heasley wrote:
> > It is a BCP that providers should filter routes that cover their address
> > space.  Filtering out P1/24 and longer is easy.  What do they do about
> > P1/22?  What filtering construct says "this overlaps my /24?"  You've
> > created a new policy need, I think. *
> 
> Which BCP is that?  It is quite common that a provider announces their
> assigned aggregate and multi-homed customers announce the prefixes
> assigned to them from that aggregate.  Perhaps I am mis-understanding
> you.

The dangerous of using acronyms.

My meaning was that it's a best common practice in the operational sense,
not that someone wrote and RFC that has received that capital letter
blessing.

If you network is a more specific in that aggregate, what policy construct
are you using to detect that your prefix is being covered in a less specific?

-- Jeff

_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr