RFC 7629: Flow-Binding Support for Mobile IP
In plain English — editorial summary, not part of the RFC
This specification defines extensions to the Mobile IP protocol for allowing a mobile node with multiple interfaces to register a care-of address for each of its network interfaces and to simultaneously establish multiple IP tunnels with its home agent. This essentially allows the mobile node to utilize all the available network interfaces and build a higher aggregated logical pipe with its home agent for its home address traffic. Furthermore, these extensions also allow the mobile node and the home agent to negotiate IP traffic flow policies for binding individual flows with the registered care-of addresses.
Document record
- Document ID
- RFC7629
- Published
- August 2015
- Authors
- S. Gundavelli; K. Leung; G. Tsirtsis; A. Petrescu
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7864Proxy Mobile IPv6 Extensions to Support Flow MobilityCurrent
May 2016
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 7829SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission ProtocolCurrent
April 2016
- RFC 7325MPLS Forwarding Compliance and Performance RequirementsCurrent
August 2014
- RFC 7190Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)Current
March 2014
- RFC 8684TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 2020
- RFC 88030-RTT TCP Convert ProtocolCurrent
July 2020
- RFC 6356Coupled Congestion Control for Multipath Transport ProtocolsCurrent
October 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?