updates to the data center benchmarking drafts

Hi all,

As the submission for updates is closed until November 4th 2013, I would 
like to provide you an update of the changes we are incorporating 
additionally to the current thread regarding jitter:

A] First draft draft-dcbench-def-01 has the following changes to date:

change 'measurement' -> to 'measurement units' [all sections]
2.1 change 'latency' -> to 'latency interval'
2.1 added content:

Another possibility to summarize the four different definitions above is 
to  refer to the bit position as they normally occur: input to output.
     FILO is FL (First bit Last bit)
     FIFO is FF (First bit First bit)
     LILO is LL (Last bit Last bit)
     LIFO is LF (Last bit First bit)


2.2 Edits around FILO due to the conversation, changed it based on the 
feedback provided

3.1 added the following:

Even with the reference to RFC 3393, there are many definitions of
    "jitter" possible. The one selected for Data Center Benchmarking is
    closest to RFC 3393.

[note that we will update the current jitter conversation as well]

B] draft-bmwg-dcbench-methodology-02:

section 2.2 added the snake test for throughput as many customers may 
not have the luxury to have so many IXIA ports:

    Alternatively when a traffic generator CAN NOT be connected to all
    ports on the DUT, a snake test MUST be used for line rate testing,
    excluding latency and jitter as those became then irrelevant. The
    snake test consists in the following method: -connect the first and
    last port of the DUT to a traffic generator-connect back to back
    sequentially all the ports in between: port 2 to 3, port 4 to 5 etc
    to port n-2 to port n-1; where n is the total number of ports of the
    DUT-configure port 1 and 2 in the same vlan X, port 3 and 4 in the
    same vlan Y, etc. port n-1 and port n in the same vlan ZZZ. This
    snake test provides a capability to test line rate for Layer 2 and
    Layer 3 RFC 2544/3918 in instance where a traffic generator with only
    two ports is available. The latency and jitter are not to be
    considered with this test.

section 2.3 added the imix genome and fixed some packet size examples.

The pattern for testing can be expressed using RFC 6985 [IMIX Genome:
    Specification of Variable Packet Sizes for Additional Testing]

Also: "-for packet drops, they MUST be expressed in packet count value 
and SHOULD be expressed in % of line rate" changed to ' % of total 
transmitted frames' instead for more clarity.

section 3.1: " To measure the size of the buffer of a DUT under all 
conditions." It's not realistic so we changed "all" to 
typical|many|multiple .

Thank you for taking the time to read this.
Looking forward to read comments.

Cheers,
Lucien