RFC 6049 on Spatial Composition of Metrics

rfc-editor@rfc-editor.org Tue, 04 January 2011 19:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B32E73A6A7C; Tue, 4 Jan 2011 11:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.007
X-Spam-Level:
X-Spam-Status: No, score=-102.007 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6TgWPQudIm3M; Tue, 4 Jan 2011 11:17:47 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 0008C3A6A74; Tue, 4 Jan 2011 11:17:46 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 552DFE070C; Tue, 4 Jan 2011 11:19:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6049 on Spatial Composition of Metrics
From: rfc-editor@rfc-editor.org
Message-Id: <20110104191954.552DFE070C@rfc-editor.org>
Date: Tue, 04 Jan 2011 11:19:54 -0800
Cc: ippm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Jan 2011 19:17:47 -0000

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

        
        RFC 6049

        Title:      Spatial Composition of Metrics 
        Author:     A. Morton, E. Stephan
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    acmorton@att.com, 
                    emile.stephan@orange-ftgroup.com
        Pages:      29
        Characters: 57486
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-spatial-composition-16.txt

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

This memo utilizes IP performance metrics that are applicable to both
complete paths and sub-paths, and it defines relationships to compose
a complete path metric from the sub-path metrics with some accuracy
with regard to the actual metrics.  This is called "spatial
composition" in RFC 2330.  The memo refers to the framework for
metric composition, and provides background and motivation for
combining metrics to derive others.  The descriptions of several
composed metrics and statistics follow.  [STANDARDS-TRACK]

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

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  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