Re: maximum ipv4 bgp prefix length of /24 ?

2023-09-30 Thread Owen DeLong via NANOG
Not sure why you think FIB compression is a risk or will be a mess. It’s a pretty straightforward task. Owen > On Sep 30, 2023, at 00:03, Mark Tinka wrote: > >  > >> On 9/30/23 01:36, William Herrin wrote: >> >> >> If I were designing the product, I'd size the SRAM with that in mind.

new net neutrality/title ii mailing list

2023-09-30 Thread Dave Taht
Since network neutrality and title ii regulation is back in the news, and the issues so fraught with technical and political mis-conceptions, I have started a new mailing list to discuss it, and try (for once) to feed back valid techical feedback into the FCC´s normal processes. I kind of expect

Re: Legal system as a weapon (was Re: AFRINIC placed in receivership)

2023-09-30 Thread Noah
Hi David Thanks for sharing this. So, its seems like Lu is continuing with his legal intimadations across other RIR regions. Christopher Hawker, should not be intimidated. I was the first internet community members to be sued by Lu and I believe Amin was the second and Brian and Benedict cases

Re: Legal system as a weapon (was Re: AFRINIC placed in receivership)

2023-09-30 Thread Collider
Lol Le 30 septembre 2023 19:49:29 UTC, Mel Beckman a écrit : >Just like a lawyer, trying to add layers to the model. :) > > -mel > >> On Sep 30, 2023, at 8:58 AM, Anne Mitchell wrote: >> >>  >> >>> On Sep 29, 2023, at 11:20 PM, Mel Beckman wrote: >>> >>> The seven lawyers of the OSI model

Re: Legal system as a weapon (was Re: AFRINIC placed in receivership)

2023-09-30 Thread Mel Beckman
Just like a lawyer, trying to add layers to the model. :) -mel > On Sep 30, 2023, at 8:58 AM, Anne Mitchell wrote: > >  > >> On Sep 29, 2023, at 11:20 PM, Mel Beckman wrote: >> >> The seven lawyers of the OSI model >> >> 1: Family lawyer (where it all starts) >> 2: Admiralty lawyer >> 3:

Re: maximum ipv4 bgp prefix length of /24 ?

2023-09-30 Thread Randy Bush
> About 60% of the table is /24 routes. > Just going to /25 will probably double the table size. or maybe just add 60%, not 100%. and it would take time. agree it would be quite painful. would rather not go there. sad to say, i suspect some degree of lengthening is inevitable. we have

Re: Legal system as a weapon (was Re: AFRINIC placed in receivership)

2023-09-30 Thread Anne Mitchell
> On Sep 29, 2023, at 11:20 PM, Mel Beckman wrote: > > The seven lawyers of the OSI model > > 1: Family lawyer (where it all starts) > 2: Admiralty lawyer > 3: Intellectual Property lawyer (because, of course) > 4. Immigration lawyer > 5. Real Estate lawyer > 6. Entertainment lawyer > 7.

Re: maximum ipv4 bgp prefix length of /24 ?

2023-09-30 Thread Mark Tinka
On 9/30/23 01:36, William Herrin wrote: If I were designing the product, I'd size the SRAM with that in mind. I'd also keep two full copies of the FIB in the outer DRAM so that the PPEs could locklessly access the active one while the standby one gets updated with changes from the RIB. But

Re: maximum ipv4 bgp prefix length of /24 ?

2023-09-30 Thread Mark Tinka
On 9/29/23 22:56, William Herrin wrote: Actually, BGP can swing that. Routing involves two distinct components: the routing information base (RIB) and the forwarding information base (FIB). BGP is part of the RIB portion of that process. It's always implemented in software (no hardware

Re: maximum ipv4 bgp prefix length of /24 ?

2023-09-30 Thread Saku Ytti
On Sat, 30 Sept 2023 at 09:42, Mark Tinka wrote: > > But when everybody upgrades, memory and processor unit prices > > decrease.. Vendors gain from demand. > > > I am yet to see that trend... Indeed. If you look like 10k/10q for Juniper their business is fairly stable in revenue and ports sold.

Re: maximum ipv4 bgp prefix length of /24 ?

2023-09-30 Thread Mark Tinka
On 9/29/23 06:43, VOLKAN SALİH wrote: But when everybody upgrades, memory and processor unit prices decrease.. Vendors gain from demand. I am yet to see that trend... Mark.

Re: maximum ipv4 bgp prefix length of /24 ?

2023-09-30 Thread Saku Ytti
On Fri, 29 Sept 2023 at 23:43, William Herrin wrote: > My understanding of Juniper's approach to the problem is that instead > of employing TCAMs for next-hop lookup, they use general purpose CPUs > operating on a radix tree, exactly as you would for an all-software They use proprietary NPUs,