On 12/08/2021 18:09, Jon Lewis wrote: >> >> Having an upstream provider that did it, in a very aggressive >> fashion. > > Odds are, they did it wrong, and you had no control and limited, if > any, visibility into what they did. Obviously, if you're going to > blindly filter routes based on prefix-length, you need to point > default at something that doesn't...and if you're acting as a transit > provider, you're likely no longer able to provide "full routes" to > customers from devices doing this or fed the "not so full table" from > devices doing it.
Yes. This is precisely why I wrote my initial email, and perhaps I wasn't specific enough, but it was a fairly generic warning against "bright ideas" that don't include the proper scrutiny (or _do_ include unnecessary amounts of arrogance). > Arista. They call it FIB compression. They mention it's a > trade-off, more memory and CPU utilization (keeping track of things) > in exchange for being able to keep hardware that might otherwise be > out of FIB space able to cope with full tables. Ah, thank you, noted. -- Tom