\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Performance Analysis of TCP Tahoe, Reno, New Reno, Sack and Vegas using NS -2},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2013-01-15 (revised: 15 January 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-01-15}
\title{Performance Analysis of TCP Tahoe, Reno, New Reno, Sack and Vegas using NS -2}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{A F M Zainul  Abadin}

             \author[2]{Md. Anwar  Hossain}

             \author[3]{Muntasir  Ahmed}

             \affil[1]{  Pabna University of Science and Technology}

\renewcommand\Authands{ and }

\date{\small \em Received: 13 December 2012 Accepted: 4 January 2013 Published: 15 January 2013}

\maketitle


\begin{abstract}
        


The Transmission Control Protocol (TCP) is the dominating end-to-end protocol on the internet today but still it faces congestion problems in some cases. To overcome congestion problems, several congestion control and avoiding mechanisms namely: Tahoe, Reno, Vegas, and Sack etc. all with different features and advantages but with maximal throughput as main objective, which are termed as the clones of TCP, have been incorporated into TCP/IP protocol for handling congestion efficiently in different network scenarios. However, one clone cannot be suitable for each case. So this paper has investigated the characteristics of the mentioned clones and calculated throughputs of them in simulated environment varying various performances metrics such as delay, buffer size, error rate, number of traffic and bandwidth for finding which one is the best for what scenario. The performance of these clones for varying network conditions and settings can effectively be evaluated using NS-2. In this work, by doing simulation in NS-2 environment the throughputs of some exiting TCP implementations are calculated considering various metrics and then the calculated throughputs are compared among one another. These comparisons show that which one is suitable in which cases.

\end{abstract}


