STD 81, RFC 7679 on A One-Way Delay Metric for IP Performance Metrics (IPPM)
rfc-editor@rfc-editor.org Fri, 29 January 2016 22:35 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 506DA1A8BB3; Fri, 29 Jan 2016 14:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 Nr-z061IjAGe; Fri, 29 Jan 2016 14:35:20 -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 A91411A8AF2; Fri, 29 Jan 2016 14:35:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3B42D180094; Fri, 29 Jan 2016 14:33:40 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: STD 81, RFC 7679 on A One-Way Delay Metric for IP Performance Metrics (IPPM)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160129223340.3B42D180094@rfc-editor.org>
Date: Fri, 29 Jan 2016 14:33:40 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/G7Es7G4Et6qQqvRitxTBJRu5TpE>
Cc: drafts-update-ref@iana.org, ippm@ietf.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: <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, 29 Jan 2016 22:35:22 -0000
A new Request for Comments is now available in online RFC libraries. STD 81 RFC 7679 Title: A One-Way Delay Metric for IP Performance Metrics (IPPM) Author: G. Almes, S. Kalidindi, M. Zekauskas, A. Morton, Ed. Status: Standards Track Stream: IETF Date: January 2016 Mailbox: almes@acm.org, skalidindi@ixiacom.com, matt@internet2.edu, acmorton@att.com Pages: 27 Characters: 59852 Obsoletes: RFC 2679 See Also: STD 81 I-D Tag: draft-ietf-ippm-2679-bis-05.txt URL: https://www.rfc-editor.org/info/rfc7679 DOI: http://dx.doi.org/10.17487/RFC7679 This memo defines a metric for one-way delay of packets across Internet paths. It builds on notions introduced and discussed in the IP Performance Metrics (IPPM) Framework document, RFC 2330; the reader is assumed to be familiar with that document. This memo makes RFC 2679 obsolete. This document is a product of the IP Performance Metrics Working Group of the IETF. This is now an Internet 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/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