Considerations for MPTCP operation in 5G
draft-purkayastha-mptcp-considerations-for-nextgen-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Debashish Purkayastha , Michelle Perras , Akbar Rahman | ||
| Last updated | 2018-05-02 (Latest revision 2017-10-29) | ||
| 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 is deployed in devices which have multiple interfaces to different networks. It takes advantage of these multiple interfaces to improve user experience by bandwidth aggregation, redundancy, and increased reliability by having a fallback option. This document describes scenarios where next generation (5G) mobility management frameworks may impact MPTCP operations thus potentially jeopardizing achievement of some of these gains.
Authors
Debashish Purkayastha
Michelle Perras
Akbar Rahman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)