Xu Xiaohu wrote: > > However, when the ILNP host changes its locator during communicating with a > legacy host, even it updates its AAAA record in the DNS, the legacy host > will not resort to the DNS to get its new IPv6 address immediately after the > locator change. As a result, the already established session between them > will be broken. That's to say, ILNP can not support such a scenario where a > legacy host communicates to a mobile host (ILNP host).
In fact, ILNP isn't going to do much for a legacy host. Period. What was your point? > Note that such a > scenario is supported in Mobile IP. So? Use Mobile IP already then. > By the way, even if the above ILNP host > is not a mobile host, but a fixed host located in a multi-homed site > network, the established session will also be broken when the site is > re-homed to another ISP. The basic reason is the transport association is > bound to one of the ILNP host's locators, rather than its identifier. See paragraph 1. It's a legacy host. It behaves like IPv6. No better, no worse. Upgrade already. ;-) Tony _______________________________________________ rrg mailing list rrg@irtf.org http://www.irtf.org/mailman/listinfo/rrg
