RE: MSTP MIB

"Romascanu, Dan \(Dan\)" <[email protected]> Thu, 21 Jul 2005 18:43:29 +0300
Newsgroups gmane.ietf.bridge
Message-ID <AAB4B3D3CF0F454F98272CBE187FDE2F08E3B0BF@is0004avexu1.global.avaya.com>
Juergen,

This version is prior to any review, and I do not believe it's useful to
make comments at this phase.  They are fighting to find an assigned
editor, when someone is in place we will review the documents and
provide all necessary inputs.

Regards,

Dan




> -----Original Message-----
> From: [email protected]=20
> [mailto:[email protected]] On Behalf Of Juergen=20
> Schoenwaelder
> Sent: Thursday, July 21, 2005 6:30 PM
> To: David B Harrington
> Cc: 'Bridge-Mib (E-mail)'
> Subject: Re: [Bridge-mib] MSTP MIB
>=20
> On Thu, Jul 21, 2005 at 10:46:45AM -0400, David B Harrington wrote:
>=20
> > The IEEE 802.1 WG is developing a MIB module for MSTP. The latest=20
> > revision is available at=20
> > http://www.ieee802.org/1/files/public/docs2005/ruzin-mstp-mib-02.txt
> >=20
> > The changes from the previous revision are:
> > 1) The syntax had been debugged (by both ucd-snmp and SNMPc).
> > 2) The object mstpGenCfgIdDigest  has been added.
> > 3) Some ideas from both malhotra-mstpmib-01and=20
> > frattura-mstp-mib-0411.txt have been used
> > 4) The explanations have been inserted (in the clause "3.=20
> Structure of=20
> > MSTP-MIB").
>=20
> Dave, can you advise them to use a decent MIB parser? I did=20
> run the MIB module through libsmi and I was not really=20
> impressed. They seem to mix SMIv2/SMIv1 syntax, they use data=20
> types not properly imported, they have notifications=20
> referencing objects that are not-accessible and so on. The=20
> point is not really to tell them what is broken and why but=20
> to teach them that they better first check whether the tools=20
> they use for syntax checking are actually appropriate.
>=20
> /js
>=20
> --=20
> Juergen Schoenwaelder		    International University Bremen
> <http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561,=20
> 28725 Bremen, Germany
>=20
> _______________________________________________
> Bridge-mib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/bridge-mib
>=20