= Router Workload =

We want to design a MobilityFirst workload that can be used to test the performance of various MF router implementations, such as the [https://mobilityfirst.orbit-lab.org/wiki/SystemPrototyping/Projects/ClickRouter CLICK software router], the [https://mobilityfirst.orbit-lab.org/wiki/SystemPrototyping/Projects/SDNOpenFlow OpenFlow based] set up and the [https://mobilityfirst.orbit-lab.org/wiki/SystemPrototyping/Projects/NetFPGARouter netFPGA router]. The workload should have an appropriate distribution of traffic classes that will go through GNRS look up, storage etc. The arrival rate of the data itself can either be from a synthetic traffic generator or trace based.

== Synthetic Traffic Generator ==

A source that can generate MobilityFirst traffic with the traffic class distribution and arrival rate desired by the user. The following are some parameters of the traffic generator that can be tweaked by the user to control the traffic.
1. Arrival rate of data/gap between chunks
2. service ID distribution of the chunks - used to force a GNRS look up or storage
3. chunk size ??

== Trace Based Traffic Generator ==

A real world trace is used to drive the traffic generator. Existing list of traces:
1. [http://traces.cs.umass.edu/index.php/Network/Network YouTube request response]  trace from UMass. 

The arrival rate is determined by the time stamps in the trace file. However, the traffic class distribution should still be under the control of the user.