metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5568: Mobile IPv6 Fast Handovers

Still current, but amended. Parts of this document are changed or extended by RFC 7411. Read both.

In plain English — editorial summary, not part of the RFC

Mobile IPv6 enables a mobile node (MN) to maintain its connectivity to the Internet when moving from one Access Router to another, a process referred to as handover. During handover, there is a period during which the mobile node is unable to send or receive packets because of link-switching delay and IP protocol operations. This "handover latency" resulting from standard Mobile IPv6 procedures (namely, movement detection, new Care-of Address configuration, and Binding Update) is often unacceptable to real-time traffic such as Voice over IP (VoIP). Reducing the handover latency could be beneficial to non-real-time, throughput-sensitive applications as well. This document specifies a protocol to improve handover latency due to Mobile IPv6 procedures. This document does not address improving the link-switching latency. This document updates the packet formats for the Handover Initiate (HI) and Handover Acknowledge (HAck) messages to the Mobility Header Type. [STANDARDS-TRACK]

Document record

Document ID
RFC5568
Published
July 2009
Authors
R. Koodli
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
51
Also known as
—
Obsoletes:
RFC 5268
Updated by:
RFC 7411

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 4068 (2005)
  2. RFC 5268 (2008)
  3. RFC 5568 (2009)

Read the full history of Mobile IPv6 Fast Handovers →

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.

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?

canonical URL: /rfc/5568-mobile-ipv6-fast-handovers