Re: [Entmib] Entity MIB Publication Schedule

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Tue, 04 January 2005 17:57 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 MAA02383 for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 12:57:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Clsqy-0000k0-RR; Tue, 04 Jan 2005 12:52:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ClsjX-0006Vq-8h for entmib@megatron.ietf.org; Tue, 04 Jan 2005 12:44:41 -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 MAA01233 for <entmib@ietf.org>; Tue, 4 Jan 2005 12:44:36 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Clsvt-0002OB-6k for entmib@ietf.org; Tue, 04 Jan 2005 12:57:28 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 00CB8D645; Tue, 4 Jan 2005 18:44:04 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 23232-06; Tue, 4 Jan 2005 18:44:03 +0100 (CET)
Received: from james (I951b.i.pppool.de [85.73.149.27]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id 08A59D5F0; Tue, 4 Jan 2005 18:44:03 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34) id 1Clsiv-0000ju-3D; Tue, 04 Jan 2005 18:44:01 +0100
Date: Tue, 4 Jan 2005 18:44:01 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
Message-ID: <20050104174401.GA2834@james>
Mail-Followup-To: Andy Bierman <abierman@cisco.com>, entmib@ietf.org
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: entmib@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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

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.

/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