[Bridge-mib] Future directions

"Harrington, David" <dbh@enterasys.com> Wed, 31 March 2004 20:23 UTC

Received: from optimus.ietf.org (optimus.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11209 for <bridge-archive@odin.ietf.org>; Wed, 31 Mar 2004 15:23:51 -0500 (EST)
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8mF8-0001rV-Pm for bridge-archive@odin.ietf.org; Wed, 31 Mar 2004 15:23:23 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VKNM8q007158 for bridge-archive@odin.ietf.org; Wed, 31 Mar 2004 15:23:22 -0500
Received: from localhost.localdomain ([] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8mF0-0001qN-Nj; Wed, 31 Mar 2004 15:23:14 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8mEA-0001oS-HS for bridge-mib@optimus.ietf.org; Wed, 31 Mar 2004 15:22:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11159 for <bridge-mib@ietf.org>; Wed, 31 Mar 2004 15:22:20 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1B8mE9-00008i-00 for bridge-mib@ietf.org; Wed, 31 Mar 2004 15:22:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B8mDA-00006m-00 for bridge-mib@ietf.org; Wed, 31 Mar 2004 15:21:21 -0500
Received: from gtfw2.enterasys.com ([] ident=firewall-user) by ietf-mx with esmtp (Exim 4.12) id 1B8mCg-00004p-00 for Bridge-mib@ietf.org; Wed, 31 Mar 2004 15:20:50 -0500
Received: from NHROCAVG2.ets.enterasys.com (nhrocavg2.enterasys.com []) by gtfw2.enterasys.com (0.25.1/8.12.6) with ESMTP id i2VKKmiR006838 for <Bridge-mib@ietf.org>; Wed, 31 Mar 2004 15:20:48 -0500 (EST)
Received: from NHROCCNC1.ets.enterasys.com ([]) by with InterScan Messaging Security Suite; Wed, 31 Mar 2004 15:20:48 -0500
Received: from source ([]) by host ([]) with SMTP; Wed, 31 Mar 2004 15:20:48 -0500
Received: from nhrocmbx1 ([]) by NHROCCNC1.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 31 Mar 2004 15:20:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 31 Mar 2004 15:20:46 -0500
Message-ID: <6D745637A7E0F94DA070743C55CDA9BA017E1113@NHROCMBX1.ets.enterasys.com>
Thread-Topic: Future directions
Thread-Index: AcQXXaZ1rb6wTKpMS2C783lQS3CDmw==
From: "Harrington, David" <dbh@enterasys.com>
To: <Bridge-mib@ietf.org>
X-OriginalArrivalTime: 31 Mar 2004 20:20:47.0945 (UTC) FILETIME=[A74CEB90:01C4175D]
X-pstn-version: pmps:sps_win32_1_1_0c1 pase:2.5
X-pstn-levels: (C:82.4442 M:97.7712 P:95.9108 R:95.9108 S:26.8380 )
X-pstn-settings: 4 (0.2500:0.7500) p:13 m:13 C:14 r:13
X-pstn-addresses: from <dbh@enterasys.com> forward (org good)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Bridge-mib] Future directions
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable


The bridgemib work has stalled, and we're working to un-stall it.

We have been in discussions with IEEE 802.1, and they are willing to
write their own mibs because this will help them produce mibs
contemporaneously with the managed functionality. I will be providing
MIB Doctor reviews for them during the transition, and possibly after
the transition. IEEE 802.1 plans to publish mibs as part of their
standard in their normal PDF format, and also make the mibs available in
text format for import into mib compilers and applications.

I have been working with Bert, and our current expectation is that the
Bridgemib WG will finalize the existing bridgemib WG documents, and then
presumably close down. I am working to get the four remaining documents
finalized and into WG last call.

Bert raised a good point; we should ask what the implementers and
deployers of the mibs would like as a future direction. So let me
stimulate some discussion, so the powers-that-be in IETF and IEEE have
some guidance:

1) Do you agree with having the IEEE write their own mibs?
2) Will you participate in the IEEE 802.1 process for developing the mib
3) Do you agree the bridgemib WG should be closed down, since it will
have completed its charter?

For future mibs produced by IEEE:
4) Should they also be published as RFCs? 
If they are published as RFCs, this would probably be as Informational
only. The IEEE standard would be the official version, and to the degree
we could achieve it, the IETF might publish a mirror copy. 
5) Synchronization between IEEE/IETF review/publishing cycles has proven
difficult, so we are considering publishing Informational RFCs with only
a pointer to the IEEE standard. Would that suffice?

For existing 802.1-related MIBs (1493, 1525, 2674, et al):
6) Should these be moved to the IEEE?
7) If not, why not? How should the IETF mib modules be maintained as the
IEEE 802.1 technologies change?
8) If yes, what should we do with the existing standards? Would making
them Historic and replacing them with Informational RFCs that point to
the IEEE standards documents suffice?

David Harrington            
Director, Network Management Architecture
Office of the CTO, Enterasys Networks

Bridge-mib mailing list