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

On 10/11/22 00:37, Matthew Petach wrote: They became even more huffy, insisting that we were breaking the internet by not following the correct routing for the more-specific /24s which were no longer present in our tables.  No amount of trying to explain to them that they should not

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

- Original Message - > From: "Randy Bush" > To: "Edvinas Kairys" > Subject: Re: any dangers of filtering every /24 on full internet table to > preserve FIB space ? >> we're thinking to deny all /24s to save the memory > > i recommend this to all my competitors So good to know things

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

Link to Arista article about their Spotify deployment (2016), has all the relevant links, can be implemented on variety of vendors https://aristanetworks.force.com/AristaCommunity/s/article/spotifys-sdn-internet-routerCheers,JeffOn Oct 10, 2022, at 15:57, Ryan Rawdon wrote:On Oct 10, 2022, at

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

> On Oct 10, 2022, at 6:37 PM, Matthew Petach wrote: > > > > On Mon, Oct 10, 2022 at 8:44 AM Mark Tinka wrote: > On 10/10/22 16:58, Edvinas Kairys wrote: > > > Hello, > > > > We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has > > 24x100G, but only 2.2mln route (FIB)

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

On Mon, Oct 10, 2022 at 8:44 AM Mark Tinka wrote: > On 10/10/22 16:58, Edvinas Kairys wrote: > > > Hello, > > > > We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has > > 24x100G, but only 2.2mln route (FIB) memory entries. In a near future > > it will be not enough - so we're

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

Randy Bush wrote: > it is a tragedy that cidr and an open market has helped us more than > ipv6 has. True. Maybe cidr and an open market for ipv6 addresses would reduce the tragedy? John

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

I frequently do this (accept peer’s, and their customers prefixes), and it works out well. Then you can choose where you want the rest of it to go. With multiple peers in your country this works out quite well. On Mon, Oct 10, 2022 at 5:02 PM richey goldberg wrote: > The OP can always take the

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

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

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

