draft-ietf-mip4-nemo-v4-base-10.txt   draft-ietf-mip4-nemo-v4-base-11.txt 
MIP4 K. Leung MIP4 K. Leung
Internet-Draft G. Dommety Internet-Draft G. Dommety
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: August 21, 2008 V. Narayanan Expires: September 12, 2008 V. Narayanan
Qualcomm, Inc. Qualcomm, Inc.
A. Petrescu A. Petrescu
Motorola Motorola
February 18, 2008 March 11, 2008
Network Mobility (NEMO) Extensions for Mobile IPv4 Network Mobility (NEMO) Extensions for Mobile IPv4
draft-ietf-mip4-nemo-v4-base-10.txt draft-ietf-mip4-nemo-v4-base-11.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 21, 2008. This Internet-Draft will expire on September 12, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes a protocol for supporting Mobile Networks This document describes a protocol for supporting Mobile Networks
between a Mobile Router and a Home Agent by extending the Mobile IPv4 between a Mobile Router and a Home Agent by extending the Mobile IPv4
protocol. A Mobile Router is responsible for the mobility of one or protocol. A Mobile Router is responsible for the mobility of one or
skipping to change at page 2, line 18 skipping to change at page 2, line 18
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Examples of Mobile Networks . . . . . . . . . . . . . . . 3 1.1. Examples of Mobile Networks . . . . . . . . . . . . . . . 3
1.2. Overview of Protocol . . . . . . . . . . . . . . . . . . . 4 1.2. Overview of Protocol . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 8 4. Mobile Network Extensions . . . . . . . . . . . . . . . . . . 8
4.1. Representing a Subnet . . . . . . . . . . . . . . . . . . 8 4.1. Mobile Network Request Extension . . . . . . . . . . . . . 8
4.2. Mobile Network Request Extension . . . . . . . . . . . . . 9 4.2. Mobile Network Acknowledgement Extension . . . . . . . . . 9
4.3. Mobile Network Acknowledgement Extension . . . . . . . . . 10 5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 11
5. Mobile Router Operation . . . . . . . . . . . . . . . . . . . 13 5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 12
5.1. Error Processing . . . . . . . . . . . . . . . . . . . . . 14 5.2. Mobile Router Management . . . . . . . . . . . . . . . . . 12
5.2. Mobile Router Management . . . . . . . . . . . . . . . . . 14 6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 13
6. Home Agent Operation . . . . . . . . . . . . . . . . . . . . . 15 6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 15 6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 14
6.2. Data Structures . . . . . . . . . . . . . . . . . . . . . 16 6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 14
6.2.1. Registration Table . . . . . . . . . . . . . . . . . . 16 6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 14
6.2.2. Prefix Table . . . . . . . . . . . . . . . . . . . . . 16 6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 14
6.3. Mobile Network Prefix Registration . . . . . . . . . . . . 16 6.4. Advertising Mobile Network Reachability . . . . . . . . . 16
6.4. Advertising Mobile Network Reachability . . . . . . . . . 18 6.5. Establishment of Bi-directional Tunnel . . . . . . . . . . 16
6.5. Establishment of Bi-directional Tunnel . . . . . . . . . . 18 6.6. Sending Registration Replies . . . . . . . . . . . . . . . 17
6.6. Sending Registration Replies . . . . . . . . . . . . . . . 18 6.7. Mobile Network Prefix De-registration . . . . . . . . . . 17
6.7. Mobile Network Prefix De-registration . . . . . . . . . . 19 7. Data Forwarding Operation . . . . . . . . . . . . . . . . . . 17
7. Data Forwarding Operation . . . . . . . . . . . . . . . . . . 19 8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . . 18
8. Nested Mobile Networks . . . . . . . . . . . . . . . . . . . . 20 9. Routing Protocol between Mobile Router and Home Agent . . . . 18
9. Routing Protocol between Mobile Router and Home Agent . . . . 20 10. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. Security Considerations . . . . . . . . . . . . . . . . . . . 21 10.1. Security when Dynamic Routing Protocol is Used . . . . . . 20
10.1. Security when Dynamic Routing Protocol is Used . . . . . . 22 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 13.1. Normative References . . . . . . . . . . . . . . . . . . . 23
13.1. Normative References . . . . . . . . . . . . . . . . . . . 25 13.2. Informative References . . . . . . . . . . . . . . . . . . 24
13.2. Informative References . . . . . . . . . . . . . . . . . . 26 Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . . 24
Appendix A. ChangeLog . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 28
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 Intellectual Property and Copyright Statements . . . . . . . . . . 30
Intellectual Property and Copyright Statements . . . . . . . . . . 32
1. Introduction 1. Introduction
This document describes network mobility extensions to the Mobile This document describes network mobility extensions to the Mobile
IPv4 protocol. The goal of introducing these extensions is to IPv4 protocol. The goal of introducing these extensions is to
acommodate mobility scenarios where groups of hosts and routers move acommodate mobility scenarios where groups of hosts and routers move
homogeneously (as a whole). It is required that all hosts and homogeneously (as a whole). It is required that all hosts and
routers in a mobile network be able to run applications connecting to routers in a mobile network be able to run applications connecting to
the Internet, and to be reachable from the Internet. the Internet, and to be reachable from the Internet.
skipping to change at page 8, line 13 skipping to change at page 8, line 13
Mobile Routers to be on it. Mobile Routers to be on it.
o The Local Fixed Nodes on a mobile network should be able to o The Local Fixed Nodes on a mobile network should be able to
execute their sessions without running themselves Mobile IP execute their sessions without running themselves Mobile IP
stacks. The Mobile Router managing the LFNs' mobile network is stacks. The Mobile Router managing the LFNs' mobile network is
'hiding' mobility events like the changes of the Care-of Address 'hiding' mobility events like the changes of the Care-of Address
from the Local Fixed Nodes in that mobile network. from the Local Fixed Nodes in that mobile network.
4. Mobile Network Extensions 4. Mobile Network Extensions
4.1. Representing a Subnet 4.1. Mobile Network Request Extension
Since the protocol extensions presented in this document concentrate
on treatment of prefixes, subnets and network masks it is important
to choose an all-encompassing wire representation of subnets, as
generic as possible.
A subnet can easily be represented as address/prefix length, as in
192.0.2.0/24. This is interpreted as the subnet being the first
leftmost 24 bits of the address 192.0.2.0, i.e. 192.0.2. This
representation corresponds to an underlying forwarding system which
uses longest-prefix match rules. It is typically in widespread
deployment in the Internet.
In a Mobile Network Extension, this representation is expressed by
the tuple of Prefix and Prefix Length fields.
On another hand, some forwarding systems don't use longest-prefix
match rules. In these cases it is important to provide the more
generic way of representing subnets by using non-contiguous sets of
1bits as netmasks. For example, 255.255.0.255 is a perfectly legal
netmask which, when applied to an address like 192.0.2.1 gives the
network part 192.0.x.1, the third 'x' byte acting alone as the host
part.
In a Mobile Network Extension, this non-contiguous netmask
representation is expressed by the tuple of Prefix and Optional
Netmask fields (Prefix Length field being ignored).
The two representation methods (address/prefix and address/netmask)
are alternative and only one method of representation is used by a
Mobile Network Extension.
Representing the subnet as address/prefix has the advantage of a more
compact encoding (40bits) whereas the address/netmask requires
64bits. Hence it is suggested as a default. However, representing
the subnet as address/netmask gives more applicability of NEMOv4
extensions to forwarding systems where more complex forwarding
schemes are used.
4.2. 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 the
Mobile Network Prefixes during registration. The Registration 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 RFC 3344 [RFC3344]. When several Mobile Networks are context of RFC 3344 [RFC3344]. When several Mobile Networks are
needed to be registered, each is included in a separate Mobile needed to be registered, each is included in a separate Mobile
Network Request extension, with its own Type, Length, Sub-Type, Network Request extension, with its own Type, Length, Sub-Type,
Prefix Length, Prefix and optionally the Optional Netmask fields. Prefix Length and Prefix. A Mobile Network Request extension is
For a discussion of the subnet encoding see Section 4.1. A Mobile encoded in Type-Length-Value (TLV) format and respects the following
Network Request extension is encoded in Type-Length-Value (TLV) ordering:
format and respects the following ordering:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optional Netmask |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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:
Decimal 6 or decimal 10, not any other. If the masking is Decimal 6.
expressed as Prefix/Prefix Length (e.g. 192.0.2.1/24), the
value of this Length field is decimal 6 and the Optional
Netmask field is absent. If the masking is expressed as
Prefix and Netmask (e.g. 192.0.2.1 255.255.0.255) then the
value of this Length field is decimal 10, the Optional
Netmask field is present and the value of the Prefix Length
field is set to all-zero by sender and ignored by receiver.
Sub-Type: Sub-Type:
TBA (Mobile Network Request) TBA (Mobile Network Request)
Prefix Length: Prefix Length:
8-bit unsigned integer indicating the number of leftmost bits 8-bit unsigned integer indicating the number of leftmost bits
covering the network part of the address contained in the covering the network part of the address contained in the
Prefix field. If the Optional Netmask field is present then Prefix field.
this field is set to all-zero by sender and ignored by
receiver.
Prefix: Prefix:
32-bit unsigned integer in network byte-order containing an 32-bit unsigned integer in network byte-order containing an
IPv4 address. If the Optional Netmask field is absent then IPv4 address whose leftmost Prefix Length bits make up the
the first Prefix Length bits make up the Mobile Network Mobile Network Prefix.
Prefix. Otherwise the Mobile Network Prefix is obtained by
masking this IPv4 address with the value of the Optional
Netmask field.
Optional Netmask:
32-bit unsigned integer in network byte-order containing an
IPv4 netmask. For example '255.255.0.255'. This field is
present when the subnet masking needs to be expressed as a
non-contiguous set of 1 bits. Otherwise it is absent. If
the Optional Netmask is present then the value of the field
Prefix Length is set to all-zero by sender and ignored by
receiver.
4.3. 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 RFC 3344 [RFC3344]. For Implicit defined by or in the context of RFC 3344 [RFC3344]. For Implicit
Mode, the Mobile Network Acknowledgement informs the Mobile Router Mode, the Mobile Network Acknowledgement informs the Mobile Router
the prefixes for which the Home Agent sets up forwarding with respect the prefixes for which the Home Agent sets up forwarding with respect
to this Mobile Router. Policies such as permitting only traffic from to this Mobile Router. Policies such as permitting only traffic from
these Mobile Networks to be tunneled to the Home Agent may be applied these Mobile Networks to be tunneled to the Home Agent may be applied
by the Mobile Router. For Explicit Mode, when several Mobile by the Mobile Router. For Explicit Mode, when several Mobile
Networks are needed to be acknowledged explicitly, each is included Networks are needed to be acknowledged explicitly, each is included
in a separate Mobile Network Acknowledgement extension, with its own in a separate Mobile Network Acknowledgement extension, with its own
Type, Sub-Type, Length, Prefix, Prefix Length and optionally the Type, Sub-Type, Length, Prefix and Prefix Length fields. At least
Optional Netmask fields. For a discussion of the subnet encoding see one Mobile Network Acknowledgement extension MUST be in a successful
Section 4.1. 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 Mobile Network Request extension was processed, thereby not skipped by the
Router that the Mobile Network Request extension was processed, Home Agent.
thereby not skipped by the Home Agent.
A Registration Reply may contain any non-zero number of Explicit Mode A Registration Reply may contain any non-zero number of Explicit Mode
and Implicit Mode Acknowledgements sub-types. Both sub-types can be and Implicit Mode Acknowledgements sub-types. Both sub-types can be
present in a single Registration Reply. A Mobile Network present in a single Registration Reply. A Mobile Network
Acknowledgement extension is encoded in Type-Length-Value (TLV) Acknowledgement extension is encoded in Type-Length-Value (TLV)
format. When the registration is denied with Code HA_MOBNET_ERROR format. When the registration is denied with Code HA_MOBNET_ERROR
(Code field in the Registration Reply), the Code field in the (Code field in the Registration Reply), the Code field in the
included Mobile Network Extension provides the reason for the included Mobile Network Extension provides the reason for the
failure. 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...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
...Prefix | Optional Netmask... ...Prefix |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
...Optional Netmask |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
TBA Mobile Network Extension (skippable type range to be TBA Mobile Network Extension (skippable type range to be
assigned by IANA). assigned by IANA).
Length: Length:
Decimal 8 or decimal 12, not any other. If the masking is Decimal 8.
expressed as Prefix/Prefix Length (e.g. 192.0.2.1/24), the
value of this Length field is decimal 8 and the Optional
Netmask field is absent. If the masking is expressed as
Prefix and Netmask (e.g. 192.0.2.1 255.255.0.255) then the
value of this Length field is decimal 12, the Optional
Netmask field is present and the value of the Prefix Length
field set to all-zero by sender and ignored by receiver.
Sub-Type: Sub-Type:
TBA (Explicit Mode Acknowledgement) TBA (Explicit Mode Acknowledgement)
TBA (Implicit Mode Acknowledgement) TBA (Implicit Mode Acknowledgement)
Code: Code:
Value indicating success or failure: Value indicating success or failure:
skipping to change at page 12, line 26 skipping to change at page 10, line 47
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)
Prefix Length: Prefix Length:
8-bit unsigned integer indicating the number of leftmost bits 8-bit unsigned integer indicating the number of leftmost bits
covering the network part of the address contained in the covering the network part of the address contained in the
Prefix field. If the Optional Netmask field is present then Prefix field.
this field is set to all-zero by sender and ignored by
receiver.
Reserved: Reserved:
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. If the Optional Netmask field is absent then IPv4 address whose leftmost Prefix Length bits make up the
the first Prefix Length bits make up the Mobile Network Mobile Network Prefix.
Prefix. Otherwise the Mobile Network Prefix is obtained by
masking this IPv4 address with the value of the Optional
Netmask field.
Optional Netmask:
32-bit unsigned integer in network byte-order containing an
IPv4 netmask. For example '255.255.0.255'. This field is
present when the subnet masking needs to be expressed as a
non-contiguous set of 1 bits. Otherwise it is absent. If
the Optional Netmask is present then the value of the field
Prefix Length is set to all-zero by sender and ignored by
receiver.
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 of
a Mobile Node, as set in RFC 3344 [RFC3344]. In addition to a Mobile Node, as set in RFC 3344 [RFC3344]. In addition to
maintaining mobility bindings for its Home Address, the Mobile maintaining mobility bindings for its Home Address, the Mobile
Router, together with the Home Agent, maintains forwarding Router, together with the Home Agent, maintains forwarding
information for the Mobile Network Prefix(es) assigned to the Mobile information for the Mobile Network Prefix(es) assigned to the Mobile
Router. Router.
skipping to change at page 19, line 9 skipping to change at page 17, line 17
The Home Agent MUST set the status code in the registration reply to The Home Agent 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 at least one mobile network successful set up of forwarding for at least one mobile network
prefixes served by the Mobile Router. The registration reply MUST prefixes served by the Mobile Router. The registration reply MUST
contain at 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 or more If the Home Agent is unable to set up forwarding for one or 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 (and the Optional Netmask field is absent) or greater length is zero or greater than decimal 32, the status Code MUST be
than decimal 32, the status Code MUST be set to set to MOBNET_INVALID_PREFIX_LEN.
MOBNET_INVALID_PREFIX_LEN.
If the Mobile Router is not authorized to forward packets to a mobile If the Mobile Router is not authorized to forward packets to a mobile
network prefixes included in the request, the Home Agent MUST set the network prefixes included in the request, the Home Agent MUST set the
Code to MOBNET_UNAUTHORIZED. Code to MOBNET_UNAUTHORIZED.
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
skipping to change at page 26, line 28 skipping to change at page 24, line 28
Appendix A. ChangeLog Appendix A. ChangeLog
[RFC Editor: please remove this section prior to publication. (said [RFC Editor: please remove this section prior to publication. (said
IESG member Russ Housley on 6th of February 2008: "Please delete IESG member Russ Housley on 6th of February 2008: "Please delete
Appendix A before publication as an RFC.")] Appendix A before publication as an RFC.")]
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-10.txt to
draft-ietf-mip4-nemo-v4-base-11.txt:
o Based on David Ward comment removed the section discussing on non-
contiguous netmasks, as well as the Optional Netmask fields (but
still kept the prefixlen-based contiguous netmasks.)
From draft-ietf-mip4-nemo-v4-base-09.txt to From draft-ietf-mip4-nemo-v4-base-09.txt to
draft-ietf-mip4-nemo-v4-base-10.txt: draft-ietf-mip4-nemo-v4-base-10.txt:
o Changed "192.168.1.1" notation to "192.0.2.0" documentation style o Changed "192.168.1.1" notation to "192.0.2.0" documentation style
addresses, as suggested by idnits. addresses, as suggested by idnits.
From draft-ietf-mip4-nemo-v4-base-08.txt to From draft-ietf-mip4-nemo-v4-base-08.txt to
draft-ietf-mip4-nemo-v4-base-09.txt, following IANA and IESG draft-ietf-mip4-nemo-v4-base-09.txt, following IANA and IESG
comments: comments:
 End of changes. 19 change blocks. 
145 lines changed or deleted 60 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/