Subject: [Mip6] [issue63] Operations when both v4 and v6 CoAs are available

From: Ryuji Wakikawa <[email-masked]>
Date: Wed, 15 Feb 2006 15:56:17 +0000

New submission from Ryuji Wakikawa <[email-masked]>:

There is no explanation for the case when a mobile node obtains both IPv4 and IPv6 addresses at a foreign 
link. AFAIK, most of IPv6 link is currently provided with IPv4 connectivity . This issue is related to 
movement detection part.

Here is proposed text.

When a mobile node occasionaly acquires both IPv4 and IPv6 care-of addresses at foreign network, it 
SHOULD prioritize IPv6 care-of address for MIP6 binding registration. The mobile node MUST NOT register 
both IPv4 and IPv6 care-of addresses to its home agent. Note that the movement detection must be 
carefully operated since each address assignment may be completed in different time (ex. DHCP and 
address autoconf[rfc2462]). It might be a case that an IPv6 address is assigned after IPv4 address 
assignment. The binding registration flapping between v4 and v6 should be avoided.

----------
category: Technical
draft: draft-ietf-mip6-nemo-v4traversal
messages: 202
nosy: ryuji
priority: Should fix
status: Text proposed
title: Operations when both v4 and v6 CoAs are available

_________________________________________________
Mip6 issue tracker <[email-masked]>
<http://www.mip4.org/issues/tracker/mip6/issue63>
_________________________________________________

_______________________________________________
Mip6 mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mip6