[Entmib] Entity MIB Publication Schedule

"C. M. Heard" <heard@pobox.com> Tue, 04 January 2005 04:42 UTC

Received: from megatron.ietf.org (megatron.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23908 for <entmib-archive@lists.ietf.org>; Mon, 3 Jan 2005 23:42:11 -0500 (EST)
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ClgV7-0008IN-EA; Mon, 03 Jan 2005 23:40:57 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ClgNx-0004tW-96 for entmib@megatron.ietf.org; Mon, 03 Jan 2005 23:33:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23310 for <entmib@ietf.org>; Mon, 3 Jan 2005 23:33:30 -0500 (EST)
Received: from smtpout1.bayarea.net ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ClgaF-0003PV-EM for entmib@ietf.org; Mon, 03 Jan 2005 23:46:15 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net []) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j044X1VA018730 for <entmib@ietf.org>; Mon, 3 Jan 2005 20:33:01 -0800
Received: from shell4.bayarea.net (localhost []) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j044X2vk031157; Mon, 3 Jan 2005 20:33:02 -0800
Received: from localhost (heard@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id j044X1Bl031154; Mon, 3 Jan 2005 20:33:02 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Mon, 3 Jan 2005 20:33:01 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: entmib@ietf.org
Message-ID: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [Entmib] Entity MIB Publication Schedule
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


I intend to post an updated version of the MIB review guidelines
shortly, and one of the normative references is the update to
RFC2737 (currently draft-ietf-entmib-v3-05.txt).  That document is a
normative reference because the PhysicalIndex and
PhysicalIndexOrZero TCs have been listed (at Juergen Schoenwaelder's
request) in Appendix B:  Commonly Used Textual Conventions.

   The following TCs are defined in ENTITY-MIB [RFC2737bis]:

   PhysicalIndex               Integer32 (1..2147483647)
   PhysicalIndexOrZero         Integer32 (0..2147483647)

I added these in the -03 guidelines draft because 2737bis had been
approved for publication, and I assumed that it would be done before
the MIB review guidelines.  I would like to leave them in, but I
don't want to have the guidelines document be help up on account of
delays in publishing 2737bis.

Can anybody offer an educated guess as to when 2737bis will be


Mike Heard

Entmib mailing list