RFC 7864: Proxy Mobile IPv6 Extensions to Support Flow Mobility
In plain English — editorial summary, not part of the RFC
Proxy Mobile IPv6 (PMIPv6) allows a mobile node to connect to the same PMIPv6 domain through different interfaces. This document describes extensions to the PMIPv6 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.
Document record
- Document ID
- RFC7864
- Published
- May 2016
- Authors
- CJ. Bernardos
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
- Updates:
- RFC 5213
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7629Flow-Binding Support for Mobile IPCurrent
August 2015
- RFC 7561Mapping Quality of Service (QoS) Procedures of Proxy Mobile IPv6 (PMIPv6) and WLANCurrent
June 2015
- RFC 8191Home Network Prefix Renumbering in Proxy Mobile IPv6 (PMIPv6)Current
August 2017
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 2014
- RFC 7148Prefix Delegation Support for Proxy Mobile IPv6Current
March 2014
- RFC 7028Multicast Mobility Routing Optimizations for Proxy Mobile IPv6Current
September 2013
- RFC 8818Distributed Mobility AnchoringCurrent
October 2020
- RFC 8885Proxy Mobile IPv6 Extensions for Distributed Mobility ManagementCurrent
October 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?