Internet Engineering Task Force (IETF)                   A. Rijhsinghani
Request for Comments: 6850                               Hewlett-Packard
Category: Standards Track                                     K. Zebrose
ISSN: 2070-1721                                              HW Embedded
                                                            January 2013


     Definitions of Managed Objects for Routing Bridges (RBridges)

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols.  In particular, it defines
   objects for managing a Routing Bridge (RBridge), also known as a
   TRILL Switch, based on the IETF TRILL (Transparent Interconnection of
   Lots of Links) protocol.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6850.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................2
   2. The Internet-Standard Management Framework ......................3
   3. Overview ........................................................3
   4. Conventions .....................................................4
   5. Structure of the MIB Module .....................................4
      5.1. Textual Conventions ........................................4
      5.2. The rbridgeBase Subtree ....................................4
      5.3. The rbridgeFdb Subtree .....................................4
      5.4. The rbridgeVlan Subtree ....................................4
      5.5. The rbridgeEsadi Subtree ...................................4
      5.6. The rbridgeCounters Subtree ................................4
      5.7. The rbridgeSnooping Subtree ................................5
      5.8. The rbridgeDtree Subtree ...................................5
      5.9. The rbridgeTrill Subtree ...................................5
      5.10. The Notifications Subtree .................................5
   6. Relationship to Other MIB Modules ...............................5
      6.1. Relationship to IF-MIB .....................................5
      6.2. Relationship to BRIDGE-MIB .................................6
      6.3. Relationship to P-BRIDGE-MIB ...............................6
      6.4. Relationship to Q-BRIDGE-MIB ...............................6
      6.5. Relationship to IEEE8021-BRIDGE-MIB ........................7
      6.6. Relationship to IEEE8021-Q-BRIDGE-MIB ......................7
      6.7. Relationship to ISIS-MIB ...................................8
      6.8. MIB Modules Required for IMPORTS ...........................8
   7. Definition of the RBridge MIB Module ............................9
   8. Security Considerations ........................................55
   9. IANA Considerations ............................................56
   10. Contributors ..................................................56
   11. References ....................................................57
      11.1. Normative References .....................................57
      11.2. Informative References ...................................58

1.  Introduction

   This document describes a model for managing Routing Bridges
   (RBridges), also known as TRILL Switches, as defined in [RFC6325].
   RBridges provide optimal pair-wise forwarding without configuration
   using IS-IS routing and encapsulation of traffic.  RBridges are
   compatible with previous IEEE 802.1 customer bridges as well as IPv4
   and IPv6 routers and end nodes.  They are as invisible to current IP
   routers as bridges are and, like routers, they terminate the bridge
   spanning tree protocol.  In creating an RBridge management model, the
   device is viewed primarily as a customer bridge.  For a discussion of
   the problem addressed by TRILL (Transparent Interconnection of Lots
   of Links), see [RFC5556].

   RBridges support features specified for transparent bridges in
   IEEE 802.1, and the corresponding MIB modules are used to manage
   those features.  For IS-IS purposes, the corresponding MIB module is
   used to manage the protocol.  This MIB module specifies those objects
   that are TRILL-specific and hence not available in other MIB modules.

2.  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].

3.  Overview

   The RBridge MIB module is intended as an overall framework for
   managing RBridges, also known as TRILL Switches.  Where possible, the
   MIB references existing MIB definitions in order to maximize reuse.
   This results in a considerable emphasis on the relationship with
   other MIB modules.

   Starting with the physical interfaces, there are requirements for
   certain elements of the IF-MIB to be implemented.  These elements are
   required in order to connect the per-port parameters to higher-level
   functions of the physical device.

   Transparent bridging, VLANs, traffic classes, and multicast filtering
   are supported by the TRILL protocol, and the corresponding management
   is expected to conform to the BRIDGE-MIB module [RFC4188] and to the
   P-BRIDGE-MIB and Q-BRIDGE-MIB modules [RFC4363].

   The IS-IS routing protocol is used in order to determine the optimum
   pair-wise forwarding path.  This protocol is managed using the IS-IS
   MIB module defined in [RFC4444].  Since the TRILL protocol specifies
   the use of a single level and a fixed area address of zero, some
   IS-IS MIB objects are not applicable.  Some IS-IS MIB objects are
   used in the TRILL protocol.

4.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   RFC 2119 [RFC2119].

5.  Structure of the MIB Module

   Objects in this MIB module are arranged into subtrees.  Each subtree
   is organized as a set of related objects.  The various subtrees are
   shown below.  These are supplemented with required elements of the
   IF-MIB, ISIS-MIB, BRIDGE-MIB, P-BRIDGE-MIB, Q-BRIDGE-MIB, and IEEE
   Bridge MIB modules.

5.1.  Textual Conventions

   Textual conventions are defined to represent object types relevant to
   TRILL.

5.2.  The rbridgeBase Subtree

   This subtree contains system- and port-specific objects applicable to
   all RBridges.

5.3.  The rbridgeFdb Subtree

   This subtree contains objects applicable to the forwarding database
   used by the RBridge in making packet-forwarding decisions.  Because
   it contains additional information used by the TRILL protocol not
   applicable to 802.1D/Q bridges, it is a superset of the corresponding
   subtrees defined in the BRIDGE-MIB and Q-BRIDGE-MIB.

5.4.  The rbridgeVlan Subtree

   This subtree describes objects applicable to VLANs configured on the
   RBridge.

5.5.  The rbridgeEsadi Subtree

   This subtree describes objects relevant to RBridges that support the
   optional End-Station Address Distribution Information (ESADI)
   protocol.

5.6.  The rbridgeCounters Subtree

   This subtree contains statistics maintained by RBridges that can aid
   in monitoring and troubleshooting networks connected by them.

