Anue Systems Inc1 v Telecommunications Industry AssociationTR-30.3/ Via Teleconference, January 5, 2009

Model updates since last meeting Modified the Packet object to support carrying an optional payload. Before, the model only carried the length of the packet. Now it can also carry content, for example from a PCAP generator or from some other source Added a method to the Switch object to allow setting a forwarding rule for a range of destination addresses. This makes it easy to create a range of destinations within a home, for example two PCs and three STBs with consecutive addreses and then program the switches in the model to forward packets for all of these destinations similarly (except, of course, the last switch/firewall). Anue Systems Inc2

Model updates since last meeting (cont.) Modified the PacketGeneratorPCAP object to read and include the PCAP packet body in packets in the simulation. Created a new monitor type, PacketMonitorPCAP which “catches” packets and does two things –Creates an output PCAP file containing the packet bodies and timestamps. This can be used as input to subsequent analysis. –Creates and output CSV text file containing the delay and packet loss statistics. This is needed because PCAP files have no way to include information about packet delay and loss (other than analyzing the packets themselves, which may have its own limitations). Anue Systems Inc3

Model updates since last meeting (cont.) Modify the CORE2LAN test bench as follows –Define new dest addr for PC1, PC2, STB1-STB3 in the home –Change the sizes of the forwarding tables from 100 to 1000 –Use the new “range-based” forwarding rule method to set up forwarding rules for all five of these destinations in one call [except, of course in the last Switch instance]. –Change the PCAP generators to use the new “real” –Add new PCAP monitors, connect them up and debug. Anue Systems Inc4

Model updates since last meeting (cont.) Add YouTube, Hulu and BitTorrent PCAP files to the source code (but not yet used) Anue Systems Inc5