Simple Two-Way Active Measurement Protocol Optional Extensions
RFC 8972

Document Type RFC - Proposed Standard (January 2021; No errata)
Updates RFC 8762
Authors Greg Mirsky  , Xiao Min  , Henrik Nydell  , Richard Foote  , Adi Masputra  , Ernesto Ruffini 
Last updated 2021-01-21
Replaces draft-mirsky-ippm-stamp-option-tlv
Stream IETF
Formats plain text html xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Yali Wang
Shepherd write-up Show (last changed 2020-06-18)
IESG IESG state RFC 8972 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Duke
Send notices to Yali Wang <wangyali11@huawei.com>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack


Internet Engineering Task Force (IETF)                         G. Mirsky
Request for Comments: 8972                                        X. Min
Updates: 8762                                                  ZTE Corp.
Category: Standards Track                                      H. Nydell
ISSN: 2070-1721                                        Accedian Networks
                                                                R. Foote
                                                                   Nokia
                                                             A. Masputra
                                                              Apple Inc.
                                                              E. Ruffini
                                                                  OutSys
                                                            January 2021

     Simple Two-Way Active Measurement Protocol Optional Extensions

Abstract

   This document describes optional extensions to Simple Two-way Active
   Measurement Protocol (STAMP) that enable measurement of performance
   metrics.  The document also defines a STAMP Test Session Identifier
   and thus updates RFC 8762.

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
   https://www.rfc-editor.org/info/rfc8972.

Copyright Notice

   Copyright (c) 2021 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
   (https://trustee.ietf.org/license-info) 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.  Acronyms
     2.2.  Requirements Language
   3.  STAMP Test Session Identifier
   4.  TLV Extensions to STAMP
     4.1.  Extra Padding TLV
     4.2.  Location TLV
       4.2.1.  Location Sub-TLVs
       4.2.2.  Theory of Operation of Location TLV
     4.3.  Timestamp Information TLV
     4.4.  Class of Service TLV
     4.5.  Direct Measurement TLV
     4.6.  Access Report TLV
     4.7.  Follow-Up Telemetry TLV
     4.8.  HMAC TLV
   5.  IANA Considerations
     5.1.  STAMP TLV Types Subregistry
     5.2.  STAMP TLV Flags Subregistry
     5.3.  STAMP Sub-TLV Types Subregistry
     5.4.  STAMP Synchronization Sources Subregistry
     5.5.  STAMP Timestamping Methods Subregistry
     5.6.  STAMP Return Codes Subregistry
   6.  Security Considerations
   7.  References
     7.1.  Normative References
     7.2.  Informative References
   Acknowledgments
   Contributors
   Authors' Addresses

1.  Introduction

   The Simple Two-way Active Measurement Protocol (STAMP) [RFC8762]
   defines the STAMP base functionalities.  This document specifies the
   use of optional extensions that use Type-Length-Value (TLV) encoding.
   Such extensions enhance the STAMP base functions, such as measurement
   of one-way and round-trip delay, latency, packet loss, packet
   duplication, and out-of-order delivery of test packets.  This
   specification defines optional STAMP extensions, their formats, and
   the theory of operation.  Also, a STAMP Test Session Identifier is
   defined as an update of the base STAMP specification [RFC8762].

2.  Conventions Used in This Document

2.1.  Acronyms

   BDS         BeiDou Navigation Satellite System

   BITS        Building Integrated Timing Supply

   CoS         Class of Service

   DSCP        Differentiated Services Code Point

   ECN         Explicit Congestion Notification

   GLONASS     Global Orbiting Navigation Satellite System

   GPS         Global Positioning System [GPS]

   HMAC        Hashed Message Authentication Code

   LORAN-C     Long Range Navigation System Version C

   MBZ         Must Be Zero

   NTP         Network Time Protocol [RFC5905]

   PMF         Performance Measurement Function

   PTP         Precision Time Protocol [IEEE.1588.2008]

   RP          Reverse Path

   SMI         Structure of Management Information

   SSID        STAMP Session Identifier

   SSU         Synchronization Supply Unit

   STAMP       Simple Two-way Active Measurement Protocol
Show full document text