draft-ietf-mip4-nemo-v4-base-07.txt   draft-ietf-mip4-nemo-v4-base-08.txt 
MIP4 K. Leung MIP4 K. Leung
Internet-Draft G. Dommety Internet-Draft G. Dommety
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: July 7, 2008 V. Narayanan Expires: July 24, 2008 V. Narayanan
Qualcomm, Inc. Qualcomm, Inc.
A. Petrescu A. Petrescu
Motorola Motorola
January 4, 2008 January 21, 2008
Network Mobility (NEMO) Extensions for Mobile IPv4 Network Mobility (NEMO) Extensions for Mobile IPv4
draft-ietf-mip4-nemo-v4-base-07.txt draft-ietf-mip4-nemo-v4-base-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 July 7, 2008. This Internet-Draft will expire on July 24, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes a protocol for supporting Mobile Networks This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4 between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol. A Mobile Router is responsible for the mobility of one or protocol. A Mobile Router is responsible for the mobility of one or
skipping to change at page 2, line 41 skipping to change at page 2, line 41
8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . . 14 8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . . 14
9. Routing Protocol between Mobile Router and Home Agent . . . . 15 9. Routing Protocol between Mobile Router and Home Agent . . . . 15
10. Security Considerations . . . . . . . . . . . . . . . . . . . 16 10. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10.1. Security when Dynamic Routing Protocol is Used . . . . . . 17 10.1. Security when Dynamic Routing Protocol is Used . . . . . . 17
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
13.1. Normative References . . . . . . . . . . . . . . . . . . . 19 13.1. Normative References . . . . . . . . . . . . . . . . . . . 19
13.2. Informative References . . . . . . . . . . . . . . . . . . 19 13.2. Informative References . . . . . . . . . . . . . . . . . . 19
Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . . 20 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 24 Intellectual Property and Copyright Statements . . . . . . . . . . 25
1. Introduction 1. Introduction
This document describes protocol extensions to Mobile IPv4 as per This document describes protocol extensions to Mobile IPv4 as per
RFC 3344 [RFC3344] and its update [I-D.ietf-mip4-rfc3344bis], to RFC 3344 [RFC3344] and its update [I-D.ietf-mip4-rfc3344bis], to
enable support for Mobile Networks. This draft addresses mainly the enable support for Mobile Networks. This draft addresses mainly the
co-located Care-of Address mode. Foreign Agent Care-of Address mode co-located Care-of Address mode. Foreign Agent Care-of Address mode
(with 'legacy' Foreign Agents, RFC 3344 [RFC3344]) are supported but (with 'legacy' Foreign Agents, RFC 3344 [RFC3344]) are supported but
without optimization, double encapsulation being used. For an without optimization, double encapsulation being used. For an
optimization of this mode, the gentle reader is directed to an optimization of this mode, the gentle reader is directed to an
skipping to change at page 4, line 32 skipping to change at page 4, line 32
Prefix Table Prefix Table
A list of Mobile Network Prefixes indexed by the Home Address A list of Mobile Network Prefixes indexed by the Home Address
of a Mobile Router. The Home Agent manages and uses Prefix of a Mobile Router. The Home Agent manages and uses Prefix
Table to determine which Mobile Network Prefixes belong to a Table to determine which Mobile Network Prefixes belong to a
particular Mobile Router. particular Mobile Router.
3. Requirements 3. Requirements
Although Mobile IPv4 stated that Mobile Network can be supported by Although the original Mobile IPv4 specifications stated that Mobile
the Mobile Router and Home Agent using static configuration or Networks can be supported by the Mobile Router and Home Agent using
running a routing protocol, there is no solution for explicit static configuration or running a routing protocol (see Section 4.5
of RFC 3344 [RFC3344]), there is no solution for explicit
registration of the Mobile Networks served by the Mobile Router. A registration of the Mobile Networks served by the Mobile Router. A
solution needs to provide the Home Agent a means to ensure that a solution needs to provide the Home Agent a means to ensure that a
Mobile Router claiming a certain Mobile Network Prefix is authorized Mobile Router claiming a certain Mobile Network Prefix is authorized
to do so. A solution would also expose the Mobile Network Prefixes to do so. A solution would also expose the Mobile Network Prefixes
(and potentially other subnet-relevant information) in the exchanged (and potentially other subnet-relevant information) in the exchanged
messages, to aid in network debugging. messages, to aid in network debugging.
The following requirements for Mobile Network support are enumerated: The following requirements for Mobile Network support are enumerated:
o A Mobile Router should be able to operate in explicit or implicit o A Mobile Router should be able to operate in explicit or implicit
skipping to change at page 6, line 33 skipping to change at page 6, line 33
Acknowledgement extensions in addition to any other extensions Acknowledgement extensions in addition to any other extensions
defined by or in the context of RFC 3344 [RFC3344] and its update defined by or in the context of RFC 3344 [RFC3344] and its update
[I-D.ietf-mip4-rfc3344bis]. For Implicit Mode, the Mobile Network [I-D.ietf-mip4-rfc3344bis]. For Implicit Mode, the Mobile Network
Acknowledgement informs the Mobile Router the prefixes for which the Acknowledgement informs the Mobile Router the prefixes for which the
Home Agent sets up forwarding with respect to this Mobile Router. Home Agent sets up forwarding with respect to this Mobile Router.
Policies such as permitting only traffic from these Mobile Networks Policies such as permitting only traffic from these Mobile Networks
to be tunneled to the Home Agent may be applied by the Mobile Router. to be tunneled to the Home Agent may be applied by the Mobile Router.
For Explicit Mode, when several Mobile Networks are needed to be For Explicit Mode, when several Mobile Networks are needed to be
acknowledged explicitly, each is included in a separate Mobile acknowledged explicitly, each is included in a separate Mobile
Network Acknowledgement extension, with its own Type, Sub-Type, Network Acknowledgement extension, with its own Type, Sub-Type,
Length and Prefix Length fields. Optionally, all requested Mobile Length and Prefix Length fields. At least one Mobile Network
Networks could be acknowledged using only one Mobile Network Acknowledgement extension MUST be in a successful Registration Reply
Acknowledgement extension with "Prefix Length" and "Prefix" fields to indicate to the Mobile Router that the Mobile Network Request
set to zero. At least one Mobile Network Acknowledgement extension extension was processed, thereby not skipped by the Home Agent.
MUST be in a successful Registration Reply to indicate to the Mobile
Router that the Mobile Network Request extension was processed,
thereby not skipped by the Home Agent.
A Registration Reply may contain any non-zero number of Explicit Mode A Registration Reply may contain any non-zero number of Explicit Mode
and Implicit Mode Acknowledgements sub-types. Both sub-types can be and Implicit Mode Acknowledgements sub-types. Both sub-types can be
present in a single Registration Reply. A Mobile Network present in a single Registration Reply. A Mobile Network
Acknowledgement extension is encoded in Type-Length-Value (TLV) Acknowledgement extension is encoded in Type-Length-Value (TLV)
format. When the registration is denied with code HA_MOBNET_ERROR, format. When the registration is denied with code HA_MOBNET_ERROR,
the Code field in the extension provides the reason for the failure. the Code field in the extension provides the reason for the failure.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 10, line 18 skipping to change at page 10, line 18
1. Check that the Mobile Network Prefix information is valid 1. Check that the Mobile Network Prefix information is valid
2. Ensure the Mobile Network Prefix(es) is or are authorized to be 2. Ensure the Mobile Network Prefix(es) is or are authorized to be
on the Mobile Router on the Mobile Router
3. Create tunnel to the Mobile Router if it does not already exist 3. Create tunnel to the Mobile Router if it does not already exist
4. Set up route for the Mobile Network Prefix via this tunnel 4. Set up route for the Mobile Network Prefix via this tunnel
5. Propagate Mobile Network Prefix routes via routing protocol 5. Propagate Mobile Network Prefix routes via routing protocol if
necessary
6. Send the Registration Reply with the Mobile Network 6. Send the Registration Reply with the Mobile Network
Acknowledgement extension(s) Acknowledgement extension(s)
If there are any subnet routes via the tunnel to the Mobile Router If there are any subnet routes via the tunnel to the Mobile Router
that are not specified in the Mobile Network extensions, these routes that are not specified in the Mobile Network extensions, these routes
are removed. are removed.
In the case where the Mobile Node is not permitted to act as a Mobile In the case where the Mobile Node is not permitted to act as a Mobile
Router, the Home Agent sends a registration denied message with error Router, the Home Agent sends a registration denied message with error
skipping to change at page 14, line 46 skipping to change at page 14, line 47
destination IP address set to Home Agent). destination IP address set to Home Agent).
8. Nested Mobile Networks 8. Nested Mobile Networks
Nested Network Mobility is a scenario where a Mobile Router allows Nested Network Mobility is a scenario where a Mobile Router allows
another Mobile Router to attach to its Mobile Network. There could another Mobile Router to attach to its Mobile Network. There could
be arbitrary levels of nested mobility. The operation of each Mobile be arbitrary levels of nested mobility. The operation of each Mobile
Router remains the same whether the Mobile Router attaches to another Router remains the same whether the Mobile Router attaches to another
Mobile Router or to a fixed Access Router on the Internet. The Mobile Router or to a fixed Access Router on the Internet. The
solution described here does not place any restriction on the number solution described here does not place any restriction on the number
of levels for nested mobility. But note that this might introduce of levels for nested mobility. Two issues should be noted though.
significant overhead on the data packets as each level of nesting First, whenever physical loops occur in a nested aggregation of
introduces another tunnel header encapsulation. mobile networks this protocol does neither detect nor solve them -
datagram forwarding may be blocked. Second, Mobile Routers in a deep
nested aggregation of mobile networks might introduce significant
overhead on the data packets as each level of nesting introduces
another tunnel header encapsulation.
9. Routing Protocol between Mobile Router and Home Agent 9. Routing Protocol between Mobile Router and Home Agent
There are several benefits of running a dynamic routing protocol There are several benefits of running a dynamic routing protocol
between the Mobile Router and the Home Agent. If the mobile network between the Mobile Router and the Home Agent. If the mobile network
is relatively large, including several wireless subnets, then the is relatively large, including several wireless subnets, then the
topology changes within the moving network can be exposed from the topology changes within the moving network can be exposed from the
Mobile Router to the Home Agent by using a dynamic routing protocol. Mobile Router to the Home Agent by using a dynamic routing protocol.
The purpose of the NEMOv4 protocol extensions to Mobile IPv4, as The purpose of the NEMOv4 protocol extensions to Mobile IPv4, as
defined in previous sections, is not to inform the Home Agent about defined in previous sections, is not to inform the Home Agent about
skipping to change at page 17, line 14 skipping to change at page 17, line 17
10.1. Security when Dynamic Routing Protocol is Used 10.1. Security when Dynamic Routing Protocol is Used
If a dynamic routing protocol is used between the Mobile Router and If a dynamic routing protocol is used between the Mobile Router and
the Home Agent to propagate the mobile network information into the the Home Agent to propagate the mobile network information into the
home network, the routing updates SHOULD be protected with IPsec ESP home network, the routing updates SHOULD be protected with IPsec ESP
confidentiality between the Mobile Router and Home Agent, to prevent confidentiality between the Mobile Router and Home Agent, to prevent
information about home network topology from being visible to information about home network topology from being visible to
eavesdroppers. eavesdroppers.
A routing protocol message protected with ESP, and sent through the
Mobile Router - Home Agent bidirectional tunnel, SHOULD NOT contain
the Mobile IPv4 Mobile-Home Authentication Extension, since ESP
provides enough security.
11. IANA Considerations 11. IANA Considerations
IANA to modify rules for the existing registry "Mobile IPv4 numbers - IANA to modify rules for the existing registry "Mobile IPv4 numbers -
per RFC 3344". The numbering space for Extensions that may appear in per RFC 3344". The numbering space for Extensions that may appear in
Mobile IP control messages (those sent to and from UDP port number Mobile IP control messages (those sent to and from UDP port number
434) should be modified. 434) should be modified.
The new Values and Names for the Type for Extensions appearing in The new Values and Names for the Type for Extensions appearing in
Mobile IP control messages are the following: Mobile IP control messages are the following:
skipping to change at page 18, line 17 skipping to change at page 18, line 17
+-------+-----------------------------------------+ +-------+-----------------------------------------+
| TBA | Mobile Network Request Extension | | TBA | Mobile Network Request Extension |
| TBA | Explicit Mode Acknowledgement Extension | | TBA | Explicit Mode Acknowledgement Extension |
| TBA | Implicit Mode Acknowledgement Extension | | TBA | Implicit Mode Acknowledgement Extension |
+-------+-----------------------------------------+ +-------+-----------------------------------------+
Table 2: New Values and Names for the Sub-Type for Mobile Network Table 2: New Values and Names for the Sub-Type for Mobile Network
Extensions Extensions
The policy of future assignments to this number space should be The policy of future assignments to this number space should be
following Expert Review. following Standards Action or IESG Approval (see
[I-D.narten-iana-considerations-rfc2434bis]).
The new Code Values for Mobile IP Registration Reply messages are the The new Code Values for Mobile IP Registration Reply messages are the
following (for a registration denied by the Home Agent): following (for a registration denied by the Home Agent):
+-------+-----------------------------------------------------------+ +-------+-----------------------------------------------------------+
| Value | Name | | Value | Name |
+-------+-----------------------------------------------------------+ +-------+-----------------------------------------------------------+
| TBA | Mobile Network Prefix operation error (HA_MOBNET_ERROR) | | TBA | Mobile Network Prefix operation error (HA_MOBNET_ERROR) |
| TBA | Mobile Router operation is not permitted | | TBA | Mobile Router operation is not permitted |
| | (HA_MOBNET_DISALLOWED) | | | (HA_MOBNET_DISALLOWED) |
skipping to change at page 18, line 48 skipping to change at page 18, line 49
| TBA | Success | | TBA | Success |
| TBA | Invalid prefix length (MOBNET_INVALID_PREFIX_LEN) | | TBA | Invalid prefix length (MOBNET_INVALID_PREFIX_LEN) |
| TBA | Mobile Router is not authorized for prefix | | TBA | Mobile Router is not authorized for prefix |
| | (MOBNET_UNAUTHORIZED) | | | (MOBNET_UNAUTHORIZED) |
| TBA | Forwarding setup failed (MOBNET_FWDING_SETUP_FAILED) | | TBA | Forwarding setup failed (MOBNET_FWDING_SETUP_FAILED) |
+-----+-------------------------------------------------------------+ +-----+-------------------------------------------------------------+
Table 4: New Code Values for Mobile Network Acknowledgement Extension Table 4: New Code Values for Mobile Network Acknowledgement Extension
The policy of future assignments to this number space should be The policy of future assignments to this number space should be
following Expert Review. following Standards Action or IESG Approval (see
[I-D.narten-iana-considerations-rfc2434bis]).
The current non-modified numbering spaces could be consulted at the The current non-modified numbering spaces could be consulted at the
URL http://www.iana.org/assignments/mobileip-numbers (contents last URL http://www.iana.org/assignments/mobileip-numbers (contents last
updated 2007-12-20 and last browsed 2008-01-04). updated 2007-12-20 and last browsed 2008-01-04).
12. Acknowledgements 12. Acknowledgements
The authors would like to thank Christophe Janneteau, George The authors would like to thank Christophe Janneteau, George
Popovich, Ty Bekiares, Ganesh Srinivasan, Alpesh Patel, Ryuji Popovich, Ty Bekiares, Ganesh Srinivasan, Alpesh Patel, Ryuji
Wakikawa, George Tsirtsis, and Henrik Levkowetz for their helpful Wakikawa, George Tsirtsis, and Henrik Levkowetz for their helpful
discussions, reviews and comments. Vijay Devarapalli extensively discussions, reviews and comments. Vijay Devarapalli extensively
reviewed one of the later versions of the draft. Hans Sjostrand reviewed one of the later versions of the draft. Hans Sjostrand
(Hans Sj\"ostrand) identified the last clarifications with respect to (Hans Sj\"ostrand) identified the last clarifications with respect to
Foreign Agent mode treatment. Pete McCann contributed necessary Foreign Agent mode treatment. Pete McCann contributed necessary
refinements of many statements. refinements of many statements.
Mobile IPv4 versions as early as 1996 (RFC 2002) described Mobile
Networks and Mobile Routers support. Charles Perkins.
13. References 13. References
13.1. Normative References 13.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.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453, [RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453,
skipping to change at page 19, line 49 skipping to change at page 20, line 8
[I-D.ietf-mip4-nemov4-fa] [I-D.ietf-mip4-nemov4-fa]
Tsirtsis, G., Park, V., Narayanan, V., and K. Leung, "FA Tsirtsis, G., Park, V., Narayanan, V., and K. Leung, "FA
extensions to NEMOv4 Base", draft-ietf-mip4-nemov4-fa-01 extensions to NEMOv4 Base", draft-ietf-mip4-nemov4-fa-01
(work in progress), November 2007. (work in progress), November 2007.
[I-D.ietf-mip4-rfc3344bis] [I-D.ietf-mip4-rfc3344bis]
Perkins, C., "IP Mobility Support for IPv4, revised", Perkins, C., "IP Mobility Support for IPv4, revised",
draft-ietf-mip4-rfc3344bis-05 (work in progress), draft-ietf-mip4-rfc3344bis-05 (work in progress),
July 2007. July 2007.
[I-D.narten-iana-considerations-rfc2434bis]
Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs",
draft-narten-iana-considerations-rfc2434bis-08 (work in
progress), October 2007.
[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.
Appendix A. ChangeLog Appendix A. ChangeLog
The changes are listed in reverse chronological order, most recent The changes are listed in reverse chronological order, most recent
changes appearing at the top of the list. changes appearing at the top of the list.
From draft-ietf-mip4-nemo-v4-base-07.txt to
draft-ietf-mip4-nemo-v4-base-08.txt, following AD Review (Jari
Arkko):
o HA propagates Mobile Network Prefix only if necessary (previously
it was always doing it).
o emphasized that within nested mobile networks looping may occur
and this document doesn't do anything to address this.
o dropped a phrase which said that Mobile-Home auth extension
shouldn't be used when ESP protects the routing protocol message,
because that extension is only applied to Registration messages
(not tunneled data, which usually contains routing protocol
exchange).
o recommending "Standards Action or IESG Review" instead of "Expert
Review" for this numbering space, and added reference to a draft
for 2434bis.
o editorial: re-phrased about how Mobile IPv4 claimed mobile
networks support.
o editorial: added a necessary paragraph in the Acknowledgements
section.
From draft-ietf-mip4-nemo-v4-base-06.txt to From draft-ietf-mip4-nemo-v4-base-06.txt to
draft-ietf-mip4-nemo-v4-base-07.txt draft-ietf-mip4-nemo-v4-base-07.txt
o encoded the draft into xml. Compiled with xml2rfc version o encoded the draft into xml. Compiled with xml2rfc version
1.33pre4. 1.33pre4.
o checked against 'idnits' script version 2.05.03. o checked against 'idnits' script version 2.05.03.
o substituted 'Care-of Address' for 'CoA'. o substituted 'Care-of Address' for 'CoA'.
From draft-ietf-mip4-nemo-v4-base-05.txt to From draft-ietf-mip4-nemo-v4-base-05.txt to
draft-ietf-mip4-nemo-v4-base-06.txt draft-ietf-mip4-nemo-v4-base-06.txt
 End of changes. 16 change blocks. 
28 lines changed or deleted 62 lines changed or added

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