draft-ietf-bmwg-imix-genome-03.txt   draft-ietf-bmwg-imix-genome-04.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft AT&T Labs Internet-Draft AT&T Labs
Intended status: Informational November 11, 2012 Intended status: Informational December 12, 2012
Expires: May 15, 2013 Expires: June 15, 2013
IMIX Genome: Specification of variable packet sizes for additional IMIX Genome: Specification of variable packet sizes for additional
testing testing
draft-ietf-bmwg-imix-genome-03 draft-ietf-bmwg-imix-genome-04
Abstract Abstract
Benchmarking Methodologies have always relied on test conditions with Benchmarking Methodologies have always relied on test conditions with
constant packet sizes, with the goal of understanding what network constant packet sizes, with the goal of understanding what network
device capability has been tested. Tests with constant packet size device capability has been tested. Tests with constant packet size
reveal device capabilities but differ significantly from the reveal device capabilities but differ significantly from the
conditions encountered in operational deployment, and so additional conditions encountered in operational deployment, and so additional
tests are sometimes conducted with a mixture of packet sizes, or tests are sometimes conducted with a mixture of packet sizes, or
"IMIX". The mixture of sizes a networking device will encounter is "IMIX". The mixture of sizes a networking device will encounter is
skipping to change at page 2, line 6 skipping to change at page 2, line 6
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 15, 2013. This Internet-Draft will expire on June 15, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 6, line 37 skipping to change at page 6, line 37
constraints. constraints.
o Non-RFC2544 packet sizes would need to be approximated by those o Non-RFC2544 packet sizes would need to be approximated by those
available in the table. available in the table.
o The Genome for very long sequences can become undecipherable by o The Genome for very long sequences can become undecipherable by
humans. humans.
o z=MTU is seen as valuable, so MTU MUST be specified if used. o z=MTU is seen as valuable, so MTU MUST be specified if used.
o Whether more tabulated packet sizes would be useful is TBD, and o "jumbo" sizes are included.
"jumbo" sizes were added in this version.
Some questions testers must ask and answer when using the IMIX Genome Some questions testers must ask and answer when using the IMIX Genome
are: are:
1. Multiple Source-Destination Address Pairs: is the IMIX sequence 1. Multiple Source-Destination Address Pairs: is the IMIX sequence
applicable to each pair, across multiple pairs in sets, or across applicable to each pair, across multiple pairs in sets, or across
all pairs? all pairs?
2. Multiple Tester Ports: is the IMIX sequence applicable to each 2. Multiple Tester Ports: is the IMIX sequence applicable to each
port, across multiple ports in sets, or across all ports? port, across multiple ports in sets, or across all ports?
skipping to change at page 7, line 13 skipping to change at page 7, line 13
form: form:
+-----------------------+-------------------------+-----------------+ +-----------------------+-------------------------+-----------------+
| Source | Destination | Corresponding | | Source | Destination | Corresponding |
| Address/Port/Blade | Address/Port/Blade | IMIX | | Address/Port/Blade | Address/Port/Blade | IMIX |
+-----------------------+-------------------------+-----------------+ +-----------------------+-------------------------+-----------------+
| x.x.x.x Blade2 | y.y.y.y Blade3 | IMIX - aaafg | | x.x.x.x Blade2 | y.y.y.y Blade3 | IMIX - aaafg |
+-----------------------+-------------------------+-----------------+ +-----------------------+-------------------------+-----------------+
where testers can specify the IMIX used between any two entities in where testers can specify the IMIX used between any two entities in
the test architecture. the test architecture (and Blade is a component in a multi-component
device chassis).
4. Specification of a Custom IMIX 4. Specification of a Custom IMIX
The Custom IMIX is specified in the following format: The Custom IMIX is specified in the following format:
CUSTOM IMIX - 123456...x CUSTOM IMIX - 123456...x
where each number is replaced by the letter corresponding to the size where each number is replaced by the letter corresponding to the size
of the packet at that position in the sequence. The tester MUST of the packet at that position in the sequence. The tester MUST
complete the following table, giving the letter encoding for each complete the following table, giving the letter encoding for each
skipping to change at page 7, line 40 skipping to change at page 7, line 41
| aaa | A | | aaa | A |
| bbb | B | | bbb | B |
| ccc | C | | ccc | C |
| ddd | D | | ddd | D |
| eee | E | | eee | E |
| fff | F | | fff | F |
| ggg | G | | ggg | G |
| etc. | up to Z | | etc. | up to Z |
+-------------+--------------------+ +-------------+--------------------+
For example: a five packet sequence with sizes aaa,aaa,aaa,ggg,ggg For example: a five packet sequence with sizes
would be designated: aaa=64,aaa=64,aaa=64,ggg=1020,ggg=1020 would be designated:
CUSTOM IMIX - AAAGG CUSTOM IMIX - AAAGG
5. Reporting Long or Pseudo-Random Packet Sequences 5. Reporting Long or Pseudo-Random Packet Sequences
When the IMIX-Genome cannot be used (when the sheer length of the When the IMIX-Genome cannot be used (when the sheer length of the
sequence would make the genome unmanageable), two options are sequence would make the genome unmanageable), two options are
possible. When a sequence can be decomposed into a series of short possible. When a sequence can be decomposed into a series of short
repeating sequences, then a run-length encoding approach MAY be used repeating sequences, then a run-length encoding approach MAY be used
as shown below: as shown below:
 End of changes. 6 change blocks. 
9 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/