RFC 5648: Multiple Care-of Addresses Registration
In plain English — editorial summary, not part of the RFC
According to the current Mobile IPv6 specification, a mobile node may have several care-of addresses but only one, called the primary care-of address, can be registered with its home agent and the correspondent nodes. However, for matters of cost, bandwidth, delay, etc, it is useful for the mobile node to get Internet access through multiple accesses simultaneously, in which case the mobile node would be configured with multiple active IPv6 care-of addresses. This document proposes extensions to the Mobile IPv6 protocol to register and use multiple care-of addresses. The extensions proposed in this document can be used by mobile routers using the NEMO (Network Mobility) Basic Support protocol as well. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5648
- Published
- October 2009
- Authors
- R. Wakikawa; V. Devarapalli; G. Tsirtsis; T. Ernst; K. Nagami
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 36
- Also known as
- —
- Updated by:
- RFC 6089
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 5640Load-Balancing for Mesh SoftwiresUpdated
August 2009
- RFC 5637Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6Current
September 2009
- RFC 5625DNS Proxy Implementation GuidelinesCurrent
August 2009
- RFC 5677IEEE 802.21 Mobility Services Framework Design (MSFD)Current
December 2009
- RFC 5619Softwire Security Analysis and RequirementsCurrent
August 2009
- RFC 5678Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) DiscoveryCurrent
December 2009
- RFC 5679Locating IEEE 802.21 Mobility Services Using DNSUpdated
December 2009
- RFC 5609State Machines for the Protocol for Carrying Authentication for Network Access (PANA)Current
August 2009
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?