IPv10
tools.ietf.org
IPv10
1–10 of 132 posts
Re: IPv10
#2Why not IPv16 and fix the problem for ever?
Re: IPv10
#3Why not IPv16 and fix the problem for ever?
> fix the problem forever
Situation: There are 14 competing standards
"14?! Ridiculous! We need to develop one universal standard that covers everyone's use cases." "Yeah!"
Situation: There are 15 competing standards
Re: IPv10
#4Why not IPv16 and fix the problem for ever?
Will it fix it? This seems like a scaling issue we're going to have to deal with forever.
Re: IPv10
#5Why not IPv16 and fix the problem for ever?
[deleted]
Re: IPv10
#6Why V10. Because 4+6?
Re: IPv10
#7Why V10. Because 4+6?
Yes:
"IPv10 allows hosts from two IP versions (IPv4 and IPv6) to be able to communicate, and this can be accomplished by having an IPv10 packet containing a mixture of IPv4 and IPv6 addresses in the same IP packet header."
Re: IPv10
#8Why V10. Because 4+6?
Yes: "IPv10 allows hosts from two IP versions (IPv4 and IPv6) to be able to communicate, and this can be accomplished by having an IPv10 packet containing a mixture of IPv4 and IPv6 addresses in the same IP packet header."
engineers have an obscure way of naming things.
Re: IPv10
#9Why V10. Because 4+6?
>From here the name of IPv10 arises, as the IP packet can contain (IPv6 + IPv4 /IPv4 + IPv6) addresses in the same layer 3 packet header.
Re: IPv10
#10Mildly off-topic, but I've always wondered about having a non-fixed length address scheme: if there are 64 bits in the address, let the first 8 bits (64/8 = 8) be 1 and the 9th bit be 0. This way we encode the length of the address. After that, every bit is available for use (all 64 - 9 = 55 bits).
Suddenly want to increase the domain from 2^55 to something much higher? Use a 15-byte address where the first 15 bits are 1s and the 16th bit is 0. The rest of the (15*8 - 16 = 104) bits are available.
You get the point - we can arbitrarily increase the size without giving up flexibility.
What's the drawback if we use something like this? Routing troubles? Speed?
Alternative method: the addresses can be as many bits as required, but every bit index that's a multiple of 8 must be 1. The last byte is signified by a byte having 0 at index 0. Basically:
[1]1010110 [1]0001111 [0]1101011
^ last byte