Improving Multipath TCP Backup Subflows
draft-bonaventure-mptcp-backup-00

Document Type Expired Internet-Draft (individual)
Last updated 2016-01-07 (latest revision 2015-07-06)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-bonaventure-mptcp-backup-00.txt

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 (Olivier.Bonaventure@uclouvain.be)
Quentin Coninck (quentin.deconinck@student.uclouvain.be)
Matthieu Baerts (matthieu.baerts@student.uclouvain.be)
Fabien Duchene (fabien.duchene@uclouvain.be)
benjamin.hesmans@uclouvain.be (benjamin.hesmans@uclouvain.be)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)