A socket API to control Multipath TCP
draft-hesmans-mptcp-socket-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | benjamin.hesmans@uclouvain.be , Olivier Bonaventure | ||
| Last updated | 2017-01-09 (Latest revision 2016-07-08) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document proposes an enhanced socket API to allow applications to control the operation of a Multipath TCP stack.
Authors
benjamin.hesmans@uclouvain.be
Olivier Bonaventure
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)