Re: [xrblock] Usage of RFC 6390 in XRBLOCK documents
Alan Clark <alan.d.clark@telchemy.com> Tue, 04 December 2012 12:22 UTC
Return-Path: <alan.d.clark@telchemy.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9968721F89DC for <xrblock@ietfa.amsl.com>; Tue, 4 Dec 2012 04:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 7TT0qi0riDsv for <xrblock@ietfa.amsl.com>; Tue, 4 Dec 2012 04:22:40 -0800 (PST)
Received: from smtp01.myhostedservice.com (smtp01.myhostedservice.com [216.134.213.70]) by ietfa.amsl.com (Postfix) with ESMTP id E9C0E21F86FC for <xrblock@ietf.org>; Tue, 4 Dec 2012 04:22:39 -0800 (PST)
Received: from mail01.netplexity.net (172.29.251.14) by SMTP01.netplexity.local (172.29.211.9) with Microsoft SMTP Server id 14.2.318.4; Tue, 4 Dec 2012 07:22:31 -0500
Received: from [192.168.1.5] (c-24-98-22-58.hsd1.ga.comcast.net [24.98.22.58]) by mail01.netplexity.net with SMTP; Tue, 4 Dec 2012 07:22:27 -0500
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Tue, 04 Dec 2012 07:22:26 -0500
From: Alan Clark <alan.d.clark@telchemy.com>
To: "Dan (Dan)" <dromasca@avaya.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Message-ID: <CCE35532.4C5E1%alan.d.clark@telchemy.com>
Thread-Topic: [xrblock] Usage of RFC 6390 in XRBLOCK documents
Thread-Index: Ac3RVZ3sndR7nrgsR2+xFQARszaEYgAxGcr7
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA02DF35@AZ-FFEXMB03.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: Benoit Claise <bclaise@cisco.com>
Subject: Re: [xrblock] Usage of RFC 6390 in XRBLOCK documents
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 12:22:40 -0000
The major risk with incorporating metric definitions for an existing metric into an XRBLOCK draft is that this would be a more comprehensive non-normative definition of a metric that was incompletely defined in some other IETF, ITU, ISO, IEEE or other standard. I support the idea of using RFC6390 however believe that we should preface the definition with a statement that the definition is non-normative and may need to be updated if the normative standard is modified. We should also send a liaison statement back to the appropriate standards committee to suggest that they adopt the template based metric definition that we have drafted. Alan On 12/3/12 7:56 AM, "Dan (Dan)" <dromasca@avaya.com> wrote: > Most if not all participants in the work of XRBLOCK are probably familiar with > BCP 170 / RFC 6390 - ' Guidelines for Considering New Performance Metric > Development'. This RFC describes a framework and a process for developing > Performance Metrics of protocols and applications transported over > IETF-specified protocols and makes a number of recommendations about the > definition of new metrics. > > Specifically section 5.4.2 of the RFC defines the normative part of a > Performance Metric definition, which MUST include the following: > > (i) Metric Name > (ii) Metric Description > (iii) Method of Measurement or Calculation > (iv) Units of Measurement > (v) Measurement Point(s) with Potential Measurement Domain > (vi) Measurement Timing > > In XRBLOCK documents we are re-using definitions of metrics already defined > somewhere else and normatively refer these documents. We do not intent to > change this, but we would like to use the list above as a checklist that all > mandatory information does exist in the definitions of the metrics that we > refer. Authors can chose whether to use the exact format or terminology used > by 6390 or not, provided that all necessary information is present. > > In documents that define new metrics (if there will be such document) it will > be required to include all normative parts of the performance metric > definition as specified in section 5.4.2 of RFC 6390. > > Please let us know if you see any problem with starting to apply this policy > immediately. > > Thanks and Regards, > > Dan > > > > _______________________________________________ > xrblock mailing list > xrblock@ietf.org > https://www.ietf.org/mailman/listinfo/xrblock
- [xrblock] Usage of RFC 6390 in XRBLOCK documents Romascanu, Dan (Dan)
- Re: [xrblock] Usage of RFC 6390 in XRBLOCK docume… Glen Zorn
- Re: [xrblock] Usage of RFC 6390 in XRBLOCK docume… Qin Wu
- Re: [xrblock] Usage of RFC 6390 in XRBLOCK docume… Romascanu, Dan (Dan)
- Re: [xrblock] Usage of RFC 6390 in XRBLOCK docume… Alan Clark