I think the purpose of such "for documentation" subnets is that you can give some really valid examples of configuration, where e.g. the user has got a /29 subnet and you want to explain what is the network address, the address of the gateway (router), the subnet broadcast address, and the usable addresses in the network.
Sure you can use things like 44.xx.xx.xx 44.xx.xx.xx+1 etc but usually you will have lost the non-technical reader and it is much better to give examples with real addresses that only have to be adapted to the assigned subnet.
44.128.0.0/16 has been a test subnet for a long time, and there even is romoured use of that range outside AMPRnet as a "test network" or "local range" (similar to RFC1918) due to misunderstanding. I think it would be the last network to ever use when we would ever run out of address space. No need to worry about people having it in their configuration by then, they would have noticed their mistake long before. (44.128.0.0/16 has been in our bogon list of non-routed addresses ever since we established our gateway here in the Netherlands, together with RFC1918, RFC6598, IANA reserved nets)
Rob
On 4/6/21 12:04 AM, Cory (NQ1E) via 44Net wrote:
Ideally you wouldn't use properly formatted IP addresses at all when checking in your code unless they were meant to be used. You could instead use something like: 44.xx.xx.xx
A perfectly reasonable exception to that is if you need your code to pass automated tests that require a properly formatted value to exist there. In that case, using 44net's testing subnet seems not only appropriate, but ideal. ;) _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net