draft-ietf-ccamp-gmpls-lsr-mib-11.txt   draft-ietf-ccamp-gmpls-lsr-mib-12.txt 
Network Working Group Thomas D. Nadeau, Ed. 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: September 2006 Adrian Farrel, Ed. Expires: September 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
March 2006 April 2006
Generalized Multiprotocol Label Switching (GMPLS) 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-11.txt draft-ietf-ccamp-gmpls-lsr-mib-12.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 9 skipping to change at page 2, line 4
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects 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 ............................. 3 1.1. Migration Strategy ............................. 3
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
2. Terminology ...................................... 3 2. Terminology ...................................... 3
3. The SNMP Management Framework .................... 4 3. The Internet-Standard Management Framework ....... 4
4. Outline .......................................... 5 4. Outline .......................................... 5
4.1 MIB Modules ..................................... 5 4.1 MIB Modules ..................................... 5
4.1.1 Summary of the GMPLS-LSR-STD-MIB Module ....... 5 4.1.1 Summary of the GMPLS-LSR-STD-MIB Module ....... 5
4.1.2 Summary of the GMPLS-LABEL-STD-MIB Module ..... 5 4.1.2 Summary of the GMPLS-LABEL-STD-MIB Module ..... 5
4.2. Configuring Statically Provisioned LSPs ........ 6 4.2. Configuring Statically Provisioned LSPs ........ 6
5. Bidirectional LSPs ............................... 6 5. Bidirectional LSPs ............................... 6
6. Example of LSP Setup ............................. 7 6. Example of LSP Setup ............................. 7
7. GMPLS Label Switching Router MIB Definitions .... 11 7. GMPLS Label Switching Router MIB Definitions .... 11
8. GMPLS Label MIB Definitions ..................... 22 8. GMPLS Label MIB Definitions ..................... 22
9. Security Considerations ......................... 37 9. Security Considerations ......................... 37
skipping to change at page 3, line 15 skipping to change at page 3, line 5
1.1. Migration Strategy 1.1. Migration Strategy
MPLS LSRs may be modeled and managed using the MPLS-LSR-STD-MIB MPLS LSRs may be modeled and managed using the MPLS-LSR-STD-MIB
module [RFC3813]. module [RFC3813].
LSRs may be migrated to be modeled and managed using the MIB modules LSRs may be migrated to be modeled and managed using the MIB modules
in this document in order to migrate the LSRs to GMPLS support, or to in this document in order to migrate the LSRs to GMPLS support, or to
take advandtage of additional MIB objects defined in these MIB take advandtage of additional MIB objects defined in these MIB
modules that are applicable to MPLS-TE. modules that are applicable to MPLS-TE.
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
The GMPLS LSR MIB module (GMPLS-LSR-STD-MIB) defined in this document The GMPLS LSR MIB module (GMPLS-LSR-STD-MIB) defined in this document
extends the MPLS-LSR-STD-MIB module [RFC3813] through a series of extends the MPLS-LSR-STD-MIB module [RFC3813] through a series of
sparse augmentations of the MIB tables. The only additions are for sparse augmentations of the MIB tables. The only additions are for
support of GMPLS or to support the increased complexity of MPLS and support of GMPLS or to support the increased complexity of MPLS and
GMPLS systems. GMPLS systems.
In order to migrate from MPLS-LSR-STD-MIB support to In order to migrate from MPLS-LSR-STD-MIB support to
GMPLS-LSR-STD-MIB support an implementation needs only to add support GMPLS-LSR-STD-MIB support an implementation needs only to add support
for the additional tables and objects defined in GMPLS-LSR-STD-MIB. for the additional tables and objects defined in GMPLS-LSR-STD-MIB.
The gmplsInterfaceSignalingCaps object allows an implementation to The gmplsInterfaceSignalingCaps object allows an implementation to
use the objects and tables of GMPLS-LSR-STD-MIB without supporting use the objects and tables of GMPLS-LSR-STD-MIB without supporting
the GMPLS protocols. the GMPLS protocols.
The GMPLS Label MIB module (GMPLS-LABEL-STD-MIB) also defined in this The GMPLS Label MIB module (GMPLS-LABEL-STD-MIB) also defined in this
document allows labels to be configured and examined, and supports document allows labels to be configured and examined, and supports
more varieties of label as appropriate for GMPLS. Labels may be more varieties of label as appropriate for GMPLS. Labels may be
referenced using a row pointer from objects within the referenced using a row pointer from objects within the
GMPLS-LSR-STD-MIB module. MPLS implementations (MPLS-LSR-STD-MIB) may GMPLS-LSR-STD-MIB module. MPLS implementations (MPLS-LSR-STD-MIB) may
also reference labels held in the GMPLS-LABEL-STD-MIB module through also reference labels held in the GMPLS-LABEL-STD-MIB module through
the various label pointer objects in the MPLS-STD-LSR-MIB module the various label pointer objects in the MPLS-LSR-STD-MIB module
(such as mplsInSegmentLabelPtr), and may do so without implementing (such as mplsInSegmentLabelPtr), and may do so without implementing
the GMPLS-LSR-STD-MIB module. the GMPLS-LSR-STD-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-STD-MIB module [RFC3812] engineering [GMPLSTEMIB] extends the MPLS-TE-STD-MIB module [RFC3812]
with the same intentions. with the same intentions.
Textual conventions and OBJECT-IDENTIFIERS are defined in Textual conventions are defined in [GMPLSTCMIB] which extends the
[GMPLSTCMIB] which extends the set of textual conventions originally set of textual conventions originally defined in [RFC3811].
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 [RFC3945]. architecture [RFC3031] and the GMPLS architecture [RFC3945].
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
by using a cross-connect. We use the terminology "connection" and by using a cross-connect. We use the terminology "connection" and
"LSP" interchangeably where the meaning is clear from the context. "LSP" interchangeably where the meaning is clear from the context.
in-segment This is analogous to a GMPLS label on an interface. in-segment This is analogous to a GMPLS label on an interface.
out-segment This is analogous to a GMPLS label on an interface. out-segment This is analogous to a GMPLS label on an interface.
cross-connect This describes the conceptual connection between a cross-connect This describes the conceptual connection between a
set of in-segments and out-segments. Note that either set of in-segments and out-segments. Note that either
set may be empty; for example, a cross-connect may set may be empty; for example, a cross-connect may
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
connect only out-segments together with no in-segments connect only out-segments together with no in-segments
in the case where an LSP originates on an LSR. in the case where an LSP originates on an LSR.
The terms 'ingress' and 'head-end' (or 'head') are used in this The terms 'ingress' and 'head-end' (or 'head') are used in this
document to indicate the signaling source of an LSP. This is document to indicate the signaling source of an LSP. This is
sometimes also referred to as the 'sender'. sometimes also referred to as the 'sender'.
The terms 'egress' and 'tail-end' (or 'tail') are used in this The terms 'egress' and 'tail-end' (or 'tail') are used in this
document to indicate the signaling destination of an LSP. document to indicate the signaling destination of an LSP.
skipping to change at page 4, line 35 skipping to change at page 4, line 28
The term 'downstream' is used in this document to refer to the part The term 'downstream' is used in this document to refer to the part
of an LSP closer to the egress than the current point of reference. of an LSP closer to the egress than the current point of reference.
The term 'forward' is used in this document to indicate the direction The term 'forward' is used in this document to indicate the direction
of data flow from the ingress toward the egress. of data flow from the ingress toward the egress.
The term 'reverse' is used in this document to indicate the direction The term 'reverse' is used in this document to indicate the direction
of data flow from the egress toward the ingress. of data flow from the egress toward the ingress.
3. The SNMP Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
skipping to change at page 5, line 16 skipping to change at page 5, line 5
4.1 MIB Modules 4.1 MIB Modules
There are two MIB modules defined in this document. There are two MIB modules defined in this document.
The GMPLS-LSR-STD-MIB module contains tables that sparse augment The GMPLS-LSR-STD-MIB module contains tables that sparse augment
tables defined in the MPLS-LSR-STD-MIB module [RFC3813]. This MIB tables defined in the MPLS-LSR-STD-MIB module [RFC3813]. This MIB
module is used in conjunction with the MPLS-LSR-STD-MIB module module is used in conjunction with the MPLS-LSR-STD-MIB module
[RFC3813] in systems that support GMPLS. [RFC3813] in systems that support GMPLS.
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
The GMPLS-LABEL-STD-MIB module contains objects for managing GMPLS The GMPLS-LABEL-STD-MIB module contains objects for managing GMPLS
labels when they cannot be represented using the textual conventions labels when they cannot be represented using the textual conventions
of the MPLS-TC-STD-MIB module [RFC3811], or when more detailed access of the MPLS-TC-STD-MIB module [RFC3811], or when more detailed access
to the sub-fields of the labels is required. to the sub-fields of the labels is required.
4.1.1 Summary of the GMPLS-LSR-STD-MIB Module 4.1.1 Summary of the GMPLS-LSR-STD-MIB Module
The MIB tables in the GMPLS-LSR-STD-MIB module are as follows. The MIB tables in the GMPLS-LSR-STD-MIB module are as follows.
- The interface configuration table (gmplsInterfaceTable), which - The interface configuration table (gmplsInterfaceTable), which
skipping to change at page 6, line 20 skipping to change at page 6, line 4
- Configuring an interface using the MPLS-LSR-STD-MIB module - Configuring an interface using the MPLS-LSR-STD-MIB module
[RFC3813]. [RFC3813].
- Enabling GMPLS on GMPLS capable interfaces using the - Enabling GMPLS on GMPLS capable interfaces using the
GMPLS-LSR-STD-MIB module in this document. GMPLS-LSR-STD-MIB module in this document.
- Configuring in and out-segments using the MPLS-LSR-STD-MIB module - Configuring in and out-segments using the MPLS-LSR-STD-MIB module
[RFC3813]. [RFC3813].
- Configuring GMPLS extensions to the in-segments and out-segments - Configuring GMPLS extensions to the in-segments and out-segments
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
using the GMPLS-LSR-STD-MIB module in this document. using the GMPLS-LSR-STD-MIB module in this document.
- Setting up the cross-connect table in the MPLS-LSR-STD-MIB module - Setting up the cross-connect table in the MPLS-LSR-STD-MIB module
[RFC3813] to associate segments and/or to indicate connection [RFC3813] to associate segments and/or to indicate connection
origination and termination. origination and termination.
- Optionally setting up labels in the label table in the - Optionally setting up labels in the label table in the
GMPLS-LABEL-STD-MIB module in this document if the textual GMPLS-LABEL-STD-MIB module in this document if the textual
convention MplsLabel [RFC3811] is not capable of holding the convention MplsLabel [RFC3811] is not capable of holding the
required label (for example, if the label requires more than 32 required label (for example, if the label requires more than 32
skipping to change at page 7, line 17 skipping to change at page 7, line 4
ingress) and the 'tail' is the destination (also known as the ingress) and the 'tail' is the destination (also known as the
egress). For manually configured LSPs an arbitrary decision must be egress). For manually configured LSPs an arbitrary decision must be
made about which segments are 'forward' and which 'reverse'. For made about which segments are 'forward' and which 'reverse'. For
consistency this decision should be made across all LSRs that consistency this decision should be made across all LSRs that
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
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
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 modules, it is not meant to illustrate every nuance of the MIB modules, it is
intended as an aid to understanding some of the key concepts. It is intended as an aid to understanding some of the key concepts. It is
meant to be read after going through the MIB modules themselves. A meant to be read after going through the MIB modules themselves. A
prerequisite is an understanding of the MPLS-LSR-STD-MIB [RFC3813]. prerequisite is an understanding of the MPLS-LSR-STD-MIB [RFC3813].
Suppose that one would like to manually create a best-effort, Suppose that one would like to manually create a best-effort,
bi-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
skipping to change at page 8, line 14 skipping to change at page 8, line 4
gmplsLabelType = gmplsFreeformLabel(3), gmplsLabelType = gmplsFreeformLabel(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 [RFC3813] 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 gmplsLabelTable rather than specifying the labels explicitly in the gmplsLabelTable 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
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
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 table mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
skipping to change at page 9, line 4 skipping to change at page 8, line 45
For the reverse direction. For the reverse direction.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x00000016 mplsInSegmentIndex = 0x00000016
mplsInSegmentLabel = 0, -- incoming label in label table mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible 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:
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
{ {
mplsOutSegmentIndex = 0x00000013, mplsOutSegmentIndex = 0x00000013,
mplsOutSegmentInterface = 12, -- outgoing interface mplsOutSegmentInterface = 12, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label table mplsOutSegmentTopLabel = 0, -- outgoing label in label table
-- RowPointer MUST point to the first accessible column. -- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable (12, 1, 0) mplsOutSegmentLabelPtr = gmplsLabelTable (12, 1, 0)
skipping to change at page 10, line 4 skipping to change at page 9, line 45
{ {
gmplsOutSegmentDirection = forward (1) gmplsOutSegmentDirection = forward (1)
} }
Next for the reverse direction: Next for the reverse direction:
In gmplsInSegmentTable(0x00000016) In gmplsInSegmentTable(0x00000016)
{ {
gmplsInSegmentDirection = reverse (2) gmplsInSegmentDirection = reverse (2)
} }
In gmplsOutSegmentTable(0x00000013) In gmplsOutSegmentTable(0x00000013)
{ {
gmplsOutSegmentDirection = reverse (2) gmplsOutSegmentDirection = reverse (2)
} }
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-STD-MIB [RFC3813], thereby associating the newly created MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
segments together. segments together.
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
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 outgoing label mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
skipping to change at page 11, line 8 skipping to change at page 10, line 51
} }
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
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3209], [RFC3443], [RFC2578], [RFC2579], [RFC2580], [GMPLSTCMIB], [RFC3811],
[RFC3472], [RFC3473], [RFC3811], [RFC3813], and [GMPLSTCMIB]. [RFC2863] and [RFC3813].
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
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 -- RFC2578 FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
RowPointer RowPointer
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
GmplsSegmentDirectionTC GmplsSegmentDirectionTC
FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB
-- RFC-Editor please resolve the reference above to GMPLSTCMIB
-- using the assigned RFC number and remove this note
mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex, mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex,
mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup, mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB -- RFC3813 FROM MPLS-LSR-STD-MIB -- RFC3813
ifGeneralInformationGroup, ifCounterDiscontinuityGroup ifGeneralInformationGroup, ifCounterDiscontinuityGroup
FROM IF-MIB -- RFC2863 FROM IF-MIB -- RFC2863
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB -- RFC3811
; ;
gmplsLsrStdMIB MODULE-IDENTITY gmplsLsrStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200603020001Z" -- 2 March 2006 00:00:01 GMT "200604060001Z" -- 06 April 2006 00:00:01 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working Group" "IETF Common Control And Measurement Plane (CCAMP) 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
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
skipping to change at page 12, line 8 skipping to change at page 12, line 4
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 Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
This MIB module contains managed object definitions for the This MIB module contains managed object definitions for the
Generalized Multiprotocol (GMPLS) Label Switching Router as Generalized Multiprotocol (GMPLS) Label Switching Router as
defined in: Generalized Multi-Protocol Label Switching (GMPLS) defined in: Generalized Multi-Protocol Label Switching (GMPLS)
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
Architecture, Mannie et al., RFC 3945, October 2004." Architecture, Mannie et al., RFC 3945, October 2004."
REVISION REVISION
"200603020001Z" -- 2 March 2006 00:00:01 GMT "200604060001Z" -- 06 April 2006 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXX." "Initial version issued as part of RFC XXX."
::= { mplsStdMIB YYY } ::= { mplsStdMIB XXX }
-- RFC Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
-- RFC Editor. Please replace YYY above with the OID assigned by IANA -- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note -- and remove this note
-- no notifications are currently defined. -- no notifications are currently defined.
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 }
gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 }
skipping to change at page 13, line 4 skipping to change at page 13, line 4
LSR for each interface that is both capable of supporting LSR for each interface that is both capable of supporting
GMPLS and that is configured to support GMPLS. Note that GMPLS and that is configured to support GMPLS. Note that
support of GMPLS is not limited to control plane signaling, support of GMPLS is not limited to control plane signaling,
but may include data-plane only function configured through but may include data-plane only function configured through
SNMP SET commands performed on this MIB module. SNMP SET commands performed on this MIB module.
A conceptual row in this table may also be created via SNMP A conceptual row in this table may also be created via SNMP
SET commands or automatically by the LSR to supplement a SET commands or automatically by the LSR to supplement a
conceptual row in the mplsInterfaceTable where the interface conceptual row in the mplsInterfaceTable where the interface
is not capable of GMPLS but where the other objects carried is not capable of GMPLS but where the other objects carried
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
in this row provide useful additional information for an in this row provide useful additional information for an
MPLS interface. MPLS interface.
A conceptual row in this table will exist if and only if a A conceptual row in this table will exist if and only if a
corresponding entry in mplsInterfaceTable exists, and a corresponding entry in mplsInterfaceTable exists, and a
corresponding entry in ifTable exists with ifType = mpls(166). corresponding entry in ifTable exists with ifType = mpls(166).
If the associated entry in ifTable is operationally disabled If the associated entry in ifTable is operationally disabled
(thus removing the GMPLS capabilities on the interface) or the (thus removing the GMPLS capabilities on the interface) or the
entry in mplsInterfaceTable is deleted, the corresponding entry entry in mplsInterfaceTable is deleted, the corresponding entry
in this table MUST be deleted shortly thereafter. in this table MUST be deleted shortly thereafter.
skipping to change at page 14, line 4 skipping to change at page 14, line 4
then no other bit may be set. Setting no bits implies that GMPLS then no other bit may be set. Setting no bits implies that GMPLS
signaling cannot be performed on this interface and all LSPs signaling cannot be performed on this interface and all LSPs
must be manually provisioned or that this table entry is only must be manually provisioned or that this table entry is only
present to supplement an entry in the mplsInterfaceTable by present to supplement an entry in the mplsInterfaceTable by
providing the information carried in other objects in this row." providing the information carried in other objects in this row."
REFERENCE REFERENCE
"1. Generalized MPLS Signaling - CR-LDP Extensions, RFC 3472. "1. Generalized MPLS Signaling - CR-LDP Extensions, RFC 3472.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
DEFVAL { { rsvpGmpls } } DEFVAL { { rsvpGmpls } }
::= { gmplsInterfaceEntry 1 } ::= { gmplsInterfaceEntry 1 }
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
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 messages on "Period, in milliseconds, between sending RSVP Hello messages on
this interface. A value of 0 indicates that no Hello messages this interface. A value of 0 indicates that no Hello messages
should be sent on this interface. should be sent on this interface.
skipping to change at page 14, line 51 skipping to change at page 15, line 4
DESCRIPTION DESCRIPTION
"An entry in this table extends the representation of an incoming "An entry in this table extends the representation of an incoming
segment represented by an entry in mplsInSegmentTable in the segment represented by an entry in mplsInSegmentTable in the
MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be
created by a network administrator via SNMP SET commands, or in created by a network administrator via SNMP SET commands, or in
response to signaling protocol events. response to signaling protocol events.
Note that the storage type for this entry is given by the value Note that the storage type for this entry is given by the value
of mplsInSegmentStorageType in the corresponding entry of the of mplsInSegmentStorageType in the corresponding entry of the
mplsInSegmentTable." mplsInSegmentTable."
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router Management Information Base (MIB), RFC 3813." Router Management Information Base (MIB), RFC 3813."
INDEX { mplsInSegmentIndex } INDEX { mplsInSegmentIndex }
::= { gmplsInSegmentTable 1 } ::= { gmplsInSegmentTable 1 }
GmplsInSegmentEntry ::= SEQUENCE { GmplsInSegmentEntry ::= SEQUENCE {
gmplsInSegmentDirection GmplsSegmentDirectionTC, gmplsInSegmentDirection GmplsSegmentDirectionTC,
gmplsInSegmentExtraParamsPtr RowPointer gmplsInSegmentExtraParamsPtr RowPointer
} }
gmplsInSegmentDirection OBJECT-TYPE gmplsInSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirectionTC SYNTAX GmplsSegmentDirectionTC
skipping to change at page 15, line 48 skipping to change at page 16, line 4
::= { gmplsInSegmentEntry 2 } ::= { gmplsInSegmentEntry 2 }
gmplsOutSegmentTable OBJECT-TYPE gmplsOutSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsOutSegmentEntry SYNTAX SEQUENCE OF GmplsOutSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table sparse augments the mplsOutSegmentTable of the "This table sparse augments the mplsOutSegmentTable of the
MPLS-LSR-STD-MIB to provide GMPLS-specific information about MPLS-LSR-STD-MIB to provide GMPLS-specific information about
outgoing segments from an LSR." outgoing segments from an LSR."
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router Management Information Base (MIB), RFC 3813." Router Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 3 } ::= { gmplsLsrObjects 3 }
gmplsOutSegmentEntry OBJECT-TYPE gmplsOutSegmentEntry OBJECT-TYPE
SYNTAX GmplsOutSegmentEntry SYNTAX GmplsOutSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table extends the representation of an outgoing "An entry in this table extends the representation of an outgoing
segment represented by an entry in mplsOutSegmentTable of the segment represented by an entry in mplsOutSegmentTable of the
MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be
created by a network administrator via SNMP SET commands, or in created by a network administrator via SNMP SET commands, or in
response to signaling protocol events. response to signaling protocol events.
skipping to change at page 16, line 46 skipping to change at page 16, line 53
segment. This object cannot be modified if segment. This object cannot be modified if
mplsOutSegmentRowStatus for the corresponding entry in the mplsOutSegmentRowStatus for the corresponding entry in the
mplsOutSegmentTable is active(1)." mplsOutSegmentTable is active(1)."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router Management Information Base (MIB), RFC 3813." Router Management Information Base (MIB), RFC 3813."
DEFVAL { forward } DEFVAL { forward }
::= { gmplsOutSegmentEntry 1 } ::= { gmplsOutSegmentEntry 1 }
gmplsOutSegmentTTLDecrement OBJECT-TYPE gmplsOutSegmentTTLDecrement OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the amount by which to decrement the TTL "This object indicates the amount by which to decrement the TTL
of any payload packets forwarded on this segment if per-hop of any payload packets forwarded on this segment if per-hop
decrementing is being done. decrementing is being done.
A value of zero indicates that no decrement should be made or A value of zero indicates that no decrement should be made or
that per-hop decrementing is not in use. that per-hop decrementing is not in use.
skipping to change at page 17, line 46 skipping to change at page 18, line 5
::= { gmplsOutSegmentEntry 3 } ::= { gmplsOutSegmentEntry 3 }
gmplsLsrGroups gmplsLsrGroups
OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 }
gmplsLsrCompliances gmplsLsrCompliances
OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 }
-- Compliance requirement for fully compliant implementations. -- Compliance requirement for fully compliant implementations.
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
gmplsLsrModuleFullCompliance MODULE-COMPLIANCE gmplsLsrModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that provide full support for "Compliance statement for agents that provide full support for
GMPLS-LSR-STD-MIB." GMPLS-LSR-STD-MIB.
The mandatory group has to be implemented by all LSRs that
originate, terminate or act as transit for TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported, other
groups become mandatory as explained below."
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 -- The MPLS LSR MIB RFC 3813 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInterfaceGroup, mplsInterfaceGroup,
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsXCGroup,
mplsPerfGroup, mplsPerfGroup,
mplsLsrNotificationGroup mplsLsrNotificationGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsInterfaceGroup, gmplsInterfaceGroup,
gmplsInSegmentGroup, gmplsInSegmentGroup,
gmplsOutSegmentGroup gmplsOutSegmentGroup
} }
OBJECT gmplsInSegmentDirection OBJECT gmplsInSegmentDirection
SYNTAX GmplsSegmentDirectionTC SYNTAX GmplsSegmentDirectionTC
MIN-ACCESS read-write MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only forward(1) needs to be supported by implementations that "The only valid value for unidrectional LSPs is forward(1)."
only support unidirectional LSPs."
OBJECT gmplsOutSegmentDirection OBJECT gmplsOutSegmentDirection
SYNTAX GmplsSegmentDirectionTC SYNTAX GmplsSegmentDirectionTC
MIN-ACCESS read-write MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only forward(1) needs to be supported by implementations that "The only valid value for unidrectional LSPs is forward(1)."
only support unidirectional LSPs." draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
OBJECT gmplsOutSegmentTTLDecrement OBJECT gmplsOutSegmentTTLDecrement
SYNTAX Unsigned32 (0..255)
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsInSegmentExtraParamsPtr OBJECT gmplsInSegmentExtraParamsPtr
SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsOutSegmentExtraParamsPtr OBJECT gmplsOutSegmentExtraParamsPtr
SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { gmplsLsrCompliances 1 } ::= { gmplsLsrCompliances 1 }
-- Compliance requirement for implementations that provide read-only -- Compliance requirement for implementations that provide read-only
-- access. -- access.
gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE
skipping to change at page 19, line 42 skipping to change at page 20, line 4
mplsInterfaceGroup, mplsInterfaceGroup,
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsXCGroup,
mplsPerfGroup mplsPerfGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
gmplsInterfaceGroup, gmplsInterfaceGroup,
gmplsInSegmentGroup, gmplsInSegmentGroup,
gmplsOutSegmentGroup gmplsOutSegmentGroup
} }
OBJECT gmplsInterfaceSignalingCaps OBJECT gmplsInterfaceSignalingCaps
SYNTAX BITS {
unknown (0),
rsvpGmpls (1),
crldpGmpls (2),
otherGmpls (3)
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsInterfaceRsvpHelloPeriod OBJECT gmplsInterfaceRsvpHelloPeriod
SYNTAX Unsigned32
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsInSegmentDirection OBJECT gmplsInSegmentDirection
SYNTAX GmplsSegmentDirectionTC SYNTAX GmplsSegmentDirectionTC
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. Only forward(1) needs to be "The only valid value for unidrectional LSPs is forward(1)."
supported by implementations that only support unidirectional
LSPs."
OBJECT gmplsInSegmentExtraParamsPtr OBJECT gmplsInSegmentExtraParamsPtr
SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsOutSegmentDirection OBJECT gmplsOutSegmentDirection
SYNTAX GmplsSegmentDirectionTC
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. Only forward(1) needs to be "The only valid value for unidrectional LSPs is forward(1)."
supported by implementations that only support unidirectional
LSPs."
OBJECT gmplsOutSegmentTTLDecrement OBJECT gmplsOutSegmentTTLDecrement
SYNTAX Unsigned32 (0..255)
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsOutSegmentExtraParamsPtr OBJECT gmplsOutSegmentExtraParamsPtr
SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { gmplsLsrCompliances 2 } ::= { gmplsLsrCompliances 2 }
gmplsInterfaceGroup OBJECT-GROUP gmplsInterfaceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsInterfaceSignalingCaps, gmplsInterfaceSignalingCaps,
gmplsInterfaceRsvpHelloPeriod gmplsInterfaceRsvpHelloPeriod
} }
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for GMPLS interface configuration "Collection of objects needed for GMPLS interface configuration
and performance information." and performance information."
::= { gmplsLsrGroups 1 } ::= { gmplsLsrGroups 1 }
gmplsInSegmentGroup OBJECT-GROUP gmplsInSegmentGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsInSegmentDirection, gmplsInSegmentDirection,
gmplsInSegmentExtraParamsPtr gmplsInSegmentExtraParamsPtr
skipping to change at page 22, line 8 skipping to change at page 21, line 38
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement a GMPLS out-segment." "Collection of objects needed to implement a GMPLS out-segment."
::= { gmplsLsrGroups 3 } ::= { gmplsLsrGroups 3 }
END END
8. GMPLS Label MIB Definitions 8. GMPLS Label MIB Definitions
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3032], [RFC3289], [RFC2578], [RFC2579], [RFC2580], [GMPLSTCMIB], [RFC3811],
[RFC3471], [RFC3811], [RFC3945], [RFC3946] and [GMPLSTCMIB]. [RFC2863], [RFC3289] and [RFC3813].
GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
RowStatus, StorageType RowStatus, StorageType
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
InterfaceIndexOrZero InterfaceIndexOrZero
FROM IF-MIB -- RFC2863 FROM IF-MIB -- RFC2863
IndexIntegerNextFree IndexIntegerNextFree
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
FROM DIFFSERV-MIB -- RFC3289 FROM DIFFSERV-MIB -- RFC3289
MplsLabel, mplsStdMIB MplsLabel, mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB -- RFC3811
GmplsLabelTypeTC, GmplsFreeformLabelTC GmplsLabelTypeTC, GmplsFreeformLabelTC
FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB
-- RFC-Editor. Please resolve the reference above to GMPLSTCMIB
-- to use the assigned RFC number and remove this note
; ;
gmplsLabelStdMIB MODULE-IDENTITY gmplsLabelStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200603020001Z" -- 2 March 2006 00:00:01 GMT "200604060001Z" -- 06 April 2006 00:00:01 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working Group" "IETF Common Control And Measurement Plane (CCAMP) 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
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
skipping to change at page 23, line 12 skipping to change at page 22, line 46
-- RFC Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
This MIB module contains managed object definitions for labels This MIB module contains managed object definitions for labels
within GMPLS systems as defined in: within GMPLS systems as defined in:
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, Berger, L. (Editor), RFC 3471, Functional Description, Berger, L. (Editor), RFC 3471,
January 2003." January 2003."
REVISION REVISION
"200603020001Z" -- 2 March 2006 00:00:01 GMT "200604060001Z" -- 06 April 2006 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXX." "Initial version issued as part of RFC XXX."
::= { mplsStdMIB ZZZ } ::= { mplsStdMIB XXX }
-- RFC Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
-- RFC Editor. Please replace ZZZ above with the OID assigned by IANA -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
-- and remove this note -- and remove this note
-- no notifications are currently defined. -- no notifications are currently defined.
gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 }
gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 }
gmplsLabelIndexNext OBJECT-TYPE gmplsLabelIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 24, line 17 skipping to change at page 24, line 4
desired. desired.
Each entry in this table represents an individual GMPLS label Each entry in this table represents an individual GMPLS label
value. Labels in the tables in other MIB modules may be referred value. Labels in the tables in other MIB modules may be referred
to using row pointer into this table. The indexing of this table to using row pointer into this table. The indexing of this table
provides for arbitrary indexing and also for concatenation of provides for arbitrary indexing and also for concatenation of
labels. labels.
For an example of label concatenation see RFC3945 section 7.1. For an example of label concatenation see RFC3945 section 7.1.
In essence, a GMPLS label may be composite in order to identify In essence, a GMPLS label may be composite in order to identify
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
a set of resources in the data plane. Practial examples are a set of resources in the data plane. Practial examples are
timeslots and wavelength sets (which are not contiguous like timeslots and wavelength sets (which are not contiguous like
wavebands). wavebands).
The indexing mechanism allows multiple entries in this table to The indexing mechanism allows multiple entries in this table to
be seen as a sequence of labels that should be concatenated. be seen as a sequence of labels that should be concatenated.
Ordering is potentially very sensitive for concatenation." Ordering is potentially very sensitive for concatenation."
REFERENCE REFERENCE
"1. Generalized Multiprotocol Label Switching (GMPLS) "1. Generalized Multiprotocol Label Switching (GMPLS)
Architecture, RFC 3945, section 7.1," Architecture, RFC 3945, section 7.1,"
skipping to change at page 25, line 15 skipping to change at page 25, line 4
gmplsLabelInterface, gmplsLabelInterface,
gmplsLabelIndex, gmplsLabelIndex,
gmplsLabelSubindex } gmplsLabelSubindex }
::= { gmplsLabelTable 1 } ::= { gmplsLabelTable 1 }
GmplsLabelEntry ::= SEQUENCE { GmplsLabelEntry ::= SEQUENCE {
gmplsLabelInterface InterfaceIndexOrZero, gmplsLabelInterface InterfaceIndexOrZero,
gmplsLabelIndex Unsigned32, gmplsLabelIndex Unsigned32,
gmplsLabelSubindex Unsigned32, gmplsLabelSubindex Unsigned32,
gmplsLabelType GmplsLabelTypeTC, gmplsLabelType GmplsLabelTypeTC,
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
gmplsLabelMplsLabel MplsLabel, gmplsLabelMplsLabel MplsLabel,
gmplsLabelPortWavelength Unsigned32, gmplsLabelPortWavelength Unsigned32,
gmplsLabelFreeform GmplsFreeformLabelTC, gmplsLabelFreeform GmplsFreeformLabelTC,
gmplsLabelSonetSdhSignalIndex Integer32, gmplsLabelSonetSdhSignalIndex Integer32,
gmplsLabelSdhVc Integer32, gmplsLabelSdhVc Integer32,
gmplsLabelSdhVcBranch Integer32, gmplsLabelSdhVcBranch Integer32,
gmplsLabelSonetSdhBranch Integer32, gmplsLabelSonetSdhBranch Integer32,
gmplsLabelSonetSdhGroupBranch Integer32, gmplsLabelSonetSdhGroupBranch Integer32,
gmplsLabelWavebandId Unsigned32, gmplsLabelWavebandId Unsigned32,
gmplsLabelWavebandStart Unsigned32, gmplsLabelWavebandStart Unsigned32,
skipping to change at page 25, line 36 skipping to change at page 25, line 27
gmplsLabelStorageType StorageType, gmplsLabelStorageType StorageType,
gmplsLabelRowStatus RowStatus gmplsLabelRowStatus RowStatus
} }
gmplsLabelInterface OBJECT-TYPE gmplsLabelInterface OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interface on which this label is used. If this object is set "The interface on which this label is used. If this object is set
to zero, the label has or could have applicability across the to zero, the label MUST have applicability across the
whole system and is not limited to a single interface." whole system and is not limited to a single interface."
::= { gmplsLabelEntry 1 } ::= { gmplsLabelEntry 1 }
gmplsLabelIndex OBJECT-TYPE gmplsLabelIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary index into the table to identify a label. "An arbitrary index into the table to identify a label.
Note that implementations that are representing 32 bit labels Note that implementations that are representing 32 bit labels
within this table MAY choose to align this index with the value within this table MAY choose to align this index with the value
of the label and this may result in the use of the value zero. of the label and this may result in the use of the value zero
Such implementation should be aware of the implications of since it represents a valid label value. Such implementation
sparsely populated tables. should be aware of the implications of sparsely populated
tables.
A management application may read the gmplsLabelIndexNext A management application may read the gmplsLabelIndexNext
object to find a suitable value for this object." object to find a suitable value for this object."
::= { gmplsLabelEntry 2 } ::= { gmplsLabelEntry 2 }
gmplsLabelSubindex OBJECT-TYPE gmplsLabelSubindex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
"In conjunction with gmplsLabelInterface and gmplsLabelIndex, "In conjunction with gmplsLabelInterface and gmplsLabelIndex,
this object uniquely identifies this row. This sub-index allows this object uniquely identifies this row. This sub-index allows
a single GMPLS label to be defined as a concatenation of labels. a single GMPLS label to be defined as a concatenation of labels.
This is particularly useful in TDM. 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 lowest gmplsLabelSubindex appearing first. Note that all
sub-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 that gmplsLabelInterface and gmplsLabelIndex values. For labels that
are not composed of concatenated sub-labels, this value SHOULD are not composed of concatenated sub-labels, this value SHOULD
skipping to change at page 27, line 4 skipping to change at page 26, line 47
Functional Description, RFC 3471, section 3." Functional Description, RFC 3471, section 3."
::= { 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) if this "The value of an MPLS label (that is a packet label) if this
table is used to store it. This may be used in MPLS systems even table is used to store it. This may be used in MPLS systems even
though the label values can be adequately stored in the MPLS MIB though the label values can be adequately stored in the MPLS MIB
modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Further, in modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Further, in
mixed MPLS and GMPLS systems it may be advantageous to store all mixed MPLS and GMPLS systems it may be advantageous to store all
labels in a single label table. Lastly, in GMPLS systems where labels in a single label table. Lastly, in GMPLS systems where
packet labels are used (that is in systems that use GMPLS packet labels are used (that is in systems that use GMPLS
signaling and GMPLS labels for packet switching) it may be signaling and GMPLS labels for packet switching) it may be
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
desirable to use this table. 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). This object cannot be modified if to gmplsMplsLabel (1). This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"1. MPLS Label Stack Encoding, RFC 3032." "1. MPLS Label Stack Encoding, RFC 3032."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 5 } ::= { gmplsLabelEntry 5 }
skipping to change at page 28, line 4 skipping to change at page 27, line 47
to one of the standardized label encoding or that an to one of the standardized label encoding or that an
implementation chooses to represent as an octet string without implementation chooses to represent as an octet string without
further decoding. Only valid if gmplsLabelType is set to further decoding. Only valid if gmplsLabelType is set to
gmplsFreeformLabel(3). This object cannot be modified gmplsFreeformLabel(3). This object cannot be modified
if gmplsLabelRowStatus is active(1)." if gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2." Functional Description, RFC 3471, section 3.2."
DEFVAL { '00'h } DEFVAL { '00'h }
::= { gmplsLabelEntry 7 } ::= { gmplsLabelEntry 7 }
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 Generalized Label. "The Signal Index value (S) of a SONET or SDH Generalized Label.
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
Zero indicates that this field is not significant. Only valid if Zero indicates that this field is not significant. Only valid if
gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if gmplsLabelRowStatus is This object cannot be modified if gmplsLabelRowStatus is
active(1)." active(1)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 3946, section 3." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 8 } ::= { gmplsLabelEntry 8 }
skipping to change at page 29, line 4 skipping to change at page 28, line 50
"The VC Branch Indicator (K) of an SDH Generalized Label. Zero "The VC Branch Indicator (K) of an SDH Generalized Label. Zero
indicates that this field is non-significant. indicates that this field is non-significant.
Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This
object cannot be modified if gmplsLabelRowStatus is active(1)." object cannot be modified if gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 3946, section 3." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 10 } ::= { gmplsLabelEntry 10 }
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
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
DESCRIPTION DESCRIPTION
"The Branch Indicator (L) of a SONET or SDH Generalized Label. "The Branch Indicator (L) of a SONET or SDH Generalized Label.
Zero indicates that this field is non-significant. Zero indicates that this field is non-significant.
Only valid gmplsLabelType is set to gmplsSonetLabel(4) or Only valid gmplsLabelType is set to gmplsSonetLabel(4) or
gmplsSdhLabel(5). This object cannot be modified if gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 3946, section 3." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
skipping to change at page 30, line 4 skipping to change at page 29, line 50
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The waveband identifier component of a waveband label. Only "The waveband identifier component of a waveband label. Only
valid if gmplsLabelType is set to gmplsWavebandLabel(6). This valid if gmplsLabelType is set to gmplsWavebandLabel(6). This
object cannot be modified if gmplsLabelRowStatus is active(1)." object cannot be modified if gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3." Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 13 } ::= { gmplsLabelEntry 13 }
gmplsLabelWavebandStart OBJECT-TYPE gmplsLabelWavebandStart OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
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 gmplsWavebandLabel(6). Only valid if gmplsLabelType is set to gmplsWavebandLabel(6).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.3." Functional Description, RFC 3471, section 3.3."
DEFVAL { 0 } DEFVAL { 0 }
skipping to change at page 31, line 4 skipping to change at page 30, line 50
pointers to this row. In particular, the storage type of this pointers to this row. In particular, the storage type of this
row must be at least as permanent as that of any row that point row must be at least as permanent as that of any row that point
to it. to it.
Conceptual rows having the value 'permanent' need not Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row." allow write-access to any columnar objects in the row."
REFERENCE REFERENCE
"1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2." "1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2."
DEFVAL { volatile } DEFVAL { volatile }
::= { gmplsLabelEntry 16 } ::= { gmplsLabelEntry 16 }
gmplsLabelRowStatus OBJECT-TYPE gmplsLabelRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or delete a row in "This variable is used to create, modify, and/or delete a row in
this table. When a row in this table has a row in the active(1) this table. When a row in this table has a row in the active(1)
state, no objects in this row can be modified except the state, no objects in this row can be modified except the
gmplsLabelRowStatus and gmplsLabelStorageType. gmplsLabelRowStatus and gmplsLabelStorageType.
The gmplsLabelType object does not have a default and must be The gmplsLabelType object does not have a default and must be
set before a row can become active. The corresponding label set before a row can become active. The corresponding label
skipping to change at page 32, line 4 skipping to change at page 31, line 50
gmplsWavebandLabel(6) gmplsLabelWavebandId gmplsWavebandLabel(6) gmplsLabelWavebandId
gmplsLabelWavebandStart gmplsLabelWavebandStart
gmplsLabelWavebandEnd" gmplsLabelWavebandEnd"
::= { gmplsLabelEntry 17 } ::= { gmplsLabelEntry 17 }
gmplsLabelGroups gmplsLabelGroups
OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 }
gmplsLabelCompliances gmplsLabelCompliances
OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 }
gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
"Compliance requirement for implementations that only provide "Compliance requirement for implementations that only provide
read-only support for GMPLS-LABEL-STD-MIB. Such devices can then read-only support for GMPLS-LABEL-STD-MIB. Such devices can then
be monitored but cannot be configured using this MIB module." be monitored but cannot be configured using this MIB module."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented by LSRs claiming -- The mandatory groups have to be implemented by LSRs claiming
-- support for this MIB module. This MIB module is, however, not -- support for this MIB module. This MIB module is, however, not
-- mandatory for a working implementation of a GMPLS LSR with full -- mandatory for a working implementation of a GMPLS LSR with full
-- MIB support if the GMPLS labels in use can be represented within -- MIB support if the GMPLS labels in use can be represented within
-- a 32 bit quantity. -- a 32 bit quantity.
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsLabelTableGroup gmplsLabelTableGroup
} }
GROUP gmplsLabelTableGroup
DESCRIPTION
"This group is mandatory for devices which support the
gmplsLabelTable."
GROUP gmplsLabelPacketGroup GROUP gmplsLabelPacketGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for implementations that "This group extends gmplsLabelTableGroup for implementations that
support packet labels. It is optional for implementations that support packet labels. It is optional for implementations that
do not support packet labels." do not support packet labels."
GROUP gmplsLabelPortWavelengthGroup GROUP gmplsLabelPortWavelengthGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for implementations that "This group extends gmplsLabelTableGroup for implementations that
support port and wavelength labels. It is optional for support port and wavelength labels. It is optional for
skipping to change at page 33, line 4 skipping to change at page 32, line 45
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for implementations that "This group extends gmplsLabelTableGroup for implementations that
support freeform labels. It is optional for implementations that support freeform labels. It is optional for implementations that
do not support freeform labels." do not support freeform labels."
GROUP gmplsLabelSonetSdhGroup GROUP gmplsLabelSonetSdhGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for implementations that "This group extends gmplsLabelTableGroup for implementations that
support SONET or SDH labels. It is optional for implementations support SONET or SDH labels. It is optional for implementations
that do not support SONET or SDH labels." that do not support SONET or SDH labels."
GROUP gmplsLabelWavebandGroup GROUP gmplsLabelWavebandGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for implementations that "This group extends gmplsLabelTableGroup for implementations that
support Waveband labels. It is optional for implementations that support Waveband labels. It is optional for implementations that
do not support Waveband labels." do not support Waveband labels."
OBJECT gmplsLabelType OBJECT gmplsLabelType
MIN-ACCESS read-only MIN-ACCESS read-only
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelMplsLabel OBJECT gmplsLabelMplsLabel
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelPortWavelength OBJECT gmplsLabelPortWavelength
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 34, line 4 skipping to change at page 33, line 48
OBJECT gmplsLabelSonetSdhBranch OBJECT gmplsLabelSonetSdhBranch
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelSonetSdhGroupBranch OBJECT gmplsLabelSonetSdhGroupBranch
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelWavebandId OBJECT gmplsLabelWavebandId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
OBJECT gmplsLabelWavebandStart OBJECT gmplsLabelWavebandStart
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelWavebandEnd OBJECT gmplsLabelWavebandEnd
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelStorageType OBJECT gmplsLabelStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelRowStatus OBJECT gmplsLabelRowStatus
MIN-ACCESS read-only
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Support for notInService, createAndWait and notReady is not "Support for notInService, createAndWait and notReady is not
required." required."
::= { gmplsLabelCompliances 1 } ::= { gmplsLabelCompliances 1 }
gmplsLabelModuleFullCompliance MODULE-COMPLIANCE gmplsLabelModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the complete "Compliance statement for agents that support the complete
GMPLS-LABEL-STD-MIB module." GMPLS-LABEL-STD-MIB module.
MODULE -- this module The mandatory groups have to be implemented by GMPLS LSRs
claiming support for this MIB module. This MIB module is,
however, not mandatory for a working implementation of a GMPLS
LSR with full MIB support if the GMPLS labels in use can be
represented within a 32 bit quantity."
-- The mandatory groups have to be implemented by GMPLS LSRs MODULE -- this module
-- claiming support for this MIB module. This MIB module is,
-- however, not mandatory for a working implementation of a GMPLS
-- LSR with full MIB support if the GMPLS labels in use can be
-- represented within a 32 bit quantity.
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsLabelTableGroup, gmplsLabelTableGroup
gmplsLabelPacketGroup,
gmplsLabelPortWavelengthGroup,
gmplsLabelFreeformGroup,
gmplsLabelSonetSdhGroup,
gmplsLabelWavebandGroup
} }
OBJECT gmplsLabelRowStatus OBJECT gmplsLabelRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
"Support for createAndWait and notReady is not required." "Support for createAndWait and notReady is not required."
::= { gmplsLabelCompliances 2 } ::= { gmplsLabelCompliances 2 }
gmplsLabelTableGroup OBJECT-GROUP gmplsLabelTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelIndexNext, gmplsLabelIndexNext,
gmplsLabelType, gmplsLabelType,
gmplsLabelStorageType, gmplsLabelStorageType,
gmplsLabelRowStatus gmplsLabelRowStatus
} }
skipping to change at page 36, line 20 skipping to change at page 36, line 4
"Object needed to implement Port and Wavelength labels." "Object needed to implement Port and Wavelength labels."
::= { gmplsLabelGroups 3 } ::= { gmplsLabelGroups 3 }
gmplsLabelFreeformGroup OBJECT-GROUP gmplsLabelFreeformGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelFreeform gmplsLabelFreeform
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement Freeform labels." "Object needed to implement Freeform labels."
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
::= { gmplsLabelGroups 4 } ::= { gmplsLabelGroups 4 }
gmplsLabelSonetSdhGroup OBJECT-GROUP gmplsLabelSonetSdhGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelSonetSdhSignalIndex, gmplsLabelSonetSdhSignalIndex,
gmplsLabelSdhVc, gmplsLabelSdhVc,
gmplsLabelSdhVcBranch, gmplsLabelSdhVcBranch,
gmplsLabelSonetSdhBranch, gmplsLabelSonetSdhBranch,
gmplsLabelSonetSdhGroupBranch gmplsLabelSonetSdhGroupBranch
} }
skipping to change at page 37, line 23 skipping to change at page 37, line 4
There are a number of management objects defined in these MIB modules There are a number of management objects defined in these MIB modules
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
and gmplsLabelTable collectively contain objects to provision and gmplsLabelTable collectively contain objects to provision
GMPLS interfaces, LSPs and their associated parameters on a Label GMPLS interfaces, LSPs and their associated parameters on a Label
Switching Router (LSR). Unauthorized write access to objects in Switching Router (LSR). Unauthorized write access to objects in
these tables, could result in disruption of traffic on the these tables, could result in disruption of traffic on the
network. This is especially true if an LSP has already been network. This is especially true if an LSP has already been
established. 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
skipping to change at page 38, line 21 skipping to change at page 38, line 4
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 [RFC3813]. The authors would like to express 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
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
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. Tom Petch and Bert Wijnen provided useful input compilation issues. Tom Petch and Bert Wijnen provided useful input
in the final stages of review. in the final stages of review.
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
skipping to change at page 39, line 17 skipping to change at page 39, line 4
The IANA is requested to assign { mplsStdMIB ZZZ } to the The IANA is requested to assign { mplsStdMIB ZZZ } to the
GMPLS-LABEL-STD-MIB module specified in this document, and to record GMPLS-LABEL-STD-MIB module specified in this document, and to record
the assignment in the SMI Numbers registry. the assignment in the SMI Numbers registry.
-- RFC Editor. Please replace ZZZ above with the OID assigned by IANA -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA
-- and remove this note -- and remove this note
12. References 12. References
12.1. Normative References 12.1. Normative References
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[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,
skipping to change at page 40, line 18 skipping to change at page 40, line 5
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Resource ReserVation Protocol-Traffic (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January Engineering (RSVP-TE) Extensions", RFC 3473, January
2003. 2003.
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions and for Multiprotocol Label Switching (MPLS)
Management", RFC 3811, June 2004. Management", RFC 3811, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
(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
skipping to change at page 41, line 18 skipping to change at page 41, line 4
(CR-LDP) Extensions", RFC 3472, January 2003. (CR-LDP) Extensions", RFC 3472, January 2003.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB)", Engineering (TE) Management Information Base (MIB)",
RFC 3812, June 2004. RFC 3812, June 2004.
13. Contact Information 13. Contact Information
Thomas D. Nadeau Thomas D. Nadeau
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Phone: +44-(0)-1978-860944 Phone: +44-(0)-1978-860944
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
skipping to change at page 42, line 6 skipping to change at page 42, line 4
Email: tim.hall@dataconnection.com Email: tim.hall@dataconnection.com
Ed Harrison Ed Harrison
Data Connection Ltd. Data Connection Ltd.
100 Church Street 100 Church Street
Enfield, Middlesex, EN2 6BQ, UK Enfield, Middlesex, EN2 6BQ, UK
Phone: +44 20 8366 1177 Phone: +44 20 8366 1177
Email: ed.harrison@dataconnection.com Email: ed.harrison@dataconnection.com
14. Intellectual Property Considerations 14. Intellectual Property Considerations
draft-ietf-ccamp-gmpls-lsr-mib-12.txt April 11, 2006
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
 End of changes. 95 change blocks. 
70 lines changed or deleted 143 lines changed or added

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