Jared Mauch said it as well as I could. Network administrators trying to add a little bit of protection at the firewall cause an entire /8 to be rendered unusable. I think this points back to my Au Revior, SMTP post, since this is related in essence to another growing problem: static site blacklists. If 100,000 mailservers deny mail from domainx.com since domainx.com used to be a spamhaus, then that domain is of Jared Mauch said it as well as I could. Network administrators trying to add a little bit of protection at the firewall cause an entire /8 to be rendered unusable. I think this points back to my Au Revior, SMTP post, since this is related in essence to another growing problem: static site blacklists. If 100,000 mailservers deny mail from domainx.com since domainx.com used to be a spamhaus, then that domain is of limited value. Attempting to change the blacklist rules in thousands and thousands of servers is a futile exercise. The domain becomes Bikini Atoll, never to be habitable. We’ve now proven that this can happen with an infinitely more precious resource, IPv4 public ranges.The crux of the issue is the perceived threat of attack from a IP range that was previously unassigned. This has already caused massive headaches for all involved, and the problem has no good solution. Until every firewall with an implicit deny of the 69.0.0.0/8 range is altered, those 1.6 million IP addresses will have intermittent connectivity with the Internet at large.Will we every reach a point when artificial constraints on network growth are the exception rather than the rule? How would we go about achieving this? Interest, education, and maintenance. The problem is in the human — coders, architects and administrators — not the machine.