UpdatedPROPOSED STANDARDIETF stream

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

Still current, but amended. Parts of this document are changed or extended by RFC 5618, RFC 5938, RFC 6038, RFC 7717, RFC 7750, RFC 8545. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC5357
Published
October 2008
Authors
K. Hedayat; R. Krzanowski; A. Morton; K. Yum; J. Babiarz
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
26
Also known as

Topics

Referenced by

6 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5357-a-two-way-active-measurement-protocol-twamp