draft-ietf-bridge-bridgemib-smiv2-04.txt   draft-ietf-bridge-bridgemib-smiv2-05.txt 
Internet Draft Editors of this version: Internet Draft K.C. Norseth
Expires June 2003 K.C. Norseth Expires December 2003 L-3 Communications
draft-ietf-bridge-bridgemib-smiv2-04.txt L-3 Communications draft-ietf-bridge-bridgemib-smiv2-05.txt E. Bell
Obsoletes: 1493 E. Bell Obsoletes: 1493 3Com Corp.
3Com Corp. July 2003
Authors of previous version:
E. Decker
Cisco Systems, Inc.
P. Langille
Newbridge Networks
A. Rijhsinghani
Enterasys Networks
K. McCloghrie
Cisco Systems, Inc.
Oct 2002
Definitions of Managed Objects for Bridges Definitions of Managed Objects for Bridges
Status of this Memo Status of this Memo
This document is an Internet Draft and is in full conformance with This document is an Internet-Draft and is subject to all provisions
all provisions of Section 10 of RFC2026. Internet Drafts are working of Section 10 of RFC2026.
documents of the Internet Engineering Task Force (IETF), its Areas,
and its Working Groups. Note that other groups may also distribute
working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Internet-Drafts are working documents of the Internet Engineering
months. Internet Drafts may be updated, replaced, or obsoleted by Task Force (IETF), its areas, and its working groups. Note that
other documents at any time. It is not appropriate to use Internet other groups may also distribute working documents as Internet-
Drafts as reference material or to cite them other than as a "working Drafts.
draft" or "work in progress."
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html
To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP based internets.
In particular it defines objects for managing MAC bridges based on In particular it defines objects for managing MAC bridges based on
the IEEE 802.1D-1998 standard between Local Area Network (LAN) the IEEE 802.1D-1998 standard between Local Area Network (LAN)
segments. Provisions are made for support of transparent bridging. segments. Provisions are made for support of transparent bridging.
Provisions are also made so that these objects apply to bridges Provisions are also made so that these objects apply to bridges
connected by subnetworks other than LAN segments. connected by subnetworks other than LAN segments.
The MIB presented in this memo is a direct translation of the BRIDGE The MIB presented in this memo is a direct translation of the BRIDGE
MIB defined in [RFC1493], to the SMIv2 syntax required for current MIB defined in [RFC1493], to the SMIv2 syntax required for current
IETF MIB standards. This memo obsoletes RFC 1493. IETF MIB standards. This memo obsoletes RFC 1493.
Table of Contents
1. The SNMP Management Framework ........................ 2
2. Overview ............................................. 3
2.1. Structure of MIB ..................................... 3
2.1.1. The dot1dBase Group .................................. 5
2.1.2. The dot1dStp Group ................................... 5
2.1.3. The dot1dSr Group .................................... 6
2.1.4. The dot1dTp Group .................................... 6
2.1.5. The dot1dStatic Group ................................ 6
2.2. Relationship to Other MIBs ........................... 6
2.2.1. Relationship to the 'system' group ................... 6
2.2.2. Relationship to the 'interfaces' group ............... 6
2.3. Textual Conventions .................................. 7
3. Definitions .......................................... 7
4. Security Considerations .............................. 34
5. Acknowledgments ...................................... 34
6. Normative References ................................. 35
7. Informative References ............................... 36
8. Changes from RFC 1493 ................................. 36
9. Authors' Addresses ................................... 37
10. Full Copyright Statement ............................. 37
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
skipping to change at page 8, line 7 skipping to change at page 8, line 15
Counter32, Integer32, TimeTicks, mib-2 Counter32, Integer32, TimeTicks, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, MacAddress TEXTUAL-CONVENTION, MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InterfaceIndex FROM IF-MIB InterfaceIndex FROM IF-MIB
; ;
bridgeMIB MODULE-IDENTITY bridgeMIB MODULE-IDENTITY
LAST-UPDATED "200212050000Z" LAST-UPDATED "200307240000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org" "Email: Bridge-mib@ietf.org
K.C. Norseth
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
3Com Europe Limited
Phone: +44 1442 438025
Email: Les_Bell@3Com.com
Postal: 3Com Centre, Boundary Way
Hemel Hempstead
Herts. HP2 7YU
UK
Send comments to <bridge-mib@ietf.org>"
DESCRIPTION DESCRIPTION
"The Bridge MIB module for managing devices that support "The Bridge MIB module for managing devices that support
IEEE 802.1D." IEEE 802.1D.
REVISION "200212050000Z"
Copyright (C) The Internet Society (2003). This version of
this MIB module is part of RFC xxxx; see the RFC itself for
full legal notices."
REVISION "200307240000Z"
DESCRIPTION DESCRIPTION
"Translation of RFC 1493 to SMIv2." "Translation of RFC 1493 to SMIv2."
REVISION "199307310000Z" REVISION "199307310000Z"
DESCRIPTION DESCRIPTION
"RFC 1493: SMIv1 version." "RFC 1493: SMIv1 version."
::= { dot1dBridge 8 } ::= { dot1dBridge 8 }
dot1dNotification OBJECT IDENTIFIER ::= { dot1dBridge 0 } dot1dNotification OBJECT IDENTIFIER ::= { dot1dBridge 0 }
-- ---------------------------------------------------------- -- -- ---------------------------------------------------------- --
skipping to change at page 34, line 34 skipping to change at page 35, line 11
the original Bridge Working Group in [RFC1493]. the original Bridge Working Group in [RFC1493].
This document was produced on behalf of the Bridge MIB Working Group This document was produced on behalf of the Bridge MIB Working Group
in the Operations and Management area of the Internet Engineering in the Operations and Management area of the Internet Engineering
Task Force. Task Force.
The authors wish to thank the members of the Bridge MIB Working Group The authors wish to thank the members of the Bridge MIB Working Group
, especially Mike MacFadden and Bert Visscher for their many comments , especially Mike MacFadden and Bert Visscher for their many comments
and suggestions which improved this effort. and suggestions which improved this effort.
6. References 6. Normative References
Normative References
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network "Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April for Describing SNMP Management Frameworks", RFC 2571, April
1999. 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
skipping to change at page 35, line 28 skipping to change at page 36, line 5
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[IEEE8021D] ANSI/IEEE Standard 802.1D-1998 MAC Bridges, IEEE Project 802 [IEEE8021D] ANSI/IEEE Standard 802.1D-1998 MAC Bridges, IEEE Project 802
Local and Metropolitan Area Networks, (March 8, 1998). Local and Metropolitan Area Networks, (March 8, 1998).
[ISO8021D] ISO DIS 10038 MAC Bridges. [ISO8021D] ISO DIS 10038 MAC Bridges.
Informative References 7. Informative References
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD of Management Information for TCP/IP-based Internets", STD
16, RFC 1155, May 1990. 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990. Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
16, RFC 1212, March 1991. 16, RFC 1212, March 1991.
skipping to change at page 36, line 7 skipping to change at page 36, line 37
[RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Management Information Base for Version 2 of the Simple "Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1907, January Network Management Protocol (SNMPv2)", RFC 1907, January
1996. 1996.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network "Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999. Management Framework", RFC 2570, April 1999.
7. Changes from RFC 1493 8. Changes from RFC 1493
The following changes have been made from RFC 1493. The following changes have been made from RFC 1493.
(1) Translated the MIB definition to use SMIv2. (1) Translated the MIB definition to use SMIv2.
(2) Updated the SNMP Framework and references to comply with the (2) Updated the SNMP Framework and references to comply with the
current IETF guidelines. current IETF guidelines.
(3) Updated the Security section to comply with current IETF (3) Updated the Security section to comply with current IETF
guidelines. guidelines.
skipping to change at page 36, line 47 skipping to change at page 37, line 23
draft-ietf-bridge-bridgemib-smiv2-02.txt draft-ietf-bridge-bridgemib-smiv2-02.txt
(1) Updated references of IEEE 802.1d draft from (1) Updated references of IEEE 802.1d draft from
1990 document to 1998 document. 1990 document to 1998 document.
The following chnages have been made from The following chnages have been made from
draft-ietf-bridge-bridgemib-smiv2-03.txt draft-ietf-bridge-bridgemib-smiv2-03.txt
(1) Adapted the current conformance statement. (1) Adapted the current conformance statement.
8. Authors' Addresses 9. Authors' Addresses
K.C. Norseth K.C. Norseth
L-3 Communications L-3 Communications
640 N. 2200 West. 640 N. 2200 West.
Salt Lake City, Utah 84116-0850 Salt Lake City, Utah 84116-0850
Email: kenyon.c.norseth@L-3com.com Email: kenyon.c.norseth@L-3com.com
kcn@norseth.com kcn@norseth.com
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
Phone: +44 1442 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
skipping to change at page 37, line 14 skipping to change at page 37, line 42
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
3Com Centre, Boundary Way 3Com Centre, Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
Phone: +44 1442 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
9. Full Copyright 10. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents
1. The SNMP Management Framework 2
2. Overview 3
2.1. Structure of MIB 3
2.1.1. The dot1dBase Group 5
2.1.2. The dot1dStp Group 5
2.1.3. The dot1dSr Group 5
2.1.4. The dot1dTp Group 6
2.1.5. The dot1dStatic Group 6
2.2. Relationship to Other MIBs 6
2.2.1. Relationship to the 'system' group 6
2.2.2. Relationship to the 'interfaces' group 6
2.3. Textual Conventions 7
3. Definitions 7
4. Security Considerations 33
5. Acknowledgments 34
6. References 34
7. Changes from RFC 1493 36
8. Authors' Addresses 36
9. Full Copyright 37
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/