draft-ietf-ccamp-gmpls-lsr-mib-05.txt   draft-ietf-ccamp-gmpls-lsr-mib-06.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: December 2004 Cheenu Srinivasan Expires: April 2005 Adrian Farrel, Ed.
Bloomberg L.P.
Adrian Farrel
Old Dog Consulting Old Dog Consulting
Tim Hall October 2004
Ed Harrison
Data Connection Ltd.
June 2004
Generalized Multiprotocol Label Switching (GMPLS) Generalized Multiprotocol Label Switching (GMPLS)
Label Switching Router (LSR) Management Information Base Label Switching Router (LSR) Management Information Base
draft-ietf-ccamp-gmpls-lsr-mib-05.txt draft-ietf-ccamp-gmpls-lsr-mib-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC 2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
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 to configure and/or In particular, it describes managed objects to configure and/or
monitor a Generalized Multiprotocol Label Switching (GMPLS) Label monitor a Generalized Multiprotocol Label Switching (GMPLS) Label
Switching Router (LSR). Switching Router (LSR).
Table of Contents Table of Contents
1. Introduction 2 1. Introduction ..................................... 2
1.1. Migration Strategy 2 1.1. Migration Strategy ....................... ..... 2
2. Terminology 3 2. Terminology ...................................... 3
3. The SNMP Management Framework 3 3. The SNMP Management Framework .................... 3
4. Outline 3 4. Outline .......................................... 3
4.1. Summary of the GMPLS LSR MIB Module 4 4.1. Summary of the GMPLS LSR MIB Module ............ 4
4.1.1 Summary of the GMPLS LSR MIB Module 4 4.1.1 Summary of the GMPLS LSR MIB Module ........... 4
4.1.2 Summary of the GMPLS Label MIB Module 4 4.1.2 Summary of the GMPLS Label MIB Module ......... 5
5. Bidirectional LSPs 5 5. Bidirectional LSPs ............................... 5
6. Example of LSP Setup 5 6. Example of LSP Setup ............................. 5
7. GMPLS Label Switching Router MIB Definitions 9 7. GMPLS Label Switching Router MIB Definitions ..... 9
8. GMPLS Label MIB Definitions 18 8. GMPLS Label MIB Definitions ..................... 19
9. Security Considerations 29 9. Security Considerations ......................... 32
10. Acknowledgments 30 10. Acknowledgments ................................ 34
11. IANA Considerations 30 11. IANA Considerations ............................ 34
11.1. IANA Considerations for GMPLS-LSR-STD-MIB 30 11.1. IANA Considerations for GMPLS-LSR-STD-MIB .... 34
11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB 31 11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB .. 34
12. References 31 12. References ..................................... 34
12.1. Normative References 31 12.1. Normative References ......................... 34
12.2. Informational References 32 12.2. Informational References ..................... 36
13. Authors' Addresses 33 13. Authors' Addresses ............................. 37
14. Full Copyright Statement 33 14. Full Copyright Statement ....................... 37
15. Intellectual Property Notice 34 15. Intellectual Property Notice ................... 38
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling a In particular, it describes managed objects for modeling a
Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label
Switching Router (LSR). Switching Router (LSR).
Comments should be made directly to the CCAMP mailing list at Comments should be made directly to the CCAMP mailing list at
ccamp@ops.ietf.org. ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference document are to be interpreted as described in BCP 14, RFC 2119,
[RFC2119]. reference [RFC2119].
1.1. Migration Strategy 1.1. Migration Strategy
There are two MIB modules in this document. The GMPLS LSR MIB module There are two MIB modules in this document. The GMPLS LSR MIB module
extends the LSR MIB module defined for use with MPLS [LSRMIB]. The extends the LSR MIB module defined for use with MPLS [RFC3813]. The
only changes made are additions for support of GMPLS or changes that only changes made are additions for support of GMPLS or changes that
are necessary to support the increased complexity of a GMPLS system. are necessary to support the increased complexity of a GMPLS system.
The GMPLS Label MIB module may be referenced using a row pointer from The GMPLS Label MIB module may be referenced using a row pointer from
objects within the LSR MIB module. objects within the LSR MIB module.
The companion document modeling and managing GMPLS based traffic The companion document modeling and managing GMPLS based traffic
engineering [GMPLSTEMIB] extends the MPLS TE MIB module [TEMIB] with engineering [GMPLSTEMIB] extends the MPLS TE MIB module [RFC3812]
the same intentions. with the same intentions.
Textual conventions and OBJECT-IDENTIFIERS are defined in Textual conventions and OBJECT-IDENTIFIERS are defined in
[GMPLSTCMIB] which extends the set of textual conventions originally [GMPLSTCMIB] which extends the set of textual conventions originally
defined in [TCMIB]. defined in [RFC3811].
2. Terminology 2. Terminology
This document uses terminology from the document describing the MPLS This document uses terminology from the document describing the MPLS
architecture [RFC3031] and the GMPLS architecture [GMPLSArch]. architecture [RFC3031] and the GMPLS architecture [GMPLSArch].
A label switched path (LSP) is modeled as a connection consisting of A label switched path (LSP) is modeled as a connection consisting of
one or more incoming segments (in-segments) and/or one or more one or more incoming segments (in-segments) and/or one or more
outgoing segments (out-segments) at an LSR. The association or outgoing segments (out-segments) at an LSR. The association or
interconnection of the in-segments and out-segments is accomplished interconnection of the in-segments and out-segments is accomplished
skipping to change at page 3, line 36 skipping to change at page 3, line 44
3. The SNMP Management Framework 3. The SNMP Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a Structure of Management Information (SMI). This memo specifies a MIB
MIB module that is compliant to the SMIv2, which is described in STD module that is compliant to the SMIv2, which is described in STD 58,
58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
2580 [RFC2580]. [RFC2580].
4. Outline 4. Outline
Configuring statically provisioned GMPLS LSPs through an LSR involves Configuring statically provisioned GMPLS LSPs through an LSR involves
the following steps: the following steps:
- Configuring an interface using the MPLS LSR MIB module. - Configuring an interface using the MPLS LSR MIB module.
- Enabling GMPLS on GMPLS capable interfaces using this MIB module. - Enabling GMPLS on GMPLS capable interfaces using this MIB module.
skipping to change at page 5, line 10 skipping to change at page 5, line 22
bit-by-bit interpretations according to the use that is made of bit-by-bit interpretations according to the use that is made of
them. them.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
5. Bidirectional LSPs 5. Bidirectional LSPs
This MIB module supports bidirectional LSPs as required for GMPLS. This MIB module supports bidirectional LSPs as required for GMPLS.
A single value of mplsXCIndex is shared by all of the segments for A single value of mplsXCIndex is shared by all of the segments for
the entire bidirectional LSP. This facilitates a simple reference the entire bidirectional LSP. This facilitates a simple reference
from [TEMIB] and [GMPLSTEMIB], and makes fate-sharing more obvious. from [RFC3812] and [GMPLSTEMIB], and makes fate-sharing more obvious.
It is, however, important that the direction of segments is It is, however, important that the direction of segments is
understood to avoid connecting all in-segments to all out-segments. understood to avoid connecting all in-segments to all out-segments.
This is achieved by an object in each segment that indicates the This is achieved by an object in each segment that indicates the
direction of the segment with respect to data flow. direction of the segment with respect to data flow.
A segment that is marked as 'forward' carries data from the 'head' of A segment that is marked as 'forward' carries data from the 'head' of
the LSP to the 'tail'. A segment marked as 'reverse' carries data in the LSP to the 'tail'. A segment marked as 'reverse' carries data in
the reverse direction. the reverse direction.
skipping to change at page 5, line 37 skipping to change at page 5, line 49
participate in the LSP by assigning 'head' and 'tail' ends to the participate in the LSP by assigning 'head' and 'tail' ends to the
LSP. LSP.
6. Example of LSP Setup 6. Example of LSP Setup
In this section we provide a brief example of using the MIB objects In this section we provide a brief example of using the MIB objects
described in sections 7 and 8 to set up an LSP. While this example is described in sections 7 and 8 to set up an LSP. While this example is
not meant to illustrate every nuance of the MIB, it is intended as an not meant to illustrate every nuance of the MIB, it is intended as an
aid to understanding some of the key concepts. It is meant to be read aid to understanding some of the key concepts. It is meant to be read
after going through the MIB itself. A prerequisite is an after going through the MIB itself. A prerequisite is an
understanding of [LSRMIB]. understanding of [RFC3813].
Suppose that one would like to manually create a best-effort, bi- Suppose that one would like to manually create a best-effort,
directional LSP. Assume that, in the forward direction, the LSP bi-directional LSP. Assume that, in the forward direction, the LSP
enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR
via MPLS interface B with ifIndex 13. For the reverse direction, we via MPLS interface B with ifIndex 13. For the reverse direction, we
assume the LSP enters via interface B and leaves via interface A assume the LSP enters via interface B and leaves via interface A
(i.e. the forward and reverse directions use the same bi-directional (i.e. the forward and reverse directions use the same bi-directional
interfaces). Let us also assume that we do not wish to have a label interfaces). Let us also assume that we do not wish to have a label
stack beneath the top label on the outgoing labeled packets. The stack beneath the top label on the outgoing labeled packets. The
following example illustrates which rows and corresponding objects following example illustrates which rows and corresponding objects
might be created to accomplish this. might be created to accomplish this.
We must first create rows in the gmplsLabelTable corresponding to the We must first create rows in the gmplsLabelTable corresponding to the
skipping to change at page 6, line 26 skipping to change at page 6, line 37
{ {
gmplsLabelInterface = 13, gmplsLabelInterface = 13,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
gmplsLabelSubindex = 0, gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformGeneralizedLabel(3), gmplsLabelType = gmplsFreeformGeneralizedLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210 gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4) gmplsLabelRowStatus = createAndGo(4)
} }
We must next create the appropriate in-segment and out-segment We must next create the appropriate in-segment and out-segment
entries. These are done in [LSRMIB] using the mplsInSegmentTable and entries. These are done in [RFC3813] using the mplsInSegmentTable and
mplsOutSegmentTable. Note that we use a row pointer to the two rows mplsOutSegmentTable. Note that we use a row pointer to the two rows
in the gmplsLableTable rather than specifying the labels explicitly in the gmplsLableTable rather than specifying the labels explicitly
in the in- and out-segment tables. Also note that the row status for in the in- and out-segment tables. Also note that the row status for
each row is set to createAndWait(5) to allow corresponding entries in each row is set to createAndWait(5) to allow corresponding entries in
the gmplsInSegmentTable and gmplsOutSegmentTable to be created. the gmplsInSegmentTable and gmplsOutSegmentTable to be created.
For the forward direction. For the forward direction.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x00000015 mplsInSegmentIndex = 0x00000015
mplsInSegmentLabel = 0, -- incoming label in label = mplsInSegmentLabel = 0, -- incoming label in label table
table
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 12, -- incoming interface mplsInSegmentInterface = 12, -- incoming interface
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accesible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentLabelPtr = gmplsLabelTable (12, 1, 0) mplsInSegmentLabelPtr = gmplsLabelTable (12, 1, 0)
mplsInSegmentRowStatus = createAndWait(5) mplsInSegmentRowStatus = createAndWait(5)
} }
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 0x00000012, mplsOutSegmentIndex = 0x00000012,
mplsOutSegmentInterface = 13, -- outgoing interface mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label = mplsOutSegmentTopLabel = 0, -- outgoing label in label table
table
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accesible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable (13, 1, 0) mplsOutSegmentLabelPtr = gmplsLabelTable (13, 1, 0)
mplsOutSegmentRowStatus = createAndWait(5) mplsOutSegmentRowStatus = createAndWait(5)
} }
For the reverse direction. For the reverse direction.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x00000016 mplsInSegmentIndex = 0x00000016
mplsInSegmentLabel = 0, -- incoming label in label = mplsInSegmentLabel = 0, -- incoming label in label table
table
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accesible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentLabelPtr = gmplsLabelTable (13, 1, 0) mplsInSegmentLabelPtr = gmplsLabelTable (13, 1, 0)
mplsInSegmentRowStatus = createAndWait(5) mplsInSegmentRowStatus = createAndWait(5)
} }
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 0x00000013, mplsOutSegmentIndex = 0x00000013,
mplsOutSegmentInterface = 12, -- outgoing interface mplsOutSegmentInterface = 12, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label = mplsOutSegmentTopLabel = 0, -- outgoing label in label table
table
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accesible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable (12, 1, 0) mplsOutSegmentLabelPtr = gmplsLabelTable (12, 1, 0)
mplsOutSegmentRowStatus = createAndWait(5) mplsOutSegmentRowStatus = createAndWait(5)
} }
These table entries are extended by entries in gmplsInSegmentTable These table entries are extended by entries in gmplsInSegmentTable
and gmplsOutSegmentTable. Note that the nature of the 'extends' and gmplsOutSegmentTable. Note that the nature of the 'extends'
skipping to change at page 8, line 18 skipping to change at page 8, line 41
Next, two cross-connect entries are created in the mplsXCTable of the Next, two cross-connect entries are created in the mplsXCTable of the
MPLS LSR MIB, thereby associating the newly created segments MPLS LSR MIB, thereby associating the newly created segments
together. together.
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000015, mplsXCInSegmentIndex = 0x00000015,
mplsXCOutSegmentIndex = 0x00000012, mplsXCOutSegmentIndex = 0x00000012,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
-- outgoing label
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x02, mplsXCIndex = 0x02,
mplsXCInSegmentIndex = 0x00000016, mplsXCInSegmentIndex = 0x00000016,
mplsXCOutSegmentIndex = 0x00000013, mplsXCOutSegmentIndex = 0x00000013,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
-- outgoing label
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
Finally, the in-segments and out-segments are activated. Finally, the in-segments and out-segments are activated.
In mplsInSegmentTable(0x00000015): In mplsInSegmentTable(0x00000015):
{ {
mplsInSegmentRowStatus = active(1) mplsInSegmentRowStatus = active(1)
} }
In mplsInSegmentTable(0x00000016): In mplsInSegmentTable(0x00000016):
{ {
mplsInSegmentRowStatus = active(1) mplsInSegmentRowStatus = active(1)
} }
In mplsOutSegmentTable(0x00000012): In mplsOutSegmentTable(0x00000012):
{ {
mplsOutSegmentRowStatus = active(1) mplsOutSegmentRowStatus = active(1)
} }
In mplsOutSegmentTable(0x00000013): In mplsOutSegmentTable(0x00000013):
{ {
mplsOutSegmentRowStatus = active(1) mplsOutSegmentRowStatus = active(1)
} }
7. GMPLS Label Switching Router MIB Definitions 7. GMPLS Label Switching Router MIB Definitions
GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
skipping to change at page 9, line 11 skipping to change at page 9, line 29
{ {
mplsOutSegmentRowStatus = active(1) mplsOutSegmentRowStatus = active(1)
} }
7. GMPLS Label Switching Router MIB Definitions 7. GMPLS Label Switching Router MIB Definitions
GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, zeroDotZero MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, zeroDotZero
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
RowPointer RowPointer
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
GmplsSegmentDirection, gmplsStdMIB GmplsSegmentDirection
FROM GMPLS-TC-STD-MIB FROM GMPLS-TC-STD-MIB -- [GMPLSTCMIB]
mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB -- [RFC3813]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
; ;
gmplsLsrStdMIB MODULE-IDENTITY gmplsLsrStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200406010900Z" -- 1 June 2004 9:00:00 GMT "200410080001Z" -- 8 October 2004 00:00:01 GMT
ORGANIZATION ORGANIZATION
"Common Control And Management Protocols (CCAMP) "Common Control And Measurement Plane (CCAMP) Working Group"
Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan
Bloomberg L.P.
Email: cheenu@bloomberg.net
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Ed Harrison
Data Connection Ltd.
Email: ed.harrison@dataconnection.com
Tim Hall
Data Connection Ltd.
Email: tim.hall@dataconnection.com
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions "Copyright (C) The Internet Society (2004). The
for the Generalized Multiprotocol Label Switching initial version of this MIB module was published
(GMPLS) Router as defined in: Mannie et al., in RFC xxxx. For full legal notices see the RFC
itself or see: http://www.ietf.org/copyrights/ianamib.html
This MIB module contains managed object definitions
for the Generalized Multiprotocol (GMPLS) Label Switching
Router as defined in:
Generalized Multi-Protocol Label Switching (GMPLS) Generalized Multi-Protocol Label Switching (GMPLS)
Architecture, draft-ietf-ccamp-gmpls- Architecture,Mannie et al.,
architecture-07.txt, May 2003, work in progress. draft-ietf-ccamp-gmpls-architecture-07.txt, May 2003,
work in progress."
Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices."
-- Revision history. -- Revision history.
REVISION
"200406010900Z" -- 1 June 2004 09:00:00 GMT
REVISION
"200410080001Z" -- 8 October 2004 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial version issued as part of RFC XXXX."
::= { gmplsStdMIB xx } ::= { mplsStdMIB xx }
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Notifications -- Notifications
-- no notifications are currently defined. -- no notifications are currently defined.
gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 } gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 }
-- Tables, Scalars -- Tables, Scalars
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 }
skipping to change at page 11, line 27 skipping to change at page 11, line 52
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the signaling capabilities on this "Defines the signaling capabilities on this
interface. Multiple bits may legitimately be set at interface. Multiple bits may legitimately be set at
once. Setting no bits implies that GMPLS signaling once. Setting no bits implies that GMPLS signaling
cannot be performed on this interface and all LSPs cannot be performed on this interface and all LSPs
must be manually provisioned or that this table must be manually provisioned or that this table
entry is only present to supplement an entry in entry is only present to supplement an entry in
the mplsInterfaceTable by providing the information the mplsInterfaceTable by providing the information
carried in other objects in this row." carried in other objects in this row."
DEFVAL { { rsvpGmpls } }
::= { gmplsInterfaceEntry 1 } ::= { gmplsInterfaceEntry 1 }
gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Period, in milliseconds, between sending RSVP Hello "Period, in milliseconds, between sending RSVP Hello
messages on this interface. A value of 0 indicates messages on this interface. A value of 0 indicates
that no Hello messages should be sent on this interface." that no Hello messages should be sent on this interface."
REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L.
(Editor), RFC 3473, January 2003."
DEFVAL { 3000 } DEFVAL { 3000 }
::= { gmplsInterfaceEntry 2 } ::= { gmplsInterfaceEntry 2 }
-- End of gmplsInterfaceTable -- End of gmplsInterfaceTable
-- In-segment table. -- In-segment table.
gmplsInSegmentTable OBJECT-TYPE gmplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInSegmentEntry SYNTAX SEQUENCE OF GmplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 14, line 15 skipping to change at page 14, line 49
A value of zero indicates that no decrement should A value of zero indicates that no decrement should
be made or that per-hop decrementing is not in be made or that per-hop decrementing is not in
force. force.
See the gmplsTunnelTTLDecrement object in the See the gmplsTunnelTTLDecrement object in the
gmplsTunnelTable of [GMPLSTEMIB] for a value by gmplsTunnelTable of [GMPLSTEMIB] for a value by
which to decrement the TTL for the whole of a which to decrement the TTL for the whole of a
tunnel. tunnel.
This object cannot be modified if This object cannot be modified if
mplsOutSegmentRowStatus for the associated entry in mplsOutSegmentRowStatus for the associated entry in
the mplsOutSegmentTable is active(1)." the mplsOutSegmentTable is active(1)."
REFERENCE
"Time To Live (TTL) Processing in Multi-Protocol Label Switching
(MPLS) Networks, Agarwal, P., Akyol, B., RFC 3443, January 2003"
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsOutSegmentEntry 2 } ::= { gmplsOutSegmentEntry 2 }
gmplsOutSegmentExtraParamsPtr OBJECT-TYPE gmplsOutSegmentExtraParamsPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Some Tunnels will run over transports that can "Some Tunnels will run over transports that can
usefully support technology-specific additional parameters usefully support technology-specific additional parameters
(for example, SONET resource usage). Such can be supplied from (for example, SONET resource usage). Such can be supplied from
an external table and referenced from here. an external table and referenced from here.
A value of zeroDotzero in this attribute indicates that there A value of zeroDotzero in this attribute indicates that there
skipping to change at page 16, line 4 skipping to change at page 16, line 50
-- Compliance requirement for implementations that provide read-only -- Compliance requirement for implementations that provide read-only
-- access. -- access.
gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only "Compliance requirement for implementations that only
provide read-only support for GMPLS-LSR-STD-MIB. Such provide read-only support for GMPLS-LSR-STD-MIB. Such
devices can then be monitored but cannot be configured devices can then be monitored but cannot be configured
using this MIB modules." using this MIB modules."
MODULE IF-MIB -- The interfaces Group MIB, RFC 2863
MODULE IF-MIB -- The interfaces Group MIB, RFC 2863
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifGeneralInformationGroup, ifGeneralInformationGroup,
ifCounterDiscontinuityGroup ifCounterDiscontinuityGroup
} }
MODULE MPLS-LSR-STD-MIB MODULE MPLS-LSR-STD-MIB
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInterfaceGroup, mplsInterfaceGroup,
mplsInSegmentGroup, mplsInSegmentGroup,
skipping to change at page 18, line 15 skipping to change at page 19, line 20
OBJECTS { OBJECTS {
gmplsOutSegmentDirection, gmplsOutSegmentDirection,
gmplsOutSegmentTTLDecrement, gmplsOutSegmentTTLDecrement,
gmplsOutSegmentExtraParamsPtr gmplsOutSegmentExtraParamsPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement a GMPLS "Collection of objects needed to implement a GMPLS
out-segment." out-segment."
::= { gmplsLsrGroups 3 } ::= { gmplsLsrGroups 3 }
END END
8. GMPLS Label MIB Definitions 8. GMPLS Label MIB Definitions
GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32,
Integer32 Integer32
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
RowStatus, StorageType RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB FROM IF-MIB -- [RFC2863]
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB FROM DIFFSERV-MIB -- [RFC3289]
MplsLabel MplsLabel
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- [RFC3811]
GmplsGeneralizedLabelTypes, GmplsFreeformLabel, GmplsGeneralizedLabelTypes, GmplsFreeformLabel
gmplsStdMIB FROM GMPLS-TC-STD-MIB -- [GMPLSTCMIB]
FROM GMPLS-TC-STD-MIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
; ;
gmplsLabelStdMIB MODULE-IDENTITY gmplsLabelStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200406010900Z" -- 1 June 2004 9:00:00 GMT "200410080001Z" -- 8 October 2004 00:00:01 GMT
ORGANIZATION ORGANIZATION
"Common Control And Management Protocols (CCAMP) "Common Control And Measurement Plane (CCAMP) Working Group"
Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan
Bloomberg L.P.
Email: cheenu@bloomberg.net
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Ed Harrison
Data Connection Ltd.
Email: ed.harrison@dataconnection.com
Tim Hall
Data Connection Ltd.
Email: tim.hall@dataconnection.com
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions "Copyright (C) The Internet Society (2004). The
for labels within GMPLS systems." initial version of this MIB module was published
in RFC xxxx. For full legal notices see the RFC
itself or see: http://www.ietf.org/copyrights/ianamib.html
This MIB module contains managed object definitions
for labels within GMPLS systems as defined in:
Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003."
-- Revision history. -- Revision history.
REVISION REVISION
"200406010900Z" -- 1 June 2004 09:00:00 GMT "200410080001Z" -- 8 October 2004 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial version issued as part of RFC XXXX."
::= { gmplsStdMIB xx } ::= { mplsStdMIB xx }
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Notifications -- Notifications
-- no notifications are currently defined. -- no notifications are currently defined.
gmplsLabelNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 = gmplsLabelNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 }
}
-- Tables, Scalars -- Tables, Scalars
gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 = gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 }
}
-- Conformance -- Conformance
gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 = gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 }
}
-- GMPLS Label Table. -- GMPLS Label Table.
gmplsLabelIndexNext OBJECT-TYPE gmplsLabelIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an unused value for "This object contains an unused value for
gmplsLabelIndex, or a zero to indicate gmplsLabelIndex, or a zero to indicate
skipping to change at page 21, line 59 skipping to change at page 23, line 26
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In conjunction with gmplsLabelInterface and gmplsLabelIndex, "In conjunction with gmplsLabelInterface and gmplsLabelIndex,
this object uniquely identifies this row. This sub-index this object uniquely identifies this row. This sub-index
allows a single GMPLS label to be defined as a concatenation allows a single GMPLS label to be defined as a concatenation
of labels. This is particularly useful in TDM. of labels. This is particularly useful in TDM.
The ordering of sub-labels is strict with the sub-label with The ordering of sub-labels is strict with the sub-label with
lowest gmplsLabelSubindex appearing first. Note that all sub- lowest gmplsLabelSubindex appearing first. Note that all
labels of a single GMPLS label must share the same sub-labels of a single GMPLS label must share the same
gmplsLabelInterface and gmplsLabelIndex values. For labels gmplsLabelInterface and gmplsLabelIndex values. For labels
that are not composed of concatenated sub-labels, this value that are not composed of concatenated sub-labels, this value
SHOULD be set to zero." SHOULD be set to zero."
::= { gmplsLabelEntry 3 } ::= { gmplsLabelEntry 3 }
gmplsLabelType OBJECT-TYPE gmplsLabelType OBJECT-TYPE
SYNTAX GmplsGeneralizedLabelTypes SYNTAX GmplsGeneralizedLabelTypes
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the type of this label. Note that this object "Identifies the type of this label. Note that this object
does not determine whether MPLS or GMPLS signaling is in does not determine whether MPLS or GMPLS signaling is in
use: a value of gmplsMplsLabel (1) denotes that a 23 bit use: a value of gmplsMplsLabel (1) denotes that a 23 bit
MPLS packet label is present, but does not describe MPLS packet label is present, but does not describe
whether this is signaled using MPLS or GMPLS. whether this is signaled using MPLS or GMPLS.
The value of this object helps determine which of The value of this object helps determine which of
the following objects are valid. the following objects are valid.
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003."
::= { gmplsLabelEntry 4 } ::= { gmplsLabelEntry 4 }
gmplsLabelMplsLabel OBJECT-TYPE gmplsLabelMplsLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of an MPLS label (that is a packet label) "The value of an MPLS label (that is a packet label)
if this table is used to store it. This may be used if this table is used to store it. This may be used
in MPLS systems even though the label values can be in MPLS systems even though the label values can be
adequately stored in the MPLS MIB modules. Further, adequately stored in the MPLS MIB modules. Further,
in mixed MPLS and GMPLS systems it may be in mixed MPLS and GMPLS systems it may be
skipping to change at page 22, line 45 skipping to change at page 24, line 23
in mixed MPLS and GMPLS systems it may be in mixed MPLS and GMPLS systems it may be
advantageous to store all labels in a single label advantageous to store all labels in a single label
table. Lastly, in GMPLS systems where packet labels table. Lastly, in GMPLS systems where packet labels
are used (that is in systems that use GMPLS are used (that is in systems that use GMPLS
signaling and GMPLS labels for packet switching) it signaling and GMPLS labels for packet switching) it
may be desirable to use this table. may be desirable to use this table.
This object is only valid if gmplsLabelType is set This object is only valid if gmplsLabelType is set
to gmplsMplsLabel (1). to gmplsMplsLabel (1).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"MPLS Label Stack Encoding, Rosen, E. et al, RFC 3032,
January 2001."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 6 } ::= { gmplsLabelEntry 6 }
gmplsLabelPortWavelength OBJECT-TYPE gmplsLabelPortWavelength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of a Port or Wavelength Label when carried "The value of a Port or Wavelength Label when carried
as a Generalized Label. Only valid if gmplsLabelType as a Generalized Label. Only valid if gmplsLabelType
is set to gmplsPortWavelengthLabel(2). is set to gmplsPortWavelengthLabel(2).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 7 } ::= { gmplsLabelEntry 7 }
gmplsLabelFreeform OBJECT-TYPE gmplsLabelFreeform OBJECT-TYPE
SYNTAX GmplsFreeformLabel SYNTAX GmplsFreeformLabel
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of a freeform Generalized Label that does "The value of a freeform Generalized Label that does
not conform to one of the standardized label not conform to one of the standardized label
encoding or that an implementation chooses to encoding or that an implementation chooses to
represent as an octet string without further represent as an octet string without further
decoding. Only valid if decoding. Only valid if gmplsLabelType is set to
gmplsLabelType is set to gmplsFreeformGeneralizedLabel(3). This object
gmplsFreeformGeneralizedLabel(3). cannot be modified if gmplsLabelRowStatus is active(1)."
This object cannot be modified if
gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 8 } ::= { gmplsLabelEntry 8 }
gmplsLabelSonetSdhSignalIndex OBJECT-TYPE gmplsLabelSonetSdhSignalIndex OBJECT-TYPE
SYNTAX Integer32 (0..4095) SYNTAX Integer32 (0..4095)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Signal Index value (S) of a SONET or SDH "The Signal Index value (S) of a SONET or SDH
Generalized Label. Zero indicates that this field is Generalized Label. Zero indicates that this field is
not significant. Only valid if gmplsLabelType is set not significant. Only valid if gmplsLabelType is set
to gmplsSonetLabel(4) or gmplsSdhLabel(5). to gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D.
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003, work in progress."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 9 } ::= { gmplsLabelEntry 9 }
gmplsLabelSdhVc OBJECT-TYPE gmplsLabelSdhVc OBJECT-TYPE
SYNTAX Integer32 (0..15) SYNTAX Integer32 (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VC Indicator (U) of an SDH Generalized Label. "The VC Indicator (U) of an SDH Generalized Label.
Zero indicates that this field is non-significant. Zero indicates that this field is non-significant.
Only valid if gmplsLabelType is set to Only valid if gmplsLabelType is set to gmplsSdhLabel(5).
gmplsSdhLabel(5).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D.
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003, work in progress."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 10 } ::= { gmplsLabelEntry 10 }
gmplsLabelSdhVcBranch OBJECT-TYPE gmplsLabelSdhVcBranch OBJECT-TYPE
SYNTAX Integer32 (0..15) SYNTAX Integer32 (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VC Branch Indicator (K) of an SDH Generalized "The VC Branch Indicator (K) of an SDH Generalized
Label. Zero indicates that this field is non- Label. Zero indicates that this field is non-significant.
significant. Only valid if gmplsLabelType is set to Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This
gmplsSdhLabel(5). object cannot be modified if gmplsLabelRowStatus is active(1)."
This object cannot be modified if REFERENCE
gmplsLabelRowStatus is active(1)." "Generalized Multi-Protocol Label Switching Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D.
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003, work in progress."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 11 } ::= { gmplsLabelEntry 11 }
gmplsLabelSonetSdhBranch OBJECT-TYPE gmplsLabelSonetSdhBranch OBJECT-TYPE
SYNTAX Integer32 (0..15) SYNTAX Integer32 (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Branch Indicator (L) of a SONET or SDH "The Branch Indicator (L) of a SONET or SDH
Generalized Label. Zero indicates that this field is Generalized Label. Zero indicates that this field is
non-significant. Only valid gmplsLabelType is set to non-significant. Only valid gmplsLabelType is set to
gmplsSonetLabel(4) or gmplsSdhLabel(5). gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if This object cannot be modified if
skipping to change at page 24, line 15 skipping to change at page 26, line 23
SYNTAX Integer32 (0..15) SYNTAX Integer32 (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Branch Indicator (L) of a SONET or SDH "The Branch Indicator (L) of a SONET or SDH
Generalized Label. Zero indicates that this field is Generalized Label. Zero indicates that this field is
non-significant. Only valid gmplsLabelType is set to non-significant. Only valid gmplsLabelType is set to
gmplsSonetLabel(4) or gmplsSdhLabel(5). gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D.
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003, work in progress."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 12 } ::= { gmplsLabelEntry 12 }
gmplsLabelSonetSdhGroupBranch OBJECT-TYPE gmplsLabelSonetSdhGroupBranch OBJECT-TYPE
SYNTAX Integer32 (0..15) SYNTAX Integer32 (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Group Branch Indicator (M) of a SONET or SDH "The Group Branch Indicator (M) of a SONET or SDH
Generalized Label. Zero indicates that this field is Generalized Label. Zero indicates that this field is
non-significant. Only valid if gmplsLabelType is set non-significant. Only valid if gmplsLabelType is set
to gmplsSonetLabel(4) or gmplsSdhLabel(5). to gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D.
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003, work in progress."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 13 } ::= { gmplsLabelEntry 13 }
gmplsLabelWavebandId OBJECT-TYPE gmplsLabelWavebandId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The waveband identifier component of a waveband "The waveband identifier component of a waveband label. Only
label. Only valid if gmplsLabelType is set to valid if gmplsLabelType is set to gmplsWavebandLabel(6). This
gmplsWavebandLabel(6). object cannot be modified if gmplsLabelRowStatus is active(1)."
This object cannot be modified if REFERENCE
gmplsLabelRowStatus is active(1)." "Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 14 } ::= { gmplsLabelEntry 14 }
gmplsLabelWavebandStart OBJECT-TYPE gmplsLabelWavebandStart OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The starting label component of a waveband label. "The starting label component of a waveband label.
Only valid if gmplsLabelType is set to Only valid if gmplsLabelType is set to
gmplsWavebandLabel(6). gmplsWavebandLabel(6).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 15 } ::= { gmplsLabelEntry 15 }
gmplsLabelWavebandEnd OBJECT-TYPE gmplsLabelWavebandEnd OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The end label component of a waveband label. Only "The end label component of a waveband label. Only
valid if gmplsLabelType is set to valid if gmplsLabelType is set to gmplsWavebandLabel(6).
gmplsWavebandLabel(6).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS)
Signaling Functional Description, Berger, L. (Editor),
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 16 } ::= { gmplsLabelEntry 16 }
gmplsLabelRowStatus OBJECT-TYPE gmplsLabelRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. When a row in this delete a row in this table. When a row in this
table has a row in the active(1) state, no table has a row in the active(1) state, no objects in this row
objects in this row can be modified except the can be modified except the gmplsLabelRowStatus and
gmplsLabelRowStatus and gmplsLabelStorageType." gmplsLabelStorageType."
::= { gmplsLabelEntry 17 } ::= { gmplsLabelEntry 17 }
gmplsLabelStorageType OBJECT-TYPE gmplsLabelStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this object.
object. The agent MUST ensure that this object's value remains
The agent MUST ensure that this object's value consistent with the storage type of any rows in other
remains consistent with the storage type of any rows tables that contain pointers to this row. In particular,
in other tables that contain pointers to this row. the storage type of this row must be at least as permanent
In particular, the storage type of this row must be as that of any row that point to it.
at least as permanent as that of any row that point Conceptual rows having the value 'permanent' need not
to it. allow write-access to any columnar objects in the row."
Conceptual rows having the value 'permanent' need
not allow write-access to any columnar objects in
the row."
REFERENCE REFERENCE
"See RFC2579." "See RFC2579."
DEFVAL { volatile } DEFVAL { volatile }
::= { gmplsLabelEntry 18 } ::= { gmplsLabelEntry 18 }
-- End of GMPLS Label Table -- End of GMPLS Label Table
-- Module compliance. -- Module compliance.
gmplsLabelGroups gmplsLabelGroups
skipping to change at page 30, line 52 skipping to change at page 34, line 7
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET "change/create/delete" them.
10. Acknowledgments 10. Acknowledgments
This document extends [LSRMIB]. The authors would like to express This draft is the work of the five authors listed in the Authors'
Addresses section.
This document extends [RFC3813]. 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.
The authors would like to express their thanks to Dan Joyle for his The authors would like to express their thanks to Dan Joyle for his
careful review and comments on early versions of the Label Table. careful review and comments on early versions of the Label Table.
Special thanks to Joan Cucchiara and Len Nieman for their help with Special thanks to Joan Cucchiara and Len Nieman for their help with
compilation issues. compilation issues.
11. IANA Considerations 11. IANA Considerations
MPLS related standards track MIB modules are rooted under the MPLS related standards track MIB modules are rooted under the
skipping to change at page 31, line 55 skipping to change at page 35, line 18
1999. 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser, "Conformance Case, J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April Statements for SMIv2", STD 58, RFC 2580, April
1999. 1999.
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management
Information Base for the Differentiated Services
Architecture", RFC 3289, May 2002.
[RFC3443] Agarwal, P. and Akyol, B., "Time To Live (TTL)
Processing in Multi-Protocol Label Switching
(MPLS) Networks", RFC 3443, January 2003.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching
(MPLS) Management", RFC 3811, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label
Switching (LSR) Router Management Information Base
(MIB)", RFC 3813, June 2004.
[GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol
Label Switching (GMPLS) Architecture", Label Switching (GMPLS) Architecture",
draft-many-gmpls-architecture-07.txt, May draft-many-gmpls-architecture-07.txt, May 2003,
2003, work in progress. work in progress.
[GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors),
"Generalized Multi-Protocol Label Switching "Generalized Multi-Protocol Label Switching
Extensions for SONET and SDH Control", Extensions for SONET and SDH Control",
draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003, work in progress. February 2003, work in progress.
[GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., [GMPLSTCMIB] Nadeau, T., Farrel, A., (Editors) "Definitions of
and Harrison, E., "Definitions of Textual
Conventions for Multiprotocol Label Switching
(MPLS) Management", draft-ietf-ccamp-gmpls-te-mib-
05.txt, June 2004, work in progress.
[GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
and Harrison, E., "Generalized Multiprotocol Label
Switching (GMPLS) Traffic Engineering Management
Information Base", draft-ietf-ccamp-gmpls-te-mib-
05.txt, June 2004, work in progress.
[TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of
Textual Conventions for Multiprotocol Label Textual Conventions for Multiprotocol Label
Switching (MPLS) Management", draft-ietf-mpls-tc- Switching (MPLS) Management",
mib-10.txt, November 2003, work in progress. draft-ietf-ccamp-gmpls-te-mib-06.txt, October 2004,
work in progress.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, [GMPLSTEMIB] Nadeau, T., Farrel, A. (Editors) "Generalized
"Multiprotocol Label Switching (MPLS) Label Multiprotocol Label Switching (GMPLS) Traffic
Switching Router (LSR) Management Information Engineering Management Information Base",
Base", draft-ietf-mpls-lsr-mib-14.txt, November draft-ietf-ccamp-gmpls-te-mib-06.txt, October 2004,
2003, work in progress. work in progress.
12.2. Informational References 12.2. Informational References
[RFC2026] S. Bradner, "The Internet Standards Process -- [RFC2026] S. Bradner, "The Internet Standards Process --
Revision 3", RFC 2026, October 1996. Revision 3", RFC 2026, October 1996.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for
Writing an IANA Considerations Section in RFCs", Writing an IANA Considerations Section in RFCs",
BCP: 26, RFC 2434, October 1998. BCP: 26, RFC 2434, October 1998.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC "Multiprotocol Label Switching Architecture", RFC
3031, January 2001. 3031, January 2001.
[RFC3032] Rosen, E. et al, "MPLS Label Stack Encoding",
RFC 3032, January 2001.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T.,
Srinivasan, V., and G. Swallow, "RSVP-TE: Srinivasan, V., and G. Swallow, "RSVP-TE:
Extensions to RSVP for LSP Tunnels", RFC 3209, Extensions to RSVP for LSP Tunnels", RFC 3209,
December 2001. December 2001.
[RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L.,
Ashwood-Smith, P., Hellstrand, F., Sundell, K., Ashwood-Smith, P., Hellstrand, F., Sundell, K.,
Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, Callon, R., Dantu, R., Wu, L., Doolan, P., Worster,
T., Feldman, N., Fredette, A., Girish, M., Gray, T., Feldman, N., Fredette, A., Girish, M., Gray,
E., Halpern, J., Heinanen, J., Kilty, T., Malis, E., Halpern, J., Heinanen, J., Kilty, T., Malis,
skipping to change at page 33, line 28 skipping to change at page 37, line 12
Label Switching (GMPLS) Signaling Functional Label Switching (GMPLS) Signaling Functional
Description", RFC 3471, January 2003. Description", RFC 3471, January 2003.
[RFC3472] Ashwood-Smith, P., Berger, L. (Editors), [RFC3472] Ashwood-Smith, P., Berger, L. (Editors),
"Generalized MPLS Signaling - CR-LDP Extensions", "Generalized MPLS Signaling - CR-LDP Extensions",
RFC 3472, January 2003. RFC 3472, January 2003.
[RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
RSVP-TE Extensions", RFC 3473 January 2003. RSVP-TE Extensions", RFC 3473 January 2003.
[TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Traffic
Engineering Management Information Base", Engineering (TE) Management Information Base
draft-ietf-mpls-te-mib-14.txt, November 2003, (MIB)", RFC 3812, June 2004.
work in progress.
13. Authors' Addresses 13. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
skipping to change at page 34, line 35 skipping to change at page 38, line 24
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.
14.1. IPR Disclosure Acknowledgement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
16. Changes and Pending Work 16. Changes
This section must be removed before the draft progresses to RFC. This section must be removed before the draft progresses to RFC.
16.1. Pending Work 16.1. Changes from version 5 to version 6
The following work items have been identified for this draft. They
will be addressed in a future version.
- Expand conformance statements to give one for monitoring only, - ID nits and MIB bolierplate
and one for monitoring and control.
- Determine whether the 'discriminated union' in the Label Table is
good MIB.
16.2. Changes from version 4 to version 5 16.2. Changes from version 4 to version 5
- New IPR and copyright boiler plate. - New IPR and copyright boiler plate.
- Clarify description of gmplsInterfaceSignalingCaps. - Clarify description of gmplsInterfaceSignalingCaps.
16.3. Changes from version 3 to version 4 16.3. Changes from version 3 to version 4
- Update references. - Update references.
- Allow configuration of the Hello timer per interface. - Allow configuration of the Hello timer per interface.
- Provide support for monitoring technology-specific resources or - Provide support for monitoring technology-specific resources or
 End of changes. 

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