Network-Assisted MPTCP: Use Cases, Deployment Scenarios and Operational Considerations
draft-nam-mptcp-deployment-considerations-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Mohamed Boucadair , Christian Jacquenet , Olivier Bonaventure , Wim Henderickx , Robert Skog | ||
Last updated | 2017-06-10 (Latest revision 2016-12-07) | ||
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
Network-Assisted MPTCP deployment models are designed to facilitate the adoption of MPTCP for the establishment of multi-path communications without making any assumption about the support of MPTCP by the communicating peers. MPTCP Conversion Points (MCPs) located in the network are responsible for establishing multi-path communications on behalf of endpoints, thereby taking advantage of MPTCP capabilities to achieve different goals that include (but are not limited to) optimization of resource usage (e.g., bandwidth aggregation), of resiliency (e.g., primary/backup communication paths), and traffic offload management. This document describes Network-Assisted MPTCP uses cases, deployment scenarios, and operational considerations.
Authors
Mohamed Boucadair
Christian Jacquenet
Olivier Bonaventure
Wim Henderickx
Robert Skog
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)