draft-ietf-ccamp-gmpls-lsr-mib-15.txt   rfc4803.txt 
Network Working Group Thomas D. Nadeau, Ed. Network Working Group T. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Request for Comment: 4803 Cisco Systems, Inc.
Proposed Status: Standards Track Category: Standards Track A. Farrel, Ed.
Expires: March 2007 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
February 2007
September 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-15.txt Status of This Memo
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six This document specifies an Internet standards track protocol for the
months and may be updated, replaced, or obsoleted by other documents Internet community, and requests discussion and suggestions for
at any time. It is inappropriate to use Internet-Drafts as improvements. Please refer to the current edition of the "Internet
reference material or to cite them other than as "work in progress." Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The IETF Trust (2007).
http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects 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).
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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 Internet-Standard Management Framework ....... 4 3. The Internet-Standard Management Framework ......................4
4. Outline .......................................... 4 4. Outline .........................................................5
4.1 MIB Modules ..................................... 4 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 ........ 5 4.2. Configuring Statically Provisioned LSPs ....................5
5. Bidirectional LSPs ............................... 6 5. Bidirectional LSPs ..............................................6
6. Example of LSP Setup ............................. 6 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 ......................... 36 9. Security Considerations ........................................36
10. Acknowledgments ................................ 37 10. Acknowledgments ...............................................37
11. IANA Considerations ............................ 38 11. IANA Considerations ...........................................38
12. References ..................................... 38 12. References ....................................................38
12.1. Normative References ......................... 38 12.1. Normative References .....................................38
12.2. Informative References ....................... 40 12.2. Informative References ...................................40
13. Contact Information ............................ 40
14. Intellectual Property Considerations ........... 41
15. Full Copyright Statement ....................... 42
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) [RFC3945] Label Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] Label
Switching Router (LSR). Switching Router (LSR).
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119, document are to be interpreted as described in BCP 14, RFC 2119
reference [RFC2119]. [RFC2119].
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 advantage of additional MIB objects defined in these MIB modules take advantage of additional MIB objects defined in these MIB modules
that are applicable to MPLS-TE. that are applicable to MPLS-TE.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006 The GMPLS LSR MIB module (GMPLS-LSR-STD-MIB), defined in this
document, extends the MPLS-LSR-STD-MIB module [RFC3813] through a
The GMPLS LSR MIB module (GMPLS-LSR-STD-MIB) defined in this document series of sparse augmentations of the MIB tables. The only additions
extends the MPLS-LSR-STD-MIB module [RFC3813] through a series of are for support of GMPLS or to support the increased complexity of
sparse augmentations of the MIB tables. The only additions are for MPLS and GMPLS systems.
support of GMPLS or to support the increased complexity of MPLS and
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-
GMPLS-LSR-STD-MIB support an implementation needs only to add support MIB support, an implementation needs only to add support for the
for the additional tables and objects defined in GMPLS-LSR-STD-MIB. additional tables and objects defined in GMPLS-LSR-STD-MIB. The
The gmplsInterfaceSignalingCaps object allows an implementation to gmplsInterfaceSignalingCaps object allows an implementation to use
use the objects and tables of GMPLS-LSR-STD-MIB without supporting the objects and tables of GMPLS-LSR-STD-MIB without supporting the
the GMPLS protocols. 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
document allows labels to be configured and examined, and supports this document, allows labels to be configured and examined, and it
more varieties of label as appropriate for GMPLS. Labels may be supports more varieties of labels as appropriate for GMPLS. Labels
referenced using a row pointer from objects within the may be referenced using a row pointer from objects within the GMPLS-
GMPLS-LSR-STD-MIB module. MPLS implementations (MPLS-LSR-STD-MIB) may LSR-STD-MIB module. MPLS implementations (MPLS-LSR-STD-MIB) may also
also reference labels held in the GMPLS-LABEL-STD-MIB module through reference labels held in the GMPLS-LABEL-STD-MIB module through the
the various label pointer objects in the MPLS-LSR-STD-MIB module various label pointer objects in the MPLS-LSR-STD-MIB module (such as
(such as mplsInSegmentLabelPtr), and may do so without implementing mplsInSegmentLabelPtr), and may do so without implementing the
the GMPLS-LSR-STD-MIB module. 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 [RFC4802] extends the MPLS-TE-STD-MIB module [RFC3812]
with the same intentions. with the same intentions.
Textual conventions are defined in [GMPLSTCMIB] which extends the Textual conventions are defined in [RFC4801], which extends the set
set of textual conventions originally defined in [RFC3811]. of textual conventions originally 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.
cross-connect This describes the conceptual connection between a
set of in-segments and out-segments. Note that either
set may be empty; for example, a cross-connect may
connect only out-segments together with no in-segments
in the case where an LSP originates on an LSR.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006 out-segment This is analogous to a GMPLS Label on an interface.
cross-connect This describes the conceptual connection between a set
of in-segments and out-segments. Note that either set
may be empty; for example, a cross-connect may connect
only out-segments together with no in-segments 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.
The term 'upstream' is used in this document to refer to the part of The term 'upstream' is used in this document to refer to the part of
an LSP closer to the ingress than the current point of reference. an LSP that is closer to the ingress than the current point of
reference.
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 that is 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 Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
skipping to change at page 4, line 43 skipping to change at page 5, line 7
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
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. Outline 4. Outline
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.
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.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006 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) sparse
sparse augments the mplsInterfaceTable [RFC3813] to enable the augments the mplsInterfaceTable [RFC3813] to enable the GMPLS
GMPLS protocol on MPLS-capable interfaces. protocol on MPLS-capable interfaces.
- The in-segment (gmplsInSegmentTable) and out-segment - The in-segment (gmplsInSegmentTable) and out-segment
(gmplsOutSegmentTable) tables sparse augment mplsInSegmentTable and (gmplsOutSegmentTable) tables sparse augment mplsInSegmentTable
mplsOutSegmentTable [RFC3813] to enable configuration of and mplsOutSegmentTable [RFC3813] to enable configuration of
GMPLS-specific parameters for LSP segments at an LSR. GMPLS-specific parameters for LSP segments at an LSR.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
4.1.2 Summary of the GMPLS-LABEL-STD-MIB Module 4.1.2. Summary of the GMPLS-LABEL-STD-MIB Module
There is one MIB table in the GMPLS-LABEL-STD-MIB module as follows. There is one MIB table in the GMPLS-LABEL-STD-MIB module as follows:
- The gmplsLabelTable allows Generalized - The gmplsLabelTable allows Generalized Labels to be defined and
Labels to be defined and managed in a central location. managed in a central location. Generalized Labels can be of
Generalized Labels can be of variable length and have distinct variable length and have distinct bit-by-bit interpretations
bit-by-bit interpretations depending upon how they are defined depending upon how they are defined for the specific technology in
for the specific technology in which they are used. For example, which they are used. For example, labels used for MPLS packet
labels used for MPLS packet switching are different in length switching are different in length and content from labels used in
and content from labels used in TDM timeslot switching. Time Division Multiplexer (TDM) timeslot switching.
4.2. Configuring Statically Provisioned LSPs 4.2. Configuring Statically Provisioned LSPs
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-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-
GMPLS-LSR-STD-MIB module in this document. STD-MIB module in this document.
- Configuring in and out-segments using the MPLS-LSR-STD-MIB module - Configuring in-segments and out-segments using the MPLS-LSR-STD-
[RFC3813]. MIB module [RFC3813].
- Configuring GMPLS extensions to the in-segments and out-segments - Configuring GMPLS extensions to the in-segments and out-segments
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.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006 - Optionally setting up labels in the label table in the GMPLS-
LABEL-STD-MIB module in this document if the textual convention
- Optionally setting up labels in the label table in the MplsLabel [RFC3811] is not capable of holding the required label
GMPLS-LABEL-STD-MIB module in this document if the textual (for example, if the label requires more than 32 bits to encode
convention MplsLabel [RFC3811] is not capable of holding the it), or if the operator wishes to disambiguate GMPLS Label types.
required label (for example, if the label requires more than 32
bits to encode it), or if the operator wishes to disambiguate GMPLS
label types.
- Optionally specifying label stack actions in the MPLS-LSR-STD-MIB - Optionally specifying label stack actions in the MPLS-LSR-STD-MIB
module [RFC3813]. module [RFC3813].
- Optionally specifying segment traffic parameters in the - Optionally specifying segment traffic parameters in the MPLS-LSR-
MPLS-LSR-STD-MIB module [RFC3813]. STD-MIB module [RFC3813].
5. Bidirectional LSPs 5. Bidirectional LSPs
The GMPLS-LSR-STD-MIB module supports bidirectional LSPs as required The GMPLS-LSR-STD-MIB module supports bidirectional LSPs as required
for GMPLS. A single value of mplsXCIndex is shared by all of the for GMPLS. A single value of mplsXCIndex is shared by all of the
segments for the entire bidirectional LSP. This facilitates a simple segments for the entire bidirectional LSP. This facilitates a simple
reference from [RFC3812] and [GMPLSTEMIB], and makes fate-sharing reference from [RFC3812] and [RFC4802] and makes fate-sharing more
more obvious. 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.
Where an LSP is signaled using a conventional signaling protocol, the Where an LSP is signaled using a conventional signaling protocol, the
'head' of the LSP is the source of the signaling (also known as the 'head' of the LSP is the source of the signaling (also known as the
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
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
not meant to illustrate every nuance of the MIB modules, it is 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 module
[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 bidirectional LSP. Assume that, in the forward direction, the LSP
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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 that 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 bidirectional
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
labels required for each of the forward and reverse direction in- and labels required for each of the forward- and reverse-direction in-
out-segments. For the purpose of this example the forward and and out-segments. For the purpose of this example, the forward and
reverse labels on each interface will be the same, hence we need to reverse labels on each interface will be the same, hence we need to
create just two rows in the gmplsLabelTable - one for each interface. create just two rows in the gmplsLabelTable - one for each interface.
In gmplsLabelTable: In gmplsLabelTable:
{ {
gmplsLabelInterface = 12, gmplsLabelInterface = 12,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
gmplsLabelSubindex = 0, gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformLabel(3), gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0x123456789ABCDEF0 gmplsLabelFreeform = 0x123456789ABCDEF0
skipping to change at page 7, line 42 skipping to change at page 8, line 15
{ {
gmplsLabelInterface = 13, gmplsLabelInterface = 13,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
gmplsLabelSubindex = 0, gmplsLabelSubindex = 0,
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
mplsOutSegmentTable. Note that we use a row pointer to the two rows and mplsOutSegmentTable. Note that we use a row pointer to the two
in the gmplsLabelTable rather than specifying the labels explicitly rows in the gmplsLabelTable rather than specify 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.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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,
mplsInSegmentInterface = 12, -- incoming interface mplsInSegmentInterface = 12, -- 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 (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
skipping to change at page 9, line 4 skipping to change at page 9, line 19
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)
} }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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 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,
skipping to change at page 9, line 16 skipping to change at page 9, line 30
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 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)
mplsOutSegmentRowStatus = createAndWait(5) mplsOutSegmentRowStatus = createAndWait(5)
} }
These table entries are extended by entries in gmplsInSegmentTable These table entries are extended by entries in the
and gmplsOutSegmentTable. Note that the nature of the 'extends' gmplsInSegmentTable and gmplsOutSegmentTable. Note that the nature
relationship is a sparse augmentation so that the entry in of the 'extends' relationship is a sparse augmentation so that the
gmplsInSegmentTable has the same index values as the entry in entry in the gmplsInSegmentTable has the same index values as the
mplsInSegmentTable. Similarly, the entry in gmplsOutSegmentTable has entry in the mplsInSegmentTable. Similarly, the entry in the
the same index values as the entry in mplsOutSegmentTable. gmplsOutSegmentTable has the same index values as the entry in the
mplsOutSegmentTable.
First for the forward direction: First for the forward direction:
In gmplsInSegmentTable(0x00000015) In gmplsInSegmentTable(0x00000015)
{ {
gmplsInSegmentDirection = forward (1) gmplsInSegmentDirection = forward (1)
} }
In gmplsOutSegmentTable(0x00000012) In gmplsOutSegmentTable(0x00000012)
{ {
skipping to change at page 10, line 5 skipping to change at page 10, line 20
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-15.txt September 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 10, line 37 skipping to change at page 11, line 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)
} }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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 reference to the following documents:
[RFC2578], [RFC2579], [RFC2580], [GMPLSTCMIB], [RFC3811], [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3209], [RFC3443],
[RFC2863] and [RFC3813]. [RFC3468], [RFC3472], [RFC3473], [RFC3811], [RFC3813], and [RFC4801].
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 -- RFC 4801
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
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working 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 directly to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org."
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2006). This version of "Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC XXX; see the RFC itself for this MIB module is part of RFC 4803; see the RFC itself for
full legal notices. full legal notices.
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)
Architecture, Mannie et al., RFC 3945, October 2004." Architecture, Mannie et al., RFC 3945, October 2004."
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
REVISION REVISION
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXX." "Initial version issued as part of RFC 4803."
::= { mplsStdMIB YYY } ::= { mplsStdMIB 15 }
-- 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 }
gmplsInterfaceTable OBJECT-TYPE gmplsInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInterfaceEntry SYNTAX SEQUENCE OF GmplsInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies per-interface GMPLS capability and "This table specifies per-interface GMPLS capability and
associated information. It extends the information in associated information. It extends the information in the
mplsInterfaceTable of the MPLS-LSR-STD-MIB through a mplsInterfaceTable of MPLS-LSR-STD-MIB through a
sparse augmentation relationship." sparse augmentation relationship."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 1 } ::= { gmplsLsrObjects 1 }
gmplsInterfaceEntry OBJECT-TYPE gmplsInterfaceEntry OBJECT-TYPE
SYNTAX GmplsInterfaceEntry SYNTAX GmplsInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in this table is created automatically by an "A conceptual row in this table is created automatically by an
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 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-15.txt September 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 the mplsInterfaceTable exists, and a
corresponding entry in ifTable exists with ifType = mpls(166). corresponding entry in the ifTable exists with ifType = mpls(166).
If the associated entry in ifTable is operationally disabled If the associated entry in the 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 the mplsInterfaceTable is deleted, the corresponding entry
in this table MUST be deleted shortly thereafter. in this table MUST be deleted shortly thereafter.
The indexes are the same as for mplsInterfaceTable. Thus, the The indexes are the same as for the mplsInterfaceTable. Thus, the
entry with index 0 represents the per-platform label space and entry with index 0 represents the per-platform label space and
contains parameters that apply to all interfaces that contains parameters that apply to all interfaces that
participate in the per-platform label space." participate in the per-platform label space."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { gmplsInterfaceTable 1 } ::= { gmplsInterfaceTable 1 }
GmplsInterfaceEntry ::= SEQUENCE { GmplsInterfaceEntry ::= SEQUENCE {
gmplsInterfaceSignalingCaps BITS, gmplsInterfaceSignalingCaps BITS,
gmplsInterfaceRsvpHelloPeriod Unsigned32 gmplsInterfaceRsvpHelloPeriod Unsigned32
} }
gmplsInterfaceSignalingCaps OBJECT-TYPE gmplsInterfaceSignalingCaps OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
skipping to change at page 14, line 4 skipping to change at page 14, line 10
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. The Multiprotocol Label Switching (MPLS) Working Group 2. The Multiprotocol Label Switching (MPLS) Working Group
decision on MPLS signaling protocols, RFC 3468. decision on MPLS signaling protocols, RFC 3468.
3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473." 3. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
DEFVAL { { rsvpGmpls } } DEFVAL { { rsvpGmpls } }
::= { gmplsInterfaceEntry 1 } ::= { gmplsInterfaceEntry 1 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 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 Resource Reservation
this interface. A value of 0 indicates that no Hello messages Protocol (RSVP) Hello messages on this interface. A value of 0
should be sent on this interface. indicates that no Hello messages should be sent on this
interface.
This object is only valid if gmplsInterfaceSignalingCaps has no This object is only valid if gmplsInterfaceSignalingCaps has no
bits set or includes the rsvpGmpls bit." bits set or includes the rsvpGmpls bit."
REFERENCE REFERENCE
"1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209, "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
section 5. section 5.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473, 2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 9.3." section 9.3."
DEFVAL { 3000 } DEFVAL { 3000 }
::= { gmplsInterfaceEntry 2 } ::= { gmplsInterfaceEntry 2 }
gmplsInSegmentTable OBJECT-TYPE gmplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInSegmentEntry SYNTAX SEQUENCE OF GmplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table sparse augments the mplsInSegmentTable of the "This table sparse augments the mplsInSegmentTable of
MPLS-LSR-STD-MIB to provide GMPLS-specific information about MPLS-LSR-STD-MIB to provide GMPLS-specific information about
incoming segments to an LSR." incoming segments to an LSR."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 2 } ::= { gmplsLsrObjects 2 }
gmplsInSegmentEntry OBJECT-TYPE gmplsInSegmentEntry OBJECT-TYPE
SYNTAX GmplsInSegmentEntry SYNTAX GmplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
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 the mplsInSegmentTable in
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."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the direction of data flow on this "This object indicates the direction of data flow on this
segment. This object cannot be modified if segment. This object cannot be modified if
mplsInSegmentRowStatus for the corresponding entry in the mplsInSegmentRowStatus for the corresponding entry in the
mplsInSegmentTable is active(1)." mplsInSegmentTable is active(1)."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
DEFVAL { forward } DEFVAL { forward }
::= { gmplsInSegmentEntry 1 } ::= { gmplsInSegmentEntry 1 }
gmplsInSegmentExtraParamsPtr OBJECT-TYPE gmplsInSegmentExtraParamsPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Some Tunnels will run over transports that can usefully support "Some tunnels will run over transports that can usefully support
technology-specific additional parameters (for example, SONET technology-specific additional parameters (for example,
resource usage). Such can be supplied from an external table and Synchronous Optical Network (SONET) resource usage). Such can be
referenced from here. A value of zeroDotzero in this attribute supplied from an external table and referenced from here. A value
indicates that there is no such additional information." of zeroDotZero in this attribute indicates that there is no such
additional information."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { 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
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."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 3 } ::= { gmplsLsrObjects 3 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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 the mplsOutSegmentTable of
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 mplsOutSegmentStorageType in the corresponding entry of the of mplsOutSegmentStorageType in the corresponding entry of the
mplsOutSegmentTable." mplsOutSegmentTable."
REFERENCE REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR) "1. Multiprotocol Label Switching (MPLS) Label Switching
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
INDEX { mplsOutSegmentIndex } INDEX { mplsOutSegmentIndex }
::= { gmplsOutSegmentTable 1 } ::= { gmplsOutSegmentTable 1 }
GmplsOutSegmentEntry ::= SEQUENCE { GmplsOutSegmentEntry ::= SEQUENCE {
gmplsOutSegmentDirection GmplsSegmentDirectionTC, gmplsOutSegmentDirection GmplsSegmentDirectionTC,
gmplsOutSegmentTTLDecrement Unsigned32, gmplsOutSegmentTTLDecrement Unsigned32,
gmplsOutSegmentExtraParamsPtr RowPointer gmplsOutSegmentExtraParamsPtr RowPointer
} }
gmplsOutSegmentDirection OBJECT-TYPE gmplsOutSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirectionTC SYNTAX GmplsSegmentDirectionTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the direction of data flow on this "This object indicates the direction of data flow on this
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
Router Management Information Base (MIB), RFC 3813." Router (LSR) Management Information Base (MIB), RFC 3813."
DEFVAL { forward } DEFVAL { forward }
::= { gmplsOutSegmentEntry 1 } ::= { gmplsOutSegmentEntry 1 }
gmplsOutSegmentTTLDecrement OBJECT-TYPE gmplsOutSegmentTTLDecrement OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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 Time
of any payload packets forwarded on this segment if per-hop to Live (TTL) of any payload packets forwarded on this segment if
decrementing is being done. per-hop decrementing is being done.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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.
See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable
of GMPLS-TE-STD-MIB for a value by which to decrement the TTL of GMPLS-TE-STD-MIB for a value by which to decrement the TTL
for the whole of a tunnel. for the whole of a tunnel.
This object cannot be modified if mplsOutSegmentRowStatus for This object cannot be modified if mplsOutSegmentRowStatus for
the associated entry in the mplsOutSegmentTable is active(1)." the associated entry in the mplsOutSegmentTable is active(1)."
REFERENCE REFERENCE
"1. Time To Live (TTL) Processing in Multi-Protocol Label "1. Time To Live (TTL) Processing in Multi-Protocol Label
Switching (MPLS) Networks, RFC 3443. Switching (MPLS) Networks, RFC 3443.
2. Generalized Multiprotocol Label Switching (GMPLS) Traffic 2. Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base, RFC XXX." Engineering Management Information Base, RFC 4802."
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 usefully support "Some tunnels will run over transports that can usefully support
technology-specific additional parameters (for example, SONET technology-specific additional parameters (for example, SONET
resource usage). Such can be supplied from an external table and resource usage). Such can be supplied from an external table and
referenced from here. referenced from here.
A value of zeroDotzero in this attribute indicates that there is A value of zeroDotZero in this attribute indicates that there is
no such additional information." no such additional information."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { 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.
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 The mandatory group has to be implemented by all LSRs that
originate, terminate or act as transit for TE-LSPs/tunnels. originate, terminate, or act as transit for TE-LSPs/tunnels.
In addition, depending on the type of tunnels supported, other In addition, depending on the type of tunnels supported, other
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
groups become mandatory as explained below." 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-STD-MIB, RFC3813 MODULE MPLS-LSR-STD-MIB -- The MPLS-LSR-STD-MIB, RFC3813
skipping to change at page 19, line 4 skipping to change at page 19, line 19
OBJECT gmplsOutSegmentTTLDecrement OBJECT gmplsOutSegmentTTLDecrement
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsInSegmentExtraParamsPtr OBJECT gmplsInSegmentExtraParamsPtr
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-15.txt September 2006
OBJECT gmplsOutSegmentExtraParamsPtr OBJECT gmplsOutSegmentExtraParamsPtr
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.
skipping to change at page 20, line 4 skipping to change at page 20, line 16
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsInterfaceGroup, gmplsInterfaceGroup,
gmplsInSegmentGroup, gmplsInSegmentGroup,
gmplsOutSegmentGroup gmplsOutSegmentGroup
} }
OBJECT gmplsInterfaceSignalingCaps OBJECT gmplsInterfaceSignalingCaps
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-15.txt September 2006
OBJECT gmplsInterfaceRsvpHelloPeriod OBJECT gmplsInterfaceRsvpHelloPeriod
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
skipping to change at page 20, line 46 skipping to change at page 21, line 8
::= { gmplsLsrCompliances 2 } ::= { gmplsLsrCompliances 2 }
gmplsInterfaceGroup OBJECT-GROUP gmplsInterfaceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsInterfaceSignalingCaps, gmplsInterfaceSignalingCaps,
gmplsInterfaceRsvpHelloPeriod gmplsInterfaceRsvpHelloPeriod
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects which provide additional "Collection of objects that provide additional
information for an MPLS interface and are needed information for an MPLS interface and are needed
for GMPLS interface configuration and performance for GMPLS interface configuration and performance
information." information."
::= { gmplsLsrGroups 1 } ::= { gmplsLsrGroups 1 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
gmplsInSegmentGroup OBJECT-GROUP gmplsInSegmentGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsInSegmentDirection, gmplsInSegmentDirection,
gmplsInSegmentExtraParamsPtr gmplsInSegmentExtraParamsPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects which provide additional "Collection of objects that provide additional
information for an MPLS in-segment and are needed information for an MPLS in-segment and are needed
for GMPLS in-segment configuration and performance for GMPLS in-segment configuration and performance
information." information."
::= { gmplsLsrGroups 2 } ::= { gmplsLsrGroups 2 }
gmplsOutSegmentGroup OBJECT-GROUP gmplsOutSegmentGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsOutSegmentDirection, gmplsOutSegmentDirection,
gmplsOutSegmentTTLDecrement, gmplsOutSegmentTTLDecrement,
gmplsOutSegmentExtraParamsPtr gmplsOutSegmentExtraParamsPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects which provide additional "Collection of objects that provide additional
information for an MPLS out-segment and are needed information for an MPLS out-segment and are needed
for GMPLS out-segment configuration and performance for GMPLS out-segment configuration and performance
information." information."
::= { gmplsLsrGroups 3 } ::= { gmplsLsrGroups 3 }
END END
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
8. GMPLS Label MIB Definitions 8. GMPLS Label MIB Definitions
This MIB module makes references to the following documents. This MIB module makes reference to the following documents:
[RFC2578], [RFC2579], [RFC2580], [GMPLSTCMIB], [RFC3811], [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3032], [RFC3289],
[RFC2863], [RFC3289], [RFC3813], and [RFC3471]. [RFC3471], [RFC3811], and [RFC4801].
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
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 -- RFC 4801
; ;
gmplsLabelStdMIB MODULE-IDENTITY gmplsLabelStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working 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 directly to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org."
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2006). This version of "Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC XXX; see the RFC itself for this MIB module is part of RFC 4803; see the RFC itself for
full legal notices. full legal notices.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702270000Z" -- 27 February 2007 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version issued as part of RFC XXX." "Initial version issued as part of RFC 4803."
::= { mplsStdMIB ZZZ } ::= { mplsStdMIB 16 }
-- 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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an unused value for gmplsLabelIndex, "This object contains an unused value for gmplsLabelIndex,
or a zero to indicate that no unused value exists or is or a zero to indicate that no unused value exists or is
available. available.
A management application wishing to create a row in the A management application wishing to create a row in the
gmplsLabelTable may read this object and then attempt to gmplsLabelTable may read this object and then attempt to
create a row in the table. If row creation fails (because create a row in the table. If row creation fails (because
another application has already created a row with the another application has already created a row with the
supplied index) the management application should read this supplied index), the management application should read this
object again to get a new index value. object again to get a new index value.
When a row is created in the gmplsLabelTable with the When a row is created in the gmplsLabelTable with the
gmplsLabelIndex value held by this object, an implementation gmplsLabelIndex value held by this object, an implementation
MUST change the value in this object." MUST change the value in this object."
::= { gmplsLabelObjects 1 } ::= { gmplsLabelObjects 1 }
gmplsLabelTable OBJECT-TYPE gmplsLabelTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsLabelEntry SYNTAX SEQUENCE OF GmplsLabelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of GMPLS Labels. This table allows the representation "Table of GMPLS Labels. This table allows the representation
of the more complex label forms required for GMPLS which cannot of the more complex label forms required for GMPLS that cannot
be held within the textual convention MplsLabel. That is labels be held within the TEXTUAL-CONVENTION MplsLabel; that is, labels
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006 that cannot be encoded within 32 bits. It is, nevertheless, also
capable of holding 32-bit labels or regular MPLS Labels if
that cannot be encoded within 32 bits. It is, nevertheless also
capable of holding 32 bit labels or regular MPLS labels if
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. The representation of Labels in tables in other MIB
to using a row pointer into this table. The indexing of this modules may be achieved by a referrence to an entry in this
table provides for arbitrary indexing and also for table by means of a row pointer into this table. The indexing
of this table provides for arbitrary indexing and also for
concatenation of labels. concatenation of labels.
For an example of label concatenation see RFC3945 section 7.1. For an example of label concatenation, see RFC 3945, 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
a set of resources in the data plane. Practical examples are a set of resources in the data plane. Practical 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."
::= { gmplsLabelObjects 2 } ::= { gmplsLabelObjects 2 }
gmplsLabelEntry OBJECT-TYPE gmplsLabelEntry OBJECT-TYPE
SYNTAX GmplsLabelEntry SYNTAX GmplsLabelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a single label value. There "An entry in this table represents a single label value. There
are three indexes into the table. are three indexes into the table.
- The interface index may be helpful to distinguish which - The interface index may be helpful to distinguish which
labels are in use on which interfaces or to handle cases labels are in use on which interfaces or to handle cases
where there are a very large number of labels in use in the where there are a very large number of labels in use in the
system. When label representation is desired to apply to the system. When label representation is desired to apply to the
whole system or when it is not important to distinguish whole system or when it is not important to distinguish
labels by their interfaces, this index MAY be set to zero. labels by their interfaces, this index MAY be set to zero.
- The label index provides a way of identifying the label. - The label index provides a way of identifying the label.
- The label sub-index is only used for concatenated labels. It - The label sub-index is only used for concatenated labels. It
identifies each component label. When non-concatenated labels identifies each component label. When non-concatenated labels
are used, this index SHOULD be set to zero. are used, this index SHOULD be set to zero.
A storage type object is supplied to control the storage type A storage type object is supplied to control the storage type
for each entry, but implementations should note that the storage for each entry, but implementations should note that the storage
type of conceptual rows in other tables that include row type of conceptual rows in other tables that include row
pointers to an entry in this table SHOULD dictate the storage pointers to an entry in this table SHOULD dictate the storage
type of the rows in this table where the row in the other table type of the rows in this table where the row in the other table
is more persistent." is more persistent."
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
INDEX { INDEX {
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,
skipping to change at page 25, line 39 skipping to change at page 25, line 37
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 MUST 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 not be 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
since it represents a valid label value. Such implementation since it represents a valid label value. Such implementation
should be aware of the implications of sparsely populated should be aware of the implications of sparsely populated
tables. tables.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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
"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 the 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
be set to zero." be set to zero."
::= { gmplsLabelEntry 3 } ::= { gmplsLabelEntry 3 }
gmplsLabelType OBJECT-TYPE gmplsLabelType OBJECT-TYPE
SYNTAX GmplsLabelTypeTC SYNTAX GmplsLabelTypeTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the type of this label. Note that this object does "Identifies the type of this label. Note that this object does
not determine whether MPLS or GMPLS signaling is in use: a value not determine whether MPLS or GMPLS signaling is in use: a value
of gmplsMplsLabel (1) denotes that an MPLS packet label is of gmplsMplsLabel(1) denotes that an MPLS Packet Label is
present in the gmplsLabelMplsLabel object and encoded using the present in the gmplsLabelMplsLabel object and encoded using the
MplsLabel textual convention (may be a 20-bit MPLS label, a 10- MplsLabel TEXTUAL-CONVENTION (may be a 20-bit MPLS Label, a 10-
or 23-bit Frame Relay label, or an ATM label), but does not or 23-bit Frame Relay Label, or an Asynchronous Transfer Mode
describe whether this is signaled using MPLS or GMPLS. (ATM) Label), but does not describe whether this is signaled
using MPLS or GMPLS.
The value of this object helps determine which of the following The value of this object helps determine which of the following
objects are valid. This object cannot be modified if objects are valid. 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." 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
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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). Furthermore, 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
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 27, line 42 skipping to change at page 27, line 45
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2.1.1." Functional Description, RFC 3471, section 3.2.1.1."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 6 } ::= { gmplsLabelEntry 6 }
gmplsLabelFreeform OBJECT-TYPE gmplsLabelFreeform OBJECT-TYPE
SYNTAX GmplsFreeformLabelTC SYNTAX GmplsFreeformLabelTC
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of a freeform Generalized Label that does not conform "The value of a Freeform Generalized Label that does not conform
to one of the standardized label encoding or that an to one of the standardized label encodings 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 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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.
Zero indicates that this field is not significant. Only valid if Zero indicates that this field is non-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 4606, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 8 } ::= { gmplsLabelEntry 8 }
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. Zero indicates "The VC Indicator (U) of an SDH Generalized Label. Zero indicates
that this field is non-significant. that this field is non-significant. Only valid if gmplsLabelType
Only valid if gmplsLabelType is set to gmplsSdhLabel(5). is set to gmplsSdhLabel(5). This object cannot be modified if
This object cannot be modified if gmplsLabelRowStatus is 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 4606, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 9 } ::= { gmplsLabelEntry 9 }
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 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
Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This 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 4606, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 10 } ::= { gmplsLabelEntry 10 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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 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
Only valid gmplsLabelType is set to gmplsSonetLabel(4) or 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 4606, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 11 } ::= { gmplsLabelEntry 11 }
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 Generalized "The Group Branch Indicator (M) of a SONET or SDH Generalized
Label. Label. Zero indicates that this field is non-significant.
Zero indicates that this field is non-significant.
Only valid if gmplsLabelType is set to gmplsSonetLabel(4) or Only valid if 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 4606, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 12 } ::= { gmplsLabelEntry 12 }
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 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 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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
Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). gmplsLabelType is set to gmplsWavebandLabel(6). This object
This object cannot be modified if 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 }
::= { gmplsLabelEntry 14 } ::= { gmplsLabelEntry 14 }
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 valid if "The end label component of a Waveband Label. Only valid if
gmplsLabelType is set to gmplsWavebandLabel(6). This object gmplsLabelType is set to gmplsWavebandLabel(6). This object
cannot be modified if gmplsLabelRowStatus is active(1)." 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 15 } ::= { gmplsLabelEntry 15 }
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 object. The "This variable indicates the storage type for this row. The
agent MUST ensure that this object's value remains consistent agent MUST ensure that this object's value remains consistent
with the storage type of any rows in other tables that contain with the storage type of any rows in other tables that contain
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 points
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 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
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 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.
skipping to change at page 32, line 4 skipping to change at page 32, line 7
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 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only provide "Compliance requirement for implementations that only provide
read-only support for GMPLS-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 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
implementations that do not support wavelength labels." implementations that do not support Wavelength Labels."
GROUP gmplsLabelFreeformGroup GROUP gmplsLabelFreeformGroup
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."
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
OBJECT gmplsLabelType OBJECT gmplsLabelType
MIN-ACCESS read-only MIN-ACCESS read-only
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."
skipping to change at page 33, line 50 skipping to change at page 34, line 4
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-15.txt September 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."
skipping to change at page 34, line 39 skipping to change at page 34, line 41
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.
The mandatory groups have to be implemented by GMPLS LSRs The mandatory groups have to be implemented by GMPLS LSRs
claiming support for this MIB module. This MIB module is, claiming support for this MIB module. This MIB module is,
however, not mandatory for a working implementation of a GMPLS however, not mandatory for a working implementation of a GMPLS
LSR with full MIB support if the GMPLS labels in use can be LSR with full MIB support if the GMPLS Labels in use can be
represented within a 32 bit quantity." represented within a 32-bit quantity."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsLabelTableGroup gmplsLabelTableGroup
} }
::= { gmplsLabelCompliances 2 } ::= { gmplsLabelCompliances 2 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
gmplsLabelTableGroup OBJECT-GROUP gmplsLabelTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelIndexNext, gmplsLabelIndexNext,
gmplsLabelType, gmplsLabelType,
gmplsLabelStorageType, gmplsLabelStorageType,
gmplsLabelRowStatus gmplsLabelRowStatus
} }
STATUS current STATUS current
skipping to change at page 35, line 34 skipping to change at page 35, line 33
gmplsLabelFreeformGroup and/or gmplsLabelFreeformGroup and/or
gmplsLabelSonetSdhGroup." gmplsLabelSonetSdhGroup."
::= { gmplsLabelGroups 1 } ::= { gmplsLabelGroups 1 }
gmplsLabelPacketGroup OBJECT-GROUP gmplsLabelPacketGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelMplsLabel gmplsLabelMplsLabel
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement Packet (MPLS) labels." "Object needed to implement Packet (MPLS) Labels."
::= { gmplsLabelGroups 2 } ::= { gmplsLabelGroups 2 }
gmplsLabelPortWavelengthGroup OBJECT-GROUP gmplsLabelPortWavelengthGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelPortWavelength gmplsLabelPortWavelength
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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."
::= { gmplsLabelGroups 4 } ::= { gmplsLabelGroups 4 }
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
gmplsLabelSonetSdhGroup OBJECT-GROUP gmplsLabelSonetSdhGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelSonetSdhSignalIndex, gmplsLabelSonetSdhSignalIndex,
gmplsLabelSdhVc, gmplsLabelSdhVc,
gmplsLabelSdhVcBranch, gmplsLabelSdhVcBranch,
gmplsLabelSonetSdhBranch, gmplsLabelSonetSdhBranch,
gmplsLabelSonetSdhGroupBranch gmplsLabelSonetSdhGroupBranch
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement SONET and SDH labels." "Objects needed to implement SONET and SDH Labels."
::= { gmplsLabelGroups 5 } ::= { gmplsLabelGroups 5 }
gmplsLabelWavebandGroup OBJECT-GROUP gmplsLabelWavebandGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelWavebandId, gmplsLabelWavebandId,
gmplsLabelWavebandStart, gmplsLabelWavebandStart,
gmplsLabelWavebandEnd gmplsLabelWavebandEnd
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement Waveband labels." "Objects needed to implement Waveband Labels."
::= { gmplsLabelGroups 6 } ::= { gmplsLabelGroups 6 }
END END
9. Security Considerations 9. Security Considerations
It is clear that the MIB modules described in this document in It is clear that the MIB modules described in this document in
association with the MPLS-LSR-STD-MIB [RFC3813] are potentially association with MPLS-LSR-STD-MIB [RFC3813] are potentially useful
useful for monitoring of GMPLS LSRs. These MIB modules can also be for monitoring of GMPLS LSRs. These MIB modules can also be used for
used for configuration of certain objects, and anything that can be configuration of certain objects, and anything that can be configured
configured can be incorrectly configured, with potentially disastrous can be incorrectly configured, with potentially disastrous results.
results.
There are a number of management objects defined in these MIB modules There are a number of management objects defined in these MIB modules
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable o the gmplsInterfaceTable, gmplsInSegmentTable,
and gmplsLabelTable collectively contain objects to provision gmplsOutSegmentTable, and gmplsLabelTable collectively contain
GMPLS interfaces, LSPs and their associated parameters on a Label objects to provision GMPLS interfaces, LSPs, and their associated
Switching Router (LSR). Unauthorized write access to objects in parameters on a Label Switching Router (LSR). Unauthorized write
these tables, could result in disruption of traffic on the access to objects in these tables could result in disruption of
network. This is especially true if an LSP has already been traffic on the network. This is especially true if an LSP has
established. already been established.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
Some of the readable objects in these MIB modules (i.e., objects with Some of the readable objects in these MIB modules (i.e., objects with
a MAX-ACCESS other than not-accessible) may be considered sensitive a MAX-ACCESS other than not-accessible) may be considered sensitive
or vulnerable in some network environments. It is thus important to or vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable o the gmplsInterfaceTable, gmplsInSegmentTable,
and gmplsLabelTable collectively show the LSP network topology and gmplsOutSegmentTable, and gmplsLabelTable collectively show the
its capabilities. If an Administrator does not want to reveal this LSP network topology and its capabilities. If an administrator
information, then these tables should be considered does not want to reveal this information, then these tables should
sensitive/vulnerable. be considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security.
if the network itself is secure (for example by using IPsec), even Even if the network itself is secure (for example by using IPsec),
then, there is no control as to who on the secure network is allowed even then, there is no control as to who on the secure network is
to access and GET/SET (read/change/create/delete) the objects in allowed to access and GET/SET (read/change/create/delete) the objects
these MIB modules. in these MIB modules.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
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
skipping to change at page 37, line 49 skipping to change at page 37, line 49
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 the MIB tables in [RFC3813]. The authors would This document extends the MIB tables in [RFC3813]. The authors would
like to express their gratitude to all those who worked on that like to express their gratitude to all those who worked on that
earlier MIB document. 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. Lars Eggert, Tom Petch, Dan Romascanu, and compilation issues. Lars Eggert, Tom Petch, Dan Romascanu, and Bert
Bert Wijnen provided useful input in the final stages of review. Wijnen provided useful input 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.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
11. IANA Considerations 11. IANA Considerations
IANA is requested to root MIB objects in the two MIB modules IANA has rooted MIB objects in the two MIB modules contained in this
contained in this document under the mplsStdMIB subtree. document under the mplsStdMIB subtree.
Upon approval of this document, the IANA will make the following IANA has made the following assignments in the "NETWORK MANAGEMENT
assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located PARAMETERS" registry located at http://www.iana.org/assignments/
at http://www.iana.org/assignments/smi-numbers in table: smi-numbers in table:
...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166) ...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
Decimal Name References Decimal Name References
------- ----- ---------- ------- ----- ----------
TBD+2 GMPLS-LSR-STD-MIB [RFC-ccamp-gmpls-lsr-mib] 15 GMPLS-LSR-STD-MIB [RFC4803]
TBD+3 GMPLS-LABEL-STD-MIB [RFC-ccamp-gmpls-lsr-mib] 16 GMPLS-LABEL-STD-MIB [RFC4803]
In the future, GMPLS related standards track MIB modules should be In the future, GMPLS-related standards-track MIB modules should be
rooted under the mplsStdMIB (sic) subtree. IANA has been requested to rooted under the mplsStdMIB (sic) subtree. IANA has been requested
manage that namespace in the SMI Numbers registry [RFC3811]. New to manage that namespace in the SMI Numbers registry [RFC3811]. New
assignments can only be made via a Standards Action as specified in assignments can only be made via a Standards Action as specified in
[RFC2434]. [RFC2434].
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Structure of "Structure of Management Information Version 2 (SMIv2)",
Management Information Version 2 (SMIv2)", STD 58, RFC STD 58, RFC 2578, April 1999.
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Conformance Statements "Conformance Statements for SMIv2", STD 58, RFC 2580,
for SMIv2", STD 58, RFC 2580, April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC 3031, "Multiprotocol Label Switching Architecture", RFC 3031,
January 2001. January 2001.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, January 2001. Encoding", RFC 3032, January 2001.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management [RFC3289] Baker, F., Chan, K., and A. Smith, "Management
Information Base for the Differentiated Services Information Base for the Differentiated Services
Architecture", RFC 3289, May 2002. Architecture", RFC 3289, May 2002.
[RFC3443] Agarwal, P. and Akyol, B., "Time To Live (TTL) [RFC3443] Agarwal, P. and B. Akyol, "Time To Live (TTL) Processing
Processing in Multi-Protocol Label Switching (MPLS) in Multi-Protocol Label Switching (MPLS) Networks", RFC
Networks", RFC 3443, January 2003. 3443, January 2003.
[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.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions (TCs) for Multiprotocol Label Switching
Management", RFC 3811, June 2004. (MPLS) 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 Router (LSR) Management Information Base (MIB)", RFC
3813, June 2004. 3813, June 2004.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label [RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching
Switching (GMPLS) Architecture", RFC 3945, October 2004. (GMPLS) Architecture", RFC 3945, October 2004.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
[RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi- [RFC4606] Mannie, E. and D. Papadimitriou, "Generalized Multi-
Protocol Label Switching (GMPLS) Extensions for Protocol Label Switching (GMPLS) Extensions for
Synchronous Optical Network (SONET) and Synchronous Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control", RFC 3946, October Digital Hierarchy (SDH) Control", RFC 4606, August 2006.
2004.
[GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual [RFC4801] Nadeau, T., Ed. and A. Farrel, Ed., "Definitions of
Conventions for Multiprotocol Label Switching (MPLS) Textual Conventions for Multiprotocol Label Switching
Management", draft-ietf-ccamp-gmpls-tc-mib, work in (MPLS) Management", RFC 4801, February 2007.
progress.
[GMPLSTEMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol [RFC4802] Nadeau, T., Ed. and A. Farrel, Ed., "Generalized
Label Switching (GMPLS) Traffic Engineering Management Multiprotocol Label Switching (GMPLS) Traffic
Information Base", draft-ietf-ccamp-gmpls-te-mib, work Engineering Management Information Base", RFC 4802,
in progress. February 2007.
12.2. Informative References 12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3468] Andersson, L., and Swallow, G., "The Multiprotocol [RFC3468] Andersson, L. and G. Swallow, "The Multiprotocol Label
Label Switching (MPLS) Working Group decision on Switching (MPLS) Working Group decision on MPLS
MPLS signaling protocols", RFC 3468, February 2003. signaling protocols", RFC 3468, February 2003.
[RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized Multi-
Multi-Protocol Label Switching (MPLS) Signaling Protocol Label Switching (GMPLS) Signaling Constraint-
- Constraint-based Routed Label Distribution Protocol based Routed Label Distribution Protocol (CR-LDP)
(CR-LDP) Extensions", RFC 3472, January 2003. 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
RFC 3812, June 2004. 3812, June 2004.
13. Contact Information Contact Information
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
Email: tnadeau@cisco.com
EMail: tnadeau@cisco.com
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
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P. Bloomberg L.P.
731 Lexington Ave. 731 Lexington Ave.
New York, NY 10022 New York, NY 10022
Phone: +1-212-617-3682 Phone: +1-212-617-3682
Email: cheenu@bloomberg.net EMail: cheenu@bloomberg.net
Tim Hall Tim Hall
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: 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 Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
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 ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
draft-ietf-ccamp-gmpls-lsr-mib-15.txt September 2006
15. Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Acknowledgement
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an Funding for the RFC Editor function is currently provided by the
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS Internet Society.
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 202 change blocks. 
445 lines changed or deleted 376 lines changed or added

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