RE: [Bridge-mib] Future directions

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Fri, 02 April 2004 22:10 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06882 for <bridge-archive@odin.ietf.org>; Fri, 2 Apr 2004 17:10:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9W3F-00067E-Ns for bridge-archive@odin.ietf.org; Fri, 02 Apr 2004 16:18:10 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i32LI9Ku023509 for bridge-archive@odin.ietf.org; Fri, 2 Apr 2004 16:18:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9SYQ-00018Z-GD; Fri, 02 Apr 2004 12:34:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9Qza-0007lo-Bj for bridge-mib@optimus.ietf.org; Fri, 02 Apr 2004 10:54:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15054 for <bridge-mib@ietf.org>; Fri, 2 Apr 2004 10:53:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B9QzX-0002d2-00 for bridge-mib@ietf.org; Fri, 02 Apr 2004 10:53:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B9QyY-0002TX-00 for bridge-mib@ietf.org; Fri, 02 Apr 2004 10:52:59 -0500
Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1B9QxZ-0002KQ-00 for Bridge-mib@ietf.org; Fri, 02 Apr 2004 10:51:57 -0500
Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i32FlQE0023941 for <Bridge-mib@ietf.org>; Fri, 2 Apr 2004 10:47:26 -0500 (EST)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i32FlOE0023895 for <Bridge-mib@ietf.org>; Fri, 2 Apr 2004 10:47:25 -0500 (EST)
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Bridge-mib] Future directions
Date: Fri, 2 Apr 2004 17:51:54 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F05C4C3DC@is0004avexu1.global.avaya.com>
Thread-Topic: Future directions
Thread-Index: AcQXXaZ1rb6wTKpMS2C783lQS3CDmwA2Hnow
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Harrington, David" <dbh@enterasys.com>, <Bridge-mib@ietf.org>
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
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

My 2 agorot (~ 0.8 cents) in-text.

Regards,

Dan



> -----Original Message-----
> From: bridge-mib-admin@ietf.org 
> [mailto:bridge-mib-admin@ietf.org]On Behalf Of Harrington, David
> Sent: 31 March, 2004 10:21 PM
> To: Bridge-mib@ietf.org
> Subject: [Bridge-mib] Future directions
> 
> 
> Hi,
> 
> 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?

yes

> 2) Will you participate in the IEEE 802.1 process for 
> developing the mib
> modules?

yes

> 3) Do you agree the bridgemib WG should be closed down, since it will
> have completed its charter?
> 
yes

> 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. 

yes, if the IEEE 802.1 WG wishes it so.

> 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?
> 

yes. If this was a problem for a large base of customers or users of these MIBs, we would have seen a more consistent participation in the Bridge MIB WG.

> For existing 802.1-related MIBs (1493, 1525, 2674, et al):
> 6) Should these be moved to the IEEE?

yes, if the IEEE 802.1 WG wishes so.

> 7) If not, why not? How should the IETF mib modules be 
> maintained as the
> IEEE 802.1 technologies change?

No, because this becomes an IEEE problem. The last years experience shows that there is no longer enough interest in the IETF to sustain IEEE 802.1 MIBs development and maintenance.

> 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?

One Informational RFC defining this process, and pointing to the IEEE standards documents would be welcome.

> 
> David Harrington            
> dbh@enterasys.com
> Director, Network Management Architecture
> Office of the CTO, Enterasys Networks
> 
> 
> _______________________________________________
> Bridge-mib mailing list
> Bridge-mib@ietf.org
> https://www1.ietf.org/mailman/listinfo/bridge-mib
> 

_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib