RE: [Mip4] I-D ACTION:draft-ietf-mip4-dsmipv4-03.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Mip4] I-D ACTION:draft-ietf-mip4-dsmipv4-03.txt
Hi George,
>
> GT> OK, I see. I will modify the appropriate part of section 4.3.2 as
> follows, based on corresponding text in 3344, so tell me if it works:
> " 1) Registration request is received with one or more IPv6 prefix
> extensions. An IPv6 tunneling mode extension is not included.
>
> All IPv6 packets destined to the registered IPv6
> prefix(es) MUST be tunneled by the home agent to
> the registered IPv4 home address of the mobile.
>
> ===start of new text=======
> The home agent first encapsulates the IPv6
> packet addressed to the mobile node's IPv4 home
> address, and then tunnels this encapsulated
> datagram to the foreign agent. This extra level
> of encapsulation is required so that IPv6
> routing remains transparent to a foreign agent
> that does not support IPv6. When received by the
> foreign agent, the unicast encapsulated packet is
> detunneled and delivered to the mobile node in
> the same way as any other datagram. The mobile
> node must decapsulate the received IPv4 packet
> it receives in order to recover the original
> IPv6 packet.
> ======end of new text========
> Additionally, the home agent MUST
> be prepared to accept reverse tunneled packets
> from the IPv4 home address of the mobile
> encapsulating IPv6 packets sent by that mobile."
>
This is good.
Thanks
Sri
--
Mip4 mailing list: Mip4 at ietf.org
Web interface: https://www1.ietf.org/mailman/listinfo/mip4
Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.