\keywords{TCP, Tahoe, Reno, New Reno, Sack, Vegas.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
ransmission Control Protocol (TCP) is the most widely used transport layer protocol in the Internet and one of the most important standards for best effort, reliable data transmission. Today's Internet traffic uses predominately TCP, as for applications like HTTP for Web Browsing, FTP for file transfer or SMTP for Electronic Mail Transfer. The performance perceived by users of these Internet applications depends largely on the performance of TCP \hyperref[b0]{[1]}. Considering that the TCP/IP protocol suite is the foundation of the Internet this comes as no surprise. TCP provides a secure and reliable transfer of information. Therefore it is used by most of the existing Internet applications today and more than 90 percent of all data transfers use TCP. The evolution of the Internet has in turn led to evolutions in the TCP protocol. transport layer and the application layer. The transport layer can be looked upon as the heart of the whole protocol hierarchy. It provides data transport for the application layer above it. Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) are two different transport protocols in the TCP/IP protocol suite. The transport protocol used in a particular situation depends on the concerned application.\par
The first implementation of TCP, simply called TCP, was succeeded by a new version: TCP Tahoe. These two versions share the fundamental rules of information transportation, but differ in the solutions. This has led to the expression 'TCP clones'. TCP clones is an expression used for talking about different versions of TCP, considering they all share the same basic functions and purpose.\par
There are many implementations of TCP, each operating slightly differently and even some with significant problems. There are numbers of variants of TCP that are currently deployed. Such as Tahoe, Reno, New Reno, Sack, Vegas, Westwood, Fack and Veno. In this thesis we will discuss the five version of TCP that is Tahoe, Reno, New Reno, SACK and Vegas. This project will investigate the performance comparisons of these aforementioned versions of TCP and find out which one is better in which cases. 
\section[{II.}]{II.} 
\section[{Performance Metrics}]{Performance Metrics}\par
Performance metric is one type of parameter. Setting this parameter we have calculated throughput which indicates the performance of the protocol. In this paper five different parameters have been used for measuring the performance of each protocol. These metrics or parameters are briefly described in the following section: ? Bandwidth: The number of packets in transit for every time instant (sec TCP/IP is considered to be a five layer system: the physical layer, the link layer, the network layer, the Using these above metrics which are called performance metrics this project calculates throughput. The throughput can be defined TCP, Tahoe, Reno, New Reno, Sack, Vegas. 
\section[{Global Journal of Computer Science and Technology}]{Global Journal of Computer Science and Technology}\par
Volume XIII Issue XVI Version I Throughput: How well does the network deliver packets from source to destination? i.e. Throughput =[total sent data-total retransmit data]/time Throughput generally represents in Mbps. It may also be expressed by Bps (Bytes per sec). 
\section[{III.}]{III.} 
\section[{Simulation Result \& Analysis}]{Simulation Result \& Analysis}\par
The network topology as shown in Figure \hyperref[fig_1]{1} consist six nodes, two nodes represent as router and rest are represent as computer transreceiver station. Now two TCP agent are attached over the node N0 and N1. Then two traffic sources are attached to the node N0 and N1 that are treated as sender and two traffic sinks attached to the node N4 and N5 that are treated as receivers. We define the bandwidth between two routers N2 and N3 is 0.3 Mbps in each direction and also define the delay is 20 ms. The buffer size of the link N2 to N3 is maximum 5 packets. The FTP traffic sources like ftp0 and ftp1 has been attached to node N0 and N1 respectively. Fixing up total simulation time and starting time of traffic source ftp0 and ftp1, the <tclScript> written for one of the protocol like Tahoe is executed. After the execution of the <tclScript> we get a trace file for Tahoe. Likewise, we get more four trace files for remaining four versions of TCP like Reno, New Reno, SACK and Vegas. Based on these trace files, throughput (Bps) is calculated for each cases in every 10 seconds. The values of these throughputs with respect to time are shown in Figure \hyperref[fig_2]{2}.\par
The average network throughput as shown in Table \hyperref[tab_1]{1}.  of node N2 is maximum 20 packets. When a link is created using OTcl language; normally that link will be error less. But here we manually include an error model that inserts any percentage of error into the specified link. In order to analysis the performance of TCP versions, the error model has been inserted into the link between N2 and N3. Then the <TclScripts> like <Tahoe.tcl> are executed. After execution of the program we will get throughput of the network. This process is repeated for all of the protocols and stores the network throughput by changing the error rate. Figure \hyperref[fig_3]{3} shows the network throughput for all five protocols with respect to the error rate. Consider the topology as shown if Figure \hyperref[fig_1]{1}. In order to analysis the parameter bandwidth we will change the bandwidth of the link N2 and N3 and calculate the throughput of the network. The propagation delay and queue limit of the link N2 to N3 is 20 ms and 20 packets respectively. After execution of Figure \hyperref[fig_5]{6} shows the throughput of five TCP versions with respect to the number of traffic source. Consider the network topology as shown in Figure \hyperref[fig_1]{1}. The bandwidth of the link between N2 to N3 is fixed 1 Mbps and the queue limit of N2 is maximum 20 packets. Now we calculate the throughput of the network by changing the propagation delay of the link between N2 to N3. Figure \hyperref[fig_6]{7} shows the throughput of five TCP protocols as compared to the propagation delay. Calculate network throughput by changing the buffer size of router N2. Figure \hyperref[fig_7]{8} shows the throughput for five TCP protocol as compared to the buffer size. Sack perform well, but the throughput of Vegas is constant after some times because Vegas uses time based bandwidth estimation scheme to control its congestion window. From the Table \hyperref[tab_1]{1} we see that the average network throughput of Tahoe is less from Reno, New Reno, Sack and Vegas. The average network throughput of Vegas is better from the other four TCP versions. 
\section[{Throughput (Bps)}]{Throughput (Bps)}\par
If the link has some error then which TCP clones perform well. From the Figure \hyperref[fig_3]{3} we see the result. When the link error below 4\% then the Vegas perform better and when link error greater than 4\% then the New Reno and Sack perform well. But the network throughput will be decrease as increasing the error rate. From the Figure  {\ref 4} we see that the throughput is linearly increased as increasing the bandwidth of the link N2 to N3.\par
From the Figure \hyperref[fig_5]{6} we see that TCP Vegas is better. The throughput of TCP Vegas always better as increasing the number of traffic sources. When the number of traffic source is less than 15 then TCP Sack and TCP New Reno perform well from rest of four TCP versions. The network throughput of TCP Tahoe, Reno, New Reno and Sack is constant as increasing the number of traffic source. From the Figure \hyperref[fig_6]{7} we see that, when propagation delay is greater than 100 ms, the performance of these protocols is not good. But when propagation delay is less than 100 ms, TCP Vegas perform well. From Figure \hyperref[fig_7]{8} we also see that the performance of TCP Vegas is better as increasing the buffer size of router N2.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_1}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_2}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-4.png}
\caption{\label{fig_3}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{45}\includegraphics[]{image-5.png}
\caption{\label{fig_4}Figure 4 :Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{6}\includegraphics[]{image-6.png}
\caption{\label{fig_5}Figure 6 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{7}\includegraphics[]{image-7.png}
\caption{\label{fig_6}Figure 7 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{8}\includegraphics[]{image-8.png}
\caption{\label{fig_7}Figure 8 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{P{0.33484848484848484\textwidth}P{0.5151515151515151\textwidth}}
Tahoe\tabcellsep 34325.75\\
Reno\tabcellsep 35159.09\\
New Reno\tabcellsep 35469.69\\
Sack\tabcellsep 35462.12\\
Vegas\tabcellsep 36969.69\end{longtable} \par
 
\caption{\label{tab_1}Table 1 :}\end{figure}
 			\footnote{Performance Analysis of TCP Tahoe, Reno, New Reno, Sack and Vegas Using NS-2} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Craig Warrington Cameron and Eng (2005)]{b1}\label{b1} 	 		 			B Craig Warrington Cameron 		,  		 			Eng 		.  		\textit{Hons.) (Melb.), M.S. (Caltech), "Optical Burst Switching: Towards Feasibility},  				April 2005.  	 
\bibitem[In partial fulfillment of the requirements for the degree Master of Science (2004)]{b6}\label{b6} 	 		 IMPROVING TRANSMISSION CONTROL PROTOCOL PERFORMANCE WITH PATH ERROR RATE INFORMATION.  		\textit{In partial fulfillment of the requirements for the degree Master of Science},  				March 2004. Wesley M. Eddy.  		 			College of Engineering and Technology of Ohio University 		 	 	 (A thesis presented to the faculty of the) 
\bibitem[Michele Aylene Clark Weigle (ed.)]{b5}\label{b5} 	 		\textit{Investigating the Use of Synchronized Clocks in TCP Congestion Control by},  		Michele Aylene Clark Weigle (ed.)  		 	 
\bibitem[Peh Wee and Liang (2004)]{b0}\label{b0} 	 		\textit{Investigation of TCP Performance Over Wireless Internet},  		 			Peh Wee 		,  		 			Liang 		.  		October, 2004. ENG 4112 Research Project.  	 
\bibitem[LBL, USC/ISI, and Xerox, PARC Kevin Fall (ed.)]{b7}\label{b7} 	 		\textit{Manual The ns Manual, The VINT Project collaboration between Researchers at UC Berkeley},  		LBL, USC/ISI, and Xerox, PARC Kevin Fall (ed.)  		Editor Kannan Varadhan.  	 
\bibitem[Fall and Floyd]{b2}\label{b2} 	 		\textit{Simulation-based Comparisons of Tahoe, Reno, and SACK TCP},  		 			Kevin Fall 		,  		 			Sally Floyd 		.  		 		 			Lawrence Berkeley National Laboratory 		 	 
\bibitem[TCP Performance Simulations Using Ns2]{b4}\label{b4} 	 		\textit{TCP Performance Simulations Using Ns2},  		Johanna Antila, 51189d, TLT.  	 
\bibitem[Hallen Creutz -Redmond ()]{b3}\label{b3} 	 		‘TCP-X: An NS-2 environment for implementation and evaluation of TCP clones’.  		 			Michael Hallen Creutz -Redmond 		.  		 IR-RT-EX-0525.  	 	 		\textit{Master's Degree Project},  				 (Stockholm, Sweden)  		2005.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
