An IPv6 Distributed Client Mobility Management approach using existing mechanisms
draft-bernardos-dmm-cmip-07

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DMM Working Group                                          CJ. Bernardos
Internet-Draft                                            A. de la Oliva
Intended status: Informational                                      UC3M
Expires: September 14, 2017                                     F. Giust
                                                                     NEC
                                                          March 13, 2017

 An IPv6 Distributed Client Mobility Management approach using existing
                               mechanisms
                      draft-bernardos-dmm-cmip-07

Abstract

   The use of centralized mobility management approaches -- such as
   Mobile IPv6 -- poses some difficulties to operators of current and
   future networks, due to the expected large number of mobile users and
   their exigent demands.  All this has triggered the need for
   distributed mobility management alternatives, that alleviate
   operators' concerns allowing for cheaper and more efficient network
   deployments.

   This draft describes a possible way of achieving a distributed
   mobility behavior with Client Mobile IP, based on Mobile IPv6 and the
   use of Cryptographic Generated Addresses.

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 September 14, 2017.

Bernardos, et al.      Expires September 14, 2017               [Page 1]
Internet-Draft           A DMM solution for CMIP              March 2017

Copyright Notice

   Copyright (c) 2017 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Description of the solution . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Comparison with Requirement document . . . . . . . .  11
     A.1.  Distributed mobility management . . . . . . . . . . . . .  11
     A.2.  Bypassable network-layer mobility support for each
           application           session . . . . . . . . . . . . . .  12
     A.3.  IPv6 deployment . . . . . . . . . . . . . . . . . . . . .  12
     A.4.  Existing mobility protocols . . . . . . . . . . . . . . .  12
     A.5.  Coexistence with deployed networks/hosts and operability
           across different networks . . . . . . . . . . . . . . . .  13
     A.6.  Operation and management considerations . . . . . . . . .  13
     A.7.  Security considerations . . . . . . . . . . . . . . . . .  13
     A.8.  Multicast . . . . . . . . . . . . . . . . . . . . . . . .  13
   Appendix B.  Open DMM platform  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   Most of the currently standardized IP mobility solutions, like Mobile
   IPv6 [RFC6275], or Proxy Mobile IPv6 [RFC5213] rely to a certain
Show full document text