RFC 6808 on Test Plan and Results Supporting Advancement of RFC 2679 on the Standards Track
rfc-editor@rfc-editor.org Thu, 06 December 2012 01:29 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 3BDF621F8D08; Wed, 5 Dec 2012 17:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.933
X-Spam-Level:
X-Spam-Status: No, score=-101.933 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uxrY139T0Zlb; Wed, 5 Dec 2012 17:29:22 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A8F8021F8D07; Wed, 5 Dec 2012 17:29:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DF8C672F4F8; Wed, 5 Dec 2012 17:21:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6808 on Test Plan and Results Supporting Advancement of RFC 2679 on the Standards Track
From: rfc-editor@rfc-editor.org
Message-Id: <20121206012105.DF8C672F4F8@rfc-editor.org>
Date: Wed, 05 Dec 2012 17:21:05 -0800
Cc: ippm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 06 Dec 2012 01:29:23 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6808
Title: Test Plan and Results Supporting
Advancement of RFC 2679 on the
Standards Track
Author: L. Ciavattone, R. Geib,
A. Morton, M. Wieser
Status: Informational
Stream: IETF
Date: December 2012
Mailbox: lencia@att.com,
Ruediger.Geib@telekom.de,
acmorton@att.com,
matthias_michael.wieser@stud.tu-darmstadt.de
Pages: 29
Characters: 62061
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ippm-testplan-rfc2679-03.txt
URL: http://www.rfc-editor.org/rfc/rfc6808.txt
This memo provides the supporting test plan and results to advance
RFC 2679 on one-way delay metrics along the Standards Track,
following the process in RFC 6576. Observing that the metric
definitions themselves should be the primary focus rather than the
implementations of metrics, this memo describes the test procedures
to evaluate specific metric requirement clauses to determine if the
requirement has been interpreted and implemented as intended. Two
completely independent implementations have been tested against the
key specifications of RFC 2679. This memo also provides direct input
for development of a revision of RFC 2679. This document is not an
Internet Standards Track specification; it is published for
informational purposes.
This document is a product of the IP Performance Metrics Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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