draft-ietf-mip4-nemo-v4-base-00.txt   draft-ietf-mip4-nemo-v4-base-01.txt 
Network Working Group K. Leung Network Working Group K. Leung
Internet-Draft G. Dommety Internet-Draft G. Dommety
Expires: August 26, 2007 Cisco Systems Expires: March 10, 2008 Cisco Systems
V. Narayanan V. Narayanan
QUALCOMM, Inc. QUALCOMM, Inc.
A. Petrescu A. Petrescu
Motorola Motorola
February 26, 2007 September 10, 2007
IPv4 Network Mobility (NEMO) Protocol IPv4 Network Mobility (NEMO) Protocol
draft-ietf-mip4-nemo-v4-base-00.txt draft-ietf-mip4-nemo-v4-base-01.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 37 skipping to change at page 1, line 37
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 26, 2007. This Internet-Draft will expire on March 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2007). Copyright (C) The Internet Society (2007).
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 1, line 60 skipping to change at page 1, line 60
on the Mobile Network may be fixed in relationship to the Mobile on the Mobile Network may be fixed in relationship to the Mobile
Router and may not have any mobility function. Router and may not have any mobility function.
Extensions to Mobile IPv4 are introduced to support Mobile Networks. Extensions to Mobile IPv4 are introduced to support Mobile Networks.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 1 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 1
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 3 4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 4
4.1. Mobile Network Request Extension . . . . . . . . . . . . . 3 4.1. Mobile Network Request Extension . . . . . . . . . . . . . 4
4.2. Mobile Network Acknowledgement Extension . . . . . . . . . 4 4.2. Mobile Network Acknowledgement Extension . . . . . . . . . 5
5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 5 5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 6
5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 5 5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 7
6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 6 6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 8
6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 7 6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 9
6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 7 6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 9
6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 7 6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 9
6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 7 6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 9
6.4. Advertising Mobile Network Reachability . . . . . . . . . 9 6.4. Advertising Mobile Network Reachability . . . . . . . . .10
6.5. Establishment of Bi-directional Tunnel . . . . . . . . . . 9 6.5. Establishment of Bi-directional Tunnel . . . . . . . . . .11
6.6. Sending Registration Replies . . . . . . . . . . . . . . . 9 6.6. Sending Registration Replies . . . . . . . . . . . . . . .11
6.7. Mobile Network Prefix De-registration . . . . . . . . . . 9 6.7. Mobile Network Prefix De-registration . . . . . . . . . .11
7. Data Forwarding Operation . . . . . . . . . . . . . . . . . .10 7. Data Forwarding Operation . . . . . . . . . . . . . . . . . .11
8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . .10 8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . .12
9. Security Considerations . . . . . . . . . . . . . . . . . . .10 9. Routing Protocol between Mobile Router and Home Agent. . . . .12
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .12 10. Security Considerations . . . . . . . . . . . . . . . . . . .13
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .13 10.1 Security when Dynamic Routing Protocol is Used. . . . . . .14
12. References . . . . . . . . . . . . . . . . . . . . . . . . . .13 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .14
12.1. Normative References . . . . . . . . . . . . . . . . . . .13 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .15
12.2. Informative References . . . . . . . . . . . . . . . . . .13 13. References . . . . . . . . . . . . . . . . . . . . . . . . . .16
13. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .13 13.1. Normative References . . . . . . . . . . . . . . . . . . .16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .14 13.2. Informative References . . . . . . . . . . . . . . . . . .16
Intellectual Property and Copyright Statements . . . . . . . . . .15 13. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .17
Intellectual Property and Copyright Statements . . . . . . . . . .19
1. Introduction 1. Introduction
This document describes protocol extensions to Mobile IPv4 This document describes protocol extensions to Mobile IPv4
([RFC3344]) to enable support for Mobile Networks. This draft ([RFC3344]) to enable support for Mobile Networks. This draft
addresses only co-located Care-of Address mode (not Foreign Agent addresses only co-located Care-of Address mode (not Foreign Agent
Care-of Address mode, for which the gentle reader is directed to Care-of Address mode, for which the gentle reader is directed to
[1]). [1]).
A Mobile Network is defined as a network segment or subnet that can A Mobile Network is defined as a network segment or subnet that can
change its point of attachment to the routing infrastructure. Such change its point of attachment to the routing infrastructure. Such
movement is performed by a Mobile Router, which is the mobility movement is performed by a Mobile Router, which is the mobility
entity that provides connectivity and reachability as well as entity that provides connectivity and reachability as well as
session continuity for all the nodes in the Mobile Network. The session continuity for all the nodes in the Mobile Network. The
Mobile Router typically serves as the default gateway for the hosts Mobile Router typically serves as the default gateway for the hosts
on the Mobile Network. on the Mobile Network.
Mobility for the Mobile Network is supported by the Mobile Router Mobility for the Mobile Network is supported by the Mobile Router
registering the point of attachment to its Home Agent. This registering the point of attachment to its Home Agent. This
signaling sets up the tunnel between the two entities. The Mobile signaling sets up the tunnel between the two entities.
Networks (either implicitly configured on the Home Agent or
explicitly identified by the Mobile Router) are advertised by the The Mobile Networks (either implicitly configured on the Home Agent
Home Agent for route propagation. Traffic to and from nodes in the or explicitly identified by the Mobile Router) are advertised by
Mobile Network are tunneled by the Home Agent to the Mobile Router, the Home Agent for route propagation. Traffic to and from nodes in
and vice versa. Though packets from the Mobile Network can be the Mobile Network are tunneled by the Home Agent to the Mobile
forwarded directly without tunneling (if reverse tunneling is not Router, and vice versa. Though packets from the Mobile Network can
used) packets will be dropped if ingress filtering is turned on. be forwarded directly without tunneling (if reverse tunneling is
not used) packets will be dropped if ingress filtering is turned
on.
This document specifies an additional tunnel between Mobile Router's This document specifies an additional tunnel between Mobile Router's
Home Address and the Home Agent. This tunnel is encapsulated within Home Address and the Home Agent. This tunnel is encapsulated within
the normal tunnel between the Care-of Address (CoA) and Home Agent. the normal tunnel between the Care-of Address (CoA) and Home Agent.
In Foreign Agent CoA mode, the tunnel between the Mobile Router and In Foreign Agent CoA mode, the tunnel between the Mobile Router and
Home Agent is needed to allow the Foreign Agent to direct the Home Agent is needed to allow the Foreign Agent to direct the
decapsulated packet to the proper visiting Mobile Router. However, decapsulated packet to the proper visiting Mobile Router. However,
in Collocated CoA mode, the additional tunnel is not essential and in Collocated CoA mode, the additional tunnel is not essential and
can be eliminated because the Mobile Router is the recipient of the can be eliminated because the Mobile Router is the recipient of the
encapsulated packets for the Mobile Network. encapsulated packets for the Mobile Network.
skipping to change at page 1, line 176 skipping to change at page 3, line 20
debugging. debugging.
The following requirements for Mobile Network support are The following requirements for Mobile Network support are
enumerated: 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
mode. A Mobile Router may explicitly inform the Home Agent which mode. A Mobile Router may explicitly inform the Home Agent which
Mobile Network(s) need to be propagated via routing protocol. A Mobile Network(s) need to be propagated via routing protocol. A
Mobile Router may also function in implicit mode, where the Home Mobile Router may also function in implicit mode, where the Home
Agent may learn the mobile networks through other means, such as Agent may learn the mobile networks through other means, such as
from the AAA server or via pre-configuration. from the AAA server, via pre-configuration or via a dynamic
routing protocol.
o The Mobile Network should be supported using Foreign Agents that o The Mobile Network should be supported using Foreign Agents that
are compliant to RFC 3344 without any changes ('legacy' Foreign are compliant to RFC 3344 without any changes ('legacy' Foreign
Agents). Agents).
o The mobile network should allow Fixed nodes, Mobile Nodes, or o The mobile network should allow Fixed nodes, Mobile Nodes, or
Mobile Routers to be on it. Mobile Routers to be on it.
4. Mobile Network Extensions 4. Mobile Network Extensions
skipping to change at page 1, line 282 skipping to change at page 6, line 4
Length: Length:
8 8
Sub-Type: Sub-Type:
TBA (Explicit Mode Acknowledgement) TBA (Explicit Mode Acknowledgement)
TBA (Implicit Mode Acknowledgement) TBA (Implicit Mode Acknowledgement)
Code: Code:
Value indicating success or failure. Value indicating success or failure.
0 Success 0 Success
TBA Invalid prefix (MOBNET_INVALID_PREFIX_LEN) TBA Invalid prefix (MOBNET_INVALID_PREFIX_LEN)
TBA MR is not authorized for prefix (MOBNET_UNAUTHORIZED) TBA Mobile Router is not authorized for prefix
(MOBNET_UNAUTHORIZED)
TBA Forwarding setup failed (MOBNET_FWDING_SETUP_FAILED) TBA Forwarding setup failed (MOBNET_FWDING_SETUP_FAILED)
Prefix Length: Prefix Length:
8-bit unsigned integer indicating the number of bits covering 8-bit unsigned integer indicating the number of bits covering
the network part of the address contained in the Prefix field. the network part of the address contained in the Prefix field.
Reserved: Reserved:
skipping to change at page 1, line 479 skipping to change at page 9, line 59
request, the Home Agent MUST perform a check against the Prefix request, the Home Agent MUST perform a check against the Prefix
Table. If the Prefix Table does not contain at least one entry Table. If the Prefix Table does not contain at least one entry
pairing that Home Address to that Mobile Network Prefix then the pairing that Home Address to that Mobile Network Prefix then the
check fails, otherwise it succeeds. check fails, otherwise it succeeds.
Following this check against the Prefix Table, the Home Agent MUST Following this check against the Prefix Table, the Home Agent MUST
construct a Registration Reply containing Mobile Network construct a Registration Reply containing Mobile Network
Acknowledgement extensions. For a Mobile Network Prefix for which Acknowledgement extensions. For a Mobile Network Prefix for which
the check was unsuccessfull the Code field in the corresponding the check was unsuccessfull the Code field in the corresponding
Mobile Network Acknowledgement extension should be set to Mobile Network Acknowledgement extension should be set to
MOBNET_UNAUTHORIZED. For a Mobile Network Prefix for which the MOBNET_UNAUTHORIZED.
check was successfull the Code field in the respective Mobile
Network Acknowledgement extensions should be set to 0. For a Mobile Network Prefix for which the check was successfull the
Code field in the respective Mobile Network Acknowledgement
extensions should be set to 0.
The Home Agent MUST attempt to set up forwarding for each Mobile The Home Agent MUST attempt to set up forwarding for each Mobile
Network Prefix extension for which the Prefix Table check was Network Prefix extension for which the Prefix Table check was
successfull. If the forwarding setup fails for a particular Mobile successfull. If the forwarding setup fails for a particular Mobile
Network Prefix (for reasons like not enough memory available, or Network Prefix (for reasons like not enough memory available, or
not enough devices available, or other similar) the Code field in not enough devices available, or other similar) the Code field in
the respective Mobile Network Acknowledgement extension should be the respective Mobile Network Acknowledgement extension should be
set to MOBNET_FWDING_SETUP_FAILED. set to MOBNET_FWDING_SETUP_FAILED.
If forwarding and setup was successful for at least one Mobile If forwarding and setup was successful for at least one Mobile
skipping to change at page 1, line 622 skipping to change at page 12, line 34
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. But note that this might introduce
significant overhead on the data packets as each level of nesting significant overhead on the data packets as each level of nesting
introduces another tunnel header encapsulation. introduces another tunnel header encapsulation.
9. Security Considerations 9. Routing Protocol between Mobile Router and Home Agent
There are several benefits of running a dynamic routing protocol
between the Mobile Router and the Home Agent. If the mobile
network is relatively large, including several wireless subnets,
then the topology changes within the moving network can be exposed
from the Mobile Router to the Home Agent by using a dynamic routing
protocol. The purpose of the NEMOv4 protocol extensions to Mobile
IPv4, as defined in previous sections, is not to inform the Home
Agent about these topology changes, but to manage the mobility of
the Mobile Router.
Similarly, topology changes in the home network can be exposed to
the Mobile Router by using a dynamic routing protocol. This may be
necessary when new fixed networks are added in the home network.
Here too, the purpose of NEMOv4 extensions is not to inform the
Mobile Router about topology changes at home.
Examples of dynamic routing protocol include but are not limited to
OSPF Version 2 [RFC2328], BGP [RFC4271] and RIP [RFC2453].
The recommendations are related to how the routing protocol and the
Mobile IPv4 implementation work in tandem on the Mobile Router and
on the Home Agent (1) without creating incoherent states in the
forwarding bases at home and on the Mobile Router (2) without
introducing topologically incorrect addressing information in the
visited domain and (3) efficiently avoid duplication of sent data
or over-provisioning of security.
The information exchanged between the Mobile Router and the Home
Agent is sent over the bi-directional tunnel established by the
Mobile IPv4 exchange Registration Request - Registration Reply (see
section 6.5). If a network address and prefix about a subnet in
the moving network is sent by the Mobile Router within a routing
protocol message then they SHOULD NOT be sent in the Mobile IPv4
Registration Request too, in order to avoid incoherencies in the
forwarding information bases. The Mobile Router SHOULD use NEMOv4
implicit mode in this case (see section 3).
The Mobile Router SHOULD NOT send routing protocol information
updates in the foreign network. The subnet addresses and prefixes
valid in the moving network are topologically incorrect in the
visited network.
If the Mobile Router and the Home Agent use a dynamic routing
protocol over the tunnel interface, and if that protocol offers
security mechanisms to protect that protocol's messages, then the
security recommendations in section 10.1 apply.
10. Security Considerations
The Mobile Network extension is protected by the same rules for The Mobile Network extension is protected by the same rules for
Mobile IP extensions in registration messages. See the Security Mobile IP extensions in registration messages. See the Security
Considerations section in RFC 3344. Considerations section in RFC 3344.
The Home Agent MUST be able to verify that the Mobile Router is The Home Agent MUST be able to verify that the Mobile Router is
authorized to provide mobility service for the Mobile Networks in authorized to provide mobility service for the Mobile Networks in
the registration request, before anchoring these Mobile Network the registration request, before anchoring these Mobile Network
Prefixes on behalf of the Mobile Router. Forwarding for prefixes Prefixes on behalf of the Mobile Router. Forwarding for prefixes
MUST NOT be set up without successful authorization of the Mobile MUST NOT be set up without successful authorization of the Mobile
skipping to change at page 1, line 648 skipping to change at page 13, line 59
MN-HA Authentication Extension as specified in ([RFC3344]). When the MN-HA Authentication Extension as specified in ([RFC3344]). When the
registration request is sent in explicit mode, i.e., with one or more registration request is sent in explicit mode, i.e., with one or more
Mobile Network Prefix extensions, all the Mobile Network Prefix Mobile Network Prefix extensions, all the Mobile Network Prefix
extensions MUST be included before the MN-HA Authentication extensions MUST be included before the MN-HA Authentication
extension. Also, these extensions MUST be included in the extension. Also, these extensions MUST be included in the
calculation of the MN-HA authenticator value. calculation of the MN-HA authenticator value.
The Mobile Router should perform ingress filtering on all the packets The Mobile Router should perform ingress filtering on all the packets
received on the mobile network prior to reverse tunneling them to the received on the mobile network prior to reverse tunneling them to the
Home Agent. The Mobile Router MUST drop any packets that do not have Home Agent. The Mobile Router MUST drop any packets that do not have
a source address belonging to the mobile network. The Mobile Router a source address belonging to the mobile network.
MUST also ensure that the source address of packets arriving on the
mobile network is not the same as the Mobile Router's IP address on The Mobile Router MUST also ensure that the source address of
any interface. These checks will protect against nodes attempting to packets arriving on the mobile network is not the same as the
launch IP spoofing attacks through the bi-directional tunnel. Mobile Router's IP address on any interface. These checks will
protect against nodes attempting to launch IP spoofing attacks
through the bi-directional tunnel.
The Home Agent, upon receiving packets through the bi-directional The Home Agent, upon receiving packets through the bi-directional
tunnel, MUST verify that the source addresses of the outer IP header tunnel, MUST verify that the source addresses of the outer IP header
of the packets are set to the Mobile Router's care-of-address. Also, of the packets are set to the Mobile Router's care-of-address. Also,
it MUST ensure that the source address of the inner IP header is a it MUST ensure that the source address of the inner IP header is a
topologically correct address on the mobile network. This will topologically correct address on the mobile network. This will
prevent nodes from using the Home Agent to launch attacks inside the prevent nodes from using the Home Agent to launch attacks inside the
protected network. protected network.
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.
10. IANA Considerations 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
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:
Value Name Value Name
skipping to change at page 1, line 691 skipping to change at page 15, line 4
TBA Mobile Network Extension (To Be Assigned by IANA) TBA Mobile Network Extension (To Be Assigned by IANA)
The new Values and Names for the Sub-Type for Mobile Network The new Values and Names for the Sub-Type for Mobile Network
Extension are the following: Extension are the following:
Value Name Value Name
----- ------------------------------------------ ----- ------------------------------------------
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
The new Code values for Mobile IP Registration Reply messages are
The new Code values for Mobile IP Registration Reply messages are the the following:
following:
Code Values for Mobile IP Registration Reply messages Code Values for Mobile IP Registration Reply messages
----------------------------------------------------- -----------------------------------------------------
Registration denied by the Home Agent: (To Be Assigned by IANA) Registration denied by the Home Agent: (To Be Assigned by IANA)
TBA Mobile Network Prefix operation error (HA_MOBNET_ERROR) TBA Mobile Network Prefix operation error (HA_MOBNET_ERROR)
TBA MR operation is not permitted (HA_MOBNET_DISALLOWED) TBA Mobile Router operation is not permitted
(HA_MOBNET_DISALLOWED)
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: following:
Code Values for Mobile Network Acknowledgement Extension Code Values for Mobile Network Acknowledgement Extension
-------------------------------------------------------- --------------------------------------------------------
Registration denied by the Home Agent: Registration denied by the Home Agent:
TBA Invalid prefix length (MOBNET_INVALID_PREFIX_LEN) TBA Invalid prefix length (MOBNET_INVALID_PREFIX_LEN)
TBA MR is not authorized for prefix (MOBNET_UNAUTHORIZED) TBA Mobile Router is not authorized for prefix
(MOBNET_UNAUTHORIZED)
TBA Forwarding setup failed (MOBNET_FWDING_SETUP_FAILED) TBA Forwarding setup failed (MOBNET_FWDING_SETUP_FAILED)
The current (non-modified) numbering spaces could be consulted at the The current non-modified numbering spaces could be consulted at the
following URL: http://www.iana.org/assignments/mobileip-numbers following URL: http://www.iana.org/assignments/mobileip-numbers
(contents last updated 2007-07-02 and last browsed 10 September
2007).
11. 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. reviewed one of the later versions of the draft.
12. References 13. References
12.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.
[RFC2794] Calhoun, P. and C. Perkins, "Mobile IP Network Access [RFC2794] Calhoun, P. and C. Perkins, "Mobile IP Network Access
Identifier Extension for IPv4", RFC 2794, March 2000. Identifier Extension for IPv4", RFC 2794, March 2000.
[RFC2453] Malkin, G., "RIP Version 2", RFC 2453, STD 56, November
1998.
[RFC2328] Moy, J., "OSPF Version 2", RFC 2328, STD 54, April
1998.
[RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344,
August 2002. August 2002.
12.2. Informative References [RFC4271] Rekhter, Y, Ed., Li, T. and S. Hares, "A Border Gateway
Protocol (BGP-4)", RFC 4271, January 2006.
13.2. Informative References
[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.
[1] Tsirtsis, G., Park, V., Narayanan, V., and K. Leung, "FA [1] Tsirtsis, G., Park, V., Narayanan, V., and K. Leung, "FA
extensions to NEMOv4 Base", extensions to NEMOv4 Base",
draft-tsirtsis-nemov4-fa-01.txt, IETF Internet-Draft, draft-ietf-mip4-nemov4-fa-01.txt, IETF Internet-Draft,
Work in Progress, January 31, 2007. Work in Progress, March 19, 2007.
13. Changelog 14. Changelog
From version 00 to 01: The changes are listed in reverse chronological order, most recent
-removed error code HA_MOBNET_UNSUPPORTED. changes appearing at the top of the list:
-changed all values to be assigned by IANA, from specific
numbers to "TBA" (To Be Assigned). From draft-ietf-mip4-nemo-v4-base-00.txt to
-substituted "egress interface" for "roaming interface". draft-ietf-mip4-nemo-v4-base-01.txt
-changed HA behaviour upon reception of MNPs. In 00 the HA -added a section on Routing Protocol between Mobile Router and
replied positively only if all MNPs in RegReq were valid, in 01 Home Agent.
a reply is constructed specifying which MNP was valid and which -added a security subsection about running simultaneously a
not. secure routing protocol with secure Mobile IPv4.
-clarified a 3-line paragraph saying that RegRep may contain -added a date tag on the IANA URL for Mobile IP numbering
both implicit and explicit acknowledgements. spaces.
-substituted 'Mobile Router' for 'MR' everywhere.
-updated reference to NEMOv4 FA draft.
From draft-ietf-nemo-v4-base-01.txt to From draft-ietf-nemo-v4-base-01.txt to
draft-ietf-mip4-nemo-v4-base-00.txt: draft-ietf-mip4-nemo-v4-base-00.txt:
-changed draft name, headers and footers. -changed draft name, headers and footers.
-changed title. -changed title.
-a more coherent use of terms 'subnet', 'prefix' and 'mobile -a more coherent use of terms 'subnet', 'prefix' and 'mobile
network'. network'.
-clarified only co-located CoA mode is supported (not FA CoA) -clarified only co-located CoA mode is supported (not FA CoA).
for Mobile Routers in this specification. And added reference for Mobile Routers in this specification. And added reference
to the FA NEMO optimizations draft. to the FA NEMO optimizations draft.
-changed 'devices' to 'hosts'. -changed 'devices' to 'hosts'.
-changed 'moving networks' to 'mobile networks'. -changed 'moving networks' to 'mobile networks'.
-clarified what 'reachability' in a certain context is: packets -clarified what 'reachability' in a certain context is: packets
may be dropped if ingress filtering is turned on. may be dropped if ingress filtering is turned on.
-removed the MR-FA-CoA tunnel overhead optimization. There is -removed the MR-FA-CoA tunnel overhead optimization. There is
still an issue with text at HA doing optimization. still an issue with text at HA doing optimization.
This document was first presented as an individual contribution to
the NEMO Working Group, then adopted as a WG item to that group.
The 01 version in the NEMO WG has been Last Called on the
INFORMATIONAL track. The evolution was:
From version draft-ietf-nemo-v4-base-00 to
draft-ietf-nemo-v4-base-01:
-removed error code HA_MOBNET_UNSUPPORTED.
-changed all values to be assigned by IANA, from specific
numbers to "TBA" (To Be Assigned).
-substituted "egress interface" for "roaming interface".
-changed HA behaviour upon reception of MNPs. In 00 the HA
replied positively only if all MNPs in RegReq were valid, in 01
a reply is constructed specifying which MNP was valid and which
not.
-clarified a 3-line paragraph saying that RegRep may contain
both implicit and explicit acknowledgements.
Authors' Addresses Authors' Addresses
Kent Leung Kent Leung
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
US US
Phone: +1 408-526-5030 Phone: +1 408-526-5030
Email: kleung@cisco.com Email: kleung@cisco.com
 End of changes. 29 change blocks. 
76 lines changed or deleted 173 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/