Proxy Mobile IPv6 Extensions to Support Flow Mobility
draft-ietf-netext-pmipv6-flowmob-18

Document Type Active Internet-Draft (netext WG)
Last updated 2016-03-31 (latest revision 2016-03-18)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Basavaraj Patil
Shepherd write-up Show (last changed 2016-02-11)
IESG IESG state RFC Ed Queue
Consensus Yes
Telechat date
Responsible AD Brian Haberman
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state RFC-EDITOR
NETEXT Working Group                                  CJ. Bernardos, Ed.
Internet-Draft                                                      UC3M
Updates: 5213 (if approved)                               March 18, 2016
Intended status: Standards Track
Expires: September 19, 2016

         Proxy Mobile IPv6 Extensions to Support Flow Mobility
                  draft-ietf-netext-pmipv6-flowmob-18

Abstract

   Proxy Mobile IPv6 allows a mobile node to connect to the same Proxy
   Mobile IPv6 domain through different interfaces.  This document
   describes extensions to the Proxy Mobile IPv6 protocol that are
   required to support network based flow mobility over multiple
   physical interfaces.

   This document updates RFC 5213.  The extensions described in this
   document consist of the operations performed by the local mobility
   anchor and the mobile access gateway to manage the prefixes assigned
   to the different interfaces of the mobile node, as well as how the
   forwarding policies are handled by the network to ensure consistent
   flow mobility management.

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 19, 2016.

Bernardos              Expires September 19, 2016               [Page 1]
Internet-Draft            PMIPv6 flow mobility                March 2016

Copyright Notice

   Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview of the PMIPv6 flow mobility
       extensions  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Use case scenarios  . . . . . . . . . . . . . . . . . . .   4
     3.2.  Basic Operation . . . . . . . . . . . . . . . . . . . . .   5
       3.2.1.  MN sharing a common
               set of prefixes on all MAGs . . . . . . . . . . . . .   5
       3.2.2.  MN with different
               sets of prefixes on each MAG  . . . . . . . . . . . .   9
     3.3.  Use of PBU/PBA signaling  . . . . . . . . . . . . . . . .  11
     3.4.  Use of flow-level information . . . . . . . . . . . . . .  12
   4.  Message Formats . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Home Network Prefix . . . . . . . . . . . . . . . . . . .  12
     4.2.  Flow Mobility Initiate (FMI)  . . . . . . . . . . . . . .  13
     4.3.  Flow Mobility Acknowledgement (FMA) . . . . . . . . . . .  14
   5.  Conceptual Data Structures  . . . . . . . . . . . . . . . . .  14
     5.1.  Multiple Proxy Care-of Address Registration . . . . . . .  14
     5.2.  Flow Mobility Cache . . . . . . . . . . . . . . . . . . .  15
   6.  Mobile Node considerations  . . . . . . . . . . . . . . . . .  16
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   9.  Authors . . . . . . . . . . . . . . . . . . . . . . . . . . .  17
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     11.2.  Informative References . . . . . . . . . . . . . . . . .  19
Show full document text