5.7.  The rbridgeSnooping Subtree

   This subtree describes objects applicable to RBridges capable of
   snooping IPv4 and/or IPv6 multicast control frames and pruning IP
   multicast traffic based on detection of IP multicast routers and
   listeners.

5.8.  The rbridgeDtree Subtree

   This subtree contains objects relevant to distribution trees computed
   by RBridges for the forwarding of multi-destination frames.

5.9.  The rbridgeTrill Subtree

   This subtree contains objects applicable to the TRILL IS-IS protocol,
   beyond what is available in the ISIS-MIB.

5.10.  The Notifications Subtree

   The defined notifications are focused on the TRILL protocol
   functionality.  Notifications are defined for changes in the
   Designated RBridge status and the topology.

6.  Relationship to Other MIB Modules

   The IF-MIB, BRIDGE-MIB, P-BRIDGE-MIB, Q-BRIDGE-MIB,
   IEEE8021-BRIDGE-MIB, IEEE8021-Q-BRIDGE-MIB, and ISIS-MIB modules all
   contain objects relevant to the RBridge MIB.  Management objects
   contained in these modules are not duplicated here, to reduce overlap
   to the extent possible.

   The Bridge MIB modules were originally written in the IETF and
   implemented by many vendors.  Per [RFC4663], this has recently been
   transferred to the IEEE 802.1 working group.  As vendors may have
   implemented either the IETF or IEEE Bridge MIB modules, this RBridge
   MIB module is designed to work with either one.

6.1.  Relationship to IF-MIB

   The port identification elements MUST be implemented in order to
   allow them to be cross-referenced.  The Interfaces MIB [RFC2863]
   requires that any MIB module that is an adjunct of the Interfaces MIB
   clarify specific areas within the Interfaces MIB module.  These areas
   were intentionally left vague in the Interfaces MIB module to avoid
   over-constraining the MIB, thereby precluding management of certain
   media types.  Section 4 of [RFC2863] enumerates several areas that a

   media-specific MIB module must clarify.  The implementor is referred
   to [RFC2863] in order to understand the general intent of these
   areas.

6.2.  Relationship to BRIDGE-MIB

   The following subtrees in the BRIDGE-MIB [RFC4188] contain
   information relevant to RBridges when the corresponding functionality
   is implemented.

   o  dot1dBase

   o  dot1dTp

   o  dot1dStatic

6.3.  Relationship to P-BRIDGE-MIB

   The following subtrees in the P-BRIDGE-MIB [RFC4363] contain
   information relevant to RBridges when the corresponding functionality
   is implemented.

   o  dot1dExtBase

   o  dot1dPriority

   o  dot1dGarp

   o  dot1dGmrp

   o  dot1dTpHCPortTable

   o  dot1dTpPortOverflowTable

6.4.  Relationship to Q-BRIDGE-MIB

   The following groups in the Q-BRIDGE-MIB [RFC4363] contain
   information relevant to RBridges when the corresponding functionality
   is implemented.  This functionality is also contained in the
   IEEE8021-Q-BRIDGE-MIB.

   o  dot1qBase

   o  dot1qTp

   o  dot1qStatic

   o  dot1qVlan

   o  dot1vProtocol

6.5.  Relationship to IEEE8021-BRIDGE-MIB

   The following subtrees in the IEEE8021-BRIDGE-MIB contain information
   relevant to RBridges when the corresponding functionality is
   implemented.

   o  ieee8021BridgeBase

   o  ieee8021BridgeTp

   o  ieee8021BridgePriority

   o  ieee8021BridgeMrp

   o  ieee8021BridgeMmrp

   o  ieee8021BridgeInternalLan

   o  ieee8021BridgeDot1d

6.6.  Relationship to IEEE8021-Q-BRIDGE-MIB

   The following subtrees in the IEEE8021-Q-BRIDGE-MIB contain
   information relevant to RBridges when the corresponding functionality
   is implemented.

   o  ieee8021QBridgeBase

   o  ieee8021QBridgeTp

   o  ieee8021QBridgeStatic

   o  ieee8021QBridgeVlan

   o  ieee8021QBridgeProtocol

6.7.  Relationship to ISIS-MIB

   "Management Information Base for Intermediate System to Intermediate
   System (IS-IS)" [RFC4444] defines a MIB module for the IS-IS routing
   protocol when it is used to construct routing tables for IP networks.
   While most of these objects are applicable to the TRILL layer 2
   implementation, note the IS-IS constraints for the current version of
   TRILL [RFC6325]:

   o  The TRILL IS-IS instance uses a single Level 1 IS-IS area.

   o  The TRILL Level 1 IS-IS area uses the fixed area address zero.

   o  The TRILL IS-IS instance is not used for IP address advertisement.

   o  The TRILL IS-IS instance is used for only a single protocol:
      TRILL.

   Accordingly, tables that report IP address reachability and tables
   that allow configuration or reporting of multiple IS-IS areas,
   multiple IS-IS levels, or multiple protocols will be empty in the
   ISIS-MIB module for the current version of TRILL.

   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
   RBridge and IS-IS IP router functions, multiple instances of the
   ISIS-MIB module can be distinguished by the use of SNMPv3 contexts or
   SNMPv1 communities.

6.8.  MIB Modules Required for IMPORTS

   The following MIB module imports objects from the SNMPv2-SMI
   [RFC2578], SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], IF-MIB
   [RFC2863], INET-ADDRESS-MIB [RFC4001], BRIDGE-MIB [RFC4188],
   and Q-BRIDGE-MIB [RFC4363].  (The IEEE Bridge MIB modules import
   similar TCs.)