Re: [ippm] Call for adoption: draft-morton-ippm-initial-registry

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 18 February 2016 10:05 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F13351B35EC; Thu, 18 Feb 2016 02:05:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006] 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 fRNPSp7jvEoT; Thu, 18 Feb 2016 02:05:54 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5339A1B3106; Thu, 18 Feb 2016 02:05:54 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2D3AQDTlsVW/xUHmMZeGQEBAQEPAQEBAYJfK4E/BroYAQ2BZ4YNAoFgOBQBAQEBAQEBZCeEQQEBAQEDEgsdNAQHDAQCAQgNAQMEAQEBChQJBzIUCQgCBAENBQgah3gBoh2ZQQEBAQEBAQEDAQEBAQEBAQEBARaGE4Q6hDWDK4EPBZcFAYhAhnWEQ4MZhTuORx4BAUKDY2qIIwF7AQEB
X-IPAS-Result: A2D3AQDTlsVW/xUHmMZeGQEBAQEPAQEBAYJfK4E/BroYAQ2BZ4YNAoFgOBQBAQEBAQEBZCeEQQEBAQEDEgsdNAQHDAQCAQgNAQMEAQEBChQJBzIUCQgCBAENBQgah3gBoh2ZQQEBAQEBAQEDAQEBAQEBAQEBARaGE4Q6hDWDK4EPBZcFAYhAhnWEQ4MZhTuORx4BAUKDY2qIIwF7AQEB
X-IronPort-AV: E=Sophos;i="5.22,464,1449550800"; d="scan'208";a="161463848"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 Feb 2016 05:05:53 -0500
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES256-SHA; 18 Feb 2016 05:05:53 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Thu, 18 Feb 2016 11:05:30 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: [ippm] Call for adoption: draft-morton-ippm-initial-registry
Thread-Index: AQHRM1Gj3Ombx6Ev3Ea0YhNXsTtcjJ7EomaAgGxcs0CAAMj+gIAAODiw
Date: Thu, 18 Feb 2016 10:05:29 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA6BF1EDD7@AZ-FFEXMB04.global.avaya.com>
References: <B29515E2-0A4D-42D2-93BD-B348910BD98B@trammell.ch> <D28EFB8F.4CFC7%jason.weil@twcable.com> <2D09D61DDFA73D4C884805CC7865E611425E355A@GAALPA1MSGUSRBF.ITServices.sbc.com> <20160218074115.GA4397@elstar.local>
In-Reply-To: <20160218074115.GA4397@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ippm/x2nFFsOZuJ5xXEr2jdmmAr2MNro>
Cc: "lmap@ietf.org" <lmap@ietf.org>
Subject: Re: [ippm] Call for adoption: draft-morton-ippm-initial-registry
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 10:05:57 -0000

(cross-posting LMAP)

I suggest that we discuss the LMAP perspective at the LMAP WG interim on Monday. 

Concrete examples would be indeed very useful.

Regards,

Dan

> -----Original Message-----
> From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Juergen
> Schoenwaelder
> Sent: Thursday, February 18, 2016 9:41 AM
> To: ippm@ietf.org
> Subject: Re: [ippm] Call for adoption: draft-morton-ippm-initial-registry
> 
> Hi,
> 
> since an empty registry is of little value, I think having a initial content defined
> somewhere is essential. In fact, I believe initial content _and_ at least one
> concrete use case example is essential in order to know that the registry
> itself is practically useful.
> 
> I am mostly active in LMAP and not too closely following IPPM so please
> forgive my ignorance. But I generally do believe that a proof of practical
> usability is essential for good specifications. Hence, concrete metric registry
> examples might help to convince us that the registry is a cool thing to have or
> they might show us how to make the registry simpler or easier to use.
> 
> /js
> 
> On Wed, Feb 17, 2016 at 06:45:00PM +0000, STARK, BARBARA H wrote:
> > +1
> > And I'm sorry I totally missed replying to this call in my get-ready-for-
> holidays frenzied mode (in December).
> > Barbara
> >
> > > I support the adoption of this draft as a WG item. It is needed to
> > > create entries for the currently defined IPPM metrics into the
> > > metric registry and is complementary to work coming out of the LMAP
> WG.
> > >
> > > Jason
> > >
> > > On 12/10/15, 8:49 AM, "ippm on behalf of Brian Trammell"
> > > <ippm-bounces@ietf.org on behalf of ietf@trammell.ch> wrote:
> > >
> > > >Greetings, all,
> > > >
> > > >Following support in the room for the adoption of
> > > >draft-morton-ippm-initial-registry in Yokohama, this message starts
> > > >a formal call for adoption of the following milestone:
> > > >
> > > >July 2016: submit a Standards Track document to the IESG defining
> > > >initial contents of performance metric registry
> > > >
> > > >in support of paragraph 7 of our charter:
> > > >
> > > >  Agreement about the definitions of metrics and methods of
> > > >measurement
> > > >  enables accurate, reproducible, and equivalent results across
> > > >different
> > > >  implementations. To this end, the WG will define and maintain a
> > > >registry of
> > > >  metric definitions. The WG encourages work which assesses the
> > > >comparability
> > > >  of measurements of IPPM metrics with metrics developed elsewhere.
> > > >The WG
> > > >  also encourages work which improves the availability of
> > > >information about
> > > >  the context in which measurements were taken.
> > > >
> > > >and to adopt draft-morton-ippm-initial-registry as the document for
> > > >this milestone.
> > > >
> > > >Please express support or concerns with adopting this document by
> > > >31 December 2015 to the IPPM working group mailing list,
> > > >ippm@ietf.org
> > > >
> > > >Many thanks, best regards,
> > > >
> > > >Brian Trammell (chair hat)
> > >
> > >
> > > ________________________________
> > >
> > > This E-mail and any of its attachments may contain Time Warner Cable
> > > proprietary information, which is privileged, confidential, or
> > > subject to copyright belonging to Time Warner Cable. This E-mail is
> > > intended solely for the use of the individual or entity to which it
> > > is addressed. If you are not the intended recipient of this E-mail,
> > > you are hereby notified that any dissemination, distribution,
> > > copying, or action taken in relation to the contents of and
> > > attachments to this E-mail is strictly prohibited and may be
> > > unlawful. If you have received this E-mail in error, please notify
> > > the sender immediately and permanently delete the original and any
> copy of this E-mail and any printout.