IMIX Genome: Specification of Variable Packet Sizes for Additional Testing
RFC 6985
| Document | Type | RFC - Informational (July 2013; No errata) | |
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-morton-bmwg-imix-genome | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Lucien Avramov | ||
| Shepherd write-up | Show (last changed 2013-04-21) | ||
| IESG | IESG state | RFC 6985 (Informational) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Joel Jaeggli | ||
| IESG note |
I've reviewed the discussion on this draft through it's revisions back to IETF 80. I don't believe there are any criticisms remaining that would be considered blocking. As noted (minutes 85) SOB states that that this method is not likely to be used to produce representation of the real world, the real world is not consistent. I think that we can be abundantly aware of the limitations and find utility in this representation. Seeing no additional concerns during the WGLC. I'm prepared to call this document done and ready to advance. |
||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | No IANA Actions | ||
Internet Engineering Task Force (IETF) A. Morton
Request for Comments: 6985 AT&T Labs
Category: Informational July 2013
ISSN: 2070-1721
IMIX Genome: Specification of Variable Packet Sizes
for Additional Testing
Abstract
Benchmarking methodologies have always relied on test conditions with
constant packet sizes, with the goal of understanding what network
device capability has been tested. Tests with a constant packet size
reveal device capabilities but differ significantly from the
conditions encountered in operational deployment, so additional tests
are sometimes conducted with a mixture of packet sizes, or "IMIX"
("Internet Mix"). The mixture of sizes a networking device will
encounter is highly variable and depends on many factors. An IMIX
suited for one networking device and deployment will not be
appropriate for another. However, the mix of sizes may be known, and
the tester may be asked to augment the fixed-size tests. To address
this need and the perpetual goal of specifying repeatable test
conditions, this document defines a way to specify the exact
repeating sequence of packet sizes from the usual set of fixed sizes
and from other forms of mixed-size specification.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6985.
Morton Informational [Page 1]
RFC 6985 IMIX Genome July 2013
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
2. Requirements Language ...........................................3
3. Scope and Goals .................................................3
4. Specification of the IMIX Genome ................................4
5. Specification of a Custom IMIX ..................................6
6. Reporting Long or Pseudorandom Packet Sequences .................7
6.1. Run-Length Encoding ........................................7
6.2. Table of Proportions .......................................7
6.3. Deterministic Algorithm ....................................7
6.4. Pseudorandom Length Algorithm ..............................8
6.5. Pseudorandom Sequence Algorithm ............................8
7. Security Considerations .........................................8
8. Acknowledgements ................................................8
9. References ......................................................9
9.1. Normative References .......................................9
9.2. Informative References .....................................9
1. Introduction
This memo defines a method to unambiguously specify the sequence of
packet sizes used in a load test.
Benchmarking methodologies [RFC2544] have always relied on test
conditions with constant packet sizes, with the goal of understanding
what network device capability has been tested. Tests with the
smallest size stress the header processing capacity, and tests with
the largest size stress the overall bit-processing capacity. Tests
with sizes in between may determine the transition between these two
capacities.
Morton Informational [Page 2]
RFC 6985 IMIX Genome July 2013
Streams of constant packet size differ significantly from the
conditions encountered in operational deployment, so additional tests
are sometimes conducted with a mixture of packet sizes. The set of
Show full document text