Wireshark-bugs: [Wireshark-bugs] [Bug 1593] New: Enhancement to add data flow reversal counts to

Date: Tue, 8 May 2007 16:02:21 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1593

           Summary: Enhancement to add data flow reversal counts to TCP
                    statistics
           Product: Wireshark
           Version: 0.99.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: Mike.Engbrecht@xxxxxxx


Build Information:
Version 0.99.0

Copyright 1998-2006 Gerald Combs <gerald@xxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.6.9, with GLib 2.6.6, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.2.2, with ADNS, with Lua
5.1.
--
In the 'TCP Conversations' (IPv4, IPv6) statistics window, please add a column
with a count of the number of times there are TCP data flow reversals for each
conversation. 

I.e. count the number of times there is payload delivered below the TCP
protocol that is in a different direction than the last non-empty payload
packet in that same conversation. Please also document if (or not) the
implementation of this statistic includes retransmission events.

I'd suggest a statistics column header of "Flow Reversals" if you don't have a
better idea.

The intent of this statistic is to be able to predict to first order the impact
of additional application turn latencies if this same conversation were to be
mapped over various network latencies. The bandwidth information is already in
the statistic window. Adding application data flow reversal events would
support latency analysis from this same statistic window.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.