RFC 6275: Mobility Support in IPv6
In plain English — editorial summary, not part of the RFC
This document specifies Mobile IPv6, a protocol that allows nodes to remain reachable while moving around in the IPv6 Internet. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about the mobile node's current location. IPv6 packets addressed to a mobile node's home address are transparently routed to its care-of address. The protocol enables IPv6 nodes to cache the binding of a mobile node's home address with its care-of address, and to then send any packets destined for the mobile node directly to it at this care-of address. To support this operation, Mobile IPv6 defines a new IPv6 protocol and a new destination option. All IPv6 nodes, whether mobile or stationary, can communicate with mobile nodes. This document obsoletes RFC 3775. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6275
- Published
- July 2011
- Authors
- C. Perkins; D. Johnson; J. Arkko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 169
- Also known as
- —
- Obsoletes:
- RFC 3775
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 8371Mobile Node Identifier Types for MIPv6Current
July 2018
- RFC 8504IPv6 Node RequirementsCurrent
January 2019
- RFC 3879Deprecating Site Local AddressesCurrent
September 2004
- RFC 3697IPv6 Flow Label SpecificationObsoleted
March 2004
- RFC 9063Host Identity Protocol ArchitectureCurrent
July 2021
- RFC 3306Unicast-Prefix-based IPv6 Multicast AddressesUpdated
September 2002
- RFC 3122Extensions to IPv6 Neighbor Discovery for Inverse Discovery SpecificationCurrent
June 2001
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?