| < draft-ietf-trill-rbridge-mib-08.txt | draft-ietf-trill-rbridge-mib-09.txt > | |||
|---|---|---|---|---|
| TRILL Working Group A. Rijhsinghani | TRILL Working Group A. Rijhsinghani | |||
| Internet-Draft Hewlett-Packard | Internet-Draft Hewlett-Packard | |||
| Intended status: Proposed Standard K. Zebrose | Intended status: Proposed Standard K. Zebrose | |||
| Expires: March 4, 2013 H.W. Embedded | Expires: April 5, 2013 H.W. Embedded | |||
| August 31, 2012 | October 2, 2012 | |||
| Definitions of Managed Objects for RBridges (Routing Bridges) | Definitions of Managed Objects for RBridges (Routing Bridges) | |||
| draft-ietf-trill-rbridge-mib-08.txt | draft-ietf-trill-rbridge-mib-09.txt | |||
| Status of This Document | Status of This Document | |||
| This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| This document is intended to become a Proposed Standard. Distribution | This document is intended to become a Proposed Standard. Distribution | |||
| of this document is unlimited. Comments should be sent to the author. | of this document is unlimited. Comments should be sent to the author. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| skipping to change at page 8, line 14 | skipping to change at page 8, line 14 | |||
| Note also that when more than one instance of the IS-IS protocol is | Note also that when more than one instance of the IS-IS protocol is | |||
| running on a device, as in the case of a device performing both | running on a device, as in the case of a device performing both | |||
| RBridge and IS-IS IP router functions, multiple instances of the | RBridge and IS-IS IP router functions, multiple instances of the | |||
| ISIS-MIB module can be distinguished by the use of SNMPv3 contexts or | ISIS-MIB module can be distinguished by the use of SNMPv3 contexts or | |||
| SNMPv1 communities. | SNMPv1 communities. | |||
| 6.8 MIB modules required for IMPORTS | 6.8 MIB modules required for IMPORTS | |||
| The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], | The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], | |||
| SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863] and | SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], | |||
| INET-ADDRESS-MIB[RFC4001]. | INET-ADDRESS-MIB[RFC4001], BRIDGE-MIB[RFC4188] and | |||
| Q-BRIDGE-MIB[RFC4363]. | ||||
| 7. Definition of the RBridge MIB module | 7. Definition of the RBridge MIB module | |||
| RBRIDGE-MIB DEFINITIONS ::= BEGIN | RBRIDGE-MIB DEFINITIONS ::= BEGIN | |||
| -- ---------------------------------------------------------- -- | -- ---------------------------------------------------------- -- | |||
| -- MIB for RBRIDGE devices, also known as TRILL Switches | -- MIB for RBRIDGE devices, also known as TRILL Switches | |||
| -- ---------------------------------------------------------- -- | -- ---------------------------------------------------------- -- | |||
| IMPORTS | IMPORTS | |||
| MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, | MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, | |||
| skipping to change at page 8, line 51 | skipping to change at page 9, line 4 | |||
| rbridgeMIB MODULE-IDENTITY | rbridgeMIB MODULE-IDENTITY | |||
| LAST-UPDATED "201201250000Z" | LAST-UPDATED "201201250000Z" | |||
| ORGANIZATION "IETF TRILL Working Group" | ORGANIZATION "IETF TRILL Working Group" | |||
| CONTACT-INFO | CONTACT-INFO | |||
| "http://www.ietf.org/dyn/wg/charter/trill-charter.html | "http://www.ietf.org/dyn/wg/charter/trill-charter.html | |||
| Email: rbridge@postel.org | Email: rbridge@postel.org | |||
| Anil Rijhsinghani | Anil Rijhsinghani | |||
| Hewlett-Packard | Hewlett-Packard | |||
| Tel: +1 508 323 1251 | ||||
| Tel: +1 508 323 1251 | ||||
| Email: anil@charter.net | Email: anil@charter.net | |||
| Kate Zebrose | Kate Zebrose | |||
| H.W. Embedded | H.W. Embedded | |||
| Tel: +1 617 840 9673 | Tel: +1 617 840 9673 | |||
| Email: kate.zebrose@alum.mit.edu" | Email: kate.zebrose@alum.mit.edu" | |||
| DESCRIPTION | DESCRIPTION | |||
| "The RBridge MIB module for managing switches that support | "The RBridge MIB module for managing switches that support | |||
| the TRILL protocol." | the TRILL protocol." | |||
| REVISION "201201250000Z" | REVISION "201210020000Z" | |||
| DESCRIPTION | DESCRIPTION | |||
| "Initial version, published as RFC yyyy" | "Initial version, published as RFC yyyy" | |||
| -- RFC Ed.: replace yyyy with actual RFC number & remove this note | -- RFC Ed.: replace yyyy with actual RFC number & remove this note | |||
| ::= { mib-2 xxx } | ::= { mib-2 xxx } | |||
| -- RFC Ed.: replace xxx with IANA-assigned number & remove this note | -- RFC Ed.: replace xxx with IANA-assigned number & remove this note | |||
| -- ---------------------------------------------------------- -- | -- ---------------------------------------------------------- -- | |||
| -- subtrees in the RBridge MIB | -- subtrees in the RBridge MIB | |||
| -- ---------------------------------------------------------- -- | -- ---------------------------------------------------------- -- | |||
| skipping to change at page 50, line 29 | skipping to change at page 50, line 29 | |||
| Editor's Note (to be removed prior to publication): the IANA is | Editor's Note (to be removed prior to publication): the IANA is | |||
| requested to assign a value for "xxx" under the 'mib-2' subtree and | requested to assign a value for "xxx" under the 'mib-2' subtree and | |||
| to record the assignment in the SMI Numbers registry. When the | to record the assignment in the SMI Numbers registry. When the | |||
| assignment has been made, the RFC Editor is asked to replace "XXX" | assignment has been made, the RFC Editor is asked to replace "XXX" | |||
| (here and in the MIB module) with the assigned value and to remove | (here and in the MIB module) with the assigned value and to remove | |||
| this note. | this note. | |||
| 10. Contributors | 10. Contributors | |||
| The authors would like to acknowledge the contributions of Donald | The authors would like to acknowledge the contributions of Donald | |||
| Eastlake, Radia Perlman, Anoop Ghanwani, Dan Romascanu, Mahesh Akula | Eastlake, Radia Perlman, Anoop Ghanwani, Dan Romascanu, Mahesh Akula, | |||
| and Joan Cucchiara. | Sue Hares and Joan Cucchiara. | |||
| 11. References | 11. References | |||
| 11.1 Normative References | 11.1 Normative References | |||
| [RFC6325] Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. | [RFC6325] Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. | |||
| Ghanwani, "Routing Bridges (RBridges): Base Protocol | Ghanwani, "Routing Bridges (RBridges): Base Protocol | |||
| Specification", RFC 6325, July 2011. | Specification", RFC 6325, July 2011. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| End of changes. 7 change blocks. | ||||
| 9 lines changed or deleted | 10 lines changed or added | |||
This html diff was produced by rfcdiff 1.39p1. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||