Re: [PMOL] PMOL directorate: meeting at the IETF?

"Aamer Akhter (aakhter)" <aakhter@cisco.com> Wed, 31 October 2012 15:59 UTC

Return-Path: <aakhter@cisco.com>
X-Original-To: pmol@ietfa.amsl.com
Delivered-To: pmol@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2806121F87D5 for <pmol@ietfa.amsl.com>; Wed, 31 Oct 2012 08:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level:
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 X0e9ubr82e5a for <pmol@ietfa.amsl.com>; Wed, 31 Oct 2012 08:59:28 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id D345721F87C4 for <pmol@ietf.org>; Wed, 31 Oct 2012 08:59:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17222; q=dns/txt; s=iport; t=1351699162; x=1352908762; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=GaZFpgjUELWDMr3UUAKYuSxYLqHtynViAUmtOrLVv1A=; b=BElwr+F7i+rMLb5/0JDS2e56fh8dts0ur86YOz4uNq248JboGxtcbxcj sBbwCn7g7TfC5afM62O3uEfWlxxy5cKNQvsGQue/Dv2w9Nr8x4FWj90mi LviD7agX3zkiWFf8DMGGIu1pX3U64ZA94YYB8Ct0v3v4I+jxDU8txqFnR E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFAGBKkVCtJV2Z/2dsb2JhbABEgkm4JQGJAIEIgh4BAQEEEgEaTBACAQgRBAEBCx0HMhQJCAIEAQ0FCBqHZAucN6AWi3iFWmEDlxCNPYFrgm+CGQ
X-IronPort-AV: E=Sophos; i="4.80,687,1344211200"; d="scan'208,217"; a="134383223"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 31 Oct 2012 15:59:21 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q9VFxL1r013144 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 Oct 2012 15:59:21 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.107]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.001; Wed, 31 Oct 2012 10:59:20 -0500
From: "Aamer Akhter (aakhter)" <aakhter@cisco.com>
To: "Benoit Claise (bclaise)" <bclaise@cisco.com>, "pmol@ietf.org" <pmol@ietf.org>
Thread-Topic: [PMOL] PMOL directorate: meeting at the IETF?
Thread-Index: AQHNsKSxCjgAeyQ9vEOO+J2GR0p4+pfTnbrg
Date: Wed, 31 Oct 2012 15:59:20 +0000
Message-ID: <75C0E47A1889264493A2DCB2869AC09631985500@xmb-rcd-x15.cisco.com>
References: <5085C8B9.2050508@cisco.com>
In-Reply-To: <5085C8B9.2050508@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [64.102.41.112]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19324.001
x-tm-as-result: No--56.559800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_75C0E47A1889264493A2DCB2869AC09631985500xmbrcdx15ciscoc_"
MIME-Version: 1.0
Cc: "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>, Ron Bonica <rbonica@juniper.net>, "ippm-chairs@tools.ietf.org" <ippm-chairs@tools.ietf.org>, Wesley Eddy <wes@mti-systems.com>
Subject: Re: [PMOL] PMOL directorate: meeting at the IETF?
X-BeenThere: pmol@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Performance Metrics Directorate list <pmol.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pmol>, <mailto:pmol-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pmol>
List-Post: <mailto:pmol@ietf.org>
List-Help: <mailto:pmol-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pmol>, <mailto:pmol-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 15:59:31 -0000

Just as an FYI:


"  http://tools.ietf.org/html/draft-akhter-opsawg-perfmon-ipfix-03<http://tools.ietf.org/html/draft-akhter-opsawg-perfmon-ipfix-03>"

