any dangers of filtering every /24 on full internet table to preserve FIB space ?

• Previous message (by thread): any dangers of filtering every /24 on full internet table to preserve FIB space ?
• Next message (by thread): any dangers of filtering every /24 on full internet table to preserve FIB space ?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

The OP can always take the provider's address space plus their
customer's routes and use a default route to fill in the blanks.    I
did this at a provider years ago where the global routing table
outgrew the speed they could spend the money on upgrades and it worked
out well.    I think it was two upstreams and a connection into  a TIE
with good peering.


-richey

On Mon, Oct 10, 2022 at 4:11 PM Geoff Huston <gih at apnic.net> wrote:
>
>
>
> > On 11 Oct 2022, at 4:23 am, Tobias Fiebig <tobias at reads-this-mailinglist.com> wrote:
> >
> > Heho,
> > Let alone $all the /24 assigned under the RIPE waiting list policy.
> >
> > In the Geoff Huston spirit, I quickly took a look how less specifics for /24s looks in my table:
> >
> […]
>
> > So it seems like there is a healthy amount (~260k) prefixes which lack a less specific.
>
>
> I also looked using a slightly different approach - namely looking for /24s where there was no spanning aggregate that matched the /24’s AS Path. In my local table there are 224,580 of them.
>
>
> Geoff
>
>
>

• Previous message (by thread): any dangers of filtering every /24 on full internet table to preserve FIB space ?
• Next message (by thread): any dangers of filtering every /24 on full internet table to preserve FIB space ?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]