[ippm] BCP 176, RFC 6576 on IP Performance Metrics (IPPM) Standard Advancement Testing

rfc-editor@rfc-editor.org Mon, 26 March 2012 11:39 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 DB36321F8628; Mon, 26 Mar 2012 04:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.451
X-Spam-Level:
X-Spam-Status: No, score=-102.451 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BDdrFKDJZkH; Mon, 26 Mar 2012 04:39:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 092BB21F867A; Mon, 26 Mar 2012 04:39:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B40B6B1E005; Mon, 26 Mar 2012 04:38:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120326113829.B40B6B1E005@rfc-editor.org>
Date: Mon, 26 Mar 2012 04:38:29 -0700
Cc: ippm@ietf.org, rfc-editor@rfc-editor.org
Subject: [ippm] BCP 176, RFC 6576 on IP Performance Metrics (IPPM) Standard Advancement Testing
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 26 Mar 2012 11:39:57 -0000

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

        BCP 176        
        RFC 6576

        Title:      IP Performance Metrics (IPPM) Standard 
                    Advancement Testing 
        Author:     R. Geib, Ed.,
                    A. Morton, R. Fardid,
                    A. Steinmitz
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2012
        Mailbox:    Ruediger.Geib@telekom.de, 
                    acmorton@att.com, 
                    rfardid@cariden.com,
                    Alexander.Steinmitz@telekom.de
        Pages:      37
        Characters: 84447
        See Also:   BCP0176

        I-D Tag:    draft-ietf-ippm-metrictest-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6576.txt

This document specifies tests to determine if multiple independent
instantiations of a performance-metric RFC have implemented the
specifications in the same way.  This is the performance-metric
equivalent of interoperability, required to advance RFCs along the
Standards Track.  Results from different implementations of metric
RFCs will be collected under the same underlying network conditions
and compared using statistical methods.  The goal is an evaluation of
the metric RFC itself to determine whether its definitions are clear
and unambiguous to implementors and therefore a candidate for
advancement on the IETF Standards Track.  This document is an
Internet Best Current Practice.  

This document is a product of the IP Performance Metrics Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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