datatracker.ietf.org
Sign in
Version 5.13.0, 2015-03-25
Report a bug

Definitions of Managed Objects for Bridges with Rapid Spanning Tree Protocol
RFC 4318

Document type: RFC - Proposed Standard (December 2005; No errata)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4318 (Proposed Standard)
Responsible AD: Bert Wijnen
Send notices to: dromasca@avaya.com, dbharrington@comcast.net; dlevi@nortel.com

Network Working Group                                            D. Levi
Request for Comments: 4318                               Nortel Networks
Category: Standards Track                                  D. Harrington
                                                      Effective Software
                                                           December 2005

               Definitions of Managed Objects for Bridges
                   with Rapid Spanning Tree Protocol

Status of This Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This memo defines an SMIv2 MIB module for managing the Rapid Spanning
   Tree capability defined by the IEEE P802.1t and P802.1w amendments to
   IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN)
   segments.  The objects in this MIB are defined to apply both to
   transparent bridging and to bridges connected by subnetworks other
   than LAN segments.

Table of Contents

   1. The Internet-Standard Management Framework ......................2
   2. Overview ........................................................2
   3. Relationship to IEEE 802.1t and 802.1w Amendments ...............2
   4. Relation to the BRIDGE-MIB ......................................3
   5. Definitions for RSTP-MIB ........................................3
   6. Acknowledgements ...............................................10
   7. IANA Considerations ............................................10
   8. Security Considerations ........................................10
   9. Normative References ...........................................11
   10. Informative References ........................................12

Levi & Harrington           Standards Track                     [Page 1]
RFC 4318                        RSTP MIB                   December 2005

1.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

2.  Overview

   This memo defines an SMIv2 MIB module for managing the Rapid Spanning
   Tree (RSTP) capability defined by the IEEE P802.1t [802.1t] and
   P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 [802.1D-1998] for
   bridging between Local Area Network (LAN) segments.  The objects in
   this MIB are defined to apply both to transparent bridging and to
   bridges connected by subnetworks other than LAN segments.

3.  Relationship to IEEE 802.1t and 802.1w Amendments

   This document defines managed objects for the Rapid Spanning Tree
   Protocol defined by the IEEE P802.1t and IEEE P802.1w amendments to
   802.1D-1998.

   RSTP-MIB Name                       IEEE 802.1 Reference

   dot1dStp
     dot1dStpVersion                   (w) 17.16.1  ForceVersion
     dot1dStpTxHoldCount               (w) 17.16.6  TxHoldCount
     dot1dStpExtPortTable
       dot1dStpPortProtocolMigration   (w) 17.18.10 mcheck
       dot1dStpPortAdminEdgePort       (t) 18.3.3   adminEdgePort
       dot1dStpPortOperEdgePort        (t) 18.3.4   operEdgePort
       dot1dStpPortAdminPointToPoint   (w) 6.4.3    adminPointToPointMAC
       dot1dStpPortOperPointToPoint    (w) 6.4.3    operPointToPointMAC
       dot1dStpPortAdminPathCost       (D) 8.5.5.3  Path Cost

   There are concerns that there may be changes made in the 802.1D-2004
   edition that would lead to non-backward-compatible SMI changes for
   802.1t and 802.1w managed objects in the MIB modules.  The Bridge MIB
   working group decided to 'freeze' the technical content of the MIB
   modules at a level that is compatible with the 802.1t and 802.1w

Levi & Harrington           Standards Track                     [Page 2]
RFC 4318                        RSTP MIB                   December 2005

[include full document text]