RFC 8191: Home Network Prefix Renumbering in Proxy Mobile IPv6 (PMIPv6)
In plain English — editorial summary, not part of the RFC
In the basic Proxy Mobile IPv6 (PMIPv6) specification, a Mobile Node (MN) is assigned with a Home Network Prefix (HNP) during its initial attachment, and the MN configures its Home Address (HoA) with the HNP. During the movement of the MN, the HNP remains unchanged to keep ongoing communications associated with the HoA. However, the current PMIPv6 specification does not specify related operations when HNP renumbering has occurred (e.g., due to change of service provider or site topology, etc.). In this document, a solution to support HNP renumbering is proposed, as an optional extension of the PMIPv6 specification.
Document record
- Document ID
- RFC8191
- Published
- August 2017
- Authors
- Z. Yan; J. Lee; X. Lee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8885Proxy Mobile IPv6 Extensions for Distributed Mobility ManagementCurrent
October 2020
- RFC 7864Proxy Mobile IPv6 Extensions to Support Flow MobilityCurrent
May 2016
- RFC 8818Distributed Mobility AnchoringCurrent
October 2020
- RFC 7561Mapping Quality of Service (QoS) Procedures of Proxy Mobile IPv6 (PMIPv6) and WLANCurrent
June 2015
- 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 6705Localized Routing for Proxy Mobile IPv6Current
September 2012
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?