RFC 7312: Advanced Stream and Sampling Framework for IP Performance Metrics (IPPM)
In plain English — editorial summary, not part of the RFC
To obtain repeatable results in modern networks, test descriptions need an expanded stream parameter framework that also augments aspects specified as Type-P for test packets. This memo updates the IP Performance Metrics (IPPM) Framework, RFC 2330, with advanced considerations for measurement methodology and testing. The existing framework mostly assumes deterministic connectivity, and that a single test stream will represent the characteristics of the path when it is aggregated with other flows. Networks have evolved and test stream descriptions must evolve with them; otherwise, unexpected network features may dominate the measured performance. This memo describes new stream parameters for both network characterization and support of application design using IPPM metrics.
Document record
- Document ID
- RFC7312
- Published
- August 2014
- Authors
- J. Fabini; A. Morton
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 17
- Also known as
- —
- Updates:
- RFC 2330
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- 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 6576IP Performance Metrics (IPPM) Standard Advancement TestingCurrent
March 2012
- RFC 8468IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) FrameworkCurrent
November 2018
- RFC 6076Basic Telephony SIP End-to-End Performance MetricsCurrent
January 2011
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
- RFC 9119Multicast Considerations over IEEE 802 Wireless MediaCurrent
October 2021
- 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?