RE: [ipcdn] The prefix for the DOCSIS-IEFT-QOS-MIB
"Fred Oko" <foko@c-cor.net> Wed, 26 January 2005 01:05 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03131 for <ipcdn-archive@ietf.org>; Tue, 25 Jan 2005 20:05:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ctbt8-0001ZW-Gl for ipcdn-archive@ietf.org; Tue, 25 Jan 2005 20:22:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CtbTZ-0005jh-7x; Tue, 25 Jan 2005 19:56:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CtbRp-0005ED-8H for ipcdn@megatron.ietf.org; Tue, 25 Jan 2005 19:54:17 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01922 for <ipcdn@ietf.org>; Tue, 25 Jan 2005 19:54:13 -0500 (EST)
Received: from mail.stargus.com ([65.193.169.166] helo=xchange.stargus.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Ctbid-0001Az-BY for ipcdn@ietf.org; Tue, 25 Jan 2005 20:11:39 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [ipcdn] The prefix for the DOCSIS-IEFT-QOS-MIB
Date: Tue, 25 Jan 2005 19:54:02 -0500
Message-ID: <6FEBB4954538C7408210BEDBE4843642311E7E@xchange.stargus.com>
Thread-Topic: [ipcdn] The prefix for the DOCSIS-IEFT-QOS-MIB
Thread-Index: AcUCLkTFlxGAzsd7QGKBcYXGqyupfQBD//Qw
From: Fred Oko <foko@c-cor.net>
To: Murwin William-LWM008 <W.Murwin@motorola.com>, "IPCDN (E-mail) (E-mail)" <ipcdn@ietf.org>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 32a65c0bf5eb4ec26489239c7cdd0636
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>, Patrick Michael-LZZ007 <Michael.Patrick@motorola.com>, Richard_woundy@cable.comcast.com
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0884671515=="
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 5b943e80df8c8cad631fd60298783617
Arguably, the QOS-MIB needs this distinguisher the most across the current IPCDN drafts as a given short name may actually map to a different OID. So even if both versions could be installed, the matching algorithm for finding the OID to use may vary (though clearly fully-qualified (or at least MODULE::leaf style) requests are best practice to lock down the desired namespace at the client so this is only corner case). Would we consider whether this should be done for the other pre-RFC draft MIBs awaiting re-root on a case by case basis or select this as policy moving forward (or assume this is the only one as this is the only one for which the MODULE-IDENTITY has changed due to object renumbers)? I do not know of any precedence of such a rename in working-implementation draft MIBs (anyone else?) and definitely am not aware of 'Ietf' being placed into the object names by any other WG though it seems as good a choice as any except for the growing prefix length (granted, of no real operational concern). If nothing else, the suggested change improves consistency between the object prefix and the already agreed upon MODULE-IDENTITY. -----Original Message----- From: Murwin William-LWM008 [mailto:W.Murwin@motorola.com] Sent: Monday, January 24, 2005 10:57 AM To: IPCDN (E-mail) (E-mail) Cc: Jean-Francois Mule; Patrick Michael-LZZ007; Richard_woundy@cable.comcast.com Subject: [ipcdn] The prefix for the DOCSIS-IEFT-QOS-MIB I am currently in the process of updating the draft-ietf-ipcdn-qos-mib-11.txt, in-order to address the rooting issue of this MIB. There has been significant discussion about how this version and version 4 will exist together in SNMP manager and agents. IPCDN even went as far as changing this mib MODULE-IDENTIER in order to be able to support both mibs within the same SNMP manager. However, from my own personal experience this seems not to be enough for some SNMP managers, and usually only one of the version can only be installed. With this update I am willing on change the the MIB Module Descriptor from "docsQosMIB" to "docsIetfQosMIB" and changing all the MIB objects prefix from "docsQos" to "docsIetfQos". Please respond if you feel strongly either way. Sincerely, Will ______________________________ William Murwin Broadband Communications Sector Motorola Inc. Email: W.Murwin@motorola.com Tel: (508) 786-7594 _______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn
_______________________________________________ IPCDN mailing list IPCDN@ietf.org https://www1.ietf.org/mailman/listinfo/ipcdn
- [ipcdn] The prefix for the DOCSIS-IEFT-QOS-MIB Murwin William-LWM008
- [ipcdn] RE: The prefix for the DOCSIS-IEFT-QOS-MIB Jean-Francois Mule
- Re: [ipcdn] The prefix for the DOCSIS-IEFT-QOS-MIB Randy Presuhn
- RE: [ipcdn] The prefix for the DOCSIS-IEFT-QOS-MIB Fred Oko