My talk's slides and video at netdev 0x13 about "Potential IPv4 Unicast expansions" is up, here:
https://netdevconf.org/0x13/session.html?talk-ipv4-unicast-expansions There are roughly 419 million IPv4 addresses that are unallocated and unused in the 0, localhost, reserved future multicast, and 240/4 spaces. Linux already supports 240/4 fully. SDN's such as AWS already support the entire IPv4 address space as a unicast playground. This first patch for 0/8 was intended primarily as a conversation starter - arguably we should rename the function across 22 fairly "hot" files - but: Should Linux treat these ranges as policy, and no longer enforce via mechanism? A full patchset for adding 225-232, and 127 address spaces is on github: https://github.com/dtaht/unicast-extensions with the very few needed patches for routing daemons and BSD also available there. Dave Taht (1): Allow 0.0.0.0/8 as a valid address range include/linux/in.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.17.1
