node119.html

相关搜索: ns2仿真结果分析 all-awk ns2 ns2 无限网络中awk文件 ... [2.tcl.rar] - 在ns2平台上实现对AODV协议的模拟

<P>
State Variables are:
<DL>
<DT><STRONG>dupacks_</STRONG></DT>
<DD>Number of duplicate acks seen since any new data was acknowledged. 

<P>
</DD>
<DT><STRONG>seqno_</STRONG></DT>
<DD>Highest sequence number for data from data source to TCP. 

<P>
</DD>
<DT><STRONG>t_seqno_</STRONG></DT>
<DD>Current transmit sequence number. 

<P>
</DD>
<DT><STRONG>ack_</STRONG></DT>
<DD>Highest acknowledgment seen from receiver. cwnd_
Current value of the congestion window. 

<P>
</DD>
<DT><STRONG>awnd_</STRONG></DT>
<DD>Current value of a low-pass filtered version of the congestion window. For
investigations of different window-increase algorithms. 

<P>
</DD>
<DT><STRONG>ssthresh_</STRONG></DT>
<DD>Current value of the slow-start threshold. 

<P>
</DD>
<DT><STRONG>rtt_</STRONG></DT>
<DD>Round-trip time estimate. 

<P>
</DD>
<DT><STRONG>srtt_</STRONG></DT>
<DD>Smoothed round-trip time estimate. 

<P>
</DD>
<DT><STRONG>rttvar_</STRONG></DT>
<DD>Round-trip time mean deviation estimate. 

<P>
</DD>
<DT><STRONG>backoff_</STRONG></DT>
<DD>Round-trip time exponential backoff constant. 
</DD>
</DL>

<P>
</DD>
<DT><STRONG>TCP/Reno Objects</STRONG></DT>
<DD>TCP/Reno objects are a subclass of TCP objects that implement the Reno TCP
transport protocol described in paper: "Fall, K., and Floyd, S.
Comparisons of Tahoe, Reno, and Sack TCP. December 1995." URL ftp://
ftp.ee.lbl.gov/papers/sacks.ps.Z. There are no methods,
configuration parameters or state variables specific to this object. 

<P>
</DD>
<DT><STRONG>TCP/Newreno Objects</STRONG></DT>
<DD>TCP/Newreno objects are a subclass of TCP objects that implement a
modified version of the BSD Reno TCP transport protocol. 
There are no methods or state variables specific to this object. 

