RFC 5270: Mobile IPv6 Fast Handovers over IEEE 802.16e Networks
In plain English — editorial summary, not part of the RFC
This document describes how a Mobile IPv6 Fast Handover can be implemented on link layers conforming to the IEEE 802.16e suite of specifications. The proposed scheme tries to achieve seamless handover by exploiting the link-layer handover indicators and thereby synchronizing the IEEE 802.16e handover procedures with the Mobile IPv6 fast handover procedures efficiently. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5270
- Published
- June 2008
- Authors
- H. Jang; J. Jee; Y. Han; S. Park; J. Cha
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5380Hierarchical Mobile IPv6 (HMIPv6) Mobility ManagementCurrent
October 2008
- RFC 6058Transient Binding for Proxy Mobile IPv6Current
March 2011
- RFC 6088Traffic Selectors for Flow BindingsCurrent
January 2011
- RFC 6496Secure Proxy ND Support for SEcure Neighbor Discovery (SEND)Current
February 2012
- RFC 3963Network Mobility (NEMO) Basic Support ProtocolCurrent
January 2005
- RFC 6618Mobile IPv6 Security Framework Using Transport Layer Security for Communication between the Mobile Node and Home AgentCurrent
May 2012
- RFC 5447Diameter Mobile IPv6: Support for Network Access Server to Diameter Server InteractionCurrent
February 2009
- RFC 5269Distributing a Symmetric Fast Mobile IPv6 (FMIPv6) Handover Key Using SEcure Neighbor Discovery (SEND)Current
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?