--- 1/draft-ietf-ccamp-gmpls-te-mib-13.txt 2006-04-12 23:12:24.000000000 +0200 +++ 2/draft-ietf-ccamp-gmpls-te-mib-14.txt 2006-04-12 23:12:24.000000000 +0200 @@ -1,22 +1,22 @@ Internet Working Group Thomas D. Nadeau, Ed. Internet Draft Cisco Systems, Inc. Proposed Status: Standards Track Expires: September 2006 Adrian Farrel, Ed. Old Dog Consulting - March 2006 + April 2006 Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base - draft-ietf-ccamp-gmpls-te-mib-13.txt + draft-ietf-ccamp-gmpls-te-mib-14.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 @@ -39,21 +39,23 @@ This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Generalized Multiprotocol Label Switching (GMPLS) based traffic engineering. Table of Contents 1. Introduction ........................................... 2 1.1. Migration Strategy ................................... 3 2. Terminology ............................................ 3 - 3. The SNMP Management Framework .......................... 4 + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + + 3. The Internet-Standard Management Framework ............. 4 4. Outline ................................................ 4 4.1. Summary of GMPLS Traffic Engineering MIB Module ...... 4 5. Brief Description of GMPLS TE MIB Objects .............. 5 5.1. gmplsTunnelTable ..................................... 5 5.2. gmplsTunnelHopTable .................................. 6 5.3. gmplsTunnelARHopTable ................................ 6 5.4. gmplsTunnelCHopTable ................................. 6 5.5. gmplsTunnelErrorTable ................................ 6 5.6. gmplsTunnelReversePerfTable .......................... 6 5.7. Use of 32-bit and 64-bit Counters ................... 6 @@ -87,20 +89,22 @@ The MIB modules in this document should be used in conjunction with the companion document [GMPLSLSRMIB] for GMPLS based traffic engineering configuration and management. Comments should be made direct to the CCAMP mailing list at ccamp@ops.ietf.org. 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 BCP 14, RFC 2119, + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + reference [RFC2119]. 1.1. Migration Strategy MPLS-TE LSPs may be modeled and managed using the MPLS-TE-STD-MIB module [RFC3812]. LSRs may be migrated to model and manage their TE LSPs using the MIB modules in this document in order to migrate the LSRs to GMPLS support, or to take advandtage of additional MIB objects defined in @@ -135,26 +139,28 @@ An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It consists of in-segment(s) and/or out-segment(s) at the egress/ingress LSRs, each segment being associated with one GMPLS enabled interface. These are also referred to as tunnel segments. Additionally, at an intermediate LSR, we model a connection as consisting of one or more in-segments and/or one or more out-segments. The binding or interconnection between in-segments and out-segments in performed using a cross-connect. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + These segment and cross-connect objects are defined in the MPLS Label Switch Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the GMPLS Label Switch Router MIB (GMPLS-LSR-STD-MIB) [GMPLSLSRMIB] for the GMPLS-specific extensions to these objects. -3. The SNMP Management Framework +3. 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 @@ -183,20 +189,22 @@ 4.1. Summary of GMPLS Traffic Engineering MIB Module The following tables contain MIB objects for performing the actions listed above when they cannot be performed solely using MIB objects defined in MPLS-TE-STD-MIB [RFC3812]. - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific tunnel configuration parameters. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + - Tunnel specified, actual, and computed hop tables (gmplsTunnelHopTable, gmplsTunnelARHopTable, and gmplsTunnelCHopTable) for providing additional configuration of strict and loose source routed tunnel hops. - Performance and error reporting tables (gmplsTunnelReversePerfTable and gmplsTunnelErrorTable). These tables are described in the subsequent sections. Additionally, the GMPLS-TE-STD-MIB module contains a new @@ -231,20 +239,22 @@ and/or one in-segment terminating at that LSR. Three objects within this table utilize enumerations in order to map to enumerations that are used in GMPLS signaling. In order to protect the GMPLS-TE-STD-MIB module from changes (in particular, extensions) to the range of enumerations supported by the signaling protocols, these MIB objects use Textual Conventions with values maintained by IANA. For further details, see the IANA Considerations section of this document. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + 5.2. gmplsTunnelHopTable The gmplsTunnelHopTable is used to indicate additional parameters for the hops, strict or loose, of a GMPLS tunnel defined in gmplsTunnelTable, when it is established using signaling. Multiple tunnels may share hops by pointing to the same entry in this table. 5.3. gmplsTunnelARHopTable The gmplsTunnelARHopTable is used to indicate the actual hops @@ -279,36 +289,39 @@ 5.7. Use of 32-bit and 64-bit Counters 64-bit counters are provided in the GMPLS-TE-STD-MIB module for high-speed interfaces where the use of 32-bit counters might be impractical. The requirements on the use of 32-bit and 64-bit counters (copied verbatim from [RFC2863]) are as follows: For interfaces that operate at 20,000,000 (20 million) bits per second or less, 32-bit byte and packet counters MUST be supported. + + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + For interfaces that operate faster than 20,000,000 bits/second, and slower than 650,000,000 bits/second, 32-bit packet counters MUST be supported and 64-bit octet counters MUST be supported. For interfaces that operate at 650,000,000 bits/second or faster, 64-bit packet counters AND 64-bit octet counters MUST be supported. 6. Cross-referencing to the gmplsLabelTable The gmplsLabelTable is found in the GMPLS-LABEL-STD-MIB module in [GMPLSLSRMIB] and provides a way to model labels in a GMPLS system where labels might not be simple 32 bit integers. - The hop tables in this document (gmplsHopTable, gmplsCHopTable and - gmplsARHopTable) and the segment tables in the [RFC3813] - (mplsInSegmentTable and mplsOutSegmentTable) contain objects with - syntax MplsLabel. + The hop tables in this document (gmplsTunnelHopTable, + gmplsTunnelCHopTable and gmplsTunnelARHopTable) and the segment + tables in the [RFC3813] (mplsInSegmentTable and mplsOutSegmentTable) + contain objects with syntax MplsLabel. MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable of representing any MPLS label and most GMPLS labels. However, some GMPLS labels are larger than 32 bits and may be of arbitrary length. Further, some labels that may be safely encoded in 32 bits are constructed from multiple sub-fields. Additionally, some GMPLS technologies support the concatenation of individual labels to represent a data flow carried as multiple sub-flows. These GMPLS cases require that something other than a simple 32-bit @@ -326,20 +339,21 @@ This provides both a good way to support legacy systems that implement the MPLS-TE-STD-MIB [RFC3812], and a significant simplification in GMPLS systems that are limited to a single, simple label type. Note that gmplsLabelTable supports concatenated labels through the use of a label sub-index (gmplsLabelSubindex). 7. Example of GMPLS Tunnel Setup + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 This section contains an example of which MIB objects should be modified to create a GMPLS tunnel. This example shows a best effort, loosely routed, bidirectional traffic engineered tunnel, which spans two hops of a simple network, uses Generalized Label requests with Lambda encoding, has label recording and shared link layer protection. Note that these objects should be created on the "head-end" LSR. First in the mplsTunnelTable: @@ -375,25 +389,28 @@ { gmplsTunnelUnnumIf = true (1), gmplsTunnelAttributes = labelRecordingRequired (1), gmplsTunnelLSPEncoding = tunnelLspLambda, gmplsTunnelSwitchingType = lsc, gmplsTunnelLinkProtection = shared (2), gmplsTunnelGPid = lambda, gmplsTunnelSecondary = false (2), gmplsTunnelDirection = bidirectional (1) gmplsTunnelPathComp = explicit(2), + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + gmplsTunnelSendPathNotifyRecipientType = ipv4(1), gmplsTunnelSendPathNotifyRecipient = 'C0000201'H, gmplsTunnelAdminStatusFlags = 0, gmplsTunnelExtraParamsPtr = 0.0 } + Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and gmplsTunnelHopTable are created and activated at this time. In mplsTunnelResourceTable: { mplsTunnelResourceIndex = 6, mplsTunnelResourceMaxRate = 0, mplsTunnelResourceMeanRate = 0, mplsTunnelResourceMaxBurstSize = 0, mplsTunnelResourceRowStatus = createAndGo (4) @@ -422,20 +439,22 @@ example. We have used the fictitious LSR identified by "192.0.2.2" as our tail end router. In mplsTunnelHopTable: { mplsTunnelHopListIndex = 1, mplsTunnelPathOptionIndex = 1, mplsTunnelHopIndex = 2, mplsTunnelHopAddrType = ipV4 (1), mplsTunnelHopIpv4Addr = 192.0.2.2, + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + mplsTunnelHopIpv4PrefixLen = 9, mplsTunnelHopType = loose (2), mplsTunnelHopRowStatus = createAndGo (4) } Now an associated entry in the gmplsTunnelHopTable is created to provide additional GMPLS hop configuration indicating that the first hop is an unnumbered link using explicit forward and reverse labels. An entry in the gmplsLabelTable is created first to include the @@ -468,20 +487,21 @@ No gmplsTunnelHopEntry is created for the second hop as it contains no special GMPLS features. Finally the mplsTunnelEntry is activated: In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2) { mplsTunnelRowStatus = active(1) } + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 8. GMPLS Traffic Engineering MIB Module This MIB module makes references to the following documents. [RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], [RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], [RFC4202] and [RFC4328]. GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN @@ -496,69 +516,69 @@ InetAddress, InetAddressType FROM INET-ADDRESS-MIB -- RFC4001 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC3411 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId, mplsTunnelHopListIndex, mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, mplsTunnelARHopListIndex, mplsTunnelARHopIndex, mplsTunnelCHopListIndex, mplsTunnelCHopIndex, mplsTunnelEntry, - mplsTunnelAdminStatus, mplsTunnelOperStatus + mplsTunnelAdminStatus, mplsTunnelOperStatus, + mplsTunnelGroup, mplsTunnelScalarGroup FROM MPLS-TE-STD-MIB -- RFC3812 - IANAGmplsLSPEncodingType, IANAGmplsSwitchingType, - IANAGmplsGeneralizedPid, IANAGmplsAdminStatusInformation + IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC, + IANAGmplsGeneralizedPidTC, IANAGmplsAdminStatusInformationTC FROM IANA-GMPLS-TC-MIB mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC3811 ; gmplsTeStdMIB MODULE-IDENTITY LAST-UPDATED - "200603020001Z" -- 2 March 2006 00:00:01 GMT + "200604060001Z" -- 06 April 2006 00:00:01 GMT ORGANIZATION "IETF Common Control And Measurement Plane (CCAMP) Working Group" CONTACT-INFO " Thomas D. Nadeau Cisco Systems, Inc. Email: tnadeau@cisco.com + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk + Comments about this document should be emailed direct to the CCAMP working group mailing list at ccamp@ops.ietf.org" DESCRIPTION "Copyright (C) The Internet Society (2006). This version of - this MIB module is part of RFC xxxx; see the RFC itself for + this MIB module is part of RFC XXX; see the RFC itself for full legal notices. --- RFC Ed. Please replace xxxx above with the correct RFC number and +-- RFC Ed. Please replace XXX above with the correct RFC number and -- remove this note. This MIB module contains managed object definitions for GMPLS Traffic Engineering (TE) as defined in: 1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, Berger, L. (Editor), RFC 3471, January 2003. 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. (Editor), RFC 3473, January 2003." REVISION - "200603020001Z" -- 2 March 2006 00:00:01 GMT + "200604060001Z" -- 06 April 2006 00:00:01 GMT DESCRIPTION - "Initial version issued as part of RFC xxxx." + "Initial version issued as part of RFC XXX." ::= { mplsStdMIB XXX } --- RFC Editor. Please replace xxxx above with the correct RFC number and --- remove this note. - -- RFC Editor. Please replace XXX above with the OID assigned by IANA -- and remove this note gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } gmplsTunnelsConfigured OBJECT-TYPE SYNTAX Gauge32 @@ -563,37 +583,40 @@ gmplsTunnelsConfigured OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of GMPLS tunnels configured on this device. A GMPLS tunnel is considered configured if an entry for the tunnel exists in the gmplsTunnelTable and the associated mplsTunnelRowStatus is active(1)." ::= { gmplsTeScalars 1 } + gmplsTunnelsActive OBJECT-TYPE SYNTAX Gauge32 + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + MAX-ACCESS read-only STATUS current DESCRIPTION "The number of GMPLS tunnels active on this device. A GMPLS tunnel is considered active if there is an entry in the gmplsTunnelTable and the associated mplsTunnelOperStatus for the tunnel is up(1)." ::= { gmplsTeScalars 2 } gmplsTunnelTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The gmplsTunnelTable sparse augments the mplsTunnelTable of + "The gmplsTunnelTable sparsely extends the mplsTunnelTable of MPLS-TE-STD-MIB. It allows GMPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point-to-multi-point connections are supported by an LSR acting as a cross-connect. Each tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. @@ -603,75 +626,81 @@ value active(1) a row in this table may not be created or modified. The exception to this rule is the gmplsTunnelAdminStatusInformation object, which can be modified whilst the tunnel is active." REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB), RFC 3812." ::= { gmplsTeObjects 1 } + gmplsTunnelEntry OBJECT-TYPE SYNTAX GmplsTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table in association with the corresponding entry in the mplsTunnelTable represents a GMPLS tunnel. An entry can be created by a network administrator via SNMP SET + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + commands, or in response to signaling protocol events." INDEX { mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId } ::= { gmplsTunnelTable 1 } GmplsTunnelEntry ::= SEQUENCE { gmplsTunnelUnnumIf TruthValue, gmplsTunnelAttributes BITS, - gmplsTunnelLSPEncoding IANAGmplsLSPEncodingType, - gmplsTunnelSwitchingType IANAGmplsSwitchingType, + gmplsTunnelLSPEncoding IANAGmplsLSPEncodingTypeTC, + gmplsTunnelSwitchingType IANAGmplsSwitchingTypeTC, gmplsTunnelLinkProtection BITS, - gmplsTunnelGPid IANAGmplsGeneralizedPid, + gmplsTunnelGPid IANAGmplsGeneralizedPidTC, gmplsTunnelSecondary TruthValue, gmplsTunnelDirection INTEGER, gmplsTunnelPathComp INTEGER, gmplsTunnelUpstreamNotifyRecipientType InetAddressType, gmplsTunnelUpstreamNotifyRecipient InetAddress, gmplsTunnelSendResvNotifyRecipientType InetAddressType, gmplsTunnelSendResvNotifyRecipient InetAddress, gmplsTunnelDownstreamNotifyRecipientType InetAddressType, gmplsTunnelDownstreamNotifyRecipient InetAddress, gmplsTunnelSendPathNotifyRecipientType InetAddressType, gmplsTunnelSendPathNotifyRecipient InetAddress, - gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformation, + gmplsTunnelAdminStatusFlags IANAGmplsAdminStatusInformationTC, gmplsTunnelExtraParamsPtr RowPointer } + gmplsTunnelUnnumIf OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether or not this tunnel corresponds to an unnumbered interface represented by an entry in the interfaces group table (the ifTable) with ifType set to mpls (166). - This object is only used if mplsTunnelIsIf is set to true(1). + This object is only used if mplsTunnelIsIf is set to 'true'. If both this object and the mplsTunnelIsIf object are set to - true(1), the originating LSR adds an LSP_TUNNEL_INTERFACE_ID + 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID object to the outgoing Path message. This object contains information that is only used by the + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + terminating LSR." REFERENCE "1. Signalling Unnumbered Links in RSVP-TE, RFC 3477." DEFVAL { false } ::= { gmplsTunnelEntry 1 } gmplsTunnelAttributes OBJECT-TYPE SYNTAX BITS { labelRecordingDesired (0) } @@ -686,55 +715,59 @@ labelRecordingDesired This flag is set to indicate that label information should be included when doing a route record. This bit is not valid unless the recordRoute bit is set." REFERENCE "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, sections 4.4.3, 4.7.1 and 4.7.2." DEFVAL { { } } ::= { gmplsTunnelEntry 2 } + gmplsTunnelLSPEncoding OBJECT-TYPE - SYNTAX IANAGmplsLSPEncodingType + SYNTAX IANAGmplsLSPEncodingTypeTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the encoding of the LSP being requested. A value of 'tunnelLspNotGmpls' indicates that GMPLS signaling is not in use. Some objects in this MIB module may be of use for MPLS signaling extensions that do not use GMPLS signaling. By setting this object to 'tunnelLspNotGmpls', an application may indicate that only those objects meaningful in MPLS should be examined. The values to use are defined in the textual convention - IANAGmplsLSPEncodingType found in the IANA-GMPLS-TC-MIB module." + IANAGmplsLSPEncodingTypeTC found in the IANA-GMPLS-TC-MIB + module." DEFVAL { tunnelLspNotGmpls } ::= { gmplsTunnelEntry 3 } + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 gmplsTunnelSwitchingType OBJECT-TYPE - SYNTAX IANAGmplsSwitchingType + SYNTAX IANAGmplsSwitchingTypeTC MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the type of switching that should be performed on a particular link. This field is needed for links that advertise more than one type of switching capability. The values to use are defined in the textual convention - IANAGmplsSwitchingType found in the IANA-GMPLS-TC-MIB module. + IANAGmplsSwitchingTypeTC found in the IANA-GMPLS-TC-MIB module. This object is only meaningful if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'." DEFVAL { unknown } ::= { gmplsTunnelEntry 4 } + gmplsTunnelLinkProtection OBJECT-TYPE SYNTAX BITS { extraTraffic(0), unprotected(1), shared (2), dedicatedOneToOne (3), dedicatedOnePlusOne(4), enhanced(5) } MAX-ACCESS read-create @@ -752,20 +785,22 @@ unprotected This glag is set to indicate that the LSP should not use any link layer protection. shared This flage is set to indicate that a shared link layer protection scheme, such as 1:N protection, should be used to support the LSP. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + dedicatedOneToOne This flag is set to indicate that a dedicated link layer protection scheme, i.e., 1:1 protection, should be used to support the LSP. dedicatedOnePlusOne This flag is set to indicate that a dedicated link layer protection scheme, i.e., 1+1 protection, should be used to support the LSP. @@ -769,49 +804,52 @@ protection scheme, i.e., 1+1 protection, should be used to support the LSP. enhanced This flag is set to indicate that a protection scheme that is more reliable than Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. This object is only meaningful if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'." + REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 7.1." DEFVAL { { } } ::= { gmplsTunnelEntry 5 } gmplsTunnelGPid OBJECT-TYPE - SYNTAX IANAGmplsGeneralizedPid + SYNTAX IANAGmplsGeneralizedPidTC MAX-ACCESS read-create STATUS current DESCRIPTION "This object indicates the payload carried by the LSP. It is only required when GMPLS will be used for this LSP. The values to use are defined in the textual convention - IANAGmplsGeneralizedPid found in the IANA-GMPLS-TC-MIB module. + IANAGmplsGeneralizedPidTC found in the IANA-GMPLS-TC-MIB module. This object is only meaningful if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'." DEFVAL { unknown } ::= { gmplsTunnelEntry 6 } gmplsTunnelSecondary OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates that the requested LSP is a secondary LSP. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + This object is only meaningful if gmplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'." REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 7.1." DEFVAL { false } ::= { gmplsTunnelEntry 7 } gmplsTunnelDirection OBJECT-TYPE SYNTAX INTEGER { @@ -847,40 +885,46 @@ The user specifies at least the source and destination of the path and expects that the CSPF will calculate the remainder of the path. explicit The user specifies the entire path for the tunnel to take. This path may contain strict or loose hops. Evaluation of the explicit route will be performed hop by hop through the network. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + dynamicPartial The user specifies at least the source and destination of the path and expects that the CSPF will calculate the remainder of the path. The path computed by CSPF is allowed to be only partially computed allowing the remainder of the path to be filled in across the network. When an entry is present in gmplsTunnelTable for a tunnel, gmplsTunnelPathComp MUST be used and any corresponding mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable MUST be ignored and SHOULD not be set. mplsTunnelHopTable and mplsTunnelHopEntryPathComp are part of - MPLS-TE-STD-MIB." + MPLS-TE-STD-MIB. + + This object should be ignored if value of gmplsTunnelLSPEncoding + is 'tunnelLspNotGmpls'." REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB), RFC 3812." DEFVAL { dynamicFull } ::= { gmplsTunnelEntry 9 } + gmplsTunnelUpstreamNotifyRecipientType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to aid in interpretation of gmplsTunnelUpstreamNotifyRecipient." DEFVAL { unknown } ::= { gmplsTunnelEntry 10 } @@ -890,20 +934,22 @@ STATUS current DESCRIPTION "Indicates the address of the upstream recipient for Notify messages relating to this tunnel and issued by this LSR. This information is typically received from an upstream LSR in a Path message. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the head end of a tunnel since there are + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + no upstream LSRs to which to send a Notify message. This object is interpreted in the context of the value of gmplsTunnelUpstreamNotifyRecipient. If this object is set to 0, the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to unknown(0)." REFERENCE "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, section 4.2." DEFVAL { '00000000'H } -- 0.0.0.0 @@ -936,20 +983,21 @@ This object is interpreted in the context of the value of gmplsTunnelSendResvNotifyRecipientType. If this object is set to 0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be set to unknown(0)." REFERENCE "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, section 4.2." DEFVAL { '00000000'H } -- 0.0.0.0 ::= { gmplsTunnelEntry 13 } + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 gmplsTunnelDownstreamNotifyRecipientType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to aid in interpretation of gmplsTunnelDownstreamNotifyRecipient." DEFVAL { unknown } ::= { gmplsTunnelEntry 14 } @@ -986,20 +1033,22 @@ "This object is used to aid in interpretation of gmplsTunnelSendPathNotifyRecipient." DEFVAL { unknown } ::= { gmplsTunnelEntry 16 } gmplsTunnelSendPathNotifyRecipient OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + "Indicates to a downstream LSR the address to which it should send upstream Notify messages relating to this tunnel. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the tail end of the tunnel since no Path messages are sent from that LSR for this tunnel. If set to 0, no Notify Request object will be included in the outgoing Path messages. @@ -1007,66 +1056,69 @@ This object is interpreted in the context of the value of gmplsTunnelSendPathNotifyRecipientType. If this object is set to 0, the value of gmplsTunnelSendPathNotifyRecipientType MUST be set to unknown(0)." REFERENCE "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, section 4.2." DEFVAL { '00000000'H } -- 0.0.0.0 ::= { gmplsTunnelEntry 17 } + gmplsTunnelAdminStatusFlags OBJECT-TYPE - SYNTAX IANAGmplsAdminStatusInformation + SYNTAX IANAGmplsAdminStatusInformationTC MAX-ACCESS read-create STATUS current DESCRIPTION "Determines the setting of the Admin Status flags in the Admin Status object or TLV, as described in RFC 3471. Setting this field to a non-zero value will result in the inclusion of the admin status object on signaling messages. The values to use are defined in the textual convention - IANAGmplsAdminStatusInformation found in the IANA-GMPLS-TC-MIB - module. + IANAGmplsAdminStatusInformationTC found in the + IANA-GMPLS-TC-MIB module. This value of this object can be modified when the corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus is active(1). By doing so, a new signaling message will be triggered including the requested Admin Status object or TLV." REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 8." DEFVAL { { } } ::= { gmplsTunnelEntry 18 } gmplsTunnelExtraParamsPtr OBJECT-TYPE + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "Some Tunnels will run over transports that can usefully support technology-specific additional parameters (for example, SONET resource usage). Such parameters can be supplied in an external table and referenced from here. A value of zeroDotzero in this attribute indicates that there is no such additional information." DEFVAL { zeroDotZero } ::= { gmplsTunnelEntry 19 } gmplsTunnelHopTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The gmplsTunnelHopTable sparse augments the mplsTunnelHopTable + "The gmplsTunnelHopTable sparsely extends the mplsTunnelHopTable of MPLS-TE-STD-MIB. It is used to indicate the explicit labels to be used in an explicit path for a GMPLS tunnel defined in mplsTunnelTable and gmplsTunnelTable, when it is established using signaling. It does not insert new hops, but does define new values for hops defined in mplsTunnelHopTable. Each row in this table is indexed by the same indexes as mplsTunnelHopTable. It is acceptable for some rows in mplsTunnelHopTable to have corresponding entries in this table and some to have no corresponding entry in this table. @@ -1081,20 +1133,22 @@ in this table, nor to modify an existing row, when the corresponding mplsTunnelHopRowStatus has value active(1)." REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB), RFC 3812. 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." ::= { gmplsTeObjects 2 } gmplsTunnelHopEntry OBJECT-TYPE SYNTAX GmplsTunnelHopEntry + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents additions to a tunnel hop defined in mplsTunnelHopEntry. At an ingress to a tunnel an entry in this table is created by a network administrator for an ERLSP to be set up by a signaling protocol. At transit and egress nodes an entry in this table may be used to represent the explicit path instructions received using the signaling protocol." @@ -1128,20 +1183,22 @@ For the Present bits, a set bit indicates that a label is present for this hop in the route. This allows zero to be a valid label value." DEFVAL { { } } ::= { gmplsTunnelHopEntry 1 } gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + STATUS current DESCRIPTION "If gmplsTunnelHopLabelStatuses object indicates that a forward label is present and gmplsTunnelHopExplicitForwardLabelPtr contains the value zeroDotZero, then the label to use on this hop is represented by the value of this object." ::= { gmplsTunnelHopEntry 2 } gmplsTunnelHopExplicitForwardLabelPtr OBJECT-TYPE SYNTAX RowPointer @@ -1176,33 +1234,35 @@ SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "If the gmplsTunnelHopLabelStatuses object indicates that a reverse label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of the GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the reverse direction. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + If the gmplsTunnelHopLabelStatuses object indicates that a reverse label is present and this object contains the value zeroDotZero, then the label to use on this hop is found in the gmplsTunnelHopExplicitReverseLabel object." DEFVAL { zeroDotZero } ::= { gmplsTunnelHopEntry 5 } gmplsTunnelARHopTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelARHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The gmplsTunnelARHopTable sparse augments the + "The gmplsTunnelARHopTable sparsely extends the mplsTunnelARHopTable of MPLS-TE-STD-MIB. It is used to indicate the labels currently in use for a GMPLS tunnel defined in mplsTunnelTable and gmplsTunnelTable, as reported by the signaling protocol. It does not insert new hops, but does define new values for hops defined in mplsTunnelARHopTable. Each row in this table is indexed by the same indexes as mplsTunnelARHopTable. It is acceptable for some rows in mplsTunnelARHopTable to have corresponding entries in this table and some to have no corresponding entry in this table. @@ -1214,29 +1274,31 @@ is optional. Furthermore, since the information in this table is actually provided by the signaling protocol after the path has been set-up, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read-only." REFERENCE "1. Extensions to RSVP for LSP Tunnels, RFC 3209. 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473. 3. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) - Management Information Base (MIB), RFC 3812. + Management Information Base (MIB), RFC 3812." ::= { gmplsTeObjects 3 } gmplsTunnelARHopEntry OBJECT-TYPE SYNTAX GmplsTunnelARHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents additions to a tunnel hop + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + visible in mplsTunnelARHopEntry. An entry is created by the signaling protocol for a signaled ERLSP set up by the signaling protocol. At any node on the LSP (ingress, transit or egress), this table and mplsTunnelARHopTable (if the tables are supported and if the signaling protocol is recording actual route information) contain the actual route of the whole tunnel. If the signaling protocol is not recording the actual route, this table MAY report the information from the gmplsTunnelHopTable or the @@ -1270,20 +1333,22 @@ STATUS current DESCRIPTION "This bitmask indicates the presence and status of labels indicated by the gmplsTunnelARHopExplicitForwardLabel or gmplsTunnelARHopExplicitForwardLabelPtr, and gmplsTunnelARHopExplicitReverseLabel or gmplsTunnelARHopExplicitReverseLabelPtr objects. For the Present bits, a set bit indicates that a label is present for this hop in the route. For the Global bits, a set + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + bit indicates that the label comes from the Global Label Space. A clear bit indicates that this is a Per-Interface label. A Global bit only has meaning if the corresponding Present bit is set." ::= { gmplsTunnelARHopEntry 1 } gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current @@ -1318,20 +1383,22 @@ STATUS current DESCRIPTION "If the gmplsTunnelARHopLabelStatuses object indicates that a reverse label is present and gmplsTunnelARHopExplicitReverseLabelPtr contains the value zeroDotZero, then the label in use on this hop is found in this object encoded as a 32-bit integer." ::= { gmplsTunnelARHopEntry 4 } gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "If the gmplsTunnelARHopLabelStatuses object indicates that a reverse label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of the GMPLS-LABEL-STD-MIB) that contains the label in use on this hop in the reverse direction. @@ -1362,23 +1429,26 @@ REFERENCE "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, section 4.4.1." ::= { gmplsTunnelARHopEntry 6 } gmplsTunnelCHopTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelCHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "The gmplsTunnelCHopTable sparse augments the mplsTunnelCHopTable + "The gmplsTunnelCHopTable sparsely extends the + mplsTunnelCHopTable of MPLS-TE-STD-MIB. It is used to indicate additional information about the hops of a GMPLS tunnel defined in + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + mplsTunnelTable and gmplsTunnelTable, as computed by a constraint-based routing protocol, based on the mplsTunnelHopTable and the gmplsTunnelHopTable. Each row in this table is indexed by the same indexes as mplsTunnelCHopTable. It is acceptable for some rows in mplsTunnelCHopTable to have corresponding entries in this table and some to have no corresponding entry in this table. Please note that since the information necessary to build @@ -1413,20 +1483,22 @@ INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } ::= { gmplsTunnelCHopTable 1 } GmplsTunnelCHopEntry ::= SEQUENCE { gmplsTunnelCHopLabelStatuses BITS, gmplsTunnelCHopExplicitForwardLabel Unsigned32, gmplsTunnelCHopExplicitForwardLabelPtr RowPointer, + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + gmplsTunnelCHopExplicitReverseLabel Unsigned32, gmplsTunnelCHopExplicitReverseLabelPtr RowPointer } gmplsTunnelCHopLabelStatuses OBJECT-TYPE SYNTAX BITS { forwardPresent (0), reversePresent (1) } MAX-ACCESS read-only @@ -1460,20 +1533,22 @@ "If the gmplsTunnelCHopLabelStatuses object indicates that a forward label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of the GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the forward direction. If the gmplsTunnelCHopLabelStatuses object indicates that a forward label is present and this object contains the value zeroDotZero, then the label to use on this hop is found in the gmplsTunnelCHopExplicitForwardLabel object." + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + ::= { gmplsTunnelCHopEntry 3 } gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "If the gmplsTunnelCHopLabelStatuses object indicates that a reverse label is present and gmplsTunnelCHopExplicitReverseLabelPtr contains the value @@ -1490,37 +1565,40 @@ reverse label is present, this object contains a pointer to a row in another MIB table (such as the gmplsLabelTable of the GMPLS-LABEL-STD-MIB) that contains the label to use on this hop in the reverse direction. If the gmplsTunnelCHopLabelStatuses object indicates that a reverse label is present and this object contains the value zeroDotZero, then the label to use on this hop is found in the gmplsTunnelCHopExplicitReverseLabel object." ::= { gmplsTunnelCHopEntry 5 } + gmplsTunnelReversePerfTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This table 'augments' the gmplsTunnelTable to provides + "This table augments the gmplsTunnelTable to provides per-tunnel packet performance information for the reverse direction of a bidirectional tunnel. It can be seen as supplementing the mplsTunnelPerfTable which augments the mplsTunnelTable. For links that do not transport packets, these packet counters cannot be maintained. For such links, attempts to read the objects in this table will return noSuchInstance. A tunnel can be known to be bidirectional by inspecting the gmplsTunnelDirection object." + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB), RFC 3812." ::= { gmplsTeObjects 5 } gmplsTunnelReversePerfEntry OBJECT-TYPE SYNTAX GmplsTunnelReversePerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -1556,20 +1634,22 @@ ::= { gmplsTunnelReversePerfEntry 1 } gmplsTunnelReversePerfHCPackets OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "High capacity counter for number of packets forwarded on the tunnel in the reverse direction if it is bidirectional. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + For links that do not transport packets, this packet counter cannot be maintained. For such links, this value will return a noSuchInstance." ::= { gmplsTunnelReversePerfEntry 2 } gmplsTunnelReversePerfErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION @@ -1601,27 +1682,28 @@ STATUS current DESCRIPTION "High capacity counter for number of bytes forwarded on the tunnel in the reverse direction if it is bidirectional. For links that do not transport packets, this packet counter cannot be maintained. For such links, this value will return a noSuchInstance." ::= { gmplsTunnelReversePerfEntry 5 } + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 gmplsTunnelErrorTable OBJECT-TYPE SYNTAX SEQUENCE OF GmplsTunnelErrorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION - "This table 'augments' the mplsTunnelTable + "This table augments the mplsTunnelTable This table provides per-tunnel information about errors. Errors may be detected locally or reported through the signaling protocol. Error reporting is not exclusive to GMPLS and this table may be applied in MPLS systems. Entries in this table are not persistent over system resets or re-initializations of the management system." REFERENCE "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB), RFC 3812." @@ -1649,20 +1732,22 @@ gmplsTunnelErrorReporter InetAddress, gmplsTunnelErrorCode Unsigned32, gmplsTunnelErrorSubcode Unsigned32, gmplsTunnelErrorTLVs OCTET STRING, gmplsTunnelErrorHelpString SnmpAdminString } gmplsTunnelErrorLastErrorType OBJECT-TYPE SYNTAX INTEGER { noError (0), + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + unknown (1), protocol (2), pathComputation (3), localConfiguration (4), localResources (5), localOther (6) } MAX-ACCESS read-only STATUS current DESCRIPTION @@ -1695,20 +1781,21 @@ "The time at which the last error occurred. This is presented as the value of SysUpTime when the error occurred or was reported to this node. If gmplsTunnelErrorLastErrorType has the value noError (0), then this object is ignored. Note that entries in this table are not persistent over system resets or re-initializations of the management system." ::= { gmplsTunnelErrorEntry 2 } + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 gmplsTunnelErrorReporterType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The address type of the error reported. This object is used to aid in interpretation of gmplsTunnelErrorReporter." @@ -1743,20 +1831,22 @@ DESCRIPTION "The primary error code associated with the last error. The interpretation of this error code depends on the value of gmplsTunnelErrorLastErrorType. If the value of gmplsTunnelErrorLastErrorType is noError (0) the value of this object should be 0 and should be ignored. If the value of gmplsTunnelErrorLastErrorType is protocol (2) the error should be interpreted in the context of the signling protocol identified by the mplsTunnelSignallingProto object." REFERENCE + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + "1. Resource ReserVation Protocol -- Version 1 Functional Specification, RFC 2205, section B. 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, section 7.3. 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, section 13.1." ::= { gmplsTunnelErrorEntry 5 } gmplsTunnelErrorSubcode OBJECT-TYPE SYNTAX Unsigned32 @@ -1789,20 +1881,22 @@ REFERENCE "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, section 8.2." ::= { gmplsTunnelErrorEntry 7 } gmplsTunnelErrorHelpString OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + "A textual string containing information about the last error, recovery actions and support advice. If there is no help string this object contains a zero length string. If the value of gmplsTunnelErrorLastErrorType is noError (0) this object should contain a zero length string, but may contain a help string indicating that there is no error." ::= { gmplsTunnelErrorEntry 8 } -- -- Notifications @@ -1838,20 +1931,22 @@ down events and SHOULD NOT use mplsTunnelDown. This notification is subject to the control of the mplsTunnelNotificationEnable. When that object is set to false(2) then the notification must not be issued. Further, this notification is also subject to mplsTunnelNotificationMaxRate. That object indicates the maximum number of notifications issued per second. If events occur more rapidly, the implementation may simply fail to emit + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + some notifications during that period, or may queue them until an appropriate time. The notification rate applies to the sum of all notificaitons in the MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB modules applied across the whole of the reporting device. mplsTunnelOperStatus, mplsTunnelAdminStatus, mplsTunnelDown, mplsTunnelNotificationEnable, and mplsTunnelNotificationMaxRate objects are found in MPLS-TE-STD-MIB." REFERENCE @@ -1869,169 +1964,187 @@ gmplsTeModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support for GMPLS-TE-STD-MIB. Such devices can then be monitored and also be configured using this MIB module. The mandatory group has to be implemented by all LSRs that originate, terminate or act as transit for TE-LSPs/tunnels. - In addition, depending on the type of tunnels supported, other groups become mandatory as explained below." + MODULE MPLS-TE-STD-MIB -- The MPLS-TE-STD-MIB, RFC3812 + + MANDATORY-GROUPS { + mplsTunnelGroup, + mplsTunnelScalarGroup + } + MODULE -- this module + MANDATORY-GROUPS { gmplsTunnelGroup, - gmplsTunnelScalarGroup, - gmplsTunnelSignaledGroup + gmplsTunnelScalarGroup } + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + + GROUP gmplsTunnelSignaledGroup + DESCRIPTION + "This group is mandatory for devices which support signaled + tunnel set up, in addition to gmplsTunnelGroup. The following + constraints apply: + mplsTunnelSignallingProto should be at least read-only + returning a value of ldp(2), or rsvp(3)." + + GROUP gmplsTunnelOptionalGroup + DESCRIPTION + "Objects in this group are optional." + + GROUP gmplsTeNotificationGroup + DESCRIPTION + "This group is mandatory for those implementations which can + implement the notifications contained in this group." + ::= { gmplsTeCompliances 1 } -- Compliance requirement for read-only compliant implementations. gmplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for GMPLS-TE-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB module." MODULE -- this module -- The mandatory group has to be implemented by all LSRs that -- originate, terminate or act as transit for TE-LSPs/tunnels. -- In addition, depending on the type of tunnels supported, other -- groups become mandatory as explained below. MANDATORY-GROUPS { gmplsTunnelGroup, - gmplsTunnelScalarGroup, - gmplsTunnelUnnumIf + gmplsTunnelScalarGroup } GROUP gmplsTunnelSignaledGroup DESCRIPTION "This group is mandatory for devices which support signaled tunnel set up, in addition to gmplsTunnelGroup. The following constraints apply: mplsTunnelSignallingProto should be at least read-only returning a value of ldp(2), or rsvp(3)." - - GROUP gmplsTunnelIsIntfcGroup - DESCRIPTION - "This group is mandatory for devices which support tunnels that - are interfaces, in addition to gmplsTunnelGroup." + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 GROUP gmplsTunnelOptionalGroup DESCRIPTION "Objects in this group are optional." + GROUP gmplsTeNotificationGroup DESCRIPTION "This group is mandatory for those implementations which can implement the notifications contained in this group." - -- All scalars have max access read-only - OBJECT gmplsTunnelAttributes MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsTunnelLSPEncoding - SYNTAX IANAGmplsLSPEncodingType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsTunnelSwitchingType - SYNTAX IANAGmplsSwitchingType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsTunnelLinkProtection MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsTunnelGPid - SYNTAX IANAGmplsGeneralizedPid MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsTunnelSecondary - SYNTAX TruthValue MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsTunnelDirection MIN-ACCESS read-only DESCRIPTION "Only forward (0) is required." OBJECT gmplsTunnelPathComp MIN-ACCESS read-only DESCRIPTION "Only explicit (2) is required." + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + OBJECT gmplsTunnelUpstreamNotifyRecipientType - SYNTAX InetAddressType + SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support + is required." OBJECT gmplsTunnelUpstreamNotifyRecipient - SYNTAX InetAddress + SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "An implementation is only required to support + unknown(0), ipv4(1) and ipv6(2) sizes." OBJECT gmplsTunnelSendResvNotifyRecipientType - SYNTAX InetAddressType + SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support + is required." OBJECT gmplsTunnelSendResvNotifyRecipient - SYNTAX InetAddress + SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "An implementation is only required to support + unknown(0), ipv4(1) and ipv6(2) sizes." OBJECT gmplsTunnelDownstreamNotifyRecipientType - SYNTAX InetAddressType + SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support + is required." OBJECT gmplsTunnelDownstreamNotifyRecipient - SYNTAX InetAddress + SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "An implementation is only required to support + unknown(0), ipv4(1) and ipv6(2) sizes." OBJECT gmplsTunnelSendPathNotifyRecipientType - SYNTAX InetAddressType + SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support + is required." OBJECT gmplsTunnelSendPathNotifyRecipient - SYNTAX InetAddress + SYNTAX InetAddress (SIZE(0|4|16)) MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." + DESCRIPTION "An implementation is only required to support + unknown(0), ipv4(1) and ipv6(2) sizes." + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + OBJECT gmplsTunnelAdminStatusFlags - SYNTAX IANAGmplsAdminStatusInformation MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT gmplsTunnelExtraParamsPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required." -- gmplsTunnelHopLabelStatuses has max access read-only @@ -2052,30 +2165,42 @@ "Write access is not required." OBJECT gmplsTunnelHopExplicitReverseLabelPtr MIN-ACCESS read-only DESCRIPTION "Write access is not required." -- gmplsTunnelARHopTable -- all objects have max access read-only - -- glmpsTunnelCHopTable + -- gmplsTunnelCHopTable -- all objects have max access read-only -- gmplsTunnelReversePerfTable -- all objects have max access read-only -- gmplsTunnelErrorTable -- all objects have max access read-only + OBJECT gmplsTunnelErrorReporterType + SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } + DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + + is required." + + OBJECT gmplsTunnelErrorReporter + SYNTAX InetAddress (SIZE(0|4|16)) + DESCRIPTION "An implementation is only required to support + unknown(0), ipv4(1) and ipv6(2)." ::= { gmplsTeCompliances 2 } + gmplsTunnelGroup OBJECT-GROUP OBJECTS { gmplsTunnelDirection, gmplsTunnelReversePerfPackets, gmplsTunnelReversePerfHCPackets, gmplsTunnelReversePerfErrors, gmplsTunnelReversePerfBytes, gmplsTunnelReversePerfHCBytes, gmplsTunnelErrorLastErrorType, gmplsTunnelErrorLastTime, @@ -2077,47 +2202,47 @@ gmplsTunnelReversePerfErrors, gmplsTunnelReversePerfBytes, gmplsTunnelReversePerfHCBytes, gmplsTunnelErrorLastErrorType, gmplsTunnelErrorLastTime, gmplsTunnelErrorReporterType, gmplsTunnelErrorReporter, gmplsTunnelErrorCode, gmplsTunnelErrorSubcode, gmplsTunnelErrorTLVs, - gmplsTunnelErrorHelpString + gmplsTunnelErrorHelpString, + gmplsTunnelUnnumIf } STATUS current DESCRIPTION "Necessary, but not sufficient, set of objects to implement tunnels. In addition, depending on the type of the tunnels supported (for example, manually configured or signaled, - persistent or non-persistent, etc.), the following other - groups defined below are mandatory: - - - gmplsTunnelSignaledGroup - - gmplsTunnelIsIntfcGroup." + persistent or non-persistent, etc.), the + gmplsTunnelSignaledGroup group is mandatory." ::= { gmplsTeGroups 1 } gmplsTunnelSignaledGroup OBJECT-GROUP OBJECTS { gmplsTunnelAttributes, gmplsTunnelLSPEncoding, gmplsTunnelSwitchingType, gmplsTunnelLinkProtection, gmplsTunnelGPid, gmplsTunnelSecondary, gmplsTunnelPathComp, gmplsTunnelUpstreamNotifyRecipientType, gmplsTunnelUpstreamNotifyRecipient, gmplsTunnelSendResvNotifyRecipientType, gmplsTunnelSendResvNotifyRecipient, + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + gmplsTunnelDownstreamNotifyRecipientType, gmplsTunnelDownstreamNotifyRecipient, gmplsTunnelSendPathNotifyRecipientType, gmplsTunnelSendPathNotifyRecipient, gmplsTunnelAdminStatusFlags, gmplsTunnelHopLabelStatuses, gmplsTunnelHopExplicitForwardLabel, gmplsTunnelHopExplicitForwardLabelPtr, gmplsTunnelHopExplicitReverseLabel, gmplsTunnelHopExplicitReverseLabelPtr @@ -2130,57 +2255,51 @@ gmplsTunnelScalarGroup OBJECT-GROUP OBJECTS { gmplsTunnelsConfigured, gmplsTunnelsActive } STATUS current DESCRIPTION "Scalar objects needed to implement MPLS tunnels." ::= { gmplsTeGroups 3 } - gmplsTunnelIsIntfcGroup OBJECT-GROUP - OBJECTS { - gmplsTunnelUnnumIf - } - STATUS current - DESCRIPTION - "Objects needed to implement tunnels that are interfaces." - ::= { gmplsTeGroups 4 } - gmplsTunnelOptionalGroup OBJECT-GROUP OBJECTS { gmplsTunnelExtraParamsPtr, gmplsTunnelARHopLabelStatuses, gmplsTunnelARHopExplicitForwardLabel, gmplsTunnelARHopExplicitForwardLabelPtr, gmplsTunnelARHopExplicitReverseLabel, gmplsTunnelARHopExplicitReverseLabelPtr, gmplsTunnelARHopProtection, gmplsTunnelCHopLabelStatuses, gmplsTunnelCHopExplicitForwardLabel, gmplsTunnelCHopExplicitForwardLabelPtr, gmplsTunnelCHopExplicitReverseLabel, gmplsTunnelCHopExplicitReverseLabelPtr } STATUS current DESCRIPTION "The objects in this group are optional." - ::= { gmplsTeGroups 5 } + ::= { gmplsTeGroups 6 } + gmplsTeNotificationGroup NOTIFICATION-GROUP + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + NOTIFICATIONS { gmplsTunnelDown } STATUS current DESCRIPTION "Set of notifications implemented in this module. None is mandatory." - ::= { gmplsTeGroups 6 } + ::= { gmplsTeGroups 7 } END 9. Security Considerations It is clear that the MIB modules described in this document in association with the MPLS-TE-STD-MIB [RFC3812] are potentially useful for monitoring of MPLS and GMPLS tunnels. These MIB modules can also be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially @@ -2202,24 +2321,26 @@ Some of the readable objects in these MIB modules (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: o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, - gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, + gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, and the gmplsTunnelErrorTable collectively show the tunnel network topology and status. If an Administrator does not want to reveal this information, then these tables should be considered + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + 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 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 these MIB modules. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), @@ -2253,24 +2374,24 @@ 11. IANA Considerations -- (Note to RFC-Editor:) -- We request that you assign contiguous RFC numbers to the three GMPLS -- MIB documents. -- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to -- draft-ietf-ccamp-gmpls-lsr-mib, and the third to -- draft-ietf-ccamp-gmpls-te-mib. -- (Please remove this note prior to publication.) + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 IANA is requested to root MIB objects in the MIB module contained in this document under the mplsStdMIB subtree. - In the future, GMPLS related standards track MIB modules should be rooted under the mplsStdMIB (sic) subtree. IANA has been requested to manage that namespace in the SMI Numbers registry [RFC3811]. New assignments can only be made via a Standards Action as specified in [RFC2434]. 11.1. IANA Considerations for GMPLS-TE-STD-MIB The IANA is requested to assign { mplsStdMIB XXX } to the GMPLS-TE-STD-MIB module specified in this document, and to record @@ -2303,67 +2424,72 @@ an IANA MIB module. The normal procedure is that this MIB module is moved into the direct control of IANA, at which time this section should be deleted from this document. IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module specified in this document as { transmission YYY }. -- RFC Editor. -- Please replace YYY above with assigned OID and remove this note. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, transmission FROM SNMPv2-SMI -- RFC2578 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 ianaGmpls MODULE-IDENTITY - LAST-UPDATED "200603020001Z" -- 2 March 2006 00:00:01 GMT - ORGANIZATION "IANA" + LAST-UPDATED + "200604060001Z" -- 06 April 2006 00:00:01 GMT + ORGANIZATION + "IANA" CONTACT-INFO " Internet Assigned Numbers Authority Postal: USC/Information Sciences Institute 4676 Admiralty Way, Marina del Rey, CA 90292 Tel: +1 310 822 1511 E-Mail: iana@isi.edu" DESCRIPTION "Copyright (C) The Internet Society (2006). The initial version - of this MIB module was published in RFC XXX. For full legal + of this MIB module was published in RFC YYY. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html" --- RFC Editor. Please replace XXX above with the correct RFC number +-- RFC Editor. Please replace YYY above with the correct RFC number -- Your actions may vary depending on how IANA chooses to handle -- this IANA MIB. -- Please remove this note. REVISION - "200603020001Z" -- 2 March 2006 00:00:01 GMT + "200604060001Z" -- 06 April 2006 00:00:01 GMT DESCRIPTION - "Initial version issued as part of RFC XXX." + "Initial version issued as part of RFC YYY." ::= { transmission YYY } -- RFC Editor. Please replace YYY above with the OID assigned by IANA --- Please replace XXX with the real RFC number. -- Please remove this note. - IANAGmplsLSPEncodingType ::= TEXTUAL-CONVENTION + IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is used as the syntax of the gmplsTunnelLSPEncoding object in the definition of GMPLS-TE-STD-MIB's gmplsTunnelTable. gmplsTunnelLSPEncoding is used to represent and control the LSP encoding type of an LSP signaled by a GMPLS signaling protocol. This textual convention is strongly tied to the LSP + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + Encoding Types sub-registry of the GMPLS Signaling Parameters registry managed by IANA. Values should be assigned by IANA in step with the LSP Encoding Types sub-registry and using the same registry management rules. However, the actual values used in this textual convention are solely within the purview of IANA and do not necessarily match the values in the values in the LSP Encoding Types sub-registry. The definition of this textual convention with the @@ -2398,21 +2524,23 @@ tunnelLspSdhSonet (5), -- SDH or SONET -- the value 6 is deprecated tunnelLspDigitalWrapper (7), -- Digital Wrapper tunnelLspLambda (8), -- Lambda tunnelLspFiber (9), -- Fiber -- the value 10 is deprecated tunnelLspFiberChannel (11), -- Fiber Channel tunnelDigitalPath (12), -- Digital Path tunnelOpticalChannel (13) -- Optical Channel } - IANAGmplsSwitchingType ::= TEXTUAL-CONVENTION + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + + IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is used as the syntax of the gmplsTunnelSwitchingType object in the definition of GMPLS-TE-STD-MIB's gmplsTunnelTable. gmplsTunnelSwitchingType is used to represent and control the LSP switching type of an LSP signaled by a GMPLS signaling protocol. @@ -2445,21 +2573,23 @@ unknown (0), -- none of the following, or not known psc1 (1), -- Packet-Switch-Capable 1 psc2 (2), -- Packet-Switch-Capable 2 psc3 (3), -- Packet-Switch-Capable 3 psc4 (4), -- Packet-Switch-Capable 4 l2sc (51), -- Layer-2-Switch-Capable tdm (100), -- Time-Division-Multiplex lsc (150), -- Lambda-Switch-Capable fsc (200) -- Fiber-Switch-Capable } - IANAGmplsGeneralizedPid ::= TEXTUAL-CONVENTION + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + + IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is used as the syntax of the gmplsTunnelGPid object in the definition of GMPLS-TE-STD-MIB's gmplsTunnelTable. gmplsTunnelGPid is used to represent and control the LSP Generalized Protocol Identifier (G-PID) of an LSP signaled by a GMPLS signaling protocol. @@ -2492,31 +2622,34 @@ -- RFC Editor. Please update this reference to the RFC before -- publication and remove this note SYNTAX INTEGER { unknown(0), -- unknown or none of the following -- the values 1, 2, 3 and 4 are reserved in RFC 3471 asynchE4(5), asynchDS3T3(6), asynchE3(7), bitsynchE3(8), bytesynchE3(9), + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + asynchDS2T2(10), bitsynchDS2T2(11), - -- the value 12 is reserved in RFC 3471 + reservedByRFC3471first(12), asynchE1(13), bytesynchE1(14), bytesynch31ByDS0(15), asynchDS1T1(16), bitsynchDS1T1(17), bytesynchDS1T1(18), vc1vc12(19), - -- the values 20 and 21 are reserved in RFC 3471 + reservedByRFC3471second(20), + reservedByRFC3471third(21), ds1SFAsynch(22), ds1ESFAsynch(23), ds3M23Asynch(24), ds3CBitParityAsynch(25), vtLovc(26), stsSpeHovc(27), posNoScramble16BitCrc(28), posNoScramble32BitCrc(29), posScramble16BitCrc(30), posScramble32BitCrc(31), @@ -2539,21 +2672,23 @@ g709CBRb (50), g709BSOT (51), g709BSNT (52), gfpIPorPPP (53), gfpEthernetMAC (54), gfpEthernetPHY (55), g709ESCON (56), g709FICON (57), g709FiberChannel (58) } - IANAGmplsAdminStatusInformation ::= TEXTUAL-CONVENTION + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + + IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This data type is used as the syntax of the gmplsTunnelAdminStatusFlags object in the definition of GMPLS-TE-STD-MIB's gmplsTunnelTable. gmplsTunnelAdminStatusFlags determines the setting of the Admin Status flags in the Admin Status object or TLV, as described in RFC 3471. Setting this object to a non-zero value will result in the inclusion of the Admin Status @@ -2585,23 +2720,25 @@ -- name for the new sub-registry as defined by IANA, and delete this -- note. The definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.) + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 Requests for new values should be made to IANA via email (iana@isi.edu)." + REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 8." SYNTAX BITS { reflect (0), -- Reflect bit (RFC 3471) reserved1 (1), -- reserved reserved2 (2), -- reserved reserved3 (3), -- reserved reserved4 (4), -- reserved reserved5 (5), -- reserved @@ -2631,20 +2768,21 @@ testing (29), -- Testing bit (RFC 3473) administrativelyDown (30), -- Admin down (RFC 3473) deleteInProgress (31) -- Delete bit (RFC 3473) } END 12. References 12.1. Normative References + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997. [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of @@ -2679,20 +2817,22 @@ [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. [RFC3477] Kompella, K. and Y. Rekhter, "Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)", RFC 3477, January 2003. [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + Conventions and for Multiprotocol Label Switching (MPLS) Management", RFC 3811, 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 @@ -2705,21 +2845,21 @@ [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005. [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in Support of Generalized Multi-Protocol Label Switching", RFC 4202, October 2005. [RFC4328] Papadimitriou, D., Ed., "Generalized MPLS Signalling Extensions for G.709 Optical Transport Networks - Control", draft-ietf-ccamp-gmpls-g709, work in progress. + Control", RFC4328, January 2006. [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", draft-ietf-ccamp-gmpls-lsr-mib, work in progress. [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual Conventions for Multiprotocol Label Switching (MPLS) Management", draft-ietf-ccamp-gmpls-tc-mib, work in progress. @@ -2727,20 +2867,22 @@ 12.2. Informative References [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 + [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized Multi-Protocol Label Switching (MPLS) Signaling - Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions", RFC 3472, January 2003. 13. Contact Information Thomas D. Nadeau Cisco Systems, Inc. 1414 Massachusetts Ave. @@ -2769,20 +2911,21 @@ Ed Harrison Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK Phone: +44 20 8366 1177 Email: ed.harrison@dataconnection.com 14. Intellectual Property Considerations + draft-ietf-ccamp-gmpls-te-mib-14.txt April 11, 2006 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.