ACM Home Page
Please provide us with feedback. Feedback
TCP congestion control with a misbehaving receiver
Full text PdfPdf (783 KB)
Source ACM SIGCOMM Computer Communication Review archive
Volume 29 ,  Issue 5  (October 1999) table of contents
SESSION: Papers table of contents
Pages: 71 - 78  
Year of Publication: 1999
ISSN:0146-4833
Authors
Stefan Savage  University of Washington, Seattle
Neal Cardwell  University of Washington, Seattle
David Wetherall  University of Washington, Seattle
Tom Anderson  University of Washington, Seattle
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 42,   Downloads (12 Months): 83,   Citation Count: 31
Additional Information:

abstract   references   cited by   collaborative colleagues  

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

ABSTRACT

In this paper, we explore the operation of TCP congestion control when the receiver can misbehave, as might occur with a greedy Web client. We first demonstrate that there are simple attacks that allow a misbehaving receiver to drive a standard TCP sender arbitrarily fast, without losing end-to-end reliability. These attacks are widely applicable because they stem from the sender behavior specified in RFC 2581 rather than implementation bugs. We then show that it is possible to modify TCP to eliminate this undesirable behavior entirely, without requiring assumptions of any kind about receiver behavior. This is a strong result: with our solution a receiver can only reduce the data transfer rate by misbehaving, thereby eliminating the incentive to do so.


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
 
4
{APS99} M. Allman, V. Paxson, and W. Stevens. TCP congestion control. RFC 2581, April 1999.
 
5
 
6
{FGM+99} R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, and T. Berners-Lee. Hypertext Transfer Protocol --- HTTP/1.1. RFC 2616, June 1999.
 
7
{Flo95} Sally Floyd. TCP and successive fast retransmits, http://www.aciri.org/floyd/papers/fastretrans.ps, May1995.
 
8
{FMM+99} Sally Floyd, Jamshid Mahdavi, Matt Mathis, Matthew Podolsky, and Allyn Romanow. An extension to the selective acknowledgment (SACK) option for TCP. Internet Draft, August 1999.
9
 
10
{JBB92} V. Jacobson, R. Braden, and D. Borman. TCP extensions for high performance. RFC 1323, May 1992.
 
11
{KA98} S. Kent and R. Atkinson. Security architecture for the internet protocol. RFC 2401, November 1998.
 
12
{MMFR96} Matt Mathis, Jamshid Mahdavi, Sally Floyd, and Allyn Romanow. TCP Selective Acknowledgement options. RFC 2018, April 1996.
 
13
{PAD+99} V. Paxson, M. Allman, S. Dawson, W. Fenner, J. Griner, I. Heavens, K. Lahey, J. Semke, and B. Volz. Known TCP implementation problems. RFC 2525, March 1999.
 
14
{RHE99} Reza Rejaie, Mark Handley, and Deborah Estrin. RAP: An end-to-end rate-based congestion control mechanism for realtime streams in the Internet, In INFOCOM '99, March 1999.
 
15
{Sch96} Bruce Schneier. Applied Cryptography. John Wiley & Sons, 2nd edition, 1996.
16
 
17
{Ste94} W. Richard Stevens. TCP/IP Illustrated, volume 1. Addison Wesley, 1994.
 
18
{Vas} Fyodor Vaskovich. nmap. http://www.insecure.org/nmap/.
 
19
{VRC98} L. Vivisano, L. Rizzo, and J. Crowcroft. TCP-like congestion control for layered multicast data transfer. In INFOCOM '98, April 1998.
 
20
{ZDE+93} L. Zhang, S. Deering, D. Estrin, S. Shenker, and D. Zappala. RSVP: A New Resource ReSerVation Protocol. IEEE Network, pages 8-18, September 1993.

CITED BY  32
Collaborative Colleagues:
Stefan Savage: colleagues
Neal Cardwell: colleagues
David Wetherall: colleagues
Tom Anderson: colleagues