Re: [ippm] next steps with IPPM registry
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Tue, 01 December 2015 10:04 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 4A4F61B3A54 for <ippm@ietfa.amsl.com>; Tue, 1 Dec 2015 02:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level:
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 q0O1uTNoVHwO for <ippm@ietfa.amsl.com>; Tue, 1 Dec 2015 02:04:23 -0800 (PST)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF71E1B3A51 for <ippm@ietf.org>; Tue, 1 Dec 2015 02:04:22 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id B2E99E7C; Tue, 1 Dec 2015 11:04:20 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id f6-_mrJpNxKJ; Tue, 1 Dec 2015 11:04:19 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Tue, 1 Dec 2015 11:04:19 +0100 (CET)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 909F720055; Tue, 1 Dec 2015 11:04:19 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id ydSx3lpFJmgT; Tue, 1 Dec 2015 11:04:18 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id EE4D420054; Tue, 1 Dec 2015 11:04:17 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 86BF2390A58A; Tue, 1 Dec 2015 11:04:09 +0100 (CET)
Date: Tue, 01 Dec 2015 11:04:09 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Message-ID: <20151201100408.GA46235@elstar.local>
Mail-Followup-To: marcelo bagnulo braun <marcelo@it.uc3m.es>, "ippm@ietf.org" <ippm@ietf.org>, "Barbara.Stark@bellsouth.com" <Barbara.Stark@bellsouth.com>
References: <565D3293.9080204@it.uc3m.es>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <565D3293.9080204@it.uc3m.es>
User-Agent: Mutt/1.4.2.3i
Archived-At: <http://mailarchive.ietf.org/arch/msg/ippm/ZYe1P34XeA1E2A9h-7z-zD-0isc>
Cc: "Barbara.Stark@bellsouth.com" <Barbara.Stark@bellsouth.com>, "ippm@ietf.org" <ippm@ietf.org>
Subject: Re: [ippm] next steps with IPPM registry
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
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: Tue, 01 Dec 2015 10:04:25 -0000
On Tue, Dec 01, 2015 at 06:39:31AM +0100, marcelo bagnulo braun wrote: > Hi, > > I understand that the only remaining open issue with the registry is to > figure out if/how we want to include machine readable information in it. > > In order to figure this out, i understand the idea was for proponents of > doing so should explain the use cases they have in mind, so we can > understand if we want to do this and now. > > I understand Barbara and Juergen were proposing this, so could you (or > anyone else who thinks this is a good idea) to explain the use cases? > I think the question is which role the registry plays in the overall framework. Is it (i) primarily some form of documentation an MA can refer to or (ii) is the idea that the registry is normative when it comes to run-time parameters and data formats. In the later case, I think it is desirable that tools can work with the portions of the registry that are used by implementations in order to drive automation (and this likely also requires putting restrictions on say parameter names - for example, the parameter name '1/lambda' in draft-morton-ippm-initial-registry-01.txt is likely troublesome if you take it literally in implementations). Perhaps the answer is in between, namely that the registry is primarily documentation for humans and that a formalization of the parameters that are relevant for implementations is a separate step (e.g., for metric X in the registry, some human writes a concrete YANG module defining the concrete configuration parameters to configure metric X following the guidelines given in the registry). If the registry is primarily documentation (and this is what section 5 might be saying), then I would prefer if parameters are described with their semantics and units and precision but not the specific encoding. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/>
- [ippm] next steps with IPPM registry marcelo bagnulo braun
- Re: [ippm] next steps with IPPM registry Juergen Schoenwaelder
- Re: [ippm] next steps with IPPM registry MORTON, ALFRED C (AL)
- Re: [ippm] next steps with IPPM registry Juergen Schoenwaelder
- Re: [ippm] next steps with IPPM registry Weil, Jason
- Re: [ippm] next steps with IPPM registry MORTON, ALFRED C (AL)
- Re: [ippm] next steps with IPPM registry MORTON, ALFRED C (AL)