RFC 5357: A Two-Way Active Measurement Protocol (TWAMP)

The One-way Active Measurement Protocol (OWAMP), specified in RFC 4656, provides a common protocol for measuring one-way metrics between network devices.…

Read RFC 5357 on the RFC Editor

Outgoing relationships (1 related RFC)

Informative reference — RFC 3692: Assigning Experimental and Testing Numbers Considered Useful

Incoming relationships (39 related RFCs)

Updated by — RFC 6038: Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features
Updated by, Normatively referenced by — RFC 5618: Mixed Security Mode for the Two-Way Active Measurement Protocol (TWAMP)
Updated by, Normatively referenced by — RFC 7717: IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)
Updated by — RFC 8545: Well-Known Port Assignments for the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP)
Updated by — RFC 5938: Individual Session Control Feature for the Two-Way Active Measurement Protocol (TWAMP)
Updated by — RFC 7750: Differentiated Service Code Point and Explicit Congestion Notification Monitoring in the Two-Way Active Measurement Protocol (TWAMP)
Normatively referenced by — RFC 8762: Simple Two-Way Active Measurement Protocol
Normatively referenced by — RFC 5835: Framework for Metric Composition
Normatively referenced by — RFC 8532: Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
Normatively referenced by — RFC 7312: Advanced Stream and Sampling Framework for IP Performance Metrics (IPPM)
Normatively referenced by — RFC 6808: Test Plan and Results Supporting Advancement of RFC 2679 on the Standards Track
Normatively referenced by — RFC 6673: Round-Trip Packet Loss Metrics
Normatively referenced by — RFC 7497: Rate Measurement Test Protocol Problem Statement and Requirements
Normatively referenced by — RFC 8186: Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol (TWAMP)
Normatively referenced by — RFC 8912: Initial Performance Metrics Registry Entries
Normatively referenced by — RFC 9097: Metrics and Methods for One-Way IP Capacity
Normatively referenced by — RFC 7718: Registries for the One-Way Active Measurement Protocol (OWAMP)
Normatively referenced by — RFC 7820: UDP Checksum Complement in the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)
Normatively referenced by — RFC 9696: Routing in Fat Trees (RIFT) Applicability and Operational Considerations
Normatively referenced by — RFC 6802: Ericsson Two-Way Active Measurement Protocol (TWAMP) Value-Added Octets
Normatively referenced by — RFC 7290: Test Plan and Results for Advancing RFC 2680 on the Standards Track
Normatively referenced by — RFC 8913: Two-Way Active Measurement Protocol (TWAMP) YANG Data Model
Normatively referenced by — RFC 9533: One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
Informatively referenced by — RFC 6374: Packet Loss and Delay Measurement for MPLS Networks
Informatively referenced by — RFC 7276: An Overview of Operations, Administration, and Maintenance (OAM) Tools
Informatively referenced by — RFC 7594: A Framework for Large-Scale Measurement of Broadband Performance (LMAP)
Informatively referenced by — RFC 9341: Alternate-Marking Method
Informatively referenced by — RFC 6576: IP Performance Metrics (IPPM) Standard Advancement Testing
Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards
Informatively referenced by — RFC 8972: Simple Two-Way Active Measurement Protocol Optional Extensions
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 8877: Guidelines for Defining Packet Timestamps
Informatively referenced by — RFC 6812: Cisco Service-Level Assurance Protocol
Informatively referenced by — RFC 8924: Service Function Chaining (SFC) Operations, Administration, and Maintenance (OAM) Framework
Informatively referenced by — RFC 8316: Autonomic Networking Use Case for Distributed Detection of Service Level Agreement (SLA) Violations
Informatively referenced by — RFC 9439: Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
Informatively referenced by — RFC 8802: The Quality for Service (Q4S) Protocol
Informatively referenced by — RFC 9534: Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
Informatively referenced by — RFC 9946: The UDP Speed Test Protocol (UDPSTP) for One-Way IP Capacity Metric Measurement