RFC 9506: Explicit Host-to-Network Flow Measurements Techniques
In plain English — editorial summary, not part of the RFC
This document describes protocol-independent methods called Explicit Host-to-Network Flow Measurement Techniques that can be applicable to transport-layer protocols between the client and server. These methods employ just a few marking bits inside the header of each packet for performance measurements and require the client and server to collaborate. Both endpoints cooperate by marking packets and, possibly, mirroring the markings on the round-trip connection. The techniques are especially valuable when applied to protocols that encrypt transport headers since they enable loss and delay measurements by passive, on-path network devices. This document describes several methods that can be used separately or jointly depending of the availability of marking bits, desired measurements, and properties of the protocol to which the methods are applied.
Document record
- Document ID
- RFC9506
- Published
- October 2023
- Authors
- M. Cociglio; A. Ferrieux; G. Fioccola; I. Lubashev; F. Bulgarella; M. Nilo; I. Hamchaoui; R. Sisto
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9342Clustered Alternate-Marking MethodCurrent
December 2022
- RFC 9343IPv6 Application of the Alternate-Marking MethodCurrent
December 2022
- RFC 9947Application of the Alternate-Marking Method to the Segment Routing HeaderCurrent
March 2026
- RFC 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 1999
- RFC 8911Registry for Performance MetricsCurrent
November 2021
- RFC 6703Reporting IP Network Performance Metrics: Different Points of ViewCurrent
August 2012
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 1997
- RFC 7200A Session Initiation Protocol (SIP) Load-Control Event PackageCurrent
April 2014
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?