RFC 3963: Network Mobility (NEMO) Basic Support Protocol
In plain English — editorial summary, not part of the RFC
This document describes the Network Mobility (NEMO) Basic Support protocol that enables Mobile Networks to attach to different points in the Internet. The protocol is an extension of Mobile IPv6 and allows session continuity for every node in the Mobile Network as the network moves. It also allows every node in the Mobile Network to be reachable while moving around. The Mobile Router, which connects the network to the Internet, runs the NEMO Basic Support protocol with its Home Agent. The protocol is designed so that network mobility is transparent to the nodes inside the Mobile Network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3963
- Published
- January 2005
- Authors
- V. Devarapalli; R. Wakikawa; A. Petrescu; P. Thubert
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5270Mobile IPv6 Fast Handovers over IEEE 802.16e NetworksCurrent
June 2008
- RFC 5380Hierarchical Mobile IPv6 (HMIPv6) Mobility ManagementCurrent
October 2008
- RFC 6088Traffic Selectors for Flow BindingsCurrent
January 2011
- RFC 6496Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)Current
February 2012
- RFC 6618Mobile IPv6 Security Framework Using Transport Layer Security for Communication between the Mobile Node and Home AgentCurrent
May 2012
- RFC 8885Proxy Mobile IPv6 Extensions for Distributed Mobility ManagementCurrent
October 2020
- RFC 5447Diameter Mobile IPv6: Support for Network Access Server to Diameter Server InteractionCurrent
February 2009
- RFC 3957Authentication, Authorization, and Accounting (AAA) Registration Keys for Mobile IPv4Current
March 2005
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?