draft-ietf-ccamp-gmpls-te-mib-16.txt   rfc4802.txt 
Internet Working Group Thomas D. Nadeau, Ed. Network Working Group T. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Request for Comment: 4802 Cisco Systems, Inc.
Proposed Status: Standards Track Category: Standards Track A. Farrel, Ed.
Expires: March 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
February 2007
September 2006 Generalized Multiprotocol Label Switching (GMPLS)
Traffic Engineering Management Information Base
Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base
draft-ietf-ccamp-gmpls-te-mib-16.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months This document specifies an Internet standards track protocol for the
and may be updated, replaced, or obsoleted by other documents at any Internet community, and requests discussion and suggestions for
time. It is inappropriate to use Internet-Drafts as reference improvements. Please refer to the current edition of the "Internet
material or to cite them other than as "work in progress." Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The IETF Trust (2007).
http://www.ietf.org/shadow.html.
Abstract Abstract
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.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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 Internet-Standard Management Framework ............. 4 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 ..........................7
6. Cross-referencing to the gmplsLabelTable ............... 7 6. Cross-referencing to the gmplsLabelTable ........................7
7. Example of GMPLS Tunnel Setup .......................... 7 7. Example of GMPLS Tunnel Setup ...................................8
8. GMPLS Traffic Engineering MIB Module .................. 11 8. GMPLS Traffic Engineering MIB Module ...........................11
9. Security Considerations ............................... 47 9. Security Considerations ........................................47
10. Acknowledgments ...................................... 48 10. Acknowledgments ...............................................48
11. IANA Considerations .................................. 48 11. IANA Considerations ...........................................49
11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 48 11.1. IANA Considerations for GMPLS-TE-STD-MIB .................49
11.2. Dependence on IANA MIB Modules ..................... 49 11.2. Dependence on IANA MIB Modules ...........................49
11.2.1. IANA-GMPLS-TC-MIB Definition ..................... 49 11.2.1. IANA-GMPLS-TC-MIB Definition ......................50
12. References ........................................... 56 12. References ....................................................56
12.1. Normative References ............................... 56 12.1. Normative References .....................................56
12.2. Informative References ............................. 58 12.2. Informative References ...................................58
13. Contact Information .................................. 58
14. Intellectual Property Considerations ................. 59
15. Full Copyright Statement ............................. 59
1. Introduction 1. Introduction
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 modeling In particular, it describes managed objects for modeling Generalized
Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based Multiprotocol Label Switching (GMPLS) [RFC3945] based traffic
traffic engineering. The tables and objects defined in this document engineering (TE). The tables and objects defined in this document
extend those defined in the equivalent document for MPLS traffic extend those defined in the equivalent document for MPLS traffic
engineering [RFC3812], and management of GMPLS traffic engineering is engineering [RFC3812], and management of GMPLS traffic engineering is
built on management of MPLS traffic engineering. built on management of MPLS traffic engineering.
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 [RFC4803] for GMPLS-based traffic engineering
engineering configuration and management. configuration and management.
Comments should be made direct to the CCAMP mailing list at
ccamp@ops.ietf.org.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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, [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 Label Switched paths (LSPs) may be modeled and managed using
module [RFC3812]. the MPLS-TE-STD-MIB module [RFC3812].
LSRs may be migrated to model and manage their TE LSPs using the MIB Label Switching Routers (LSRs) may be migrated to model and manage
modules in this document in order to migrate the LSRs to GMPLS their TE LSPs using the MIB modules in this document in order to
support, or to take advantage of additional MIB objects defined in migrate the LSRs to GMPLS support, or to take advantage of additional
these MIB modules that are applicable to MPLS-TE. MIB objects defined in these MIB modules that are applicable to
MPLS-TE.
The GMPLS TE MIB module (GMPLS-TE-STD-MIB) defined in this document The GMPLS TE MIB module (GMPLS-TE-STD-MIB) defined in this document
extends the MPLS-TE-STD-MIB module [RFC3812] through a series of extends the MPLS-TE-STD-MIB module [RFC3812] through a series of
augmentations and sparse augmentations of the MIB tables. The only augmentations and sparse augmentations of the MIB tables. The only
additions are for support of GMPLS or to support the increased additions are for support of GMPLS or to support the increased
complexity of MPLS and GMPLS systems. complexity of MPLS and GMPLS systems.
In order to migrate from MPLS-TE-STD-MIB support to GMPLS-TE-STD-MIB In order to migrate from MPLS-TE-STD-MIB support to GMPLS-TE-STD-MIB
support an implementation needs only to add support for the support, an implementation needs only to add support for the
additional tables and objects defined in GMPLS-TE-STD-MIB. The additional tables and objects defined in GMPLS-TE-STD-MIB. The
gmplsTunnelLSPEncoding may be set to tunnelLspNotGmpls to allow an gmplsTunnelLSPEncoding may be set to tunnelLspNotGmpls to allow an
MPLS-TE LSP tunnel to benefit from the additional objects and tables MPLS-TE LSP tunnel to benefit from the additional objects and tables
of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols. of GMPLS-LSR-STD-MIB without supporting the GMPLS protocols.
The companion document for modeling and managing GMPLS based LSRs The companion document for modeling and managing GMPLS-based LSRs
[GMPLSLSRMIB] extends the MPLS-LSR-STD-MIB module [RFC3813] with the [RFC4803] extends the MPLS-LSR-STD-MIB module [RFC3813] with the same
same intentions. intentions.
Textual conventions are defined in [RFC3811] and the Textual conventions are defined in [RFC3811] and the IANA-GMPLS-TC-
IANA-GMPLS-TC-MIB MIB module. MIB module.
2. Terminology 2. Terminology
This document uses terminology from the MPLS architecture document This document uses terminology from the MPLS architecture document
[RFC3031], from the GMPLS architecture document [RFC3945], and from [RFC3031], from the GMPLS architecture document [RFC3945], and from
the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used
terms are described next. terms are described next.
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.
consists of in-segment(s) and/or out-segment(s) at the egress/ingress It consists of in-segment(s) and/or out-segment(s) at the
LSRs, each segment being associated with one GMPLS enabled interface. egress/ingress LSRs, each segment being associated with one GMPLS-
These are also referred to as tunnel segments. enabled interface. 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-
out-segments. The binding or interconnection between in-segments and segments. The binding or interconnection between in-segments and
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006 out-segments is performed using a cross-connect.
out-segments in performed using a cross-connect.
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 Switching Router MIB (MPLS-LSR-STD-MIB) [RFC3813], but see also the
GMPLS Label Switching Router MIB (GMPLS-LSR-STD-MIB) [GMPLSLSRMIB] GMPLS Label Switching Router MIB (GMPLS-LSR-STD-MIB) [RFC4803] for
for the GMPLS-specific extensions to these objects. the GMPLS-specific extensions to these objects.
3. The Internet-Standard 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).
skipping to change at page 4, line 35 skipping to change at page 4, line 32
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. Outline 4. Outline
Support for GMPLS traffic-engineered tunnels requires the following Support for GMPLS traffic-engineered tunnels requires the following
configuration. configuration.
- Setting up tunnels with appropriate MPLS configuration parameters - Setting up tunnels with appropriate MPLS configuration parameters
using [RFC3812]. using [RFC3812].
- Extending the tunnels with GMPLS configuration parameters.
- Configuring tunnel loose and strict source routed hops. - Extending the tunnel definitions with GMPLS configuration
parameters.
- Configuring loose and strict source routed tunnel hops.
These actions may need to be accompanied with corresponding actions These actions may need to be accompanied with corresponding actions
using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel using [RFC3813] and [RFC4803] to establish and configure tunnel
segments, if this is done manually. Also, the in-segment and segments, if this is done manually. Also, the in-segment and out-
out-segment performance tables, mplsInSegmentPerfTable and segment performance tables, mplsInSegmentPerfTable and
mplsOutSegmentPerfTable [RFC3813], should be used to determine mplsOutSegmentPerfTable [RFC3813], should be used to determine
performance of the tunnels and tunnel segments although it should be performance of the tunnels and tunnel segments, although it should be
noted that those tables may not be appropriate for measuring noted that those tables may not be appropriate for measuring
performance on some types of GMPLS links. performance on some types of GMPLS links.
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-16.txt September 2006 - Tunnel hop, actual tunnel hop, and computed tunnel 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
and gmplsTunnelErrorTable). - Performance and error reporting tables
(gmplsTunnelReversePerfTable 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
notification. notification.
- The GMPLS Tunnel Down Notification (gmplsTunnelDown) should be used - The GMPLS Tunnel Down Notification (gmplsTunnelDown) should be
for all GMPLS tunnels in place of the mplsTunnelDown notification used for all GMPLS tunnels in place of the mplsTunnelDown
defined in [RFC3812]. An implementation must not issue both the notification defined in [RFC3812]. An implementation must not
gmplsTunnelDown and the mplsTunnelDown notifications for the same issue both the gmplsTunnelDown and the mplsTunnelDown
event. As well as indicating that a tunnel has transitioned to notifications for the same event. As well as indicating that a
operational down state, this new notification indicates the cause tunnel has transitioned to operational down state, this new
of the failure. notification indicates the cause of the failure.
5. Brief Description of GMPLS TE MIB Objects 5. Brief Description of GMPLS TE MIB Objects
The objects described in this section support the functionality The objects described in this section support the functionality
described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables described in [RFC3473] and [RFC3472] for GMPLS tunnels. The tables
support both manually configured and signaled tunnels. support both manually configured and signaled tunnels.
5.1. gmplsTunnelTable 5.1. gmplsTunnelTable
The gmplsTunnelTable extends the MPLS traffic engineering MIB module The gmplsTunnelTable extends the MPLS traffic engineering MIB module
(MPLS-TE-STD-MIB [RFC3812]) to allow GMPLS tunnels to be created (MPLS-TE-STD-MIB [RFC3812]) to allow GMPLS tunnels to be created
between an LSR and a remote endpoint, and existing GMPLS tunnels to between an LSR and a remote endpoint, and existing GMPLS tunnels to
be reconfigured or removed. be reconfigured or removed.
Note that we only support point-to-point tunnel segments, although Note that we only support point-to-point tunnel segments, although
multi-point-to-point and point-to-multi-point connections are multipoint-to-point and point-to-multipoint connections are supported
supported by an LSR acting as a cross-connect. by an LSR acting as a cross-connect.
Each tunnel can thus have one out-segment originating at an LSR Each tunnel can thus have one out-segment originating at an LSR
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
the GMPLS-TE-STD-MIB module from changes (in particular, extensions) protect the GMPLS-TE-STD-MIB module from changes (in particular,
to the range of enumerations supported by the signaling protocols, extensions) to the range of enumerations supported by the signaling
these MIB objects use Textual Conventions with values maintained by protocols, these MIB objects use textual conventions with values
IANA. For further details, see the IANA Considerations section of maintained by IANA. For further details, see the IANA Considerations
this document. section of this document.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 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 the
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
traversed by a tunnel as reported by the signaling protocol after the traversed by a tunnel as reported by the signaling protocol after the
tunnel is setup. The support of this table is optional since not all tunnel is set up. The support of this table is optional since not
GMPLS signaling protocols support this feature. all GMPLS signaling protocols support this feature.
5.4. gmplsTunnelCHopTable 5.4. gmplsTunnelCHopTable
The gmplsTunnelCHopTable lists the actual hops computed by a The gmplsTunnelCHopTable lists the actual hops computed by a
constraint-based routing algorithm based on the gmplsTunnelHopTable. constraint-based routing algorithm based on the gmplsTunnelHopTable.
The support of this table is optional since not all implementations The support of this table is optional since not all implementations
support computation of hop lists using a constraint-based routing support computation of hop lists using a constraint-based routing
protocol. protocol.
5.5. gmplsTunnelErrorTable 5.5. gmplsTunnelErrorTable
The gmplsTunnelErrorTable provides access to information about the The gmplsTunnelErrorTable provides access to information about the
last error that occurred on each tunnel known about by the MIB. It last error that occurred on each tunnel known about by the MIB. It
indicates the nature of the error, when and how it was reported and indicates the nature of the error and when and how it was reported,
can give recovery advice through an admin string. and it can give recovery advice through an admin string.
5.6. gmplsTunnelReversePerfTable 5.6. gmplsTunnelReversePerfTable
gmplsTunnelReversePerfTable provides additional counters to measure The gmplsTunnelReversePerfTable provides additional counters to
the performance of bidirectional GMPLS tunnels in which packets are measure the performance of bidirectional GMPLS tunnels in which
visible. It supplements the counters in mplsTunnelPerfTable and packets are visible. It supplements the counters in
augments gmplsTunnelTable. mplsTunnelPerfTable and augments gmplsTunnelTable.
Note that not all counters may be appropriate or available for some Note that not all counters may be appropriate or available for some
types of tunnel. types of tunnel.
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.
For interfaces that operate faster than 20,000,000 bits/second, and For interfaces that operate faster than 20,000,000 bits/second,
slower than 650,000,000 bits/second, 32-bit packet counters MUST be and slower than 650,000,000 bits/second, 32-bit packet counters
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006 MUST be supported and 64-bit octet counters MUST be supported.
For interfaces that operate at 650,000,000 bits/second or faster,
supported and 64-bit octet counters MUST be supported. For 64-bit packet counters AND 64-bit octet counters MUST be
interfaces that operate at 650,000,000 bits/second or faster, 64-bit 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 [RFC4803] and provides a way to model labels in a GMPLS system where
where labels might not be simple 32 bit integers. labels might not be simple 32-bit integers.
The hop tables in this document (gmplsTunnelHopTable, The hop tables in this document (gmplsTunnelHopTable,
gmplsTunnelCHopTable and gmplsTunnelARHopTable) and the segment gmplsTunnelCHopTable, and gmplsTunnelARHopTable) and the segment
tables in the [RFC3813] (mplsInSegmentTable and mplsOutSegmentTable) tables in [RFC3813] (mplsInSegmentTable and mplsOutSegmentTable)
contain objects with 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 Furthermore, 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
integer is made available to represent the labels. This is achieved integer be made available to represent the labels. This is achieved
through the gmplsLabelTable contained in the GMPLS-LABEL-STD-MIB through the gmplsLabelTable contained in the GMPLS-LABEL-STD-MIB
[GMPLSLSRMIB]. [RFC4803].
The tables in this document and [RFC3813] that include objects with The tables in this document and [RFC3813] that include objects with
syntax MplsLabel also include companion objects that are row syntax MplsLabel also include companion objects that are row
pointers. If the row pointer is set to zeroDotZero (0.0) then object pointers. If the row pointer is set to zeroDotZero (0.0), then an
of syntax MplsLabel contains the label encoded as a 32-bit integer. object of syntax MplsLabel contains the label encoded as a 32-bit
But otherwise the row pointer indicates a row in another MIB table integer. But otherwise the row pointer indicates a row in another
that includes the label. In these cases, the row pointer may indicate MIB table that includes the label. In these cases, the row pointer
a row in the gmplsLabelTable. may indicate a row in the gmplsLabelTable.
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 MPLS-TE-STD-MIB [RFC3812], and a significant simplification
simplification in GMPLS systems that are limited to a single, simple 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
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
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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-
"head-end" LSR. end" LSR.
First in the mplsTunnelTable: First in the mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
mplsTunnelIngressLSRId = 192.0.2.1, mplsTunnelIngressLSRId = 192.0.2.1,
mplsTunnelEgressLSRId = 192.0.2.2, mplsTunnelEgressLSRId = 192.0.2.2,
mplsTunnelName = "My first tunnel", mplsTunnelName = "My first tunnel",
mplsTunnelDescr = "Here to there and back again", mplsTunnelDescr = "Here to there and back again",
mplsTunnelIsIf = true (1), mplsTunnelIsIf = true (1),
mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, mplsTunnelXCPointer = mplsXCIndex.3.0.0.12,
mplsTunnelSignallingProto = none (1), mplsTunnelSignallingProto = none (1),
skipping to change at page 9, line 4 skipping to change at page 9, line 20
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),
gmplsTunnelSendPathNotifyRecipientType = ipv4(1), gmplsTunnelSendPathNotifyRecipientType = ipv4(1),
gmplsTunnelSendPathNotifyRecipient = 'C0000201'H, gmplsTunnelSendPathNotifyRecipient = 'C0000201'H,
gmplsTunnelAdminStatusFlags = 0, gmplsTunnelAdminStatusFlags = 0,
gmplsTunnelExtraParamsPtr = 0.0 gmplsTunnelExtraParamsPtr = 0.0
} }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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)
} }
The next two instances of mplsTunnelHopEntry are used to denote the The next two instances of mplsTunnelHopEntry are used to denote the
hops this tunnel will take across the network. hops this tunnel will take across the network.
The following denotes the beginning of the network, or the first hop. The following denotes the beginning of the network, or the first hop
We have used the fictitious LSR identified by "192.0.2.1" as our in our example. We have used the fictitious LSR identified by
example head-end router. "192.0.2.1" as our head-end router.
In mplsTunnelHopTable: In mplsTunnelHopTable:
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 1, mplsTunnelHopIndex = 1,
mplsTunnelHopAddrType = ipV4 (1), mplsTunnelHopAddrType = ipv4(1),
mplsTunnelHopIpv4Addr = 192.0.2.1, mplsTunnelHopIpv4Addr = 192.0.2.1,
mplsTunnelHopIpv4PrefixLen = 9, mplsTunnelHopIpv4PrefixLen = 9,
mplsTunnelHopType = strict (1), mplsTunnelHopType = strict (1),
mplsTunnelHopRowStatus = createAndWait (5), mplsTunnelHopRowStatus = createAndWait (5),
} }
The following denotes the end of the network, or the last hop in our The following denotes the end of the network, or the last hop in our
example. We have used the fictitious LSR identified by example. We have used the fictitious LSR identified by "192.0.2.2"
"192.0.2.2" as our tail end router. 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,
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.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
An entry in the gmplsLabelTable is created first to include the An entry in the gmplsLabelTable is created first to include the
explicit label. Explicit Label.
In gmplsLabelTable: In gmplsLabelTable:
{ {
gmplsLabelInterface = 2, gmplsLabelInterface = 2,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
gmplsLabelSubindex = 0, gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3), gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210 gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4) gmplsLabelRowStatus = createAndGo(4)
} }
skipping to change at page 10, line 34 skipping to change at page 11, line 4
gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable (2, 1, 0) gmplsTunnelHopExplicitForwardLabelPtr = gmplsLabelTable (2, 1, 0)
gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable (2, 1, 0) gmplsTunnelHopExplicitReverseLabelPtr = gmplsLabelTable (2, 1, 0)
} }
The first hop is now activated: The first hop is now activated:
In mplsTunnelHopTable(1,1,1): In mplsTunnelHopTable(1,1,1):
{ {
mplsTunnelHopRowStatus = active (1) mplsTunnelHopRowStatus = active (1)
} }
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-16.txt September 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 reference to the following documents:
[RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], [RFC2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411],
[RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], and [RFC3471], [RFC3473], [RFC3477], [RFC3812], [RFC4001], and [RFC4202].
[RFC4202].
GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32 Unsigned32, Counter32, Counter64, zeroDotZero, Gauge32
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
TruthValue, TimeStamp, RowPointer TruthValue, TimeStamp, RowPointer
skipping to change at page 11, line 45 skipping to change at page 12, line 7
FROM MPLS-TE-STD-MIB -- RFC3812 FROM MPLS-TE-STD-MIB -- RFC3812
IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC, IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC,
IANAGmplsGeneralizedPidTC, IANAGmplsAdminStatusInformationTC 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
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 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
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
Comments about this document should be emailed direct to the Comments about this document should be emailed directly
CCAMP working group mailing list at ccamp@ops.ietf.org" to the CCAMP working group mailing list at
ccamp@ops.ietf.org."
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2006). This version of "Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC XXX; see the RFC itself for this MIB module is part of RFC 4802; see the RFC itself for
full legal notices. full legal notices.
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
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXX." "Initial version issued as part of RFC 4802."
::= { mplsStdMIB YYY } ::= { mplsStdMIB 13 }
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
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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelsActive OBJECT-TYPE gmplsTunnelsActive 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 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)."
skipping to change at page 13, line 28 skipping to change at page 13, line 31
SYNTAX SEQUENCE OF GmplsTunnelEntry SYNTAX SEQUENCE OF GmplsTunnelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gmplsTunnelTable sparsely extends 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 multipoint-to-point and point-to-multipoint
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.
The row status of an entry in this table is controlled by The row status of an entry in this table is controlled by the
mplsTunnelRowStatus in the corresponding entry in mplsTunnelRowStatus in the corresponding entry in the
mplsTunnelTable. When the corresponding mplsTunnelRowStatus has mplsTunnelTable. When the corresponding mplsTunnelRowStatus has
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." while 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.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
An entry can be created by a network administrator via SNMP SET An entry can be created by a network administrator via SNMP SET
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 }
skipping to change at page 15, line 4 skipping to change at page 15, line 13
(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'. 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', 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
terminating LSR." terminating LSR."
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 15, line 30 skipping to change at page 15, line 37
mplsTunnelSessionAttributes in order to determine the full set mplsTunnelSessionAttributes in order to determine the full set
of options to be signaled (for example SESSION_ATTRIBUTES flags of options to be signaled (for example SESSION_ATTRIBUTES flags
in RSVP-TE). The following describes these bitfields: in RSVP-TE). The following describes these bitfields:
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 IANAGmplsLSPEncodingTypeTC 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
IANAGmplsLSPEncodingTypeTC found in the IANA-GMPLS-TC-MIB IANAGmplsLSPEncodingTypeTC found in the IANA-GMPLS-TC-MIB
module." module."
DEFVAL { tunnelLspNotGmpls } DEFVAL { tunnelLspNotGmpls }
::= { gmplsTunnelEntry 3 } ::= { gmplsTunnelEntry 3 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelSwitchingType OBJECT-TYPE gmplsTunnelSwitchingType OBJECT-TYPE
SYNTAX IANAGmplsSwitchingTypeTC 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
IANAGmplsSwitchingTypeTC 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 gmplsTunnelLSPEncodingType
set to 'tunnelLspNotGmpls'." is not 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),
skipping to change at page 17, line 5 skipping to change at page 17, line 14
unprotected unprotected
This flag is set to indicate that the LSP should not use any This flag is set to indicate that the LSP should not use any
link layer protection. link layer protection.
shared shared
This flag is set to indicate that a shared link layer This flag 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-16.txt September 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 17, line 39 skipping to change at page 17, line 45
::= { gmplsTunnelEntry 5 } ::= { gmplsTunnelEntry 5 }
gmplsTunnelGPid OBJECT-TYPE gmplsTunnelGPid OBJECT-TYPE
SYNTAX IANAGmplsGeneralizedPidTC 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
IANAGmplsGeneralizedPidTC 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.
This object is only meaningful if gmplsTunnelLSPEncoding is not This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'." set to 'tunnelLspNotGmpls'."
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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 {
forward (0), forward (0),
bidirectional (1) bidirectional (1)
skipping to change at page 18, line 44 skipping to change at page 18, line 52
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value instructs the source node on how to perform path "This value instructs the source node on how to perform path
computation on the explicit route specified by the associated computation on the explicit route specified by the associated
entries in the gmplsTunnelHopTable. entries in the gmplsTunnelHopTable.
dynamicFull dynamicFull
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 Constrained
will calculate the remainder of the path. Shortest Path First (CSPF) 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-16.txt September 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 the gmplsTunnelTable for a
gmplsTunnelPathComp MUST be used and any corresponding tunnel, gmplsTunnelPathComp MUST be used and any
mplsTunnelHopEntryPathComp object in the mplsTunnelHopTable corresponding mplsTunnelHopEntryPathComp object in the
MUST be ignored and SHOULD not be set. mplsTunnelHopTable 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 This object should be ignored if the value of
is 'tunnelLspNotGmpls'." 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
skipping to change at page 20, line 5 skipping to change at page 20, line 14
"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
no upstream LSRs to which to send a Notify message. no upstream LSRs to which to send a Notify message.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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, gmplsTunnelUpstreamNotifyRecipientType. If this object is set to
the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to 0, the value of gmplsTunnelUpstreamNotifyRecipientType MUST be
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 11 } ::= { gmplsTunnelEntry 11 }
gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE gmplsTunnelSendResvNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 21, line 4 skipping to change at page 21, line 11
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-16.txt September 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 21, line 29 skipping to change at page 21, line 35
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the address of the downstream recipient for Notify "Indicates the address of the downstream 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 Resv information is typically received from an upstream LSR in a Resv
message. This object is only valid when signaling a tunnel using message. This object is only valid when signaling a tunnel using
RSVP. RSVP.
It is also not valid at the tail end of a tunnel since there are It is also not valid at the tail end of a tunnel since there are
no downstream LSRs to which to send a Notify message. no downstream 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
gmplsTunnelDownstreamNotifyRecipient. If this object is set to gmplsTunnelDownstreamNotifyRecipientType. If this object is set
0, the value of gmplsTunnelDownstreamNotifyRecipient MUST be set to 0, the value of gmplsTunnelDownstreamNotifyRecipientType MUST
to unknown(0)." be 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 15 } ::= { gmplsTunnelEntry 15 }
gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE gmplsTunnelSendPathNotifyRecipientType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 22, line 4 skipping to change at page 22, line 13
DESCRIPTION DESCRIPTION
"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
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
DESCRIPTION DESCRIPTION
"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
skipping to change at page 22, line 37 skipping to change at page 22, line 43
::= { gmplsTunnelEntry 17 } ::= { gmplsTunnelEntry 17 }
gmplsTunnelAdminStatusFlags OBJECT-TYPE gmplsTunnelAdminStatusFlags OBJECT-TYPE
SYNTAX IANAGmplsAdminStatusInformationTC 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
IANAGmplsAdminStatusInformationTC found in the IANAGmplsAdminStatusInformationTC found in the
IANA-GMPLS-TC-MIB 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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelExtraParamsPtr OBJECT-TYPE gmplsTunnelExtraParamsPtr OBJECT-TYPE
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,
resource usage). Such parameters can be supplied in an external Synchronous Optical Network (SONET) resource usage). Such
table and referenced from here. parameters can be supplied in an external 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 sparsely extends 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 the
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 the 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 in the
mplsTunnelHopTable. It is acceptable for some rows in mplsTunnelHopTable. It is acceptable for some rows in the
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.
The storage type for this entry is given by the value The storage type for this entry is given by the value
of mplsTunnelHopStorageType in the corresponding entry in the of mplsTunnelHopStorageType in the corresponding entry in the
mplsTunnelHopTable. mplsTunnelHopTable.
The row status of an entry in this table is controlled by The row status of an entry in this table is controlled by
mplsTunnelHopRowStatus in the corresponding entry in mplsTunnelHopRowStatus in the corresponding entry in the
mplsTunnelHopTable. That is, it is not permitted to create a row mplsTunnelHopTable. That is, it is not permitted to create a row
in this table, nor to modify an existing row, when the in this table, or to modify an existing row, when the
corresponding mplsTunnelHopRowStatus has value active(1)." corresponding mplsTunnelHopRowStatus has the 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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelHopEntry OBJECT-TYPE gmplsTunnelHopEntry OBJECT-TYPE
SYNTAX GmplsTunnelHopEntry SYNTAX GmplsTunnelHopEntry
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."
INDEX { INDEX {
mplsTunnelHopListIndex, mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex, mplsTunnelHopPathOptionIndex,
mplsTunnelHopIndex mplsTunnelHopIndex
} }
::= { gmplsTunnelHopTable 1 } ::= { gmplsTunnelHopTable 1 }
GmplsTunnelHopEntry ::= SEQUENCE { GmplsTunnelHopEntry ::= SEQUENCE {
skipping to change at page 24, line 45 skipping to change at page 25, line 4
forwardPresent (0), forwardPresent (0),
reversePresent (1) reversePresent (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence of labels indicated by the "This bitmask indicates the presence of labels indicated by the
gmplsTunnelHopExplicitForwardLabel or gmplsTunnelHopExplicitForwardLabel or
gmplsTunnelHopExplicitForwardLabelPtr, and gmplsTunnelHopExplicitForwardLabelPtr, and
gmplsTunnelHopExplicitReverseLabel or gmplsTunnelHopExplicitReverseLabel or
gmplsTunnelHopExplicitReverseLabel objects. gmplsTunnelHopExplicitReverseLabelPtr 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. 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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE gmplsTunnelHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
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
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
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 row in another MIB table (such as the gmplsLabelTable of
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 gmplsTunnelHopLabelStatuses object indicates that a If the gmplsTunnelHopLabelStatuses 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
gmplsTunnelHopExplicitForwardLabel object." gmplsTunnelHopExplicitForwardLabel object."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { gmplsTunnelHopEntry 3 } ::= { gmplsTunnelHopEntry 3 }
gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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 and Reverse Label is present and
gmplsTunnelHopExplicitReverseLabelPtr contains the value gmplsTunnelHopExplicitReverseLabelPtr contains the value
zeroDotZero, then the label to use on this this hop is found in zeroDotZero, then the label to use on this hop is found in
this object encoded as a 32-bit integer." this object encoded as a 32-bit integer."
::= { gmplsTunnelHopEntry 4 } ::= { gmplsTunnelHopEntry 4 }
gmplsTunnelHopExplicitReverseLabelPtr OBJECT-TYPE gmplsTunnelHopExplicitReverseLabelPtr OBJECT-TYPE
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
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
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
in the reverse direction. in the reverse direction.
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 sparsely extends 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
the labels currently in use for a GMPLS tunnel defined in indicate the labels currently in use for a GMPLS tunnel
mplsTunnelTable and gmplsTunnelTable, as reported by the defined in the mplsTunnelTable and gmplsTunnelTable, as
signaling protocol. It does not insert new hops, but does define reported by the signaling protocol. It does not insert
new values for hops defined in mplsTunnelARHopTable. new hops, but does define new values for hops defined in
the 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 in the
mplsTunnelARHopTable. It is acceptable for some rows in mplsTunnelARHopTable. It is acceptable for some rows in the
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.
Note that since the information necessary to build entries Note that since the information necessary to build entries
within this table is not provided by some signaling protocols within this table is not provided by some signaling protocols
and might not be returned in all cases of other signaling and might not be returned in all cases of other signaling
protocols, implementation of this table and mplsTunnelARHopTable protocols, implementation of this table and the
is optional. Furthermore, since the information in this table is mplsTunnelARHopTable is optional. Furthermore, since the
actually provided by the signaling protocol after the path has information in this table is actually provided by the
been set-up, the entries in this table are provided only for signaling protocol after the path has been set up, the entries
observation, and hence, all variables in this table are in this table are provided only for observation, and hence,
accessible exclusively as read-only." all variables in this table are 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
skipping to change at page 27, line 4 skipping to change at page 27, line 17
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
visible in mplsTunnelARHopEntry. An entry is created by the visible in mplsTunnelARHopEntry. An entry is created by the
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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 the mplsTunnelARHopTable (if the tables are supported and if
signaling protocol is recording actual route information) the 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
gmplsTunnelCHopTable. gmplsTunnelCHopTable.
Note that the recording of actual labels is distinct from the Note that the recording of actual labels is distinct from the
recording of the actual route in some signaling protocols. This recording of the actual route in some signaling protocols. This
feature is enabled using the gmplsTunnelAttributes object." feature is enabled using the gmplsTunnelAttributes object."
INDEX { INDEX {
mplsTunnelARHopListIndex, mplsTunnelARHopListIndex,
skipping to change at page 27, line 52 skipping to change at page 28, line 14
MAX-ACCESS read-only MAX-ACCESS read-only
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.
bit indicates that the label comes from the Global Label Space.
A clear bit indicates that this is a Per-Interface label. A
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
Global bit only has meaning if the corresponding Present bit is For the Global bits, a set bit indicates that the label comes
set." from the Global Label Space; a clear bit indicates that this is
a Per-Interface label. A Global bit only has meaning if the
corresponding Present bit is set."
::= { gmplsTunnelARHopEntry 1 } ::= { gmplsTunnelARHopEntry 1 }
gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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
forward label is present and Forward Label is present and
gmplsTunnelARHopExplicitForwardLabelPtr contains the value gmplsTunnelARHopExplicitForwardLabelPtr 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 within a 32-bit integer." object encoded as a 32-bit integer."
::= { gmplsTunnelARHopEntry 2 } ::= { gmplsTunnelARHopEntry 2 }
gmplsTunnelARHopExplicitForwardLabelPtr OBJECT-TYPE gmplsTunnelARHopExplicitForwardLabelPtr OBJECT-TYPE
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
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
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 forward direction. in the forward direction.
If the gmplsTunnelARHopLabelStatuses object indicates that a If the gmplsTunnelARHopLabelStatuses 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 in use on this hop is found in the zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExplicitForwardLabel object." gmplsTunnelARHopExplicitForwardLabel object."
::= { gmplsTunnelARHopEntry 3 } ::= { gmplsTunnelARHopEntry 3 }
gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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 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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE gmplsTunnelARHopExplicitReverseLabelPtr OBJECT-TYPE
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
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.
If the gmplsTunnelARHopLabelStatuses object indicates that a If the gmplsTunnelARHopLabelStatuses 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 in use on this hop is found in the zeroDotZero, then the label in use on this hop is found in the
gmplsTunnelARHopExplicitReverseLabel object." gmplsTunnelARHopExplicitReverseLabel object."
::= { gmplsTunnelARHopEntry 5 } ::= { gmplsTunnelARHopEntry 5 }
gmplsTunnelARHopProtection OBJECT-TYPE gmplsTunnelARHopProtection OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
localAvailable (0), localAvailable (0),
localInUse (1) localInUse (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 29, line 54 skipping to change at page 30, line 16
::= { 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 sparsely extends the "The gmplsTunnelCHopTable sparsely extends the
mplsTunnelCHopTable of MPLS-TE-STD-MIB. It is used to indicate mplsTunnelCHopTable of MPLS-TE-STD-MIB. It is used to indicate
additional information about the hops of a GMPLS tunnel defined additional information about the hops of a GMPLS tunnel defined
in mplsTunnelTable and gmplsTunnelTable, as computed by a in the mplsTunnelTable and gmplsTunnelTable, as computed by a
constraint-based routing protocol, based on the constraint-based routing protocol, based on the
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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 in the
mplsTunnelCHopTable. It is acceptable for some rows in mplsTunnelCHopTable. It is acceptable for some rows in the
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
entries within this table may not be supported by some LSRs, entries within this table may not be supported by some LSRs,
implementation of this table is optional. implementation of this table is optional.
Furthermore, since the information in this table is actually Furthermore, since the information in this table is actually
provided by a path computation component after the path has been provided by a path computation component after the path has been
computed, the entries in this table are provided only for computed, the entries in this table are provided only for
skipping to change at page 30, line 39 skipping to change at page 30, line 50
gmplsTunnelCHopEntry OBJECT-TYPE gmplsTunnelCHopEntry OBJECT-TYPE
SYNTAX GmplsTunnelCHopEntry SYNTAX GmplsTunnelCHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents additions to a computed tunnel "An entry in this table represents additions to a computed tunnel
hop visible in mplsTunnelCHopEntry. An entry is created by a hop visible in mplsTunnelCHopEntry. An entry is created by a
path computation component based on the hops specified in the path computation component based on the hops specified in the
corresponding mplsTunnelHopTable and gmplsTunnelHopTable. corresponding mplsTunnelHopTable and gmplsTunnelHopTable.
At a transit LSR this table (if the table is supported) MAY At a transit LSR, this table (if the table is supported) MAY
contain the path computed by path computation engine on (or on contain the path computed by a path computation engine on (or on
behalf of) the transit LSR." behalf of) the transit LSR."
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,
gmplsTunnelCHopExplicitReverseLabel Unsigned32, gmplsTunnelCHopExplicitReverseLabel Unsigned32,
gmplsTunnelCHopExplicitReverseLabelPtr RowPointer gmplsTunnelCHopExplicitReverseLabelPtr RowPointer
} }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence of labels indicated by the "This bitmask indicates the presence of labels indicated by the
skipping to change at page 31, line 19 skipping to change at page 31, line 32
reversePresent (1) reversePresent (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence of labels indicated by the "This bitmask indicates the presence of labels indicated by the
gmplsTunnelCHopExplicitForwardLabel or gmplsTunnelCHopExplicitForwardLabel or
gmplsTunnelCHopExplicitForwardLabelPtr and gmplsTunnelCHopExplicitForwardLabelPtr and
gmplsTunnelCHopExplicitReverseLabel or gmplsTunnelCHopExplicitReverseLabel or
gmplsTunnelCHopExplicitReverseLabelPtr objects. gmplsTunnelCHopExplicitReverseLabelPtr objects.
A set bit indicates that a label is present for this hop in the A set bit indicates that a label is present for this hop in the
route thus allowing zero to be a valid label value." route, thus allowing zero to be a valid label value."
::= { gmplsTunnelCHopEntry 1 } ::= { gmplsTunnelCHopEntry 1 }
gmplsTunnelCHopExplicitForwardLabel OBJECT-TYPE gmplsTunnelCHopExplicitForwardLabel 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
forward label is present and Forward Label is present and
gmplsTunnelCHopExplicitForwardLabelPtr contains the value gmplsTunnelCHopExplicitForwardLabelPtr contains the value
zeroDotZero, then the label to use on this hop is found in this zeroDotZero, then the label to use on this hop is found in this
object encoded within a 32-bit integer." object encoded as a 32-bit integer."
::= { gmplsTunnelCHopEntry 2 } ::= { gmplsTunnelCHopEntry 2 }
gmplsTunnelCHopExplicitForwardLabelPtr OBJECT-TYPE gmplsTunnelCHopExplicitForwardLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
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
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
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."
::= { gmplsTunnelCHopEntry 3 } ::= { gmplsTunnelCHopEntry 3 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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
zeroDotZero, then the label to use on this hop is found in this zeroDotZero, then the label to use on this hop is found in this
object encoded as a 32-bit integer." object encoded as a 32-bit integer."
::= { gmplsTunnelCHopEntry 4 } ::= { gmplsTunnelCHopEntry 4 }
gmplsTunnelCHopExplicitReverseLabelPtr OBJECT-TYPE gmplsTunnelCHopExplicitReverseLabelPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
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, 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
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 provide
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."
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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelReversePerfEntry OBJECT-TYPE gmplsTunnelReversePerfEntry OBJECT-TYPE
SYNTAX GmplsTunnelReversePerfEntry SYNTAX GmplsTunnelReversePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for every "An entry in this table is created by the LSR for every
bidirectional GMPLS tunnel where packets are visible to the bidirectional GMPLS tunnel where packets are visible to the
LSR." LSR."
AUGMENTS { gmplsTunnelEntry } AUGMENTS { gmplsTunnelEntry }
skipping to change at page 33, line 33 skipping to change at page 33, line 48
} }
gmplsTunnelReversePerfPackets OBJECT-TYPE gmplsTunnelReversePerfPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of packets forwarded on the tunnel in the reverse "Number of packets forwarded on the tunnel in the reverse
direction if it is bidirectional. direction if it is bidirectional.
This object should represents the 32-bit value of the least This object represents the 32-bit value of the least
significant part of the 64-bit value if both significant part of the 64-bit value if both
gmplsTunnelReversePerfHCPackets and this object are returned. gmplsTunnelReversePerfHCPackets and this object are returned.
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
noSuchInstance." noSuchInstance."
::= { 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.
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
noSuchInstance." noSuchInstance."
::= { gmplsTunnelReversePerfEntry 2 } ::= { gmplsTunnelReversePerfEntry 2 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelReversePerfErrors OBJECT-TYPE gmplsTunnelReversePerfErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of errored packets received on the tunnel in the reverse "Number of errored packets received on the tunnel in the reverse
direction if it is bidirectional. For links that do not direction if it is bidirectional. For links that do not
transport packets, this packet counter cannot be maintained. For transport packets, this packet counter cannot be maintained. For
such links, this value will return a noSuchInstance." such links, this value will return noSuchInstance."
::= { gmplsTunnelReversePerfEntry 3 } ::= { gmplsTunnelReversePerfEntry 3 }
gmplsTunnelReversePerfBytes OBJECT-TYPE gmplsTunnelReversePerfBytes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Number of bytes forwarded on the tunnel in the reverse direction "Number of bytes forwarded on the tunnel in the reverse direction
if it is bidirectional. if it is bidirectional.
This object should represents the 32-bit value of the least This object represents the 32-bit value of the least
significant part of the 64-bit value if both significant part of the 64-bit value if both
gmplsTunnelReversePerfHCBytes and this object are returned. gmplsTunnelReversePerfHCBytes and this object are returned.
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
noSuchInstance." noSuchInstance."
::= { gmplsTunnelReversePerfEntry 4 } ::= { gmplsTunnelReversePerfEntry 4 }
gmplsTunnelReversePerfHCBytes OBJECT-TYPE gmplsTunnelReversePerfHCBytes 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 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
noSuchInstance." noSuchInstance."
::= { gmplsTunnelReversePerfEntry 5 } ::= { gmplsTunnelReversePerfEntry 5 }
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
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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."
::= { gmplsTeObjects 6 } ::= { gmplsTeObjects 6 }
gmplsTunnelErrorEntry OBJECT-TYPE gmplsTunnelErrorEntry OBJECT-TYPE
SYNTAX GmplsTunnelErrorEntry SYNTAX GmplsTunnelErrorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by the LSR for every tunnel "An entry in this table is created by the LSR for every tunnel
where error information is visible to the LSR. where error information is visible to the LSR.
Note that systems which read the objects in this table one Note that systems that read the objects in this table one at
at a time should read gmplsTunnelErrorLastTime prior to a time and do not perform atomic operations to read entire
the first object and after reading the last object of this instantiated table rows at once, should, for each conceptual
table to ensure that no additional errors occurred." column with valid data, read gmplsTunnelErrorLastTime
prior to the other objects in the row and again subsequent to
reading the last object of the row. They should verify that
the value of gmplsTunnelErrorLastTime did not change and
thereby ensure that all data read belongs to the same error
event."
AUGMENTS { mplsTunnelEntry } AUGMENTS { mplsTunnelEntry }
::= { gmplsTunnelErrorTable 1 } ::= { gmplsTunnelErrorTable 1 }
GmplsTunnelErrorEntry ::= SEQUENCE { GmplsTunnelErrorEntry ::= SEQUENCE {
gmplsTunnelErrorLastErrorType INTEGER, gmplsTunnelErrorLastErrorType INTEGER,
gmplsTunnelErrorLastTime TimeStamp, gmplsTunnelErrorLastTime TimeStamp,
gmplsTunnelErrorReporterType InetAddressType, gmplsTunnelErrorReporterType InetAddressType,
gmplsTunnelErrorReporter InetAddress, gmplsTunnelErrorReporter InetAddress,
gmplsTunnelErrorCode Unsigned32, gmplsTunnelErrorCode Unsigned32,
gmplsTunnelErrorSubcode Unsigned32, gmplsTunnelErrorSubcode Unsigned32,
skipping to change at page 36, line 4 skipping to change at page 36, line 30
noError (0), noError (0),
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
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
DESCRIPTION DESCRIPTION
"The nature of the last error. Provides interpretation context "The nature of the last error. Provides interpretation context
for gmplsTunnelErrorProtocolCode and for gmplsTunnelErrorProtocolCode and
gmplsTunnelErrorProtocolSubcode. gmplsTunnelErrorProtocolSubcode.
A value of noError (0) shows that there is no error associated A value of noError (0) shows that there is no error associated
with this tunnel and means that the other objects in this table with this tunnel and means that the other objects in this table
entry have no meaning. entry (conceptual row) have no meaning.
A value of unknown (1) shows that there is an error but that no A value of unknown (1) shows that there is an error but that no
additional information about the cause is known. The error may additional information about the cause is known. The error may
have been received in a signaled message or generated locally. have been received in a signaled message or generated locally.
A value of protocol (2) or pathComputation (3) indicates the A value of protocol (2) or pathComputation (3) indicates the
cause of an error and identifies an error that has been received cause of an error and identifies an error that has been received
through signaling or will itself be signaled. through signaling or will itself be signaled.
A value of localConfiguration (4), localResources (5) or A value of localConfiguration (4), localResources (5) or
localOther (6) identifies an error which has been detected localOther(6) identifies an error that has been detected
by the local node, but which will not be reported through by the local node but that will not be reported through
signaling." signaling."
::= { gmplsTunnelErrorEntry 1 } ::= { gmplsTunnelErrorEntry 1 }
gmplsTunnelErrorLastTime OBJECT-TYPE gmplsTunnelErrorLastTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 not valid and should be 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 }
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."
::= { gmplsTunnelErrorEntry 3 } ::= { gmplsTunnelErrorEntry 3 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelErrorReporter OBJECT-TYPE gmplsTunnelErrorReporter OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the node reporting the last error, or the address "The address of the node reporting the last error, or the address
of the resource (such as an interface) associated with the of the resource (such as an interface) associated with the
error. error.
If gmplsTunnelErrorLastErrorType has the value noError (0), then If gmplsTunnelErrorLastErrorType has the value noError (0), then
this object is ignored. this object is not valid and should be ignored.
If gmplsTunnelErrorLastErrorType has the value unknown (1), If gmplsTunnelErrorLastErrorType has the value unknown (1),
localConfiguration (4), localResources (5), or localOther (6) localConfiguration(4), localResources(5), or localOther(6),
this object MAY contain a zero value. this object MAY contain a zero value.
This object should be interpreted in the context of the value of This object should be interpreted in the context of the value of
the object gmplsTunnelErrorReporterType." the object gmplsTunnelErrorReporterType."
REFERENCE REFERENCE
"1. Textual Conventions for Internet Network Addresses, RFC 4001, "1. Textual Conventions for Internet Network Addresses, RFC 4001,
section 4, Usage Hints." section 4, Usage Hints."
::= { gmplsTunnelErrorEntry 4 } ::= { gmplsTunnelErrorEntry 4 }
gmplsTunnelErrorCode OBJECT-TYPE gmplsTunnelErrorCode OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
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
skipping to change at page 37, line 38 skipping to change at page 38, line 16
gmplsTunnelErrorCode OBJECT-TYPE gmplsTunnelErrorCode OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
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 signaling protocol be interpreted in the context of the signaling protocol
identified by the mplsTunnelSignallingProto object." identified by the mplsTunnelSignallingProto object."
REFERENCE REFERENCE
"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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelErrorSubcode OBJECT-TYPE gmplsTunnelErrorSubcode OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The secondary error code associated with the last error and the "The secondary error code associated with the last error and the
protocol used to signal this tunnel. This value is interpreted protocol used to signal this tunnel. This value is interpreted
in the context of the value of gmplsTunnelErrorCode. in the context of the value of gmplsTunnelErrorCode.
If the value of gmplsTunnelErrorLastErrorType is noError (0) the If the value of gmplsTunnelErrorLastErrorType is noError(0), the
value of this object should be 0 and should be ignored." value of this object should be 0 and should be ignored."
REFERENCE REFERENCE
"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 6 } ::= { gmplsTunnelErrorEntry 6 }
gmplsTunnelErrorTLVs OBJECT-TYPE gmplsTunnelErrorTLVs OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..65535)) SYNTAX OCTET STRING (SIZE(0..65535))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 38, line 47 skipping to change at page 39, line 21
"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
"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 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
-- --
-- Notifications -- Notifications
-- --
gmplsTunnelDown NOTIFICATION-TYPE gmplsTunnelDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
mplsTunnelAdminStatus, mplsTunnelAdminStatus,
mplsTunnelOperStatus, mplsTunnelOperStatus,
gmplsTunnelErrorLastErrorType, gmplsTunnelErrorLastErrorType,
gmplsTunnelErrorReporterType, gmplsTunnelErrorReporterType,
gmplsTunnelErrorReporter, gmplsTunnelErrorReporter,
gmplsTunnelErrorCode, gmplsTunnelErrorCode,
gmplsTunnelErrorSubcode gmplsTunnelErrorSubcode
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a mplsTunnelOperStatus "This notification is generated when an mplsTunnelOperStatus
object for a tunnel in the gmplsTunnelTable is about to enter object for a tunnel in the gmplsTunnelTable is about to enter
the down state from some other state (but not from the the down state from some other state (but not from the
notPresent state). This other state is indicated by the notPresent state). This other state is indicated by the
included value of mplsTunnelOperStatus. included value of mplsTunnelOperStatus.
The objects in this notification provide additional error The objects in this notification provide additional error
information that indicates the reason why the tunnel has information that indicates the reason why the tunnel has
transitioned down. transitioned to down(2).
Note that an implementation MUST only issue one of Note that an implementation MUST only issue one of
mplsTunnelDown and gmplsTunnelDown for any single event on a mplsTunnelDown and gmplsTunnelDown for any single event on a
single tunnel. If the tunnel has an entry in gmplsTunnelTable single tunnel. If the tunnel has an entry in the
an implementation SHOULD use gmplsTunnelDown for all tunnel gmplsTunnelTable, an implementation SHOULD use gmplsTunnelDown
down events and SHOULD NOT use mplsTunnelDown. for all tunnel-down events and SHOULD NOT use mplsTunnelDown.
This notification is subject to the control of the This notification is subject to the control of
mplsTunnelNotificationEnable. When that object is set to mplsTunnelNotificationEnable. When that object is set
false(2) then the notification must not be issued. to 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
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 notifications in the MPLS-TE-STD-MIB and of all notifications 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."
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering "1. Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB), RFC 3812." (TE) Management Information Base (MIB), RFC 3812."
::= { gmplsTeNotifications 1 } ::= { gmplsTeNotifications 1 }
gmplsTeGroups gmplsTeGroups
OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } OBJECT IDENTIFIER ::= { gmplsTeConformance 1 }
gmplsTeCompliances gmplsTeCompliances
OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } OBJECT IDENTIFIER ::= { gmplsTeConformance 2 }
skipping to change at page 40, line 27 skipping to change at page 40, line 50
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
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 MODULE MPLS-TE-STD-MIB -- The MPLS-TE-STD-MIB, RFC3812
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsTunnelGroup, mplsTunnelGroup,
mplsTunnelScalarGroup mplsTunnelScalarGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsTunnelGroup, gmplsTunnelGroup,
gmplsTunnelScalarGroup gmplsTunnelScalarGroup
} }
GROUP gmplsTunnelSignaledGroup GROUP gmplsTunnelSignaledGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support signaled "This group is mandatory for devices that 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)."
GROUP gmplsTunnelOptionalGroup GROUP gmplsTunnelOptionalGroup
DESCRIPTION DESCRIPTION
"Objects in this group are optional." "Objects in this group are optional."
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
GROUP gmplsTeNotificationGroup GROUP gmplsTeNotificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those implementations which can "This group is mandatory for those implementations that can
implement the notifications contained in this group." 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
} }
GROUP gmplsTunnelSignaledGroup GROUP gmplsTunnelSignaledGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support signaled "This group is mandatory for devices that 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)."
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 that can
implement the notifications contained in this group." implement the notifications contained in this group."
OBJECT gmplsTunnelUnnumIf OBJECT gmplsTunnelUnnumIf
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 42, line 49 skipping to change at page 43, line 29
"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."
OBJECT gmplsTunnelUpstreamNotifyRecipientType OBJECT gmplsTunnelUpstreamNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required." is required."
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
OBJECT gmplsTunnelUpstreamNotifyRecipient OBJECT gmplsTunnelUpstreamNotifyRecipient
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes." unknown(0), ipv4(1), and ipv6(2) sizes."
OBJECT gmplsTunnelSendResvNotifyRecipientType OBJECT gmplsTunnelSendResvNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required." is required."
OBJECT gmplsTunnelSendResvNotifyRecipient OBJECT gmplsTunnelSendResvNotifyRecipient
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes." unknown(0), ipv4(1), and ipv6(2) sizes."
OBJECT gmplsTunnelDownstreamNotifyRecipientType OBJECT gmplsTunnelDownstreamNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required." is required."
OBJECT gmplsTunnelDownstreamNotifyRecipient OBJECT gmplsTunnelDownstreamNotifyRecipient
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes." unknown(0), ipv4(1), and ipv6(2) sizes."
OBJECT gmplsTunnelSendPathNotifyRecipientType OBJECT gmplsTunnelSendPathNotifyRecipientType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required." is required."
OBJECT gmplsTunnelSendPathNotifyRecipient OBJECT gmplsTunnelSendPathNotifyRecipient
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes." unknown(0), ipv4(1), and ipv6(2) sizes."
OBJECT gmplsTunnelAdminStatusFlags OBJECT gmplsTunnelAdminStatusFlags
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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
OBJECT gmplsTunnelHopExplicitForwardLabel OBJECT gmplsTunnelHopExplicitForwardLabel
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 44, line 47 skipping to change at page 45, line 24
-- 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 OBJECT gmplsTunnelErrorReporterType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required." is required."
OBJECT gmplsTunnelErrorReporter OBJECT gmplsTunnelErrorReporter
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION "An implementation is only required to support DESCRIPTION "An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2)." unknown(0), ipv4(1), and ipv6(2)."
::= { gmplsTeCompliances 2 } ::= { gmplsTeCompliances 2 }
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelGroup OBJECT-GROUP gmplsTunnelGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelDirection, gmplsTunnelDirection,
gmplsTunnelReversePerfPackets, gmplsTunnelReversePerfPackets,
gmplsTunnelReversePerfHCPackets, gmplsTunnelReversePerfHCPackets,
gmplsTunnelReversePerfErrors, gmplsTunnelReversePerfErrors,
gmplsTunnelReversePerfBytes, gmplsTunnelReversePerfBytes,
gmplsTunnelReversePerfHCBytes, gmplsTunnelReversePerfHCBytes,
gmplsTunnelErrorLastErrorType, gmplsTunnelErrorLastErrorType,
skipping to change at page 46, line 4 skipping to change at page 46, line 33
gmplsTunnelSendResvNotifyRecipient, gmplsTunnelSendResvNotifyRecipient,
gmplsTunnelDownstreamNotifyRecipientType, gmplsTunnelDownstreamNotifyRecipientType,
gmplsTunnelDownstreamNotifyRecipient, gmplsTunnelDownstreamNotifyRecipient,
gmplsTunnelSendPathNotifyRecipientType, gmplsTunnelSendPathNotifyRecipientType,
gmplsTunnelSendPathNotifyRecipient, gmplsTunnelSendPathNotifyRecipient,
gmplsTunnelAdminStatusFlags, gmplsTunnelAdminStatusFlags,
gmplsTunnelHopLabelStatuses, gmplsTunnelHopLabelStatuses,
gmplsTunnelHopExplicitForwardLabel, gmplsTunnelHopExplicitForwardLabel,
gmplsTunnelHopExplicitForwardLabelPtr, gmplsTunnelHopExplicitForwardLabelPtr,
gmplsTunnelHopExplicitReverseLabel, gmplsTunnelHopExplicitReverseLabel,
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
gmplsTunnelHopExplicitReverseLabelPtr gmplsTunnelHopExplicitReverseLabelPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects needed to implement signaled tunnels." "Objects needed to implement signaled tunnels."
::= { gmplsTeGroups 2 } ::= { gmplsTeGroups 2 }
gmplsTunnelScalarGroup OBJECT-GROUP gmplsTunnelScalarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelsConfigured, gmplsTunnelsConfigured,
gmplsTunnelsActive gmplsTunnelsActive
} }
skipping to change at page 47, line 4 skipping to change at page 47, line 33
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 5 } ::= { gmplsTeGroups 5 }
END END
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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 MPLS-TE-STD-MIB [RFC3812] are potentially useful for
for monitoring of MPLS and GMPLS tunnels. These MIB modules can also monitoring of MPLS and GMPLS tunnels. These MIB modules can also be
be used for configuration of certain objects, and anything that can used for configuration of certain objects, and anything that can be
be configured can be incorrectly configured, with potentially configured can be incorrectly configured, with potentially disastrous
disastrous results. results.
There are a number of management objects defined in these MIB modules There are a number of management objects defined in these MIB modules
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain
objects to provision GMPLS tunnels interfaces at their ingress objects to provision GMPLS tunnels interfaces at their ingress
LSRs. Unauthorized write access to objects in these tables, could LSRs. Unauthorized write access to objects in these tables could
result in disruption of traffic on the network. This is especially result in disruption of traffic on the network. This is
true if a tunnel has already been established. especially true if a tunnel has already been established.
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, and the gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, and
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
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.
if the network itself is secure (for example by using IPsec), even Even if the network itself is secure (for example by using IPsec),
then, there is no control as to who on the secure network is allowed even then, there is no control as to who on the secure network is
to access and GET/SET (read/change/create/delete) the objects in allowed to access and GET/SET (read/change/create/delete) the objects
these MIB modules. in 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),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. Acknowledgments 10. Acknowledgments
This document is a product of the CCAMP Working Group. This document is a product of the CCAMP Working Group.
This document extends [RFC3812]. The authors would like to express This document extends [RFC3812]. The authors would like to express
their gratitude to all those who worked on that earlier MIB document. their gratitude to all those who worked on that earlier MIB document.
Thanks also to Tony Zinicola and Jeremy Crossen for their valuable Thanks also to Tony Zinicola and Jeremy Crossen for their valuable
contributions during an early implementation, and to Lars Eggert, contributions during an early implementation, and to Lars Eggert,
Baktha Muralidharan, Tom Petch, Dan Romascanu, Dave Thaler and Baktha Muralidharan, Tom Petch, Dan Romascanu, Dave Thaler, and Bert
Bert Wijnen for their review comments. Wijnen for their review comments.
Special thanks to Joan Cucchiara and Len Nieman for their help with Special thanks to Joan Cucchiara and Len Nieman for their help with
compilation issues. compilation issues.
Joan Cucchiara provided a helpful and very thorough MIB Doctor Joan Cucchiara provided a helpful and very thorough MIB Doctor
review. review.
11. IANA Considerations 11. IANA Considerations
IANA is requested to root MIB objects in the MIB modules contained in IANA has rooted MIB objects in the MIB modules contained in this
this document according to the sections below. document according to the sections below.
11.1. IANA Considerations for GMPLS-TE-STD-MIB 11.1. IANA Considerations for GMPLS-TE-STD-MIB
IANA is requested to root MIB objects in the GMPLS-TE-STD-MIB module IANA has rooted MIB objects in the GMPLS-TE-STD-MIB module contained
contained in this document under the mplsStdMIB subtree. in this document under the mplsStdMIB subtree.
Upon approval of this document, the IANA will make the following IANA has made the following assignments in the "NETWORK MANAGEMENT
assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located PARAMETERS" registry located at http://www.iana.org/assignments/
at http://www.iana.org/assignments/smi-numbers in table: smi-numbers in table:
...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166) ...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
Decimal Name References Decimal Name References
------- ----- ---------- ------- ----- ----------
TBD+3 GMPLS-LSR-STD-MIB [RFC-ccamp-gmpls-lsr-mib] 13 GMPLS-TE-STD-MIB [RFC4802]
In the future, GMPLS related standards track MIB modules should be
rooted under the mplsStdMIB (sic) subtree. IANA has been requested to
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
manage that namespace in the SMI Numbers registry [RFC3811]. New In the future, GMPLS-related standards-track MIB modules should be
rooted under the mplsStdMIB (sic) subtree. IANA has been requested
to manage that namespace in the SMI Numbers registry [RFC3811]. New
assignments can only be made via a Standards Action as specified in assignments can only be made via a Standards Action as specified in
[RFC2434]. [RFC2434].
11.2. Dependence on IANA MIB Modules 11.2. Dependence on IANA MIB Modules
Three MIB objects in the GMPLS-LSR-STD-MIB module defined in this Three MIB objects in the GMPLS-TE-STD-MIB module defined in this
document (gmplsTunnelLSPEncoding, gmplsTunnelSwitchingType, and document (gmplsTunnelLSPEncoding, gmplsTunnelSwitchingType, and
gmplsTunnelGPid) use textual conventions imported from the gmplsTunnelGPid) use textual conventions imported from the IANA-
IANA-GMPLS-TC-MIB module. The purpose of defining these textual GMPLS-TC-MIB module. The purpose of defining these textual
conventions in a separate MIB module is to allow additional values to conventions in a separate MIB module is to allow additional values to
be defined without having to issue a new version of this document. be defined without having to issue a new version of this document.
The Internet Assigned Numbers Authority (IANA) is responsible for the The Internet Assigned Numbers Authority (IANA) is responsible for the
assignment of all Internet numbers; it will administer the values assignment of all Internet numbers; it will administer the values
associated with these textual conventions. associated with these textual conventions.
The rules for additions or changes to the IANA-GMPLS-TC-MIB are The rules for additions or changes to IANA-GMPLS-TC-MIB are outlined
outlined in the DESCRIPTION clause associated with its in the DESCRIPTION clause associated with its MODULE-IDENTITY
MODULE-IDENTITY statement. statement.
The current versions of the IANA-GMPLS-TC-MIB can be accessed from The current version of IANA-GMPLS-TC-MIB can be accessed from the
the IANA home page at: "http://www.iana.org/". IANA home page at: http://www.iana.org/.
11.2.1. IANA-GMPLS-TC-MIB Definition 11.2.1. IANA-GMPLS-TC-MIB Definition
This is a temporary section intended to supply the base definition of This section provides the base definition of the IANA GMPLS TC MIB
an IANA MIB module. The normal procedure is that this MIB module is module. This MIB module is under the direct control of IANA. Please
moved into the direct control of IANA, at which time this section see the most updated version of this MIB at
should be deleted from this document. <http://www.iana.org/assignments/ianagmplstc-mib>.
IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module
specified in this document as { mib-2 ZZZ }.
This MIB makes reference to the following documents: [RFC2578],
[RFC2579], [RFC3471], [RFC3473], [RFC4202], [RFC4328], and [RFC4783].
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006 IANA assigned an OID to the IANA-GMPLS-TC-MIB module specified in
this document as { mib-2 152 }.
IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC2578 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC2578
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579 TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC2579
ianaGmpls MODULE-IDENTITY ianaGmpls MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 GMT
ORGANIZATION ORGANIZATION
"IANA" "IANA"
CONTACT-INFO CONTACT-INFO
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Postal: USC/Information Sciences Institute Postal: 4676 Admiralty Way, Suite 330
4676 Admiralty Way, Marina del Rey, CA 90292 Marina del Rey, CA 90292
Tel: +1 310 822 1511 Tel: +1 310 823 9358
E-Mail: iana@isi.edu" E-Mail: iana@iana.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2006). The initial version "Copyright (C) The IETF Trust (2007). The initial version
of this MIB module was published in RFC WWW. For full legal of this MIB module was published in RFC 4802. 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"
REVISION REVISION
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC WWW." "Initial version issued as part of RFC 4802."
::= { mib-2 ZZZ } ::= { mib-2 152 }
IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION IANAGmplsLSPEncodingTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to represent and control "This type 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.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
This textual convention is strongly tied to the LSP This textual convention is strongly tied to the LSP
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 LSP Encoding Types
Encoding Types sub-registry. sub-registry.
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.)
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@iana.org)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section Signaling Functional Description, RFC 3471, section
3.1.1." 3.1.1.
2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, RFC 4328, section 3.1.1."
SYNTAX INTEGER { SYNTAX INTEGER {
tunnelLspNotGmpls (0), -- GMPLS is not in use tunnelLspNotGmpls (0), -- GMPLS is not in use
tunnelLspPacket (1), -- Packet tunnelLspPacket (1), -- Packet
tunnelLspEthernet (2), -- Ethernet tunnelLspEthernet (2), -- Ethernet
tunnelLspAnsiEtsiPdh (3), -- PDH tunnelLspAnsiEtsiPdh (3), -- PDH
-- the value 4 is deprecated -- the value 4 is deprecated
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
skipping to change at page 52, line 5 skipping to change at page 52, line 15
tunnelOpticalChannel (13) -- Optical Channel tunnelOpticalChannel (13) -- Optical Channel
} }
IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to represent and "This type 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.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
This textual convention is strongly tied to the Switching This textual convention is strongly tied to the Switching
Types sub-registry of the GMPLS Signaling Parameters Types sub-registry of the GMPLS Signaling Parameters
registry managed by IANA. Values should be assigned by IANA registry managed by IANA. Values should be assigned by
in step with the Switching Types sub-registry and using the IANA in step with the Switching Types sub-registry and
same registry management rules. However, the actual values using the same registry management rules. However, the
used in this textual convention are solely within the actual values used in this textual convention are solely
purview of IANA and do not necessarily match the values in within the purview of IANA and do not necessarily match
the values in the Switching Types sub-registry. the values in the Switching Types sub-registry.
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.)
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@iana.org)."
REFERENCE REFERENCE
"1. Routing Extensions in Support of Generalized "1. Routing Extensions in Support of Generalized
Multi-Protocol Label Switching, RFC 4202, section 2.4. Multi-Protocol Label Switching, RFC 4202, section 2.4.
2. Generalized Multi-Protocol Label Switching (GMPLS) 2. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section Signaling Functional Description, RFC 3471, section
3.1.1." 3.1.1."
SYNTAX INTEGER { SYNTAX INTEGER {
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
skipping to change at page 52, line 43 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
} }
IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION IANAGmplsGeneralizedPidTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used to represent and control the LSP "This data type 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.
This textual convention is strongly tied to the Generalized This textual convention is strongly tied to the Generalized
PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters PIDs (G-PID) sub-registry of the GMPLS Signaling Parameters
registry managed by IANA. Values should be assigned by IANA registry managed by IANA. Values should be assigned by
in step with the Generalized PIDs (G-PID) sub-registry and IANA in step with the Generalized PIDs (G-PID) sub-registry
using the same registry management rules. However, the and using the same registry management rules. However, the
actual values used in this textual convention are solely actual values used in this textual convention are solely
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
within the purview of IANA and do not necessarily match the within the purview of IANA and do not necessarily match the
values in the values in the Generalized PIDs (G-PID) values in the Generalized PIDs (G-PID) sub-registry.
sub-registry.
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.)
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@iana.org)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471, section Signaling Functional Description, RFC 3471, section
3.1.1. 3.1.1.
" 2. Generalized MPLS Signalling Extensions for G.709 Optical
Transport Networks Control, RFC 4328, section 3.1.3."
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),
asynchDS2T2(10), asynchDS2T2(10),
bitsynchDS2T2(11), bitsynchDS2T2(11),
skipping to change at page 54, line 4 skipping to change at page 54, line 17
reservedByRFC3471third(21), 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),
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
posScramble32BitCrc(31), posScramble32BitCrc(31),
atm(32), atm(32),
ethernet(33), ethernet(33),
sdhSonet(34), sdhSonet(34),
digitalwrapper(36), digitalwrapper(36),
lambda(37), lambda(37),
ansiEtsiPdh (38), ansiEtsiPdh (38),
lapsSdh (40), lapsSdh (40),
fddi (41), fddi (41),
dqdb (42), dqdb (42),
skipping to change at page 54, line 43 skipping to change at page 55, line 6
IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION IANAGmplsAdminStatusInformationTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type determines the setting of the "This data type 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
object or TLV on signaling messages. object or TLV on signaling messages.
This textual convention is strongly tied to the Admin This textual convention is strongly tied to the
Status Flags sub-registry of the GMPLS Signaling Parameters Administrative Status Information Flags sub-registry of
registry managed by IANA. Values should be assigned by IANA the GMPLS Signaling Parameters registry managed by IANA.
in step with the Admin Status Flags sub-registry and using Values should be assigned by IANA in step with the
the same registry management rules. However, the actual Administrative Status Flags sub-registry and using the
values used in this textual convention are solely within same registry management rules. However, the actual
the purview of IANA and do not necessarily match the values values used in this textual convention are solely
in the values in the Admin Status Flags sub-registry. within the purview of IANA and do not necessarily match
the values in the Administrative Status Information
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006 Flags sub-registry.
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.)
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@iana.org)."
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.
2. Generalized MPLS Signaling - RSVP-TE Extensions,
RFC 3473, section 7.
3. GMPLS - Communication of Alarm Information,
RFC 4783, section 3.2.1."
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
reserved6 (6), -- reserved reserved6 (6), -- reserved
reserved7 (7), -- reserved reserved7 (7), -- reserved
reserved8 (8), -- reserved reserved8 (8), -- reserved
reserved9 (9), -- reserved reserved9 (9), -- reserved
reserved10 (10), -- reserved reserved10 (10), -- reserved
reserved11 (11), -- reserved reserved11 (11), -- reserved
reserved12 (12), -- reserved reserved12 (12), -- reserved
reserved13 (13), -- reserved reserved13 (13), -- reserved
reserved14 (14), -- reserved reserved14 (14), -- reserved
reserved15 (15), -- reserved reserved15 (15), -- reserved
reserved16 (16), -- reserved reserved16 (16), -- reserved
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
reserved17 (17), -- reserved reserved17 (17), -- reserved
reserved18 (18), -- reserved reserved18 (18), -- reserved
reserved19 (19), -- reserved reserved19 (19), -- reserved
reserved20 (20), -- reserved reserved20 (20), -- reserved
reserved21 (21), -- reserved reserved21 (21), -- reserved
reserved22 (22), -- reserved reserved22 (22), -- reserved
reserved23 (23), -- reserved reserved23 (23), -- reserved
reserved24 (24), -- reserved reserved24 (24), -- reserved
reserved25 (25), -- reserved reserved25 (25), -- reserved
reserved26 (26), -- reserved reserved26 (26), -- reserved
reserved27 (27), -- reserved reserved27(27), -- Inhibit Alarm bit (RFC 4783)
reserved28 (28), -- reserved reserved28 (28), -- reserved
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
[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. Requirement 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
1 Functional Specification", RFC 2205, September 1997. Functional Specification", RFC 2205, September 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Structure of "Structure of Management Information Version 2 (SMIv2)",
Management Information Version 2 (SMIv2)", STD 58, RFC STD 58, RFC 2578, April 1999.
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
J., Rose, M., and S. Waldbusser, "Conformance Statements Conventions for SMIv2", STD 58, RFC 2579, April 1999.
for SMIv2", STD 58, RFC 2580, April 1999.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, April
1999.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
"Multiprotocol Label Switching Architecture", RFC 3031, Label Switching Architecture", RFC 3031, January 2001.
January 2001.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
3411, December 2002. December 2002.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[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
Links in Resource ReSerVation Protocol - Traffic in Resource ReSerVation Protocol - Traffic Engineering
Engineering (RSVP-TE)", RFC 3477, January 2003. (RSVP-TE)", RFC 3477, January 2003.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions (TCs) 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
Engineering (TE) Management Information Base (MIB)", (TE) Management Information Base (MIB)", RFC 3812, June
RFC 3812, June 2004. 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
(LSR) Router Management Information Base (MIB)", RFC Router (LSR) Management Information Base (MIB)", RFC 3813,
3813, June 2004. June 2004.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label [RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching
Switching (GMPLS) Architecture", RFC 3945, October 2004. (GMPLS) Architecture", RFC 3945, October 2004.
[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
Support of Generalized Multi-Protocol Label Switching", of Generalized Multi-Protocol Label Switching (GMPLS)", RFC
RFC 4202, October 2005. 4202, October 2005.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006 [RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Extensions for G.709 Optical
Transport Networks Control", RFC 4328, January 2006.
[GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol [RFC4783] Berger, L., "GMPLS - Communication of Alarm Information",
Label Switching (GMPLS) Label Switching Router (LSR) RFC 4783, December 2006.
Management Information Base",
draft-ietf-ccamp-gmpls-lsr-mib, work in progress. [RFC4803] Nadeau, T., Ed. and A. Farrel, Ed., "Generalized
Multiprotocol Label Switching (GMPLS) Label Switching
Router (LSR) Management Information Base", RFC 4803,
February 2007.
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-
Internet-Standard Management Framework", RFC 3410, Standard Management Framework", RFC 3410, December 2002.
December 2002.
[RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized Multi-
Multi-Protocol Label Switching (MPLS) Signaling Protocol Label Switching (GMPLS) Signaling Constraint-based
- Constraint-based Routed Label Distribution Protocol Routed Label Distribution Protocol (CR-LDP) Extensions",
(CR-LDP) Extensions", RFC 3472, January 2003. RFC 3472, January 2003.
13. Contact Information Contact Information
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
Email: tnadeau@cisco.com
EMail: tnadeau@cisco.com
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P. Bloomberg L.P.
731 Lexington Ave. 731 Lexington Ave.
New York, NY 10022 New York, NY 10022
Phone: +1-212-617-3682 Phone: +1-212-617-3682
Email: cheenu@bloomberg.net EMail: cheenu@bloomberg.net
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Phone: +44-(0)-1978-860944 Phone: +44-(0)-1978-860944
Email: adrian@olddog.co.uk EMail: adrian@olddog.co.uk
Tim Hall Tim Hall
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: tim.hall@dataconnection.com EMail: tim.hall@dataconnection.com
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
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 Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
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.
skipping to change at page 59, line 38 skipping to change at page 60, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
15. Full Copyright Statement Acknowledgement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an Funding for the RFC Editor function is currently provided by the
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS Internet Society.
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 281 change blocks. 
568 lines changed or deleted 487 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/