RFC 8186: Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol (TWAMP)
In plain English — editorial summary, not part of the RFC
This document describes an OPTIONAL feature for active performance measurement protocols that allows use of the Precision Time Protocol timestamp format defined in IEEE 1588v2, as an alternative to the Network Time Protocol that is currently used.
Document record
- Document ID
- RFC8186
- Published
- June 2017
- Authors
- G. Mirsky; I. Meilik
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7750Differentiated Service Code Point and Explicit Congestion Notification Monitoring in the Two-Way Active Measurement Protocol (TWAMP)Current
February 2016
- RFC 8545Well-Known Port Assignments for the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP)Current
March 2019
- RFC 7820UDP Checksum Complement in the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)Current
March 2016
- RFC 8911Registry for Performance MetricsCurrent
November 2021
- RFC 8972Simple Two-Way Active Measurement Protocol Optional ExtensionsCurrent
January 2021
- RFC 9198Advanced Unidirectional Route Assessment (AURA)Current
May 2022
- RFC 9533One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation GroupCurrent
January 2024
- RFC 9544Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs)Current
March 2024
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?