Multipath TCP timestamp option
draft-bonaventure-mptcp-timestamp-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Olivier Bonaventure | ||
| Last updated | 2015-04-29 (Latest revision 2014-10-26) | ||
| 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
The TCP timestamps defined in [RFC1323] were designed to improve round-trip-time estimations and provide protection against wrapped sequence numbers (PAWS). This draft clarifies the utilisation of timestamps by Multipath TCP and proposes a new timestamp option that better suits the needs of Multipath TCP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)