5.3 Merge window, part 1
5.3 Merge window, part 1
Posted Jul 16, 2019 23:19 UTC (Tue) by mtaht (subscriber, #11087)In reply to: 5.3 Merge window, part 1 by naptastic
Parent article: 5.3 Merge window, part 1
Only a few routing daemons and related routing hw needs to be modified to make 240/4 globally routable. Babeld already has support, the FRR and bird folk have agreed in principle to make it work, juniper works with a flag, cisco's enterprise routers work, smaller scale ones don't. currently.
Posted Jul 16, 2019 23:40 UTC (Tue)
by Cyberax (✭ supporter ✭, #52523)
[Link] (5 responses)
Is it worth it now?
Posted Jul 17, 2019 3:23 UTC (Wed)
by mtaht (subscriber, #11087)
[Link] (4 responses)
Posted Jul 17, 2019 16:42 UTC (Wed)
by Cyberax (✭ supporter ✭, #52523)
[Link] (1 responses)
So yes, 7 years is about right. However, this assumes linear growth and it's probably not. For example, China has an official plan to move to IPv6 by 2025 with major deployments starting next year.
Posted Jul 18, 2019 6:19 UTC (Thu)
by cpitrat (subscriber, #116459)
[Link]
Posted Jul 17, 2019 20:31 UTC (Wed)
by farnz (subscriber, #17727)
[Link]
The trouble is that if you look at Geoff's IPv4 Address Report, we were consuming more than a /8 per month until we ran out of free-floating addresses. So cleaning up IPv4 needs to provide 84 /8s to get us to 7 years - for decades, you're looking at hundreds of /8s, which is going to get awkward…
Posted Jul 18, 2019 23:02 UTC (Thu)
by naptastic (guest, #60139)
[Link]
5.3 Merge window, part 1
5.3 Merge window, part 1
5.3 Merge window, part 1
5.3 Merge window, part 1
5.3 Merge window, part 1
5.3 Merge window, part 1