draft-ietf-mip4-nemo-v4-base-02.txt   draft-ietf-mip4-nemo-v4-base-03.txt 
Network Working Group K. Leung Network Working Group K. Leung
Internet-Draft G. Dommety Internet-Draft G. Dommety
Expires: March 15, 2008 Cisco Systems Expires: April 9, 2008 Cisco Systems
V. Narayanan V. Narayanan
QUALCOMM, Inc. Qualcomm, Inc.
A. Petrescu A. Petrescu
Motorola Motorola
September 12, 2007 October 4, 2007
Network Mobility (NEMO) Extensions for Mobile IPv4 Network Mobility (NEMO) Extensions for Mobile IPv4
draft-ietf-mip4-nemo-v4-base-02.txt draft-ietf-mip4-nemo-v4-base-03.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 March 10, 2008. This Internet-Draft will expire on April 9, 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 59 skipping to change at page 1, line 59
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.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 4 4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 3
4.1. Mobile Network Request Extension . . . . . . . . . . . . . 4 4.1. Mobile Network Request Extension . . . . . . . . . . . . . 3
4.2. Mobile Network Acknowledgement Extension . . . . . . . . . 5 4.2. Mobile Network Acknowledgement Extension . . . . . . . . . 4
5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 6 5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 6
5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 7 5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 6
6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 8 6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 7
6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 8 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 9 6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 8
6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 9 6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 8
6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 9 6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 8
6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 9 6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 8
6.4. Advertising Mobile Network Reachability . . . . . . . . .10 6.4. Advertising Mobile Network Reachability . . . . . . . . .10
6.5. Establishment of Bi-directional Tunnel . . . . . . . . . .11 6.5. Establishment of Bi-directional Tunnel . . . . . . . . . .10
6.6. Sending Registration Replies . . . . . . . . . . . . . . .11 6.6. Sending Registration Replies . . . . . . . . . . . . . . .10
6.7. Mobile Network Prefix De-registration . . . . . . . . . .11 6.7. Mobile Network Prefix De-registration . . . . . . . . . .11
7. Data Forwarding Operation . . . . . . . . . . . . . . . . . .11 7. Data Forwarding Operation . . . . . . . . . . . . . . . . . .11
8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . .12 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. . . . . . .14 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 . . . . . . . . . . . . . . . . . . . . . . . . . .16 13. References . . . . . . . . . . . . . . . . . . . . . . . . . .15
13.1. Normative References . . . . . . . . . . . . . . . . . . .16 13.1. Normative References . . . . . . . . . . . . . . . . . . .15
13.2. Informative References . . . . . . . . . . . . . . . . . .16 13.2. Informative References . . . . . . . . . . . . . . . . . .15
13. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .16 13. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .17
Intellectual Property and Copyright Statements . . . . . . . . . .19 Intellectual Property and Copyright Statements . . . . . . . . . .18
1. Introduction 1. Introduction
This document describes protocol extensions to Mobile IPv4 This document describes protocol extensions to Mobile IPv4 as per
([RFC3344]) to enable support for Mobile Networks. This draft [RFC3344] and its update [2], to enable support for Mobile
addresses only co-located Care-of Address mode (not Foreign Agent Networks. This draft addresses mainly the co-located Care-of
Care-of Address mode, for which the gentle reader is directed to Address mode. Foreign Agent Care-of Address mode (with 'legacy'
[1]). Foreign Agents, RFC 3344) are supported but without optimization,
double encapsulation being used. For an optimization of this mode,
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.
Mobility for the Mobile Network is supported by the Mobile Router Mobility for the Mobile Network is supported by the Mobile Router
skipping to change at page 2, line 40 skipping to change at page 2, line 40
Multihoming for Mobile Routers is outside the scope of this Multihoming for Mobile Routers is outside the scope of this
document. document.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Terminology for network mobility support is defined in [RFC3344]. In Terminology for network mobility support is defined in [RFC3344]
addition, this document defines the following terms. and its update [2]. In addition, this document defines the
following terms.
Mobile Network Prefix Mobile Network Prefix
The network prefix of the subnet delegated to a Mobile Router The network prefix of the subnet delegated to a Mobile Router
as the Mobile Network. as the Mobile Network.
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
skipping to change at page 4, line 9 skipping to change at page 3, line 40
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
4.1. Mobile Network Request Extension 4.1. Mobile Network Request Extension
For Explicit Mode, the Mobile Router informs the Home Agent about the For Explicit Mode, the Mobile Router informs the Home Agent about
Mobile Network Prefixes during registration. The Registration the Mobile Network Prefixes during registration. The Registration
Request contains zero, one or several Mobile Network Request Request contains zero, one or several Mobile Network Request
extensions in addition to any other extensions defined by or in the extensions in addition to any other extensions defined by or in the
context of ([RFC3344]). When several Mobile Networks are needed to context of [RFC3344]. When several Mobile Networks are needed to
be registered, each is included in a separate Mobile Network Request be registered, each is included in a separate Mobile Network
extension, with its own Type, Length, Sub-Type, Prefix Length and Request extension, with its own Type, Length, Sub-Type, Prefix
Prefix fields. A Mobile Network Request extension is encoded in Length and Prefix fields. A Mobile Network Request extension is
Type-Length-Value (TLV) format and respects the following format: encoded in Type-Length-Value (TLV) format and respects the
following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Sub-Type | Prefix Length | | Type | Length | Sub-Type | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix | | Prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
skipping to change at page 5, line 9 skipping to change at page 4, line 41
Prefix: Prefix:
32-bit unsigned integer in network byte-order containing an 32-bit unsigned integer in network byte-order containing an
IPv4 address whose first Prefix Length bits make up the Mobile IPv4 address whose first Prefix Length bits make up the Mobile
Network Prefix. Network Prefix.
4.2. Mobile Network Acknowledgement Extension 4.2. Mobile Network Acknowledgement Extension
The Registration Reply contains zero, one or several Mobile Network The Registration Reply contains zero, one or several Mobile Network
Acknowledgement extensions in addition to any other extensions Acknowledgement extensions in addition to any other extensions
defined by or in the context of ([RFC3344]). For Implicit Mode, defined by or in the context of [RFC3344] and its update [2].
the Mobile Network Acknowledgement informs the Mobile Router the For Implicit Mode, the Mobile Network Acknowledgement informs the
prefixes for which the Home Agent sets up forwarding with respect Mobile Router the prefixes for which the Home Agent sets up
to this Mobile Router. Policies such as permitting only traffic forwarding with respect to this Mobile Router. Policies such as
from these Mobile Networks to be tunneled to the Home Agent may be permitting only traffic from these Mobile Networks to be tunneled
applied by the Mobile Router. For Explicit Mode, when several to the Home Agent may be applied by the Mobile Router. For
Mobile Networks are needed to be acknowledged explicitly, each is Explicit Mode, when several Mobile Networks are needed to be
included in a separate Mobile Network Acknowledgement extension, acknowledged explicitly, each is included in a separate Mobile
with its own Type, Sub-Type, Length and Prefix Length fields. Network Acknowledgement extension, with its own Type, Sub-Type,
Optionally, all requested Mobile Networks could be acknowledged Length and Prefix Length fields. Optionally, all requested Mobile
using only one Mobile Network Acknowledgement extension with Networks could be acknowledged using only one Mobile Network
"Prefix Length" and "Prefix" fields set to zero. At least one Acknowledgement extension with "Prefix Length" and "Prefix" fields
Mobile Network Acknowledgement extension MUST be in a successful set to zero. At least one Mobile Network Acknowledgement extension
Registration Reply to indicate to the Mobile Router that the Mobile MUST be in a successful Registration Reply to indicate to the
Network Request extension was processed, thereby not skipped by the Mobile Router that the Mobile Network Request extension was
Home Agent. A Registration Reply may contain any non-zero number processed, thereby not skipped by the Home Agent.
of Explicit Mode and Implicit Mode Acknowledgements sub-types. Both
sub-types can be present in a single Registration Reply. A Mobile
Network Acknowledgement extension is encoded in Type-Length-Value
(TLV) format and respects the following format:
When the registration is denied with code HA_MOBNET_ERROR, the Code A Registration Reply may contain any non-zero number of Explicit
field in the extension provides the reason for the failure. Mode and Implicit Mode Acknowledgements sub-types. Both sub-types
can be present in a single Registration Reply. A Mobile Network
Acknowledgement extension is encoded in Type-Length-Value (TLV)
format. When the registration is denied with code HA_MOBNET_ERROR,
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Sub-Type | Code | | Type | Length | Sub-Type | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prefix Length | Reserved | Prefix | Prefix Length | Reserved | Prefix
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 34 skipping to change at page 6, line 13
Sent as zero; ignored on reception. Sent as zero; ignored on reception.
Prefix: Prefix:
32-bit unsigned integer in network byte-order containing an 32-bit unsigned integer in network byte-order containing an
IPv4 address whose first Prefix Length bits make up the Mobile IPv4 address whose first Prefix Length bits make up the Mobile
Network Prefix. Network Prefix.
5. Mobile Router Operation 5. Mobile Router Operation
A Mobile Router's operation is generally derived from the behavior of A Mobile Router's operation is generally derived from the behavior
a Mobile Node, as set in ([RFC3344]). In addition to maintaining of a Mobile Node, as set in [RFC3344] and its update [2]. In
mobility bindings for its Home Address, the Mobile Router, together addition to maintaining mobility bindings for its Home Address, the
with the Home Agent, maintains forwarding information for the Mobile Mobile Router, together with the Home Agent, maintains forwarding
Network Prefix(es) assigned to the Mobile Router. information for the Mobile Network Prefix(es) assigned to the
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 successful registration reply, the
Mobile Router processes the registration in accordance to RFC 3344. Mobile Router processes the registration in accordance to RFC 3344.
In addition, the following steps are taken: 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
skipping to change at page 8, line 9 skipping to change at page 7, line 32
be interpreted by the Mobile Router as the case where the Home Agent be interpreted by the Mobile Router as the case where the Home Agent
does not support mobile networks. does not support mobile networks.
All the error code values are TBA (To Be Assigned) subject to IANA All the error code values are TBA (To Be Assigned) subject to IANA
allocation. allocation.
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]
for mobile node support. The Home Agent MUST support both implicit and its update [2] for mobile node support. The Home Agent MUST
and explicit modes of operation for a Mobile Router. support both implicit and explicit modes of operation for a Mobile
Router.
The Home Agent processes the registration in accordance to RFC 3344, The Home Agent processes the registration in accordance to RFC 3344,
which includes route set up to the Mobile Router's home address via which includes route set up to the Mobile Router's home address via
the tunnel to the Care-of Address. In addition, for a Mobile Router the tunnel to the Care-of Address. In addition, for a Mobile Router
registering in explicit mode, the following steps are taken: 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
skipping to change at page 9, line 10 skipping to change at page 8, line 22
For deregistration, the Home Agent removes the tunnel to the Mobile For deregistration, the Home Agent removes the tunnel to the Mobile
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], contains binding information for every Mobile Node [RFC3344] and its update [2], contains binding information for
registered with it. [RFC3344] defines the format of Registration every Mobile Node registered with it. [RFC3344] and its update [2]
Table. In addition to all the parameters specified by [RFC3344], define the format of Registration Table. In addition to all the
the Home Agent MUST store the Mobile Network Prefixes associated parameters specified by [RFC3344] and its update [2], the Home
with the Mobile Router in the corresponding registration entry, Agent MUST store the Mobile Network Prefixes associated with the
when the corresponding registration was performed in explicit mode. Mobile Router in the corresponding registration entry, when the
When the Home Agent is advertising reachability to Mobile Network corresponding registration was performed in explicit mode. When
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 the NAI [RFC2794] of the Mobile Router that will be used in dynamic
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 Mobile The Home Agent must process registration requests coming from
Routers in accordance with this section. ([RFC3344]) specifies that Mobile Routers in accordance with this section. The document
the home address of a mobile node registering with a Home Agent must [RFC3344] and its update [2] specify that the home address of a
belong to a prefix advertised on the home network. In accordance mobile node registering with a Home Agent must belong to a prefix
with this specification, however, the home address must be configured advertised on the home network. In accordance with this
from a prefix that is served by the Home Agent, not necessarily the specification, however, the home address must be configured from a
one on the home network. prefix that is served by the Home Agent, not necessarily the one on
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. If so, the Mobile Network Prefix information Registration Request.
is obtained from the included extensions, and the Home Address from
the Home Address field of the UDP header Registration Request. For If so, the Mobile Network Prefix information is obtained from the
every Mobile Network Prefix extension included in the registration included extensions, and the Home Address from the Home Address
request, the Home Agent MUST perform a check against the Prefix field of the UDP header Registration Request. For every Mobile
Table. If the Prefix Table does not contain at least one entry Network Prefix extension included in the registration request, the
pairing that Home Address to that Mobile Network Prefix then the Home Agent MUST perform a check against the Prefix Table. If the
check fails, otherwise it succeeds. Prefix Table does not contain at least one entry pairing that Home
Address to that Mobile Network Prefix then the 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. 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 10, line 41 skipping to change at page 9, line 57
information in the registration request, it MUST delete those information in the registration request, it MUST delete those
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 In accordance with [RFC3344], the Home Agent does proxy ARP for the
the Mobile Router home address, when the Mobile Router home address Mobile Router home address, when the Mobile Router home address is
is derived from the home network. If the 'T' bit is set, the Home derived from the home network.
Agent creates a bi-directional tunnel for the corresponding mobile
network prefixes or updates the existing bi-directional tunnel. If the 'T' bit is set, the Home Agent creates a bi-directional
This tunnel is maintained independent of the reverse tunnel for the tunnel for the corresponding mobile network prefixes or updates the
Mobile Router home address itself. existing bi-directional tunnel. This tunnel is maintained
independent of the reverse tunnel for the Mobile Router home
address itself.
6.4. Advertising Mobile Network Reachability 6.4. Advertising Mobile Network Reachability
If the mobile network prefixes served by the Home Agent are If the mobile network prefixes served by the Home Agent are
aggregated with the home network prefix and if the Home Agent is aggregated with the home network prefix and if the Home Agent is
the default router on the home network, the Home Agent does not the default router on the home network, the Home Agent does not
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
skipping to change at page 13, line 8 skipping to change at page 12, line 29
necessary when new fixed networks are added in the home network. necessary when new fixed networks are added in the home network.
Here too, the purpose of NEMOv4 extensions is not to inform the Here too, the purpose of NEMOv4 extensions is not to inform the
Mobile Router about topology changes at home. Mobile Router about topology changes at home.
Examples of dynamic routing protocol include but are not limited to Examples of dynamic routing protocol include but are not limited to
OSPF Version 2 [RFC2328], BGP [RFC4271] and RIP [RFC2453]. OSPF Version 2 [RFC2328], BGP [RFC4271] and RIP [RFC2453].
The recommendations are related to how the routing protocol and the The recommendations are related to how the routing protocol and the
Mobile IPv4 implementation work in tandem on the Mobile Router and Mobile IPv4 implementation work in tandem on the Mobile Router and
on the Home Agent (1) without creating incoherent states in the on the Home Agent (1) without creating incoherent states in the
forwarding bases at home and on the Mobile Router (2) without forwarding information bases at home and on the Mobile Router (2)
introducing topologically incorrect addressing information in the without introducing topologically incorrect addressing information
visited domain and (3) efficiently avoid duplication of sent data in the visited domain and (3) efficiently avoid duplication of sent
or over-provisioning of security. data or over-provisioning of security.
The information exchanged between the Mobile Router and the Home The information exchanged between the Mobile Router and the Home
Agent is sent over the bi-directional tunnel established by the Agent is sent over the bi-directional tunnel established by the
Mobile IPv4 exchange Registration Request - Registration Reply (see Mobile IPv4 exchange Registration Request - Registration Reply (see
section 6.5). If a network address and prefix about a subnet in 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 the moving network is sent by the Mobile Router within a routing
protocol message then they SHOULD NOT be sent in the Mobile IPv4 protocol message then they SHOULD NOT be sent in the Mobile IPv4
Registration Request too, in order to avoid incoherencies in the Registration Request too, in order to avoid incoherencies in the
forwarding information bases. The Mobile Router SHOULD use NEMOv4 forwarding information bases. The Mobile Router SHOULD use NEMOv4
implicit mode in this case (see section 3). implicit mode in this case (see section 3).
skipping to change at page 13, line 49 skipping to change at page 13, line 21
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.
All registration requests and replies MUST be authenticated by the All registration requests and replies MUST be authenticated by the
MN-HA Authentication Extension as specified in ([RFC3344]). When the MN-HA Authentication Extension as specified in [RFC3344] and its
registration request is sent in explicit mode, i.e., with one or more update [2]. When the registration request is sent in explicit
Mobile Network Prefix extensions, all the Mobile Network Prefix mode, i.e., with one or more Mobile Network Prefix extensions, all
extensions MUST be included before the MN-HA Authentication the Mobile Network Prefix extensions MUST be included before the
extension. Also, these extensions MUST be included in the MN-HA Authentication extension. Also, these extensions MUST be
calculation of the MN-HA authenticator value. included in the 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. a source address belonging to the mobile network.
The Mobile Router MUST also ensure that the source address of The Mobile Router MUST also ensure that the source address of
packets arriving on the mobile network is not the same as the packets arriving on the mobile network is not the same as the
Mobile Router's IP address on any interface. These checks will Mobile Router's IP address on any interface. These checks will
protect against nodes attempting to launch IP spoofing attacks protect against nodes attempting to launch IP spoofing attacks
skipping to change at page 15, line 28 skipping to change at page 15, line 4
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 10 September (contents last updated 2007-07-02 and last browsed 2007-10-04,
2007). 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.
13. References 13. References
skipping to change at page 16, line 38 skipping to change at page 15, line 50
[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-ietf-mip4-nemov4-fa-01.txt, IETF Internet-Draft, draft-ietf-mip4-nemov4-fa-01.txt, IETF Internet-Draft,
Work in Progress, March 19, 2007. Work in Progress, March 19, 2007.
[2] Perkins, C., Ed., "IP Mobility Support for IPv4,
revised", draft-ietf-mip4-rfc3344bis-05.txt, IETF
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-02.txt to
draft-ietf-mip4-nemo-v4-base-03.txt
-changed a sentence in the introduction to say that FA mode _is_
supported but unoptimized, and that a reference [1] optimizes
that mode.
-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
 End of changes. 31 change blocks. 
112 lines changed or deleted 135 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/