Proxy Mobile IPv6 Extensions to Support Flow Mobility
RFC 7864
| Document | Type |
RFC - Proposed Standard
(May 2016; No errata)
Updates RFC 5213
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized 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 7864 (Proposed Standard) | |
| Consensus Boilerplate | 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 | ||
Internet Engineering Task Force (IETF) CJ. Bernardos, Ed.
Request for Comments: 7864 UC3M
Updates: 5213 May 2016
Category: Standards Track
ISSN: 2070-1721
Proxy Mobile IPv6 Extensions to Support Flow Mobility
Abstract
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.
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/rfc7864.
Bernardos Standards Track [Page 1]
RFC 7864 PMIPv6 Flow Mobility May 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 . . . 6
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 . . . . . . . . . . . . . . . . . . . 13
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 (FMC) . . . . . . . . . . . . . . . . 15
6. Mobile Node Considerations . . . . . . . . . . . . . . . . . 16
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . 18
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 18
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 19
Bernardos Standards Track [Page 2]
RFC 7864 PMIPv6 Flow Mobility May 2016
1. Introduction
Proxy Mobile IPv6 (PMIPv6), specified in [RFC5213], provides network-
based mobility management to hosts connecting to a PMIPv6 domain.
PMIPv6 introduces two new functional entities, the Local Mobility
Anchor (LMA) and the Mobile Access Gateway (MAG). The MAG is the
entity detecting the Mobile Node's (MN's) attachment and providing IP
connectivity. The LMA is the entity assigning one or more Home
Network Prefixes (HNPs) to the MN and is the topological anchor for
all traffic belonging to the MN.
PMIPv6 allows an MN to connect to the same PMIPv6 domain through
Show full document text