BTW - regarding why these effots while being ip-independet would not work for Ipv6, the reason is addressing. We need new kind of addresses and they all require "id" that TCP can use for establishing connection and that ID can not be limited to 32 bit so we end up considering reusing part of IPv6 space for this new kind of "non-ip" addresses. I think given large amount of available IPv6 space that is acceptable - if we cut the pool to 1/4 we'd still have enough.
Correcting myself... Its not that you can not use multi6 with IPv4 - you can but your ip stack will need to be IPv6 capable in order to do it and programs and service should be prepared to deal with 128bit addresses for TCP/UDP connections. So upgrade to support IPv6 will still be necessary, but its not a requirement to actually run ipv6 network. Of course to support something like HIP or Multi6 you will need yet another upgrade to your ip stack and we really should have been pushing these upgrades together with IPv6 itself. -- William Leibzon Elan Networks william@elan.net