Re: Benoit Claise's No Objection on draft-ietf-bmwg-imix-genome-04: (with COMMENT)

"MORTON JR., ALFRED C (AL)" <[email protected]>
Newsgroups gmane.ietf.bmwg
Message-ID <F1312FAF1A1E624DA0972D1C9A91379A1C9F46A0FD@njfpsrvexg7.research.att.com>
Hi Benoit, 
thanks for your comments, minimal replies where needed below.
Al

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Benoit Claise
...
> COMMENT:
> ... Please engage in the discussion.
> 
> 
> -  z=MTU is seen as valuable, so MTU MUST be specified if used.
> Where? by whom? The tester? Following Section 4 " The tester MUST
> complete the following table" example", you might need something such as:
> 
>     If the z (MTU) is used, the tester MUST specifiy the MTU value in the
> report

acm - I have added the sentence above (with slight clarification, see below),
and appended the following sentence to the scope and goals in section 2, 
which should help to clarify the role of the document:

Thus, the requirements presented in this specification, expressed in 
[RFC2119] terms, are intended for those performing/reporting laboratory 
tests to improve clarity and repeatability.


> 
> - While this approach allows some flexibility, there are also
>    constraints.
> 
>    o  Non-RFC2544 packet sizes would need to be approximated by those
>       available in the table.
> 
>    o  The Genome for very long sequences can become undecipherable by
>       humans.
> 
>    o  z=MTU is seen as valuable, so MTU MUST be specified if used.
> 
>    o  "jumbo" sizes are included.
> 
> "jumbo" sizes are included: is this a constraint or an advantage? I
> thought it was an advantage.

acm - it is, but it evolved from a constraint when jumbo sizes were
 not included.
 Removed that last two bullets, above.


<editorial change fixed>

> 
> -
>    +-----------------------+-------------------------+-----------------+
>    | Source                | Destination             | Corresponding   |
>    | Address/Port/Blade    | Address/Port/Blade      | IMIX            |
>    +-----------------------+-------------------------+-----------------+
>    | x.x.x.x Blade2        | y.y.y.y Blade3          | IMIX - aaafg    |
>    +-----------------------+-------------------------+-----------------+
> 
> I don't see the port in the examples.
> Maybe you meant Address/{Port|Blade} ?
> Or maybe you meant Address/{Port AND/OR Blade} ?

acm - Address + (Port AND/OR Blade)


> 
> - Section 4.
> The custom IMIX can use the MTU size, by setting it up in the Genome.
> However, the MTU semantic is not conveyed.
> Is this intentional? I was thinking that Z would be the MTU, with the
> constraint that the tester MUST specify the MTU value in the report?

acm - the sentence that covers this now reads:
   If z (MTU) is used, the tester MUST specify the length of the MTU 
   in the report.

(so the MTU semantic remains in the table)

> 
> - Section 4.
> Isn't it an issue that only 26 discrete values are possible?

acm - even if a sequence of different sizes is too long to describe,
the packet sizes are usually chosen from bins in a histogram and 
therefore some summarization of lengths.

At the end of Section 5, we have provisions for pseudo-random
packet size generation, where the algorithm and seed need to be
specified.  The size generation you mention below:

> Don't we have test for which the packet size increases by 1
> monotonically?

acm - could also be included, but we didn't have this suggestion previously
and it would seem fairly obvious how to report the method, as
you've done above.

   If a deterministic packet size generation method is used (such as 
   monotonic increase by one octet from start value to MTU), then the
   generation algorithm SHOULD be reported.


> 
> - Section 5
> I guess that the sentence "When a sequence can be decomposed into a
> series of short repeating sequences, then a run-length encoding approach
> MAY be used as shown below:" can also apply to custom IMIX. The example
> doesn't show it. If this is the case, you should mention it.

acm - yes, added that point.

> 
> Editorial
> "Genome" versus "genome" throughout document
> 

acm - ok

> 
> _______________________________________________
> bmwg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/bmwg

