Argus-2.0 byte count strategy

[Peter Van Epp]

	One thought that occurred is making the application data count the 
goodput value (i.e. acked application bytes, ignoring retransmissions, 
delivered to the application) with the -A flag. That would allow a comparison 
of traffic (the default count value) to goodput (real throughput) on a link 
which would be an application that I think would be useful. A drop in the ratio
for instance would signal an impairment on the link (i.e. likely 
retransmissions). Comments from other folks? Does someone see a need for 
application only data count including retransmissions?

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada