At 5:04 AM 8/17/95, Yakov Rekhter wrote:
In IPv6 there is a notion of "IPv4 compatible" addresses. These are IPv6 addresses (128 bits) that have IPv4 address as their low order 32 bits and the rest (96 bits) are zero. ...
What you said is correct only if hosts use IPv6 addresses that are not "IPv4 compatible". But transition with hosts that don't have IPv4 compatible addresses is quite messy.
Yakov; If you have an IPv6 capable host, why use "IPv4 compatible" addresses? Why not use an algorithmic translation that includes a provider prefix? It would seem to me that any IPv6 host should have the capability to algorithmically translate its IPv4 address, preferably dynamically. --Kent
Kent,
If you have an IPv6 capable host, why use "IPv4 compatible" addresses? Why not use an algorithmic translation that includes a provider prefix? It would seem to me that any IPv6 host should have the capability to algorithmically translate its IPv4 address, preferably dynamically.
IPv4 compatible addresses are needed to allow IPv6 communication across IPv4 only "cloud". This way a router at the border between "dual" (IPv6/IPv4) part of a network and IPv4 only part of the network can determine packet's destination by just looking at the low order 32 bits of the IPv6 destination address (the IPv4 address is needed to figure out how to tunnel the packet across the IPv4 only part of the network). An alternative would be to maintain a static mapping on the router (and this is a not an easy manageable proposition). Yakov. P.S. Perhaps this discussion is a bit outside the scope of this list, so we should either (a) continue this in private, or (b) move it to the IPng mailing list.
participants (2)
-
kwe@6SigmaNets.com
-
Yakov Rekhter