Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 5618,RFC 5938,RFC 6038,RFC 7717,RFC 7750,RFC 8545

Authors:

K. Hedayat
R. Krzanowski
A. Morton
K. Yum
J. Babiarz

Stream:

IETF

Source:

ippm (ops)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5357

Discuss this RFC: Send questions or comments to the mailing listippm@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5357

Abstract

The One-way Active Measurement Protocol (OWAMP), specified in RFC4656, provides a common protocol for measuring one-way metrics between networkdevices. OWAMP can be used bi-directionally to measure one-waymetrics in both directions between two network elements. However,it does not accommodate round-trip or two-way measurements. Thismemo specifies a Two-Way Active Measurement Protocol (TWAMP), basedon the OWAMP, that adds two-way or round-trip measurementcapabilities. The TWAMP measurement architecture is usuallycomprised of two hosts with specific roles, and this allows forsome protocol simplifications, making it an attractive alternativein some circumstances. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.