draft-ietf-ccamp-gmpls-te-mib-15.txt   draft-ietf-ccamp-gmpls-te-mib-16.txt 
Internet Working Group Thomas D. Nadeau, Ed. Internet Working Group Thomas D. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: September 2006 Adrian Farrel, Ed. Expires: March 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
September 2006
Generalized Multiprotocol Label Switching (GMPLS) Traffic Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base Engineering Management Information Base
draft-ietf-ccamp-gmpls-te-mib-15.txt draft-ietf-ccamp-gmpls-te-mib-16.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 42 skipping to change at page 2, line 5
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 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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 ................... 6
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 .......................... 7
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 .................................. 48
11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 49 11.1. IANA Considerations for GMPLS-TE-STD-MIB ........... 48
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 ..................... 49
12. References ........................................... 57 12. References ........................................... 56
12.1. Normative References ............................... 57 12.1. Normative References ............................... 56
12.2. Informative References ............................. 58 12.2. Informative References ............................. 58
13. Contact Information .................................. 59 13. Contact Information .................................. 58
14. Intellectual Property Considerations ................. 59 14. Intellectual Property Considerations ................. 59
15. Full Copyright Statement ............................. 60 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 Multiprotocol Label Switching (GMPLS) [RFC3945] based Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] 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 [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 [GMPLSLSRMIB] for GMPLS based traffic
engineering configuration and management. engineering configuration and management.
Comments should be made direct to the CCAMP mailing list at Comments should be made direct to the CCAMP mailing list at
ccamp@ops.ietf.org. ccamp@ops.ietf.org.
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, RFC 2119,
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
reference [RFC2119]. reference [RFC2119].
1.1. Migration Strategy 1.1. Migration Strategy
MPLS-TE LSPs may be modeled and managed using the MPLS-TE-STD-MIB MPLS-TE LSPs may be modeled and managed using the MPLS-TE-STD-MIB
module [RFC3812]. module [RFC3812].
LSRs may be migrated to model and manage their TE LSPs using the MIB LSRs may be migrated to model and manage their TE LSPs using the MIB
modules in this document in order to migrate the LSRs to GMPLS modules in this document in order to migrate the LSRs to GMPLS
support, or to take advandtage of additional MIB objects defined in support, or to take advantage of additional MIB objects defined in
these MIB modules that are applicable to MPLS-TE. 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
skipping to change at page 3, line 53 skipping to change at page 4, line 4
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. It
consists of in-segment(s) and/or out-segment(s) at the egress/ingress consists of in-segment(s) and/or out-segment(s) at the egress/ingress
LSRs, each segment being associated with one GMPLS enabled interface. LSRs, each segment being associated with one GMPLS enabled interface.
These are also referred to as tunnel segments. These are also referred to as tunnel segments.
Additionally, at an intermediate LSR, we model a connection as Additionally, at an intermediate LSR, we model a connection as
consisting of one or more in-segments and/or one or more consisting of one or more in-segments and/or one or more
out-segments. The binding or interconnection between in-segments and out-segments. The binding or interconnection between in-segments and
out-segments in performed using a cross-connect. draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 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 Switch 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) [GMPLSLSRMIB]
for the GMPLS-specific extensions to these objects. for 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
skipping to change at page 5, line 5 skipping to change at page 5, line 5
4.1. Summary of GMPLS Traffic Engineering MIB Module 4.1. Summary of GMPLS Traffic Engineering MIB Module
The following tables contain MIB objects for performing the actions The following tables contain MIB objects for performing the actions
listed above when they cannot be performed solely using MIB objects listed above when they cannot be performed solely using MIB objects
defined in MPLS-TE-STD-MIB [RFC3812]. defined in MPLS-TE-STD-MIB [RFC3812].
- Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific
tunnel configuration parameters. tunnel configuration parameters.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
- Tunnel specified, actual, and computed hop tables - Tunnel specified, actual, and computed hop tables
(gmplsTunnelHopTable, gmplsTunnelARHopTable, and (gmplsTunnelHopTable, gmplsTunnelARHopTable, and
gmplsTunnelCHopTable) for providing additional configuration of gmplsTunnelCHopTable) for providing additional configuration of
strict and loose source routed tunnel hops. strict and loose source routed tunnel hops.
- Performance and error reporting tables (gmplsTunnelReversePerfTable - Performance and error reporting tables (gmplsTunnelReversePerfTable
and gmplsTunnelErrorTable). and gmplsTunnelErrorTable).
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
skipping to change at page 6, line 5 skipping to change at page 6, line 5
and/or one in-segment terminating at that LSR. and/or one in-segment terminating at that LSR.
Three objects within this table utilize enumerations in order to map Three objects within this table utilize enumerations in order to map
to enumerations that are used in GMPLS signaling. In order to protect to enumerations that are used in GMPLS signaling. In order to protect
the GMPLS-TE-STD-MIB module from changes (in particular, extensions) the GMPLS-TE-STD-MIB module from changes (in particular, extensions)
to the range of enumerations supported by the signaling protocols, to the range of enumerations supported by the signaling protocols,
these MIB objects use Textual Conventions with values maintained by these MIB objects use Textual Conventions with values maintained by
IANA. For further details, see the IANA Considerations section of IANA. For further details, see the IANA Considerations section of
this document. this document.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 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
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
skipping to change at page 7, line 4 skipping to change at page 6, line 54
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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, and
slower than 650,000,000 bits/second, 32-bit packet counters MUST be slower than 650,000,000 bits/second, 32-bit packet counters MUST be
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
supported and 64-bit octet counters MUST be supported. For supported and 64-bit octet counters MUST be supported. For
interfaces that operate at 650,000,000 bits/second or faster, 64-bit interfaces that operate at 650,000,000 bits/second or faster, 64-bit
packet counters AND 64-bit octet counters MUST be supported. packet counters AND 64-bit octet counters MUST be supported.
6. Cross-referencing to the gmplsLabelTable 6. Cross-referencing to the gmplsLabelTable
The gmplsLabelTable is found in the GMPLS-LABEL-STD-MIB module in The gmplsLabelTable is found in the GMPLS-LABEL-STD-MIB module in
[GMPLSLSRMIB] and provides a way to model labels in a GMPLS system [GMPLSLSRMIB] and provides a way to model labels in a GMPLS system
where labels might not be simple 32 bit integers. where labels might not be simple 32 bit integers.
skipping to change at page 8, line 4 skipping to change at page 7, line 51
This provides both a good way to support legacy systems that This provides both a good way to support legacy systems that
implement the MPLS-TE-STD-MIB [RFC3812], and a significant implement the MPLS-TE-STD-MIB [RFC3812], and a significant
simplification in GMPLS systems that are limited to a single, simple simplification in GMPLS systems that are limited to a single, simple
label type. label type.
Note that gmplsLabelTable supports concatenated labels through the Note that gmplsLabelTable supports concatenated labels through the
use of a label sub-index (gmplsLabelSubindex). use of a label sub-index (gmplsLabelSubindex).
7. Example of GMPLS Tunnel Setup 7. Example of GMPLS Tunnel Setup
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
This section contains an example of which MIB objects should be This section contains an example of which MIB objects should be
modified to create a GMPLS tunnel. This example shows a best effort, modified to create a GMPLS tunnel. This example shows a best effort,
loosely routed, bidirectional traffic engineered tunnel, which spans loosely routed, bidirectional traffic engineered tunnel, which spans
two hops of a simple network, uses Generalized Label requests with two hops of a simple network, uses Generalized Label requests with
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-end" LSR. "head-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,
skipping to change at page 9, line 4 skipping to change at page 8, line 49
In gmplsTunnelTable(1,1,192.0.2.1,192.0.2.2): In gmplsTunnelTable(1,1,192.0.2.1,192.0.2.2):
{ {
gmplsTunnelUnnumIf = true (1), gmplsTunnelUnnumIf = true (1),
gmplsTunnelAttributes = labelRecordingRequired (1), gmplsTunnelAttributes = labelRecordingRequired (1),
gmplsTunnelLSPEncoding = tunnelLspLambda, gmplsTunnelLSPEncoding = tunnelLspLambda,
gmplsTunnelSwitchingType = lsc, gmplsTunnelSwitchingType = lsc,
gmplsTunnelLinkProtection = shared (2), gmplsTunnelLinkProtection = shared (2),
gmplsTunnelGPid = lambda, gmplsTunnelGPid = lambda,
gmplsTunnelSecondary = false (2), gmplsTunnelSecondary = false (2),
gmplsTunnelDirection = bidirectional (1) gmplsTunnelDirection = bidirectional (1)
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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,
skipping to change at page 10, line 4 skipping to change at page 9, line 47
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" as our tail end router. "192.0.2.2" as our tail end router.
In mplsTunnelHopTable: In mplsTunnelHopTable:
{ {
mplsTunnelHopListIndex = 1, mplsTunnelHopListIndex = 1,
mplsTunnelPathOptionIndex = 1, mplsTunnelPathOptionIndex = 1,
mplsTunnelHopIndex = 2, mplsTunnelHopIndex = 2,
mplsTunnelHopAddrType = ipV4 (1), mplsTunnelHopAddrType = ipV4 (1),
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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
skipping to change at page 11, line 4 skipping to change at page 11, line 4
No gmplsTunnelHopEntry is created for the second hop as it contains No gmplsTunnelHopEntry is created for the second hop as it contains
no special GMPLS features. no special GMPLS features.
Finally the mplsTunnelEntry is activated: Finally the mplsTunnelEntry is activated:
In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2) In mplsTunnelTable(1,1,192.0.2.1,192.0.2.2)
{ {
mplsTunnelRowStatus = active(1) mplsTunnelRowStatus = active(1)
} }
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 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 references to the following documents.
[RCF2205], [RFC2578], [RFC2579], [RFC2580], [RFC3209], [RFC3411], [RCF2205], [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
skipping to change at page 11, line 45 skipping to change at page 11, line 45
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
"200604060001Z" -- 06 April 2006 00:00:01 GMT "200609060001Z" -- 06 September 2006 00:00:01 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working "IETF Common Control And Measurement Plane (CCAMP) Working
Group" Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 direct to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2006). This version of "Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC XXX; see the RFC itself for this MIB module is part of RFC XXX; see the RFC itself for
full legal notices. full legal notices.
-- RFC Ed. Please replace XXX above with the correct RFC number and -- RFC Ed. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
This MIB module contains managed object definitions This MIB module contains managed object definitions
for GMPLS Traffic Engineering (TE) as defined in: for GMPLS Traffic Engineering (TE) as defined in:
1. Generalized Multi-Protocol Label Switching (GMPLS) 1. Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor), Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003. RFC 3471, January 2003.
2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, 2. Generalized MPLS Signaling - RSVP-TE Extensions, Berger,
L. (Editor), RFC 3473, January 2003. L. (Editor), RFC 3473, January 2003.
" "
REVISION REVISION
"200604060001Z" -- 06 April 2006 00:00:01 GMT "200609060001Z" -- 06 September 2006 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXX." "Initial version issued as part of RFC XXX."
::= { mplsStdMIB XXX } ::= { mplsStdMIB YYY }
-- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note.
-- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note -- and remove this note
gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 }
gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 } gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeStdMIB 1 }
gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 } gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeStdMIB 2 }
gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 } gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeStdMIB 3 }
gmplsTunnelsConfigured OBJECT-TYPE gmplsTunnelsConfigured OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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)."
::= { gmplsTeScalars 2 } ::= { gmplsTeScalars 2 }
skipping to change at page 14, line 5 skipping to change at page 14, line 5
::= { 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-15.txt April 20, 2006 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 5 skipping to change at page 14, line 54
"Denotes whether or not this tunnel corresponds to an unnumbered "Denotes whether or not this tunnel corresponds to an unnumbered
interface represented by an entry in the interfaces group table interface represented by an entry in the interfaces group table
(the ifTable) with ifType set to mpls (166). (the ifTable) with ifType set to mpls (166).
This object is only used if mplsTunnelIsIf is set to 'true'. 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.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 16, line 4 skipping to change at page 15, line 52
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 }
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
::= { 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.
skipping to change at page 17, line 4 skipping to change at page 16, line 52
preempted when the links carrying the (primary) traffic being preempted when the links carrying the (primary) traffic being
protected fail. protected fail.
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 18, line 5 skipping to change at page 17, line 54
DEFVAL { unknown } DEFVAL { unknown }
::= { gmplsTunnelEntry 6 } ::= { gmplsTunnelEntry 6 }
gmplsTunnelSecondary OBJECT-TYPE gmplsTunnelSecondary OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates that the requested LSP is a secondary LSP. "Indicates that the requested LSP is a secondary LSP.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
This object is only meaningful if gmplsTunnelLSPEncoding is not This object is only meaningful if gmplsTunnelLSPEncoding is not
set to 'tunnelLspNotGmpls'." set to 'tunnelLspNotGmpls'."
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 19, line 4 skipping to change at page 18, line 51
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 CSPF
will calculate the remainder of the path. will calculate the remainder of the path.
explicit explicit
The user specifies the entire path for the tunnel to The user specifies the entire path for the tunnel to
take. This path may contain strict or loose hops. take. This path may contain strict or loose hops.
Evaluation of the explicit route will be performed Evaluation of the explicit route will be performed
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 gmplsTunnelTable for a tunnel,
gmplsTunnelPathComp MUST be used and any corresponding gmplsTunnelPathComp MUST be used and any corresponding
skipping to change at page 20, line 5 skipping to change at page 19, line 53
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 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.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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, gmplsTunnelUpstreamNotifyRecipient. If this object is set to 0,
the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to the value of gmplsTunnelUpstreamNotifyRecipient MUST be set to
unknown(0)." unknown(0)."
REFERENCE REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. " section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0 DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 11 } ::= { gmplsTunnelEntry 11 }
skipping to change at page 21, line 4 skipping to change at page 21, line 4
This object is interpreted in the context of the value of This object is interpreted in the context of the value of
gmplsTunnelSendResvNotifyRecipientType. If this object is set to gmplsTunnelSendResvNotifyRecipientType. If this object is set to
0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be 0, the value of gmplsTunnelSendResvNotifyRecipientType MUST be
set to unknown(0)." set to unknown(0)."
REFERENCE REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 4.2. " section 4.2. "
DEFVAL { '00000000'H } -- 0.0.0.0 DEFVAL { '00000000'H } -- 0.0.0.0
::= { gmplsTunnelEntry 13 } ::= { gmplsTunnelEntry 13 }
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 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 22, line 4 skipping to change at page 21, line 53
STATUS current STATUS current
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 23, line 4 skipping to change at page 23, line 4
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-15.txt April 20, 2006 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, SONET
resource usage). Such parameters can be supplied in an external resource usage). Such parameters can be supplied in an external
table and referenced from here. table and referenced from here.
skipping to change at page 24, line 4 skipping to change at page 24, line 4
mplsTunnelHopRowStatus in the corresponding entry in mplsTunnelHopRowStatus in the corresponding entry in
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, nor to modify an existing row, when the
corresponding mplsTunnelHopRowStatus has value active(1)." corresponding mplsTunnelHopRowStatus has value active(1)."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) "1. Multiprotocol Label Switching (MPLS) Traffic Engineering (TE)
Management Information Base (MIB), RFC 3812. Management Information Base (MIB), RFC 3812.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473. 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473.
" "
::= { gmplsTeObjects 2 } ::= { gmplsTeObjects 2 }
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 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
skipping to change at page 25, line 4 skipping to change at page 25, line 4
gmplsTunnelHopExplicitForwardLabel or gmplsTunnelHopExplicitForwardLabel or
gmplsTunnelHopExplicitForwardLabelPtr, and gmplsTunnelHopExplicitForwardLabelPtr, and
gmplsTunnelHopExplicitReverseLabel or gmplsTunnelHopExplicitReverseLabel or
gmplsTunnelHopExplicitReverseLabel objects. gmplsTunnelHopExplicitReverseLabel 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-15.txt April 20, 2006 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."
skipping to change at page 26, line 4 skipping to change at page 25, line 54
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
row in another MIB table (such as the gmplsLabelTable of the row in another MIB table (such as the gmplsLabelTable of the
GMPLS-LABEL-STD-MIB) that contains the label to use on this hop GMPLS-LABEL-STD-MIB) that contains the label to use on this hop
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
skipping to change at page 27, line 4 skipping to change at page 26, line 52
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 mplsTunnelARHopTable (if the tables are supported and if the
signaling protocol is recording actual route information) signaling protocol is recording actual route information)
contain the actual route of the whole tunnel. If the signaling contain the actual route of the whole tunnel. If the signaling
protocol is not recording the actual route, this table MAY protocol is not recording the actual route, this table MAY
report the information from the gmplsTunnelHopTable or the report the information from the gmplsTunnelHopTable or the
gmplsTunnelCHopTable. gmplsTunnelCHopTable.
skipping to change at page 28, line 5 skipping to change at page 27, line 51
} }
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.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
For the Present bits, a set bit indicates that a label is For the Present bits, a set bit indicates that a label is
present for this hop in the route. For the Global bits, a set present for this hop in the route. For the Global bits, a set
bit indicates that the label comes from the Global Label Space. bit indicates that the label comes from the Global Label Space.
A clear bit indicates that this is a Per-Interface label. A A clear bit indicates that this is a Per-Interface label. A
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
Global bit only has meaning if the corresponding Present bit is Global bit only has meaning if the corresponding Present bit is
set." set."
::= { gmplsTunnelARHopEntry 1 } ::= { gmplsTunnelARHopEntry 1 }
gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE gmplsTunnelARHopExplicitForwardLabel OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the gmplsTunnelARHopLabelStatuses object indicates that a "If the gmplsTunnelARHopLabelStatuses object indicates that a
skipping to change at page 29, line 4 skipping to change at page 28, line 49
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."
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
::= { 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 the
GMPLS-LABEL-STD-MIB) that contains the label in use on this hop GMPLS-LABEL-STD-MIB) that contains the label in use on this hop
skipping to change at page 30, line 4 skipping to change at page 29, line 52
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 4.4.1." section 4.4.1."
::= { gmplsTunnelARHopEntry 6 } ::= { gmplsTunnelARHopEntry 6 }
gmplsTunnelCHopTable OBJECT-TYPE gmplsTunnelCHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsTunnelCHopEntry SYNTAX SEQUENCE OF GmplsTunnelCHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The gmplsTunnelCHopTable sparsely extends the "The gmplsTunnelCHopTable sparsely extends the
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 mplsTunnelCHopTable of MPLS-TE-STD-MIB. It is used to indicate
additional information about the hops of a GMPLS tunnel defined
mplsTunnelCHopTable in mplsTunnelTable and gmplsTunnelTable, as computed by a
of MPLS-TE-STD-MIB. It is used to indicate additional
information about the hops of a GMPLS tunnel defined in
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
mplsTunnelCHopTable. It is acceptable for some rows in mplsTunnelCHopTable. It is acceptable for some rows in
mplsTunnelCHopTable to have corresponding entries in this table mplsTunnelCHopTable to have corresponding entries in this table
and some to have no corresponding entry in this table. and some to have no corresponding entry in this table.
Please note that since the information necessary to build Please note that since the information necessary to build
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.
skipping to change at page 31, line 4 skipping to change at page 30, line 49
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 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 {
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 32, line 4 skipping to change at page 31, line 47
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 the
GMPLS-LABEL-STD-MIB) that contains the label to use on this hop GMPLS-LABEL-STD-MIB) that contains the label to use on this hop
in the forward direction. in the forward direction.
If the gmplsTunnelCHopLabelStatuses object indicates that a If the gmplsTunnelCHopLabelStatuses object indicates that a
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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
skipping to change at page 33, line 5 skipping to change at page 32, line 50
"This table augments the gmplsTunnelTable to provides "This table augments the gmplsTunnelTable to provides
per-tunnel packet performance information for the reverse per-tunnel packet performance information for the reverse
direction of a bidirectional tunnel. It can be seen as direction of a bidirectional tunnel. It can be seen as
supplementing the mplsTunnelPerfTable which augments the supplementing the mplsTunnelPerfTable which augments the
mplsTunnelTable. mplsTunnelTable.
For links that do not transport packets, these packet counters For links that do not transport packets, these packet counters
cannot be maintained. For such links, attempts to read the cannot be maintained. For such links, attempts to read the
objects in this table will return noSuchInstance. objects in this table will return noSuchInstance.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 34, line 4 skipping to change at page 33, line 46
For links that do not transport packets, this packet counter For links that do not transport packets, this packet counter
cannot be maintained. For such links, this value will return a cannot be maintained. For such links, this value will return a
noSuchInstance." noSuchInstance."
::= { gmplsTunnelReversePerfEntry 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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 a
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 a noSuchInstance."
skipping to change at page 35, line 4 skipping to change at page 34, line 45
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 a
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 }
skipping to change at page 36, line 4 skipping to change at page 35, line 44
gmplsTunnelErrorLastTime TimeStamp, gmplsTunnelErrorLastTime TimeStamp,
gmplsTunnelErrorReporterType InetAddressType, gmplsTunnelErrorReporterType InetAddressType,
gmplsTunnelErrorReporter InetAddress, gmplsTunnelErrorReporter InetAddress,
gmplsTunnelErrorCode Unsigned32, gmplsTunnelErrorCode Unsigned32,
gmplsTunnelErrorSubcode Unsigned32, gmplsTunnelErrorSubcode Unsigned32,
gmplsTunnelErrorTLVs OCTET STRING, gmplsTunnelErrorTLVs OCTET STRING,
gmplsTunnelErrorHelpString SnmpAdminString gmplsTunnelErrorHelpString SnmpAdminString
} }
gmplsTunnelErrorLastErrorType OBJECT-TYPE gmplsTunnelErrorLastErrorType OBJECT-TYPE
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
SYNTAX INTEGER { SYNTAX INTEGER {
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 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
skipping to change at page 37, line 4 skipping to change at page 36, line 43
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 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."
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
::= { 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.
skipping to change at page 37, line 48 skipping to change at page 37, line 35
"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
gmplsTunnelErrorLastErrorType. If the value of gmplsTunnelErrorLastErrorType. If the value of
gmplsTunnelErrorLastErrorType is noError (0) the value of this gmplsTunnelErrorLastErrorType is noError (0) the value of this
object should be 0 and should be ignored. If the value of object should be 0 and should be ignored. If the value of
gmplsTunnelErrorLastErrorType is protocol (2) the error should gmplsTunnelErrorLastErrorType is protocol (2) the error should
be interpreted in the context of the signling protocol be interpreted in the context of the signaling protocol
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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
skipping to change at page 39, line 4 skipping to change at page 38, line 44
references. A value of zero in the first octet indicates that no references. A value of zero in the first octet indicates that no
TLVs are present." TLVs are present."
REFERENCE REFERENCE
"1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, "1. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 8.2." section 8.2."
::= { gmplsTunnelErrorEntry 7 } ::= { gmplsTunnelErrorEntry 7 }
gmplsTunnelErrorHelpString OBJECT-TYPE gmplsTunnelErrorHelpString OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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,
skipping to change at page 40, line 4 skipping to change at page 39, line 44
single tunnel. If the tunnel has an entry in gmplsTunnelTable single tunnel. If the tunnel has an entry in gmplsTunnelTable
an implementation SHOULD use gmplsTunnelDown for all tunnel an implementation SHOULD use gmplsTunnelDown for all tunnel
down events and SHOULD NOT use mplsTunnelDown. down events and SHOULD NOT use mplsTunnelDown.
This notification is subject to the control of the This notification is subject to the control of the
mplsTunnelNotificationEnable. When that object is set to mplsTunnelNotificationEnable. When that object is set to
false(2) then the notification must not be issued. false(2) then the notification must not be issued.
Further, this notification is also subject to Further, this notification is also subject to
mplsTunnelNotificationMaxRate. That object indicates the mplsTunnelNotificationMaxRate. That object indicates the
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 notificaitons 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 41, line 4 skipping to change at page 40, line 43
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsTunnelGroup, mplsTunnelGroup,
mplsTunnelScalarGroup mplsTunnelScalarGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsTunnelGroup, gmplsTunnelGroup,
gmplsTunnelScalarGroup gmplsTunnelScalarGroup
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
} }
GROUP gmplsTunnelSignaledGroup GROUP gmplsTunnelSignaledGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support signaled "This group is mandatory for devices which support signaled
tunnel set up, in addition to gmplsTunnelGroup. The following tunnel set up, in addition to gmplsTunnelGroup. The following
constraints apply: constraints apply:
mplsTunnelSignallingProto should be at least read-only mplsTunnelSignallingProto should be at least read-only
returning a value of ldp(2), or rsvp(3)." returning a value of ldp(2), or rsvp(3)."
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 which 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.
skipping to change at page 42, line 4 skipping to change at page 41, line 40
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 which support signaled
tunnel set up, in addition to gmplsTunnelGroup. The following tunnel set up, in addition to gmplsTunnelGroup. The following
constraints apply: constraints apply:
mplsTunnelSignallingProto should be at least read-only mplsTunnelSignallingProto should be at least read-only
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 which 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 43, line 4 skipping to change at page 42, line 38
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelSecondary OBJECT gmplsTunnelSecondary
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsTunnelDirection OBJECT gmplsTunnelDirection
MIN-ACCESS read-only MIN-ACCESS read-only
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
DESCRIPTION DESCRIPTION
"Only forward (0) is required." "Only forward (0) is required."
OBJECT gmplsTunnelPathComp OBJECT gmplsTunnelPathComp
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only explicit (2) is required." "Only explicit (2) is required."
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
skipping to change at page 44, line 4 skipping to change at page 43, line 40
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 45, line 4 skipping to change at page 44, line 41
"Write access is not required." "Write access is not required."
-- gmplsTunnelARHopTable -- gmplsTunnelARHopTable
-- all objects have max access read-only -- all objects have max access read-only
-- gmplsTunnelCHopTable -- gmplsTunnelCHopTable
-- all objects have max access read-only -- all objects have max access read-only
-- gmplsTunnelReversePerfTable -- gmplsTunnelReversePerfTable
-- all objects have max access read-only -- all objects have max access read-only
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
-- 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 45, line 39
persistent or non-persistent, etc.), the persistent or non-persistent, etc.), the
gmplsTunnelSignaledGroup group is mandatory." gmplsTunnelSignaledGroup group is mandatory."
::= { gmplsTeGroups 1 } ::= { gmplsTeGroups 1 }
gmplsTunnelSignaledGroup OBJECT-GROUP gmplsTunnelSignaledGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsTunnelAttributes, gmplsTunnelAttributes,
gmplsTunnelLSPEncoding, gmplsTunnelLSPEncoding,
gmplsTunnelSwitchingType, gmplsTunnelSwitchingType,
gmplsTunnelLinkProtection, gmplsTunnelLinkProtection,
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
gmplsTunnelGPid, gmplsTunnelGPid,
gmplsTunnelSecondary, gmplsTunnelSecondary,
gmplsTunnelPathComp, gmplsTunnelPathComp,
gmplsTunnelUpstreamNotifyRecipientType, gmplsTunnelUpstreamNotifyRecipientType,
gmplsTunnelUpstreamNotifyRecipient, gmplsTunnelUpstreamNotifyRecipient,
gmplsTunnelSendResvNotifyRecipientType, gmplsTunnelSendResvNotifyRecipientType,
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 46, line 38
gmplsTunnelARHopExplicitForwardLabel, gmplsTunnelARHopExplicitForwardLabel,
gmplsTunnelARHopExplicitForwardLabelPtr, gmplsTunnelARHopExplicitForwardLabelPtr,
gmplsTunnelARHopExplicitReverseLabel, gmplsTunnelARHopExplicitReverseLabel,
gmplsTunnelARHopExplicitReverseLabelPtr, gmplsTunnelARHopExplicitReverseLabelPtr,
gmplsTunnelARHopProtection, gmplsTunnelARHopProtection,
gmplsTunnelCHopLabelStatuses, gmplsTunnelCHopLabelStatuses,
gmplsTunnelCHopExplicitForwardLabel, gmplsTunnelCHopExplicitForwardLabel,
gmplsTunnelCHopExplicitForwardLabelPtr, gmplsTunnelCHopExplicitForwardLabelPtr,
gmplsTunnelCHopExplicitReverseLabel, gmplsTunnelCHopExplicitReverseLabel,
gmplsTunnelCHopExplicitReverseLabelPtr gmplsTunnelCHopExplicitReverseLabelPtr
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The objects in this group are optional." "The objects in this group are optional."
::= { gmplsTeGroups 4 } ::= { gmplsTeGroups 4 }
gmplsTeNotificationGroup NOTIFICATION-GROUP gmplsTeNotificationGroup NOTIFICATION-GROUP
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 the MPLS-TE-STD-MIB [RFC3812] are potentially useful
for monitoring of MPLS and GMPLS tunnels. These MIB modules can also for monitoring of MPLS and GMPLS tunnels. These MIB modules can also
be used for configuration of certain objects, and anything that can be used for configuration of certain objects, and anything that can
be configured can be incorrectly configured, with potentially be configured can be incorrectly configured, with potentially
disastrous results. disastrous results.
skipping to change at page 48, line 4 skipping to change at page 47, line 35
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 especially
true if a tunnel has already been established. 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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
sensitivity/vulnerability: sensitivity/vulnerability:
o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable,
gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, and the gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, and the
gmplsTunnelErrorTable collectively show the tunnel network gmplsTunnelErrorTable collectively show the tunnel network
topology and status. If an Administrator does not want to reveal topology and status. If an Administrator does not want to reveal
this information, then these tables should be considered this information, then these tables should be considered
sensitive/vulnerable. sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security. Even
if the network itself is secure (for example by using IPSec), even if the network itself is secure (for example by using IPsec), even
then, there is no control as to who on the secure network is allowed then, there is no control as to who on the secure network is allowed
to access and GET/SET (read/change/create/delete) the objects in to access and GET/SET (read/change/create/delete) the objects in
these MIB modules. these MIB modules.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
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 Baktha contributions during an early implementation, and to Lars Eggert,
Muralidharan, Tom Petch, Dave Thaler and Bert Wijnen for their review Baktha Muralidharan, Tom Petch, Dan Romascanu, Dave Thaler and
comments. Bert 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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006 IANA is requested to root MIB objects in the MIB modules contained in
this document according to the sections below.
11.1. IANA Considerations for GMPLS-TE-STD-MIB
IANA is requested to root MIB objects in the GMPLS-TE-STD-MIB module
contained in this document under the mplsStdMIB subtree.
Upon approval of this document, the IANA will make the following
assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located
at http://www.iana.org/assignments/smi-numbers in table:
...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
Decimal Name References
------- ----- ----------
TBD+3 GMPLS-LSR-STD-MIB [RFC-ccamp-gmpls-lsr-mib]
-- RFC Editor. Please replace YYY above with assigned OID and remove
-- this note
IANA is requested to root MIB objects in the MIB module contained in
this document under the mplsStdMIB subtree.
In the future, GMPLS related standards track MIB modules should be In the future, GMPLS related standards track MIB modules should be
rooted under the mplsStdMIB (sic) subtree. IANA has been requested to rooted under the mplsStdMIB (sic) subtree. IANA has been requested to
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
manage that namespace in the SMI Numbers registry [RFC3811]. New manage that namespace in the SMI Numbers registry [RFC3811]. New
assignments can only be made via a Standards Action as specified in assignments can only be made via a Standards Action as specified in
[RFC2434]. [RFC2434].
11.1. IANA Considerations for GMPLS-TE-STD-MIB
The IANA is requested to assign { mplsStdMIB XXX } to the
GMPLS-TE-STD-MIB module specified in this document, and to record
the assignment in the SMI Numbers registry.
11.2. Dependence on IANA MIB Modules 11.2. Dependence on IANA MIB Modules
Three MIB objects in this MIB module (gmplsTunnelLSPEncoding, Three MIB objects in the GMPLS-LSR-STD-MIB module defined in this
gmplsTunnelSwitchingType, and gmplsTunnelGPid) use textual document (gmplsTunnelLSPEncoding, gmplsTunnelSwitchingType, and
conventions imported from the IANA-GMPLS-TC-MIB. The purpose of gmplsTunnelGPid) use textual conventions imported from the
defining these textual conventions in a separate MIB module is to IANA-GMPLS-TC-MIB module. The purpose of defining these textual
allow additional values to be defined without having to issue a new conventions in a separate MIB module is to allow additional values to
version of this document. The Internet Assigned Numbers Authority be defined without having to issue a new version of this document.
(IANA) is responsible for the assignment of all Internet numbers; it The Internet Assigned Numbers Authority (IANA) is responsible for the
will administer the values associated with these textual conventions. assignment of all Internet numbers; it will administer the values
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 the IANA-GMPLS-TC-MIB are
outlined in the DESCRIPTION clause associated with its outlined in the DESCRIPTION clause associated with its
MODULE-IDENTITY statement. MODULE-IDENTITY statement.
The current versions of the IANA-GMPLS-TC-MIB can be accessed from The current versions of the IANA-GMPLS-TC-MIB can be accessed from
the IANA home page at: "http://www.iana.org/". the 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 is a temporary section intended to supply the base definition of
an IANA MIB module. The normal procedure is that this MIB module is an IANA MIB module. The normal procedure is that this MIB module is
moved into the direct control of IANA, at which time this section moved into the direct control of IANA, at which time this section
should be deleted from this document. should be deleted from this document.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module IANA is requested to assign an OID to the IANA-GMPLS-TC-MIB module
specified in this document as { transmission YYY }. specified in this document as { mib-2 ZZZ }.
-- RFC Editor. -- RFC Editor.
-- Please replace ZZZ in the text below with assigned OID and remove
-- this note.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN IANA-GMPLS-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, transmission 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
"200604060001Z" -- 06 April 2006 00:00:01 GMT "200609060001Z" -- 06 September 2006 00:00:01 GMT
ORGANIZATION ORGANIZATION
"IANA" "IANA"
CONTACT-INFO CONTACT-INFO
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
Postal: USC/Information Sciences Institute Postal: USC/Information Sciences Institute
4676 Admiralty Way, Marina del Rey, CA 90292 4676 Admiralty Way, Marina del Rey, CA 90292
Tel: +1 310 822 1511 Tel: +1 310 822 1511
E-Mail: iana@isi.edu" E-Mail: iana@isi.edu"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2006). The initial version "Copyright (C) The Internet Society (2006). The initial version
of this MIB module was published in RFC YYY. For full legal of this MIB module was published in RFC WWW. For full legal
notices see the RFC itself. Supplementary information notices see the RFC itself. Supplementary information
may be available on: may be available on:
http://www.ietf.org/copyrights/ianamib.html" http://www.ietf.org/copyrights/ianamib.html"
-- RFC Editor. Please replace WWW above with the correct RFC number
-- Your actions may vary depending on how IANA chooses to handle -- Your actions may vary depending on how IANA chooses to handle
-- this IANA MIB. -- this IANA MIB.
-- Please remove this note. -- Please remove this note.
REVISION REVISION
"200604060001Z" -- 06 April 2006 00:00:01 GMT "200609060001Z" -- 06 September 2006 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC YYY." "Initial version issued as part of RFC WWW."
::= { transmission YYY } ::= { mib-2 ZZZ }
-- RFC Editor. Please replace WWW above with the correct RFC number
-- Your actions may vary depending on how IANA chooses to handle
-- this IANA MIB.
-- Please remove this note.
-- RFC Editor. Please replace ZZZ above with the OID assigned by IANA
-- Please remove this note. -- Please remove this note.
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 values in the LSP
Encoding Types sub-registry. Encoding Types sub-registry.
skipping to change at page 52, line 4 skipping to change at page 51, line 53
tunnelLspFiber (9), -- Fiber tunnelLspFiber (9), -- Fiber
-- the value 10 is deprecated -- the value 10 is deprecated
tunnelLspFiberChannel (11), -- Fiber Channel tunnelLspFiberChannel (11), -- Fiber Channel
tunnelDigitalPath (12), -- Digital Path tunnelDigitalPath (12), -- Digital Path
tunnelOpticalChannel (13) -- Optical Channel tunnelOpticalChannel (13) -- Optical Channel
} }
IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION IANAGmplsSwitchingTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
"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 IANA
in step with the Switching Types sub-registry and using the in step with the Switching Types sub-registry and using the
same registry management rules. However, the actual values same registry management rules. However, the actual values
used in this textual convention are solely within the used in this textual convention are solely within the
purview of IANA and do not necessarily match the values in purview of IANA and do not necessarily match the values in
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
skipping to change at page 53, line 5 skipping to change at page 52, line 51
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.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 IANA
in step with the Generalized PIDs (G-PID) sub-registry and in step with the Generalized PIDs (G-PID) sub-registry and
using the same registry management rules. However, the 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 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
skipping to change at page 54, line 4 skipping to change at page 53, line 48
asynchE1(13), asynchE1(13),
bytesynchE1(14), bytesynchE1(14),
bytesynch31ByDS0(15), bytesynch31ByDS0(15),
asynchDS1T1(16), asynchDS1T1(16),
bitsynchDS1T1(17), bitsynchDS1T1(17),
bytesynchDS1T1(18), bytesynchDS1T1(18),
vc1vc12(19), vc1vc12(19),
reservedByRFC3471second(20), reservedByRFC3471second(20),
reservedByRFC3471third(21), reservedByRFC3471third(21),
ds1SFAsynch(22), ds1SFAsynch(22),
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 55, line 4 skipping to change at page 54, line 46
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 Admin
Status Flags sub-registry of the GMPLS Signaling Parameters Status Flags 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 IANA
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
in step with the Admin Status Flags sub-registry and using in step with the Admin Status Flags sub-registry and using
the same registry management rules. However, the actual the same registry management rules. However, the actual
values used in this textual convention are solely within values used in this textual convention are solely within
the purview of IANA and do not necessarily match the values the purview of IANA and do not necessarily match the values
in the values in the Admin Status Flags sub-registry. in the values in the Admin Status Flags sub-registry.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
-- RFC Editor / IANA note -- RFC Editor / IANA note
-- At the time of writing, the referenced Admin Status Flags -- At the time of writing, the referenced Admin Status Flags
-- sub-registry has not been created. -- sub-registry has not been created.
-- It is not requested in RFC 3471 (the base reference for this protocol -- It is not requested in RFC 3471 (the base reference for this protocol
-- element). But it is requested in two I-Ds that are ahead of this MIB -- element). But it is requested in two I-Ds that are ahead of this MIB
-- module in the IETF process -- module in the IETF process
-- draft-ietf-ccamp-gmpls-recovery-e2e-signaling -- draft-ietf-ccamp-gmpls-recovery-e2e-signaling
-- draft-ietf-ccamp-gmpls-alarm-spec -- draft-ietf-ccamp-gmpls-alarm-spec
-- Note, however, that at this stage no request is made to IANA for the -- Note, however, that at this stage no request is made to IANA for the
-- definition of values in the textual convention to match any of the -- definition of values in the textual convention to match any of the
skipping to change at page 56, line 4 skipping to change at page 55, line 50
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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
skipping to change at page 56, line 43 skipping to change at page 56, line 36
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. Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version Jamin, "Resource ReSerVation Protocol (RSVP) -- Version
1 Functional Specification", RFC 2205, September 1997. 1 Functional Specification", RFC 2205, September 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance Statements J., Rose, M., and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999. for SMIv2", STD 58, RFC 2580, April 1999.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC 3031, "Multiprotocol 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., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP V., 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
skipping to change at page 58, line 4 skipping to change at page 57, line 51
[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 (LSR) Router Management Information Base (MIB)", RFC
3813, June 2004. 3813, June 2004.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Switching (GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in
Support of Generalized Multi-Protocol Label Switching", Support of Generalized Multi-Protocol Label Switching",
RFC 4202, October 2005. RFC 4202, October 2005.
draft-ietf-ccamp-gmpls-te-mib-16.txt September 2006
[GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol [GMPLSLSRMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol
Label Switching (GMPLS) Label Switching Router (LSR) Label Switching (GMPLS) Label Switching Router (LSR)
Management Information Base", Management Information Base",
draft-ietf-ccamp-gmpls-lsr-mib, work in progress. draft-ietf-ccamp-gmpls-lsr-mib, work in progress.
[GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual
Conventions for Multiprotocol Label Switching (MPLS)
Management", draft-ietf-ccamp-gmpls-tc-mib, work in
progress.
12.2. Informative References 12.2. Informative References
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
skipping to change at page 59, line 4 skipping to change at page 58, line 43
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
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
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 14. Intellectual Property Considerations
skipping to change at page 60, line 5 skipping to change at page 59, line 38
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.
draft-ietf-ccamp-gmpls-te-mib-15.txt April 20, 2006
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The Internet Society (2006). 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,
 End of changes. 141 change blocks. 
159 lines changed or deleted 173 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/