Ah, I stand corrected; I've updated the entry. The section on 44.128/16 was pointing to an obsolete article that incorrectly gave the impression that that subnet was unroutable like an RFC1918 network, whereas it's really just reserved for testing.
Unfortunately, there's an article on www.eastnetpacket.net that incorrectly states that it *IS* an RFC1918-style network and people outside the AMPRNet are quoting it as justification for using the network AS an unrouted network.
Well, that amprnets.txt file of course has existed and has been maintained on hamradio.ucsd.edu for many many years. I have 3 old copies and all of them mention that it may be assumed that any packets with 44.128 addresses are bogons, so this text has probably been there for at least a decade if not much more.
Currently this file does not exist anymore at hamradio.ucsd.edu, I presume its function has been taken over by the "networks" menu item at portal.ampr.org.
However, that listing does not mention 44.128.0.0/16 at all. When it is desired to change the definition of this subnet, it may be better to provide an explicit new definition, instead of trying to remove the old definition from internet without providing a new one. I think that is not going to work well, given the way information is stored, copied and archived on the web.
Also note that this information on portal.ampr.org is only available to registered users, so it would be wise to put some information on a publicly available site as well (maybe a description of the subnetting of net 44 at the top level without all that country-specific info). That could be on the www.ampr.org site.
Rob
On Sun, Nov 06, 2016 at 10:45:04AM +0100, Rob Janssen wrote:
Also note that this information on portal.ampr.org is only available to registered users, so it would be wise to put some information on a publicly available site as well (maybe a description of the subnetting of net 44 at the top level without all that country-specific info). That could be on the www.ampr.org site.
I'll work on writing something along those lines. In the meantime, I added an entry for 44.128.0.0/16 to the FAQ on the wiki. That may help a little. - Brian