According to a blog post, written by Dave Taht, director of the Make-Wifi-Fast and committed by David Stephen Miller, an American software developer mentions that the use of 0.0.0.0/8 has been prohibited since the beginning due to two main issues.
Why the use of 0.0.0.0/8 was prohibited until now?
The use of 0.x.y.z was later revoked in RFC1122. The reason was — the original ICMP-based mechanism for learning the network prefix wasn’t working on many networks such as Ethernet. This is due to the longer addresses that couldn’t fit into the 24 node number bits. Modern networks use reverse ARP, BOOTP or DHCP to find their 32-bit address and CIDR netmask. 0.x.y.z has had a total of 16,777,215 addresses left unused and reserved for future use in 0.0.0.0/8 space. If you are unaware, whole the discussion of allowing these IP Addresses was started during early this year at NetDevConf 2019, the technical conference on Linux Networking. The conference was held from March 20th to 22nd, 2019 in Prague, Czech Republic. One of the sessions, “Potential IPv4 Unicast Expansions”, was conducted by Dave Taht, along with John Gilmore, and Paul Wouters. Also Read: Linux 5.1 Released with Memory and Security Improvements Patch code for 0.0.0.0/8 for Linux:
As the majority of Internet client nodes don’t have IPv6 addresses yet, service sites still need IPv4 addresses for everything. These addresses now cost around USD 15 – 20 apiece (times the size of your network) and the price keeps rising. Lastly, users have a mixed reaction to this announcement. They assume these addresses would be unassigned forever. A user explained the difference between the address ranges in a post, “0.0.0.0/8 – Addresses in this block refer to source hosts on ‘this’ network. Address 0.0.0.0/32 may be used as a source address for this host on this network; other addresses within 0.0.0.0/8 may be used to refer to specified hosts on this network.” A few people also mentioned that for most business, IPv6 is still an unnecessary headache.
