Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 23 January 2012 19:12 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF7921F86C1 for <opsawg@ietfa.amsl.com>; Mon, 23 Jan 2012 11:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.23
X-Spam-Level:
X-Spam-Status: No, score=-103.23 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 TxxujDOYajG6 for <opsawg@ietfa.amsl.com>; Mon, 23 Jan 2012 11:12:57 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 0F82F21F8618 for <opsawg@ietf.org>; Mon, 23 Jan 2012 11:12:57 -0800 (PST)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 2F989206A6; Mon, 23 Jan 2012 20:12:56 +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 2IAgUFC8kBGZ; Mon, 23 Jan 2012 20:12:56 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id B3B0420222; Mon, 23 Jan 2012 20:12:55 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 318C31C98E80; Mon, 23 Jan 2012 20:12:37 +0100 (CET)
Date: Mon, 23 Jan 2012 20:12:37 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20120123191237.GA47321@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, Christopher LILJENSTOLPE <ietf@cdl.asgaard.org>, opsawg@ietf.org, draft-ietf-opsawg-management-stds@tools.ietf.org
References: <519C94F2-F0FB-46EE-AD8F-426E389F62B9@cdl.asgaard.org> <20120122152950.GB42368@elstar.local> <4F1D9A79.8030001@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4F1D9A79.8030001@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: opsawg@ietf.org, draft-ietf-opsawg-management-stds@tools.ietf.org
Subject: Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2012 19:12:58 -0000

On Mon, Jan 23, 2012 at 06:35:53PM +0100, Benoit Claise wrote:
> Juergen,
> 
> Thanks for your careful feedback, and suggestions.
> I specifically like the fact that you cared to propose some new text.
> 
> Two comments
> >
> >x) I doubt these are in any way practically relevant nor am I sure
> >    about the support agreement argument. This neither RFC3165 nor
> >    RFC4011 seem to be used in practice, I would rather drop these
> >    three paragraphs.
> >
> >    OLD:
> >
> >    [RFC3165] supports the use of user-written scripts to delegate
> >    management functionality.
> >
> >    Policy Based Management MIB [RFC4011] defines objects that enable
> >    policy-based monitoring using SNMP, using a scripting language, and a
> >    script execution environment.
> >
> >    Few vendors have implemented MIB modules that support scripting.
> >    Some vendors consider running user-developed scripts within the
> >    managed device as a violation of support agreements.
> >
> >    NEW:
> 
> BC>  Not sure if "This neither RFC3165 nor RFC4011 seem to be used in
> practice" is a good argument.
> So I would rather keep, as this RFC is supposed to be an inventory.

I think you told me several times it is not inventory. If this is
supposed to be an inventory, then I must say the document is somewhat
incomplete. That said, I am religious since a reference to 3165 is
actually good for my h-index (but otherwise likely more confusing
readers than helping them ;-).

> >z) Why do we have text for something that according to RFC 6248 has
> >    seen no usage?
> >
> >    OLD:
> >
> >    The IPPM working group has defined [BCP108][RFC4148] "IP Performance
> >    Metrics (IPPM) Metrics Registry".  The IANA-assigned registry
> >    contains an initial set of OBJECT IDENTITIES to currently defined
> >    metrics in the IETF as well as defines the rules for adding IP
> >    Performance Metrics that are defined in the future.  However, the
> >    current registry structure has been found to be insufficiently
> >    detailed to uniquely identify IPPM metrics.  Due to the ambiguities
> >    between the current metrics registrations and the metrics used, and
> >    the apparent non-adoption of the registry in practice, it has been
> >    proposed to reclassify [RFC4148] as Obsolete.
> >
> >    Note: With the publication of [RFC6248] the latest IANA registry for
> >    IPPM metrics and [RFC4148] have been declared Obsolete and IANA
> >    prevents registering new metrics.  Actual users can continue using
> >    the current registry and its contents.
> >
> >    NEW:
> 
> BC>  Since this decision [RFC6248] is brand new, I would rather keep the second
> paragraph. A little bit of history would not hurt.
> 

I remain unconvinced that pointing readers to stuff that is not used
(and where it is even documented that it is not used) is helpful. A
historic perspective of the development of NM standards I think is a
different document.

/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/>