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

"Alex Rozin" <Arozin@mrv.com> Fri, 02 April 2004 15:07 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 KAA11907 for <bridge-archive@odin.ietf.org>; Fri, 2 Apr 2004 10:07:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9N65-00029j-QY for bridge-archive@odin.ietf.org; Fri, 02 Apr 2004 06:44:29 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i32BiTAJ008285 for bridge-archive@odin.ietf.org; Fri, 2 Apr 2004 06:44:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B9IsL-0004Ai-Ok; Fri, 02 Apr 2004 02:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B91Ft-000783-1b for bridge-mib@optimus.ietf.org; Thu, 01 Apr 2004 07:25:09 -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 HAA08628 for <bridge-mib@ietf.org>; Thu, 1 Apr 2004 07:25:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B91Fs-0003N0-00 for bridge-mib@ietf.org; Thu, 01 Apr 2004 07:25:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B91Eu-0003IP-00 for bridge-mib@ietf.org; Thu, 01 Apr 2004 07:24:11 -0500
Received: from apollo.nbase.co.il ([194.90.137.2]) by ietf-mx with esmtp (Exim 4.12) id 1B91Dt-0003AM-00 for Bridge-mib@ietf.org; Thu, 01 Apr 2004 07:23:05 -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 AAA2862; Thu, 1 Apr 2004 14:28:30 +0200
Reply-To: <Arozin@mrv.com>
From: "Alex Rozin" <Arozin@mrv.com>
To: "'Elisabeth Gloria'" <green_elisabeth@yahoo.com.au>, <Bridge-mib@ietf.org>
Cc: <stds-802-1@ieee.org>
Subject: RE: [802.1] Re: [Bridge-mib] MSTP (IEEE 802.1s) MIB (or draft) ?
Date: Thu, 1 Apr 2004 14:27:47 +0200
Message-ID: <006b01c417e4$be7e5830$87885ac2@Alexr>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_006C_01C417F5.82072830"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <20040401114327.87529.qmail@web13126.mail.yahoo.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.1 required=5.0 tests=AWL,UPPERCASE_25_50 autolearn=no version=2.60
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>

Beth,

On Thursday, April 01 you wrote:
> IMO this [the MSTP MIB draft] is a most relevant place
> to public this document.
OK, I make you responsible for this :)
I attached here a last edition of the draft and a result of
its compilation with snmptranslate.

> Apropos, may I ask you regarding your MIB?
> I see here (I mean an edition, that Thom sent me),
> that there are a few objects, that are absent
> in .1s, for example, port roles (dot1sXstPortRole)
> and ports STP traffic counters
> (like dot1sPortTxMstBpduCounter). Why do you want
> to have these objects in the MIB?
Yes, the bitter experience of management large or/and
complicated networks shows, that managers would like
to know the reasons of established port states. It constrains
to insert the object dot1sXstPortRole.
Counters like dot1sPortTxMstBpduCounter carries out a similar
function, but more for a debugging.

With respect, Alex