MPTCP Enhancement Opportunities
draft-palanivelanchetansenthil-mptcp-enhancements-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Palanivelan Appanasamy , Chetan Harsha | ||
| Last updated | 2016-04-19 (Latest revision 2015-10-17) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
MPTCP Intends to address a wide range of issues, with minimal implementation tweaks. Though this works in a range of use cases,there are some use cases, where some standard implementation recommendations could help. The Purpose of this draft is to document Opportunities, where Enhancements to MPTCP can translate to more wider deployments.
Authors
Palanivelan Appanasamy
Chetan Harsha
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)