<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>On Nov 18, 2021, at 9:00 AM, John R. Levine <<a href="mailto:johnl@iecc.com" class="">johnl@iecc.com</a>> wrote:<br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">The only effort involved on the IETF's jurisdiction was to stop squatting on 240/4 and perhaps maybe some other small pieces of IPv4 that could possibly be better used elsewhere by others who may choose to do so.<br class=""></blockquote><br class="">The IETF is not the Network Police, and all IETF standards are entirely voluntary.<br class=""></div></div></blockquote><div><br class=""></div>True…</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">Nothing is keeping you from persuading people to change their software to treat class E addresses as routable other than the detail that the idea is silly.<br class=""></div></div></blockquote></div><br class=""><div class="">Of course, it’s not quite that simple.</div><div class=""><br class=""></div><div class="">First, <a href="https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml" class="">https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml</a> would need to be updated, then the RIRs would need to issue a request according to <a href="https://www.icann.org/resources/pages/allocation-ipv4-rirs-2012-02-25-en" class="">https://www.icann.org/resources/pages/allocation-ipv4-rirs-2012-02-25-en</a>. At that point, existing requests lodged at the RIRs could be fulfilled using the formerly reserved space. Network operators that received the allocations could then number their devices with the new address space and announcing that space into the routing system.</div><div class=""><br class=""></div><div class="">Of course, there are probably an unknowable number of “bogon” filters out there that are hardcoded into various bits of infrastructure that would need to be updated. There are also various hardware, firmware, and software IP stack implementations, perhaps sitting in closets somewhere, that still think they can’t use reserved space that would need to be updated/replaced. </div><div class=""><br class=""></div><div class="">As far as I can tell, assertions about the scale of that update/replace exercise are based on limited data. Perhaps as an alternative to declaring various chunks of reserved space as free for use, a chunk of that space could be allocated to one or more of the RIRs and announced with a set of services placed upon it to see just how much actually breaks, similar to what APNIC and Cloudflare did with 1.1.1.0/24?</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">-drc</div><div class=""><br class=""></div></body></html>