draft-ietf-mip4-nemov4-dynamic-00.txt   draft-ietf-mip4-nemov4-dynamic-01.txt 
Network Working Group G. Tsirtsis Network Working Group G. Tsirtsis
Internet-Draft V. Park Internet-Draft V. Park
Intended status: Standards Track V. Narayanan Intended status: Standards Track V. Narayanan
Expires: September 20, 2007 Qualcomm Expires: May 9, 2008 Qualcomm
K. Leung K. Leung
Cisco Cisco
March 19, 2007 November 6, 2007
Dynamic Prefix Allocation for NEMOv4 Dynamic Prefix Allocation for NEMOv4
draft-ietf-mip4-nemov4-dynamic-00.txt draft-ietf-mip4-nemov4-dynamic-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 36 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 September 20, 2007. This Internet-Draft will expire on May 9, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
The base NEMOv4 specification defines extensions to Mobile IPv4 for The base NEMOv4 specification defines extensions to Mobile IPv4 for
mobile networks. This specification defines a dynamic prefix mobile networks. This specification defines a dynamic prefix
allocation mechanism. allocation mechanism.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Dynamic Mobile Prefix allocation . . . . . . . . . . . . . . . 5 3. Dynamic Mobile Prefix allocation . . . . . . . . . . . . . . . 5
3.1. Mobile Client Considerations . . . . . . . . . . . . . . . 5 3.1. Mobile Client Considerations . . . . . . . . . . . . . . . 5
3.2. Home Agent Considerations . . . . . . . . . . . . . . . . 5 3.2. Home Agent Considerations . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. Normative References . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Normative References . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . . . . 11
1. Requirements notation 1. Requirements notation
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].
2. Introduction 2. Introduction
The base NEMOv4 specification [NEMOv4] defines extensions to Mobile The base NEMOv4 specification [I-D.ietf-mip4-nemo-v4-base] defines
IPv4 [RFC3344] for mobile networks. This specification adds support extensions to Mobile IPv4 [RFC3344] for mobile networks. This
for dynamic allocation of mobile prefixes by the home agent. specification adds support for dynamic allocation of mobile prefixes
by the home agent.
3. Dynamic Mobile Prefix allocation 3. Dynamic Mobile Prefix allocation
The following extension is defined according to this specification. The following extension is defined according to this specification.
3.1. Mobile Client Considerations 3.1. Mobile Client Considerations
[NEMOv4] defines that the prefix field of the mobile network request [I-D.ietf-mip4-nemo-v4-base] defines that the prefix field of the
extension can not be set to zero. mobile network request extension can not be set to zero.
According to this specification, however, a mobile client MAY include According to this specification, however, a mobile client MAY include
one or more mobile network request extensions with the prefix field one or more mobile network request extensions with the prefix field
set to zero. Such mobile network request extensions indicate that set to zero. Such mobile network request extensions indicate that
the mobile client requests mobile network prefix(es) to be assigned the mobile client requests mobile network prefix(es) to be assigned
to it by the home agent. In this case, the mobile client MAY set the to it by the home agent. In this case, the mobile client MAY set the
prefix length field of such extensions to zero or to a length of its prefix length field of such extensions to zero or to a length of its
choice as a hint to the home agent. According to this specification, choice as a hint to the home agent. According to this specification,
mobile network request extensions with the prefix field set to zero mobile network request extensions with the prefix field set to zero
MAY be included in a registration request message either during MAY be included in a registration request message either during
initial registration or during a subsequent registration. initial registration or during a subsequent registration.
When a mobile client receives a registration reply it MUST process it When a mobile client receives a registration reply it MUST process it
as defined in MIPv4 [RFC3344] and [NEMOv4]. If one or more network as defined in MIPv4 [RFC3344] and [I-D.ietf-mip4-nemo-v4-base]. If
acknowledgement extension are included with the Code field set to one or more network acknowledgement extension are included with the
"Success" the mobile client SHOULD treat the prefixes in the Code field set to "Success" the mobile client SHOULD treat the
corresponding prefix fields as allocated prefixes and create the prefixes in the corresponding prefix fields as allocated prefixes and
appropriate bindings as defined in [NEMOv4]. create the appropriate bindings as defined in
[I-D.ietf-mip4-nemo-v4-base].
If in response to a registration request with a mobile network If in response to a registration request with a mobile network
request extension with the prefix field set to zero, a mobile client request extension with the prefix field set to zero, a mobile client
receives a registration reply with a Code field set to 70 "poorly receives a registration reply with a Code field set to 70 "poorly
formed request", it may use it as a hint that the home agent does not formed request", it may use it as a hint that the home agent does not
support dynamic prefix allocation. support dynamic prefix allocation.
[Ed. Note: alternatively [NEMOv4] should define an appropriate Code [Ed. Note: alternatively [I-D.ietf-mip4-nemo-v4-base] should define
in the Mobile Network Acknowledgment extension e.g., "Bad Prefix" an appropriate Code in the Mobile Network Acknowledgment extension
e.g., "Bad Prefix"
3.2. Home Agent Considerations 3.2. Home Agent Considerations
A home agent receiving a mobile network request extension with the A home agent receiving a mobile network request extension with the
prefix field set to zero MAY return a mobile network acknowledgement prefix field set to zero MAY return a mobile network acknowledgement
extension [NEMOv4] with the prefix field set to the prefix allocated extension [I-D.ietf-mip4-nemo-v4-base] with the prefix field set to
to the mobile client. The length of that prefix is at the discretion the prefix allocated to the mobile client. The length of that prefix
of the home agent. The home agent MAY take into account the prefix is at the discretion of the home agent. The home agent MAY take into
length hint if one is included in the mobile network request account the prefix length hint if one is included in the mobile
extension. Once the home agent allocates a prefix it MUST maintain network request extension. Once the home agent allocates a prefix it
the prefix registration table as defined in [NEMOv4]. Alternatively MUST maintain the prefix registration table as defined in
the home agent MAY return a mobile network acknowledgement extension [I-D.ietf-mip4-nemo-v4-base]. Alternatively the home agent MAY
with the Code field set to one of the negative codes defined in return a mobile network acknowledgement extension with the Code field
[NEMOv4]. set to one of the negative codes defined in
[I-D.ietf-mip4-nemo-v4-base].
Dynamic mobile prefix allocation as defined in this specification MAY Dynamic mobile prefix allocation as defined in this specification MAY
be combined with dynamic home address allocation as defined in MIPv4 be combined with dynamic home address allocation as defined in MIPv4
[RFC3344]. In other words the home address field of the registration [RFC3344]. In other words the home address field of the registration
request message MAY be set to zero while the message also includes request message MAY be set to zero while the message also includes
one or more mobile network request extensions with the prefix field one or more mobile network request extensions with the prefix field
also set to zero. also set to zero.
Once the home agent allocates a prefix it MUST maintain the prefix Once the home agent allocates a prefix it MUST maintain the prefix
registration table as defined in [NEMOv4]. registration table as defined in [I-D.ietf-mip4-nemo-v4-base].
For dynamic prefix allocation the mobile client's home address MAY be For dynamic prefix allocation the mobile client's home address MAY be
used to identify the client if it is not set to zero. If the home used to identify the client if it is not set to zero. If the home
Otherwise, as defined in MIPv4 [RFC3344] and NAI [RFC2794], the NAI Otherwise, as defined in MIPv4 [RFC3344] and NAI [RFC2794], the NAI
[RFC2794] extension needs to be included in the registration request, [RFC2794] extension needs to be included in the registration request,
in which case the same extension SHOULD be used to identify the in which case the same extension SHOULD be used to identify the
mobile client for prefix allocation purposes. mobile client for prefix allocation purposes.
4. Security Considerations 4. Security Considerations
This specification operates in the security constraints and This specification operates in the security constraints and
requirements of MIPv4 [RFC3344], NAI [RFC2794] and [NEMOv4]. requirements of MIPv4 [RFC3344], NAI [RFC2794] and
[I-D.ietf-mip4-nemo-v4-base].
Home agent implementations SHOULD take steps to prevent address Home agent implementations SHOULD take steps to prevent address
exhaustion attacks. One way to limit the effectiveness of such an exhaustion attacks. One way to limit the effectiveness of such an
attack is to limit the number and size of prefixes any one mobile attack is to limit the number and size of prefixes any one mobile
router can be allocated. router can be allocated.
5. Normative References 5. IANA Considerations
This document has no actions for IANA
6. Normative References
[I-D.ietf-mip4-nemo-v4-base] [I-D.ietf-mip4-nemo-v4-base]
Leung, K., "IPv4 Network Mobility (NEMO) Protocol", Leung, K., Dommety, G., Narayanan, V., and A. Petrescu,
draft-ietf-mip4-nemo-v4-base-00 (work in progress), "Network Mobility (NEMO) Extensions for Mobile IPv4",
March 2007. draft-ietf-mip4-nemo-v4-base-06 (work in progress),
October 2007.
[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.
 End of changes. 15 change blocks. 
34 lines changed or deleted 46 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/