Re: RSTP-MIB extension suggestion

"Les Bell" <[email protected]> Mon, 13 Sep 2004 09:02:12 +0100
Newsgroups gmane.ietf.bridge
Message-ID <[email protected]>


I think the 'Port Role' fits in the category of diagnostic information that is
potentially useful for developers while debugging their implementations.  I do
not object to adding a MIB item for it, but I do not think it is essential.

A change that was introduced in 802.1D-2004 (clause 17.3.3) that does require a
new MIB item is the 'autoEdgePort' parameter.  This extends the adminEdgePort
functionality to allow automatic detection of an Edge Port, with a short delay
before it enters the Forwarding state.  802.1D-2004 chose to add this as an
optional, seperately managed object so as not to make implementations that
supported the existing adminEdgePort non-conformant.

It may be worth completing the RSTP MIB as it is currently, and waiting for IEEE
802.1 to pick up any new work to add these MIB objects.  Any opinons?

Les...





Johannes Herlitz <[email protected]> on 11/09/2004 19:09:24

Sent by:  Johannes Herlitz <[email protected]>


To:   Les Bell/GB/3Com, [email protected]
cc:
Subject:  RSTP-MIB extension suggestion


Hi,

I've been working on a master thesis which deals a lot with the spanning
tree protocol. Since

http://ietfreport.isoc.org/ids/draft-ietf-bridge-rstpmib-04.txt

is a draft and later on should be a request for comments, I hereby
suggest an extension: Since RSTP decouples the role of a port from its
state (see table 17-1 of IEEE 802.1w, chapter 17.5, p.30) the role of a
port should be accessible via the RSTP MIB, too. The port role could be
added to the dot1dStpExtPortTable using this OID/MIB:

dot1dStpPortRole (.1.3.6.1.2.1.17.2.19.1.7)

which should be an enum holding the values "Unknown (0)", "Alternate
(1)", "Backup (2)", "Root (3)", "Designated (4)" and "Disabled (5)".
Alternatively, it also could be a less detailed enum just
differentiating between the port role as transmitted in the flags field
of a RST BPDU (see chapter 9.2.9. of IEEE 802.1w, p.12): "Unknown (0)",
"Alternate or Backup (1)", "Root (2)", "Designated (3)"
I'd prefer the first, more detailed enum.

Whats your opinion about this extension?