<P>
Configuration Parameters are:
<DL>
<DT><STRONG>newreno_changes_</STRONG></DT>
<DD>Set to zero for the default New Reno described in "Fall, K., and Floyd, S.
Comparisons of Tahoe, Reno, and Sack TCP. December 1995". Set to 1 for
additional New Reno algorithms [see Hoe, J., Improving the Start-up
Behavior of a Congestion Control Scheme for TCP. in SIGCOMM 96, August
1996, pp. 270-280. URL 
http://www.acm.org/sigcomm/sigcomm96/papers/hoe.html.]; this includes the
estimation of the ssthresh parameter during slow-start. 
</DD>
</DL>

<P>
</DD>
<DT><STRONG>TCP/Vegas Objects</STRONG></DT>
<DD>There are no methods or configuration parameters specific to this
object. State variables are:

<UL>
<LI>v_alpha_
</LI>
<LI>v_beta_
</LI>
<LI>v_gamma_
</LI>
<LI>v_rtt_
</LI>
</UL>

<P>
</DD>
<DT><STRONG>TCP/Sack1 Objects</STRONG></DT>
<DD>TCP/Sack1 objects are a subclass of TCP objects that implement the BSD
Reno TCP transport protocol with Selective Acknowledgement Extensions
described in "Fall, K., and Floyd, S. Comparisons of Tahoe, Reno, and
Sack TCP. December 1995". URL ftp:// ftp.ee.lbl.gov/papers/sacks.ps.Z. 
They inherit all of the TCP object functionality. There are no methods,
configuration parameters or state variables specific to this object. 

<P>
</DD>
<DT><STRONG>TCP/FACK Objects</STRONG></DT>
<DD>TCP/Fack objects are a subclass of TCP objects that implement the BSD Reno
TCP transport protocol with Forward Acknowledgement congestion control. 
They inherit all of the TCP object functionality. There are no methods or
state variables specific to this object. 

<P>
Configuration Parameters are:
<DL>
<DT><STRONG>ss-div4</STRONG></DT>
<DD>Overdamping algorithm. Divides ssthresh by 4 (instead of 2) if congestion
is detected within 1/2 RTT of slow-start. (1=Enable, 0=Disable) 

<P>
</DD>
<DT><STRONG>rampdown</STRONG></DT>
<DD>Rampdown data smoothing algorithm. Slowly reduces congestion window rather
than instantly halving it. (1=Enable, 0=Disable) 
</DD>
</DL>

<P>
</DD>
<DT><STRONG>TCP/FULLTCP Objects</STRONG></DT>
<DD>This section has not yet been added here. The implementation
and the configuration parameters are described in paper: "Fall, K.,
Floyd, S., and Henderson, T., Ns Simulator Tests for Reno FullTCP.
July, 1997." URL ftp://ftp.ee.lbl.gov/papers/fulltcp.ps. 

<P>
</DD>
<DT><STRONG>TCPSINK Objects</STRONG></DT>
<DD>TCPSink objects are a subclass of agent objects that implement a receiver
for TCP packets. The simulator only implements "one-way" TCP connections,
where the TCP source sends data packets and the TCP sink sends ACK
packets. TCPSink objects inherit all of the generic agent functionality.
There are no methods or state variables specific to the TCPSink object. 
Configuration Parameters are
<DL>
<DT><STRONG>packetSize_</STRONG></DT>
<DD>The size in bytes to use for all acknowledgment packets. 

<P>
</DD>
<DT><STRONG>maxSackBlocks_</STRONG></DT>
<DD>The maximum number of blocks of data that can be acknowledged in a SACK
option. For a receiver that is also using the time stamp option [RFC
1323], the SACK option specified in RFC 2018 has room to include three
SACK blocks. This is only used by the TCPSink/Sack1 subclass. This value
may not be increased within any particular TCPSink object after that
object has been allocated. (Once a TCPSink object has been allocated, the
value of this parameter may be decreased but not increased). 
</DD>
</DL>

<P>
</DD>
<DT><STRONG>TCPSINK/DELACK Objects</STRONG></DT>
<DD>DelAck objects are a subclass of TCPSink that implement a delayed-ACK
receiver for TCP packets. They inherit all of the TCPSink object
functionality. There are no methods or state variables specific to the
DelAck object. 
Configuration Parameters are:
<DL>
<DT><STRONG>interval_</STRONG></DT>
<DD>The amount of time to delay before generating an acknowledgment for a
single packet. If another packet arrives before this time expires,
generate an acknowledgment immediately. 
</DD>
</DL>

<P>
</DD>
<DT><STRONG>TCPSINK/SACK1 Objects</STRONG></DT>
<DD>TCPSink/Sack1 objects are a subclass of TCPSink that implement a SACK
receiver for TCP packets. They inherit all of the TCPSink object
functionality. There are no methods, configuration parameters or state
variables specific to this object. 

<P>
</DD>
<DT><STRONG>TCPSINK/SACK1/DELACK Objects</STRONG></DT>
<DD>TCPSink/Sack1/DelAck objects are a subclass of TCPSink/Sack1 that
implement a delayed-SACK receiver for TCP packets. They inherit all of the
TCPSink/Sack1 object functionality. There are no methods or state
variables specific to this object. 
Configuration Parameters are:
<DL>
<DT><STRONG>interval_</STRONG></DT>
<DD>The amount of time to delay before generating an acknowledgment for a
single packet. If another packet arrives before this time expires,
generate an acknowledgment immediately. 
</DD>
</DL>
</DD>
</DL>

<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html3124"
  HREF="node120.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node120.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
 SRC="file:/usr/share/latex2html/icons/next.png"></A> 
<A NAME="tex2html3118"
  HREF="node99.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node99.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
 SRC="file:/usr/share/latex2html/icons/up.png"></A> 
<A NAME="tex2html3112"
  HREF="node118.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node118.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
 SRC="file:/usr/share/latex2html/icons/prev.png"></A> 
<A NAME="tex2html3120"
  HREF="node1.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents"
 SRC="file:/usr/share/latex2html/icons/contents.png"></A> 
<A NAME="tex2html3122"
  HREF="node590.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node590.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index"
 SRC="file:/usr/share/latex2html/icons/index.png"></A> 
<BR>
<B> Next:</B> <A NAME="tex2html3125"
  HREF="node120.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node120.html">10.9 Commands at a</A>
<B> Up:</B> <A NAME="tex2html3119"
  HREF="node99.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node99.html">10. Agents</A>
<B> Previous:</B> <A NAME="tex2html3113"
  HREF="node118.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node118.html">10.7 The Agent API</A>
 &nbsp <B>  <A NAME="tex2html3121"
  HREF="node1.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node1.html">Contents</A></B> 
 &nbsp <B>  <A NAME="tex2html3123"
  HREF="node590.html" tppabs="http://www.isi.edu/nsnam/ns/doc/node590.html">Index</A></B> 
<!--End of Navigation Panel-->
<ADDRESS>

2003-09-23
</ADDRESS>
</BODY>
</HTML>