draft-ietf-nemo-v4-base-00.txt   draft-ietf-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 24, 2006 Cisco Systems Expires: December 26, 2006 Cisco Systems
V. Narayanan V. Narayanan
QUALCOMM, Inc. QUALCOMM, Inc.
A. Petrescu A. Petrescu
Motorola Motorola
February 24, 2006 June 26, 2006
IPv4 Network Mobility (NEMO) Basic Support Protocol IPv4 Network Mobility (NEMO) Basic Support Protocol
draft-ietf-nemo-v4-base-00.txt draft-ietf-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 38 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 24, 2006. This Internet-Draft will expire on December 26, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document describes the support of Mobile Networks, as defined in This document describes the support of Mobile Networks, as defined in
Mobile IPv4, by the Mobile Router and Home Agent. A Mobile Router is Mobile IPv4, by the Mobile Router and Home Agent. A Mobile Router is
responsible for the mobility of one or more network segments or responsible for the mobility of one or more network segments or
subnets moving together. The Mobile Router hides its mobility from subnets moving together. The Mobile Router hides its mobility from
the nodes on the mobile network. The nodes on the Mobile Network may the nodes on the mobile network. The nodes on the Mobile Network may
be fixed in relationship to the Mobile Router and may not have any be fixed in relationship to the Mobile Router and may not have any
mobility function. 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 6 4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 4
4.1. Mobile Network Request Extension . . . . . . . . . . . . . 6 4.1. Mobile Network Request Extension . . . . . . . . . . . . . 4
4.2. Mobile Network Acknowledgement Extension . . . . . . . . . 7 4.2. Mobile Network Acknowledgement Extension . . . . . . . . . 5
5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 9 5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 6
5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 9 5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 7
6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 11 6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 7
6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 11 6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 8
6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 11 6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 8
6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 12 6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 8
6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 12 6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 9
6.4. Advertising Mobile Network Reachability . . . . . . . . . 13 6.4. Advertising Mobile Network Reachability . . . . . . . . .10
6.5. Establishment of Bi-directional Tunnel . . . . . . . . . . 13 6.5. Establishment of Bi-directional Tunnel . . . . . . . . . .10
6.6. Sending Registration Replies . . . . . . . . . . . . . . . 14 6.6. Sending Registration Replies . . . . . . . . . . . . . . .10
6.7. Mobile Network Prefix De-registration . . . . . . . . . . 14 6.7. Mobile Network Prefix De-registration . . . . . . . . . .11
7. Data Forwarding Operation . . . . . . . . . . . . . . . . . . 15 7. Data Forwarding Operation . . . . . . . . . . . . . . . . . .11
8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . . 16 8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . .11
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17 9. Security Considerations . . . . . . . . . . . . . . . . . . .12
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .13
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 20 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .14
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 12. References . . . . . . . . . . . . . . . . . . . . . . . . . .14
12.1. Normative References . . . . . . . . . . . . . . . . . . . 21 12.1. Normative References . . . . . . . . . . . . . . . . . . .14
12.2. Informative References . . . . . . . . . . . . . . . . . . 21 12.2. Informative References . . . . . . . . . . . . . . . . . .14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 13. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .14
Intellectual Property and Copyright Statements . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .15
Intellectual Property and Copyright Statements . . . . . . . . . .16
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. A Mobile Network ([RFC3344]) to enable support for Mobile Networks. A Mobile Network
is defined as a network segment or subnet that can change its point is defined as a network segment or subnet that can change its point
of attachment to the routing infrastructure. Such movement is of attachment to the routing infrastructure. Such movement is
performed by a Mobile Router, which is the mobility entity that performed by a Mobile Router, which is the mobility entity that
provides connectivity and reachability as well as session continuity provides connectivity and reachability as well as session continuity
for all the nodes in the Mobile Network. The Mobile Router typically for all the nodes in the Mobile Network. The Mobile Router typically
skipping to change at page 7, line 9 skipping to change at page 5, line 9
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, the defined by or in the context of ([RFC3344]). For Implicit Mode,
Mobile Network Acknowledgement informs the Mobile Router the prefixes the Mobile Network Acknowledgement informs the Mobile Router the
served by the Home Agent. Policies such as permitting only traffic prefixes served by the Home Agent. Policies such as permitting
from these Mobile Networks to be tunneled to the Home Agent may be only traffic from these Mobile Networks to be tunneled to the Home
applied by the Mobile Router. For Explicit Mode, when several Mobile Agent may be applied by the Mobile Router. For Explicit Mode, when
Networks are needed to be acknowledged explicitly, each is included several Mobile Networks are needed to be acknowledged explicitly,
in a separate Mobile Network Acknowledgement extension, with its own each is included in a separate Mobile Network Acknowledgement
Type, Sub-Type, Length and Prefix Length fields. Optionally, all extension, with its own Type, Sub-Type, Length and Prefix Length
requested Mobile Networks could be acknowledged using only one Mobile fields. Optionally, all requested Mobile Networks could be
Network Acknowledgement extension with "Prefix Length" and "Prefix" acknowledged using only one Mobile Network Acknowledgement
fields set to zero. At least one Mobile Network Acknowledgement extension with "Prefix Length" and "Prefix" fields set to zero. At
extension MUST be in a successful Registration Reply to indicate to least one Mobile Network Acknowledgement extension MUST be in a
the Mobile Router that the Mobile Network Request extension was successful Registration Reply to indicate to the Mobile Router that
processed, thereby not skipped by the Home Agent. A Registration the Mobile Network Request extension was processed, thereby not
Reply may have either or both Implicit Mode Acknowledgement or skipped by the Home Agent. A Registration Reply may contain any
Explicit Mode Acknowledgement extensions. A Mobile Network non-zero number of Explicit Mode and Implicit Mode Acknowledgements
Acknowledgement extension is encoded in Type-Length-Value (TLV) sub-types. Both sub-types can be present in a single Registration
format and respects the following format: 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 When the registration is denied with code HA_MOBNET_ERROR, the Code
field in the extension provides the reason for the failure. 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 8, line 4 skipping to change at page 5, line 50
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
Mobile Network Extension (skippable type range to be assigned Mobile Network Extension (skippable type range to be assigned
by IANA) by IANA)
Length: Length:
8 8
Sub-Type:
2 (Explicit Mode Acknowledgement) Sub-Type:
3 (Implicit Mode Acknowledgement) TBA (Explicit Mode Acknowledgement)
TBA (Implicit Mode Acknowledgement)
Code: Code:
Value indicating success or failure. Value indicating success or failure.
0 Success 0 Success
1 Invalid prefix (MOBNET_INVALID_PREFIX_LEN) TBA Invalid prefix (MOBNET_INVALID_PREFIX_LEN)
2 MR is not authorized for prefix (MOBNET_UNAUTHORIZED) TBA MR is not authorized for prefix (MOBNET_UNAUTHORIZED)
3 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:
Sent as zero; ignored on reception. Sent as zero; ignored on reception.
skipping to change at page 9, line 27 skipping to change at page 6, line 53
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
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 roaming 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 in
one of the following two modes: explicit and implicit. In explicit one of the following two modes: explicit and implicit. In explicit
mode, the Mobile Router includes Mobile Network Prefix information in mode, the Mobile Router includes Mobile Network Prefix information in
all Registration Requests (as Mobile Network Request extensions), all Registration Requests (as Mobile Network Request extensions),
while in implicit mode it does not include this information in any while in implicit mode it does not include this information in any
Registration Request. In this latter case, the Home Agent obtains Registration Request. In this latter case, the Home Agent obtains
the Mobile Network Prefixes by other means than Mobile IP. the Mobile Network Prefixes by other means than Mobile IP.
skipping to change at page 10, line 4 skipping to change at page 7, line 24
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 Mobile
Network Acknowledgement Extension of the Registration Reply in order Network Acknowledgement Extension of the Registration Reply in order
to identify any error related to managing the Mobile Network Prefixes to identify any error related to managing the Mobile Network Prefixes
by the Home Agent. 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_UNSUPPORTED or HA_MOBNET_DISALLOWED, then the Mobile Router HA_MOBNET_DISALLOWED, then the Mobile Router MUST stop sending
MUST stop sending Registration Requests with any Mobile Network Registration Requests with any Mobile Network Prefix extensions to
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
Mobile Network Acknowledgement extension. Note that the registration Mobile Network Acknowledgement extension. Note that the registration
is denied in this case and no forwarding for any Mobile Network is denied in this case and no forwarding for any Mobile Network
Prefixes would be set up by the Home Agent for the Mobile Router. Prefixes would be set up by the Home Agent for the Mobile Router.
It is possible that the Mobile Router receives a registration reply It is possible that the Mobile Router receives a registration reply
with no mobile network extensions if the registration was processed with no mobile network extensions if the registration was processed
by a Mobile IPv4 home agent that does not support this specification by a Mobile IPv4 home agent that does not support this specification
at all. In that case, the absence of mobile network extensions must at all. In that case, the absence of mobile network extensions must
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 subject to IANA allocation. All the error code values are TBA (To Be Assigned) subject to IANA
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 for mobile node support. The Home Agent MUST support both implicit
and explicit modes of operation for a Mobile Router. 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,
skipping to change at page 12, line 35 skipping to change at page 9, line 15
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 Mobile
Routers in accordance with this section. ([RFC3344]) specifies that Routers in accordance with this section. ([RFC3344]) specifies that
the home address of a mobile node registering with a Home Agent must the home address of a mobile node registering with a Home Agent must
belong to a prefix advertised on the home network. In accordance belong to a prefix advertised on the home network. In accordance
with this specification, however, the home address must be configured with this specification, however, the home address must be configured
from a prefix that is served by the Home Agent, not necessarily the from a prefix that is served by the Home Agent, not necessarily the
one on the home network. one on the home network.
If the registration request is valid, the Home Agent checks to see if If the registration request is valid, the Home Agent checks to see
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. If so, the Mobile Network Prefix information
is obtained from the included extensions. For every Mobile Network is obtained from the included extensions, and the Home Address from
Prefix extension included in the registration request, the Home Agent the Home Address field of the UDP header Registration Request. For
MUST perform a check against the Prefix Table. If the check fails or every Mobile Network Prefix extension included in the registration
if the Mobile Router is not authorized for using any of those request, the Home Agent MUST perform a check against the Prefix
prefixes, the Home Agent MUST reject the registration request with Table. If the Prefix Table does not contain at least one entry
Mobile Network Acknowledgement Extension code MOBNET_UNAUTHORIZED. pairing that Home Address to that Mobile Network Prefix then the
On the other hand, if check passes for every requested Mobile Network check fails, otherwise it succeeds.
Prefix, the Home Agent MUST attempt to set up forwarding for all the
Mobile Network Prefixes included in the registration request. If Following this check against the Prefix Table, the Home Agent MUST
forwarding set up fails for any of the prefixes, the Home Agent MUST construct a Registration Reply containing Mobile Network
reject the registration request with Mobile Network Acknowledgement Acknowledgement extensions. For a Mobile Network Prefix for which
Extension code MOBNET_FWDING_SETUP_FAILED. The Home Agent, in this the check was unsuccessfull the Code field in the corresponding
case, MUST NOT forward traffic to any of these prefixes. Note that Mobile Network Acknowledgement extension should be set to
only the Mobile Network Prefix(es) that failed validation or set up MOBNET_UNAUTHORIZED. For a Mobile Network Prefix for which the
procedure are included in the denied Registration Reply with error check was successfull the Code field in the respective Mobile
code HA_MOBNET_ERROR. Network Acknowledgement extensions should be set to 0.
The Home Agent MUST attempt to set up forwarding for each Mobile
Network Prefix extension for which the Prefix Table check was
successfull. If the forwarding setup fails for a particular Mobile
Network Prefix (for reasons like not enough memory available, or
not enough devices available, or other similar) the Code field in
the respective Mobile Network Acknowledgement extension should be
set to MOBNET_FWDING_SETUP_FAILED.
If forwarding and setup was successful for at least one Mobile
Network Prefix then the Code field of the Registration Reply
message should be set to 0. Otherwise that Code should be
HA_MOBNET_ERROR.
If the registration request is sent in implicit mode, i.e., without If the registration request is sent in implicit mode, i.e., without
any Mobile Network Request extension, the Home Agent may use pre- any Mobile Network Request extension, the Home Agent may use pre-
configured mobile network prefix information for the Mobile Router to configured mobile network prefix information for the Mobile Router to
set up forwarding. set up forwarding.
If the Home Agent is updating an existing binding entry for the If the Home Agent is updating an existing binding entry for the
Mobile Router, it MUST check all the prefixes in the registration Mobile Router, it MUST check all the prefixes in the registration
table against the prefixes included in the registration request. If table against the prefixes included in the registration request.
one or more mobile network prefix is missing from the included If one or more mobile network prefix is missing from the included
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(ies) for the Mobile Router or updates an existing binding entry(ies) for the Mobile Router or updates an existing binding
entry(ies) for it and returns a successful registration reply back to entry(ies) for it and returns a successful registration reply back
the Mobile Router or the Foreign Agent (if the registration request to the Mobile Router or the Foreign Agent (if the registration
was received from a Foreign Agent). request was 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
Mobile Router home address, when the Mobile Router home address is the Mobile Router home address, when the Mobile Router home address
derived from the home network. If the 'T' bit is set, the Home Agent is derived from the home network. If the 'T' bit is set, the Home
creates a bi-directional tunnel for the corresponding mobile network Agent creates a bi-directional tunnel for the corresponding mobile
prefixes or updates the existing bi-directional tunnel. This tunnel network prefixes or updates the existing bi-directional tunnel.
is maintained independent of the reverse tunnel for the Mobile Router This tunnel is maintained independent of the reverse tunnel for the
home address itself. 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 the aggregated with the home network prefix and if the Home Agent is the
default router on the home network, the Home Agent does not have to default router on the home network, the Home Agent does not have to
do anything different than normal. The routes for the mobile network do anything different than normal. The routes for the mobile network
prefix are automatically aggregated into the home network prefix. If prefix are automatically aggregated into the home network prefix. If
the Mobile Router updates the mobile network prefix routes via a the Mobile Router updates the mobile network prefix routes via a
dynamic routing protocol, the Home Agent SHOULD propagate the routes dynamic routing protocol, the Home Agent SHOULD propagate the routes
skipping to change at page 14, line 18 skipping to change at page 10, line 51
network prefixes. 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 Agents MUST set the status code in the registration reply to
0 to indicate successful processing of the registration request and 0 to indicate successful processing of the registration request and
successful set up of forwarding for all the mobile network prefixes successful set up of forwarding for all the mobile network prefixes
served by the Mobile Router. The registration reply MUST contain at served by the Mobile Router. The registration reply MUST contain at
least one Mobile Network Acknowledgement extension. least one Mobile Network Acknowledgement extension.
If the Home Agent does not support Mobile Routers, it SHOULD set the
status code in the registration reply to HA_MOBNET_UNSUPPORTED.
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.
skipping to change at page 18, line 17 skipping to change at page 13, line 17
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
----- ------------------------------------------ ----- ------------------------------------------
45 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
----- ------------------------------------------ ----- ------------------------------------------
1 Mobile Network Request Extension TBA Mobile Network Request Extension
2 Explicit Mode Acknowledgement Extension TBA Explicit Mode Acknowledgement Extension
3 Implicit Mode Acknowledgement Extension TBA Implicit Mode Acknowledgement Extension
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 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)
143 Mobile Network Prefix operation error (HA_MOBNET_ERROR) TBA Mobile Network Prefix operation error (HA_MOBNET_ERROR)
144 MR is not supported on HA (HA_MOBNET_UNSUPPORTED) TBA MR operation is not permitted (HA_MOBNET_DISALLOWED)
145 MR 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:
1 Invalid prefix length (MOBNET_INVALID_PREFIX_LEN) TBA Invalid prefix length (MOBNET_INVALID_PREFIX_LEN)
2 MR is not authorized for prefix (MOBNET_UNAUTHORIZED) TBA MR is not authorized for prefix (MOBNET_UNAUTHORIZED)
3 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
11. Acknowledgements 11. Acknowledgements
The authors would like to thank Christophe Janneteau, George The authors would like to thank Christophe Janneteau, George
Popovich, Ty Bekiares, Ganesh Srinivasan and Alpesh Patel for their Popovich, Ty Bekiares, Ganesh Srinivasan, Alpesh Patel, Ryuji
helpful discussions, reviews and comments. Wakikawa, George Tsirtsis and Henrik Levkowetz for their helpful
discussions, reviews and comments.
12. References 12. References
12.1. Normative References 12.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.
[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 12.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.
13. Changelog
From version 00 to 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. 30 change blocks. 
110 lines changed or deleted 136 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/