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

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/