RE:"Tactical" /24 announcements

Ytti, We have introduced the scalable as-set into the XR route policy language. as-path-set does not scale well with 1000's of ASNs. Now, you don't need to expand AS-SET into prefix-set, just enter it directly. Example: as-set test 2914, 3356, end-set ! route-policy sample if as-path

Re: "Tactical" /24 announcements

Every major vendor at some point in time has implemented RIB->FIB(really BGP->RIB->FIB) filtering, on Redback/Ericsson routers we did around 2013/2014(@Jakob Heitz;-)) Route compression is a more complex topic, it is not difficult to aggregate, it is to effectively disaggregate on changes. MS

Re: "Tactical" /24 announcements

Baldur Norddahl wrote: For all the stub networks out there we should be able to aggressively filter routes without much harm. Stub networks, which, by definition, do not have transit traffic over them, can not filter routes for transit traffic at all. But, if both of two stub networks with

Re: "Tactical" /24 announcements

Tom Beecher wrote: 6.1.3 . at the time of writing of this document, IPv4 prefixes longer than /24 and IPv6 prefixes longer than /48 are generally neither announced nor accepted in the Internet That's why, unlike IPv4, IPv6 is

Re: "Tactical" /24 announcements

On 8/12/21 19:57, Jon Lewis wrote: Yeah...changes to the network could suddenly run such a box out of FIB resources, and you could easily be wrong when predicting how much longer a box has for it's "full routes" days...but the alternatives are "don't do full routes" or replace the box

Re: "Tactical" /24 announcements

On 8/12/21 19:30, Nick Hilliard wrote: it also causes non-deterministic fib resource consumption. On most edge deployments this won't matter, but it wouldn't be hard to cook up a topology that could fail in interesting ways.  Overall fib compression is a net win, but you need to be