RFC 4980: Analysis of Multihoming in Network Mobility Support
In plain English — editorial summary, not part of the RFC
This document is an analysis of multihoming in the context of network mobility (NEMO) in IPv6. As there are many situations in which mobile networks may be multihomed, a taxonomy is proposed to classify the possible configurations. The possible deployment scenarios of multihomed mobile networks are described together with the associated issues when network mobility is supported by RFC 3963 (NEMO Basic Support). Recommendations are offered on how to address these issues. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4980
- Published
- October 2007
- Authors
- C. Ng; T. Ernst; E. Paik; M. Bagnulo
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5007DHCPv6 LeasequeryCurrent
September 2007
- RFC 4889Network Mobility Route Optimization Solution Space AnalysisCurrent
July 2007
- RFC 4888Network Mobility Route Optimization Problem StatementCurrent
July 2007
- RFC 5072IP Version 6 over PPPUpdated
September 2007
- RFC 4887Network Mobility Home Network ModelsCurrent
July 2007
- RFC 4886Network Mobility Support Goals and RequirementsCurrent
July 2007
- RFC 4885Network Mobility Support TerminologyCurrent
July 2007
- 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?