RFC 9341: Alternate-Marking Method

This document describes the Alternate-Marking technique to perform packet loss, delay, and jitter measurements on live traffic. This technology can be applied…

Read RFC 9341 on the RFC Editor

Outgoing relationships (16 related RFCs)

Obsoletes, Informative reference — RFC 8321: Alternate-Marking Method for Passive and Hybrid Performance Monitoring
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3393: IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)
Normative reference — RFC 7679: A One-Way Delay Metric for IP Performance Metrics (IPPM)
Normative reference — RFC 7680: A One-Way Loss Metric for IP Performance Metrics (IPPM)
Informative reference — RFC 5905: Network Time Protocol Version 4: Protocol and Algorithms Specification
Informative reference — RFC 2330: Framework for IP Performance Metrics
Informative reference — RFC 5357: A Two-Way Active Measurement Protocol (TWAMP)
Informative reference — RFC 4656: A One-way Active Measurement Protocol (OWAMP)
Informative reference — RFC 6390: Guidelines for Considering New Performance Metric Development
Informative reference — RFC 7799: Active and Passive Metrics and Methods (with Hybrid Types In-Between)
Informative reference — RFC 5481: Packet Delay Variation Applicability Statement
Informative reference — RFC 7384: Security Requirements of Time Protocols in Packet Switched Networks
Informative reference — RFC 6703: Reporting IP Network Performance Metrics: Different Points of View
Informative reference — RFC 8799: Limited Domains and Internet Protocols

Incoming relationships (8 related RFCs)

Normatively referenced by — RFC 9947: Application of the Alternate-Marking Method to the Segment Routing Header
Normatively referenced by — RFC 9779: Performance Measurement for Segment Routing Networks with the MPLS Data Plane
Informatively referenced by — RFC 9551: Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)
Informatively referenced by — RFC 9714: Encapsulation for MPLS Performance Measurement with the Alternate-Marking Method
Informatively referenced by — RFC 9791: Use Cases for MPLS Network Action Indicators and Ancillary Data
Informatively referenced by — RFC 9506: Explicit Host-to-Network Flow Measurements Techniques
Informatively referenced by — RFC 9974: Operations, Administration, and Maintenance (OAM) Requirements for the Bit Index Explicit Replication (BIER) Layer
Informatively referenced by — RFC 10014: Guidelines for Characterizing the Term "OAM"