ACM Home Page
Please provide us with feedback. Feedback
Structured streams: a new transport abstraction
Full text PdfPdf (695 KB)
Source
Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Proceedings of the 2007 conference on Applications, technologies, architectures, and protocols for computer communications table of contents
Kyoto, Japan
SESSION: Resource allocation table of contents
Pages: 361 - 372  
Year of Publication: 2007
ISBN:978-1-59593-713-1
Also published in ...
Author
Bryan Ford  Massachusetts Institute of Technology, Cambridge, MA
Sponsors
SIGCOMM: ACM Special Interest Group on Data Communication
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 13,   Downloads (12 Months): 123,   Citation Count: 3
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1282380.1282421
What is a DOI?

ABSTRACT

Internet applications currently have a choice between stream and datagram transport abstractions. Datagrams efficiently support small transactions and streams are suited for long-running conversations, but neither abstraction adequately supports applications like HTTP that exhibit a mixture of transaction sizes, or applications like FTP and SIP that use multiple transport instances. Structured Stream Transport (SST) enhances the traditional stream abstraction with a hierarchical hereditary structure, allowing applications to create lightweight child streams from any existing stream. Unlike TCP streams, these lightweight streams incur neither 3-way handshaking delays on startup nor TIME-WAIT periods on close. Each stream offers independent data transfer and flow control, allowing different transactions to proceed in parallel without head-of-line blocking, but all streams share one congestion control context. SST supports both reliable and best-effort delivery in a way that semantically unifies datagrams with streams and solves the classic "large datagram" problem, where a datagram's loss probability increases exponentially with fragment count. Finally, an application can prioritize its streams relative to each other and adjust priorities dynamically through out-of-band signaling. A user-space prototype shows that SST is TCP-friendly to within 2%, and performs comparably to a user-space TCP and to within 10% of kernel TCP on a WiFi network.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
 
3
Hari Balakrishnan et al. TCP behavior of a busy Internet server: Analysis and improvements. In IEEE INFOCOM, March 1998.
4
 
5
 
6
7
 
8
9
10
 
11
 
12
13
14
 
15
16
 
17
 
18
Theodore Faber, Joe Touch, and Wei Yue. The TIME-WAIT state in TCP and its effects on busy servers. In IEEE INFOCOM, volume 3, pages 1573--1583, March 1999.
 
19
 
20
 
21
Bryan Ford. Scalable Internet routing on topology-independent node identities. Technical Report 926, MIT LCS MIT Laboratory for Computer Science, October 2003.
 
22
 
23
Jim Gettys. Simple MUX protocol specification, October 1996. W3C Working Draft.
 
24
V. Gurbani and S. Lawrence. Handling large User Datagram Protocol responses in the Session Initiation Protocol, October 2006. Internet-Draft (Work in Progress).
 
25
 
26
 
27
The internet traffic archive. http://ita.ee.lbl.gov/.
 
28
 
29
 
30
 
31
 
32
E. Kohler, M. Handley, and S. Floyd. Datagram congestion control protocol (DCCP), March 2006. RFC 4340.
 
33
Venkat Kudallur et al. IE7 networking improvements in content caching and decompression. IEBlog, October 2005.
 
34
35
 
36
R. Moskowitz and P. Nikander. Host identity protocol (HIP) architecture, May 2006. RFC 4423.
 
37
Mozilla.org. Firefox tips & tricks: Pipelining. http://www.mozilla.org/support/firefox/tips#oth_pipelining.
 
38
H. F. Nielsen et al. Network performance effects of HTTP/1.1, CSS1, and PNG, June 1997. W3C NOTE-pipelining-970624.
 
39
 
40
Craig Partridge. Implementing the reliable data protocol (RDP). In USENIX Summer Conference, June 1987.
 
41
 
42
 
43
E. Rescorla and N. Modadugu. Datagram transport layer security, April 2006. RFC 4347.
 
44
 
45
 
46
47
 
48
 
49
R. Stewart et al. Stream control transmission protocol, October 2000. RFC 2960.
 
50
 
51
Carl A. Sunshine and Yogen K. Dalal. Connection management in transport protocols. Computer Networks, 2(6):454--473, December 1978.
 
52
Transmission control protocol, September 1981. RFC 793.
53
 
54
 
55
T. Ylonen and C. Lonvick, Ed. The secure shell protocol architecture, January 2006. RFC 4251.
56