RE: [802.1] Re: [Bridge-mib] MSTP (IEEE 802.1s) MIB (or draft) ?

"Alex Rozin" <> Thu, 01 April 2004 07:15 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id CAA20941 for <>; Thu, 1 Apr 2004 02:15:32 -0500 (EST)
Received: from localhost.localdomain ([] by with esmtp (Exim 4.20) id 1B8wPn-0003Ev-Fq for; Thu, 01 Apr 2004 02:15:04 -0500
Received: (from exim@localhost) by (8.12.8/8.12.8/Submit) id i317F37P012428 for; Thu, 1 Apr 2004 02:15:03 -0500
Received: from localhost.localdomain ([] by with esmtp (Exim 4.20) id 1B8wPl-0003Dr-Tn; Thu, 01 Apr 2004 02:15:01 -0500
Received: from ([] by with esmtp (Exim 4.20) id 1B8KfD-00025A-9I for; Tue, 30 Mar 2004 09:56:27 -0500
Received: from ietf-mx ( []) by (8.9.1a/8.9.1a) with ESMTP id JAA22583 for <>; Tue, 30 Mar 2004 09:56:23 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1B8KfB-0006Bo-00 for; Tue, 30 Mar 2004 09:56:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B8Kee-00063j-00 for; Tue, 30 Mar 2004 09:55:53 -0500
Received: from ([]) by ietf-mx with esmtp (Exim 4.12) id 1B8Kdo-0005oB-00 for; Tue, 30 Mar 2004 09:55:00 -0500
Received: from Alexr ([]) by (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-44418U200L2S100) with SMTP id AAA2728; Tue, 30 Mar 2004 16:59:28 +0200
Reply-To: <>
From: "Alex Rozin" <>
To: "'Harrington, David'" <>, "'Ali Chanaui'" <>, <>, <>, <>
Subject: RE: [802.1] Re: [Bridge-mib] MSTP (IEEE 802.1s) MIB (or draft) ?
Date: Tue, 30 Mar 2004 16:59:45 +0200
Message-ID: <003d01c41667$a44f27b0$87885ac2@Alexr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <>
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Transfer-Encoding: 7bit

I am ready to participate in this activity as a volunteer.
It seems that my edition of the draft is circulating.
Any feedbacks or/and proposition are encouraged to come

Regards, Alex

Dbh> Hi,
Dbh> There has been inconsistency about whether the mib modules 
Dbh> for new 802.1
Dbh> functionality would be developed by 802.1 or by IETF's 
Dbh> Bridgemib WG. We
Dbh> are working to improve the consistency of that decision. 
Dbh> The IETF Bridgemib WG has some existing work near to 
Dbh> completion, so they
Dbh> will complete it, and then the WG will probably close. All new mib
Dbh> editing work for 802.1 functionality will be done in IEEE 
Dbh> 802.1. Some of
Dbh> the IETF MIB Doctors are providing review services, at least 
Dbh> during the transition.
Dbh> A number of companies have written 802.1s mib modules, and once 802.1
Dbh> has an editor to do the legwork, and the work is approved 
Dbh> within a PAR,
Dbh> that mib module work can be brought into an 802.1 effort. The 802.1 WG
Dbh> needs to assess what is still missing that should be addressed.
Dbh> Volunteers to edit are encouraged to come forward.
Dbh> Dbh
Dbh> David Harrington
Dbh> Acting co-chair, Bridgemib WG
Dbh> Acting MIB Doctor, IEEE 802.1
> Ali> Why does .1x (and .1aa) have MIB and .1w & .1s 
> Ali> don't? It seems, that a MIB
> Ali> is not less important here.
> Ali> 
> Ali> Is WG going to insert a MIB into new .1D?
> Ali> 
> Ali> Regards, Ali

Bridge-mib mailing list