Re: [Entmib] Entity MIB Publication Schedule

Kaj Tesink <kaj@research.telcordia.com> Tue, 04 January 2005 18:46 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06880 for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 13:46:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Clteo-00067e-IB; Tue, 04 Jan 2005 13:43:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CltXk-0002LC-IJ for entmib@megatron.ietf.org; Tue, 04 Jan 2005 13:36:32 -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 NAA05677 for <entmib@ietf.org>; Tue, 4 Jan 2005 13:36:31 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cltk9-0003iD-CN for entmib@ietf.org; Tue, 04 Jan 2005 13:49:22 -0500
Received: from shannon.research.telcordia.com (shannon [128.96.81.11]) by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id j04IZj5u028337; Tue, 4 Jan 2005 13:35:49 -0500 (EST)
Received: from KAJ-2.research.telcordia.com (pc22535.cc.telcordia.com [128.96.171.169]) by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA06244; Tue, 4 Jan 2005 13:35:42 -0500 (EST)
Message-Id: <6.1.2.0.2.20050104132350.01dc6ec0@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Tue, 04 Jan 2005 13:25:42 -0500
To: j.schoenwaelder@iu-bremen.de
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
In-Reply-To: <20050104174401.GA2834@james>
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net> <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net> <4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com> <20050104174401.GA2834@james>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: entmib@ietf.org, Andy Bierman <abierman@cisco.com>
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
Sender: entmib-bounces@ietf.org
Errors-To: entmib-bounces@ietf.org

At 12:44 PM 1/4/2005, Juergen Schoenwaelder wrote:
>On Tue, Jan 04, 2005 at 08:47:15AM -0800, Andy Bierman wrote:
>
> > Does 2737bis need a normative reference to the CLEI URN I-D?
> > I think so, if it's mentioned inside an OBJECT-TYPE macro.
>
>Probably depends on the details of the wording. If the CLEI URNs
>are used as usage examples while the precise format is expressed
>in terms of general URI formats, one could argue that a suitable
>URI RFC would be normative while the specific CLEI URNs are
>informative examples. If we make the ENTITY-MIB depend on the
>CLEI URN I-D, we open another can of worms and delays.


Since the CLEI is just an example of the use of that object
I'd suggest that the ENTITY-MIB can not depend on it,
and therefore it should not be normative, no?

kaj





>/js
>
>--
>Juergen Schoenwaelder               International University Bremen
><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany
>
>_______________________________________________
>Entmib mailing list
>Entmib@ietf.org
>https://www1.ietf.org/mailman/listinfo/entmib


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
Email: kaj@research.telcordia.com
Tel: (732) 699-6068
Fax: (732) 336-2336

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


_______________________________________________
Entmib mailing list
Entmib@ietf.org
https://www1.ietf.org/mailman/listinfo/entmib