RE: [arch-d] Mobility and multi-homing: Summary and going forward

> Absolutely!  That's they way it was designed, coincidentally. :-)

Trouble is that IPv6 most interesting feature is that it can provide
for large number of internet-connected hosts, that means number of
hosts would increase quite a bit and so per-host multi-homing ends
up being quite expensive to maintain. If any such type of multi-homing
is to exist and be widely used (especially in enterprise and businesses)
it would have to allow for easy network-wide setup & configuration
and without a need to renumber when you change providers.

So, I see the result of current effort is that those businesses would
not actually do per-host multi-homing [even though that is what protocol
would specify] but would use intermediate gateway device. All local
hosts on their network instead of having global ipv6 address would use
some type of shim6 host id and this network device would translate
between those host ids and real IPv6 addresses as well as maintain
proper dns configuration for such lan. Unless I'm mistaken such
setup is called NAT! So the result is that you'd now have special
protocol that would allow to use NAT not only for outgoing traffic
load-balancing (current NAT gateways can already translate into more
then one address pool) but also for incoming traffic multi-homing.

So if you want to introduce and greatly increase use of NAT in IPv6
(as compared to IPv4), please by all means continue with shim6!

-- 
William Leibzon
Elan Networks
william@elan.net

_______________________________________________
Architecture-discuss mailing list
Architecture-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/architecture-discuss