A generic control stream for Multipath TCP

Document Type Expired Internet-Draft (individual)
Authors Christoph Paasch  , Olivier Bonaventure 
Last updated 2014-08-15 (latest revision 2014-02-11)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml pdf ps htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Multipath TCP's extensive use of TCP options to exchange control information consumes a significant part of the TCP option space. Extending MPTCP to add more control information into the session becomes cumbersome as the TCP option space is limited to 40 bytes. This draft introduces a control stream that allows to send control information as part of the subflow's payload. The control stream is mapped into a separate sequence number space and uses a TLV-format for maximum extensibility. It is left to future documents to specify how the TLV-format might be used to exchange control information. As the control stream is sent as part of the subflow's payload, it is not subject to the 40 bytes limitation of the TCP option space.


Christoph Paasch (christoph.paasch@uclouvain.be)
Olivier Bonaventure (Olivier.Bonaventure@uclouvain.be)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)