Search icone
Search and publish your papers
Our Guarantee
We guarantee quality.
Find out more!

Performance based comparision of TCP variants: Reno and Sack on real test beds

Or download with : a doc exchange

About the author

Level
Expert

About the document

Published date
Language
documents in English
Format
pdf
Type
term papers
Pages
4 pages
Level
Expert
Accessed
0 times
Validated by
Committee Oboolo.com
0 Comment
Rate this document
  1. Introduction
  2. Reading parameters
  3. NIST net
  4. TCP reno
  5. Motivation for improving reno
  6. TCP selective acknowledgement (sack)
  7. Reading for TCP sack
  8. Conclusion
  9. References

One of the most important parameter of data communication is the TCP protocol. It has underwent many changes which brought into existence many variant of it like tahoe, reno, new reno, sack, vegas, westwood. Nowadays we are using TCP SACK as the tcp variant as it is better as compared to its predecessor reno. With the software NIST Net we could emulate any kind of links and get the results with actual packets in consideration. The procedure of testing any network related protocol is first simulated and if the results are satisfactory than the emulation is done which is in actual a real test bed so if the output are satisfactory then it is directly used as a part of existing network. With Linux as the operating system installed in three computers and one of them acting as a router which has NIST Net installed in it; we could generate the all the parameter that need to be considered in data communication. We can change the bandwidth, delay, drop rate with respect to congestion etc so that we could consider the parameters of actual links that will be involved and can get the idea of the throughput with the system and hence we could get the idea of the output. All new protocols go through this testing procedure before getting into implementation. By getting these results we can know the difference in the throughput with the variants of TCP and get the comparison of reno and sack. Keywords: TCP variants, Emulator, NIST Net

[...] However, under Reno, it will not fall back to Slow Start; but instead, it should take advantage of the fact that the flow that currently exists should keep on sending, but using less resources. This is implemented by first halving the size of its cwnd and storing this value in ssthresh. We then set cwnd to ssthresh plus 3*MSS (where 3 is the number of dupacks required to trigger fast retransmit). This will include only up to half of the number of segments just before the Fast Recovery. [...]


[...] Emulation, as defined here, is a combination of two common techniques for testing network code: simulation, which we can define as a synthetic environment for running representations of code; and live testing, a real environment for running real code. In these terms, emulation is a ?semisynthetic? environment for running real code. The environment is semi-synthetic in the sense that it is a real network implementation (in the case of NIST Net, the Linux 2.xx kernel) with a supplementary means for introducing synthetic delays and faults. [...]

Recent documents in computer science category

Reconstructing householder vectors from tall-skinny QR

 Science & technology   |  Computer science   |  Presentation   |  04/21/2017   |   .doc   |   4 pages

Software requirement development - The airline ticketing reservations software systems

 Science & technology   |  Computer science   |  Presentation   |  01/30/2017   |   .doc   |   3 pages