draft-ietf-mip4-nemov4-dynamic-01.txt   draft-ietf-mip4-nemov4-dynamic-02.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: May 9, 2008 Qualcomm Expires: March 2, 2009 Qualcomm
K. Leung K. Leung
Cisco Cisco
November 6, 2007 August 29, 2008
Dynamic Prefix Allocation for NEMOv4 Dynamic Prefix Allocation for NEMOv4
draft-ietf-mip4-nemov4-dynamic-01.txt draft-ietf-mip4-nemov4-dynamic-02.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 May 9, 2008. This Internet-Draft will expire on March 2, 2009.
Copyright Notice
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
skipping to change at page 4, line 7 skipping to change at page 4, line 7
Intellectual Property and Copyright Statements . . . . . . . . . . 11 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 [I-D.ietf-mip4-nemo-v4-base] defines The base NEMOv4 specification [RFC5177] defines extensions to Mobile
extensions to Mobile IPv4 [RFC3344] for mobile networks. This IPv4 [RFC3344] for mobile networks. This specification adds support
specification adds support for dynamic allocation of mobile prefixes for dynamic allocation of mobile prefixes by the home agent.
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
[I-D.ietf-mip4-nemo-v4-base] defines that the prefix field of the [RFC5177] defines that the prefix field of the mobile network request
mobile network request extension can not be set to zero. extension can not be set to zero. This mechanism works only in
combination with the explicit mode of operation defined in [RFC5177].
According to this specification, however, a mobile client MAY include According to this specification, a mobile client MAY include one or
one or more mobile network request extensions with the prefix field more mobile network request extensions with the prefix field set to
set to zero. Such mobile network request extensions indicate that zero. Such mobile network request extensions indicate that the
the mobile client requests mobile network prefix(es) to be assigned mobile client requests mobile network prefix(es) to be assigned to it
to it by the home agent. In this case, the mobile client MAY set the 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 [I-D.ietf-mip4-nemo-v4-base]. If as defined in MIPv4 [RFC3344] and [RFC5177]. If one or more network
one or more network acknowledgement extension are included with the acknowledgement extension are included with the Code field set to
Code field set to "Success" the mobile client SHOULD treat the "Success" the mobile client SHOULD treat the prefixes in the
prefixes in the corresponding prefix fields as allocated prefixes and corresponding prefix fields as allocated prefixes and create the
create the appropriate bindings as defined in appropriate bindings as defined in [RFC5177].
[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 network acknowledgement
formed request", it may use it as a hint that the home agent does not extensiona including Code field set to 1 "invalid prefix", it may use
support dynamic prefix allocation. it as a hint that the home agent does not support dynamic prefix
allocation.
[Ed. Note: alternatively [I-D.ietf-mip4-nemo-v4-base] should define
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 [I-D.ietf-mip4-nemo-v4-base] with the prefix field set to extension [RFC5177] with the prefix field set to the prefix allocated
the prefix allocated to the mobile client. The length of that prefix to the mobile client. The length of that prefix is at the discretion
is at the discretion of the home agent. The home agent MAY take into of the home agent. The home agent MAY take into account the prefix
account the prefix length hint if one is included in the mobile length hint if one is included in the mobile network request
network request extension. Once the home agent allocates a prefix it extension. Once the home agent allocates a prefix it MUST maintain
MUST maintain the prefix registration table as defined in the prefix registration table as defined in [RFC5177]. Alternatively
[I-D.ietf-mip4-nemo-v4-base]. Alternatively the home agent MAY the home agent MAY return a mobile network acknowledgement extension
return a mobile network acknowledgement extension with the Code field with the Code field set to one of the negative codes defined in
set to one of the negative codes defined in [RFC5177].
[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
[RFC3344]. In other words the home address field of the registration [RFC5177]. 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 [I-D.ietf-mip4-nemo-v4-base]. registration table as defined in [RFC5177]. The lifetime of the
allocated prefix will be equal to the lifetime of the binding cache
entry
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. Otherwise, as
Otherwise, as defined in MIPv4 [RFC3344] and NAI [RFC2794], the NAI defined in the NAI extension [RFC2794] of MIPv4 [RFC2794], the NAI
[RFC2794] extension needs to be included in the registration request, extension needs to be included in the registration request, in which
in which case the same extension SHOULD be used to identify the case the same extension SHOULD be used to identify the mobile client
mobile client for prefix allocation purposes. 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 requirements of MIPv4 [RFC3344], NAI [RFC2794] and [RFC5177].
[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. IANA Considerations 5. IANA Considerations
This document has no actions for IANA This document has no actions for IANA
6. Normative References 6. Normative References
[I-D.ietf-mip4-nemo-v4-base]
Leung, K., Dommety, G., Narayanan, V., and A. Petrescu,
"Network Mobility (NEMO) Extensions for Mobile IPv4",
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.
[RFC5177] Leung, K., Dommety, G., Narayanan, V., and A. Petrescu,
"Network Mobility (NEMO) Extensions for Mobile IPv4",
RFC 5177, April 2008.
Authors' Addresses Authors' Addresses
George Tsirtsis George Tsirtsis
Qualcomm Qualcomm
Phone: +908-443-8174 Email: tsirtsis@googlemail.com
Email: tsirtsis@qualcomm.com
Vincent Park Vincent Park
Qualcomm Qualcomm
Phone: +908-947-7084 Phone: +908-947-7084
Email: vpark@qualcomm.com Email: vpark@qualcomm.com
Vidya Narayana Vidya Narayana
Qualcomm Qualcomm
skipping to change at page 11, line 7 skipping to change at page 11, line 7
Email: vidyan@qualcomm.com Email: vidyan@qualcomm.com
Kent Leung Kent Leung
Cisco Cisco
Phone: +408-526-5030 Phone: +408-526-5030
Email: kleung@cisco.com Email: kleung@cisco.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 11, line 44 skipping to change at line 230
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 19 change blocks. 
61 lines changed or deleted 50 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/