draft-ietf-ccamp-gmpls-te-mib-05.txt   draft-ietf-ccamp-gmpls-te-mib-06.txt 
CCAMP Working Group Thomas D. Nadeau CCAMP Working Group Thomas D. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: December 2004 Cheenu Srinivasan Expires: April 2005 Adrian Farrel, Ed.
Bloomberg L.P.
Adrian Farrel
Old Dog Consulting Old Dog Consulting
Tim Hall October 2004
Ed Harrison
Data Connection Ltd.
June 2004
Generalized Multiprotocol Label Switching (GMPLS) Traffic Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base Engineering Management Information Base
draft-ietf-ccamp-gmpls-te-mib-05.txt draft-ietf-ccamp-gmpls-te-mib-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines a portion of the Management Information Base (MIB)
Information Base (MIB) for use with network management protocols in for use with network management protocols in the Internet community.
the Internet community. In particular, it describes managed objects In particular, it describes managed objects for Generalized
for Generalized Multiprotocol Label Switching (GMPLS) based traffic Multiprotocol Label Switching (GMPLS) based traffic engineering.
engineering.
Table of Contents Table of Contents
1. Introduction 2 1. Introduction ........................................... 2
1.1. Migration Strategy 3 1.1. Migration Strategy ................................... 3
2. Terminology 3 2. Terminology ............................................ 3
3. The SNMP Management Framework 3 3. The SNMP Management Framework .......................... 3
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 4 5. Brief Description of GMPLS TE MIB Objects .............. 4
5.1. gmplsTunnelTable 4 5.1. gmplsTunnelTable ..................................... 4
5.2. gmplsTunnelHopTable 5 5.2. gmplsTunnelHopTable .................................. 5
5.3. gmplsTunnelARHopTable 5 5.3. gmplsTunnelARHopTable ................................ 5
5.4. gmplsTunnelCHopTable 5 5.4. gmplsTunnelCHopTable ................................. 5
5.5. gmplsTunnelErrorTable 5 5.5. gmplsTunnelErrorTable ................................ 5
5.6. gmplsTunnelReversePerfTable 5 5.6. gmplsTunnelReversePerfTable .......................... 5
6. Cross-referencing to the mplsLabelTable 5 6. Cross-referencing to the mplsLabelTable ................ 6
7. Example of GMPLS Tunnel Setup 6 7. Example of GMPLS Tunnel Setup .......................... 6
8. GMPLS Traffic Engineering MIB Definitions 9 8. GMPLS Traffic Engineering MIB Definitions ............. 10
9. Security Considerations 37 9. Security Considerations ............................... 43
10. Acknowledgments 38 10. Acknowledgments ...................................... 44
11. References 39 11. IANA Considerations .................................. 44
11.1. Normative Refenerces 39 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 44
11.2. Informational References 40 12. References ........................................... 45
12. Authors' Addresses 41 12.1. Normative Refenerces ............................... 45
13. Full Copyright Statement 41 12.2. Informational References ........................... 46
14. Intellectual Property Notice 42 13. Authors' Addresses ................................... 47
14. Full Copyright Statement ............................. 48
15. Intellectual Property Notice ......................... 48
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 a In particular, it describes managed objects for modeling
Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] based Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] based
traffic engineering. The tables and objects defined in this document traffic engineering. 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 [TEMIB], 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.
This MIB module should be used in conjunction with the companion This MIB module should be used in conjunction with the companion
document [GMPLSLSRMIB] for GMPLS based traffic engineering document [GMPLSLSRMIB] for GMPLS based traffic engineering
configuration and management. configuration and management.
Comments should be made direct to the CCAMP mailing list at Comments should be made direct to the CCAMP mailing list at
ccamp@ops.ietf.org. ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference document are to be interpreted as described in BCP 14, RFC 2119,
[RFC2119]. reference [RFC2119].
1.1. Migration Strategy 1.1. Migration Strategy
This MIB module extends the traffic engineering MIB module defined This MIB module extends the traffic engineering MIB module defined
for use with MPLS [TEMIB]. It provides additions for support of GMPLS for use with MPLS [RFC3812]. It provides additions for support of
tunnels. GMPLS tunnels.
The companion document for modeling and managing GMPLS based LSRs The companion document for modeling and managing GMPLS based LSRs
[GMPLSLSRMIB] extends MPLS LSR MIB [LSRMIB] with the same intentions. [GMPLSLSRMIB] extends MPLS LSR MIB [RFC3813] with the same
intentions.
Textual conventions and OBJECT-IDENTIFIERS are defined in [TCMIB] and Textual conventions and OBJECT-IDENTIFIERS are defined in [RFC3811]
[GMPLSTCMIB]. and [GMPLSTCMIB].
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 [GMPLSArch], and from [RFC3031], from the GMPLS architecture document [GMPLSArch], and from
the MPLS Traffic Engineering MIB [TEMIB]. Some frequently used terms the MPLS Traffic Engineering MIB [RFC3812]. Some frequently used
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. It
consists of in-segment(s) and/or out-segment(s) at the egress/ingress consists of in-segment(s) and/or out-segment(s) at the egress/ingress
LSRs, each segment being associated with one GMPLS enabled interface. LSRs, each segment being associated with one GMPLS enabled interface.
These are also referred to as tunnel segments. These are also referred to as tunnel segments.
Additionally, at an intermediate LSR, we model a connection as Additionally, at an intermediate LSR, we model a connection as
consisting of one or more in-segments and/or one or more out- consisting of one or more in-segments and/or one or more
segments. The binding or interconnection between in-segments and out- out-segments. The binding or interconnection between in-segments and
segments in 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 [LSRMIB], but see also the GMPLS Label Switch Switch Router MIB [RFC3813], but see also the GMPLS Label Switch
Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these
objects. objects.
3. The SNMP Management Framework 3. The SNMP Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a Structure of Management Information (SMI). This memo specifies a MIB
MIB module that is compliant to the SMIv2, which is described in STD module that is compliant to the SMIv2, which is described in STD 58,
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
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 [TEMIB]. using [RFC3812].
- Extending the tunnels with GMPLS configuration parameters. - Extending the tunnels with GMPLS configuration parameters.
- Configuring tunnel loose and strict source routed hops. - Configuring tunnel loose and strict source routed hops.
These actions may need to be accompanied with corresponding actions These actions may need to be accompanied with corresponding actions
using [LSRMIB] and [GMPLSLSRMIB] to establish and configure tunnel using [RFC3813] and [GMPLSLSRMIB] to establish and configure tunnel
segments, if this is done manually. Also, the in-segment and out- segments, if this is done manually. Also, the in-segment and
segment performance tables, mplsInSegmentPerfTable and out-segment performance tables, mplsInSegmentPerfTable and
mplsOutSegmentPerfTable [LSRMIB], 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 MIB objects for performing the actions listed above that cannot The MIB objects for performing the actions listed above that cannot
be performed solely using the MIB objects defined in [TEMIB] consist be performed solely using the MIB objects defined in [RFC3812]
of the following tables. consist of the following tables.
- Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific
tunnel configuration parameters. tunnel configuration parameters.
- Tunnel specified, actual, and computed hop tables - Tunnel specified, actual, and computed hop tables
(gmplsTunnelHopTable, gmplsTunnelARHopTable, and (gmplsTunnelHopTable, gmplsTunnelARHopTable, and
gmplsTunnelCHopTable) for providing additional configuration of gmplsTunnelCHopTable) for providing additional configuration of
strict and loose source routed tunnel hops. strict and loose source routed tunnel hops.
- Performance and error reporting tables (gmplsTunnelReversePerfTable - Performance and error reporting tables (gmplsTunnelReversePerfTable
and gmplsTunnelErrorTable). and gmplsTunnelErrorTable).
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
Additionally, this MIB module contains a new Notification. Additionally, this MIB module contains a new Notification.
- The GMPLS Tunnel Down Notification (gmplsTunnelDown) is intended to - The GMPLS Tunnel Down Notification (gmplsTunnelDown) is intended to
be used in place of the mplsTunnelDown Notification defined in be used in place of the mplsTunnelDown Notification defined in
[TEMIB]. As well as indicating that a tunnel has transitioned to [RFC3812]. As well as indicating that a tunnel has transitioned to
operational down state, this new Notificaiton indicates the cause operational down state, this new Notificaiton indicates the cause
of the failure. 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. described in [RFC3473] and [RFC3472] for GMPLS tunnels.
The tables support both manually configured and signaled tunnels. The tables support both manually configured and signaled tunnels.
5.1. gmplsTunnelTable 5.1. gmplsTunnelTable
The gmplsTunnelTable extends the MPLS traffic engineering MIB to The gmplsTunnelTable extends the MPLS traffic engineering MIB module
allow GMPLS tunnels to be created between an LSR and a remote to allow GMPLS tunnels to be created between an LSR and a remote
endpoint, and existing GMPLS tunnels to be reconfigured or removed. endpoint, and existing GMPLS tunnels to 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 multi-point-to-point and point-to-multi-point connections are
supported by an LSR acting as a cross-connect. supported 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.
5.2. gmplsTunnelHopTable 5.2. gmplsTunnelHopTable
The gmplsTunnelHopTable is used to indicate additional parameters for The gmplsTunnelHopTable is used to indicate additional parameters for
the hops, strict or loose, of a GMPLS tunnel defined in the hops, strict or loose, of a GMPLS tunnel defined in
gmplsTunnelTable, when it is established using signaling. Multiple gmplsTunnelTable, when it is established using signaling. Multiple
tunnels may share the same hops by pointing to the same entry in this tunnels may share hops by pointing to the same entry in this table.
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 setup. The support of this table is optional since not all
GMPLS signaling protocols support this feature. GMPLS signaling protocols support this feature.
5.4. gmplsTunnelCHoptable 5.4. gmplsTunnelCHoptable
skipping to change at page 5, line 59 skipping to change at page 6, line 12
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.
6. Cross-referencing to the gmplsLabelTable 6. Cross-referencing to the gmplsLabelTable
The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and
provides a way to model labels in a GMPLS system where labels might provides a way to model labels in a GMPLS system where labels might
not be simple 32 bit integers. not be simple 32 bit integers.
The hop tables in this document (gmplsHopTable, gmplsCHopTable and The hop tables in this document (gmplsHopTable, gmplsCHopTable and
gmplsARHopTable) and the segment tables in the [LSRMIB] gmplsARHopTable) and the segment tables in the [RFC3813]
(mplsInSegmentTable and mplsOutSegmentTable) contain objects with (mplsInSegmentTable and mplsOutSegmentTable) contain objects with
syntax MplsLabel. syntax MplsLabel.
MplsLabel (defined in [TCMIB]) is a 32-bit integer that is capable of MplsLabel (defined in [RFC3811]) is a 32-bit integer that is capable
representing any MPLS label and most GMPLS labels. However, some of representing any MPLS label and most GMPLS labels. However, some
GMPLS labels are larger than 32 bits and may be of arbitrary length. GMPLS labels are larger than 32 bits and may be of arbitrary length.
Further, some labels that may be safely encoded in 32 bits are Further, some labels that may be safely encoded in 32 bits are
constructed from multiple sub-fields. Additionally, some GMPLS constructed from multiple sub-fields. Additionally, some GMPLS
technologies support the concatenation of individual labels to technologies support the concatenation of individual labels to
represent a data flow carried as multiple sub-flows. represent a data flow carried as multiple sub-flows.
These GMPLS cases require that something other than a simple 32-bit These GMPLS cases require that something other than a simple 32-bit
integer is made available to represent the labels. This is achieved integer is made available to represent the labels. This is achieved
through the gmplsLabelTable contained in [GMPLSLSRMIB]. through the gmplsLabelTable contained in [GMPLSLSRMIB].
The tables in this document and [LSRMIB] 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 object
of syntax MplsLabel contains the label encoded as a 32-bit integer. of syntax MplsLabel contains the label encoded as a 32-bit integer.
But otherwise the row pointer indicates a row in another MIB table But otherwise the row pointer indicates a row in another MIB table
that includes the label. In these cases, the row pointer may indicate that includes the label. In these cases, the row pointer may indicate
a row in the gmplsLabelTable. 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 previous version of this MIB [TEMIB], and a significant implement the previous version of this MIB module [RFC3812], and a
simplification in GMPLS systems that are limited to a single, simple significant simplification in GMPLS systems that are limited to a
label type. single, simple 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
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 "head- protection. Note that these objects should be created on the
end" LSR. "head-end" LSR.
First in the mplsTunnelTable: First in the mplsTunnelTable:
{ {
mplsTunnelIndex = 1, mplsTunnelIndex = 1,
mplsTunnelInstance = 1, mplsTunnelInstance = 1,
mplsTunnelIngressLSRId = 123.123.125.1, mplsTunnelIngressLSRId = 123.123.125.1,
mplsTunnelEgressLSRId = 123.123.126.1, mplsTunnelEgressLSRId = 123.123.126.1,
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),
skipping to change at page 8, line 31 skipping to change at page 9, line 10
provide additional GMPLS hop configuration indicating that the first provide additional GMPLS hop configuration indicating that the first
hop is an unnumbered link using explicit forward and reverse labels. hop is an unnumbered link using explicit forward and reverse labels.
An entry in the gmplsLabelTable is created first to include the An entry in the gmplsLabelTable is created first to include the
explicit label. explicit label.
In gmplsLabelTable: In gmplsLabelTable:
{ {
gmplsLabelInterface = 2, gmplsLabelInterface = 2,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
gmplsLabelSubindex = 0, gmplsLabelSubindex = 0,
gmplsLabelType = = gmplsLabelType = gmplsFreeformGeneralizedLabel(3),
gmplsFreeformGeneralizedLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210 gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4) gmplsLabelRowStatus = createAndGo(4)
} }
In gmplsTunnelHopTable(1,1,1): In gmplsTunnelHopTable(1,1,1):
{ {
gmplsTunnelHopLabelStatuses = forwardPresent(0) gmplsTunnelHopLabelStatuses = forwardPresent(0)
+reversePresent(1), +reversePresent(1),
gmplsTunnelHopExpLabelPtr = gmplsLabelTable (2, 1, 0) gmplsTunnelHopExpLabelPtr = gmplsLabelTable (2, 1, 0)
gmplsTunnelHopExpRvrsLabelPtr = gmplsLabelTable (2, 1, 0) gmplsTunnelHopExpRvrsLabelPtr = gmplsLabelTable (2, 1, 0)
skipping to change at page 9, line 13 skipping to change at page 10, line 13
} }
8. GMPLS Traffic Engineering MIB Definitions 8. GMPLS Traffic Engineering MIB Definitions
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,
Integer32, Unsigned32, Counter32, Integer32, Unsigned32, Counter32,
Counter64, IpAddress, zeroDotZero Counter64, IpAddress, zeroDotZero
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
TruthValue, TimeStamp, DisplayString, RowPointer TruthValue, TimeStamp, DisplayString, RowPointer
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
InetAddress InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB -- [RFC3291]
mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId,
mplsTunnelEgressLSRId, mplsTunnelHopListIndex, mplsTunnelEgressLSRId, mplsTunnelHopListIndex,
mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex, mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex,
mplsTunnelARHopListIndex, mplsTunnelARHopIndex, mplsTunnelARHopListIndex, mplsTunnelARHopIndex,
mplsTunnelCHopListIndex, mplsTunnelCHopIndex, mplsTunnelCHopListIndex, mplsTunnelCHopIndex,
mplsTunnelEntry, mplsTunnelSignallingProto, mplsTunnelEntry,
mplsTunnelAdminStatus, mplsTunnelOperStatus mplsTunnelAdminStatus, mplsTunnelOperStatus
FROM MPLS-TE-STD-MIB FROM MPLS-TE-STD-MIB -- [RFC3812]
gmplsStdMIB mplsStdMIB
FROM GMPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- [RFC3811]
; ;
gmplsTeStdMIB MODULE-IDENTITY gmplsTeStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200406010900Z" -- 1 June 2004 9:00:00 GMT "200410080001Z" -- 8 October 2004 00:00:01 GMT
ORGANIZATION ORGANIZATION
"Common Control And Management Protocols (CCAMP) "Common Control And Measurement Plane (CCAMP) Working Group"
Working 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
Cheenu Srinivasan
Bloomberg L.P.
Email: cheenu@bloomberg.net
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Ed Harrison
Data Connection Ltd.
Email: ed.harrison@dataconnection.com
Tim Hall
Data Connection Ltd.
Email: tim.hall@dataconnection.com
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION
"This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE).
Copyright (C) The Internet Society (2004). This DESCRIPTION
version of this MIB module is part of RFCXXX; see "Copyright (C) The Internet Society (2004). The
the RFC itself for full legal notices." initial version of this MIB module was published
in RFC xxxx. For full legal notices see the RFC
itself or see: http://www.ietf.org/copyrights/ianamib.html
This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE) as defined in:
1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
-- Revision history. -- Revision history.
REVISION REVISION
"200406010900Z" -- 1 June 2004 09:00:00 GMT "200410080001Z" -- 8 October 2004 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial version issued as part of RFC XXXX."
::= { gmplsStdMIB xx } ::= { mplsStdMIB xx }
-- Top level components of this MIB. -- Top level components of this MIB.
-- Notifications -- Notifications
gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 }
-- tables, scalars -- tables, scalars
gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 }
gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 }
-- conformance -- conformance
gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 }
-- GMPLS Tunnel scalars. -- GMPLS Tunnel scalars.
gmplsTunnelsConfigured OBJECT-TYPE gmplsTunnelsConfigured OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 10, line 38 skipping to change at page 11, line 36
-- conformance -- conformance
gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 }
-- GMPLS Tunnel scalars. -- GMPLS Tunnel scalars.
gmplsTunnelsConfigured OBJECT-TYPE gmplsTunnelsConfigured OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of GMPLS tunnels configured on this "The number of GMPLS tunnels configured on this device. A GMPLS
device. A GMPLS tunnel is considered configured if tunnel is considered configured if an entry for the tunnel
an entry for the tunnel exists in the exists in the gmplsTunnelTable and the associated
gmplsTunnelTable and the associated
mplsTunnelRowStatusis active(1)." mplsTunnelRowStatusis active(1)."
::= { gmplsTeScalars 1 } ::= { gmplsTeScalars 1 }
gmplsTunnelsActive OBJECT-TYPE gmplsTunnelsActive OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of GMPLS tunnels active on this device. "The number of GMPLS tunnels active on this device. A GMPLS
A GMPLS tunnel is considered active if there is an tunnel is considered active if there is an entry in the
entry in the gmplsTunnelTable and the associated gmplsTunnelTable and the associated mplsTunnelOperStatus
mplsTunnelOperStatus for the tunnel is up(1)." for the tunnel is up(1)."
::= { gmplsTeScalars 2 } ::= { gmplsTeScalars 2 }
-- End of GMPLS Tunnel scalars. -- End of GMPLS Tunnel scalars.
-- GMPLS tunnel table. -- GMPLS tunnel table.
gmplsTunnelTable OBJECT-TYPE gmplsTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelEntry SYNTAX SEQUENCE OF GmplsTunnelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 11, line 16 skipping to change at page 12, line 16
gmplsTunnelTable OBJECT-TYPE gmplsTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelEntry SYNTAX SEQUENCE OF GmplsTunnelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gmplsTunnelTable 'extends' the mplsTunnelTable. "The gmplsTunnelTable 'extends' the mplsTunnelTable.
It allows GMPLS tunnels to be created between an LSR It allows GMPLS tunnels to be created between an LSR
and a remote endpoint, and existing tunnels to be and a remote endpoint, and existing tunnels to be
reconfigured or removed. reconfigured or removed.
Note that only point-to-point tunnel segments are Note that only point-to-point tunnel segments are
supported, although multi-point-to-point and point- supported, although multi-point-to-point and
to-multi-point connections are supported by an LSR point-to-multi-point connections are supported by an LSR
acting as a cross-connect. Each tunnel can thus have acting as a cross-connect. Each tunnel can thus have
one out-segment originating at this LSR and/or one one out-segment originating at this LSR and/or one
in-segment terminating at this LSR. in-segment terminating at this LSR.
The row status of an entry in this table is The row status of an entry in this table is
controlled by mplsTunnelRowStatus in the controlled by mplsTunnelRowStatus in the
corresponding entry in mplsTunnelTable. That is, corresponding entry in mplsTunnelTable. That is,
it is not permitted to create a row in this table, it is not permitted to create a row in this table,
nor to modify an existing row, when the nor to modify an existing row, when the
corresponding mplsTunnelRowStatus has value corresponding mplsTunnelRowStatus has value
skipping to change at page 12, line 55 skipping to change at page 14, line 15
signaled (for example SESSION_ATTRIBUTES flags in signaled (for example SESSION_ATTRIBUTES flags in
RSVP-TE). RSVP-TE).
The following describes these bitfields: The following describes these bitfields:
labelRecordingDesired labelRecordingDesired
This flag indicates that label information should be This flag indicates that label information should be
included when doing a route record. This bit is not included when doing a route record. This bit is not
valid unless the recordRoute bit is set." valid unless the recordRoute bit is set."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, "RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche
Awduche et al, RFC 3209, December 2001." et al, RFC 3209, December 2001."
DEFVAL { { } } DEFVAL { { } }
::= { gmplsTunnelEntry 2 } ::= { gmplsTunnelEntry 2 }
gmplsTunnelLSPEncoding OBJECT-TYPE gmplsTunnelLSPEncoding OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the encoding of the LSP being "This object indicates the encoding of the LSP being requested.
requested.
A value of zero indicates that GMPLS signaling is A value of zero indicates that GMPLS signaling is
not in use. Some objects in this MIB module may be not in use. Some objects in this MIB module may be
of use for MPLS signaling extensions that do not use of use for MPLS signaling extensions that do not use
GMPLS signaling. By setting this object to zero, an GMPLS signaling. By setting this object to zero, an
application may indicate that only those objects application may indicate that only those objects
meaningful in MPLS should be examined. meaningful in MPLS should be examined.
The values to use are currently defined in The values to use are currently defined in
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, RFC 3471. Further Signaling Functional Description, RFC 3471. Further
values may be defined in future RFCs. values may be defined in future RFCs.
skipping to change at page 13, line 38 skipping to change at page 15, line 4
tunnelLspLambda (8), tunnelLspLambda (8),
tunnelLspFiber (9), tunnelLspFiber (9),
-- the value 10 is deprecated -- the value 10 is deprecated
tunnelLspFiberChannel (11), tunnelLspFiberChannel (11),
tunnelDigitalPath (12), tunnelDigitalPath (12),
tunnelOpticalChannel (13)" tunnelOpticalChannel (13)"
REFERENCE REFERENCE
"1. Berger, L., et al., Generalized Multi-Protocol "1. Berger, L., et al., Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional Label Switching (GMPLS) Signaling Functional
Description, RFC 3471, January 2003. Description, RFC 3471, January 2003.
2. D. Papadimitriou (Editor), Generalized MPLS 2. D. Papadimitriou (Editor), Generalized MPLS
Signalling Extensions for G.709 Optical Transport Signalling Extensions for G.709 Optical Transport
Networks Control" Networks Control, draft-ietf-ccamp-gmpls-g709-06.txt,
January 2004, work in progress."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsTunnelEntry 3 } ::= { gmplsTunnelEntry 3 }
gmplsTunnelSwitchingType OBJECT-TYPE gmplsTunnelSwitchingType OBJECT-TYPE
SYNTAX Integer32 (0..255) SYNTAX Integer32 (0..255)
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
skipping to change at page 14, line 10 skipping to change at page 15, line 35
psc2 (2), psc2 (2),
psc3 (3), psc3 (3),
psc4 (4), psc4 (4),
l2sc (51), l2sc (51),
tdm (100), tdm (100),
lsc (150), lsc (150),
fsc (200) fsc (200)
This object is only meaningful if This object is only meaningful if
gmplsTunnelLSPEncoding is not set to 0." gmplsTunnelLSPEncoding is not set to 0."
REFERENCE REFERENCE
"1. Kompella, K., et al., OSPF Extensions in Support "1. Kompella, K., Rekhter, Y. (Editors), Routing Extensions in
of Generalized MPLS, draft-ietf-ccamp-ospf-gmpls- Support of Generalized Multi-Protocol Label Switching,
extensions-12.txt, October 2003, work in progress. draft-ietf-ccamp-gmpls-routing-09.txt, October 2003, work in
progress.
2. Berger, L., et al., Generalized Multi-Protocol 2. Berger, L., et al., Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional Label Switching (GMPLS) Signaling Functional
Description, RFC 3471, January 2003." Description, RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsTunnelEntry 4 } ::= { gmplsTunnelEntry 4 }
gmplsTunnelLinkProtection OBJECT-TYPE gmplsTunnelLinkProtection OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
extraTraffic(0), extraTraffic(0),
unprotected(1), unprotected(1),
skipping to change at page 15, line 5 skipping to change at page 16, line 36
i.e., 1:1 protection, should be used to support the LSP. i.e., 1:1 protection, should be used to support the LSP.
dedicatedOnePlusOne dedicatedOnePlusOne
Indicates that a dedicated link layer protection scheme, Indicates that a dedicated link layer protection scheme,
i.e., 1+1 protection, should be used to support the LSP. i.e., 1+1 protection, should be used to support the LSP.
enhanced enhanced
Indicates that a protection scheme that is more reliable than Indicates that a protection scheme that is more reliable than
Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING.
This object is only meaningful if This object is only meaningful if gmplsTunnelLSPEncoding is
gmplsTunnelLSPEncoding is not set to 0." not set to 0."
REFERENCE
"Berger, L., et al., Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional
Description, RFC 3471, January 2003."
DEFVAL { { } } DEFVAL { { } }
::= { gmplsTunnelEntry 5 } ::= { gmplsTunnelEntry 5 }
gmplsTunnelGPid OBJECT-TYPE gmplsTunnelGPid OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the payload carried by the "This object indicates the payload carried by the
LSP. It is only required when GMPLS will be used for LSP. It is only required when GMPLS will be used for
skipping to change at page 16, line 22 skipping to change at page 18, line 14
gfpEthernetPHY (55), gfpEthernetPHY (55),
g709ESCON (56), g709ESCON (56),
g709FICON (57), g709FICON (57),
g709FiberChannel (58) g709FiberChannel (58)
This object is only meaningful if This object is only meaningful if
gmplsTunnelLSPEncoding is not set to 0." gmplsTunnelLSPEncoding is not set to 0."
REFERENCE REFERENCE
"1. Berger, L., et al., Generalized Multi-Protocol "1. Berger, L., et al., Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional Label Switching (GMPLS) Signaling Functional
Description, RFC 3471, January 2003." Description, RFC 3471, January 2003.
2. D. Papadimitriou (Editor), Generalized MPLS
Signalling Extensions for G.709 Optical Transport
Networks Control, draft-ietf-ccamp-gmpls-g709-06.txt,
January 2004, work in progress."
DEFVAL { 0 } DEFVAL { 0 }
::= { 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 This object is only meaningful if
gmplsTunnelLSPEncoding is not set to 0." gmplsTunnelLSPEncoding is not set to 0."
REFERENCE
"Berger, L., et al., Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional
Description, RFC 3471, January 2003."
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)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether this tunnel carries forward data (is "Whether this tunnel carries forward data only (is
unidirectional) or is bidirectional. unidirectional) or is bidirectional.
Values of this object other than 'forward' are meaningful Values of this object other than 'forward' are meaningful
only if gmplsTunnelLSPEncoding is not set to 0." only if gmplsTunnelLSPEncoding is not set to 0."
DEFVAL { forward } DEFVAL { forward }
::= { gmplsTunnelEntry 8 } ::= { gmplsTunnelEntry 8 }
gmplsTunnelPathComp OBJECT-TYPE gmplsTunnelPathComp OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dynamicFull(1),-- CSPF fully computed dynamicFull(1),-- CSPF fully computed
explicit(2),-- fully specified path explicit(2),-- fully specified path
dynamicPartial(3) -- CSPF partially computed dynamicPartial(3) -- CSPF partially computed
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value instructs the source node on how to perform "This value instructs the source node on how to perform
skipping to change at page 17, line 26 skipping to change at page 19, line 34
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.
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.
This object deprecates gmplsTunnelHopEntryPathComp." This object deprecates mplsTunnelHopEntryPathComp."
DEFVAL { dynamicFull } DEFVAL { dynamicFull }
::= { gmplsTunnelEntry 9 } ::= { gmplsTunnelEntry 9 }
gmplsTunnelUpNotRecip OBJECT-TYPE gmplsTunnelUpNotRecip OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the address of the upstream recipient for Notify "Indicates the address of the upstream recipient for Notify
messages relating to this tunnel. messages relating to this tunnel.
skipping to change at page 17, line 40 skipping to change at page 19, line 48
gmplsTunnelUpNotRecip OBJECT-TYPE gmplsTunnelUpNotRecip OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the address of the upstream recipient for Notify "Indicates the address of the upstream recipient for Notify
messages relating to this tunnel. messages relating to this tunnel.
This object is only valid when signaling a tunnel using This object is only valid when signaling a tunnel using
RSVP. It is also not valid at the tail end of the tunnel. RSVP. It is also not valid at the tail end of the tunnel.
If set to 0, no Notify Request object will be included in If set to 0, no Notify Request object will be included in
outgoing Path messages." outgoing Path messages."
REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
DEFVAL { '00000000'H } -- 0.0.0.0 DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 10 } ::= { gmplsTunnelEntry 10 }
gmplsTunnelDownNotRecip OBJECT-TYPE gmplsTunnelDownNotRecip OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the address of the upstream recipient for Notify "Indicates the address of the upstream recipient for Notify
messages relating to this tunnel. messages relating to this tunnel.
This object is only valid when signaling a tunnel using This object is only valid when signaling a tunnel using
RSVP. It is also not valid at the head end of the tunnel. RSVP. It is also not valid at the head end of the tunnel.
skipping to change at page 18, line 4 skipping to change at page 20, line 17
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the address of the upstream recipient for Notify "Indicates the address of the upstream recipient for Notify
messages relating to this tunnel. messages relating to this tunnel.
This object is only valid when signaling a tunnel using This object is only valid when signaling a tunnel using
RSVP. It is also not valid at the head end of the tunnel. RSVP. It is also not valid at the head end of the tunnel.
If set to 0, no Notify Request object will be included in If set to 0, no Notify Request object will be included in
outgoing Resv messages." outgoing Resv messages."
REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
DEFVAL { '00000000'H } -- 0.0.0.0 DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 11 } ::= { gmplsTunnelEntry 11 }
gmplsTunnelAdminStatusFlags OBJECT-TYPE gmplsTunnelAdminStatusFlags OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
delInProgress (0), delInProgress (0),
adminDown (1), adminDown (1),
testing (2), testing (2),
reflect (31) reflect (31)
} }
skipping to change at page 18, line 28 skipping to change at page 20, line 45
Admin Status object or TLV, as described in Admin Status object or TLV, as described in
RFC 3471. Setting this field to a non-zero value will RFC 3471. Setting this field to a non-zero value will
result in the inclusion of the admin status object on result in the inclusion of the admin status object on
signaling messages. signaling messages.
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
"Berger, L., et al., Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional
Description, RFC 3471, January 2003."
DEFVAL { { } }
::= { gmplsTunnelEntry 12 } ::= { gmplsTunnelEntry 12 }
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 "Some Tunnels will run over transports that can usefully support
usefully support technology-specific additional parameters technology-specific additional parameters (for example, SONET
(for example, SONET resource usage). resource usage). Such parameters can be supplied in an external
Such can be supplied from an external table and referenced from table and referenced from here.
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 13 } ::= { gmplsTunnelEntry 13 }
-- End of gmplsTunnelTable -- End of gmplsTunnelTable
-- Begin gmplsTunnelHopTable -- Begin gmplsTunnelHopTable
gmplsTunnelHopTable OBJECT-TYPE gmplsTunnelHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelHopEntry SYNTAX SEQUENCE OF GmplsTunnelHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 18, line 56 skipping to change at page 21, line 25
-- End of gmplsTunnelTable -- End of gmplsTunnelTable
-- Begin gmplsTunnelHopTable -- Begin gmplsTunnelHopTable
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 'extends' the "The gmplsTunnelHopTable 'extends' the mplsTunnelHopTable.
mplsTunnelHopTable. It is used to indicate the It is used to indicate the explicit labels to be used in an
explicit labels to be used in an explicit path for a explicit path for a GMPLS tunnel defined in mplsTunnelTable
GMPLS tunnel defined in mplsTunnelTable and and gmplsTunnelTable, when it is established using signaling.
gmplsTunnelTable, when it is established using It does not insert new hops, but does define new values for
signaling. It does not insert new hops, but does hops defined in mplsTunnelHopTable.
define new values for hops defined in
mplsTunnelHopTable.
Each row in this table is indexed by the same Each row in this table is indexed by the same
indexes as mplsTunnelHopTable. It is acceptable for indexes as mplsTunnelHopTable. It is acceptable for
some rows in mplsTunnelHopTable to have some rows in mplsTunnelHopTable to have
corresponding entries in this table and some to have corresponding entries in this table and some to have
no corresponding entry in this table. no corresponding entry in this table.
The storage type for an entry in this table is The storage type for an entry in this table is
inherited from mplsTunnelHopStorageType in the inherited from mplsTunnelHopStorageType in the
corresponding entry in mplsTunnelHopTable. corresponding entry in mplsTunnelHopTable.
The row status of an entry in this table is The row status of an entry in this table is
controlled by mplsTunnelHopRowStatus in the controlled by mplsTunnelHopRowStatus in the
corresponding entry in mplsTunnelHopTable. That is, corresponding entry in mplsTunnelHopTable. That is,
it is not permitted to create a row in this table, it is not permitted to create a row in this table,
nor to modify an existing row, when the nor to modify an existing row, when the
corresponding mplsTunnelHopRowStatus has value corresponding mplsTunnelHopRowStatus has value
active(1)." active(1)."
REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
::= { gmplsTeObjects 2 } ::= { gmplsTeObjects 2 }
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 "An entry in this table represents additions to a
tunnel hop defined in mplsTunnelHopEntry. At an tunnel hop defined in mplsTunnelHopEntry. At an
ingress to a tunnel an entry in this table is ingress to a tunnel an entry in this table is
created by a network administrator for an ERLSP to created by a network administrator for an ERLSP to
be set up by a signaling protocol. At transit and be set up by a signaling protocol. At transit and
skipping to change at page 20, line 21 skipping to change at page 22, line 49
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence of labels "This bitmask indicates the presence of labels
indicated by the gmplsTunnelHopExpLabel or indicated by the gmplsTunnelHopExpLabel or
gmplsTunnelHopExpLabelPtr and gmplsTunnelHopExpLabelPtr and
gmplsTunnelHopExpRvrsLabel or gmplsTunnelHopExpRvrsLabel gmplsTunnelHopExpRvrsLabel or gmplsTunnelHopExpRvrsLabel
objects. objects.
For the Present bits, a set bit indicates that a For the Present bits, a set bit indicates that a
label is present for this hop in the route. This label is present for this hop in the route. This
allows zero to be a valid label value." allows zero to be a valid label value."
DEFVAL { { } }
::= { gmplsTunnelHopEntry 1 } ::= { gmplsTunnelHopEntry 1 }
gmplsTunnelHopExpLabel OBJECT-TYPE gmplsTunnelHopExpLabel 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 "If gmplsTunnelHopLabelStatuses object indicates that a
forward label is present and gmplsTunnelHopExpLabelPtr forward label is present and gmplsTunnelHopExpLabelPtr
contains the value zeroDotZero, then the label to use on this contains the value zeroDotZero, then the label to use on this
hop is found in this object encoded within a 32-bit integer." hop is found in this object encoded within a 32-bit integer."
::= { gmplsTunnelHopEntry 2 } ::= { gmplsTunnelHopEntry 2 }
skipping to change at page 21, line 54 skipping to change at page 24, line 45
entries within this table is not provided by some entries within this table is not provided by some
signaling protocols and might not be returned in all signaling protocols and might not be returned in all
cases of other signaling protocols, implementation cases of other signaling protocols, implementation
of this table and mplsTunnelARHopTable is optional. of this table and mplsTunnelARHopTable is optional.
Furthermore, since the information in this table is Furthermore, since the information in this table is
actually provided by the signaling protocol after actually provided by the signaling protocol after
the path has been set-up, the entries in this table the path has been set-up, the entries in this table
are provided only for observation, and hence, all are provided only for observation, and hence, all
variables in this table are accessible exclusively variables in this table are accessible exclusively
as read-only." as read-only."
REFERENCE
"1. Extensions to RSVP for LSP Tunnels, Awduche et
al, RFC 3209, December 2001
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
::= { 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 "An entry in this table represents additions to a
tunnel hop visible in mplsTunnelARHopEntry. An entry tunnel hop visible in mplsTunnelARHopEntry. An entry
is created by the signaling protocol for a signaled is created by the signaling protocol for a signaled
skipping to change at page 22, line 52 skipping to change at page 26, line 4
reverseGlobal (3) reverseGlobal (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This bitmask indicates the presence and status of "This bitmask indicates the presence and status of
labels indicated by the labels indicated by the
gmplsTunnelARHopExpLabel or gmplsTunnelARHopExpLabelPtr and gmplsTunnelARHopExpLabel or gmplsTunnelARHopExpLabelPtr and
gmplsTunnelARHopExpRvrsLabel or gmplsTunnelARHopExpRvrsLabelPtr gmplsTunnelARHopExpRvrsLabel or gmplsTunnelARHopExpRvrsLabelPtr
objects. objects.
For the Present bits, a set bit indicates that a label For the Present bits, a set bit indicates that a label
is present for this hop in the route. For the Global bits, is present for this hop in the route. For the Global bits,
a set bit indicates that the label comes from the Global a set bit indicates that the label comes from the Global
Label Space. A clear bit indicates that this is a Per- Label Space. A clear bit indicates that this is a
Interface label. A Global bit only has meaning if the Per-Interface label. A Global bit only has meaning if the
corresponding Present bit is set." corresponding Present bit is set."
::= { gmplsTunnelARHopEntry 1 } ::= { gmplsTunnelARHopEntry 1 }
gmplsTunnelARHopExpLabel OBJECT-TYPE gmplsTunnelARHopExpLabel 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 "If the gmplsTunnelARHopLabelStatuses object indicates
that a forward label is present and that a forward label is present and
gmplsTunnelARHopExpLabelPtr contains the value gmplsTunnelARHopExpLabelPtr contains the value
zeroDotZero, then the label in use on this hop is zeroDotZero, then the label in use on this hop is
found in this object encoded within a 32-bit integer." found in this object encoded within a 32-bit integer."
skipping to change at page 24, line 53 skipping to change at page 28, line 19
Please note that since the information necessary to Please note that since the information necessary to
build entries within this table may not be supported build entries within this table may not be supported
by some LSRs, implementation of this table is optional. by some LSRs, 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 provided by a path computation component after the path has
been computed, the entries in this table are provided only been computed, the entries in this table are provided only
for observation, and hence, all objects in this table are for observation, and hence, all objects in this table are
accessible exclusively as read-only." accessible exclusively as read-only."
REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
::= { gmplsTeObjects 4 } ::= { gmplsTeObjects 4 }
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 "An entry in this table represents additions to a
computed tunnel hop visible in mplsTunnelCHopEntry. computed tunnel hop visible in mplsTunnelCHopEntry.
An entry is created by a path computation component An entry is created by a path computation component
skipping to change at page 26, line 55 skipping to change at page 30, line 39
gmplsTunnelReversePerfTable OBJECT-TYPE gmplsTunnelReversePerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table 'augments' the gmplsTunnelTable to provides "This table 'augments' the gmplsTunnelTable to provides
per-tunnel packet performance information for the per-tunnel packet performance information for the
reverse direction of a bidirectional tunnel. It can be reverse direction of a bidirectional tunnel. It can be
seen as supplementing the mplsTunnelPerfTable which seen as supplementing the mplsTunnelPerfTable which
augments the mplsTunnelTable." augments the mplsTunnelTable."
REFERENCE
"Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), Srinivasan, C., Viswanathan,
A., Nadeau, T., RFC 3812, June 2004."
::= { gmplsTeObjects 5 } ::= { gmplsTeObjects 5 }
gmplsTunnelReversePerfEntry OBJECT-TYPE gmplsTunnelReversePerfEntry OBJECT-TYPE
SYNTAX GmplsTunnelReversePerfEntry SYNTAX GmplsTunnelReversePerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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 bidirectional GMPLS tunnel where packets are visible to
the LSR." the LSR."
skipping to change at page 28, line 28 skipping to change at page 32, line 20
-- End of gmplsTunnelReversePerfTable -- End of gmplsTunnelReversePerfTable
-- GMPLS Tunnel Error Table. -- GMPLS Tunnel Error Table.
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 This table provides per-tunnel information about
errors. Errors may be detected locally or reported errors. Errors may be detected locally or reported
through the signaling protocol. through the signaling protocol.
Error reporting is not exclusive to GMPLS and this Error reporting is not exclusive to GMPLS and this
table may be applied in MPLS systems." table may be applied in MPLS systems."
REFERENCE
"Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), Srinivasan, C., Viswanathan,
A., Nadeau, T., RFC 3812, June 2004."
::= { 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 "An entry in this table is created by the LSR for
every tunnel where error information is visible to every tunnel where error information is visible to
the LSR. the LSR.
skipping to change at page 30, line 27 skipping to change at page 34, line 44
REFERENCE REFERENCE
"RFC3291, Textual Conventions for Internet Network "RFC3291, Textual Conventions for Internet Network
Addresses, Section 4. Usage Hints." Addresses, 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 "The primary error code associated with the last error.
error.
The interpretation of this error code depends on the The interpretation of this error code depends on the
value of gmplsTunnelErrorLastErrorType. If the value value of gmplsTunnelErrorLastErrorType. If the value
of gmplsTunnelErrorLastErrorType is noError (0) the of gmplsTunnelErrorLastErrorType is noError (0) the
value of this object should be 0 and should be value of this object should be 0 and should be
ignored. If the value of ignored. If the value of
gmplsTunnelErrorLastErrorType is localProtocol (2) gmplsTunnelErrorLastErrorType is localProtocol (2)
or remoteProtocol (3) the error should be or remoteProtocol (3) the error should be
interpreted in the context of the signling protocol interpreted in the context of the signling protocol
identified by the mplsTunnelSignallingProto object. identified by the mplsTunnelSignallingProto object.
Values in excess 32767 of are not used by signaling Values in excess 32767 of are not used by signaling
protocols and may safely be used as implementation- protocols and may safely be used as
specific error codes. " implementation-specific error codes. "
REFERENCE
"1. Braden, R. (Ed.) et al., Resource ReserVation Protocol --
Version 1 Functional Specification, RFC 2205, September 1997.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche
et al, RFC 3209, December 2001.
3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
::= { gmplsTunnelErrorEntry 5 } ::= { gmplsTunnelErrorEntry 5 }
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 "The secondary error code associated with the last error and the
error and the protocol used to signal this tunnel. protocol used to signal this tunnel. This value is interpreted
This value is interprettd in the context of the in the context of the value of gmplsTunnelErrorCode.
value of gmplsTunnelErrorCode.
If the value of gmplsTunnelErrorLastErrorType is If the value of gmplsTunnelErrorLastErrorType is
noError (0) the value of this object should be 0 and noError (0) the value of this object should be 0 and
should be ignored." should be ignored."
REFERENCE
"1. Braden, R. (Ed.) et al., Resource ReserVation Protocol --
Version 1 Functional Specification, RFC 2205, September 1997.
2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche
et al, RFC 3209, December 2001.
3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003."
::= { gmplsTunnelErrorEntry 6 } ::= { gmplsTunnelErrorEntry 6 }
gmplsTunnelErrorTLVs OBJECT-TYPE gmplsTunnelErrorTLVs OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequence of interface identifier TLVs reported "The sequence of interface identifier TLVs reported
with the error by the protocol code. The interpretation with the error by the protocol code. The interpretation
of the TLVs and the encoding within the protocol are of the TLVs and the encoding within the protocol are
described in the references. described in the references.
A value of zero in the first octet indicates that no A value of zero in the first octet indicates that no
skipping to change at page 31, line 16 skipping to change at page 35, line 49
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequence of interface identifier TLVs reported "The sequence of interface identifier TLVs reported
with the error by the protocol code. The interpretation with the error by the protocol code. The interpretation
of the TLVs and the encoding within the protocol are of the TLVs and the encoding within the protocol are
described in the references. described in the references.
A value of zero in the first octet indicates that no A value of zero in the first octet indicates that no
TLVs are present." TLVs are present."
REFERENCE REFERENCE
"RFC3471, Generalized Multi-Protocol Label Switching "Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
(GMPLS) Signaling Functional Description, L. (Editor), RFC 3473, January 2003."
Section 9.1. Interface Identification.
RFC3473, Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions, Section 8.2. Errored
Interface Identification"
::= { gmplsTunnelErrorEntry 7 } ::= { gmplsTunnelErrorEntry 7 }
gmplsTunnelErrorHelpString OBJECT-TYPE gmplsTunnelErrorHelpString OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual string containing information about the "A textual string containing information about the
last error, recovery actions and support advice. If last error, recovery actions and support advice. If
there is no help string this object contains a zero there is no help string this object contains a zero
length string. length string.
If the value of gmplsTunnelErrorLastErrorType is If the value of gmplsTunnelErrorLastErrorType is
skipping to change at page 32, line 44 skipping to change at page 37, line 36
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsTunnelGroup, gmplsTunnelGroup,
gmplsTunnelScalarGroup gmplsTunnelScalarGroup
} }
-- GROUP gmplsTunnelManualGroup -- GROUP gmplsTunnelManualGroup
-- DESCRIPTION -- DESCRIPTION
-- "This group is mandatory for devices which support -- "This group is mandatory for devices which support
-- manual configuration of tunnels, in addition to -- manual configuration of tunnels, in addition to
-- gmplsTunnelGroup. The following constraints apply: -- gmplsTunnelGroup. The following constraints apply:
-- mplsTunnelSignallingProto should be at least
-- read-only with a value of none(1)."
GROUP gmplsTunnelSignaledGroup GROUP gmplsTunnelSignaledGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
signaled tunnel set up, in addition to signaled tunnel set up, in addition to
gmplsTunnelGroup. The following constraints apply: gmplsTunnelGroup. The following constraints apply:
mplsTunnelSignallingProto should be at least read- mplsTunnelSignallingProto should be at least
only returning a value of ldp(2), or rsvp(3)." read-only returning a value of ldp(2), or rsvp(3)."
GROUP gmplsTunnelIsNotIntfcGroup GROUP gmplsTunnelIsNotIntfcGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
tunnels that are not interfaces, in addition to tunnels that are not interfaces, in addition to
gmplsTunnelGroup. The following constraints apply: gmplsTunnelGroup. The following constraints apply:
gmplsTunnelIsIf must at least be read-only returning no(0)." gmplsTunnelIsIf must at least be read-only returning no(0)."
GROUP gmplsTunnelIsIntfcGroup GROUP gmplsTunnelIsIntfcGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support "This group is mandatory for devices which support
tunnels that are interfaces, in addition to tunnels that are interfaces, in addition to gmplsTunnelGroup."
gmplsTunnelGroup."
GROUP gmplsTunnelOptionalGroup GROUP gmplsTunnelOptionalGroup
DESCRIPTION DESCRIPTION
"Objects in this group are optional." "Objects in this group are optional."
GROUP gmplsTeNotificationGroup GROUP gmplsTeNotificationGroup
DESCRIPTION "This group is mandatory for those implementations DESCRIPTION "This group is mandatory for those implementations
which can implement the notifications contained which can implement the notifications contained
in this group." in this group."
skipping to change at page 38, line 49 skipping to change at page 44, line 26
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 extends [TEMIB]. The authors would like to express This draft is the work of the five authors listed in the Authors'
Addresses section.
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 Baktha contributions during an early implementation, and to Baktha
Muralidharan for his review. Muralidharan for his review.
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.
11. References 11. IANA Considerations
11.1. Normative References As requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB], GMPLS related
standards track MIB modules should be rooted under the mplsStdMIB
subtree. There is one GMPLS MIB Module contained in this document,
and the following "IANA Considerations" subsection requests IANA for
a new assignment under the mplsStdMIB subtree. New assignments can
only be made via a Standards Action as specified in [RFC2434].
11.1. IANA Considerations for GMPLS-TE-STD-MIB
IANA is requested to assign an OID to the GMPLS-TE-STD-MIB module
specified in this document as { mplsStdMIB xx }.
12. 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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser, "Structure Case, J., Rose, M., and S. Waldbusser, "Structure
of Management Information Version 2 (SMIv2)", STD of Management Information Version 2 (SMIv2)", STD
58, RFC 2578, April 1999. 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
skipping to change at page 40, line 9 skipping to change at page 46, line 15
[RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
RSVP-TE Extensions", RFC 3473, January 2003. RSVP-TE Extensions", RFC 3473, January 2003.
[RFC3477] Kompella, K. and Rekhter, Y., "Signalling Unnumbered [RFC3477] Kompella, K. and Rekhter, Y., "Signalling Unnumbered
Links in RSVP-TE", RFC 3477, January 2003. Links in RSVP-TE", RFC 3477, January 2003.
[RFC3480] Kompella, K., Rekhter, Y. and Kullberg, A., [RFC3480] Kompella, K., Rekhter, Y. and Kullberg, A.,
"Signalling Unnumbered Links in CR-LDP", RFC 3480, "Signalling Unnumbered Links in CR-LDP", RFC 3480,
February 2003. February 2003.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching
(MPLS) Management", RFC 3811, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB)",
RFC 3812, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label
Switching (LSR) Router Management Information Base
(MIB)", RFC 3813, June 2004.
[GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol
Label Switching (GMPLS) Architecture", Label Switching (GMPLS) Architecture",
draft-many-gmpls-architecture-07.txt, May draft-many-gmpls-architecture-07.txt, May
2003, work in progress. 2003, work in progress.
[GMPLSLSRMIB] Nadeau, T., Srinivasan, C., A., Farrel, A., Hall, [GMPLSLSRMIB] Nadeau, T., Farrel, A., (Editors) "Generalized
T., and Harrison, E., "Generalized Multiprotocol Multiprotocol Label Switching (GMPLS) Label
Label Switching (GMPLS) Label Switching Router Switching Router (LSR) Management Information
(LSR) Management Information Base", draft-ietf- Base", draft-ietf-ccamp-gmpls-lsr-mib-06.txt,
ccamp-gmpls-lsr-mib-05.txt, June 2004, work in October 2004, work in progress.
progress.
[GMPLSOSPF] Kompella, K., et al., "OSPF Extensions in Support [GMPLSOSPF] Kompella, K., et al., "OSPF Extensions in Support
of Generalized MPLS", draft-ietf-ccamp-ospf-gmpls- of Generalized MPLS",
extensions-12.txt, October 2003, work in progress. draft-ietf-ccamp-ospf-gmpls-extensions-12.txt,
October 2003, work in progress.
[GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
and Harrison, E., "Definitions of Textual
Conventions for Multiprotocol Label Switching
(MPLS) Management", draft-ietf-ccamp-gmpls-te-mib-
05.txt, June 2004, work in progress.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label
Switching Router (LSR) Management Information
Base", draft-ietf-mpls-lsr-mib-14.txt, November
2003, work in progress.
[TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of [GMPLSTCMIB] Nadeau, T., Farrel, A., (Editors) "Definitions of
Textual Conventions for Multiprotocol Label Textual Conventions for Multiprotocol Label
Switching (MPLS) Management", Switching (MPLS) Management",
draft-ietf-mpls-tc-mib-10.txt, November 2003, work draft-ietf-ccamp-gmpls-te-mib-06.txt, October 2004,
in progress.
[TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A.,
"Multiprotocol Label Switching (MPLS) Traffic
Engineering Management Information Base",
draft-ietf-mpls-te-mib-14.txt, November 2003,
work in progress. work in progress.
11.2. Informational References 12.2. Informational References
[RFC2026] S. Bradner, "The Internet Standards Process -- [RFC2026] S. Bradner, "The Internet Standards Process --
Revision 3", RFC 2026, October 1996. Revision 3", RFC 2026, October 1996.
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for
Writing an IANA Considerations Section in RFCs",
BCP 26, RFC 2434, October 1998.
[RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP
Applications", RFC 3413, December 2002. Applications", RFC 3413, December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Architecture for Describing Simple Network
Management Protocol (SNMP) Management Frameworks", Management Protocol (SNMP) Management Frameworks",
RFC 3411, December 2002. RFC 3411, December 2002.
[GMPLS-G709] D. Papadimitriou (Editor), "Generalized MPLS [GMPLS-G709] D. Papadimitriou (Editor), "Generalized MPLS
Signalling Extensions for G.709 Optical Transport Signalling Extensions for G.709 Optical Transport
Networks Control", draft-ietf-ccamp-gmpls-g709- Networks Control", draft-ietf-ccamp-gmpls-g709-
06.txt, January 2004, work in progress. 07.txt, September 2004, work in progress.
12. Authors' Addresses 13. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P. Bloomberg L.P.
skipping to change at page 41, line 43 skipping to change at page 48, line 4
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
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
13. Intellectual Property Considerations 14. Intellectual Property Considerations
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 42, line 18 skipping to change at page 48, line 36
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.
13.1. IPR Disclosure Acknowledgement 15. Full Copyright Statement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
14. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
15. Changes and Pending Work 16. Changes
This section to be removed before the draft progresses to RFC. This section to be removed before the draft progresses to RFC.
15.1. Pending Work 16.1. Changes from version 5 to version 6
The following work items have been identified for this draft. They
will be addressed in a future version.
- Expand conformance statements to give one for monitoring only, - ID nits and MIB boilerplate
and one for monitoring and control.
- Resolve conformance statement from gmplsTunnelManualGroup.
15.1. Changes from version 4 to version 5 16.2. Changes from version 4 to version 5
- New IPR and copyright boiler plate. - New IPR and copyright boiler plate.
- Correct typo in name of gmplsTunnelExtraParamsPtr - Correct typo in name of gmplsTunnelExtraParamsPtr
- Add to list of encoding types and GPids for G.709 - Add to list of encoding types and GPids for G.709
- Add G.709 reference - Add G.709 reference
15.2. Changes from version 3 to version 4 16.3. Changes from version 3 to version 4
- Provide a way to configure additional tunnel parameters such as - Provide a way to configure additional tunnel parameters such as
tunnel resources through an arbitrary row pointer. tunnel resources through an arbitrary row pointer.
- Update references. - Update references.
- Change reporting IP addresses to use InetAddress syntax - Change reporting IP addresses to use InetAddress syntax
- Add support for IF_ID error reporting. - Add support for IF_ID error reporting.
- Add a new notification, gmplsTunnelDown, containing cause - Add a new notification, gmplsTunnelDown, containing cause
information. information.
- Clarify relationship to the gmplsLabelTable. - Clarify relationship to the gmplsLabelTable.
- Update descriptive text. - Update descriptive text.
- Bring usage of labels in line with latest [LSRMIB]. - Bring usage of labels in line with latest [RFC3813].
15.3. Changes from version 2 to version 3 16.4. Changes from version 2 to version 3
- Work on basic compilation issues. - Work on basic compilation issues.
- Resolve defaults for objects with syntax BITS. - Resolve defaults for objects with syntax BITS.
- Update references. - Update references.
- Clarify which objects can be modified when rowStatus and - Clarify which objects can be modified when rowStatus and
adminStatus are set to active. adminStatus are set to active.
- Control and reporting of upstream and downstream Notify - Control and reporting of upstream and downstream Notify
Recipients. Recipients.
- Add support for control and reporting of GMPLS Administrative - Add support for control and reporting of GMPLS Administrative
Status object. Status object.
 End of changes. 

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