Subject: [Mip6] [issue70] The IP address fields are unclear when IPv4 traffic is tunneled

From: Ryuji Wakikawa <[email-masked]>
Date: Mon, 06 Mar 2006 17:06:11 +0000

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

When a MN communicates with IPv6-HoA from IPv4 foreign link, there is no texts 
about how IP headers are specified.

*option1
MN->HA
IPv4 (src = IPv4-CoA, dst= IPv4-HA)
IPv6 (src = IPv6-MAPPED, dst= IPV6-HA)
    HoA (IPv6-HoA)

HA->MN
IPv4 (src = IPv4-HA, dst= IPv4-CoA)
IPv6 (src = IPv6-HA, dst= IPV6-MAPPED)
    RTHDR(IPv6-HoA)

*option2
MN->HA
IPv4 (src = IPv4-CoA, dst= IPv4-HA)
IPv6 (src = IPv6-HoA, dst= IPV6-HA)

HA->MN
IPv4 (src = IPv4-HA, dst= IPv4-CoA)

I prefer the option 2, because it can save the packet size.
Furthermore, carrying IPv4 mapped address in the IPv6 headers are
troublesome.  Since the MN may not configure the IPv4-MAPPED address
on the network interface, it can not receive any packets meant for the
IPv4-MAPPED address. There is no routing entry for the IPv4 mapped
address and MN can not treat that the received packets are mine.

We should use the IPv4 mapped address only for managing IPv4 CoA in
database of MIP6 such as BUL, BC. Otherwise, the MN must create a
route entry for the IPv4-MAPPED.

----------
category: Technical
draft: draft-ietf-mip6-nemo-v4traversal
messages: 222
nosy: ryuji
priority: Must fix
status: Pending
title: The IP address fields are unclear when IPv4 traffic is tunneled

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

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