Simple Two-Way Active Measurement Protocol
RFC 8762

Document Type RFC - Proposed Standard (March 2020; No errata)
Updated by RFC 8972
Authors Greg Mirsky  , Guo Jun  , Henrik Nydell  , Richard Foote 
Last updated 2020-03-19
Replaces draft-mirsky-ippm-stamp
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Tal Mizrahi
Shepherd write-up Show (last changed 2019-05-19)
IESG IESG state RFC 8762 (Proposed Standard)
Action Holders
Consensus Boilerplate Yes
Telechat date
Responsible AD Mirja K├╝hlewind
Send notices to Tal Mizrahi <>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions

Internet Engineering Task Force (IETF)                         G. Mirsky
Request for Comments: 8762                                        G. Jun
Category: Standards Track                                      ZTE Corp.
ISSN: 2070-1721                                                H. Nydell
                                                       Accedian Networks
                                                                R. Foote
                                                              March 2020

               Simple Two-Way Active Measurement Protocol


   This document describes the Simple Two-way Active Measurement
   Protocol (STAMP), which enables the measurement of both one-way and
   round-trip performance metrics, like delay, delay variation, and
   packet loss.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
   2.  Conventions Used in This Document
     2.1.  Terminology
     2.2.  Requirements Language
   3.  Operation and Management of Performance Measurement Based on
   4.  Theory of Operation
     4.1.  UDP Port Numbers in STAMP Testing
     4.2.  Session-Sender Behavior and Packet Format
       4.2.1.  Session-Sender Packet Format in Unauthenticated Mode
       4.2.2.  Session-Sender Packet Format in Authenticated Mode
     4.3.  Session-Reflector Behavior and Packet Format
       4.3.1.  Session-Reflector Packet Format in Unauthenticated Mode
       4.3.2.  Session-Reflector Packet Format in Authenticated Mode
     4.4.  Integrity Protection in STAMP
     4.5.  Confidentiality Protection in STAMP
     4.6.  Interoperability with TWAMP Light
   5.  Operational Considerations
   6.  IANA Considerations
   7.  Security Considerations
   8.  References
     8.1.  Normative References
     8.2.  Informative References
   Authors' Addresses

1.  Introduction

   Development and deployment of the Two-Way Active Measurement Protocol
   (TWAMP) [RFC5357] and its extensions (e.g., [RFC6038], which defines
   Symmetrical Size for TWAMP) provided invaluable experience.  Several
   independent implementations of both TWAMP and TWAMP Light exist, have
   been deployed, and provide important operational performance

   At the same time, there has been noticeable interest in using a more
   straightforward mechanism for active performance monitoring that can
   provide deterministic behavior and inherent separation of control
   (vendor-specific configuration or orchestration) and test functions.
   Recent work on "Performance Measurement from IP Edge to Customer
   Equipment using TWAMP Light" [BBF.TR-390] by the Broadband Forum
   demonstrates that interoperability among implementations of TWAMP
   Light is difficult because the composition and operation of TWAMP
   Light were not sufficiently specified in [RFC5357].  According to
   [RFC8545], TWAMP Light includes a subset of TWAMP-Test functions.
   Thus, to have a comprehensive tool to measure packet loss and delay
   requires support by other applications that provide, for example,
   control and security.

   This document defines an active performance measurement test
   protocol, Simple Two-way Active Measurement Protocol (STAMP), that
   enables measurement of both one-way and round-trip performance
   metrics, like delay, delay variation, and packet loss.  Support of
   some optional TWAMP extensions, e.g., [RFC7750], is discussed in

2.  Conventions Used in This Document

2.1.  Terminology

   STAMP:      Simple Two-way Active Measurement Protocol

   NTP:        Network Time Protocol

   PTP:        Precision Time Protocol

   HMAC:       Hashed Message Authentication Code
Show full document text