RFC 8762: Simple Two-Way Active Measurement Protocol
In plain English — editorial summary, not part of the RFC
This document describes the Simple Two-way Active Measurement Protocol (STAMP), which enables the measurement of both one-way and round-trip performance metrics, like delay, delay variation, and packet loss.
Document record
- Document ID
- RFC8762
- Published
- March 2020
- Authors
- G. Mirsky; G. Jun; H. Nydell; R. Foote
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
- Updated by:
- RFC 8972
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 8767Serving Stale Data to Improve DNS ResiliencyCurrent
March 2020
- RFC 8749Moving DNSSEC Lookaside Validation (DLV) to Historic StatusCurrent
March 2020
- RFC 8748Registry Fee Extension for the Extensible Provisioning Protocol (EPP)Current
March 2020
- RFC 8777DNS Reverse IP Automatic Multicast Tunneling (AMT) DiscoveryCurrent
April 2020
- RFC 8791YANG Data Structure ExtensionsCurrent
June 2020
- RFC 8792Handling Long Lines in Content of Internet-Drafts and RFCsCurrent
June 2020
- RFC 8806Running a Root Server Local to a ResolverCurrent
June 2020
- RFC 8807Login Security Extension for the Extensible Provisioning Protocol (EPP)Current
August 2020
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?