> On 11 Oct 2022, at 4:23 am, Tobias Fiebig > 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

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

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: 8 {'no_less_specific': 16, 'has_less_specific': 0, 'sum': 16, 'least_specific_length': {}} 9 {'no_less_specific': 9,

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

< rant > there once used to be 'swamp' space, down in the low 190s where /24s were expected. and folk/rirs tried to keep shorter aggregates, e.g. /19s, as the norm above swamp (negotiated at ietf/danvers). in those days, one could actually filter above swamp on /19. for a while, one could even

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

On 10/10/22 9:20 AM, Stephane Bortzmeyer wrote: But theoretically every filtered /24 could be routed via smaller prefix /23 /22 /21 or etc. I don't think this is true, even in theory, specially for legacy prefixes. There is probably somewhere a Geoff Huston survey on /24 without a covering

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

On Mon, Oct 10, 2022 at 11:18 AM Jeff Tantsura wrote: > There has been a number of efforts to implement FIB (actually BGP RIB) > compression. > There’s a white paper from MS research; I recall Spotify talking of running > off-box BGP > compression SW and re-injecting summarized BGP RIB; Hi

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

There has been a number of efforts to implement FIB (actually BGP RIB) compression. There’s a white paper from MS research; I recall Spotify talking of running off-box BGP compression SW and re-injecting summarized BGP RIB; Volta Networks had an implementation of full BGP table compression to

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

You’ll need to be very selective about the IP ranges you apply that filter to, or more likely, just do it and make sure have one or more default routes to devices/providers that carry full tables. As for alternate devices, have you looked at Arista 7280, particularly the Jericho >1 versions.

RE: Any experiences using SIIT-DC in an IXP setting ?

As I understand the initial question: the client has no IPv4. Initial “4” in 464XLAT means IPv4 client. DNS64 could mislead the client that the server (on the internet) is available on IPv6. Then NAT64 would convert IPv6 to IPv4. But it is not stateless by any means (requested below). Ed/ From:

Re: Any experiences using SIIT-DC in an IXP setting ?

On Mon, Oct 10, 2022 at 9:17 AM Vasilenko Eduard via NANOG wrote: > The technology for IPv6 client to connect IPv4 web server on Internet is > just not specified in IETF. > > Ed/ > Ed, you seem to be not so familiar with the this ietf body of work RFC6877 “ 464XLAT is a simple and scalable

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

On Mon, Oct 10, 2022 at 8:37 AM Mike Hammett wrote: > Feasibility of adding some middleware that culls unneeded routes (existing > more specific and aggregate routes pointing to the same next hop), when that > table starts to fill? This is called "FIB aggregation." It exists and works but is

RE: Any experiences using SIIT-DC in an IXP setting ?

The technology for IPv6 client to connect IPv4 web server on Internet is just not specified in IETF. Ed/ From: NANOG [mailto:nanog-bounces+vasilenko.eduard=huawei@nanog.org] On Behalf Of Carlos Martinez-Cagnazzo Sent: Monday, October 10, 2022 6:57 PM To: NANOG Subject: Any experiences using

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

I like that idea. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com - Original Message - From: "Jay Hennigan" To: nanog@nanog.org Sent: Monday, October 10, 2022 10:39:06 AM Subject: Re: any dangers of filtering

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

There are most definitely a number of organizations that have /24s that are not part of a larger aggregate. If you don’t have a default route to some router that takes the full table on your behalf, then you will loose connectivity to/from those entities. Owen > On Oct 10, 2022, at 07:58 ,

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

My assumption is that it's not a one-and-done scenario - that the middleware continually adjusts. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com - Original Message - From: "Elmar K. Bins" To: "NANOG Operators'

Any experiences using SIIT-DC in an IXP setting ?

Hi all, I'm looking at a use case for stateless 6-4 mappings in the context of an IXP. The problem we are looking to solve is allowing IXP members who have no IPv4 of their own and in most cases they have a /26 or /27 issued by their transit provider and rely on CGN to provide service to their

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

On 2022-10-10 09:39, Jay Hennigan wrote: On 10/10/22 07:58, Edvinas Kairys wrote: We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has 24x100G, but only 2.2mln route (FIB) memory entries. In a near future it will be not enough - so we're thinking to deny all /24s to save the

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

na...@ics-il.net (Mike Hammett) wrote: > Feasibility of adding some middleware that culls unneeded routes (existing > more specific and aggregate routes pointing to the same next hop), when that > table starts to fill? Well... if that covering prefix goes away, let's hope you still have a

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

> we're thinking to deny all /24s to save the memory i recommend this to all my competitors randy

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

On 10/10/22 17:26, William Herrin wrote: The Internet FIB is around 900k IPv4 routes. You have years before exhausting a 2.2M table. Depends on what else they may be carrying in their IGP, MPLS domain, SR domain, e.t.c. Mark.

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

On 10/10/22 07:58, Edvinas Kairys wrote: Hello, We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has 24x100G, but only 2.2mln route (FIB) memory entries. In a near future it will be not enough - so we're thinking to deny all /24s to save the memory. What do you think about

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

On 10/10/22 16:58, Edvinas Kairys wrote: Hello, We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has 24x100G, but only 2.2mln route (FIB) memory entries. In a near future it will be not enough - so we're thinking to deny all /24s to save the memory. What do you think

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

Feasibility of adding some middleware that culls unneeded routes (existing more specific and aggregate routes pointing to the same next hop), when that table starts to fill? Not great for passing downstream, but should fill a need internally. - Mike Hammett Intelligent Computing

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

If you filter out /23 or longer you cut the v4 table size about in half. I have done this with some edge and eyeball network clients that had really old or underpowered routing gear and upgrades were just not in the budget, and they could barely spell BGP. I know of a number of ASNs with SUP720

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

On Mon, Oct 10, 2022 at 05:20:33PM +0200, Stephane Bortzmeyer wrote a message of 10 lines which said: > > But theoretically every filtered /24 could be routed via smaller > > prefix /23 /22 /21 or etc. > > I don't think this is true, even in theory, specially for legacy > prefixes. I even

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

On Mon, Oct 10, 2022 at 7:58 AM Edvinas Kairys wrote: > We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has > 24x100G, but only 2.2mln route (FIB) memory entries. In a near future it will > be not enough - so we're thinking to deny all /24s to save the memory. What > do you

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

There's 69,055 pure /24's allocated or assigned directly from an RIRs. At least c,d,e, and g root servers only have /24s allocated to them. Major services like Cloudflare only advertise the /24 without advertising an aggregate. Unless you're also getting a default from upstream, it sounds like

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

On Mon, Oct 10, 2022 at 05:58:45PM +0300, Edvinas Kairys wrote a message of 35 lines which said: > But theoretically every filtered /24 could be routed via smaller > prefix /23 /22 /21 or etc. I don't think this is true, even in theory, specially for legacy prefixes. There is probably

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

On Mon, Oct 10, 2022 at 7:59 AM Edvinas Kairys wrote: > Hello, > > We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has > 24x100G, but only 2.2mln route (FIB) memory entries. In a near future it > will be not enough - so we're thinking to deny all /24s to save the memory. >

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

Hello, We're considering to buy some Cisco boxes - NCS-55A1-24H. That box has 24x100G, but only 2.2mln route (FIB) memory entries. In a near future it will be not enough - so we're thinking to deny all /24s to save the memory. What do you think about that approach - I know it could provide some

RE: FCC chairwoman: Fines alone aren't enough (Robocalls)

Hi, > > Most operators here have been against stir/shaken as a means to resolve the > problems. > > What reasons? > That it is complex and would take too much time and money, that it is only effective if done on international level and should only be done if decided on a European level.