RFC 7290 on Test Plan and Results for Advancing RFC 2680 on the Standards Track
rfc-editor@rfc-editor.org Tue, 22 July 2014 18:46 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33A841A00BA for <ietf-announce@ietfa.amsl.com>; Tue, 22 Jul 2014 11:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level:
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 uNhxJLin3UKz for <ietf-announce@ietfa.amsl.com>; Tue, 22 Jul 2014 11:46:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 411561A0023 for <ietf-announce@ietf.org>; Tue, 22 Jul 2014 11:46:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BD33F18001B; Tue, 22 Jul 2014 11:45:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7290 on Test Plan and Results for Advancing RFC 2680 on the Standards Track
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140722184525.BD33F18001B@rfc-editor.org>
Date: Tue, 22 Jul 2014 11:45:25 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/LG7pAKWY4qW8BPgrrnL0GmHcHWY
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: Tue, 22 Jul 2014 18:46:41 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7290
Title: Test Plan and Results for
Advancing RFC 2680 on the Standards
Track
Author: L. Ciavattone, R. Geib,
A. Morton, M. Wieser
Status: Informational
Stream: IETF
Date: July 2014
Mailbox: lencia@att.com,
Ruediger.Geib@telekom.de,
acmorton@att.com,
matthias_michael.wieser@stud.tu-darmstadt.de
Pages: 31
Characters: 59898
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ippm-testplan-rfc2680-05.txt
URL: https://www.rfc-editor.org/rfc/rfc7290.txt
This memo provides the supporting test plan and results to advance
RFC 2680, a performance metric RFC defining one-way packet loss
metrics, along the Standards Track. 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 2680.
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
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/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