Evolving TCP.: how hard can it be?

Authors:
Zubair Nabi;Toby Moncaster;Anil Madhavapeddy;Steven Hand;Jon Crowcroft
Affiliations:
University of Cambridge, Cambridge, United Kingdom;University of Cambridge, Cambridge, United Kingdom;University of Cambridge, Cambridge, United Kingdom;University of Cambridge, Cambridge, United Kingdom;University of Cambridge, Cambridge, United Kingdom
Venue:
Proceedings of the 2012 ACM conference on CoNEXT student workshop
Year:
2012

Citing 5
Cited 0

Why the Internet only just works

BT Technology Journal
Flow rate fairness: dismantling a religion

ACM SIGCOMM Computer Communication Review
Is it still possible to extend TCP?

Proceedings of the 2011 ACM SIGCOMM conference on Internet measurement conference
Fitting square pegs through round pipes: unordered delivery wire-compatible with TCP and TLS

NSDI'12 Proceedings of the 9th USENIX conference on Networked Systems Design and Implementation
How hard can it be? designing and implementing a deployable multipath TCP

NSDI'12 Proceedings of the 9th USENIX conference on Networked Systems Design and Implementation

Quantified Score

Hi-index	0.00

Visualization

Abstract

Over the last decade TCP has become the de facto "narrow waist" of the Internet -- a one-size-fits-all transport that is poorly suited to the needs of modern applications. As middleboxes have become ubiquitous, it has become nigh impossible for alternative transports to exist and so application developers have come to view opening a TCP socket as the only reliable way to connect to a server. Some recent proposals circumvent this problem by camouflaging new transports so that they appear like TCP to middleboxes. We draw the key lessons from this approach and show how this could lead to a true one-size-fits-all transport: "Polyversal TCP".