draft-ietf-mip4-nemov4-dynamic-06.txt   rfc6626.txt 
Network Working Group G. Tsirtsis Internet Engineering Task Force (IETF) G. Tsirtsis
Internet-Draft V. Park Request for Comments: 6626 V. Park
Intended status: Standards Track V. Narayanan Updates: 5177 V. Narayanan
Expires: August 26, 2012 Qualcomm Category: Standards Track Qualcomm
K. Leung ISSN: 2070-1721 K. Leung
Cisco Cisco
February 23, 2012 May 2012
Dynamic Prefix Allocation for NEMOv4 Dynamic Prefix Allocation for
draft-ietf-mip4-nemov4-dynamic-06.txt Network Mobility for Mobile IPv4 (NEMOv4)
Abstract Abstract
The base NEMOv4 specification defines extensions to Mobile IPv4 for The base Network Mobility for Mobile IPv4 (NEMOv4) specification
mobile networks. This specification defines a dynamic prefix defines extensions to Mobile IPv4 for mobile networks. This
allocation mechanism. specification defines a dynamic prefix allocation mechanism for
NEMOv4.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on August 26, 2012. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6626.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Notation ...........................................2
3. Dynamic Mobile Prefix allocation . . . . . . . . . . . . . . . 5 3. Dynamic Mobile Prefix Allocation ................................2
3.1. Mobile Client Considerations . . . . . . . . . . . . . . . 5 3.1. Mobile Client Considerations ...............................2
3.2. Home Agent Considerations . . . . . . . . . . . . . . . . 5 3.2. Home Agent Considerations ..................................3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations .........................................4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations .............................................4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements ................................................4
7. Normative References . . . . . . . . . . . . . . . . . . . . . 10 7. Normative References ............................................4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. Introduction 1. Introduction
The base NEMOv4 specification [RFC5177] defines extensions to Mobile The base NEMOv4 specification [RFC5177] defines extensions to Mobile
IPv4 [RFC5944] for mobile networks. This specification adds support IPv4 [RFC5944] for mobile networks. This specification adds support
for dynamic allocation of mobile prefixes by the home agent. for dynamic allocation of mobile prefixes by the home agent.
3. Dynamic Mobile Prefix allocation 2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
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
According to this specification, the Prefix field of the Mobile According to this specification, the Prefix field of the Mobile
Network Request Extension MUST be set to zero to indicate that that Network Request extension MUST be set to zero to indicate that the
the Mobile Router requests mobile network prefix(es) to be assigned Mobile Router requests mobile network prefix(es) be assigned to it by
to it by the home agent. In this case, the Mobile Router MAY set the the home agent. In this case, the Mobile Router MAY set the prefix
prefix length field of such extensions to zero or to a length of its length field of such extensions to zero or to a length of its choice
choice as a hint to the home agent. According to this specification, as a hint to the home agent. According to this specification, Mobile
mobile network request extensions with the prefix field set to zero Network Request extensions with the Prefix field set to zero MAY be
MAY be included in a registration request message either during included in a registration request message either during initial
initial registration or during a subsequent registration. registration or during a subsequent registration.
When a Mobile Router receives a registration reply it MUST process it When a Mobile Router receives a registration reply, it MUST process
as defined in Mobile IPv4 [RFC5944] and [RFC5177]. If one or more it as defined in Mobile IPv4 [RFC5944] and [RFC5177]. If one or more
network acknowledgement extension are included with the Code field network acknowledgement extensions are included with the Code field
set to "Success" the Mobile Router SHOULD treat the prefixes in the set to "Success", the Mobile Router SHOULD treat the prefixes in the
corresponding prefix fields as allocated prefixes and create the corresponding Prefix fields as allocated prefixes and create the
appropriate bindings as defined in [RFC5177]. appropriate bindings as defined in [RFC5177].
If in response to a registration request with a mobile network In response to a registration request with a Mobile Network Request
request extension with the prefix field set to zero, a Mobile Router extension with the Prefix field set to zero, if a Mobile Router
receives a registration reply with a network acknowledgement receives a registration reply with a network acknowledgement
extension including Code field set to 1 "invalid prefix", it may use extension including Code field set to 1 "invalid prefix", it may use
it as a hint that the home agent does not support dynamic prefix it as a hint that the home agent does not support dynamic prefix
allocation. allocation.
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 [RFC5177] with the prefix field set to the prefix allocated extension [RFC5177] with the Prefix field set to the prefix allocated
to the Mobile Router. The length of that prefix is at the discretion to the Mobile Router. The length of that prefix is at the discretion
of the home agent. The home agent MAY take into account the prefix of the home agent. The home agent MAY take into account the prefix
length hint if one is included in the mobile network request length hint if one is included in the Mobile Network Request
extension. Once the home agent allocates a prefix it MUST maintain extension. Once the home agent allocates a prefix, it MUST maintain
the prefix registration table as defined in [RFC5177]. Alternatively the prefix registration table as defined in [RFC5177].
the home agent MAY return a mobile network acknowledgement extension Alternatively, the home agent MAY return a Mobile Network
with the Code field set to one of the negative codes defined in Acknowledgement extension with the Code field set to one of the
[RFC5177]. negative codes defined in [RFC5177].
Dynamic mobile prefix allocation as defined in this specification MAY Dynamic mobile prefix allocation, as defined in this specification,
be combined with dynamic home address allocation as defined in MAY be combined with dynamic home address allocation, as defined in
[RFC5177]. In other words the home address field of the registration [RFC5177]. In other words, the home address field of the
request message MAY be set to zero while the message also includes registration request message MAY be set to zero while the message
one or more mobile network request extensions with the prefix field also includes one or more Mobile Network Request extensions with the
also set to zero. Prefix field 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 [RFC5177]. The lifetime of the registration table as defined in [RFC5177]. The lifetime of the
allocated prefix will be equal to the lifetime of the binding cache allocated prefix will be equal to the lifetime of the binding cache
entry. The Mobile Router may request for multiple mobile network entry. The Mobile Router may request for multiple mobile network
prefixes to be assigned by the home agent. For a Mobile Network prefixes to be assigned by the home agent. For a Mobile Network
Prefix for which the assignment was unsuccessful, the Code field in Prefix for which the assignment was unsuccessful, the Code field in
the corresponding Mobile Network Acknowledgement extension should be the corresponding Mobile Network Acknowledgement extension should be
set to MOBNET_UNASSIGNED. set to 4 (MOBNET_UNASSIGNED).
For dynamic prefix allocation the Mobile Router's home address MAY be For dynamic prefix allocation, the Mobile Router's home address MAY
used to identify the client if it is not set to zero. Otherwise, as be used to identify the client if it is not set to zero. Otherwise,
defined in the NAI extension [RFC2794] of Mobile IPv4 [RFC2794], the as defined in the Network Access Identifier (NAI) extension [RFC2794]
NAI extension needs to be included in the registration request, in of Mobile IPv4 [RFC2794], the NAI extension needs to be included in
which case the same extension SHOULD be used to identify the Mobile the registration request, in which case the same extension SHOULD be
Router for prefix allocation purposes. used to identify the Mobile Router 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 Mobile IPv4 [RFC5944], NAI [RFC2794] and [RFC5177]. requirements of Mobile IPv4 [RFC5944], NAI [RFC2794], and [RFC5177].
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
A new Code Value for the Mobile Network Acknowledgement Extension: 4 A new value has been assigned in the Mobile Network Acknowledgement
(Home Agent cannot assign a mobile network prefix - Extension registry: 4 - Home Agent cannot assign a mobile network
MOBNET_UNASSIGNED). prefix (MOBNET_UNASSIGNED).
6. Acknowledgements 6. Acknowledgements
The authors would like to thank Pete McCann, Alexandru Petrescu, The authors would like to thank Pete McCann, Alexandru Petrescu,
Ralph Droms, and Jari Arkko for their reviews and comments. Ralph Droms, and Jari Arkko for their reviews and comments.
7. Normative References 7. 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.
skipping to change at page 11, line 10 skipping to change at page 5, line 10
RFC 5177, April 2008. RFC 5177, April 2008.
[RFC5944] Perkins, C., "IP Mobility Support for IPv4, Revised", [RFC5944] Perkins, C., "IP Mobility Support for IPv4, Revised",
RFC 5944, November 2010. RFC 5944, November 2010.
Authors' Addresses Authors' Addresses
George Tsirtsis George Tsirtsis
Qualcomm Qualcomm
Email: tsirtsis@googlemail.com EMail: tsirtsis@googlemail.com
Vincent Park Vincent Park
Qualcomm Qualcomm
Phone: +908-947-7084 Phone: +908-443-8141
Email: vpark@qualcomm.com EMail: vpark@qualcomm.com
Vidya Narayana Vidya Narayana
Qualcomm Qualcomm
Phone: +858-845-2483 Phone: +858-845-2483
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
 End of changes. 27 change blocks. 
90 lines changed or deleted 87 lines changed or added

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