The Ripe NCC Has Run Out of IPv4 Addresses

Re:The Ripe NCC Has Run Out of IPv4 Addresses by sh-run on Monday November 25, 2019 @03:32PM (#21632474)

Really it's meant to solve the fragmentation that already exists. Cisco developed the standard, but it's completely open.

I believe Cisco is the only large vendor that's implemented it, but there are Linux and BSD implementations, which should make it easy for any Linux or BSD based NOS to implement it in the future.

Honestly this problem will probably be mostly solved in hardware with larger FIBs/TCAMs

Edit - I should clarify the problem I'm referring to here is fragmentation, not exhaustion.

[ Parent | on HN ]

Re:The Ripe NCC Has Run Out of IPv4 Addresses by mprovost on Monday November 25, 2019 @05:19PM (#21633427)

Especially if you stop allocating TCAM memory for the much larger v6 addresses. I hate to think how much memory is sitting out there in routers, configured for 128 bit v6 addresses and never used...

[ Parent | on HN ]

Re:The Ripe NCC Has Run Out of IPv4 Addresses by lmm on Tuesday November 26, 2019 @02:36PM (#21641810)

You only need 64 bits for routing v6, and since the address space isn't fragmented the routing table ends up at a similar efficiency level to the v4 one - probably better once you take into account not needing CIDR.

[ Parent | on HN ]