Explicitly does NOT define any performance metrics-just the IPFIX transport. There are references to other documents (the XRBLOCK, RFC3550, the perf-mon methodology draft, etc.) that do define the metrics. Both this draft and the perf-mon methodology draft (it's expired currently, and I need to update it), are using the templates defined RFC6390. There might be some mistakes here and there, but that is the intent anyway and I'm hopeful that further reviews will make these drafts sharper.

==

That said, I do not disagree with the premise below that the entire performance monitoring (IMHO) creation and dissemination is (frankly) a mess. I would like to propose an enforced clean separation between metrics definition (the methodology and usage etc-which should follow the templates in RFC6390) from the transport-expression of these metrics (RTCP, MIB, IPFIX, syslog whatever), which refer back to the methodology.

Unfortunately, I've got other commitments and will not be in ATL, but very interested in moving this discussion along.


From: pmol-bounces@ietf.org [mailto:pmol-bounces@ietf.org] On Behalf Of Benoit Claise (bclaise)
Sent: Monday, October 22, 2012 6:29 PM
To: pmol@ietf.org
Cc: xrblock-chairs@tools.ietf.org; Ron Bonica; ippm-chairs@tools.ietf.org; Wesley Eddy
Subject: [PMOL] PMOL directorate: meeting at the IETF?

Dear PMOL directorate members,

During my review of the latest AVTCORE and  XRBLOCK drafts ( draft-ietf-xrblock-rtcp-xr-pdv and draft-ietf-avtcore-monarch), I came to the conclusion that we have an issue in terms of performance metrics at the IETF, and actually in the industry.

As background information, here is my DISCUSS on the two drafts

----------------------------------------------------------------------

DISCUSS:

----------------------------------------------------------------------



My entire point is more a DISCUSS-DISCUSS, for both

draft-ietf-avtcore-monarch-19 and draft-ietf-xrblock-rtcp-xr-pdv-05.txt.

Sorry to pick on these two drafts, but we need to have an IESG

performance metrics discussion.

Where does the list of performance metric definitions come from at the

IETF?

We have multiple sources:

- IPPM for IP performance metrics

- RTCP for RTP performance metrics:

  Definitions in the document themselves or potentially referencing some

other SDOs

  Example: http://tools.ietf.org/html/draft-ietf-xrblock-rtcp-xr-pdv-05

   bits 014-011

            0: MAPDV2, Clause 6.2.3.2 of [G.1020],

            1: 2-point PDV, Clause 6.2.4 of [Y.1540].

- PMOL: Performance Metrics at Other Layers, with

  RFC 6076 on Basic Telephony SIP End-to-End Performance Metrics

- IPFIX will one day or the other exports performance metrics.

  I see for example

  http://tools.ietf.org/html/draft-akhter-opsawg-perfmon-ipfix-03<http://tools.ietf.org/html/draft-akhter-opsawg-perfmon-ipfix-03>

  It's again a redefinition, and it should not be!



My concerns are that we start to define performance metrics in different

parts of the IETF, without consistency.



We have defined RFC 6390 on "Guidelines for Considering New Performance

Metric Development", which ask for specific definition

See http://tools.ietf.org/html/rfc6390#section-5.4.4



I believe that the IETF should at least:

- define the performance metrics in a consistent way according to

RFC6390.

- document those performance metrics in a single location



So my questions are:

- are we defining the performance metrics the right way?

- where is this shared repository of performance metrics (at least for

the ones created in the IETF)?

- is the PMOL directorate (RFC 6390) used effectively?
After discussing with Dan Romascanu, we came to this conclusion

I had a discussion with Dan Romascanu, and we settled on:

- RFC 6390 template is required for new perf metric definition

- RFC 6390 template is a nice-to-have when we refer to an existing perf metric

Nice-to-have because the performance metric reference doesn't always include

all the required information about: measurement points, measurement timing, use

and applications, reporting model, etc... but focus only on the "Method of

Measurement or Calculation"
I would like to have a meeting during the IETF, with the following agenda


- are we defining the performance metrics the right way?

- where is this shared repository of performance metrics (at least for

the ones created in the IETF)?

- is the PMOL directorate (RFC 6390) used effectively?

- conclusion discussed with Dan



Here is a doodle invite. Please let me know if/when you are available.

Your feedback on this mailer is also welcome.
Regards, Benoit