Re: [xrblock] Fwd: [ippm] Performance Metrics Registry: new draft

Benoit Claise <bclaise@cisco.com> Wed, 31 July 2013 07:55 UTC

Return-Path: <bclaise@cisco.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 AD2CE21F9CF2 for <xrblock@ietfa.amsl.com>; Wed, 31 Jul 2013 00:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.54
X-Spam-Level:
X-Spam-Status: No, score=-10.54 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKIBv5utn5Dq for <xrblock@ietfa.amsl.com>; Wed, 31 Jul 2013 00:55:22 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 6F39721F9AC1 for <xrblock@ietf.org>; Wed, 31 Jul 2013 00:55:02 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6V7sr72009916; Wed, 31 Jul 2013 09:54:53 +0200 (CEST)
Received: from [10.61.74.75] (ams3-vpn-dhcp2635.cisco.com [10.61.74.75]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6V7s2U1005284; Wed, 31 Jul 2013 09:54:18 +0200 (CEST)
Message-ID: <51F8C271.5010900@cisco.com>
Date: Wed, 31 Jul 2013 09:53:21 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Qin Wu <bill.wu@huawei.com>
References: <51E41F08.4060407@cisco.com> <51E65CAC.9030900@cisco.com> <B8F9A780D330094D99AF023C5877DABA43B6D084@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA43B6D084@nkgeml501-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------030507050004060006090402"
Cc: me <bclaise@cisco.com>, "Aamer Akhter (aakhter)" <aakhter@cisco.com>, "xrblock@ietf.org" <xrblock@ietf.org>
Subject: Re: [xrblock] Fwd: [ippm] Performance Metrics Registry: new draft
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: Wed, 31 Jul 2013 07:55:26 -0000

Hi Qin,
>
> Hi, Benoit:
>
> I think it is useful to provide such performance metrics registry. In 
> most cases, we uses the metrics defined somewhere rather than defining 
> new metrics.
>
> Unfortunately not everyone who writes the PM related draft knows the 
> distinction between using metrics and defining metrics.
>
> Three comments I have:
>
> a. Is performance metrics registry provided for the metrics defined 
> within IETF or metrics defined somewhere else in other SDO?
>
> If the metrics are defined in other SDO, IETF will not provide 
> registry, am I right?
>
Good question: to be discussed.
>
> b. Is performance metrics registry provided for the existing metrics 
> defined in IETF existing RFCs or any other new metrics defined in the 
> new IETF RFCs or any drafts that are in RFC Queue?
>
> If you define performance metrics registry for the existing ones? How 
> do you identify them when RFC6390 template hasn't been applied to them?
>
We will be discussing this point in IPPM today.
Having an IPPM registry will be required.
>
> c. what procedure should I follow if I identify additional set of 
> permanence metrics beyond that is given in the section 4? It is not 
> clear in the draft.
>
What do you propose?

Regards, Benoit
>
> Regards!
>
> -Qin
>
> *From:*xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] *On 
> Behalf Of *Benoit Claise
> *Sent:* Wednesday, July 17, 2013 4:58 PM
> *To:* xrblock@ietf.org
> *Subject:* [xrblock] Fwd: [ippm] Performance Metrics Registry: new draft
>
> Dear all,
>
> You're feedback is welcome regarding this draft.
>
> Regards, Benoit
>
>
>
> -------- Original Message --------
>
> *Subject: *
>
> 	
>
> [ippm] Performance Metrics Registry: new draft
>
> *Date: *
>
> 	
>
> Mon, 15 Jul 2013 18:10:48 +0200
>
> *From: *
>
> 	
>
> Benoit Claise <bclaise@cisco.com> <mailto:bclaise@cisco.com>
>
> *To: *
>
> 	
>
> IETF IPPM WG <ippm@ietf.org> <mailto:ippm@ietf.org>
>
> Dear all,
>   
> Let me introduce
> http://datatracker.ietf.org/doc/draft-claise-ippm-perf-metric-registry/
> This draft creates of a new IANA registry, for performance metrics that
> follows the RFC6390 template.
> And, let's not forget that the IPPM charter mentions: "Metric
> definitions will follow the template given in RFC 6390."
>   
> Thanks Brian for giving me 10 min to present this draft.
>   
> Regards, Benoit.
>   
>   
>   
> _______________________________________________
> ippm mailing list
> ippm@ietf.org  <mailto:ippm@ietf.org>
> https://www.ietf.org/mailman/listinfo/ippm
>   
>   
>