Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
Benoit Claise <bclaise@cisco.com> Mon, 23 January 2012 17:36 UTC
Return-Path: <bclaise@cisco.com>
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 5441321F86CF for <opsawg@ietfa.amsl.com>; Mon, 23 Jan 2012 09:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.296
X-Spam-Level:
X-Spam-Status: No, score=-2.296 tagged_above=-999 required=5 tests=[AWL=0.303, BAYES_00=-2.599]
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 MqNuacC-OGGs for <opsawg@ietfa.amsl.com>; Mon, 23 Jan 2012 09:36:02 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFFC21F84A2 for <opsawg@ietf.org>; Mon, 23 Jan 2012 09:36:02 -0800 (PST)
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 q0NHZvoB014581; Mon, 23 Jan 2012 18:35:57 +0100 (CET)
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q0NHZrAI015237; Mon, 23 Jan 2012 18:35:54 +0100 (CET)
Message-ID: <4F1D9A79.8030001@cisco.com>
Date: Mon, 23 Jan 2012 18:35:53 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: 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>
In-Reply-To: <20120122152950.GB42368@elstar.local>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [OPSAWG] WGLC draft-ietf-opsawg-management-stds
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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 17:36:03 -0000
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. > > > 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. Thanks again. Regards, Benoit
- [OPSAWG] WGLC draft-ietf-opsawg-management-stds Christopher LILJENSTOLPE
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Juergen Schoenwaelder
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Benoit Claise
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Juergen Schoenwaelder
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Benoit Claise
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Juergen Schoenwaelder
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… David Harrington
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Romascanu, Dan (Dan)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Romascanu, Dan (Dan)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… Bert Wijnen (IETF)
- Re: [OPSAWG] WGLC draft-ietf-opsawg-management-st… David Harrington
- [OPSAWG] FW: WGLC draft-ietf-opsawg-management-st… Ersue, Mehmet (NSN - DE/Munich)
- [OPSAWG] IPv6 zoneid in SNMP t.petch
- Re: [OPSAWG] IPv6 zoneid in SNMP Juergen Schoenwaelder
- Re: [OPSAWG] IPv6 zoneid in SNMP Brian E Carpenter