RFC 6815: Applicability Statement for RFC 2544: Use on Production Networks Considered Harmful
In plain English — editorial summary, not part of the RFC
The Benchmarking Methodology Working Group (BMWG) has been developing key performance metrics and laboratory test methods since 1990, and continues this work at present. The methods described in RFC 2544 are intended to generate traffic that overloads network device resources in order to assess their capacity. Overload of shared resources would likely be harmful to user traffic performance on a production network, and there are further negative consequences identified with production application of the methods. This memo clarifies the scope of RFC 2544 and other IETF BMWG benchmarking work for isolated test environments only, and it encourages new standards activity for measurement methods applicable outside that scope. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6815
- Published
- November 2012
- Authors
- S. Bradner; K. Dubray; J. McQuaid; A. Morton
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
- Updates:
- RFC 2544
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6038Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size FeaturesCurrent
October 2010
- RFC 1944Benchmarking Methodology for Network Interconnect DevicesObsoleted
May 1996
- RFC 6645IP Flow Information Accounting and Export Benchmarking MethodologyCurrent
July 2012
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
- RFC 7679A One-Way Delay Metric for IP Performance Metrics (IPPM)Current
January 2016
- RFC 7680A One-Way Loss Metric for IP Performance Metrics (IPPM)Current
January 2016
- RFC 7799Active and Passive Metrics and Methods (with Hybrid Types In-Between)Current
May 2016
- RFC 8337Model-Based Metrics for Bulk Transport CapacityCurrent
March 2018
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?