We analyze behavior of packet trains of the same packet sizes (troops), using a 1 minute OC3mon trace (taken 12/97) from the FIX-West network interconnection point.

packet troops (or trains of all one common packet size) for all sizes using oc32plenrunlength.pl.

Viewing by single packet sizes is somewhat unwieldy, so we also clustered size ranges (at bucket boundaries of 40, 80, 160, 320, 640, 1500, and < 1500 bytes), again using an oc32plenrunlengthc.pl conversion program that takes raw OC3mon trace as input.

We graph the resulting distributions of packet troop lengths for these 5 size ranges. (Note there were no packets in range 6 in this trace.) Each line in the graph reflects the number of troops, i.e., continuous sequenes of packets, all of which have size in the same range (as indicated in the legend). The last line, labelled un-class runlength in the legend, reflects packet sequences (trains) that were not ``troops'', i.e., they contained packets sizes across more than one range.

oc32plenrunlengthc2.pl is a similar program, but creates a matrix output instead, which can provide spreadsheet-compatible (or a VRML-object compatible) data set (use vsurf.pl to convert to VRML object).