Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

H. Yokota
K. Chowdhury
R. Koodli
B. Patil
F. Xia

Stream:

IETF

Source:

mipshop (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5949

Discuss this RFC: Send questions or comments to the mailing listmipshop@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5949

Abstract

Mobile IPv6 (MIPv6; RFC 3775) provides a mobile node with IP mobilitywhen it performs a handover from one access router to another, andfast handovers for Mobile IPv6 (FMIPv6) are specified to enhance thehandover performance in terms of latency and packet loss. WhileMIPv6 (and FMIPv6 as well) requires the participation of the mobilenode in the mobility-related signaling, Proxy Mobile IPv6 (PMIPv6;RFC 5213) provides IP mobility to nodes that either have or do nothave MIPv6 functionality without such involvement. Nevertheless, thebasic performance of PMIPv6 in terms of handover latency and packetloss is considered no different from that of MIPv6.

When the fast handover is considered in such an environment, severalmodifications are needed to FMIPv6 to adapt to the network-basedmobility management. This document specifies the usage of fasthandovers for Mobile IPv6 (FMIPv6; RFC 5568) when Proxy Mobile IPv6is used as the mobility management protocol. Necessary extensionsare specified for FMIPv6 to support the scenario when the mobile nodedoes not have IP mobility functionality and hence is not involvedwith either MIPv6 or FMIPv6 operations. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.