draft-ietf-mip4-nemo-v4-base-04.txt   draft-ietf-mip4-nemo-v4-base-05.txt 
Network Working Group K. Leung Network Working Group K. Leung
Internet-Draft G. Dommety Internet-Draft G. Dommety
Expires: April 10, 2008 Cisco Systems Intended Status: Proposed Standard Cisco Systems
V. Narayanan Expires: May 4, 2008 V. Narayanan
Qualcomm, Inc. Qualcomm, Inc.
A. Petrescu A. Petrescu
Motorola Motorola
October 5, 2007 October 29, 2007
Network Mobility (NEMO) Extensions for Mobile IPv4 Network Mobility (NEMO) Extensions for Mobile IPv4
draft-ietf-mip4-nemo-v4-base-04.txt draft-ietf-mip4-nemo-v4-base-05.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 April 10, 2008. This Internet-Draft will expire on May 4, 2008.
Copyright Notice
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
more network segments or subnets moving together. The Mobile Router more network segments or subnets moving together. The Mobile Router
hides its mobility from the nodes on the mobile network. The nodes hides its mobility from the nodes on the mobile network. The nodes
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.
skipping to change at page 1, line 85 skipping to change at page 1, line 81
7. Data Forwarding Operation . . . . . . . . . . . . . . . . . .11 7. Data Forwarding Operation . . . . . . . . . . . . . . . . . .11
8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . .11 8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . .11
9. Routing Protocol between Mobile Router and Home Agent. . . . .12 9. Routing Protocol between Mobile Router and Home Agent. . . . .12
10. Security Considerations . . . . . . . . . . . . . . . . . . .13 10. Security Considerations . . . . . . . . . . . . . . . . . . .13
10.1 Security when Dynamic Routing Protocol is Used. . . . . . .13 10.1 Security when Dynamic Routing Protocol is Used. . . . . . .13
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .14 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .14
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .15 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .15
13. References . . . . . . . . . . . . . . . . . . . . . . . . . .15 13. References . . . . . . . . . . . . . . . . . . . . . . . . . .15
13.1. Normative References . . . . . . . . . . . . . . . . . . .15 13.1. Normative References . . . . . . . . . . . . . . . . . . .15
13.2. Informative References . . . . . . . . . . . . . . . . . .15 13.2. Informative References . . . . . . . . . . . . . . . . . .15
13. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .16 14. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .17
Intellectual Property and Copyright Statements . . . . . . . . . .18 Intellectual Property and Copyright Statements . . . . . . . . . .18
1. Introduction 1. Introduction
This document describes protocol extensions to Mobile IPv4 as per This document describes protocol extensions to Mobile IPv4 as per
[RFC3344] and its update [2], to enable support for Mobile [RFC3344] and its update [2], to enable support for Mobile
Networks. This draft addresses mainly the co-located Care-of Networks. This draft addresses mainly the co-located Care-of
Address mode. Foreign Agent Care-of Address mode (with 'legacy' Address mode. Foreign Agent Care-of Address mode (with 'legacy'
Foreign Agents, RFC 3344) are supported but without optimization, Foreign Agents, [RFC3344]) are supported but without optimization,
double encapsulation being used. For an optimization of this mode, double encapsulation being used. For an optimization of this mode,
the gentle reader is directed to [1]. the gentle reader is directed to [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.
skipping to change at page 2, line 14 skipping to change at page 2, line 18
The Mobile Networks (either implicitly configured on the Home Agent The Mobile Networks (either implicitly configured on the Home Agent
or explicitly identified by the Mobile Router) are advertised by or explicitly identified by the Mobile Router) are advertised by
the Home Agent for route propagation. Traffic to and from nodes in the Home Agent for route propagation. Traffic to and from nodes in
the Mobile Network are tunneled by the Home Agent to the Mobile the Mobile Network are tunneled by the Home Agent to the Mobile
Router, and vice versa. Though packets from the Mobile Network can Router, and vice versa. Though packets from the Mobile Network can
be forwarded directly without tunneling (if reverse tunneling is be forwarded directly without tunneling (if reverse tunneling is
not used) packets will be dropped if ingress filtering is turned not used) packets will be dropped if ingress filtering is turned
on. on.
This document specifies an additional tunnel between Mobile This document specifies an additional tunnel between a Mobile
Router's Home Address and the Home Agent. This tunnel is Router's Home Address and the Home Agent. This tunnel is
encapsulated within the normal tunnel between the Care-of Address encapsulated within the normal tunnel between the Care-of Address
(CoA) and Home Agent. In Foreign Agent CoA mode, the tunnel (CoA) and Home Agent. In Foreign Agent CoA mode, the tunnel
between the Mobile Router and Home Agent is needed to allow the between the Mobile Router and Home Agent is needed to allow the
Foreign Agent to direct the decapsulated packet to the proper Foreign Agent to direct the decapsulated packet to the proper
visiting Mobile Router. However, in Collocated CoA mode, the visiting Mobile Router. However, in Collocated CoA mode, the
additional tunnel is not essential and could be eliminated because additional tunnel is not essential and could be eliminated because
the Mobile Router is the recipient of the encapsulated packets for the Mobile Router is the recipient of the encapsulated packets for
the Mobile Network; a proposal for this feature is in [1]. the Mobile Network; a proposal for this feature is in [1].
skipping to change at page 3, line 22 skipping to change at page 3, line 22
Mobile Router claiming a certain Mobile Network Prefix is Mobile Router claiming a certain Mobile Network Prefix is
authorized to do so. A solution would also expose the Mobile authorized to do so. A solution would also expose the Mobile
Network Prefixes (and potentially other subnet-relevant Network Prefixes (and potentially other subnet-relevant
information) in the exchanged messages, to aid in network information) in the exchanged messages, to aid in network
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
Mobile Network(s) need to be propagated via routing protocol. A which Mobile Network(s) need to be propagated via a routing
Mobile Router may also function in implicit mode, where the Home protocol. A Mobile Router may also function in implicit mode,
Agent may learn the mobile networks through other means, such as where the Home Agent may learn the mobile networks through other
from the AAA server, via pre-configuration or via a dynamic means, such as from the AAA server, via pre-configuration, or
routing protocol. 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 [RFC3344] 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
4.1. Mobile Network Request Extension 4.1. Mobile Network Request Extension
For Explicit Mode, the Mobile Router informs the Home Agent about For Explicit Mode, the Mobile Router informs the Home Agent about
skipping to change at page 6, line 24 skipping to change at page 6, line 24
of a Mobile Node, as set in [RFC3344] and its update [2]. In of a Mobile Node, as set in [RFC3344] and its update [2]. In
addition to maintaining mobility bindings for its Home Address, the addition to maintaining mobility bindings for its Home Address, the
Mobile Router, together with the Home Agent, maintains forwarding Mobile Router, together with the Home Agent, maintains forwarding
information for the Mobile Network Prefix(es) assigned to the information for the Mobile Network Prefix(es) assigned to the
Mobile Router. Mobile Router.
A Mobile Router SHOULD set the 'T' bit to 1 in all Registration A Mobile Router SHOULD set the 'T' bit to 1 in all Registration
Request messages it sends to indicate the need for reverse tunnels Request messages it sends to indicate the need for reverse tunnels
for all traffic. Without reverse tunnels, all the traffic from the for all traffic. Without reverse tunnels, all the traffic from the
mobile network will be subject to ingress filtering in the visited mobile network will be subject to ingress filtering in the visited
networks. Upon reception of successful registration reply, the networks. Upon reception of a successful registration reply, the
Mobile Router processes the registration in accordance to RFC 3344. Mobile Router processes the registration in accordance to
In addition, the following steps are taken: [RFC3344]. In addition, the following steps are taken:
o Check for Mobile Network Acknowledgement extension(s) in o Check for Mobile Network Acknowledgement extension(s) in
Registration Reply Registration Reply
o Create tunnel to the Home Agent if registered in reverse tunneling o Create tunnel to the Home Agent if registered in reverse tunneling
mode mode
o Set up default route via this tunnel or egress interface when o Set up default route via this tunnel or egress interface when
registered with or without reverse tunneling, respectively registered with or without reverse tunneling, respectively
In accordance with this specification, a Mobile Router may operate in In accordance with this specification, a Mobile Router may operate
one of the following two modes: explicit and implicit. In explicit in one of the following two modes: explicit and implicit. In
mode, the Mobile Router includes Mobile Network Prefix information in explicit mode, the Mobile Router includes Mobile Network Prefix
all Registration Requests (as Mobile Network Request extensions), information in all Registration Requests (as Mobile Network Request
while in implicit mode it does not include this information in any extensions), while in implicit mode it does not include this
Registration Request. In this latter case, the Home Agent obtains information in any Registration Request. In this latter case, the
the Mobile Network Prefixes by other means than Mobile IP. One Home Agent obtains the Mobile Network Prefixes by other means than
example of obtention of the Mobile Network Prefix is through static Mobile IP. One example of obtaining the Mobile Network Prefix is
configuration on the Home Agent. through static configuration on the Home Agent.
A Mobile Router can obtain a Collocated or Foreign Agent Care-of- A Mobile Router can obtain a Collocated or Foreign Agent Care-of
Address while operating in explicit or implicit modes. Address while operating in explicit or implicit modes.
For de-registration, the Mobile Router sends a registration request For de-registration, the Mobile Router sends a registration request
with lifetime set to zero without any Mobile Network Request with lifetime set to zero without any Mobile Network Request
extensions. extensions.
5.1. Error Processing 5.1. Error Processing
A Mobile Router interprets the values of the Code field in Mobile A Mobile Router interprets the values of the Code field in the
Network Acknowledgement Extension of the Registration Reply in order Mobile Network Acknowledgement Extension of the Registration Reply
to identify any error related to managing the Mobile Network Prefixes in order to identify any error related to managing the Mobile
by the Home Agent. Network Prefixes by the Home Agent.
If the value of the Code field in the Registration Reply is set to If the value of the Code field in the Registration Reply is set to
HA_MOBNET_DISALLOWED, then the Mobile Router MUST stop sending HA_MOBNET_DISALLOWED, then the Mobile Router MUST stop sending
Registration Requests with any Mobile Network Prefix extensions to Registration Requests with any Mobile Network Prefix extensions to
that Home Agent. that Home Agent.
If the value of the Code field in the Registration Reply is set to If the value of the Code field in the Registration Reply is set to
HA_MOBNET_ERROR then the Mobile Router MUST stop sending Registration HA_MOBNET_ERROR then the Mobile Router MUST stop sending Registration
Requests that contain any of the Mobile Network Prefixes that are Requests that contain any of the Mobile Network Prefixes that are
defined by the values of the fields Prefix and Prefix Length in the defined by the values of the fields Prefix and Prefix Length in the
skipping to change at page 7, line 37 skipping to change at page 7, line 37
6. Home Agent Operation 6. Home Agent Operation
6.1. Summary 6.1. Summary
A Home Agent MUST support all the operations specified in [RFC3344] A Home Agent MUST support all the operations specified in [RFC3344]
and its update [2] for mobile node support. The Home Agent MUST and its update [2] for mobile node support. The Home Agent MUST
support both implicit and explicit modes of operation for a Mobile support both implicit and explicit modes of operation for a Mobile
Router. Router.
The Home Agent processes the registration in accordance to RFC 3344, The Home Agent processes the registration in accordance to
which includes route set up to the Mobile Router's home address via [RFC3344], which includes route set up to the Mobile Router's Home
the tunnel to the Care-of Address. In addition, for a Mobile Router Address via the tunnel to the Care-of Address. In addition, for a
registering in explicit mode, the following steps are taken: Mobile Router registering in explicit mode, the following steps are
taken:
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
skipping to change at page 8, line 24 skipping to change at page 8, line 24
Router and all routes using this tunnel. The Mobile Network Router and all routes using this tunnel. The Mobile Network
extensions are ignored. extensions are ignored.
6.2. Data Structures 6.2. Data Structures
6.2.1. Registration Table 6.2.1. Registration Table
The Registration Table in the Home Agent, in accordance with The Registration Table in the Home Agent, in accordance with
[RFC3344] and its update [2], contains binding information for [RFC3344] and its update [2], contains binding information for
every Mobile Node registered with it. [RFC3344] and its update [2] every Mobile Node registered with it. [RFC3344] and its update [2]
define the format of Registration Table. In addition to all the define the format of a Registration Table. In addition to all the
parameters specified by [RFC3344] and its update [2], the Home parameters specified by [RFC3344] and its update [2], the Home
Agent MUST store the Mobile Network Prefixes associated with the Agent MUST store the Mobile Network Prefixes associated with the
Mobile Router in the corresponding registration entry, when the Mobile Router in the corresponding registration entry, when the
corresponding registration was performed in explicit mode. When corresponding registration was performed in explicit mode. When
the Home Agent is advertising reachability to Mobile Network the Home Agent is advertising reachability to Mobile Network
Prefixes served by a Mobile Router, this information stored in the Prefixes served by a Mobile Router, this information stored in the
Registration Table can be used. Registration Table can be used.
6.2.2. Prefix Table 6.2.2. Prefix Table
The Home Agent must be able to authorize a Mobile Router for use of The Home Agent must be able to authorize a Mobile Router for use of
Mobile Network Prefixes when the Mobile Router is operating in Mobile Network Prefixes when the Mobile Router is operating in
explicit mode. Also, when the Mobile Router operates in implicit explicit mode. Also, when the Mobile Router operates in implicit
mode, the Home Agent must be able to locate the Mobile Network mode, the Home Agent must be able to locate the Mobile Network
Prefixes associated with that Mobile Router. The Home Agent may Prefixes associated with that Mobile Router. The Home Agent may
store the home address of the Mobile Router along with the mobile store the Home Address of the Mobile Router along with the mobile
network prefixes associated with that Mobile Router. If the Mobile network prefixes associated with that Mobile Router. If the Mobile
Router does not have a home address assigned, this table may store Router does not have a Home Address assigned, this table may store
the NAI [RFC2794] of the Mobile Router that will be used in dynamic the NAI [RFC2794] of the Mobile Router that will be used in dynamic
home address assignment. Home Address assignment.
6.3. Mobile Network Prefix Registration 6.3. Mobile Network Prefix Registration
The Home Agent must process registration requests coming from The Home Agent must process registration requests coming from
Mobile Routers in accordance with this section. The document Mobile Routers in accordance with this section. The document
[RFC3344] and its update [2] specify that the home address of a [RFC3344] and its update [2] specify that the Home Address of a
mobile node registering with a Home Agent must belong to a prefix mobile node registering with a Home Agent must belong to a prefix
advertised on the home network. In accordance with this advertised on the home network. In accordance with this
specification, however, the home address must be configured from a specification, however, the Home Address must be configured from a
prefix that is served by the Home Agent, not necessarily the one on prefix that is served by the Home Agent, not necessarily the one on
the home network. the home network.
If the registration request is valid, the Home Agent checks to see If the registration request is valid, the Home Agent checks to see
if there are any Mobile Network Prefix extensions included in the if there are any Mobile Network Prefix extensions included in the
Registration Request. Registration Request.
If so, the Mobile Network Prefix information is obtained from the If so, the Mobile Network Prefix information is obtained from the
included extensions, and the Home Address from the Home Address included extensions, and the Home Address from the Home Address
field of the UDP header Registration Request. For every Mobile field of the Registration Request. For every Mobile Network Prefix
Network Prefix extension included in the registration request, the extension included in the registration request, the Home Agent MUST
Home Agent MUST perform a check against the Prefix Table. If the perform a check against the Prefix Table. If the Prefix Table does
Prefix Table does not contain at least one entry pairing that Home not contain at least one entry pairing that Home Address to that
Address to that Mobile Network Prefix then the check fails, Mobile Network Prefix then the check fails, otherwise it succeeds.
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. MOBNET_UNAUTHORIZED.
For a Mobile Network Prefix for which the check was successfull the For a Mobile Network Prefix for which the check was successfull the
Code field in the respective Mobile Network Acknowledgement Code field in the respective Mobile Network Acknowledgement
skipping to change at page 9, line 58 skipping to change at page 9, line 57
prefixes from the registration table. Also, the Home Agent MUST prefixes from the registration table. Also, the Home Agent MUST
disable forwarding for those prefixes. disable forwarding for those prefixes.
If all checks are successful, the Home Agent either creates a new If all checks are successful, the Home Agent either creates a new
entry for the Mobile Router or updates an existing binding entry entry for the Mobile Router or updates an existing binding entry
for it and returns a successful registration reply back to the for it and returns a successful registration reply back to the
Mobile Router or the Foreign Agent (if the registration request was Mobile Router or the Foreign Agent (if the registration request was
received from a Foreign Agent). received from a Foreign Agent).
In accordance with [RFC3344], the Home Agent does proxy ARP for the In accordance with [RFC3344], the Home Agent does proxy ARP for the
Mobile Router home address, when the Mobile Router home address is Mobile Router Home Address, when the Mobile Router Home Address is
derived from the home network. derived from the home network.
If the 'T' bit is set, the Home Agent creates a bi-directional If the 'T' bit is set, the Home Agent creates a bi-directional
tunnel for the corresponding mobile network prefixes or updates the tunnel for the corresponding mobile network prefixes or updates the
existing bi-directional tunnel. This tunnel is maintained existing bi-directional tunnel. This tunnel is maintained
independent of the reverse tunnel for the Mobile Router home independent of the reverse tunnel for the Mobile Router home
address itself. address itself.
6.4. Advertising Mobile Network Reachability 6.4. Advertising Mobile Network Reachability
skipping to change at page 10, line 26 skipping to change at page 10, line 26
have to advertise the Mobile Network Prefixes. The routes for the have to advertise the Mobile Network Prefixes. The routes for the
Mobile Network Prefix are automatically aggregated into the home Mobile Network Prefix are automatically aggregated into the home
network prefix (it is assumed that the Mobile Network Prefixes are network prefix (it is assumed that the Mobile Network Prefixes are
automatically aggregated into the home network prefix). If the automatically aggregated into the home network prefix). If the
Mobile Router updates the mobile network prefix routes via a Mobile Router updates the mobile network prefix routes via a
dynamic routing protocol, the Home Agent SHOULD propagate the dynamic routing protocol, the Home Agent SHOULD propagate the
routes on the appropriate networks. routes on the appropriate networks.
6.5. Establishment of Bi-directional Tunnel 6.5. Establishment of Bi-directional Tunnel
The Home Agent creates and maintains a bi-directional tunnel for the The Home Agent creates and maintains a bi-directional tunnel for
mobile network prefixes of a Mobile Router registered with it. A the mobile network prefixes of a Mobile Router registered with it.
home agent supporting IPv4 Mobile Router operation MUST be able to A home agent supporting IPv4 Mobile Router operation MUST be able
forward packets destined to the mobile network prefixes served by the to forward packets destined to the mobile network prefixes served
mobile router to its care-of-address. Also, the Home Agent MUST be by the Mobile Router to its Care-of Address. Also, the Home Agent
able to accept packets tunneled by the Mobile Router with the source MUST be able to accept packets tunneled by the Mobile Router with
address of the outer header is set to the care-of-address of the the source address of the outer header set to the Care-of Address
mobile router and that of the inner header is set to the Mobile of the Mobile Router and that of the inner header set to the Mobile
Router's home address or an address from one of the registered mobile Router's Home Address or an address from one of the registered
network prefixes. mobile network prefixes.
6.6. Sending Registration Replies 6.6. Sending Registration Replies
The Home Agents MUST set the status code in the registration reply to The Home Agent MUST set the status code in the registration reply
0 to indicate successful processing of the registration request and to 0 to indicate successful processing of the registration request
successful set up of forwarding for all the mobile network prefixes and successful set up of forwarding for all the mobile network
served by the Mobile Router. The registration reply MUST contain at prefixes served by the Mobile Router. The registration reply MUST
least one Mobile Network Acknowledgement extension. contain at least one Mobile Network Acknowledgement extension.
If the Home Agent is unable to set up forwarding for one of more If the Home Agent is unable to set up forwarding for one of more
mobile network prefixes served by the Mobile Router, it MUST set the mobile network prefixes served by the Mobile Router, it MUST set the
Mobile Network Acknowledgement Extension status code in the Mobile Network Acknowledgement Extension status code in the
registration reply to MOBNET_FWDING_SETUP_FAILED. When the prefix registration reply to MOBNET_FWDING_SETUP_FAILED. When the prefix
length is zero or greater than 32, the status code MUST be set to length is zero or greater than 32, the status code MUST be set to
MOBNET_INVALID_PREFIX_LEN. MOBNET_INVALID_PREFIX_LEN.
If the Mobile Router is not authorized to forward packets to one or If the Mobile Router is not authorized to forward packets to one or
mobile network prefixes included in the request, the Home Agent MUST mobile network prefixes included in the request, the Home Agent MUST
set the code to MOBNET_UNAUTHORIZED_MR. set the code to MOBNET_UNAUTHORIZED_MR.
6.7. Mobile Network Prefix De-registration 6.7. Mobile Network Prefix De-registration
If the received registration request is for de-registration of the If the received registration request is for de-registration of the
care-of-address, the Home Agent, upon successful processing of it, Care-of Address, the Home Agent, upon successful processing of it,
MUST delete the entry(ies) from its registration table. The home MUST delete the entry(ies) from its registration table. The home
agent tears down the bi-directional tunnel and stops forwarding any agent tears down the bi-directional tunnel and stops forwarding any
packets to/from the Mobile Router. The Home Agent MUST ignore any packets to/from the Mobile Router. The Home Agent MUST ignore any
included Mobile Network Request extension in a de-registration included Mobile Network Request extension in a de-registration
request. request.
7. Data Forwarding Operation 7. Data Forwarding Operation
For traffic to the nodes in the Mobile Network, the Home Agent MUST For traffic to the nodes in the Mobile Network, the Home Agent MUST
perform double tunneling of the packet, if the Mobile Router had perform double tunneling of the packet, if the Mobile Router had
registered with a Foreign Agent care-of-address. In this case, the registered with a Foreign Agent Care-of Address. In this case, the
Home Agent MUST encapsulate the packet with tunnel header (source IP Home Agent MUST encapsulate the packet with tunnel header (source
address set to Home Agent and destination IP address set to Mobile IP address set to Home Agent and destination IP address set to
Router's home address) and then encapsulate one more time with tunnel Mobile Router's Home Address) and then encapsulate one more time
header (source IP address set to Home Agent and destination IP with tunnel header (source IP address set to Home Agent and
address set to CoA). destination IP address set to CoA).
For optimization, the Home Agent SHOULD only encapsulate the packet For optimization, the Home Agent SHOULD only encapsulate the packet
with the tunnel header (source IP address set to Home Agent and with the tunnel header (source IP address set to Home Agent and
destination IP address set to CoA) for Collocated CoA mode. destination IP address set to CoA) for Collocated CoA mode.
When a Home Agent receives a packet from the mobile network prefix in When a Home Agent receives a packet from the mobile network prefix
the bi-directional tunnel, it MUST de-encapsulate the packet and in the bi-directional tunnel, it MUST de-encapsulate the packet and
route it as a normal IP packet. It MUST verify that the incoming route it as a normal IP packet. It MUST verify that the incoming
packet has the source IP address set to the care-of-address of the packet has the source IP address set to the Care-of Address of the
Mobile Router. The packet MUST be dropped if the source address is Mobile Router. The packet MUST be dropped if the source address is
not set to the care-of-address of the Mobile Router. not set to the Care-of Address of the Mobile Router.
For traffic from the nodes in the Mobile Network, the Mobile Router For traffic from the nodes in the Mobile Network, the Mobile Router
encapsulates the packet with tunnel header (source IP address set to encapsulates the packet with a tunnel header (source IP address set
Mobile Router's home address and destination IP address set to Home to Mobile Router's Home Address and destination IP address set to
Agent) if reverse tunnel is enabled. Otherwise, the packet is routed Home Agent) if reverse tunnel is enabled. Otherwise, the packet is
directly to the Foreign Agent or access router. routed directly to the Foreign Agent or access router.
In Collocated CoA mode, the Mobile Router MAY encapsulate one more In Collocated CoA mode, the Mobile Router MAY encapsulate one more
times with tunnel header (source IP address set to the CoA and times with a tunnel header (source IP address set to the CoA and
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
skipping to change at page 13, line 9 skipping to change at page 13, line 9
If the Mobile Router and the Home Agent use a dynamic routing If the Mobile Router and the Home Agent use a dynamic routing
protocol over the tunnel interface, and if that protocol offers protocol over the tunnel interface, and if that protocol offers
security mechanisms to protect that protocol's messages, then the security mechanisms to protect that protocol's messages, then the
security recommendations in section 10.1 apply. security recommendations in section 10.1 apply.
10. Security Considerations 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 [RFC3344].
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
Router for those prefixes. A registration failure MUST be notified Router for those prefixes. A registration failure MUST be notified
to the mobile router when it cannot be successfully authorized for to the mobile router when it cannot be successfully authorized for
prefixes requested by it. prefixes requested by it.
skipping to change at page 15, line 4 skipping to change at page 14, line 52
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 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)
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 2007-10-04, (contents last updated 2007-07-02 and last browsed 2007-10-04).
October).
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. reviewed one of the later versions of the draft. Hans Sjostrand
(Hans Sj\"ostrand) identified the last clarifications with respect
to Foreign Agent mode treatment. Pete McCann contributed necessary
refinements of many statements.
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.
[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.
skipping to change at page 16, line 10 skipping to change at page 16, line 10
[2] Perkins, C., Ed., "IP Mobility Support for IPv4, [2] Perkins, C., Ed., "IP Mobility Support for IPv4,
revised", draft-ietf-mip4-rfc3344bis-05.txt, IETF revised", draft-ietf-mip4-rfc3344bis-05.txt, IETF
Internet-Draft, Work in Progress, July 9, 2007. Internet-Draft, Work in Progress, July 9, 2007.
14. Changelog 14. 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-04.txt to
draft-ietf-mip4-nemo-v4-base-05.txt
-updated the Acknowledgements section.
-capitalized all occurences of "Home Address", "Mobile Router"
and "Care-of Address".
-refined many statements.
-checked against 'idnits' script version 2.04.16.
From draft-ietf-mip4-nemo-v4-base-03.txt to From draft-ietf-mip4-nemo-v4-base-03.txt to
draft-ietf-mip4-nemo-v4-base-04.txt draft-ietf-mip4-nemo-v4-base-04.txt
-more changes in Introduction to say that with FA mode only the -more changes in Introduction to say that with FA mode only the
non-optimized double-encapsulation operation is supported and non-optimized double-encapsulation operation is supported and
[1] proposes optimization. [1] proposes a optimization.
From draft-ietf-mip4-nemo-v4-base-02.txt to From draft-ietf-mip4-nemo-v4-base-02.txt to
draft-ietf-mip4-nemo-v4-base-03.txt draft-ietf-mip4-nemo-v4-base-03.txt
-changed a sentence in the introduction to say that FA mode _is_ -changed a sentence in the Introduction to say that FA mode _is_
supported but unoptimized, and that a reference [1] optimizes supported but unoptimized, and that a reference [1] optimizes
that mode. that mode.
-added reference [2] to the rfc3344bis draft. -added reference [2] to the rfc3344bis draft.
From draft-ietf-mip4-nemo-v4-base-01.txt to From draft-ietf-mip4-nemo-v4-base-01.txt to
draft-ietf-mip4-nemo-v4-base-02.txt draft-ietf-mip4-nemo-v4-base-02.txt
-changed title from "IPv4 Network Mobility (NEMO) Protocol" to -changed title from "IPv4 Network Mobility (NEMO) Protocol" to
"Network Mobility (NEMO) Extensions for Mobile IPv4" "Network Mobility (NEMO) Extensions for Mobile IPv4".
From draft-ietf-mip4-nemo-v4-base-00.txt to From draft-ietf-mip4-nemo-v4-base-00.txt to
draft-ietf-mip4-nemo-v4-base-01.txt draft-ietf-mip4-nemo-v4-base-01.txt
-added a section on Routing Protocol between Mobile Router and -added a section on Routing Protocol between Mobile Router and
Home Agent. Home Agent.
-added a security subsection about running simultaneously a -added a security subsection about running simultaneously a
secure routing protocol with secure Mobile IPv4. secure routing protocol with secure Mobile IPv4.
-added a date tag on the IANA URL for Mobile IP numbering -added a date tag on the IANA URL for Mobile IP numbering
spaces. spaces.
-substituted 'Mobile Router' for 'MR' everywhere. -substituted 'Mobile Router' for 'MR' everywhere.
skipping to change at page 17, line 46 skipping to change at page 18, line 4
Email: gdommety@cisco.com Email: gdommety@cisco.com
Vidya Narayanan Vidya Narayanan
QUALCOMM, Inc. QUALCOMM, Inc.
5775 Morehouse Dr 5775 Morehouse Dr
San Diego, CA San Diego, CA
USA USA
Phone: +1 858-845-2483 Phone: +1 858-845-2483
Email: vidyan@qualcomm.com Email: vidyan@qualcomm.com
Alexandru Petrescu Alexandru Petrescu
Motorola Motorola
Parc les Algorithmes Saint Aubin Parc les Algorithmes Saint Aubin
Gif-sur-Yvette 91193 Gif-sur-Yvette 91193
France France
Email: Alexandru.Petrescu@motorola.com Email: Alexandru.Petrescu@motorola.com
Comments are solicited and should be addressed to the working
group's mailing list at mip4@ietf.org and/or the authors.
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 18, line 33 skipping to change at page 18, line 42
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Disclaimer of Validity
This document and the information contained herein are provided on This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE IETF TRUST AND THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The IETF Trust (2007). This document is subject to Copyright (C) The IETF Trust (2007). This document is subject to
the rights, licenses and restrictions contained in BCP 78, and the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
 End of changes. 43 change blocks. 
99 lines changed or deleted 107 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/