RFC 6985: IMIX Genome: Specification of Variable Packet Sizes for Additional Testing
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6985
- Published
- July 2013
- Authors
- A. Morton
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 4814Hash and Stuffing: Overlooked Factors in Network Device BenchmarkingCurrent
March 2007
- RFC 9411Benchmarking Methodology for Network Security Device PerformanceCurrent
March 2023
- RFC 9693Benchmarking Methodology for Stateful NATxy GatewaysCurrent
January 2025
- RFC 3670Information Model for Describing Network Device QoS Datapath MechanismsCurrent
January 2004
- RFC 3511Benchmarking Methodology for Firewall PerformanceObsoleted
April 2003
- RFC 2588IP Multicast and FirewallsCurrent
May 1999
- RFC 3711The Secure Real-time Transport Protocol (SRTP)Updated
March 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?