RFC 7148: Prefix Delegation Support for Proxy Mobile IPv6
In plain English — editorial summary, not part of the RFC
This specification defines extensions to the Proxy Mobile IPv6 protocol for allowing a mobile router in a Proxy Mobile IPv6 domain to obtain IP prefixes for its attached mobile networks using DHCPv6 prefix delegation. Network-based mobility management support is provided for those delegated IP prefixes just as it is provided for the mobile node's home address. Even if the mobile router performs a handoff and changes its network point of attachment, mobility support is ensured for all the delegated IP prefixes and for all the IP nodes in the mobile network that use IP address configuration from those delegated IP prefixes.
Document record
- Document ID
- RFC7148
- Published
- March 2014
- Authors
- X. Zhou; J. Korhonen; C. Williams; S. Gundavelli; CJ. Bernardos
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7161Proxy Mobile IPv6 (PMIPv6) Multicast Handover Optimization by the Subscription Information Acquisition through the LMA (SIAL)Current
March 2014
- RFC 6602Bulk Binding Update Support for Proxy Mobile IPv6Current
May 2012
- RFC 6496Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)Current
February 2012
- RFC 7028Multicast Mobility Routing Optimizations for Proxy Mobile IPv6Current
September 2013
- RFC 7550Issues and Recommendations with Multiple Stateful DHCPv6 OptionsObsoleted
May 2015
- RFC 7561Mapping Quality of Service (QoS) Procedures of Proxy Mobile IPv6 (PMIPv6) and WLANCurrent
June 2015
- RFC 6705Localized Routing for Proxy Mobile IPv6Current
September 2012
- RFC 6636Tuning the Behavior of the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) for Routers in Mobile and Wireless NetworksCurrent
May 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?