A Two-Way Active Measurement Protocol
RFC 5357, “A Two-Way Active Measurement Protocol”, is a Proposed Standard document published in October 2008 by K. Hedayat, R. Krzanowski, A. Morton, K. Yum, J. Babiarz. It has since been updated by RFC 5618, RFC 5938, RFC 6038, RFC 7717, RFC 7750, RFC 8545. The canonical text is published by the RFC Editor.
Abstract
The One-way Active Measurement Protocol (OWAMP), specified in RFC 4656, provides a common protocol for measuring one-way metrics between network devices. OWAMP can be used bi-directionally to measure one-way metrics in both directions between two network elements. However, it does not accommodate round-trip or two-way measurements. This memo specifies a Two-Way Active Measurement Protocol (TWAMP), based on the OWAMP, that adds two-way or round-trip measurement capabilities. The TWAMP measurement architecture is usually comprised of two hosts with specific roles, and this allows for some protocol simplifications, making it an attractive alternative in some circumstances. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5357 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5356 Reliable Server Pooling Policies
- RFC 5358 Preventing Use of Recursive Nameservers in Reflector Attacks
- RFC 5355 Threats Introduced by Reliable Server Pooling and Requirements for Security in Response to Threats
- RFC 5359 Session Initiation Protocol Service Examples
- RFC 5354 Aggregate Server Access Protocol and Endpoint Handlespace Redundancy Protocol Parameters
- RFC 5360 A Framework for Consent-Based Communications in the Session Initiation Protocol
- RFC 5353 Endpoint Handlespace Redundancy Protocol
- RFC 5361 A Document Format for Requesting Consent