> From: "JinHyeock Choi" <[EMAIL PROTECTED]>
> There are pro and con between them. For example, if an MN receives a complete
> RA which contains all the prefixes, it can form new CoA immediately. Whereas, if
> it receives a RA which contains LinkID but no prefixe, an additional RS/ RA
> exchange is needed.
MIP6 should not configure new COA just because it sees RA. It should
always wait until stack has accepted and configured valid address.
Mobile IP6 should be considered as two almost independent components:
MIP6 and Movement detection (MOVD). Something like follows
IP6 Stack
----------
| |
MIP6 MOVD
MIP6 has really no need for messing with RA's. It should just detect
"movement" by the fact that the CoA it has been using has been removed
from the stack. Then it can find a new CoA from the stack, when it
configures.
MOVD may monitore RA's (and use LinkId's or whatever) or use other
Layer2 meeans to detect movement. When it notices that the link has
changed, it only needs an api to prematurely expire the addressess and
prefixes associated with the old link.
This way MIP6 works regardless of the reason why link goes down (even
if it is done manually).
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
