RFC 6576: IP Performance Metrics (IPPM) Standard Advancement Testing
In plain English — editorial summary, not part of the RFC
This document specifies tests to determine if multiple independent instantiations of a performance-metric RFC have implemented the specifications in the same way. This is the performance-metric equivalent of interoperability, required to advance RFCs along the Standards Track. Results from different implementations of metric RFCs will be collected under the same underlying network conditions and compared using statistical methods. The goal is an evaluation of the metric RFC itself to determine whether its definitions are clear and unambiguous to implementors and therefore a candidate for advancement on the IETF Standards Track. This document is an Internet Best Current Practice.
Document record
- Document ID
- RFC6576
- Published
- March 2012
- Authors
- R. Geib; A. Morton; R. Fardid; A. Steinmitz
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 37
- Also known as
- BCP176
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6349Framework for TCP Throughput TestingCurrent
August 2011
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
- RFC 6038Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size FeaturesCurrent
October 2010
- RFC 7312Advanced Stream and Sampling Framework for IP Performance Metrics (IPPM)Current
August 2014
- RFC 7594A Framework for Large-Scale Measurement of Broadband Performance (LMAP)Current
September 2015
- RFC 7679A One-Way Delay Metric for IP Performance Metrics (IPPM)Current
January 2016
- RFC 5472IP Flow Information Export (IPFIX) ApplicabilityCurrent
March 2009
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?