RFC 8239: Data Center Benchmarking Methodology
In plain English — editorial summary, not part of the RFC
The purpose of this informational document is to establish test and evaluation methodology and measurement techniques for physical network equipment in the data center. RFC 8238 is a prerequisite for this document, as it contains terminology that is considered normative. Many of these terms and methods may be applicable beyond the scope of this document as the technologies originally applied in the data center are deployed elsewhere.
Document record
- Document ID
- RFC8239
- Published
- August 2017
- Authors
- L. Avramov; J. Rapp
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 19
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8238Data Center Benchmarking TerminologyCurrent
August 2017
- RFC 8244Special-Use Domain Names Problem StatementCurrent
October 2017
- RFC 8250IPv6 Performance and Diagnostic Metrics (PDM) Destination OptionCurrent
September 2017
- RFC 8219Benchmarking Methodology for IPv6 Transition TechnologiesCurrent
August 2017
- RFC 8215Local-Use IPv4/IPv6 Translation PrefixCurrent
August 2017
- RFC 8212Default External BGP (EBGP) Route Propagation Behavior without PoliciesCurrent
July 2017
- RFC 8273Unique IPv6 Prefix per HostCurrent
December 2017
- RFC 8204Benchmarking Virtual Switches in the Open Platform for NFV (OPNFV)Current
September 2017
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?