RFC 4885: Network Mobility Support Terminology
In plain English — editorial summary, not part of the RFC
This document defines a terminology for discussing network mobility (NEMO) issues and solution requirements. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4885
- Published
- July 2007
- Authors
- T. Ernst; H-Y. Lach
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4886Network Mobility Support Goals and RequirementsCurrent
July 2007
- RFC 4887Network Mobility Home Network ModelsCurrent
July 2007
- RFC 4888Network Mobility Route Optimization Problem StatementCurrent
July 2007
- RFC 4889Network Mobility Route Optimization Solution Space AnalysisCurrent
July 2007
- RFC 4980Analysis of Multihoming in Network Mobility SupportCurrent
October 2007
- RFC 5522Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile NetworksCurrent
October 2009
- RFC 5555Mobile IPv6 Support for Dual Stack Hosts and RoutersUpdated
June 2009
- RFC 4882IP Address Location Privacy and Mobile IPv6: Problem StatementCurrent
May 2007
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?