|
|
This is a frozen OID (no more child OIDs can be added to the existing ones).
|
OID:
|
|
(ASN.1 notation) |
|
(dot notation) |
|
(OID-IRI notation) |
|
|
Description:
|
dot1dBridge MODULE-IDENTITY
LAST-UPDATED "200509190000Z"
ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO
"Email: bridge-mib@ietf.org
K.C. Norseth (Editor)
L-3 Communications
Tel: +1 801-594-2809
Email: kenyon.c.norseth@L-3com.com
Postal: 640 N. 2200 West.
Salt Lake City, Utah 84116-0850
Les Bell (Editor)
3Com Europe Limited
Phone: +44 1442 438025
Email: elbell@ntlworld.com
Postal: 3Com Centre, Boundary Way
Hemel Hempstead
Herts. HP2 7YU
UK
Send comments to <bridge-mib@ietf.org>"
DESCRIPTION
"The Bridge MIB module for managing devices that support IEEE 802.1D.
Copyright (C) The Internet Society (2005). This version of this MIB module is part of RFC 4188; see the RFC itself for full legal notices."
REVISION "200509190000Z"
DESCRIPTION
"Third revision, published as part of RFC 4188.
The MIB module has been converted to SMIv2 format.
Conformance statements have been added and some description and reference clauses have been updated.
The object dot1dStpPortPathCost32 was added to support IEEE 802.1t and the permissible values of dot1dStpPriority and dot1dStpPortPriority have been clarified for bridges supporting IEEE 802.1t or IEEE 802.1w.
The interpretation of dot1dStpTimeSinceTopologyChange has been clarified for bridges supporting the Rapid Spanning Tree Protocol (RSTP)."
REVISION "199307310000Z"
DESCRIPTION
"Second revision, published as part of RFC 1493."
REVISION "199112310000Z"
DESCRIPTION
"Initial revision, published as part of RFC 1286."
|
|
Information:
|
See IETF RFC 4188. Note: The practice of registering related MIB modules below this OID has been discouraged since there is no robust mechanism to track such registrations.
See also IETF RFC 4663 "Transferring Management Information Base (MIB) Work from IETF Bridge MIB Working Group (WG) to IEEE 802.1 WG", in particular section 2.3 "Transferring MIB Work from IETF Bridge MIB WG to IEEE 802.1 WG".
|
|
Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved © 2007-2024 |