* Here in the Washington DC area, we are ready and willing to make use of address space over RF links and make use of 44 address space. * I personally use 44 space for experimentation and development of new protocols, which in most cases, might not work over the Public Internet. I also am working to implement services and mesh access to/from agencies the our ARES/RACES serves (e.g. standing links in situation rooms of our local hospitals, public health facilities, shelter go-kits, etc.). * I'm not sure you reviewed RFC-6598 before suggesting use of 100.64.0.0/10 address space; but there are many technical restrictions that must be considered if using this address space. - DNS and Reverse DNS cannot be used - The addresses should not be forwarded outside of the "carrier's network," which could happen easily, even if by mistake - DNS filtering of addresses is recommended as to prevent leakage of 100.64.0.0/10 queries into the public Internet - A gateway's connectivity to the Public Internet may be lost if the carrier providing your "public" IP address switches to Carrier-Grade NATing (CGN) - Newer devices may be RFC6598 aware and not behave correctly using CGN IP space (e.g. not provide DNS responses, not routing or forwarding packets, etc.) If you need other private address space consider... 100.64.0.0/10 as defined in RFC-6598. 73, Lynwood KB3VWG