draft-ietf-mip4-nemov4-dynamic-04.txt   draft-ietf-mip4-nemov4-dynamic-05.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: October 2, 2011 Qualcomm Expires: October 30, 2011 Qualcomm
K. Leung K. Leung
Cisco Cisco
March 31, 2011 April 28, 2011
Dynamic Prefix Allocation for NEMOv4 Dynamic Prefix Allocation for NEMOv4
draft-ietf-mip4-nemov4-dynamic-04.txt draft-ietf-mip4-nemov4-dynamic-05.txt
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.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on October 2, 2011. This Internet-Draft will expire on October 30, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Normative References . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Normative References . . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 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 [RFC5177] defines extensions to Mobile The base NEMOv4 specification [RFC5177] defines extensions to Mobile
IPv4 [RFC3344] 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 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
[RFC5177] defines that the prefix field of the mobile network request [RFC5177] defines that the prefix field of the mobile network request
extension can not be set to zero. This mechanism works only in extension can not be set to zero. This mechanism works only in
combination with the explicit mode of operation defined in [RFC5177]. combination with the explicit mode of operation defined in [RFC5177].
According to this specification, a mobile client MAY include one or According to this specification, a Mobile Router MAY include one or
more mobile network request extensions with the prefix field set to more mobile network request extensions with the prefix field set to
zero. Such mobile network request extensions indicate that the zero. Such mobile network request extensions indicate that the
mobile client requests mobile network prefix(es) to be assigned to it Mobile Router requests mobile network prefix(es) to be assigned to it
by the home agent. In this case, the mobile client MAY set the by the home agent. In this case, the Mobile Router 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 Router receives a registration reply it MUST process it
as defined in MIPv4 [RFC3344] and [RFC5177]. If one or more network as defined in Mobile IPv4 [RFC5944] and [RFC5177]. If one or more
acknowledgement extension are included with the Code field set to network acknowledgement extension are included with the Code field
"Success" the mobile client 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 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 Router
receives a registration reply with a network acknowledgement receives a registration reply with a network acknowledgement
extensiona 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 client. 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]. Alternatively
the home agent MAY return a mobile network acknowledgement extension the home agent MAY return a mobile network acknowledgement extension
with the Code field set to one of the negative codes defined in with the Code field set to one of the negative codes defined in
[RFC5177]. [RFC5177].
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 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 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 [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 entry
For dynamic prefix allocation the mobile client's home address MAY be For dynamic prefix allocation the Mobile Router's home address MAY be
used to identify the client if it is not set to zero. Otherwise, as used to identify the client if it is not set to zero. Otherwise, as
defined in the NAI extension [RFC2794] of MIPv4 [RFC2794], the NAI defined in the NAI extension [RFC2794] of Mobile IPv4 [RFC2794], the
extension needs to be included in the registration request, in which NAI extension needs to be included in the registration request, in
case the same extension SHOULD be used to identify the mobile client which case the same extension SHOULD be used to identify the Mobile
for prefix allocation purposes. 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 MIPv4 [RFC3344], 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
This document has no actions for IANA This document has no actions for IANA
6. Normative References 6. Acknowledgements
The authors would like to thank Pete McCann and Alexandru Petrescu
for their reviews and comments.
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.
[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,
August 2002.
[RFC5177] Leung, K., Dommety, G., Narayanan, V., and A. Petrescu, [RFC5177] Leung, K., Dommety, G., Narayanan, V., and A. Petrescu,
"Network Mobility (NEMO) Extensions for Mobile IPv4", "Network Mobility (NEMO) Extensions for Mobile IPv4",
RFC 5177, April 2008. RFC 5177, April 2008.
[RFC5944] Perkins, C., "IP Mobility Support for IPv4, Revised",
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
 End of changes. 18 change blocks. 
27 lines changed or deleted 33 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/