_______________________________________________
bmwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bmwg
Diff-bmwg-imix-genome-04-05prelim.htm (text/html, 62.6 KB)
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.41: rfcdiff  --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Linux cabernet 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 GNU/Linux --> 
<!-- Using awk: /usr/bin/gawk: GNU Awk 3.1.8 --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 3.2 --> 
<!-- Using wdiff: /usr/bin/wdiff: wdiff (GNU wdiff) 0.6.5 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: draft-ietf-bmwg-imix-genome-04.txt - draft-ietf-bmwg-imix-genome-05prelim.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th><a href="/rfcdiff?url2=draft-ietf-bmwg-imix-genome-04.txt" style="color:#008; text-decoration:none;">&lt;</a>&nbsp;<a href="/html/draft-ietf-bmwg-imix-genome-04.txt" style="color:#008">draft-ietf-bmwg-imix-genome-04.txt</a>&nbsp;</th><th> </th><th>&nbsp;<a href="/html/draft-ietf-bmwg-imix-genome-05prelim.txt" style="color:#008">draft-ietf-bmwg-imix-genome-05prelim.txt</a>&nbsp;<a href="/rfcdiff?url1=draft-ietf-bmwg-imix-genome-05prelim.txt" style="color:#008; text-decoration:none;">&gt;</a></th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Network Working Group                                          A. Morton</td><td> </td><td class="right">Network Working Group                                          A. Morton</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                 AT&amp;T Labs</td><td> </td><td class="right">Internet-Draft                                                 AT&amp;T Labs</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Intended status: Informational                         <span class="delete">December 12, 2012</span></td><td> </td><td class="rblock">Intended status: Informational                              <span class="insert">May 28, 2013</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">June 15,</span> 2013</td><td> </td><td class="rblock">Expires: <span class="insert">November 29,</span> 2013</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IMIX Genome: Specification of variable packet sizes for additional</td><td> </td><td class="right">   IMIX Genome: Specification of variable packet sizes for additional</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                testing</td><td> </td><td class="right">                                testing</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                     draft-ietf-bmwg-imix-genome-0<span class="delete">4</span></td><td> </td><td class="rblock">                     draft-ietf-bmwg-imix-genome-0<span class="insert">5 PRELIM</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Benchmarking Methodologies have always relied on test conditions with</td><td> </td><td class="right">   Benchmarking Methodologies have always relied on test conditions with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   constant packet sizes, with the goal of understanding what network</td><td> </td><td class="right">   constant packet sizes, with the goal of understanding what network</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   device capability has been tested.  Tests with constant packet size</td><td> </td><td class="right">   device capability has been tested.  Tests with constant packet size</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   reveal device capabilities but differ significantly from the</td><td> </td><td class="right">   reveal device capabilities but differ significantly from the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   conditions encountered in operational deployment, and so additional</td><td> </td><td class="right">   conditions encountered in operational deployment, and so additional</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   tests are sometimes conducted with a mixture of packet sizes, or</td><td> </td><td class="right">   tests are sometimes conducted with a mixture of packet sizes, or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   "IMIX".  The mixture of sizes a networking device will encounter is</td><td> </td><td class="right">   "IMIX".  The mixture of sizes a networking device will encounter is</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 1, line 36</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 1, line 36</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   defines a way to specify the exact repeating sequence of packet sizes</td><td> </td><td class="right">   defines a way to specify the exact repeating sequence of packet sizes</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   from the usual set of fixed sizes, and other forms of mixed size</td><td> </td><td class="right">   from the usual set of fixed sizes, and other forms of mixed size</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   specification.</td><td> </td><td class="right">   specification.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Requirements Language</td><td> </td><td class="right">Requirements Language</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td> </td><td class="right">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document are to be interpreted as described in RFC 2119 [RFC2119].</td><td> </td><td class="right">   document are to be interpreted as described in RFC 2119 [RFC2119].</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Status of <span class="delete">t</span>his Memo</td><td> </td><td class="rblock">Status of <span class="insert">T</span>his Memo</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This Internet-Draft is submitted in full conformance with the</td><td> </td><td class="right">   This Internet-Draft is submitted in full conformance with the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   provisions of BCP 78 and BCP 79.</td><td> </td><td class="right">   provisions of BCP 78 and BCP 79.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                        </td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">November 29,</span> 2013.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">June 15,</span> 2013.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Copyright (c) 201<span class="delete">2</span> IETF Trust and the persons identified as the</td><td> </td><td class="rblock">   Copyright (c) 201<span class="insert">3</span> IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   carefully, as they describe your rights and restrictions with respect</td><td> </td><td class="right">   carefully, as they describe your rights and restrictions with respect</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to this document.  Code Components extracted from this document must</td><td> </td><td class="right">   to this document.  Code Components extracted from this document must</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   include Simplified BSD License text as described in Section 4.e of</td><td> </td><td class="right">   include Simplified BSD License text as described in Section 4.e of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Trust Legal Provisions and are provided without warranty as</td><td> </td><td class="right">   the Trust Legal Provisions and are provided without warranty as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   described in the Simplified BSD License.</td><td> </td><td class="right">   described in the Simplified BSD License.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Table of Contents</td><td> </td><td class="right">Table of Contents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">.  4</span></td><td> </td><td class="rblock">   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <span class="insert">2</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  Scope and Goals  . . . . . . . . . . . . . . . . . . . . . . .  <span class="delete">4</span></td><td> </td><td class="rblock">   2.  Scope and Goals . . . . . . . . . . . . . . . . . . . . . . .   <span class="insert">3</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  Specification of the IMIX Genome . . . . . . . . . . . . . . <span class="delete">.  5</span></td><td> </td><td class="rblock">   3.  Specification of the IMIX Genome  . . . . . . . . . . . . . .   <span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   4.  Specification of a Custom IMIX . . . . . . . . . . . . . . . <span class="delete">.  7</span></td><td> </td><td class="rblock">   4.  Specification of a Custom IMIX  . . . . . . . . . . . . . . .   <span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   5.  Reporting Long or Pseudo-Random Packet Sequences . . . . . . <span class="delete">.  7</span></td><td> </td><td class="rblock">   5.  Reporting Long or Pseudo-Random Packet Sequences  . . . . . .   <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  <span class="delete">8</span></td><td> </td><td class="rblock">   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  <span class="delete">9</span></td><td> </td><td class="rblock">   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <span class="delete">.  9</span></td><td> </td><td class="rblock">   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">.  9</span></td><td> </td><td class="rblock">   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     9.1.  Normative References . . . . . . . . . . . . . . . . . . <span class="delete">.  9</span></td><td> </td><td class="rblock">     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   <span class="insert">7</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">     9.2.  Informative References . . . . . . . . . . . . . . . . . <span class="delete">.  9</span></td><td> </td><td class="rblock">     9.2.  Informative References  . . . . . . . . . . . . . . . . .   <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <span class="delete">. 10</span></td><td> </td><td class="rblock">   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This memo defines a method to unambiguously specify the sequence of</td><td> </td><td class="right">   This memo defines a method to unambiguously specify the sequence of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   packet sizes used in a load test.</td><td> </td><td class="right">   packet sizes used in a load test.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Benchmarking Methodologies [RFC2544] have always relied on test</td><td> </td><td class="right">   Benchmarking Methodologies [RFC2544] have always relied on test</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   conditions with constant packet sizes, with the goal of understanding</td><td> </td><td class="right">   conditions with constant packet sizes, with the goal of understanding</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   what network device capability has been tested.  Tests with the</td><td> </td><td class="right">   what network device capability has been tested.  Tests with the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   smallest size stress the header processing capacity, and tests with</td><td> </td><td class="right">   smallest size stress the header processing capacity, and tests with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 5, line 21</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 3, line 51</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   other circumstances.</td><td> </td><td class="right">   other circumstances.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   While documentation of the exact sequence is ideal, the memo also</td><td> </td><td class="right">   While documentation of the exact sequence is ideal, the memo also</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   covers the case where the sequence of sizes is very long or may be</td><td> </td><td class="right">   covers the case where the sequence of sizes is very long or may be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   generated by a pseudo-random process.</td><td> </td><td class="right">   generated by a pseudo-random process.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   It is a colossal non-goal to standardize one or more versions of the</td><td> </td><td class="right">   It is a colossal non-goal to standardize one or more versions of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IMIX.  This topic has been discussed on many occasions on the bmwg-</td><td> </td><td class="right">   IMIX.  This topic has been discussed on many occasions on the bmwg-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   list[IMIXonList].  The goal is to enable customization with minimal</td><td> </td><td class="right">   list[IMIXonList].  The goal is to enable customization with minimal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   constraints while fostering repeatable testing once the fixed size</td><td> </td><td class="right">   constraints while fostering repeatable testing once the fixed size</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   testing is complete.</td><td> </td><td class="rblock">   testing is complete.  <span class="insert">Thus, the requirements presented in this</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   specification, expressed in [RFC2119] terms, are intended for those</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   performing/reporting laboratory tests to improve clarity and</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   repeatability.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">3.  Specification of the IMIX Genome</td><td> </td><td class="right">3.  Specification of the IMIX Genome</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The IMIX Genome is specified in the following format:</td><td> </td><td class="right">   The IMIX Genome is specified in the following format:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IMIX - 123456...x</td><td> </td><td class="right">   IMIX - 123456...x</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   where each number is replaced by the letter corresponding to the size</td><td> </td><td class="right">   where each number is replaced by the letter corresponding to the size</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   of the packet at that position in the sequence.  The following table</td><td> </td><td class="right">   of the packet at that position in the sequence.  The following table</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   gives the letter encoding for the [RFC2544] standard sizes (64, 128,</td><td> </td><td class="right">   gives the letter encoding for the [RFC2544] standard sizes (64, 128,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 6, line 26</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 4, line 42</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                   | 9000        | i                  |</td><td> </td><td class="right">                   | 9000        | i                  |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                   | 16000       | j                  |</td><td> </td><td class="right">                   | 16000       | j                  |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                   | MTU         | z                  |</td><td> </td><td class="right">                   | MTU         | z                  |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                   +-------------+--------------------+</td><td> </td><td class="right">                   +-------------+--------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   For example: a five packet sequence with sizes 64,64,64,1280,1518</td><td> </td><td class="right">   For example: a five packet sequence with sizes 64,64,64,1280,1518</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   would be designated:</td><td> </td><td class="right">   would be designated:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   IMIX - aaafg</td><td> </td><td class="right">   IMIX - aaafg</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0008" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">If z (MTU) is used, the tester MUST specify the length of the MTU in</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   the report.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                        </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   While this approach allows some flexibility, there are also</td><td> </td><td class="right">   While this approach allows some flexibility, there are also</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   constraints.</td><td> </td><td class="right">   constraints.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  Non-RFC2544 packet sizes would need to be approximated by those</td><td> </td><td class="right">   o  Non-RFC2544 packet sizes would need to be approximated by those</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      available in the table.</td><td> </td><td class="right">      available in the table.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   o  The Genome for very long sequences can become undecipherable by</td><td> </td><td class="right">   o  The Genome for very long sequences can become undecipherable by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      humans.</td><td> </td><td class="right">      humans.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0009" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">o  z=MTU is seen as valuable, so MTU MUST be specified if used.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  "jumbo" sizes are included.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                        </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Some questions testers must ask and answer when using the IMIX Genome</td><td> </td><td class="right">   Some questions testers must ask and answer when using the IMIX Genome</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   are:</td><td> </td><td class="right">   are:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Multiple Source-Destination Address Pairs: is the IMIX sequence</td><td> </td><td class="right">   1.  Multiple Source-Destination Address Pairs: is the IMIX sequence</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       applicable to each pair, across multiple pairs in sets, or across</td><td> </td><td class="right">       applicable to each pair, across multiple pairs in sets, or across</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       all pairs?</td><td> </td><td class="right">       all pairs?</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Multiple Tester Ports: is the IMIX sequence applicable to each</td><td> </td><td class="right">   2.  Multiple Tester Ports: is the IMIX sequence applicable to each</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">       port, across multiple ports in sets, or across all ports?</td><td> </td><td class="right">       port, across multiple ports in sets, or across all ports?</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0010" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   The chosen configuration would be expressed the following general</td><td> </td><td class="rblock">   The chosen configuration would be expressed <span class="insert">in </span>the following general</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   form:</td><td> </td><td class="right">   form:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0011" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+-----------------------+-------------------------+-----------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+-------------------------+---------------------+</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   | Source                | Destination             | Corresponding   |</td><td> </td><td class="rblock">   | Source <span class="insert">Address +</span>  | Destination <span class="insert">Address +</span>   | Corresponding <span class="insert">IMIX</span>  |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   | <span class="delete">Address/Port/Blade</span>    | <span class="delete">Address/Port/Blade</span>      | <span class="delete">IMIX</span>            |</td><td> </td><td class="rblock">   | <span class="insert">Port AND/OR Blade</span> | <span class="insert">Port AND/OR Blade</span>       |                     |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+-----------------------+-------------------------+-----------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+-------------------------+---------------------+</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   | x.x.x.x Blade2        | y.y.y.y Blade3          | IMIX - aaafg    |</td><td> </td><td class="rblock">   | x.x.x.x Blade2    | y.y.y.y Blade3          | IMIX - aaafg        |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">+-----------------------+-------------------------+-----------------+</span></td><td> </td><td class="rblock">   <span class="insert">+-------------------+-------------------------+---------------------+</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   where testers can specify the IMIX used between any two entities in</td><td> </td><td class="right">   where testers can specify the IMIX used between any two entities in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the test architecture (and Blade is a component in a multi-component</td><td> </td><td class="right">   the test architecture (and Blade is a component in a multi-component</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   device chassis).</td><td> </td><td class="right">   device chassis).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.  Specification of a Custom IMIX</td><td> </td><td class="right">4.  Specification of a Custom IMIX</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The Custom IMIX is specified in the following format:</td><td> </td><td class="right">   The Custom IMIX is specified in the following format:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   CUSTOM IMIX - 123456...x</td><td> </td><td class="right">   CUSTOM IMIX - 123456...x</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 7, line 49</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 6, line 17</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                   +-------------+--------------------+</td><td> </td><td class="right">                   +-------------+--------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   For example: a five packet sequence with sizes</td><td> </td><td class="right">   For example: a five packet sequence with sizes</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   aaa=64,aaa=64,aaa=64,ggg=1020,ggg=1020 would be designated:</td><td> </td><td class="right">   aaa=64,aaa=64,aaa=64,ggg=1020,ggg=1020 would be designated:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   CUSTOM IMIX - AAAGG</td><td> </td><td class="right">   CUSTOM IMIX - AAAGG</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">5.  Reporting Long or Pseudo-Random Packet Sequences</td><td> </td><td class="right">5.  Reporting Long or Pseudo-Random Packet Sequences</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When the IMIX-Genome cannot be used (when the sheer length of the</td><td> </td><td class="right">   When the IMIX-Genome cannot be used (when the sheer length of the</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0012" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   sequence would make the <span class="delete">g</span>enome unmanageable), two options are</td><td> </td><td class="rblock">   sequence would make the <span class="insert">G</span>enome unmanageable), two options are</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   possible.  When a sequence can be decomposed into a series of short</td><td> </td><td class="right">   possible.  When a sequence can be decomposed into a series of short</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   repeating sequences, then a run-length encoding approach MAY be used</td><td> </td><td class="right">   repeating sequences, then a run-length encoding approach MAY be used</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   as shown below:</td><td> </td><td class="right">   as shown below:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">          +------------------------------+----------------------+</td><td> </td><td class="right">          +------------------------------+----------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">          | Count of Repeating Sequences | Packet Size Sequence |</td><td> </td><td class="right">          | Count of Repeating Sequences | Packet Size Sequence |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">          +------------------------------+----------------------+</td><td> </td><td class="right">          +------------------------------+----------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">          | 20                           | abcd                 |</td><td> </td><td class="right">          | 20                           | abcd                 |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">          | 5                            | ggga                 |</td><td> </td><td class="right">          | 5                            | ggga                 |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">          | 10                           | dcba                 |</td><td> </td><td class="right">          | 10                           | dcba                 |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">          +------------------------------+----------------------+</td><td> </td><td class="right">          +------------------------------+----------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0013" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">The run-length encoding approach is also applicable to custom IMIX</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   described in section 4.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                        </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   When the sequence is designed to vary within some proportional</td><td> </td><td class="right">   When the sequence is designed to vary within some proportional</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   constraints, a table simply giving the proportions of each size MAY</td><td> </td><td class="right">   constraints, a table simply giving the proportions of each size MAY</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   be used instead.</td><td> </td><td class="right">   be used instead.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      +-----------+---------------------+---------------------------+</td><td> </td><td class="right">      +-----------+---------------------+---------------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      | IP Length | Percentage of Total | Length(s) at other layers |</td><td> </td><td class="right">      | IP Length | Percentage of Total | Length(s) at other layers |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      +-----------+---------------------+---------------------------+</td><td> </td><td class="right">      +-----------+---------------------+---------------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      | 64        | 23                  | 82                        |</td><td> </td><td class="right">      | 64        | 23                  | 82                        |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      | 128       | 67                  | 146                       |</td><td> </td><td class="right">      | 128       | 67                  | 146                       |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      | 1000      | 10                  | 1018                      |</td><td> </td><td class="right">      | 1000      | 10                  | 1018                      |</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      +-----------+---------------------+---------------------------+</td><td> </td><td class="right">      +-----------+---------------------+---------------------------+</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Note that the table of proportions also allows non-standard packet</td><td> </td><td class="right">   Note that the table of proportions also allows non-standard packet</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0014" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   sizes, but trades the short <span class="delete">g</span>enome specification and ability to</td><td> </td><td class="rblock">   sizes, but trades the short <span class="insert">G</span>enome specification and ability to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   specify the exact sequence for other flexibilities.</td><td> </td><td class="right">   specify the exact sequence for other flexibilities.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0015" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   <span class="insert">If a deterministic packet size generation method is used (such as</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   monotonic increase by one octet from start value to MTU), then the</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   generation algorithm SHOULD be reported.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                        </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   If a pseudo-random length generation capability is used, then the</td><td> </td><td class="right">   If a pseudo-random length generation capability is used, then the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   generation algorithm SHOULD be reported with the results along with</td><td> </td><td class="right">   generation algorithm SHOULD be reported with the results along with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the seed value used.  We also recognize the opportunity to randomize</td><td> </td><td class="right">   the seed value used.  We also recognize the opportunity to randomize</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   inter-packet spacing from a test sender as well as the size, and both</td><td> </td><td class="right">   inter-packet spacing from a test sender as well as the size, and both</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   spacing and length pseudo-random generation algorithms and seeds</td><td> </td><td class="right">   spacing and length pseudo-random generation algorithms and seeds</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD be reported when used.</td><td> </td><td class="right">   SHOULD be reported when used.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">6.  Security Considerations</td><td> </td><td class="right">6.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Benchmarking activities as described in this memo are limited to</td><td> </td><td class="right">   Benchmarking activities as described in this memo are limited to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 10, line 7</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 8, line 27</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [IXIA]     http://www.ixiacom.com/library/test_plans/</td><td> </td><td class="right">   [IXIA]     http://www.ixiacom.com/library/test_plans/</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              display?skey=testing_pppox, "Library: Test Plans", 2010.</td><td> </td><td class="right">              display?skey=testing_pppox, "Library: Test Plans", 2010.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5470]  Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,</td><td> </td><td class="right">   [RFC5470]  Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              "Architecture for IP Flow Information Export", RFC 5470,</td><td> </td><td class="right">              "Architecture for IP Flow Information Export", RFC 5470,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              March 2009.</td><td> </td><td class="right">              March 2009.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   [Spirent]  http://gospirent.com/whitepaper/</td><td> </td><td class="right">   [Spirent]  http://gospirent.com/whitepaper/</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">              IMIX%20Test%20Methodolgy%20Journal.pdf, "Test Methodology</td><td> </td><td class="right">              IMIX%20Test%20Methodolgy%20Journal.pdf, "Test Methodology</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0016" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">              Journal: IMIX (Internet Mix) Journal", <span class="delete">  </span>2006.</td><td> </td><td class="rblock">              Journal: IMIX (Internet Mix) Journal", 2006.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0017" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   [jumbo]    <span class="delete">http://www.ietf.org/mail-archive/web/bmwg/current/</span></td><td> </td><td class="rblock">   [jumbo]    <span class="insert">http://sd.wareonearth.com/~phil/jumbo.html and</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">              msg00691.html,</span> "Discussion of Jumbo Packets and FCS</td><td> </td><td class="rblock"><span class="insert">              http://staff.psc.edu/mathis/MTU/arguments.html#crc,</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">Failure, see http://sd.wareonearth.com/~phil/jumbo.html</span></td><td> </td><td class="rblock">              "Discussion of Jumbo Packets and FCS <span class="insert">Failure", .</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">              and http://staff.psc.edu/mathis/MTU/arguments.html#crc".</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Author's Address</td><td> </td><td class="right">Author's Address</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Al Morton</td><td> </td><td class="right">   Al Morton</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   AT&amp;T Labs</td><td> </td><td class="right">   AT&amp;T Labs</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   200 Laurel Avenue South</td><td> </td><td class="right">   200 Laurel Avenue South</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Middletown,, NJ  07748</td><td> </td><td class="right">   Middletown,, NJ  07748</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   USA</td><td> </td><td class="right">   USA</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Phone: +1 732 420 1571</td><td> </td><td class="right">   Phone: +1 732 420 1571</td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 17 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>38 lines changed or deleted</i></th><th><i> </i></th><th><i>45 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.