Negotiating the Maximum Number of MPTCP Subflows
draft-boucadair-mptcp-extensions-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mohamed Boucadair , Christian Jacquenet | ||
| Last updated | 2015-06-17 (Latest revision 2015-06-16) | ||
| Replaced by | draft-boucadair-mptcp-max-subflow | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-boucadair-mptcp-max-subflow | |
| 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 specifies an experimental MPTCP option that is meant to negotiate the maximum number of subflows that can be established and maintained for a given MPTCP connection. The purpose is to minimize any possible performance degradation that can be induced by a possibly large number of establishment requests for additional subflows if the remote endpoint is not appropriateley dimensioned to handle such requests.
Authors
Mohamed Boucadair
Christian Jacquenet
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)