TCP goes to Hollywood

Stephen McQuistin, Colin Perkins, Marwan Fayed

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Real-time multimedia applications use either TCP or UDP at the transport layer, yet neither of these protocols offer all of the features required. Deploying a new protocol that does offer these features is made difficult by ossification: firewalls, and other middleboxes, in the network expect TCP or UDP, and block other types of traffic. We present TCP Hollywood, a protocol that is wire-compatible with TCP, while offering an unordered, partially reliable message-oriented transport service that is well suited to multimedia applications. Analytical results show that TCP Hollywood extends the feasibility of using TCP for real-time multimedia applications, by reducing latency and increasing utility. Preliminary evaluations also show that TCP Hollywood is deployable on the public Internet, with safe failure modes. Measurements across all major UK fixed-line and cellular networks validate the possibility of deployment.

Original languageEnglish
Title of host publicationProceedings of the 26th International Workshop on Network and Operating Systems Support for Digital Audio and Video, NOSSDAV 2016
Place of PublicationNew York
PublisherACM
Pages25-30
Number of pages6
ISBN (Electronic)9781450343565
DOIs
Publication statusPublished - 10 May 2016
Event26th ACM Workshop on Network and Operating Systems Support for Digital Audio and Video, NOSSDAV 2016 - Klagenfurt, Austria
Duration: 10 May 2016 → …
Conference number: 26
https://mmsys2016.itec.aau.at/nossdav-2016/

Workshop

Workshop26th ACM Workshop on Network and Operating Systems Support for Digital Audio and Video, NOSSDAV 2016
Abbreviated titleNOSSDAV
Country/TerritoryAustria
CityKlagenfurt
Period10/05/16 → …
Internet address

Keywords

  • Real-time multimedia applications
  • Transport protocols

Fingerprint

Dive into the research topics of 'TCP goes to Hollywood'. Together they form a unique fingerprint.

Cite this