RFC 8972 on Simple Two-Way Active Measurement Protocol Optional Extensions
rfc-editor@rfc-editor.org Fri, 22 January 2021 04:37 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D0C3A0EDB; Thu, 21 Jan 2021 20:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gyYGk0J7q2lR; Thu, 21 Jan 2021 20:37:34 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BED303A0EDA; Thu, 21 Jan 2021 20:37:34 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 48E08F40710; Thu, 21 Jan 2021 20:37:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8972 on Simple Two-Way Active Measurement Protocol Optional Extensions
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ippm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210122043716.48E08F40710@rfc-editor.org>
Date: Thu, 21 Jan 2021 20:37:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-v_CJwULOEeKGgl9InrbxYgNX14>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 04:37:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8972
Title: Simple Two-Way Active Measurement Protocol
Optional Extensions
Author: G. Mirsky,
X. Min,
H. Nydell,
R. Foote,
A. Masputra,
E. Ruffini
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: gregimirsky@gmail.com,
xiao.min2@zte.com.cn,
hnydell@accedian.com,
footer.foote@nokia.com,
adi@apple.com,
eruffini@outsys.org
Pages: 29
Updates: RFC 8762
I-D Tag: draft-ietf-ippm-stamp-option-tlv-10.txt
URL: https://www.rfc-editor.org/info/rfc8972
DOI: 10.17487/RFC8972
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.
This document is a product of the IP Performance Measurement Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC