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

"Alex Rozin" <Arozin@mrv.com> Thu, 01 April 2004 07:15 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 CAA20941 for <bridge-archive@odin.ietf.org>; Thu, 1 Apr 2004 02:15:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8wPn-0003Ev-Fq for bridge-archive@odin.ietf.org; Thu, 01 Apr 2004 02:15:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i317F37P012428 for bridge-archive@odin.ietf.org; Thu, 1 Apr 2004 02:15:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8wPl-0003Dr-Tn; Thu, 01 Apr 2004 02:15:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8KfD-00025A-9I for bridge-mib@optimus.ietf.org; Tue, 30 Mar 2004 09:56:27 -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 JAA22583 for <bridge-mib@ietf.org>; Tue, 30 Mar 2004 09:56:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B8KfB-0006Bo-00 for bridge-mib@ietf.org; 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 bridge-mib@ietf.org; Tue, 30 Mar 2004 09:55:53 -0500
Received: from apollo.nbase.co.il ([194.90.137.2]) by ietf-mx with esmtp (Exim 4.12) id 1B8Kdo-0005oB-00 for Bridge-mib@ietf.org; Tue, 30 Mar 2004 09:55:00 -0500
Received: from Alexr ([194.90.136.135]) by apollo.nbase.co.il (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: <Arozin@mrv.com>
From: "Alex Rozin" <Arozin@mrv.com>
To: "'Harrington, David'" <dbh@enterasys.com>, "'Ali Chanaui'" <ali_chanaui@yahoo.com>, <stds-802-1@ieee.org>, <Bridge-mib@ietf.org>, <Les_Bell@3com.com>
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: <6D745637A7E0F94DA070743C55CDA9BA017E1007@NHROCMBX1.ets.enterasys.com>
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 ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,
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
forward.

Regards, Alex

Dbh> Hi,
Dbh> 
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> 
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> 
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> 
Dbh> Volunteers to edit are encouraged to come forward.
Dbh> 
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
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib