RFC 5271: Mobile IPv6 Fast Handovers for 3G CDMA Networks
In plain English — editorial summary, not part of the RFC
Mobile IPv6 is designed to maintain its connectivity while moving from one network to another. It is adopted in 3G CDMA networks as a way to maintain connectivity when the mobile node (MN) moves between access routers. However, this handover procedure requires not only movement detection by the MN, but also the acquisition of a new Care-of Address and Mobile IPv6 registration with the new care-of address before the traffic can be sent or received in the target network. During this period, packets destined for the mobile node may be lost, which may not be acceptable for a real-time application such as Voice over IP (VoIP) or video telephony. This document specifies fast handover methods in the 3G CDMA networks in order to reduce latency and packet loss during handover. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5271
- Published
- June 2008
- Authors
- H. Yokota; G. Dommety
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5949Fast Handovers for Proxy Mobile IPv6Current
September 2010
- RFC 4281The Codecs Parameter for "Bucket" Media TypesObsoleted
December 2005
- RFC 6381The 'Codecs' and 'Profiles' Parameters for "Bucket" Media TypesCurrent
August 2011
- RFC 5270Mobile IPv6 Fast Handovers over IEEE 802.16e NetworksCurrent
June 2008
- RFC 5269Distributing a Symmetric Fast Mobile IPv6 (FMIPv6) Handover Key Using SEcure Neighbor Discovery (SEND)Current
June 2008
- RFC 5268Mobile IPv6 Fast HandoversObsoleted
June 2008
- RFC 5266Secure Connectivity and Mobility Using Mobile IPv4 and IKEv2 Mobility and Multihoming (MOBIKE)Current
June 2008
- RFC 5265Mobile IPv4 Traversal across IPsec-Based VPN GatewaysCurrent
June 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?