Jeff Chan wrote:
Ask application writers like SpamAssassin and others to check or modify their code to be able to handle bits in the other octets, i.e. 127.0.1.X, 127.64.X.X, etc. Should we let them know ahead of time that their code should be able to handle these cases without breaking?
In rxwhois 1.7.1 dedicated to one "Jeff Chan" <eg> I've added support for either 127.0.X.Y or 127.1.X.Y. The latter is for OPM and allows up to 16 bits.
For the former I now display 127.0.0.0/31 as "utter dubious".
2.0.0.127.wadb.isipp.com = 127.0.0.1, I'll probably eliminate WADB, it's below my minimal standards for any well-behaved BL. We can discuss about more than 16 bits in 2006, is that okay ?
Comments?
I'm not sure why OPM uses 127.1.0.Y instead of 127.0.0.Y.
A simple explanation would be "avoid 127.0.0.0/31 like hell and allow up to 8 bits in Y". Another explanation could be "no 127.0.0.0/31, up to 16 bits in 127.1.X.Y, _and_ additionally a version number in the case of incompatible changes, starting with version 1 in 127.1.X.Y". Bye, Frank