RFC 3811 (rfc3811) - Page 2 of 20
Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management
Alternative Format: Original Text Document
RFC 3811 MPLS TC MIB June 2004 1. Introduction This document defines a MIB module which contains Textual Conventions for Multiprotocol Label Switching (MPLS) networks. These Textual Conventions should be imported by MIB modules which manage MPLS networks. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC 2119]. For an introduction to the concepts of MPLS, see [RFC 3031]. 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 [RFC 3410]. 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 [RFC 2578], STD 58, RFC 2579 [RFC 2579] and STD 58, RFC 2580 [RFC 2580]. 3. MPLS Textual Conventions MIB Definitions MPLS-TC-STD-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, Unsigned32, Integer32, transmission FROM SNMPv2-SMI -- [RFC 2578] TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC 2579] mplsTCStdMIB MODULE-IDENTITY LAST-UPDATED "200406030000Z" -- June 3, 2004 ORGANIZATION "IETF Multiprotocol Label Switching (MPLS) Working Group." CONTACT-INFO " Thomas D. Nadeau Nadeau & Cucchiara Standards Track



