RFC 5481: Packet Delay Variation Applicability Statement
In plain English — editorial summary, not part of the RFC
Packet delay variation metrics appear in many different standards documents. The metric definition in RFC 3393 has considerable flexibility, and it allows multiple formulations of delay variation through the specification of different packet selection functions. Although flexibility provides wide coverage and room for new ideas, it can make comparisons of independent implementations more difficult. Two different formulations of delay variation have come into wide use in the context of active measurements. This memo examines a range of circumstances for active measurements of delay variation and their uses, and recommends which of the two forms is best matched to particular conditions and tasks. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5481
- Published
- March 2009
- Authors
- A. Morton; B. Claise
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 39
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8219Benchmarking Methodology for IPv6 Transition TechnologiesCurrent
August 2017
- RFC 3393IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)Current
November 2002
- RFC 9693Benchmarking Methodology for Stateful NATxy GatewaysCurrent
January 2025
- RFC 5477Information Model for Packet Sampling ExportsCurrent
March 2009
- RFC 5476Packet Sampling (PSAMP) Protocol SpecificationsCurrent
March 2009
- RFC 5475Sampling and Filtering Techniques for IP Packet SelectionCurrent
March 2009
- RFC 5474A Framework for Packet Selection and ReportingCurrent
March 2009
- RFC 5473Reducing Redundancy in IP Flow Information Export (IPFIX) and Packet Sampling (PSAMP) ReportsCurrent
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?