RFC 5177: Network Mobility (NEMO) Extensions for Mobile IPv4
In plain English — editorial summary, not part of the RFC
This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the Mobile Network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5177
- Published
- April 2008
- Authors
- K. Leung; G. Dommety; V. Narayanan; A. Petrescu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 26
- Also known as
- —
- Updated by:
- RFC 6626
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6276DHCPv6 Prefix Delegation for Network Mobility (NEMO)Current
July 2011
- RFC 6521Home Agent-Assisted Route Optimization between Mobile IPv4 NetworksCurrent
March 2012
- RFC 4980Analysis of Multihoming in Network Mobility SupportCurrent
October 2007
- RFC 4487Mobile IPv6 and Firewalls: Problem StatementCurrent
May 2006
- RFC 7148Prefix Delegation Support for Proxy Mobile IPv6Current
March 2014
- RFC 7458Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet CoreCurrent
February 2015
- RFC 5175IPv6 Router Advertisement Flags OptionCurrent
March 2008
- RFC 5172Negotiation for IPv6 Datagram Compression Using IPv6 Control ProtocolCurrent
March 2008
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?