pull down to refresh

I'm one of the reasons as well!

IPv6 was designed by very very smart people and in terms of a stand-alone protocol its great. However in the sense of a protocol meant to migrated to from IPv4 its very cumbersome. You basically need 2 distinct network stacks each with their own issues.

I'm not a network engineer but over the years I've heard people propose that we should've just added another one or two octets. So instead of A.B.C.D we could've had A.B.C.D.E.F

In fact it seems the smart way would've been to expand A.B.C.D into E.F.A.B.C.D, that is prepend the new octets to beginning then infer that 12.1.1.1 is really 0.0.12.1.1. to help with backwards compatibility.

That "extension" proposal was rejected because it was seen as a hack and they wanted to expand the space so much that literally nearly every grain of sand could get its own IP address, but its created lots of migration issues.

122 sats \ 1 reply \ @brink 21 Jul
IPv6 was designed by very very smart people and in terms of a stand-alone protocol its great.

I doubt it, ipv6 is overly complicated.

In fact it seems the smart way would've been to expand A.B.C.D into E.F.A.B.C.D, that is prepend the new octets to beginning then infer that 12.1.1.1 is really 0.0.12.1.1. to help with backwards compatibility.

Sounds smart.

That "extension" proposal was rejected because it was seen as a hack and they wanted to expand the space so much that literally nearly every grain of sand could get its own IP address, but its created lots of migration issues.

Sounds dumb, maybe even done on purpose to facilitate user surveillance.

reply
11 sats \ 0 replies \ @justin_shocknet 21 Jul -489 sats

Interesting bit of history considering IP4 gateways have made IP6 a defacto extension much like they tried to avoid