Re: IPv4 Address Pool Has Been Expanded Significantly
> The arrogance of proposing the wholesale replacement of the standard
> that the Internet was built on with a "new" and non-inclusive standard was
> not only socially inept, but a major engineering fail. Doubling down by rejecting
> solutions like NAT64 only makes it worse.
Purists may have said NAT66 isn't needed, but that doesn't stop you using it. It can be done.
And as for NAT64, I don't know what you mean by 'rejecting' it - it exists too.
When you consider all the NAT66/NAT64 options, along with the other transition mechanisms, like 6in4, 6over4, 6to4, ISATAP, DNS64, SIIT, MAP, Terodo........... what else could be done?
How can you make a protocol which requires an extended header to be backwards compatible? Do you think there could be a scheme where sometime we'd get addresses like 257.3.3.3 - if we did, it would require an extended header, which would require a new protocol - and these magic addresses won't just work with old stacks.
Please, someone for once just explain how a protocol offering more addresses can be backwards compatible with one offering less? How would you make ip4 stacks magically be able to connect to an expanded space without modification?
Biting the hand that feeds IT
