Architectural Guidelines for Multipath TCP Development
draft-ford-mptcp-architecture-01

Document Type Replaced Internet-Draft (individual)
Last updated 2010-05-21 (latest revision 2010-02-03)
Replaced by draft-ietf-mptcp-architecture
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-mptcp-architecture
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-ford-mptcp-architecture-01.txt

Abstract

Often endpoints are connected by multiple paths, but the nature of TCP/IP restricts communications to a single path per socket. Resource usage within the network would be more efficient were these multiple paths able to be used concurrently. This should enhance user experience through improved resilience to network failure and higher throughput. This document outlines architectural guidelines for the development of a Multipath Transport Protocol, with references to how these architectural components come together in the Multipath TCP (MPTCP) protocol. This document also lists certain high level design decisions that provide foundations for the MPTCP design, based upon these architectural requirements.

Authors

Alan Ford (alanford@cisco.com)
Costin Raiciu (c.raiciu@cs.ucl.ac.uk)
Sebastien Barre (sebastien.barre@uclouvain.be)
Jana (jiyengar@fandm.edu)
Bryan Ford (baford@mpi-sws.org)

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