2 ms·
The FIRST problem is that IPv6 wasn't designed to be backwards-compatible with IPv4. That is the MAIN reason why its deployment and adoption rate has been a lo
by pmarreck 11y ago
The FIRST problem is that IPv6 wasn't designed to be backwards-compatible with IPv4.
That is the MAIN reason why its deployment and adoption rate has been a long clusterfuck.
- TenOhms 11y agoI wonder if it couldn't still be accomplished at this late hour. An RFC to reserve 32 bits of an IPv6 Address along with a logical (read: Easy to remember) remaining 96 bits might be in order.
- chronid 11y agoIn theory - and if I remember correctly - you can embed IPv4 addresses into IPv6 addresses. The prefix should be all zeroes, so you get something like: ::12.123.99.222 Which is not that hard to remember. :P
- pmarreck 11y agoCould they modify IPv4 in a backwards-compatible way, allocating more address space to that part of the TCP header for example? And including perhaps a version flag? In fact I'm not sure why it wasn't done that way to begin with, unless IPv6 fixes a bunch of other problems I was not aware of
- _ikke_ 11y agoThe problem isn't that IPv6 isn't backwards compattible. The problem is that IPv4 is not forwards compattible. Arstechnica has an article about it: http://arstechnica.com/business/2016/01/ipv6-celebrates-its-20th-birthday-by-reaching-10-percent-deployment/2/ http://arstechnica.com/business/2016/01/ipv6-celebrates-its-...
- lurkinggrue 11y agoYeah, they really didn't think though the transition when designing IPv4.