Improving Multipath TCP Backup Subflows
draft-bonaventure-mptcp-backup-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Olivier Bonaventure , Quentin De Coninck , Matthieu Baerts , Fabien Duchene , benjamin.hesmans@uclouvain.be | ||
Last updated | 2016-01-07 (Latest revision 2015-07-06) | ||
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
This document documents some issues with the current definition of the backup subflows in [RFC6824]. The solution proposed in [RFC6824] works well when a subflow completely fails. However, if a subflow suffers from huge packet losses, but still remains up, then the delay to switch to the backup subflow may be very long. We propose to measure the evolution of the retransmission timer (RTO) to detect the bad performance of subflows.
Authors
Olivier Bonaventure
Quentin De Coninck
Matthieu Baerts
Fabien Duchene
benjamin.hesmans@uclouvain.be
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)