draft-ietf-mext-nemo-v4traversal-09.txt   draft-ietf-mext-nemo-v4traversal-10.txt 
Network Working Group H. Soliman, Ed. Network Working Group H. Soliman, Ed.
Internet-Draft Elevate Technologies Internet-Draft Elevate Technologies
Intended status: Standards Track February 27, 2009 Intended status: Standards Track April 7, 2009
Expires: August 31, 2009 Expires: October 9, 2009
Mobile IPv6 Support for Dual Stack Hosts and Routers Mobile IPv6 Support for Dual Stack Hosts and Routers
draft-ietf-mext-nemo-v4traversal-09.txt draft-ietf-mext-nemo-v4traversal-10.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 31, 2009. This Internet-Draft will expire on October 9, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 21 skipping to change at page 2, line 21
specification also allows the Mobile Node to roam over both IPv6 and specification also allows the Mobile Node to roam over both IPv6 and
IPv4, including the case where Network Address Translation is present IPv4, including the case where Network Address Translation is present
on the path between the mobile node and its home agent. on the path between the mobile node and its home agent.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 4 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Motivation for Using Mobile IPv6 Only . . . . . . . . . . 6 2.1. Motivation for Using Mobile IPv6 Only . . . . . . . . . . 6
2.2. Scenarios Considered by This Specification . . . . . . . . 6 2.2. Scenarios Considered by This Specification . . . . . . . . 6
3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 8 3. Solution Overview . . . . . . . . . . . . . . . . . . . . . . 9
3.1. Home Agent Address Discovery . . . . . . . . . . . . . . . 8 3.1. Home Agent Address Discovery . . . . . . . . . . . . . . . 9
3.2. Mobile Prefix Solicitation and Advertisement . . . . . . . 9 3.2. Mobile Prefix Solicitation and Advertisement . . . . . . . 10
3.3. Binding Management . . . . . . . . . . . . . . . . . . . . 9 3.3. Binding Management . . . . . . . . . . . . . . . . . . . . 10
3.3.1. Foreign Network Supports IPv6 . . . . . . . . . . . . 10 3.3.1. Foreign Network Supports IPv6 . . . . . . . . . . . . 11
3.3.2. Foreign Network Supports IPv4 Only . . . . . . . . . . 10 3.3.2. Foreign Network Supports IPv4 Only . . . . . . . . . . 11
3.4. Route Optimization . . . . . . . . . . . . . . . . . . . . 12 3.4. Route Optimization . . . . . . . . . . . . . . . . . . . . 13
3.5. Dynamic IPv4 Home Address Allocation . . . . . . . . . . . 13 3.5. Dynamic IPv4 Home Address Allocation . . . . . . . . . . . 14
4. Extensions And Modifications To Mobile IPv6 . . . . . . . . . 14 4. Extensions And Modifications To Mobile IPv6 . . . . . . . . . 15
4.1. Binding Update Extensions . . . . . . . . . . . . . . . . 14 4.1. Binding Update Extensions . . . . . . . . . . . . . . . . 15
4.1.1. IPv4 Home Address Option . . . . . . . . . . . . . . . 14 4.1.1. IPv4 Home Address Option . . . . . . . . . . . . . . . 15
4.1.2. The IPv4 Care-of Address Option . . . . . . . . . . . 15 4.1.2. The IPv4 Care-of Address Option . . . . . . . . . . . 16
4.1.3. The Binding Update Message Extensions . . . . . . . . 16 4.1.3. The Binding Update Message Extensions . . . . . . . . 17
4.2. Binding Acknowledgement Extensions . . . . . . . . . . . . 16 4.2. Binding Acknowledgement Extensions . . . . . . . . . . . . 17
4.2.1. IPv4 Address Acknowledgement Option . . . . . . . . . 16 4.2.1. IPv4 Address Acknowledgement Option . . . . . . . . . 17
4.2.2. The NAT Detection Option . . . . . . . . . . . . . . . 18 4.2.2. The NAT Detection Option . . . . . . . . . . . . . . . 19
5. Protocol operation . . . . . . . . . . . . . . . . . . . . . . 20 5. Protocol operation . . . . . . . . . . . . . . . . . . . . . . 21
5.1. Tunelling Formats . . . . . . . . . . . . . . . . . . . . 20 5.1. Tunelling Formats . . . . . . . . . . . . . . . . . . . . 21
5.1.1. tunnelling Impacts on Transport and MTU . . . . . . . 21 5.1.1. tunnelling Impacts on Transport and MTU . . . . . . . 22
5.2. NAT Detection . . . . . . . . . . . . . . . . . . . . . . 21 5.2. NAT Detection . . . . . . . . . . . . . . . . . . . . . . 22
5.3. NAT Keepalives . . . . . . . . . . . . . . . . . . . . . . 23 5.3. NAT Keepalives . . . . . . . . . . . . . . . . . . . . . . 24
5.4. Mobile Node Operation . . . . . . . . . . . . . . . . . . 24 5.4. Mobile Node Operation . . . . . . . . . . . . . . . . . . 25
5.4.1. Selecting a Care-of address . . . . . . . . . . . . . 24 5.4.1. Selecting a Care-of address . . . . . . . . . . . . . 25
5.4.2. Sending Binding Updates . . . . . . . . . . . . . . . 25 5.4.2. Sending Binding Updates . . . . . . . . . . . . . . . 26
5.4.3. Sending Packets from a Visited Network . . . . . . . . 27 5.4.3. Sending Packets from a Visited Network . . . . . . . . 28
5.4.4. Movement Detection in IPv4-only Networks . . . . . . . 28 5.4.4. Movement Detection in IPv4-only Networks . . . . . . . 29
5.5. Home agent operation . . . . . . . . . . . . . . . . . . . 28 5.5. Home agent operation . . . . . . . . . . . . . . . . . . . 29
5.5.1. Sending Packets to the Mobile Node . . . . . . . . . . 30 5.5.1. Sending Packets to the Mobile Node . . . . . . . . . . 31
5.6. Correspondent Node Operation . . . . . . . . . . . . . . . 31 5.6. Correspondent Node Operation . . . . . . . . . . . . . . . 32
6. Security Considerations . . . . . . . . . . . . . . . . . . . 32 6. Security Considerations . . . . . . . . . . . . . . . . . . . 33
6.1. Handover Interactions for IPsec and IKE . . . . . . . . . 33 6.1. Handover Interactions for IPsec and IKE . . . . . . . . . 34
6.2. IKE negotiation messages between the mobile node and 6.2. IKE negotiation messages between the mobile node and
Home Agent . . . . . . . . . . . . . . . . . . . . . . . . 35 Home Agent . . . . . . . . . . . . . . . . . . . . . . . . 36
6.2.1. IKEv2 Operation for Securing DSMIPv6 Signaling . . . . 36 6.2.1. IKEv2 Operation for Securing DSMIPv6 Signaling . . . . 37
6.2.2. IKEv2 Operation for Securing Data over IPv4 . . . . . 39 6.2.2. IKEv2 Operation for Securing Data over IPv4 . . . . . 40
7. Protocol Constants . . . . . . . . . . . . . . . . . . . . . . 41 7. Protocol Constants . . . . . . . . . . . . . . . . . . . . . . 42
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 42 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45
10.1. Normative References . . . . . . . . . . . . . . . . . . . 44 10.1. Normative References . . . . . . . . . . . . . . . . . . . 45
10.2. Informative . . . . . . . . . . . . . . . . . . . . . . . 44 10.2. Informative . . . . . . . . . . . . . . . . . . . . . . . 46
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 46 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 47
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 47 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 48
1. Requirements notation 1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
Mobile IPv6 [RFC3775] and [RFC3963] allow mobile nodes to move within Mobile IPv6 [RFC3775] and [RFC3963] allow mobile nodes to move within
skipping to change at page 7, line 9 skipping to change at page 7, line 9
In this scenario, a mobile node is connected to an IPv4-only foreign In this scenario, a mobile node is connected to an IPv4-only foreign
network. The mobile node can only configure an IPv4 Care-of Address. network. The mobile node can only configure an IPv4 Care-of Address.
Scenario 2: Mobile node behind a NAT Scenario 2: Mobile node behind a NAT
In this scenario, the mobile node is in a private IPv4 foreign In this scenario, the mobile node is in a private IPv4 foreign
network that has a NAT device connecting it to the Internet. If the network that has a NAT device connecting it to the Internet. If the
home agent is located outside the NAT device, the mobile node will home agent is located outside the NAT device, the mobile node will
need a NAT traversal mechanism to communicate with the home agent. need a NAT traversal mechanism to communicate with the home agent.
It should be noted that [RFC5389] highlights issues with some types
of NATs that act as generic ALGs and rewrite any 32-bit field
containing the NAT's public IP addresses. This specification will
not support such NATs.
Scenario 3: Home Agent behind a NAT Scenario 3: Home Agent behind a NAT
In this scenario, the communication between the mobile node and the In this scenario, the communication between the mobile node and the
home agent is further complicated by the fact that the home agent is home agent is further complicated by the fact that the home agent is
located within a private IPv4 network. However, in this scenario, we located within a private IPv4 network. However, in this scenario, we
assume that the home agent is allocated a globally unique IPv4 assume that the home agent is allocated a globally unique IPv4
address. The address might not be physically configured on the home address. The address might not be physically configured on the home
agent interface. Instead, it is associated with the home agent on agent interface. Instead, it is associated with the home agent on
the NAPT device, which allows the home agent to be reachable through the NAPT device, which allows the home agent to be reachable through
address or port mapping. address or port mapping.
skipping to change at page 44, line 15 skipping to change at page 45, line 15
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in
IPv6 Specification", RFC 2473, December 1998. IPv6 Specification", RFC 2473, December 1998.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
of Explicit Congestion Notification (ECN) to IP",
RFC 3168, September 2001.
[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004. in IPv6", RFC 3775, June 2004.
[RFC3948] Huttunen, A., Swander, B., Volpe, V., DiBurro, L., and M. [RFC3948] Huttunen, A., Swander, B., Volpe, V., DiBurro, L., and M.
Stenberg, "UDP Encapsulation of IPsec ESP Packets", Stenberg, "UDP Encapsulation of IPsec ESP Packets",
RFC 3948, January 2005. RFC 3948, January 2005.
[RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P. [RFC3963] Devarapalli, V., Wakikawa, R., Petrescu, A., and P.
Thubert, "Network Mobility (NEMO) Basic Support Protocol", Thubert, "Network Mobility (NEMO) Basic Support Protocol",
RFC 3963, January 2005. RFC 3963, January 2005.
[RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol", [RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
RFC 4306, December 2005. RFC 4306, December 2005.
[RFC4436] Aboba, B., Carlson, J., and S. Cheshire, "Detecting [RFC4436] Aboba, B., Carlson, J., and S. Cheshire, "Detecting
Network Attachment in IPv4 (DNAv4)", RFC 4436, March 2006. Network Attachment in IPv4 (DNAv4)", RFC 4436, March 2006.
[RFC4555] Eronen, P., "IKEv2 Mobility and Multihoming Protocol
(MOBIKE)", RFC 4555, June 2006.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
September 2007. September 2007.
[RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with [RFC4877] Devarapalli, V. and F. Dupont, "Mobile IPv6 Operation with
IKEv2 and the Revised IPsec Architecture", RFC 4877, IKEv2 and the Revised IPsec Architecture", RFC 4877,
April 2007. April 2007.
[RFC5026] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
Bootstrapping in Split Scenario", RFC 5026, October 2007.
10.2. Informative 10.2. Informative
[I-D.ietf-mip6-bootstrapping-integrated-dhc] [I-D.ietf-mip6-bootstrapping-integrated-dhc]
Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the Chowdhury, K. and A. Yegin, "MIP6-bootstrapping for the
Integrated Scenario", Integrated Scenario",
draft-ietf-mip6-bootstrapping-integrated-dhc-06 (work in draft-ietf-mip6-bootstrapping-integrated-dhc-06 (work in
progress), April 2008. progress), April 2008.
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
Traina, "Generic Routing Encapsulation (GRE)", RFC 2784,
March 2000.
[RFC2983] Black, D., "Differentiated Services and Tunnels", [RFC2983] Black, D., "Differentiated Services and Tunnels",
RFC 2983, October 2000. RFC 2983, October 2000.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
of Explicit Congestion Notification (ECN) to IP",
RFC 3168, September 2001.
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002. August 2002.
[RFC3519] Levkowetz, H. and S. Vaarala, "Mobile IP Traversal of [RFC3519] Levkowetz, H. and S. Vaarala, "Mobile IP Traversal of
Network Address Translation (NAT) Devices", RFC 3519, Network Address Translation (NAT) Devices", RFC 3519,
April 2003. April 2003.
[RFC3978] Bradner, S., "IETF Rights in Contributions", RFC 3978, [RFC3978] Bradner, S., "IETF Rights in Contributions", RFC 3978,
March 2005. March 2005.
[RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms [RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms
for IPv6 Hosts and Routers", RFC 4213, October 2005. for IPv6 Hosts and Routers", RFC 4213, October 2005.
[RFC4459] Savola, P., "MTU and Fragmentation Issues with In-the- [RFC4459] Savola, P., "MTU and Fragmentation Issues with In-the-
Network Tunneling", RFC 4459, April 2006. Network Tunneling", RFC 4459, April 2006.
[RFC4555] Eronen, P., "IKEv2 Mobility and Multihoming Protocol
(MOBIKE)", RFC 4555, June 2006.
[RFC4844] Daigle, L. and Internet Architecture Board, "The RFC [RFC4844] Daigle, L. and Internet Architecture Board, "The RFC
Series and RFC Editor", RFC 4844, July 2007. Series and RFC Editor", RFC 4844, July 2007.
[RFC4977] Tsirtsis, G. and H. Soliman, "Problem Statement: Dual [RFC4977] Tsirtsis, G. and H. Soliman, "Problem Statement: Dual
Stack Mobility", RFC 4977, August 2007. Stack Mobility", RFC 4977, August 2007.
[RFC5026] Giaretta, G., Kempf, J., and V. Devarapalli, "Mobile IPv6
Bootstrapping in Split Scenario", RFC 5026, October 2007.
[RFC5380] Soliman, H., Castelluccia, C., ElMalki, K., and L. [RFC5380] Soliman, H., Castelluccia, C., ElMalki, K., and L.
Bellier, "Hierarchical Mobile IPv6 (HMIPv6) Mobility Bellier, "Hierarchical Mobile IPv6 (HMIPv6) Mobility
Management", RFC 5380, October 2008. Management", RFC 5380, October 2008.
[RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
"Session Traversal Utilities for NAT (STUN)", RFC 5389,
October 2008.
[RFC5405] Eggert, L. and G. Fairhurst, "Unicast UDP Usage Guidelines [RFC5405] Eggert, L. and G. Fairhurst, "Unicast UDP Usage Guidelines
for Application Designers", BCP 145, RFC 5405, for Application Designers", BCP 145, RFC 5405,
November 2008. November 2008.
Appendix A. Contributors Appendix A. Contributors
This document reflects discussions and contributions from several This document reflects discussions and contributions from several
people including (in alphabetical order): people including (in alphabetical order):
Vijay Devarapalli: vijay.devarapalli@azairenet.com Vijay Devarapalli: vijay.devarapalli@azairenet.com
 End of changes. 14 change blocks. 
60 lines changed or deleted 65 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/