RFC 7429: Distributed Mobility Management: Current Practices and Gap Analysis
In plain English — editorial summary, not part of the RFC
This document analyzes deployment practices of existing IP mobility protocols in a distributed mobility management environment. It then identifies existing limitations when compared to the requirements defined for a distributed mobility management solution.
Document record
- Document ID
- RFC7429
- Published
- January 2015
- Authors
- D. Liu; JC. Zuniga; P. Seite; H. Chan; CJ. Bernardos
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7333Requirements for Distributed Mobility ManagementCurrent
August 2014
- RFC 8818Distributed Mobility AnchoringCurrent
October 2020
- RFC 8885Proxy Mobile IPv6 Extensions for Distributed Mobility ManagementCurrent
October 2020
- RFC 7428Transmission of IPv6 Packets over ITU-T G.9959 NetworksCurrent
February 2015
- RFC 7421Analysis of the 64-bit Boundary in IPv6 AddressingCurrent
January 2015
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 7402Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)Current
April 2015
- RFC 7401Host Identity Protocol Version 2 (HIPv2)Updated
April 2015
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?