RFC 6279: Proxy Mobile IPv6 (PMIPv6) Localized Routing Problem Statement
In plain English — editorial summary, not part of the RFC
Proxy Mobile IPv6 is the IETF Standard for network-based mobility management. In Proxy Mobile IPv6, mobile nodes are topologically anchored at a Local Mobility Anchor, which forwards all data for registered mobile nodes. The setup and maintenance of localized routing, which allows forwarding of data packets between two mobile nodes' Mobility Access Gateways without involvement of their Local Mobility Anchor in forwarding, is not considered. This document describes the problem space of localized routing in Proxy Mobile IPv6. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6279
- Published
- June 2011
- Authors
- M. Liebsch; S. Jeong; Q. Wu
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5522Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile NetworksCurrent
October 2009
- RFC 6282Compression Format for IPv6 Datagrams over IEEE 802.15.4-Based NetworksUpdated
September 2011
- RFC 6276DHCPv6 Prefix Delegation for Network Mobility (NEMO)Current
July 2011
- RFC 6275Mobility Support in IPv6Current
July 2011
- RFC 6273The Secure Neighbor Discovery (SEND) Hash Threat AnalysisCurrent
June 2011
- RFC 6269Issues with IP Address SharingCurrent
June 2011
- RFC 6261Encrypted Signaling Transport Modes for the Host Identity ProtocolCurrent
May 2011
- RFC 6302Logging Recommendations for Internet-Facing ServersCurrent
June 2011
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?