[ippm] RFC 8762 on Simple Two-Way Active Measurement Protocol

rfc-editor@rfc-editor.org Thu, 19 March 2020 22:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59FFF3A1130; Thu, 19 Mar 2020 15:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_TEMPERROR=0.01, 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 rP1GwUltRsiX; Thu, 19 Mar 2020 15:00:08 -0700 (PDT)
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 584843A10A4; Thu, 19 Mar 2020 15:00:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id ABE82F40737; Thu, 19 Mar 2020 14:59:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20200319215953.ABE82F40737@rfc-editor.org>
Date: Thu, 19 Mar 2020 14:59:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/L_J5CPhz7hn6AXD5uofQC-TjrcA>
Subject: [ippm] RFC 8762 on Simple Two-Way Active Measurement Protocol
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2020 22:00:30 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8762

        Title:      Simple Two-Way Active Measurement Protocol 
        Author:     G. Mirsky,
                    G. Jun,
                    H. Nydell,
                    R. Foote
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    gregimirsky@gmail.com, 
                    guo.jun2@zte.com.cn, 
                    hnydell@accedian.com,
                    footer.foote@nokia.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-stamp-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8762

        DOI:        10.17487/RFC8762

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.

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