RFC 6089: Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic Support
In plain English — editorial summary, not part of the RFC
This document introduces extensions to Mobile IPv6 that allow nodes to bind one or more flows to a care-of address. These extensions allow multihomed nodes to instruct home agents and other Mobile IPv6 entities to direct inbound flows to specific addresses. [STANDARDS- TRACK]
Document record
- Document ID
- RFC6089
- Published
- January 2011
- Authors
- G. Tsirtsis; H. Soliman; N. Montavont; G. Giaretta; K. Kuladinithi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 31
- Also known as
- —
- Updates:
- RFC 5648
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 8372MPLS Flow Identification ConsiderationsCurrent
May 2018
- RFC 3388Grouping of Media Lines in the Session Description Protocol (SDP)Obsoleted
December 2002
- RFC 6088Traffic Selectors for Flow BindingsCurrent
January 2011
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
- RFC 6098Generic Notification Message for Mobile IPv4Current
April 2012
- RFC 6079HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment (BONE)Current
January 2011
- RFC 6078Host Identity Protocol (HIP) Immediate Carriage and Conveyance of Upper-Layer Protocol Signaling (HICCUPS)Current
January 2011
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?