RFC 4830: Problem Statement for Network-Based Localized Mobility Management (NETLMM)
In plain English — editorial summary, not part of the RFC
Localized mobility management is a well-understood concept in the IETF, with a number of solutions already available. This document looks at the principal shortcomings of the existing solutions, all of which involve the host in mobility management, and makes a case for network-based local mobility management. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4830
- Published
- April 2007
- Authors
- J. Kempf
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 13
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4831Goals for Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4832Security Threats to Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4833Timezone Options for DHCPCurrent
April 2007
- RFC 4857Mobile IPv4 Regional RegistrationCurrent
June 2007
- RFC 4861Neighbor Discovery for IP version 6 (IPv6)Updated
September 2007
- RFC 4862IPv6 Stateless Address AutoconfigurationUpdated
September 2007
- RFC 4795Link-local Multicast Name Resolution (LLMNR)Current
January 2007
- RFC 4866Enhanced Route Optimization for Mobile IPv6Current
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?