datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

A PMIPv6-based solution for Distributed Mobility Management
draft-bernardos-dmm-pmip-03

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-02-03
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

DMM Working Group                                          CJ. Bernardos
Internet-Draft                                            A. de la Oliva
Intended status: Standards Track                                F. Giust
Expires: August 4, 2014                                             UC3M
                                                        January 31, 2014

      A PMIPv6-based solution for Distributed Mobility Management
                      draft-bernardos-dmm-pmip-03

Abstract

   The number of mobile users and their traffic demand is expected to be
   ever-increasing in future years, and this growth can represent a
   limitation for deploying current mobility management schemes that are
   intrinsically centralized, e.g., Mobile IPv6 and Proxy Mobile IPv6.
   For this reason it has been waved a need for distributed and dynamic
   mobility management approaches, with the objective of reducing
   operators' burdens, evolving to a cheaper and more efficient
   architecture.

   This draft describes multiple solutions for network-based distributed
   mobility management inspired by the well known Proxy Mobile IPv6.

Requirements Language

   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 RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   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
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 4, 2014.

Bernardos, et al.        Expires August 4, 2014                 [Page 1]
Internet-Draft          A DMM solution for PMIPv6           January 2014

Copyright Notice

   Copyright (c) 2014 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Partially distributed solution  . . . . . . . . . . . . . . .   4
     3.1.  Initial registration  . . . . . . . . . . . . . . . . . .   6
     3.2.  The CMD as PBU/PBA relay  . . . . . . . . . . . . . . . .   7
     3.3.  The CMD as MAAR locator . . . . . . . . . . . . . . . . .   9
     3.4.  The CMD as MAAR proxy . . . . . . . . . . . . . . . . . .  10
     3.5.  De-registration . . . . . . . . . . . . . . . . . . . . .  11
     3.6.  Message Format  . . . . . . . . . . . . . . . . . . . . .  11
       3.6.1.  Previous MAAR Option  . . . . . . . . . . . . . . . .  11
       3.6.2.  Serving MAAR Option . . . . . . . . . . . . . . . . .  13
   4.  Fully distributed solution  . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Appendix A.  Comparison with Requirement document . . . . . . . .  15
     A.1.  Distributed Processing  . . . . . . . . . . . . . . . . .  16
     A.2.  Transparency to Upper Layers when needed  . . . . . . . .  16
     A.3.  IPv6 deployment . . . . . . . . . . . . . . . . . . . . .  16
     A.4.  Existing mobility protocols . . . . . . . . . . . . . . .  16
     A.5.  Co-existence with deployed networks and hosts . . . . . .  17
     A.6.  Security considerations . . . . . . . . . . . . . . . . .  17

[include full document text]