3 ms·
Prefix every IP with 'missing' info with 0.0. Part of this would just be transitory, but... would take up far less space. Even as late as last year, I'm readi
by lowercased 2y ago
Prefix every IP with 'missing' info with 0.0.
Part of this would just be transitory, but... would take up far less space. Even as late as last year, I'm reading stories about BGP issues and slowdowns because routing tables are too large/many for the hardware. In 2024. How on earth was this expected to work on hardware from 1999?
- Dylan16807 2y agoThose routing tables are badly made. An IPv6 route takes twice as much memory as an IPv4 route, and there are a lot less than half as many IPv6 routes. https://blog.apnic.net/wp-content/uploads/2023/01/Figure-1-%E2%80%93-IPv4-routing-table-since-1994-as-seen-by-Route-Views-peers..png https://blog.apnic.net/wp-content/uploads/2023/01/Figure-1-%... https://blog.apnic.net/wp-content/uploads/2023/01/Figure-14-%E2%80%94-IPv6-routing-table-since-2004-as-seen-by-Route-Views-peers..png https://blog.apnic.net/wp-content/uploads/2023/01/Figure-14-...
- yrro 2y agothere is something called an "IPv4-compatible IPv6 address" and it's exactly the scheme you suggest: the first 96 bits are zero. It doesn't help deal with the billions of devices that only handle a 32-bit address space, however. What do you suggest we do with them? _They_ are the long tail that keeps us in the dual stack world.