datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

Dynamic Prefix Allocation for Network Mobility for Mobile IPv4 (NEMOv4)
RFC 6626

Internet Engineering Task Force (IETF)                       G. Tsirtsis
Request for Comments: 6626                                       V. Park
Updates: 5177                                               V. Narayanan
Category: Standards Track                                       Qualcomm
ISSN: 2070-1721                                                 K. Leung
                                                                   Cisco
                                                                May 2012

                     Dynamic Prefix Allocation for
               Network Mobility for Mobile IPv4 (NEMOv4)

Abstract

   The base Network Mobility for Mobile IPv4 (NEMOv4) specification
   defines extensions to Mobile IPv4 for mobile networks.  This
   specification defines a dynamic prefix allocation mechanism for
   NEMOv4.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   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 (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Tsirtsis, et al.             Standards Track                    [Page 1]
RFC 6626          Dynamic Prefix Allocation for NEMOv4          May 2012

Table of Contents

   1. Introduction ....................................................2
   2. Requirements Notation ...........................................2
   3. Dynamic Mobile Prefix Allocation ................................2
      3.1. Mobile Client Considerations ...............................2
      3.2. Home Agent Considerations ..................................3
   4. Security Considerations .........................................4
   5. IANA Considerations .............................................4
   6. Acknowledgements ................................................4
   7. Normative References ............................................4

1.  Introduction

   The base NEMOv4 specification [RFC5177] defines extensions to Mobile
   IPv4 [RFC5944] for mobile networks.  This specification adds support
   for dynamic allocation of mobile prefixes by the home agent.

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.

3.1.  Mobile Client Considerations

   According to this specification, the Prefix field of the Mobile
   Network Request extension MUST be set to zero to indicate that the
   Mobile Router requests mobile network prefix(es) be assigned to it 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 choice
   as a hint to the home agent.  According to this specification, Mobile
   Network Request extensions with the Prefix field set to zero MAY be
   included in a registration request message either during initial
   registration or during a subsequent registration.

   When a Mobile Router receives a registration reply, it MUST process
   it as defined in Mobile IPv4 [RFC5944] and [RFC5177].  If one or more
   network acknowledgement extensions are included with the Code field
   set to "Success", the Mobile Router SHOULD treat the prefixes in the
   corresponding Prefix fields as allocated prefixes and create the
   appropriate bindings as defined in [RFC5177].

Tsirtsis, et al.             Standards Track                    [Page 2]

[include full document text]