In your letter dated Thu, 28 Jul 2011 18:55:04 -0700 you wrote: >On Jul 28, 2011 5:28 PM, "Martin Rex" <m...@sap.com> wrote: >> It would be so much easier if hosts on the public internet could >> use one single IPv6 address that contains both, the IPv6 network prefix >> and the IPv4 host address, and then let the network figure out whether >> the connect goes through as IPv4 or IPv6 (for IPv6 clients).
In particular, if the remote address is encoded this way. If the host has to chose between an IPv6 or IPv4 destination address then the protocol is fixed. I think that would have been a much better use of thse bits then simply storing the ethernet address there. But anyhow, it should be possible to do that with a destination option with is then inspected by some middle box that makes a routing decision. But that would require a lot of changes to retrofit it in todays operating systems. >This is largely (not entirely) achieved with nat64 / dns64. That would require the dns64 box to do destination selection. Possible, but maybe also tricky to keep a dns resolver informed about the current state of the network. _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
