| | 2 | Tmix generates realistic TCP traffic by "replaying" a TCP/IP header trace collected from a real link. This page will give more details on Tmix, and how it generates traffic. |
| | 3 | |
| | 4 | == The a-b-t Model == |
| | 5 | A TCP/IP header trace is obtained from a real-world link, and is then "reverse compiled" into a higher-level representation. For every TCP/IP connection in the trace a connection vector is generated. The connection vector represents an entire single connection between "a", the connection initiator, and "b", the connection accepter. Rather than modeling the individual packets or TCP segments, Tmix instead uses inferences to characterize connections as a sequence of request-response exchanges between "a" and "b". Each exchange is called an epoch. An epoch includes a<sub>i</sub> |
| | 6 | |
| | 7 | Note that Tmix does not require any knowledge about what the application layer, or application layer headers. |
| | 8 | |
| | 9 | Note that the data units used in this model are not packets or TCP segments, but rather objects or protocol elements. |
