Architectural Guidelines for Multipath TCP Development

Ford, Alan;Raiciu, Costin;Handley, Mark;Barré, Sébastien;Iyengar, Janardhan
(2011) Internet Engineering Task Force - RFC — Vol. No object, n° 6182, p. 28 (2011)

Files

rfc6182.txt
  • Open Access
  • Text
  • 67.16 KB
Download
rfc6182.txt
  • Open Access
  • Text
  • 67.16 KB
Download

Details

Authors
  • Ford, AlanRoke Manor Research
    Author
  • Raiciu, CostinUniversity College London
    Author
  • Handley, MarkUniversity College London
    Author
  • Barré, SébastienUCLouvain
    Author
  • Iyengar, JanardhanFranklin and Marshall College
    Author
Abstract
Hosts are often connected by multiple paths, but TCP restricts communications to a single path per transport connection. 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 development of a Multipath TCP (MPTCP). This document lists certain high-level design decisions that provide foundations for the design of the MPTCP protocol, based upon these architectural requirements.
Affiliations
  • Roke Manor ResearchNo object
  • University College LondonNo object
  • Institution iconUCLouvainEPL/INGI - Département d'ingénierie informatique
  • Franklin and Marshall CollegeMathematics and Computer Science

Citations

  • APA
  • Chicago
  • FWB

Ford, A., Raiciu, C., Handley, M., Barré, S., & Iyengar, J. (2011). Architectural Guidelines for Multipath TCP Development. Internet Engineering Task Force - RFC, No object(6182), 28. https://hdl.handle.net/2078.5/255164 (Original work published 2011)