INTERNET-DRAFT Masanori Miyazawa Intended status: Standard Truck Tomohiro Otani Expires: Jan 31, 2009 KDDI R&D Labs Thomas Nadeau BT Kenji Kumaki KDDI R&D Labs July 13, 2008 Traffic Engineering Database Management Information Base in support of MPLS-TE/GMPLS Document: draft-ietf-ccamp-gmpls-ted-mib-04.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working 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 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 http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This memo defines the Management Information Base (MIB) objects in order to manage traffic engineering database (TED) information with extension in support of Multi-Protocol Label Switching (MPLS) with traffic engineering (TE) as well as Generalized MPLS (GMPLS) for use with network management protocols. Table of Contents Status of this Memo................................................... 1 Abstract.............................................................. 1 1. The Internet-Standard Management Framework......................... 3 2. Introduction....................................................... 3 3. Overview........................................................... 3 T. Otani et al. Expires Jan. 2009 [Page 1] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 3.1 Conventions used in this document................................. 3 3.2 Terminology....................................................... 3 3.3 Acronyms.......................................................... 3 4. Motivations........................................................ 4 5. Brief description of MIB Objects................................... 4 5.1 tedTable.......................................................... 4 5.2 teLocalIntIpAddrTable............................................. 4 5.3 teRemoteIntIpAddrTable............................................ 4 5.4 teSwCapTable...................................................... 5 5.5 teSrlgTable....................................................... 5 6.Example of the TED MIB module usage ................................ 5 7. TED MIB Definitions in support of GMPLS............................ 6 8. Security consideration............................................ 22 9. IANA Considerations............................................... 23 9.1 IANA Considerations for TED-MIB.................................. 23 10. References....................................................... 23 10.1 Normative References............................................ 23 11. Acknowledgment................................................... 25 12. Author's Address................................................. 25 13. Intellectual Property Statement.................................. 25 Copyright Statement.................................................. 26 T. Otani et al. Expires Jan. 2009 [Page 2] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 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. Introduction The OSPF MIB is defined as [RFC4750] and the ISIS MIB as [RFC4444]. On the other side, MPLS/GMPLS based traffic engineering has so far extended OSPF/ISIS routing protocol with TE functionality [RFC4202], [RFC3630], [RFC4205], [RFC3784]. To manage such MPLS-TE/GMPLS networks effectively, routing information associated with MPLS/GMPLS TE parameters (TED) is preferred for the network management, however, there is no clear definition of MPLS/GMPLS TE information in existing MIBs related with OSPF/ISIS. This memo defines the Management Information Base (MIB) objects for managing TED in support of MPLS-TE/GMPLS for use with network management protocols. This MIB module should be used in conjunction with OSPF/ISIS MIB as well as other MIBs defined in [RFC3812], [RFC3813], [RFC4802], [RFC4803] for the management of MPLS/GMPLS based traffic engineering information. 3. Overview 3.1 Conventions used in this document 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 [RFC2119]. 3.2 Terminology Definitions of key terms for MPLS OAM and GMPLS are found in [RFC4377, RFC3945] and the reader is assumed to be familiar with those definitions which are not repeated here. 3.3 Acronyms GMPLS: Generalized Multi-Protocol Label Switching T. Otani et al. Expires Jan. 2009 [Page 3] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 LDP: Label Distribution Protocol LSP: Label Switching Path LSR: Label Switching Router MIB: Management Information Base OAM: Operations and Management OA&M: Operations, Administration and Maintenance. OSPF: Open Shortest Path First RSVP: Resource reSerVation Protocol TE: Traffic Engineering PSC: Packet switch capable LSC: Lambda switch capable FSC: Fiber switch capable TDM: Time Division Multiplexing SRLG: Shared risk link group LSA: Link state advertisement 4. Motivations The existing OSPF, MPLS and GMPLS MIBs do not provide for the management of all of the extensions to the OSPF protocol. To manage MPLS/GMPLS TE attributes, MIB objects to indicate such MPLS/GMPLS TED is significant. 5. Brief description of MIB Objects The objects described in this section support the management of TED described in [RFC4202], [RFC4203] and [RFC4205] for GMPLS extensions as well as in [RFC3630] and [RFC3784] for MPLS/GMPLS. 5.1 tedTable The tedTable is basically used to indicate TED information of OSPF-TE or ISIS-TE. However, this table does not contain the information of Local/Remote interface IP address, Interface Switching Capability Descriptor and Shared Risk Link Group information within the sub-TLVs for the Link-TLV. 5.2 teLocalIntIpAddrTable The teLocalIntIpAddrTable is identical to the Local interface IP address information in a sub-TLV for the Link-TLV. This is independently defined, because the Interface IP Address sub-TLV may appear more than once within the same Link-TLV. 5.3 teRemoteIntIpAddrTable The teRemoteIntIpAddrTable is identical to the Remote interface IP address information in a sub-TLV of the Link-TLV. This is also independently utilized, because one or more local interface IP address sub TLVs may exist in the same Link-TLV. T. Otani et al. Expires Jan. 2009 [Page 4] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 5.4 teSwCapTable The teSwCapTable represents Interface Switching Capability Descriptor information. This is independently defined due to the possibility of multiple appearances of the sub TLV within the same Link-TLV. 5.5 teSrlgTable The teSrlgTable contains the Sub-TLV information of Shared Risk Link Group (SRLG) information. This is separately defined, because more than one sub TLVs may appear in the same Link-TLV. 6.Example of the TED MIB module usage In this section, we provide an example of the TED MIB module usage. The following indicates the information of a numbered TE link originated in a GMPLS controlled node. When TE link information is retrieved in a MPLS network, GMPLS specific objects such as teLocalIntAddrTable, teRemoteIntAddrTable, teSwCapTable and teSrlgTable are not supported. Note that the TE MIB modules are only limited to "read-only" access except for tedNotificationEnabled and tedNotificationMaxRate. The TED MIB is designed to be independent of OSPF or ISIS MIBs, however each TE information is belonging to a node or a link, which is managed by the routing protocol. Therefore it should not be locally changed without triggering from the routing protocol. In tedTable: { teAreaId.0.842150510.167772640 0 teRouterId.0.842150510.16777264 1848783410 teLinkStateId.0.842150510.16777264 805306369 teLinkInformationSource.0.842150510.16777264 ospf(2) teLinkInformationData.0.842150510.16777264 zeroDotZero teLinkType.0.842150510.16777264 pointToPoint(1) teRouterIdAddr.0.842150510.16777264 50.50.50.110 teRouterIdAddr.0.842150530.16777296 50.50.50.130 teLinkIdAddr.0.842150510.16777264 50.50.50.120 teMetric.0.842150510.167772641 teMaxBandwidth.0.842150510.16777264 1376193201 teMaxReservableBandwidth.0.842150510.167772641376193201 teUnreservedBandwidthPri0.0.842150510.16777264 1375888025 teUnreservedBandwidthPri1.0.842150510.16777264 1375888025 teUnreservedBandwidthPri2.0.842150510.16777264 1375888025 teUnreservedBandwidthPri3.0.842150510.16777264 1375888025 teUnreservedBandwidthPri4.0.842150510.16777264 1375888025 teUnreservedBandwidthPri5.0.842150510.16777264 1375888025 teUnreservedBandwidthPri6.0.842150510.16777264 1375888025 teUnreservedBandwidthPri7.0.842150510.16777264 1375888025 teAdministrativeGroup.0.842150510.16777264 0 teLocalId.0.842150510.16777264 0 teRemoteId.0.842150510.16777264 0 T. Otani et al. Expires Jan. 2009 [Page 5] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 teLinkProtectionType.0.842150510.16777264 01 00 00 00 7 In teLocalIntAddrTable: { teLocalIntAddr.0.842150510.16777264.010.10.10.1 } In teRemoteIntAddrTable: { teRemoteIntAddr.0.842150510.16777264.0 10.10.10.2 } In teSwCapTable: { teSwitchingType.0.842150510.16777264.1 lsc(150) teEncoding.0.842150510.16777264.1 ethernet(2) teMaxLspBandwidthPri0.0.842150510.16777264.1 1375888025 teMaxLspBandwidthPri1.0.842150510.16777264.1 1375888025 teMaxLspBandwidthPri2.0.842150510.16777264.1 1375888025 teMaxLspBandwidthPri3.0.842150510.16777264.1 1375888025 teMaxLspBandwidthPri4.0.842150510.16777264.1 1375888025 teMaxLspBandwidthPri5.0.842150510.16777264.1 1375888025 teMaxLspBandwidthPri6.0.842150510.16777264.1 1375888025 teMaxLspBandwidthPri7.0.842150510.16777264.1 1375888025s teMinLspBandwidth.0.842150510.16777264.1 0 teIntMtu.0.842150510.16777264.1 0 teIndication.0.842150510.16777264.1 standard(0) } In teSrlgTable: { teSrlg.0.842150510.16777264.00 } 7. TED MIB Definitions in support of GMPLS TED-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission, IpAddress, NOTIFICATION-TYPE FROM SNMPv2-SMI -- RFC2578 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC2580 RowPointer, TruthValue FROM SNMPv2-TC -- RFC2579 IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC FROM IANA-GMPLS-TC-MIB -- RFC4801 ; tedMIB MODULE-IDENTITY LAST-UPDATED "200807030000Z" -- 03 July 2008 00:00:00 GMT ORGANIZATION "IETF CCAMP Working Group." CONTACT-INFO T. Otani et al. Expires Jan. 2009 [Page 6] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 " Tomohiro Otani otani@kddilabs.jp Masanori Miyazawa ma-miyazawa@kddilabs.jp Thomas D. Nadeau tnadeau@bt.com Kenji Kumaki ke-kumaki@kddilabs.jp Comments and discussion to ccamp@ietf.org" DESCRIPTION "This MIB contains managed object definitions for TED in support of MPLS/GMPLS TE Database. Copyright (C) The IETF Trust (2008). This version of this MIB module is part of RFCXXX; see the RFC itself for full legal notices." -- Revision history. REVISION "200807030000Z" -- 04 July 2008 00:00:00 GMT DESCRIPTION "Initial version. Published as RFC xxxx." -- RFC-editor pls fill in xxx ::= { transmission xxx } -- assigned by IANA, see section 8.1 for details -- Textual Conventions. -- Top level components of this MIB. tedNotifications OBJECT IDENTIFIER ::= { tedMIB 0 } tedObjects OBJECT IDENTIFIER ::= { tedMIB 1 } tedScalars OBJECT IDENTIFIER ::= { tedObjects 1 } tedTables OBJECT IDENTIFIER ::= { tedObjects 2 } tedConformance OBJECT IDENTIFIER ::= { tedMIB 2 } -- MIB Definitions -- -- Scalar Objects -- tedNotificationEnabled OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is set to true, it enables the generation of tedTeInfoStatusChange, tedTeCreation and tedTeDeletion notifications." DEFVAL {false} ::={ tedScalars 1 } T. Otani et al. Expires Jan. 2009 [Page 7] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 tedNotificationMaxRate OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "A lot of notifications are expected to generate in a node, especially when a network failure occurs and might cause a performance degradation of the node itself. To avoid such a defect, this object provides the maximum number of notifications generated per minute. If events occur more rapidly, the implementation may simply fail to emit these notifications during that period, or may queue them until an appropriate time. A value of 0 means no throttling is applied and events may be notified at the rate at which they occur." DEFVAL {0} ::= { tedScalars 2 } -- -- TE DB Table -- tedTable OBJECT-TYPE SYNTAX SEQUENCE OF TedEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table indicates multiple TED information which has been supported by [RFC3630]." ::= { tedTables 1 } tedEntry OBJECT-TYPE SYNTAX TedEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry contains TED information commonly utilized in both MPLS and GMPLS" INDEX { teAreaId, teRouterId, teLinkStateId } ::= { tedTable 1 } TedEntry ::= SEQUENCE { teAreaId Unsigned32, teRouterId Unsigned32, teLinkStateId Unsigned32, teLinkInformationSource INTEGER, teLinkInformationData RowPointer, teLinkType INTEGER, teRouterIdAddr IpAddress, teLinkIdAddr IpAddress, teMetric Integer32, teMaxBandwidth Unsigned32, teMaxReservableBandwidth Unsigned32, teUnreservedBandwidthPri0 Unsigned32, T. Otani et al. Expires Jan. 2009 [Page 8] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 teUnreservedBandwidthPri1 Unsigned32, teUnreservedBandwidthPri2 Unsigned32, teUnreservedBandwidthPri3 Unsigned32, teUnreservedBandwidthPri4 Unsigned32, teUnreservedBandwidthPri5 Unsigned32, teUnreservedBandwidthPri6 Unsigned32, teUnreservedBandwidthPri7 Unsigned32, teAdministrativeGroup Integer32, teLocalId Integer32, teRemoteId Integer32, teLinkProtectionType BITS } teAreaId OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the area identifier of the IGP. If OSPF is used to advertise LSA, this represents an ospfArea. If ISIS is used, this represents an area address. Otherwise, this represents zero." ::= { tedEntry 1 } teRouterId OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the router identifier. If OSPF is used to advertise LSA, this represents a Router ID. If ISIS is used, this represents a System ID. Otherwise, this represents zero." ::= { tedEntry 2 } teLinkStateId OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the link state identifier. If OSPF is used, this represents an ospfLsdbID. If ISIS is used, this represents an isisLSPID. Otherwise, this represents a unique identifier within a node." ::= { tedEntry 3 } teLinkInformationSource OBJECT-TYPE SYNTAX INTEGER { unknown(0), locallyConfigured(1), ospf(2), isis(3), other(4) T. Otani et al. Expires Jan. 2009 [Page 9] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the source of the information about the TE link" ::= { tedEntry 4 } teLinkInformationData OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "This object cross-references the source of the information about this TE link and should be interpretted in the context of teLinkInformationSource. If teLinkInformationSource has the value unknown(0), this object SHOULD contain a value of zeroDotZero.If teLinkInformationSource has the value locallyConfigured(1), this object MAY contain the identifier of the corresponding row entry in the teLinkTable of TE-LINK-STD-MIB, the identifier of the corresponding row in a local proprietary TE link MIB module, or the value of zeroDotZero otherwise. If teLinkInformationSource has the value ospf(2), this object MAY contain the identifier of the corresponding row entry in the ospfLocalLsdbTable of OSPF-MIB [RFC4750], or the value of zeroDotZero otherwise. If teLinkInformationSource has the value isis(3) this object MAY contain the identifier of the corresponding row entry in the isisAreaAddr of ISIS-MIB [RFC4444], or the value of zeroDotZero otherwise. If teLinkInformationSource has the value other(4) this object MAY contain the identifier of the corresponding row entry a local proprietary MIB module, or the value of zeroDotZero otherwise." ::= { tedEntry 5 } teLinkType OBJECT-TYPE SYNTAX INTEGER { pointToPoint (1), multiAccess (2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the type of the link such as point-to-point or multi-access" ::= { tedEntry 6 } teRouterIdAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION T. Otani et al. Expires Jan. 2009 [Page 10] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 "This object indicates the TE-Router ID" ::= { tedEntry 7 } teLinkIdAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the Router ID of the neighbor in the case of point-to-point links. This also indicates the interface address of the designated router in the case of multi-access links." ::= { tedEntry 8 } teMetric OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the traffic engineering metric value of the TE link." ::= { tedEntry 9 } teMaxBandwidth OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the maximum bandwidth that can be used on this link in this direction" ::= { tedEntry 10 } teMaxReservableBandwidth OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the maximum bandwidth that may be reserved on this link in this direction" ::= { tedEntry 11 } teUnreservedBandwidthPri0 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 0" ::= { tedEntry 12 } teUnreservedBandwidthPri1 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) T. Otani et al. Expires Jan. 2009 [Page 11] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 1" ::= { tedEntry 13 } teUnreservedBandwidthPri2 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 2" ::= { tedEntry 14 } teUnreservedBandwidthPri3 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 3" ::= { tedEntry 15 } teUnreservedBandwidthPri4 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 4" ::= { tedEntry 16 } teUnreservedBandwidthPri5 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 5" ::= { tedEntry 17 } teUnreservedBandwidthPri6 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION T. Otani et al. Expires Jan. 2009 [Page 12] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 "This indicates the amount of bandwidth not yet reserved at the priority 6" ::= { tedEntry 18 } teUnreservedBandwidthPri7 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 7" ::= { tedEntry 19 } teAdministrativeGroup OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the Administrative Group which the link belong to. Since the value is a bit mask, the link can belong to multiple groups. This is also called Resource Class/Color." ::= { tedEntry 20 } teLocalId OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the Link local identifier of an unnumbered link." ::= { tedEntry 21 } teRemoteId OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the Link remote identifier of an unnumbered link." ::= { tedEntry 22 } teLinkProtectionType OBJECT-TYPE SYNTAX BITS { extraTraffic(0), unprotected(1), shared (2), dedicatedOneToOne (3), dedicatedOnePlusOne(4), enhanced(5) } MAX-ACCESS read-only STATUS current DESCRIPTION T. Otani et al. Expires Jan. 2009 [Page 13] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 "This object indicates the protection type of the TE link" ::= { tedEntry 23 } -- -- TED Local Interface IP Address Table -- teLocalIntAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF TeLocalIntAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the IP address information of a local TE link." ::= { tedTables 2 } teLocalIntAddrEntry OBJECT-TYPE SYNTAX TeLocalIntAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry contains the IP address information of the local TE link." INDEX { teAreaId, teRouterId, teLinkStateId, teLocalIntAddrIndex } ::= { teLocalIntAddrTable 1 } TeLocalIntAddrEntry ::= SEQUENCE { teLocalIntAddrIndex Unsigned32, teLocalIntAddr IpAddress } teLocalIntAddrIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This indicates the index to identify multiple local TE links" ::= { teLocalIntAddrEntry 1 } teLocalIntAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the address of the local TE link." ::= { teLocalIntAddrEntry 2 } -- -- TED Remote Interface IP Address Table -- T. Otani et al. Expires Jan. 2009 [Page 14] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 teRemoteIntAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF TeRemoteIntAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the IP address information of a remote TE link." ::= { tedTables 3 } teRemoteIntAddrEntry OBJECT-TYPE SYNTAX TeRemoteIntAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry contains the IP address information of the remote TE link." INDEX { teAreaId, teRouterId, teLinkStateId, teRemoteIntAddrIndex } ::= { teRemoteIntAddrTable 1 } TeRemoteIntAddrEntry ::= SEQUENCE { teRemoteIntAddrIndex Unsigned32, teRemoteIntAddr IpAddress } teRemoteIntAddrIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This indicates the index to identify multiple remote TE links." ::= { teRemoteIntAddrEntry 1 } teRemoteIntAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the address of the remote TE link." ::= { teRemoteIntAddrEntry 2 } -- -- TED Switch Capable Table -- teSwCapTable OBJECT-TYPE SYNTAX SEQUENCE OF TeSwCapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the GMPLS TED switching capability information." ::= { tedTables 4 } T. Otani et al. Expires Jan. 2009 [Page 15] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 teSwCapEntry OBJECT-TYPE SYNTAX TeSwCapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry relates each TE link with its GMPLS TE switching capability information. IF the MIB deals with only OSPF-TE information, the value of each object related with GMPLS TE extensions should be null." INDEX { teAreaId, teRouterId, teLinkStateId, teSwCapIndex } ::= { teSwCapTable 1 } TeSwCapEntry ::= SEQUENCE { teSwCapIndex Unsigned32, teSwitchingType IANAGmplsSwitchingTypeTC, teEncoding IANAGmplsLSPEncodingTypeTC, teMaxLspBandwidthPri0 Unsigned32, teMaxLspBandwidthPri1 Unsigned32, teMaxLspBandwidthPri2 Unsigned32, teMaxLspBandwidthPri3 Unsigned32, teMaxLspBandwidthPri4 Unsigned32, teMaxLspBandwidthPri5 Unsigned32, teMaxLspBandwidthPri6 Unsigned32, teMaxLspBandwidthPri7 Unsigned32, teMinLspBandwidth Unsigned32, teIntMtu Integer32, teIndication INTEGER } teSwCapIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is utilized to identify multiple switching functions on a local or remote TE link according to definitions of textual conventions of GMPLS [RFC4801]." ::= { teSwCapEntry 1 } teSwitchingType OBJECT-TYPE SYNTAX IANAGmplsSwitchingTypeTC MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the GMPLS switching capability assigned to the TE link according to definitions of textual conventions of GMPLS [RFC4801]. " ::= { teSwCapEntry 2 } teEncoding OBJECT-TYPE SYNTAX IANAGmplsLSPEncodingTypeTC MAX-ACCESS read-only STATUS current T. Otani et al. Expires Jan. 2009 [Page 16] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 DESCRIPTION "This object indicates the GMPLS encoding type assigned to the TE link." ::= { teSwCapEntry 3 } teMaxLspBandwidthPri0 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 0 for GMPLS LSP creation." ::= { teSwCapEntry 4 } teMaxLspBandwidthPri1 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 1 for GMPLS LSP creation." ::= { teSwCapEntry 5 } teMaxLspBandwidthPri2 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 2 for GMPLS LSP creation." ::= { teSwCapEntry 6 } teMaxLspBandwidthPri3 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 3 for GMPLS LSP creation." ::= { teSwCapEntry 7 } teMaxLspBandwidthPri4 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 4 for GMPLS LSP creation." ::= { teSwCapEntry 8 } T. Otani et al. Expires Jan. 2009 [Page 17] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 teMaxLspBandwidthPri5 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 5 for GMPLS LSP creation." ::= { teSwCapEntry 9 } teMaxLspBandwidthPri6 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 6 for GMPLS LSP creation." ::= { teSwCapEntry 10 } teMaxLspBandwidthPri7 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 7 for GMPLS LSP creation." ::= { teSwCapEntry 11 } teMinLspBandwidth OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the minimum bandwidth of the TE link for GMPLS LSP creation if the switching capability field is TDM, PSC- 1, PSC-2, PSC-3, or PSC-4." ::= { teSwCapEntry 12 } teIntMtu OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the MTU of the local or remote TE link" ::= { teSwCapEntry 13 } teIndication OBJECT-TYPE SYNTAX INTEGER { T. Otani et al. Expires Jan. 2009 [Page 18] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 standard (0), arbitrary (1) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether the interface supports Standard or Arbitrary SONET/SDH." ::= { teSwCapEntry 14 } -- -- TED SRLG Table -- teSrlgTable OBJECT-TYPE SYNTAX SEQUENCE OF TeSrlgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the SRLG information of the TE link." ::= { tedTables 5 } teSrlgEntry OBJECT-TYPE SYNTAX TeSrlgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry relates each TE link with its SRLG information." INDEX { teAreaId, teRouterId, teLinkStateId, teSrlgIndex } ::= { teSrlgTable 1 } TeSrlgEntry ::= SEQUENCE { teSrlgIndex Unsigned32, teSrlg Integer32 } teSrlgIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is utilized to identify multiple SRLG values on a local or remote TE link." ::= { teSrlgEntry 1 } teSrlg OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicate the SRLG value assigned to a local or remote TE link" ::= { teSrlgEntry 2 } T. Otani et al. Expires Jan. 2009 [Page 19] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 -- -- Notifications -- tedTeInfoStatusChange NOTIFICATION-TYPE OBJECTS { teAreaId, teRouterId, teLinkStateId } STATUS current DESCRIPTION "This notification is generated when TED information is changed." ::= { tedNotifications 1 } tedTeCreation NOTIFICATION-TYPE OBJECTS { teAreaId, teRouterId, teLinkStateId } STATUS current DESCRIPTION " This notification is generated when a new entry is registered as TED information." ::= { tedNotifications 2 } tedTeDeletion NOTIFICATION-TYPE OBJECTS { teAreaId, teRouterId, teLinkStateId } STATUS current DESCRIPTION "This notification is generated when one of existing entries is deleted." ::= { tedNotifications 3 } -- Conformance Statement tedGroups OBJECT IDENTIFIER ::= { tedConformance 1 } tedCompliances OBJECT IDENTIFIER ::= { tedConformance 2 } -- Module Compliance teModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents provides full support for the TED MIB" MODULE -- this module MANDATORY-GROUPS { tedMainGroup } ::= { tedCompliances 1 } T. Otani et al. Expires Jan. 2009 [Page 20] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 -- -- ReadOnly Compliance -- teModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations only provide read-only support for TED. Such devices can then be monitored but cannot be configured using this MIB module. " MODULE -- this module MANDATORY-GROUPS { tedMainGroup } ::= { tedCompliances 2 } -- Units of conformance. tedMainGroup OBJECT-GROUP OBJECTS { teAreaId , teRouterId , teLinkStateId , tedNotificationEnabled , tedNotificationMaxRate , teLinkInformationSource , teLinkType , teRouterIdAddr , teLinkIdAddr , teMetric , teMaxBandwidth , teMaxReservableBandwidth , teUnreservedBandwidthPri0 , teUnreservedBandwidthPri1 , teUnreservedBandwidthPri2 , teUnreservedBandwidthPri3 , teUnreservedBandwidthPri4 , teUnreservedBandwidthPri5 , teUnreservedBandwidthPri6 , teUnreservedBandwidthPri7 , teAdministrativeGroup , teLocalId , teRemoteId , teLinkProtectionType , teLinkInformationData , teLocalIntAddr , teRemoteIntAddr , teSwitchingType , teEncoding , teMaxLspBandwidthPri0 , teMaxLspBandwidthPri1 , teMaxLspBandwidthPri2 , T. Otani et al. Expires Jan. 2009 [Page 21] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 teMaxLspBandwidthPri3 , teMaxLspBandwidthPri4 , teMaxLspBandwidthPri5 , teMaxLspBandwidthPri6 , teMaxLspBandwidthPri7 , teMinLspBandwidth , teIntMtu , teIndication , teSrlg } STATUS current DESCRIPTION "Collection of objects for TED management" ::= { tedGroups 1 } tedNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { tedTeInfoStatusChange, tedTeCreation, tedTeDeletion } STATUS current DESCRIPTION "This indicates a set of notifications implemented in this module" ::= { tedGroups 2 } END 8. Security consideration There are no management objects defined in this MIB module that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB module is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB module via direct SNMP SET operations. Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: - teTEDtable, teLocalIntAddrTable, teRemoteIntAddrTable, teSWcaptable and teSrlgtable contain topology information for the MPLS/GMPLS network. If an administrator does not want to reveal this information, then these tables should be considered sensitive/vulnerable. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even T. Otani et al. Expires Jan. 2009 [Page 22] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principles (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 9. IANA Considerations The following "IANA Considerations" subsection requests IANA for a new assignment under the transmission subtree. New assignments can only be made via a Standards Action as specified in [RFC5226]. 9.1 IANA Considerations for TED-MIB The IANA is requested to assign { transmission XXX } to the TED-MIB module specified in this document. 10. References 10.1 Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC4801] T. Nadeau and A. Farrel, Ed., "Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management", RFC4801, Feb. 2007. 10.2 Informative References T. Otani et al. Expires Jan. 2009 [Page 23] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 [RFC4750] Dan Joyal, et al, "OSPF Version 2 Management Information Base", RFC4750, December 2006. [RFC4444] J. Parker, et al, "Management Information Base for Intermediate System to Intermediate System (IS-IS)", RFC 4444, April 2006. [RFC4202] K. Kompella, and Y. Rekhter, "Routing Extensions in Support of Generalized Multi-Protocol Label Switching", RFC4202, Oct. 2005. [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions to OSPF Version2", RFC3630, September 2003. [RFC4205] K. Kompella, and Y. Rekhter, "Intermediate System to Intermediate System (IS-IS) Extensions in Support of Multi-Protocol Label Switching (GMPLS)", RFC4205, Oct. 2005. [RFC3784] H. Smit and T. Li, "IS-IS extensions for Traffic Engineering", RFC 3784, June 2004. [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching (LSR) Router Management Information Base (MIB)", RFC 3813, June 2004. [RFC4802] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base", RFC4802, Feb., 2007. [RFC4803] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", RFC4803, Feb., 2007. [RFC4377] T. Nadeau, Allan D., et al., "OAM Requirements for MPLS Network", RFC4377, Feb., 2006. [RFC3945] E. Mannie, "Generalized Multi-Protocol Label Switching Architecture", RFC3945, October, 2004. [RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in Support of Generalized Multi-Protocol Label Switching", RFC4203, Oct. 2005. [RFC3630] Katz, D., et al, "Traffic Engineering (TE) Extensions to OSPF Version 2", RFC3630, September 2003. T. Otani et al. Expires Jan. 2009 [Page 24] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 [RFC5226] Narten, T. and H. Alvestrand., " Guidelines for Writing an IANA Considerations Section in RFCs" BCP 26, RFC 5226, May 2008. [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction and Applicability Statement for Internet Standard Management Framework", RFC 3410, December 2002. 11. Acknowledgment The authors wish to acknowledge and thank the following individuals for their valuable comments to this document: Ken Nagami, Shuichi Okamoto, Adrian Farrel and Diego Caviglia. 12. Author's Address Tomohiro Otani KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan Phone: +81-49-278-7357 Email: otani@kddilabs.jp Masanori Miyazawa KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan. Phone: +81-49-278-7559 Email: ma-miyazawa@kddilabs.jp Thomas D. Nadeau BT Email: tom.nadeau@bt.com Kenji Kumaki KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan Phone: +81-49-278-7863 Email: ke-kumaki@kddilabs.jp 13. Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an T. Otani et al. Expires Jan. 2009 [Page 25] Internet Drafts draft-ietf-ccamp-gmpls-ted-mib-04.txt July 2008 attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. T. Otani et al. Expires Jan. 2009 [Page 26]