RFC 4737: Packet Reordering Metrics
In plain English — editorial summary, not part of the RFC
This memo defines metrics to evaluate whether a network has maintained packet order on a packet-by-packet basis. It provides motivations for the new metrics and discusses the measurement issues, including the context information required for all metrics. The memo first defines a reordered singleton, and then uses it as the basis for sample metrics to quantify the extent of reordering in several useful dimensions for network characterization or receiver design. Additional metrics quantify the frequency of reordering and the distance between separate occurrences. We then define a metric oriented toward assessment of reordering effects on TCP. Several examples of evaluation using the various sample metrics are included. An appendix gives extended definitions for evaluating order with packet fragmentation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4737
- Published
- November 2006
- Authors
- A. Morton; L. Ciavattone; G. Ramachandran; S. Shalunov; J. Perser
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 45
- Also known as
- —
- Updated by:
- RFC 6248
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6049Spatial Composition of MetricsUpdated
January 2011
- RFC 3393IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)Current
November 2002
- RFC 6673Round-Trip Packet Loss MetricsCurrent
August 2012
- RFC 2681A Round-trip Delay Metric for IPPMCurrent
September 1999
- RFC 2680A One-way Packet Loss Metric for IPPMObsoleted
September 1999
- RFC 2679A One-way Delay Metric for IPPMObsoleted
September 1999
- RFC 6808Test Plan and Results Supporting Advancement of RFC 2679 on the Standards TrackCurrent
December 2012
- RFC 7750Differentiated Service Code Point and Explicit Congestion Notification Monitoring in the Two-Way Active Measurement Protocol (TWAMP)Current
February 2016
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?