Enabling compatibility between TCP Reno and TCP Vegas

PDF Version Also Available for Download.

Description

Despite research showing the superiority of TCP Vegas over TCP Reno, Reno is still the most widely deployed variant of TCP This predicament is due primarily to the alleged incompatibility of Vegas with Reno. While Yegas in isolation performs better with respect to overall network utilization, stability, fairness, throughput lznd packet loss, and burstiness; its perfarmance is generally mediocre in any environment where Reno connections exist. Hence, there exists no incentive for any operating system to adopt TCP Vegas. In this paper. we show that the accepted (default) configuration of Vegas is indeed incompatible with TCP Reno. However: with a ... continued below

Physical Description

8 p.

Creation Information

Feng, Wu-Chun & Vanichpun, Sarut January 1, 2002.

Context

This article is part of the collection entitled: Office of Scientific & Technical Information Technical Reports and was provided by UNT Libraries Government Documents Department to Digital Library, a digital repository hosted by the UNT Libraries. It has been viewed 100 times . More information about this article can be viewed below.

Who

People and organizations associated with either the creation of this article or its content.

Publisher

Provided By

UNT Libraries Government Documents Department

Serving as both a federal and a state depository library, the UNT Libraries Government Documents Department maintains millions of items in a variety of formats. The department is a member of the FDLP Content Partnerships Program and an Affiliated Archive of the National Archives.

Contact Us

What

Descriptive information to help identify this article. Follow the links below to find similar items on the Digital Library.

Description

Despite research showing the superiority of TCP Vegas over TCP Reno, Reno is still the most widely deployed variant of TCP This predicament is due primarily to the alleged incompatibility of Vegas with Reno. While Yegas in isolation performs better with respect to overall network utilization, stability, fairness, throughput lznd packet loss, and burstiness; its perfarmance is generally mediocre in any environment where Reno connections exist. Hence, there exists no incentive for any operating system to adopt TCP Vegas. In this paper. we show that the accepted (default) configuration of Vegas is indeed incompatible with TCP Reno. However: with a careful analysis of how Reno and Vegas use buffer space in routers, Reno and Vegas can be compatible with one another if Vegas is conjigured properly Furthermore, we show that overall network performance actually improves with the addition of properly conjigured Vegas flows competing head-to-head with Reno flows.

Physical Description

8 p.

Source

  • Submitted to: IEEE SAINT 2003, Symposium on Applications and the Internet, Jan. 27-31, 2003

Language

Item Type

Identifier

Unique identifying numbers for this article in the Digital Library or other systems.

  • Report No.: LA-UR-02-6973
  • Grant Number: none
  • Office of Scientific & Technical Information Report Number: 976435
  • Archival Resource Key: ark:/67531/metadc932183

Collections

This article is part of the following collection of related materials.

Office of Scientific & Technical Information Technical Reports

Reports, articles and other documents harvested from the Office of Scientific and Technical Information.

Office of Scientific and Technical Information (OSTI) is the Department of Energy (DOE) office that collects, preserves, and disseminates DOE-sponsored research and development (R&D) results that are the outcomes of R&D projects or other funded activities at DOE labs and facilities nationwide and grantees at universities and other institutions.

What responsibilities do I have when using this article?

When

Dates and time periods associated with this article.

Creation Date

  • January 1, 2002

Added to The UNT Digital Library

  • Nov. 13, 2016, 7:26 p.m.

Description Last Updated

  • Dec. 12, 2016, 5:51 p.m.

Usage Statistics

When was this article last used?

Yesterday: 0
Past 30 days: 2
Total Uses: 100

Interact With This Article

Here are some suggestions for what to do next.

Start Reading

PDF Version Also Available for Download.

International Image Interoperability Framework

IIF Logo

We support the IIIF Presentation API

Feng, Wu-Chun & Vanichpun, Sarut. Enabling compatibility between TCP Reno and TCP Vegas, article, January 1, 2002; United States. (digital.library.unt.edu/ark:/67531/metadc932183/: accessed October 19, 2018), University of North Texas Libraries, Digital Library, digital.library.unt.edu; crediting UNT Libraries Government Documents Department.