draft-ietf-ccamp-gmpls-lsr-mib-08.txt   draft-ietf-ccamp-gmpls-lsr-mib-09.txt 
Network Working Group Thomas D. Nadeau, Ed. Network Working Group Thomas D. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: December 2005 Adrian Farrel, Ed. Expires: April 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
June 2005 October 2005
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-08.txt draft-ietf-ccamp-gmpls-lsr-mib-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 6 skipping to change at page 2, line 6
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects to configure and/or In particular, it describes managed objects to configure and/or
monitor a Generalized Multiprotocol Label Switching (GMPLS) Label monitor a Generalized Multiprotocol Label Switching (GMPLS) Label
Switching Router (LSR). Switching Router (LSR).
Table of Contents Table of Contents
1. Introduction ..................................... 2 1. Introduction ..................................... 2
1.1. Migration Strategy ....................... ..... 2 1.1. Migration Strategy ............................. 3
2. Terminology ...................................... 3 2. Terminology ...................................... 3
3. The SNMP Management Framework .................... 3 3. The SNMP Management Framework .................... 4
4. Outline .......................................... 3 4. Outline .......................................... 5
4.1. Summary of the GMPLS LSR MIB Module ............ 4 4.1 MIB Modules ..................................... 5
4.1.1 Summary of the GMPLS LSR MIB Module ........... 4 4.1.1 Summary of the GMPLS-LSR-STD-MIB Module ....... 5
4.1.2 Summary of the GMPLS Label MIB Module ......... 5 4.1.2 Summary of the GMPLS-LABEL-STD-MIB Module ..... 5
5. Bidirectional LSPs ............................... 5 4.2. Configuring Statically Provisioned LSPs ........ 6
6. Example of LSP Setup ............................. 5 5. Bidirectional LSPs ............................... 6
7. GMPLS Label Switching Router MIB Definitions ..... 9 6. Example of LSP Setup ............................. 9
8. GMPLS Label MIB Definitions ..................... 20 7. GMPLS Label Switching Router MIB Definitions .... 11
9. Security Considerations ......................... 35 8. GMPLS Label MIB Definitions ..................... 22
10. Acknowledgments ................................ 36 9. Security Considerations ......................... 37
11. IANA Considerations ............................ 36 10. Acknowledgments ................................ 39
11.1. IANA Considerations for GMPLS-LSR-STD-MIB .... 36 11. IANA Considerations ............................ 39
11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB .. 36 11.1. IANA Considerations for GMPLS-LSR-STD-MIB .... 39
12. References ..................................... 37 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB .. 39
12.1. Normative References ......................... 37 12. References ..................................... 39
12.2. Informational References ..................... 38 12.1. Normative References ......................... 39
13. Authors' Addresses ............................. 39 12.2. Informative References ....................... 41
14. Intellectual Property Notice ................... 40 13. Contact Information ............................ 41
15. Full Copyright Statement ....................... 40 14. Intellectual Property Considerations ........... 42
15. Full Copyright Statement ....................... 43
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).
Comments should be made directly to the CCAMP mailing list at Comments should be made directly to the CCAMP mailing list at
ccamp@ops.ietf.org. ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119, document are to be interpreted as described in BCP 14, RFC 2119,
reference [RFC2119]. reference [RFC2119].
1.1. Migration Strategy 1.1. Migration Strategy
There are two MIB modules in this document. The GMPLS LSR MIB module MPLS LSRs may be modeled and managed using the MPLS-LSR-STD-MIB
extends the LSR MIB module defined for use with MPLS [RFC3813]. The module [RFC3813].
only changes made are additions for support of GMPLS or changes that
are necessary to support the increased complexity of a GMPLS system. LSRs may be migrated to be modeled and managed using the MIB modules
The GMPLS Label MIB module may be referenced using a row pointer from in this document in order to migrate the LSRs to GMPLS support, or to
objects within the LSR MIB module. take advandtage of additional MIB objects defined in these MIB
modules that are applicable to MPLS-TE.
The GMPLS LSR MIB module (GMPLS-LSR-STD-MIB) defined in this document
extends the MPLS-LSR-STD-MIB module [RFC3813] through a series of
sparse augmentations of the MIB tables. The only additions are for
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
GMPLS-LSR-STD-MIB support an implementation needs only to add support
for the additional tables and objects defined in GMPLS-LSR-STD-MIB.
The gmplsInterfaceSignalingCaps object allows an implementation to
use the objects and tables of GMPLS-LSR-STD-MIB without supporting
the GMPLS protocols.
The GMPLS Label MIB module (GMPLS-LABEL-STD-MIB) also defined in this
document allows labels to be configured and examined, and supports
more varieties of label as appropriate for GMPLS. Labels may be
referenced using a row pointer from objects within the
GMPLS-LSR-STD-MIB module. MPLS implementations (MPLS-LSR-STD-MIB) may
also reference labels held in the GMPLS-LABEL-STD-MIB module through
the various label pointer objects in the MPLS-STD-LSR-MIB module
(such as mplsInSegmentLabelPtr), and may do so without implementing
the GMPLS-LSR-STD-MIB module.
The companion document modeling and managing GMPLS based traffic The companion document modeling and managing GMPLS based traffic
engineering [GMPLSTEMIB] extends the MPLS TE MIB module [RFC3812] engineering [GMPLSTEMIB] extends the MPLS-TE-STD-MIB module [RFC3812]
with the same intentions. with the same intentions.
Textual conventions and OBJECT-IDENTIFIERS are defined in Textual conventions and OBJECT-IDENTIFIERS are defined in
[GMPLSTCMIB] which extends the set of textual conventions originally [GMPLSTCMIB] which extends the set of textual conventions originally
defined in [RFC3811]. defined in [RFC3811].
2. Terminology 2. Terminology
This document uses terminology from the document describing the MPLS This document uses terminology from the document describing the MPLS
architecture [RFC3031] and the GMPLS architecture [RFC3945]. architecture [RFC3031] and the GMPLS architecture [RFC3945].
skipping to change at page 3, line 33 skipping to change at page 4, line 17
"LSP" interchangeably where the meaning is clear from the context. "LSP" interchangeably where the meaning is clear from the context.
in-segment This is analogous to a GMPLS label on an interface. in-segment This is analogous to a GMPLS label on an interface.
out-segment This is analogous to a GMPLS label on an interface. out-segment This is analogous to a GMPLS label on an interface.
cross-connect This describes the conceptual connection between a cross-connect This describes the conceptual connection between a
set of in-segments and out-segments. Note that either set of in-segments and out-segments. Note that either
set may be empty; for example, a cross-connect may set may be empty; for example, a cross-connect may
connect only out-segments together with no in-segments connect only out-segments together with no in-segments
in the case where an LSP originates on an LSR. in the case where an LSP originates on an LSR.
The terms 'ingress' and 'head-end' (or 'head') are used in this
document to indicate the signaling source of an LSP. This is
sometimes also referred to as the 'sender'.
The terms 'egress' and 'tail-end' (or 'tail') are used in this
document to indicate the signaling destination of an LSP.
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.
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.
The term 'forward' is used in this document to indicate the direction
of data flow from the ingress toward the egress.
The term 'reverse' is used in this document to indicate the direction
of data flow from the egress toward the ingress.
3. The SNMP Management Framework 3. The SNMP Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a 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
Configuring statically provisioned GMPLS LSPs through an LSR involves 4.1 MIB Modules
the following steps:
- Configuring an interface using the MPLS LSR MIB module. There are two MIB modules defined in this document.
- Enabling GMPLS on GMPLS capable interfaces using this MIB module. The GMPLS-LSR-STD-MIB module contains tables that sparse augment
tables defined in the MPLS-LSR-STD-MIB module [RFC3813]. This MIB
module is used in conjunction with the MPLS-LSR-STD-MIB module
[RFC3813] in systems that support GMPLS.
- Configuring in and out-segments using the MPLS LSR MIB module. The GMPLS-LABEL-STD-MIB module contains objects for managing GMPLS
labels when they cannot be represented using the textual conventions
of the MPLS-TC-STD-MIB module [RFC3811], or when more detailed access
to the sub-fields of the labels is required.
- Configuring GMPLS extensions to the in-segments and out-segments 4.1.1 Summary of the GMPLS-LSR-STD-MIB Module
using this MIB module.
- Setting up the cross-connect table in the MPLS LSR MIB module to The MIB tables in the GMPLS-LSR-STD-MIB module are as follows.
associate segments and/or to indicate connection origination and
termination.
- Optionally setting up labels in the label table in this MIB module - The interface configuration table (gmplsInterfaceTable), which
if the textual convention MplsLabel is not capable of holding the sparse augments the mplsInterfaceTable [RFC3813] to enable the
required label (for example, if the label requires more than 32 GMPLS protocol on MPLS-capable interfaces.
bits to encode it), or if the operator wishes to disambiguate
GMPLS label types.
- Optionally specifying label stack actions in the MPLS LSR MIB - The in-segment (gmplsInSegmentTable) and out-segment
module. (gmplsOutSegmentTable) tables sparse augment mplsInSegmentTable and
mplsOutSegmentTable [RFC3813] to enable configuration of
GMPLS-specific parameters for LSP segments at an LSR.
- Optionally specifying segment traffic parameters in the MPLS LSR These tables are described in the subsequent sections.
MIB module.
4.1 MIB Modules 4.1.2 Summary of the GMPLS-LABEL-STD-MIB Module
There are two MIB modules defined in this document. There is one MIB table in the GMPLS-LABEL-STD-MIB module as follows.
The GMPLS LSR MIB module contains tables that extend tables defined - The gmplsLabelTable allows Generalized
in the MPLS LSR MIB module. This MIB module is used in conjunction Labels to be defined and managed in a central location.
with the MPLS LSR MIB module in systems that support GMPLS. Generalized Labels can be of variable length and have distinct
bit-by-bit interpretations depending upon how they are defined
for the specific technology in which they are used. For example,
labels used for MPLS packet switching are different in length
and content from labels used in TDM timeslot switching.
The GMPLS Label MIB module contains objects for managing GMPLS labels 4.2. Configuring Statically Provisioned LSPs
when they cannot be represented using the textual conventions of the
MPLS TC MIB module, or when more detailed access to the sub-fields of
the labels is required.
4.1.1 Summary of the GMPLS LSR MIB Module Configuring statically provisioned GMPLS LSPs through an LSR involves
the following steps:
The MIB tables in this MIB module are as follows. - Configuring an interface using the MPLS-LSR-STD-MIB module
[RFC3813].
- The interface configuration table (gmplsInterfaceTable), which - Enabling GMPLS on GMPLS capable interfaces using the
extends mplsInterfaceTable to enable the GMPLS protocol on GMPLS-LSR-STD-MIB module in this document.
MPLS-capable interfaces.
- The in-segment (gmplsInSegmentTable) and out-segment - Configuring in and out-segments using the MPLS-LSR-STD-MIB module
(gmplsOutSegmentTable) tables extend mplsInSegmentTable and [RFC3813].
mplsOutSegmentTable to configuring GMPLS-specific parameters for
LSP segments at an LSR.
These tables are described in the subsequent sections. - Configuring GMPLS extensions to the in-segments and out-segments
using the GMPLS-LSR-STD-MIB module in this document.
4.1.2 Summary of the GMPLS Label MIB Module - Setting up the cross-connect table in the MPLS-LSR-STD-MIB module
[RFC3813] to associate segments and/or to indicate connection
origination and termination.
There is one MIB table in this MIB module as follows. - Optionally setting up labels in the label table in the
GMPLS-LABEL-STD-MIB module in this document if the textual
convention MplsLabel [RFC3811] is not capable of holding the
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.
- The gmplsLabelTable allows Generalized - Optionally specifying label stack actions in the MPLS-LSR-STD-MIB
Labels to be defined and managed in a central location. module [RFC3813].
Generalized Labels can be of variable length and have distinct
bit-by-bit interpretations according to the use that is made of
them.
These tables are described in the subsequent sections. - Optionally specifying segment traffic parameters in the
MPLS-LSR-STD-MIB module [RCF3813].
5. Bidirectional LSPs 5. Bidirectional LSPs
This MIB module supports bidirectional LSPs as required for GMPLS. The GMPLS-LSR-STD-MIB module supports bidirectional LSPs as required
A single value of mplsXCIndex is shared by all of the segments for for GMPLS. A single value of mplsXCIndex is shared by all of the
the entire bidirectional LSP. This facilitates a simple reference segments for the entire bidirectional LSP. This facilitates a simple
from [RFC3812] and [GMPLSTEMIB], and makes fate-sharing more obvious. reference from [RFC3812] and [GMPLSTEMIB], and makes fate-sharing
more obvious.
It is, however, important that the direction of segments is It is, however, important that the direction of segments is
understood to avoid connecting all in-segments to all out-segments. understood to avoid connecting all in-segments to all out-segments.
This is achieved by an object in each segment that indicates the This is achieved by an object in each segment that indicates the
direction of the segment with respect to data flow. direction of the segment with respect to data flow.
A segment that is marked as 'forward' carries data from the 'head' of A segment that is marked as 'forward' carries data from the 'head' of
the LSP to the 'tail'. A segment marked as 'reverse' carries data in the LSP to the 'tail'. A segment marked as 'reverse' carries data in
the reverse direction. the reverse direction.
skipping to change at page 5, line 46 skipping to change at page 7, line 22
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 is
not meant to illustrate every nuance of the MIB, it is intended as an not meant to illustrate every nuance of the MIB modules, it is
aid to understanding some of the key concepts. It is meant to be read intended as an aid to understanding some of the key concepts. It is
after going through the MIB itself. A prerequisite is an meant to be read after going through the MIB modules themselves. A
understanding of [RFC3813]. prerequisite is an understanding of the MPLS-LSR-STD-MIB [RFC3813].
Suppose that one would like to manually create a best-effort, Suppose that one would like to manually create a best-effort,
bi-directional LSP. Assume that, in the forward direction, the LSP bi-directional LSP. Assume that, in the forward direction, the LSP
enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR
via MPLS interface B with ifIndex 13. For the reverse direction, we via MPLS interface B with ifIndex 13. For the reverse direction, we
assume the LSP enters via interface B and leaves via interface A assume the LSP enters via interface B and leaves via interface A
(i.e. the forward and reverse directions use the same bi-directional (i.e. the forward and reverse directions use the same bi-directional
interfaces). Let us also assume that we do not wish to have a label interfaces). Let us also assume that we do not wish to have a label
stack beneath the top label on the outgoing labeled packets. The stack beneath the top label on the outgoing labeled packets. The
following example illustrates which rows and corresponding objects following example illustrates which rows and corresponding objects
skipping to change at page 6, line 21 skipping to change at page 7, line 49
labels required for each of the forward and reverse direction in- and labels required for each of the forward and reverse direction in- and
out-segments. For the purpose of this example the forward 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 = gmplsFreeformGeneralizedLabel(3), gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0x123456789ABCDEF0 gmplsLabelFreeform = 0x123456789ABCDEF0
gmplsLabelRowStatus = createAndGo(4) gmplsLabelRowStatus = createAndGo(4)
} }
In gmplsLabelTable: In gmplsLabelTable:
{ {
gmplsLabelInterface = 13, gmplsLabelInterface = 13,
gmplsLabelIndex = 1, gmplsLabelIndex = 1,
gmplsLabelSubindex = 0, gmplsLabelSubindex = 0,
gmplsLabelType = gmplsFreeformGeneralizedLabel(3), gmplsLabelType = gmplsFreeformLabel(3),
gmplsLabelFreeform = 0xFEDCBA9876543210 gmplsLabelFreeform = 0xFEDCBA9876543210
gmplsLabelRowStatus = createAndGo(4) gmplsLabelRowStatus = createAndGo(4)
} }
We must next create the appropriate in-segment and out-segment We must next create the appropriate in-segment and out-segment
entries. These are done in [RFC3813] using the mplsInSegmentTable and entries. These are done in [RFC3813] using the mplsInSegmentTable and
mplsOutSegmentTable. Note that we use a row pointer to the two rows mplsOutSegmentTable. Note that we use a row pointer to the two rows
in the gmplsLableTable rather than specifying the labels explicitly in the gmplsLabelTable rather than specifying the labels explicitly
in the in- and out-segment tables. Also note that the row status for in the in- and out-segment tables. Also note that the row status for
each row is set to createAndWait(5) to allow corresponding entries in each row is set to createAndWait(5) to allow corresponding entries in
the gmplsInSegmentTable and gmplsOutSegmentTable to be created. the gmplsInSegmentTable and gmplsOutSegmentTable to be created.
For the forward direction. For the forward direction.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x00000015 mplsInSegmentIndex = 0x00000015
mplsInSegmentLabel = 0, -- incoming label in label table mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 12, -- incoming interface mplsInSegmentInterface = 12, -- incoming interface
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accsesible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentLabelPtr = gmplsLabelTable (12, 1, 0) mplsInSegmentLabelPtr = gmplsLabelTable (12, 1, 0)
mplsInSegmentRowStatus = createAndWait(5) mplsInSegmentRowStatus = createAndWait(5)
} }
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 0x00000012, mplsOutSegmentIndex = 0x00000012,
mplsOutSegmentInterface = 13, -- outgoing interface mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 0, -- outgoing label in label table mplsOutSegmentTopLabel = 0, -- outgoing label in label table
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = gmplsLabelTable (13, 1, 0) mplsOutSegmentLabelPtr = gmplsLabelTable (13, 1, 0)
mplsOutSegmentRowStatus = createAndWait(5) mplsOutSegmentRowStatus = createAndWait(5)
} }
For the reverse direction. For the reverse direction.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x00000016 mplsInSegmentIndex = 0x00000016
mplsInSegmentLabel = 0, -- incoming label in label table mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface mplsInSegmentInterface = 13, -- incoming interface
skipping to change at page 7, line 30 skipping to change at page 9, line 14
For the reverse direction. For the reverse direction.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x00000016 mplsInSegmentIndex = 0x00000016
mplsInSegmentLabel = 0, -- incoming label in label table mplsInSegmentLabel = 0, -- incoming label in label table
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 13, -- incoming interface mplsInSegmentInterface = 13, -- incoming interface
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accessible column.
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentLabelPtr = gmplsLabelTable (13, 1, 0) mplsInSegmentLabelPtr = gmplsLabelTable (13, 1, 0)
mplsInSegmentRowStatus = createAndWait(5) mplsInSegmentRowStatus = createAndWait(5)
} }
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
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 accesible 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 gmplsInSegmentTable
and gmplsOutSegmentTable. Note that the nature of the 'extends' and gmplsOutSegmentTable. Note that the nature of the 'extends'
relationship is that the entry in gmplsInSegmentTable has the same relationship is a sparse augmentation so that the entry in
index values as the entry in mplsInSegmentTable. Similarly, the entry gmplsInSegmentTable has the same index values as the entry in
in gmplsOutSegmentTable has the same index values as the entry in mplsInSegmentTable. Similarly, the entry in gmplsOutSegmentTable has
mplsOutSegmentTable. the same index values as the entry in 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 8, line 36 skipping to change at page 10, line 17
{ {
gmplsInSegmentDirection = reverse (2) gmplsInSegmentDirection = reverse (2)
} }
In gmplsOutSegmentTable(0x00000013) In gmplsOutSegmentTable(0x00000013)
{ {
gmplsOutSegmentDirection = reverse (2) gmplsOutSegmentDirection = reverse (2)
} }
Next, two cross-connect entries are created in the mplsXCTable of the Next, two cross-connect entries are created in the mplsXCTable of the
MPLS LSR MIB, thereby associating the newly created segments MPLS-LSR-STD-MIB [RFC3813], thereby associating the newly created
together. segments together.
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x01, mplsXCIndex = 0x01,
mplsXCInSegmentIndex = 0x00000015, mplsXCInSegmentIndex = 0x00000015,
mplsXCOutSegmentIndex = 0x00000012, mplsXCOutSegmentIndex = 0x00000012,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single outgoing label mplsXCLabelStackIndex = 0x00, -- only a single outgoing label
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
skipping to change at page 9, line 29 skipping to change at page 11, line 15
{ {
mplsOutSegmentRowStatus = active(1) mplsOutSegmentRowStatus = active(1)
} }
In mplsOutSegmentTable(0x00000013): In mplsOutSegmentTable(0x00000013):
{ {
mplsOutSegmentRowStatus = active(1) mplsOutSegmentRowStatus = active(1)
} }
7. GMPLS Label Switching Router MIB Definitions 7. GMPLS Label Switching Router MIB Definitions
This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3209], [RFC3443],
[RFC3472], [RFC3473], [RFC3811], [RFC3813], and [GMPLSTCMIB].
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
GmplsSegmentDirection GmplsSegmentDirection
FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB
-- RFC-Editor please resolve the reference above -- RFC-Editor please resolve the reference above using the RFC number
mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex -- and remove this note
mplsInterfaceIndex, mplsInSegmentIndex, mplsOutSegmentIndex,
mplsInterfaceGroup, mplsInSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsPerfGroup, mplsLsrNotificationGroup
FROM MPLS-LSR-STD-MIB -- RFC3813 FROM MPLS-LSR-STD-MIB -- RFC3813
ifGeneralInformationGroup, ifCounterDiscontinuityGroup
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
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
ORGANIZATION ORGANIZATION
"Common Control And Measurement Plane (CCAMP) Working Group" "IETF Common Control And Measurement Plane (CCAMP) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
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 (2005). The initial version "Copyright (C) The Internet Society (2005). This version of
of this MIB module was published in RFC XXXX. For full legal this MIB module is part of RFC XXX; see the RFC itself for
notices see the RFC itself or see: full legal notices.
http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note.
This MIB module contains managed object definitions for the This MIB module contains managed object definitions for the
Generalized Multiprotocol (GMPLS) Label Switching Router as Generalized Multiprotocol (GMPLS) Label Switching Router as
defined in: Generalized Multi-Protocol Label Switching (GMPLS) defined in: Generalized Multi-Protocol Label Switching (GMPLS)
Architecture, Mannie et al., RFC 3945, October 2004." Architecture, Mannie et al., RFC 3945, October 2004."
-- Revision history.
REVISION REVISION
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
DESCRIPTION DESCRIPTION
-- RFC-editor please fill in XXXX and see IANA section "Initial version issued as part of RFC XXX."
"Initial version issued as part of RFC XXXX." ::= { mplsStdMIB YYY }
::= { mplsStdMIB XXX } -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note.
-- Top level components of this MIB module. -- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note
-- Notifications
-- no notifications are currently defined. -- no notifications are currently defined.
gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 }
-- Tables, Scalars
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 } gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 }
-- Conformance
gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 } gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 }
-- GMPLS Interface Table.
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
mplsInterfaceTable." mplsInterfaceTable of the MPLS-LSR-STD-MIB through a
sparse augmentation relationship."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router 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 every interface capable of supporting GMPLS and which LSR for each interface that is both capable of supporting
is configured to do so. A conceptual row in this table will GMPLS and that is configured to support GMPLS. Note that
exist if and only if a corresponding entry in mplsInterfaceTable support of GMPLS is not limited to control plane signaling,
exists, and a corresponding entry in ifTable exists with but may include data-plane only function configured through
ifType = mpls(166). If the associated entry in ifTable is SNMP SET commands performed on this MIB module.
operationally disabled (thus removing the GMPLS capabilities on
the interface) or the entry in mplsInterfaceTable is deleted,
the corresponding entry in this table MUST be deleted shortly
thereafter.
The indexing is the same as that for mplsInterfaceTable. Thus, A conceptual row in this table may also be created via SNMP
the entry with index 0 represents the per-platform label space SET commands or automatically by the LSR to supplement a
and contains parameters that apply to all interfaces that conceptual row in the mplsInterfaceTable where the interface
is not capable of GMPLS but where the other objects carried
in this row provide useful additional information for an
MPLS interface.
A conceptual row in this table will exist if and only if a
corresponding entry in mplsInterfaceTable exists, and a
corresponding entry in ifTable exists with ifType = mpls(166).
If the associated entry in ifTable is operationally disabled
(thus removing the GMPLS capabilities on the interface) or the
entry in mplsInterfaceTable is deleted, the corresponding entry
in this table MUST be deleted shortly thereafter.
The indexes are the same as for mplsInterfaceTable. Thus, the
entry with index 0 represents the per-platform label space and
contains parameters that apply to all interfaces that
participate in the per-platform label space." participate in the per-platform label space."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router 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 {
unknown (0), unknown (0),
rsvpGmpls (1), rsvpGmpls (1),
crldpGmpls (2), -- note the use of CR-LDP is deprecated crldpGmpls (2), -- note the use of CR-LDP is deprecated
otherGmpls (3) otherGmpls (3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 12, line 15 skipping to change at page 14, line 8
SYNTAX BITS { SYNTAX BITS {
unknown (0), unknown (0),
rsvpGmpls (1), rsvpGmpls (1),
crldpGmpls (2), -- note the use of CR-LDP is deprecated crldpGmpls (2), -- note the use of CR-LDP is deprecated
otherGmpls (3) otherGmpls (3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the signaling capabilities on this interface. Multiple "Defines the signaling capabilities on this interface. Multiple
bits may legitimately be set at once. Setting no bits implies bits may legitimately be set at once, but if 'unknown' is set
that GMPLS signaling cannot be performed on this interface and then no other bit may be set. Setting no bits implies that GMPLS
all LSPs must be manually provisioned or that this table entry signaling cannot be performed on this interface and all LSPs
is only present to supplement an entry in the mplsInterfaceTable must be manually provisioned or that this table entry is only
by providing the information carried in other objects in this present to supplement an entry in the mplsInterfaceTable by
row." providing the information carried in other objects in this row."
REFERENCE
"1. Generalized MPLS Signaling - CR-LDP Extensions, RFC 3472.
2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473."
DEFVAL { { rsvpGmpls } } DEFVAL { { rsvpGmpls } }
::= { gmplsInterfaceEntry 1 } ::= { gmplsInterfaceEntry 1 }
gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE gmplsInterfaceRsvpHelloPeriod OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Period, in milliseconds, between sending RSVP Hello messages on "Period, in milliseconds, between sending RSVP Hello messages on
this interface. A value of 0 indicates that no Hello messages this interface. A value of 0 indicates that no Hello messages
should be sent on this interface." should be sent on this interface.
This object is only valid if gmplsInterfaceSignalingCaps has no
bits set or includes the rsvpGmpls bit."
REFERENCE REFERENCE
"Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, RFC 3209,
(Editor), RFC 3473, January 2003." section 5.
"2. Generalized MPLS Signaling - RSVP-TE Extensions, RFC 3473,
section 9.3."
DEFVAL { 3000 } DEFVAL { 3000 }
::= { gmplsInterfaceEntry 2 } ::= { gmplsInterfaceEntry 2 }
-- End of gmplsInterfaceTable
-- In-segment table.
gmplsInSegmentTable OBJECT-TYPE gmplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInSegmentEntry SYNTAX SEQUENCE OF GmplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table extends the mplsInSegmentTable to provide "This table sparse augments the mplsInSegmentTable of the
GMPLS-specific information about incoming segments to an LSR." MPLS-LSR-STD-MIB to provide GMPLS-specific information about
incoming segments to an LSR."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router 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. An entry segment represented by an entry in mplsInSegmentTable in the
can be created by a network administrator or an SNMP agent, or a MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be
GMPLS signaling protocol. created by a network administrator via SNMP SET commands, or in
response to signaling protocol events.
Note that the storage type for this entry SHOULD be inherited Note that the storage type for this entry is given by the value
from the corresponding entry in the mplsInSegmentTable given by of mplsInSegmentStorageType in the corresponding entry of the
the value of the mplsInSegmentStorageType object." mplsInSegmentTable."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router Management Information Base (MIB), RFC 3813."
INDEX { mplsInSegmentIndex } INDEX { mplsInSegmentIndex }
::= { gmplsInSegmentTable 1 } ::= { gmplsInSegmentTable 1 }
GmplsInSegmentEntry ::= SEQUENCE { GmplsInSegmentEntry ::= SEQUENCE {
gmplsInSegmentDirection GmplsSegmentDirection, gmplsInSegmentDirection GmplsSegmentDirection,
gmplsInSegmentExtraParamsPtr RowPointer gmplsInSegmentExtraParamsPtr RowPointer
} }
gmplsInSegmentDirection OBJECT-TYPE gmplsInSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
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 associated entry in the mplsInSegmentRowStatus for the corresponding entry in the
mplsInSegmentTable is active(1)." mplsInSegmentTable is active(1)."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router 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, 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. A value of zeroDotzero in this attribute referenced from here. A value of zeroDotzero in this attribute
indicates that there is no such additional information." indicates that there is no such additional information."
skipping to change at page 13, line 50 skipping to change at page 16, line 17
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. A value of zeroDotzero in this attribute referenced from here. A value of zeroDotzero in this attribute
indicates that there is no such additional information." indicates that there is no such additional information."
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { gmplsInSegmentEntry 2 } ::= { gmplsInSegmentEntry 2 }
-- End of gmplsInSegmentTable
-- Out-segment table.
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 extends the mplsOutSegmentTable to provide "This table sparse augments the mplsOutSegmentTable of the
GMPLS-specific information about outgoing segments from an LSR." MPLS-LSR-STD-MIB to provide GMPLS-specific information about
outgoing segments from an LSR."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router Management Information Base (MIB), RFC 3813."
::= { gmplsLsrObjects 3 } ::= { gmplsLsrObjects 3 }
gmplsOutSegmentEntry OBJECT-TYPE gmplsOutSegmentEntry OBJECT-TYPE
SYNTAX GmplsOutSegmentEntry SYNTAX GmplsOutSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table extends the representation of an outgoing "An entry in this table extends the representation of an outgoing
segment represented by an entry in mplsOutSegmentTable. An entry segment represented by an entry in mplsOutSegmentTable of the
can be created by a network administrator or an SNMP agent, or a MPLS-LSR-STD-MIB through a sparse augmentation. An entry can be
GMPLS signaling protocol. created by a network administrator via SNMP SET commands, or in
response to signaling protocol events.
Note that the storage type for this entry SHOULD be inherited Note that the storage type for this entry is given by the value
from the corresponding entry in the mplsOutSegmentTable given by of mplsOutSegmentStorageType in the corresponding entry of the
the value of the mplsOutSegmentStorageType object." mplsOutSegmentTable."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router Management Information Base (MIB), RFC 3813."
INDEX { mplsOutSegmentIndex } INDEX { mplsOutSegmentIndex }
::= { gmplsOutSegmentTable 1 } ::= { gmplsOutSegmentTable 1 }
GmplsOutSegmentEntry ::= SEQUENCE { GmplsOutSegmentEntry ::= SEQUENCE {
gmplsOutSegmentDirection GmplsSegmentDirection, gmplsOutSegmentDirection GmplsSegmentDirection,
gmplsOutSegmentTTLDecrement Unsigned32, gmplsOutSegmentTTLDecrement Unsigned32,
gmplsOutSegmentExtraParamsPtr RowPointer gmplsOutSegmentExtraParamsPtr RowPointer
} }
gmplsOutSegmentDirection OBJECT-TYPE gmplsOutSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 14, line 44 skipping to change at page 17, line 17
gmplsOutSegmentExtraParamsPtr RowPointer gmplsOutSegmentExtraParamsPtr RowPointer
} }
gmplsOutSegmentDirection OBJECT-TYPE gmplsOutSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
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 associated entry in the mplsOutSegmentRowStatus for the corresponding entry in the
mplsOutSegmentTable is active(1)." mplsOutSegmentTable is active(1)."
REFERENCE
"1. Multiprotocol Label Switching (MPLS) Label Switching (LSR)
Router Management Information Base (MIB), RFC 3813."
DEFVAL { forward } DEFVAL { forward }
::= { gmplsOutSegmentEntry 1 } ::= { gmplsOutSegmentEntry 1 }
gmplsOutSegmentTTLDecrement OBJECT-TYPE gmplsOutSegmentTTLDecrement OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the amount by which to decrement the TTL "This object indicates the amount by which to decrement the TTL
of any payload packets forwarded on this segment if per-hop of any payload packets forwarded on this segment if per-hop
decrementing is being done. decrementing is being done.
A value of zero indicates that no decrement should be made or A value of zero indicates that no decrement should be made or
skipping to change at page 15, line 14 skipping to change at page 17, line 35
gmplsOutSegmentTTLDecrement OBJECT-TYPE gmplsOutSegmentTTLDecrement OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the amount by which to decrement the TTL "This object indicates the amount by which to decrement the TTL
of any payload packets forwarded on this segment if per-hop of any payload packets forwarded on this segment if per-hop
decrementing is being done. decrementing is being done.
A value of zero indicates that no decrement should be made or A value of zero indicates that no decrement should be made or
that per-hop decrementing is not in force. that per-hop decrementing is not in use.
See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable See the gmplsTunnelTTLDecrement object in the gmplsTunnelTable
of [GMPLSTEMIB] for a value by which to decrement the TTL for of GMPLS-TE-STD-MIB for a value by which to decrement the TTL
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
"Time To Live (TTL) Processing in Multi-Protocol Label Switching "1. Time To Live (TTL) Processing in Multi-Protocol Label
(MPLS) Networks, Agarwal, P., Akyol, B., RFC 3443, January 2003" Switching (MPLS) Networks, RFC 3443.
2. Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base, RFC XXX."
-- RFC Editor. Please insert the correct RFC number and remove this note
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.
skipping to change at page 15, line 43 skipping to change at page 18, line 19
"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 }
-- End of gmplsOutSegmentTable
-- Module compliance.
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."
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863.
skipping to change at page 16, line 19 skipping to change at page 18, line 40
"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."
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863.
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifGeneralInformationGroup, ifGeneralInformationGroup,
ifCounterDiscontinuityGroup ifCounterDiscontinuityGroup
} }
MODULE MPLS-LSR-STD-MIB -- The MPLS LSR MIB MODULE MPLS-LSR-STD-MIB -- The MPLS LSR MIB RFC 3813
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInterfaceGroup, mplsInterfaceGroup,
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsXCGroup,
mplsPerfGroup, mplsPerfGroup,
mplsLsrNotificationGroup mplsLsrNotificationGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsInterfaceGroup, gmplsInterfaceGroup,
gmplsInSegmentGroup, gmplsInSegmentGroup,
gmplsOutSegmentGroup gmplsOutSegmentGroup
} }
-- gmplsInSegmentTable
OBJECT gmplsInSegmentDirection OBJECT gmplsInSegmentDirection
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
MIN-ACCESS read-write MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"Only forward(1) needs to be supported by implementations that "Only forward(1) needs to be supported by implementations that
only support unidirectional LSPs." only support unidirectional LSPs."
-- gmplsOutSegmentTable
OBJECT gmplsOutSegmentDirection OBJECT gmplsOutSegmentDirection
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
MIN-ACCESS read-write MIN-ACCESS read-write
DESCRIPTION DESCRIPTION
"Only forward(1) needs to be supported by implementations that "Only forward(1) needs to be supported by implementations that
only support unidirectional LSPs." only support unidirectional LSPs."
OBJECT gmplsOutSegmentTTLDecrement OBJECT gmplsOutSegmentTTLDecrement
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
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 18, line 4 skipping to change at page 20, line 21
mplsPerfGroup mplsPerfGroup
} }
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsInterfaceGroup, gmplsInterfaceGroup,
gmplsInSegmentGroup, gmplsInSegmentGroup,
gmplsOutSegmentGroup gmplsOutSegmentGroup
} }
-- gmplsInterfaceGroup
OBJECT gmplsInterfaceSignalingCaps OBJECT gmplsInterfaceSignalingCaps
SYNTAX BITS { SYNTAX BITS {
unknown (0), unknown (0),
rsvpGmpls (1), rsvpGmpls (1),
crldpGmpls (2), crldpGmpls (2),
otherGmpls (3) otherGmpls (3)
} }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsInterfaceRsvpHelloPeriod OBJECT gmplsInterfaceRsvpHelloPeriod
SYNTAX Unsigned32 SYNTAX Unsigned32
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- gmplsInSegmentTable
OBJECT gmplsInSegmentDirection OBJECT gmplsInSegmentDirection
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. Only forward(1) needs to be "Write access is not required. Only forward(1) needs to be
supported by implementations that only support unidirectional supported by implementations that only support unidirectional
LSPs." LSPs."
OBJECT gmplsInSegmentExtraParamsPtr OBJECT gmplsInSegmentExtraParamsPtr
SYNTAX RowPointer SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- gmplsOutSegmentTable
OBJECT gmplsOutSegmentDirection OBJECT gmplsOutSegmentDirection
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required. Only forward(1) needs to be "Write access is not required. Only forward(1) needs to be
supported by implementations that only support unidirectional supported by implementations that only support unidirectional
LSPs." LSPs."
OBJECT gmplsOutSegmentTTLDecrement OBJECT gmplsOutSegmentTTLDecrement
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
skipping to change at page 19, line 4 skipping to change at page 21, line 17
DESCRIPTION DESCRIPTION
"Write access is not required. Only forward(1) needs to be "Write access is not required. Only forward(1) needs to be
supported by implementations that only support unidirectional supported by implementations that only support unidirectional
LSPs." LSPs."
OBJECT gmplsOutSegmentTTLDecrement OBJECT gmplsOutSegmentTTLDecrement
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsOutSegmentExtraParamsPtr OBJECT gmplsOutSegmentExtraParamsPtr
SYNTAX RowPointer SYNTAX RowPointer
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { gmplsLsrCompliances 2 } ::= { gmplsLsrCompliances 2 }
-- Units of conformance.
gmplsInterfaceGroup OBJECT-GROUP gmplsInterfaceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsInterfaceSignalingCaps, gmplsInterfaceSignalingCaps,
gmplsInterfaceRsvpHelloPeriod gmplsInterfaceRsvpHelloPeriod
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for GMPLS interface configuration "Collection of objects needed for GMPLS interface configuration
and performance information." and performance information."
::= { gmplsLsrGroups 1 } ::= { gmplsLsrGroups 1 }
skipping to change at page 20, line 7 skipping to change at page 22, line 18
gmplsOutSegmentExtraParamsPtr gmplsOutSegmentExtraParamsPtr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement a GMPLS out-segment." "Collection of objects needed to implement a GMPLS out-segment."
::= { gmplsLsrGroups 3 } ::= { gmplsLsrGroups 3 }
END END
8. GMPLS Label MIB Definitions 8. GMPLS Label MIB Definitions
This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC3032], [RFC3289],
[RFC3471], [RFC3811], [RFC3945], [RFC3946] and [GMPLSTCMIB].
GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, Integer32
Integer32
FROM SNMPv2-SMI -- 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 MplsLabel, mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB -- RFC3811
GmplsGeneralizedLabelTypes, GmplsFreeformLabel GmplsLabelType, GmplsFreeformLabel
FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB FROM GMPLS-TC-STD-MIB -- GMPLSTCMIB
-- RFC-Editor please resolve the reference above -- RFC-Editor. Please resolve the reference above to use the RFC number
mplsStdMIB -- and remove this note
FROM MPLS-TC-STD-MIB -- RFC3811
; ;
- <span class="insert">and remove this note</span>
gmplsLabelStdMIB MODULE-IDENTITY gmplsLabelStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
ORGANIZATION ORGANIZATION
"Common Control And Measurement Plane (CCAMP) Working Group" "IETF Common Control And Measurement Plane (CCAMP) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
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 (2005). The initial version "Copyright (C) The Internet Society (2005). This version of
of this MIB module was published in RFC YYYY. For full legal this MIB module is part of RFC XXX; see the RFC itself for
notices see the RFC itself or see: full legal notices.
http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note.
This MIB module contains managed object definitions for labels This MIB module contains managed object definitions for labels
within GMPLS systems as defined in: within GMPLS systems as defined in:
Generalized Multi-Protocol Label Switching (GMPLS) Signaling Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, Berger, L. (Editor), RFC 3471, Functional Description, Berger, L. (Editor), RFC 3471,
January 2003." January 2003."
-- Revision history.
REVISION REVISION
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
DESCRIPTION DESCRIPTION
-- RFC-editor please fill in YYYY and see IANA section "Initial version issued as part of RFC XXX."
"Initial version issued as part of RFC YYYY." ::= { mplsStdMIB ZZZ }
::= { mplsStdMIB YYY } -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note.
-- Top level components of this MIB module. -- RFC Editor. Please replace ZZZ above with the OID assigned by IANA
-- and remove this note
-- Notifications
-- no notifications are currently defined. -- no notifications are currently defined.
gmplsLabelNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 }
-- Tables, Scalars
gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 } gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 }
-- Conformance
gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 } gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 }
-- GMPLS Label Table.
gmplsLabelIndexNext OBJECT-TYPE gmplsLabelIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree SYNTAX IndexIntegerNextFree
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an unused value for 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."
skipping to change at page 22, line 17 skipping to change at page 24, line 25
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 which cannot
be held within the textual convention MplsLabel. That is labels be held within the textual convention MplsLabel. That is labels
that cannot be encoded within 32 bits. It is, nevertheless also that cannot be encoded within 32 bits. It is, nevertheless also
capable of holding 32 bit labels or regular MPLS labels if 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 MIBs are referred to using value. Labels in the tables in other MIB modules may be referred
row pointer into this table. The indexing of this table provides to using row pointer into this table. The indexing of this table
for arbitrary indexing and also for concatenation of labels." provides for arbitrary indexing and also for concatenation of
labels.
For an example of label concatenation see RFC3945 section 7.1.
In essence, a GMPLS label may be composite in order to identify
a set of resources in the data plane. Practial examples are
timeslots and wavelength sets (which are not contiguous like
wavebands).
The indexing mechanism allows multiple entries in this table to
be seen as a sequence of labels that should be concatenated.
Ordering is potentially very sensitive for concatenation."
REFERENCE
"1. Generalized Multiprotocol Label Switching (GMPLS)
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
skipping to change at page 23, line 4 skipping to change at page 25, line 24
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."
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,
gmplsLabelType GmplsGeneralizedLabelTypes, gmplsLabelType GmplsLabelType,
gmplsLabelMplsLabel MplsLabel, gmplsLabelMplsLabel MplsLabel,
gmplsLabelPortWavelength Unsigned32, gmplsLabelPortWavelength Unsigned32,
gmplsLabelFreeform GmplsFreeformLabel, gmplsLabelFreeform GmplsFreeformLabel,
gmplsLabelSonetSdhSignalIndex Integer32, gmplsLabelSonetSdhSignalIndex Integer32,
gmplsLabelSdhVc Integer32, gmplsLabelSdhVc Integer32,
gmplsLabelSdhVcBranch Integer32, gmplsLabelSdhVcBranch Integer32,
gmplsLabelSonetSdhBranch Integer32, gmplsLabelSonetSdhBranch Integer32,
gmplsLabelSonetSdhGroupBranch Integer32, gmplsLabelSonetSdhGroupBranch Integer32,
gmplsLabelWavebandId Unsigned32, gmplsLabelWavebandId Unsigned32,
gmplsLabelWavebandStart Unsigned32, gmplsLabelWavebandStart Unsigned32,
gmplsLabelWavebandEnd Unsigned32, gmplsLabelWavebandEnd Unsigned32,
gmplsLabelRowStatus RowStatus, gmplsLabelStorageType StorageType,
gmplsLabelStorageType StorageType 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 the label has or "The interface on which this label is used. If this object is set
could have applicability across the whole system, this object to zero, the label has or could have applicability across the
SHOULD be set to zero." whole system and is not limited to a single interface."
::= { gmplsLabelEntry 1 } ::= { gmplsLabelEntry 1 }
gmplsLabelIndex OBJECT-TYPE gmplsLabelIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary index into the table to identify a label. "An arbitrary index into the table to identify a label.
Note that implementations that are representing 32 bit labels Note that implementations that are representing 32 bit labels
within this table MAY choose to align this index with the value within this table MAY choose to align this index with the value
of the label, but should be aware of the implications of of the label and this may result in the use of the value zero.
Such implementation should be aware of the implications of
sparsely populated tables. sparsely populated tables.
A management application may read the gmplsLabelIndexNext A management application may read the gmplsLabelIndexNext
object to find a suitable value for this object." object to find a suitable value for this object."
::= { gmplsLabelEntry 2 } ::= { gmplsLabelEntry 2 }
gmplsLabelSubindex OBJECT-TYPE gmplsLabelSubindex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"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.
skipping to change at page 24, line 21 skipping to change at page 27, line 4
a single GMPLS label to be defined as a concatenation of labels. a single GMPLS label to be defined as a concatenation of labels.
This is particularly useful in TDM. This is particularly useful in TDM.
The ordering of sub-labels is strict with the sub-label with The ordering of sub-labels is strict with the sub-label with
lowest gmplsLabelSubindex appearing first. Note that all lowest gmplsLabelSubindex appearing first. Note that all
sub-labels of a single GMPLS label must share the same sub-labels of a single GMPLS label must share the same
gmplsLabelInterface and gmplsLabelIndex values. For labels that gmplsLabelInterface and gmplsLabelIndex values. For labels that
are not composed of concatenated sub-labels, this value SHOULD are not composed of concatenated sub-labels, this value SHOULD
be set to zero." be set to zero."
::= { gmplsLabelEntry 3 } ::= { gmplsLabelEntry 3 }
gmplsLabelType OBJECT-TYPE gmplsLabelType OBJECT-TYPE
SYNTAX GmplsGeneralizedLabelTypes SYNTAX GmplsLabelType
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 a 23 bit MPLS packet label is of gmplsMplsLabel (1) denotes that an MPLS packet label is
present, but does not describe whether this is signaled using present in the gmplsLabelMplsLabel object and encoded using the
MPLS or GMPLS. 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
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
"Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Signaling Functional Description, Berger, L. (Editor), Functional Description, RFC 3471, section 3."
RFC 3471, January 2003."
::= { gmplsLabelEntry 4 } ::= { gmplsLabelEntry 4 }
gmplsLabelMplsLabel OBJECT-TYPE gmplsLabelMplsLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of an MPLS label (that is a packet label) if this "The value of an MPLS label (that is a packet label) if this
table is used to store it. This may be used in MPLS systems even table is used to store it. This may be used in MPLS systems even
though the label values can be adequately stored in the MPLS MIB though the label values can be adequately stored in the MPLS MIB
modules. Further, in mixed MPLS and GMPLS systems it may be modules (MPLS-LSR-STD-MIB and MPLS-TE-STD-MIB). Further, in
advantageous to store all labels in a single label table. mixed MPLS and GMPLS systems it may be advantageous to store all
Lastly, in GMPLS systems where packet labels are used (that is labels in a single label table. Lastly, in GMPLS systems where
in systems that use GMPLS signaling and GMPLS labels for packet packet labels are used (that is in systems that use GMPLS
switching) it may be desirable to use this table. signaling and GMPLS labels for packet switching) it may be
desirable to use this table.
This object is only valid if gmplsLabelType is set This object is only valid if gmplsLabelType is set
to gmplsMplsLabel (1). 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
"MPLS Label Stack Encoding, Rosen, E. et al, RFC 3032, "1. MPLS Label Stack Encoding, RFC 3032."
January 2001."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 6 } ::= { gmplsLabelEntry 5 }
gmplsLabelPortWavelength OBJECT-TYPE gmplsLabelPortWavelength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of a Port or Wavelength Label when carried as a "The value of a Port or Wavelength Label when carried as a
Generalized Label. Only valid if gmplsLabelType is set to Generalized Label. Only valid if gmplsLabelType is set to
gmplsPortWavelengthLabel(2). This object cannot be modified if gmplsPortWavelengthLabel(2). This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Signaling Functional Description, Berger, L. (Editor), Functional Description, RFC 3471, section 3.2.1.1."
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 7 } ::= { gmplsLabelEntry 6 }
gmplsLabelFreeform OBJECT-TYPE gmplsLabelFreeform OBJECT-TYPE
SYNTAX GmplsFreeformLabel SYNTAX GmplsFreeformLabel
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of a freeform Generalized Label that does 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 encoding or that an
implementation chooses to represent as an octet string without implementation chooses to represent as an octet string without
further decoding. Only valid if gmplsLabelType is set to further decoding. Only valid if gmplsLabelType is set to
gmplsFreeformGeneralizedLabel(3). This object cannot be modified gmplsFreeformLabel(3). This object cannot be modified
if gmplsLabelRowStatus is active(1)." if gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 8 } REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2."
DEFVAL { '' }
::= { gmplsLabelEntry 7 }
gmplsLabelSonetSdhSignalIndex OBJECT-TYPE gmplsLabelSonetSdhSignalIndex OBJECT-TYPE
SYNTAX Integer32 (0..4095) SYNTAX Integer32 (0..4095)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Signal Index value (S) of a SONET or SDH Generalized Label. "The Signal Index value (S) of a SONET or SDH Generalized Label.
Zero indicates that this field is not significant. Only valid if Zero indicates that this field is not significant. Only valid if
gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5). gmplsLabelType is set to gmplsSonetLabel(4) or gmplsSdhLabel(5).
This object cannot be modified if gmplsLabelRowStatus is This object cannot be modified if gmplsLabelRowStatus is
active(1)." active(1)."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D. for Synchronous Optical Network (SONET) and Synchronous
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh, work in progress." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 9 } ::= { 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 is set to gmplsSdhLabel(5). Only valid if gmplsLabelType is set to gmplsSdhLabel(5).
This object cannot be modified if gmplsLabelRowStatus is This object cannot be modified if gmplsLabelRowStatus is
active(1)." active(1)."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D. for Synchronous Optical Network (SONET) and Synchronous
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh, work in progress." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 10 } ::= { 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 gmplsLabelType is set to gmplsSdhLabel(5). This Only valid if gmplsLabelType is set to gmplsSdhLabel(5). This
object cannot be modified if gmplsLabelRowStatus is active(1)." object cannot be modified if gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D. for Synchronous Optical Network (SONET) and Synchronous
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh, work in progress." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 11 } ::= { gmplsLabelEntry 10 }
gmplsLabelSonetSdhBranch OBJECT-TYPE gmplsLabelSonetSdhBranch OBJECT-TYPE
SYNTAX Integer32 (0..15) SYNTAX Integer32 (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Branch Indicator (L) of a SONET or SDH Generalized Label. "The Branch Indicator (L) of a SONET or SDH Generalized Label.
Zero indicates that this field is non-significant. Zero indicates that this field is non-significant.
Only valid gmplsLabelType is set to gmplsSonetLabel(4) or Only valid gmplsLabelType is set to gmplsSonetLabel(4) or
gmplsSdhLabel(5). This object cannot be modified if gmplsSdhLabel(5). This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D. for Synchronous Optical Network (SONET) and Synchronous
(Editors), draft-ietf-ccamp-gmpls-sonet-sdh, work in progress." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 12 } ::= { 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
"Generalized Multi-Protocol Label Switching Extensions "1. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for SONET and SDH Control, Mannie, E., Papadimitriou, D. for Synchronous Optical Network (SONET) and Synchronous
(Editors), draft-ietf-ccamp-gmpls-sonet, work in progress." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 13 } ::= { 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
"Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Signaling Functional Description, Berger, L. (Editor), Functional Description, RFC 3471, section 3.3."
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 14 } ::= { gmplsLabelEntry 13 }
gmplsLabelWavebandStart OBJECT-TYPE gmplsLabelWavebandStart OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The starting label component of a waveband label. "The starting label component of a waveband label.
Only valid if gmplsLabelType is set to gmplsWavebandLabel(6). Only valid if gmplsLabelType is set to gmplsWavebandLabel(6).
This object cannot be modified if This object cannot be modified if
gmplsLabelRowStatus is active(1)." gmplsLabelRowStatus is active(1)."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Signaling Functional Description, Berger, L. (Editor), Functional Description, RFC 3471, section 3.3."
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 15 } ::= { 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
"Generalized Multi-Protocol Label Switching (GMPLS) "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Signaling Functional Description, Berger, L. (Editor), Functional Description, RFC 3471, section 3.3."
RFC 3471, January 2003."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsLabelEntry 16 } ::= { gmplsLabelEntry 15 }
gmplsLabelRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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)
state, no objects in this row can be modified except the
gmplsLabelRowStatus and gmplsLabelStorageType."
::= { gmplsLabelEntry 17 }
gmplsLabelStorageType OBJECT-TYPE gmplsLabelStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this object. The "This variable indicates the storage type for this object. 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 point
to it. to it.
Conceptual rows having the value 'permanent' need not Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row." allow write-access to any columnar objects in the row."
REFERENCE REFERENCE
"See RFC2579." "1. Textual Conventions for SMIv2, STD 58, RFC 2579, section 2."
DEFVAL { volatile } DEFVAL { volatile }
::= { gmplsLabelEntry 18 } ::= { gmplsLabelEntry 16 }
-- End of GMPLS Label Table gmplsLabelRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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)
state, no objects in this row can be modified except the
gmplsLabelRowStatus and gmplsLabelStorageType.
-- Module compliance. The gmplsLabelType object does not have a default and must be
set before a row can become active. The corresponding label
objects (dependent on the value of gmplsLabelType) should also
be set unless they happen to need to use the specified default
values as follows:
gmplsLabelType setting objects to be set
--------------------------------------------------------------
gmplsMplsLabel(1) gmplsLabelMplsLabel
gmplsPortWavelengthLabel(2) gmplsLabelPortWavelength
gmplsFreeformLabel(3) gmplsLabelFreeform
gmplsSonetLabel(4) gmplsLabelSonetSdhSignalIndex
gmplsLabelSdhVc
gmplsLabelSdhVcBranch
gmplsLabelSonetSdhBranch
gmplsLabelSonetSdhGroupBranch
gmplsSdhLabel(5) gmplsLabelSonetSdhSignalIndex
gmplsLabelSdhVc
gmplsLabelSdhVcBranch
gmplsLabelSonetSdhBranch
gmplsLabelSonetSdhGroupBranch
gmplsWavebandLabel(6) gmplsLabelWavebandId
gmplsLabelWavebandStart
gmplsLabelWavebandEnd"
::= { gmplsLabelEntry 17 }
gmplsLabelGroups gmplsLabelGroups
OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 }
gmplsLabelCompliances gmplsLabelCompliances
OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 }
gmplsLabelModuleROCompliance MODULE-COMPLIANCE gmplsLabelModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only "Compliance requirement for implementations that only provide
provide read-only support for GMPLS-LABEL-STD-MIB. Such read-only support for GMPLS-LABEL-STD-MIB. Such devices can then
devices can then be monitored but cannot be configured be monitored but cannot be configured using this MIB module."
using this MIB modules."
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
} }
-- Units of conformance.
GROUP gmplsLabelTableGroup GROUP gmplsLabelTableGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which support the "This group is mandatory for devices which support the
gmplsLabelTable." gmplsLabelTable."
GROUP gmplsLabelPacketGroup GROUP gmplsLabelPacketGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for implementations that "This group extends gmplsLabelTableGroup for implementations that
support packet labels." support packet labels."
skipping to change at page 30, line 36 skipping to change at page 33, line 34
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." 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." support Waveband labels."
-- gmplsLabelTable
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 31, line 49 skipping to change at page 34, line 44
OBJECT gmplsLabelWavebandStart OBJECT gmplsLabelWavebandStart
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelWavebandEnd OBJECT gmplsLabelWavebandEnd
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsLabelRowStatus OBJECT gmplsLabelRowStatus
SYNTAX RowStatus { SYNTAX RowStatus {
active(1), active(1),
notInService(2) notInService(2)
} }
WRITE-SYNTAX RowStatus { WRITE-SYNTAX RowStatus {
active(1), active(1),
notInService(2), notInService(2),
createAndGo(4), createAndGo(4),
destroy(6) destroy(6)
} }
DESCRIPTION DESCRIPTION
"Support for notInService, createAndWait and notReady is not "Support for notInService, createAndWait and notReady is not
required." required."
skipping to change at page 32, line 14 skipping to change at page 35, line 20
WRITE-SYNTAX RowStatus { WRITE-SYNTAX RowStatus {
active(1), active(1),
notInService(2), notInService(2),
createAndGo(4), createAndGo(4),
destroy(6) destroy(6)
} }
DESCRIPTION DESCRIPTION
"Support for notInService, createAndWait and notReady is not "Support for notInService, createAndWait and notReady is not
required." required."
OBJECT gmplsLabelStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { gmplsLabelCompliances 1 } ::= { gmplsLabelCompliances 1 }
gmplsLabelModuleFullCompliance MODULE-COMPLIANCE gmplsLabelModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the complete GMPLS "Compliance statement for agents that support the complete
Label MIB module." GMPLS-LABEL-STD-MIB module."
MODULE -- this module MODULE -- this 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.
MANDATORY-GROUPS { MANDATORY-GROUPS {
skipping to change at page 32, line 47 skipping to change at page 35, line 48
gmplsLabelPacketGroup, gmplsLabelPacketGroup,
gmplsLabelPortWavelengthGroup, gmplsLabelPortWavelengthGroup,
gmplsLabelFreeformGroup, gmplsLabelFreeformGroup,
gmplsLabelSonetSdhGroup, gmplsLabelSonetSdhGroup,
gmplsLabelWavebandGroup gmplsLabelWavebandGroup
} }
OBJECT gmplsLabelRowStatus OBJECT gmplsLabelRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) createAndGo(4), destroy(6) }
}
DESCRIPTION DESCRIPTION
"Support for notInService, createAndWait and notReady is not "Support for notInService, createAndWait and notReady is not
required." required."
::= { gmplsLabelCompliances 2 } ::= { gmplsLabelCompliances 2 }
-- Units of conformance.
gmplsLabelTableGroup OBJECT-GROUP gmplsLabelTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelIndexNext, gmplsLabelIndexNext,
gmplsLabelType, gmplsLabelType,
gmplsLabelRowStatus, gmplsLabelStorageType,
gmplsLabelStorageType gmplsLabelRowStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of objects to implement label "Necessary, but not sufficient, set of objects to implement label
table support. In addition, depending on the type of labels table support. In addition, depending on the type of labels
supported (for example, wavelength labels), the following other supported (for example, wavelength labels), the following other
groups defined below are mandatory: groups defined below are mandatory:
gmplsLabelPacketGroup and/or gmplsLabelPacketGroup and/or
gmplsLabelPortWavelengthGroup and/or gmplsLabelPortWavelengthGroup and/or
skipping to change at page 35, line 8 skipping to change at page 37, line 32
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement Waveband labels." "Object 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 are potentially useful for association with the MPLS-LSR-STD-MIB [RFC3813] are potentially
monitoring of GMPLS LSRs. These MIB modules can also be used for useful for monitoring of GMPLS LSRs. These MIB modules can also be
configuration of certain objects, and anything that can be configured used for configuration of certain objects, and anything that can be
can be incorrectly configured, with potentially disastrous results. configured can be incorrectly configured, with potentially disastrous
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, gmplsOutSegmentTable
and gmplsLabelTable collectively contain objects to provision and gmplsLabelTable collectively contain objects to provision
GMPLS interfaces, LSPs and their associated parameters on a Label GMPLS interfaces, LSPs and their associated parameters on a Label
Switching Router (LSR). Unauthorized write access to objects in Switching Router (LSR). Unauthorized write access to objects in
these tables, could result in disruption of traffic on the these tables, could result in disruption of traffic on the
network. This is especially true if an LSP has already been network. This is especially true if an LSP has already been
established. The use of stronger mechanisms such as SNMPv3 established.
security should be considered where possible. Specifically, SNMPv3
VACM and USM MUST be used with any SNMPv3 agent which implements
these MIB modules.
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, gmplsOutSegmentTable
and gmplsLabelTable collectively show the LSP network topology and and gmplsLabelTable collectively show the LSP network topology and
its capabilities. If an Administrator does not want to reveal this its capabilities. If an Administrator does not want to reveal this
information, then these tables should be considered information, then these tables should be considered
sensitive/vulnerable. sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security. Even
if the network itself is secure "for example by using IPSec", even if the network itself is secure (for example by using IPSec), even
then, there is no control as to who on the secure network is allowed then, there is no control as to who on the secure network is allowed
to access and GET/SET "read/change/create/delete" the objects in to access and GET/SET (read/change/create/delete) the objects in
these MIB modules. It is RECOMMENDED that implementers consider the these MIB modules.
security features as provided by the SNMPv3 framework "see [RFC3410],
section 8", including full support for the SNMPv3 cryptographic It is RECOMMENDED that implementers consider the security features as
mechanisms "for authentication and privacy". provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
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
instance of this MIB module, is properly configured to give access to instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET (change/create/delete) them.
10. Acknowledgments 10. Acknowledgments
This draft is the work of the five authors listed in the Authors' This document is a product of the CCAMP Working Group.
Addresses section.
This document extends [RFC3813]. The authors would like to express This document extends [RFC3813]. The authors would like to express
their gratitude to all those who worked on that earlier MIB document. their gratitude to all those who worked on that earlier MIB document.
The authors would like to express their thanks to Dan Joyle for his The authors would like to express their thanks to Dan Joyle for his
careful review and comments on early versions of the Label Table. careful review and comments on early versions of the Label Table.
Special thanks to Joan Cucchiara and Len Nieman for their help with Special thanks to Joan Cucchiara and Len Nieman for their help with
compilation issues. Tom Petch provided useful input in the final compilation issues. Tom Petch and Bert Wijnen provided useful input
stages of review. in the final stages of review.
11. IANA Considerations Joan Cucchiara provided a helpful and very thorough MIB Doctor
review.
MPLS related standards track MIB modules are rooted under the 11. IANA Considerations
mplsStdMIB subtree.
One of the MIB modules contained in this document extends tables -- (Note to RFC-Editor:)
contained in MPLS MIB modules. -- We request that you assign contiguous RFC numbers to the three GMPLS
-- MIB documents.
-- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to
-- draft-ietf-ccamp-gmpls-lsr-mib, and the third to
-- draft-ietf-ccamp-gmpls-te-mib.
-- (Please remove this note prior to publication.)
The two MIB modules contained in this document, like that in IANA is requested to root MIB objects in the two MIB modules
GMPLS-TC-STD-MIB [GMPLSTCMIB], should be placed in the mplsStdMIB contained in this document under the mplsStdMIB subtree.
subtree.
New assignments in the mplsStdMIB subtree can only be made via a In the future, GMPLS related standards track MIB modules should be
Standards Action as specified in [RFC2434]. rooted under the mplsStdMIB (sic) subtree. IANA has been requested to
manage that namespace in the SMI Numbers registry [RFC3811]. New
assignments can only be made via a Standards Action as specified in
[RFC2434].
11.1. IANA Considerations for GMPLS-LSR-STD-MIB 11.1. IANA Considerations for GMPLS-LSR-STD-MIB
The IANA is requested to assign { mplsStdMIB XXX } to the The IANA is requested to assign { mplsStdMIB YYY } to the
GMPLS-LSR-STD-MIB module specified in this document. GMPLS-LSR-STD-MIB module specified in this document, and to record
the assignment in the SMI Numbers registry.
-- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note
11.2. IANA Considerations for GMPLS-LABEL-STD-MIB 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB
The IANA is requested to assign { mplsStdMIB YYY } to the The IANA is requested to assign { mplsStdMIB ZZZ } to the
GMPLS-LABEL-STD-MIB module specified in this document. GMPLS-LABEL-STD-MIB module specified in this document, and to record
the assignment in the SMI Numbers registry.
-- RFC Editor. Please replace ZZZ above with the OID assigned by IANA
-- and remove this note
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Case, J., Rose, M., and S. Waldbusser, "Structure J., Rose, M., and S. Waldbusser, "Structure of
of Management Information Version 2 (SMIv2)", STD Management Information Version 2 (SMIv2)", STD 58, RFC
58, RFC 2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Case, J., Rose, M., and S. Waldbusser, "Textual J., Rose, M., and S. Waldbusser, "Textual Conventions
Conventions for SMIv2", STD 58, RFC 2579, April for SMIv2", STD 58, RFC 2579, April 1999.
1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Case, J., Rose, M., and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Conformance Statements
Statements for SMIv2", STD 58, RFC 2580, April for SMIv2", STD 58, RFC 2580, April 1999.
1999.
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Group MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC 3031,
January 2001.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, January 2001.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
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 Akyol, B., "Time To Live (TTL)
Processing in Multi-Protocol Label Switching Processing in Multi-Protocol Label Switching (MPLS)
(MPLS) Networks", RFC 3443, January 2003. Networks", RFC 3443, January 2003.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching
(MPLS) Management", RFC 3811, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label
Switching (LSR) Router Management Information Base
(MIB)", RFC 3813, June 2004.
[RFC3945] Mannie, E. (Editor), "Generalized Multiprotocol
Label Switching (GMPLS) Architecture", RFC 3945,
October 2004.
[GMPLSTCMIB] Nadeau, T., Farrel, A., (Editors) "Definitions of [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
Textual Conventions for Multiprotocol Label (GMPLS) Signaling Functional Description", RFC 3471,
Switching (MPLS) Management", January 2003.
draft-ietf-ccamp-gmpls-tc-mib, work in progress.
[GMPLSTEMIB] Nadeau, T., Farrel, A. (Editors) "Generalized [RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
Multiprotocol Label Switching (GMPLS) Traffic (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering Management Information Base", Engineering (RSVP-TE) Extensions", RFC 3473, January
draft-ietf-ccamp-gmpls-te-mib, work in progress. 2003.
12.2. Informational References [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching (MPLS)
Management", RFC 3811, June 2004.
[RFC2026] S. Bradner, "The Internet Standards Process -- [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
Revision 3", RFC 2026, October 1996. "Multiprotocol Label Switching (MPLS) Label Switching
(LSR) Router Management Information Base (MIB)", RFC
3813, June 2004.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Writing an IANA Considerations Section in RFCs", Switching (GMPLS) Architecture", RFC 3945, October 2004.
BCP: 26, RFC 2434, October 1998.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi-
"Multiprotocol Label Switching Architecture", RFC Protocol Label Switching (GMPLS) Extensions for
3031, January 2001. Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control", RFC 3946, October
2004.
[RFC3032] Rosen, E. et al, "MPLS Label Stack Encoding", [GMPLSTCMIB] Nadeau, T. and A. Farrel, "Definitions of Textual
RFC 3032, January 2001. Conventions for Multiprotocol Label Switching (MPLS)
Management", draft-ietf-ccamp-gmpls-tc-mib, work in
progress.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., [GMPLSTEMIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol
Srinivasan, V., and G. Swallow, "RSVP-TE: Label Switching (GMPLS) Traffic Engineering Management
Extensions to RSVP for LSP Tunnels", RFC 3209, Information Base", draft-ietf-ccamp-gmpls-te-mib, work
December 2001. in progress.
[RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 12.2. Informative References
Ashwood-Smith, P., Hellstrand, F., Sundell, K.,
Callon, R., Dantu, R., Wu, L., Doolan, P., Worster,
T., Feldman, N., Fredette, A., Girish, M., Gray,
E., Halpern, J., Heinanen, J., Kilty, T., Malis,
A., and P. Vaananen, "Constraint-Based LSP Setup
using LDP", RFC 3212, December 2001."
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3472] Ashwood-Smith, P. and L. Berger, "Generalized
Architecture for Describing Simple Network Multi-Protocol Label Switching (MPLS) Signaling
Management Protocol (SNMP) Management Frameworks", - Constraint-based Routed Label Distribution Protocol
RFC 3411, December 2002. (CR-LDP) Extensions", RFC 3472, January 2003.
[RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP
Applications", RFC 3413, December 2002.
[RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional
Description", RFC 3471, January 2003.
[RFC3472] Ashwood-Smith, P., Berger, L. (Editors),
"Generalized MPLS Signaling - CR-LDP Extensions",
RFC 3472, January 2003.
[RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
RSVP-TE Extensions", RFC 3473 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 Engineering (TE) Management Information Base (MIB)",
(MIB)", RFC 3812, June 2004. RFC 3812, June 2004.
[GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors),
"Generalized Multi-Protocol Label Switching
Extensions for SONET and SDH Control",
draft-ietf-ccamp-gmpls-sonet-sdh, work in progress.
13. Authors' Addresses 13. Contact Information
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 1414 Massachusetts Ave.
Chelmsford, MA 01824 Boxborough, MA 01719
Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel
Old Dog Consulting
Phone: +44-(0)-1978-860944
Email: adrian@olddog.co.uk
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P. Bloomberg L.P.
731 Lexington Ave. 731 Lexington Ave.
New York, NY 10022 New York, NY 10022
Phone: +1-212-617-3682 Phone: +1-212-617-3682
Email: cheenu@bloomberg.net Email: cheenu@bloomberg.net
Adrian Farrel
Old Dog Consulting
Phone: +44-(0)-1978-860944
Email: adrian@olddog.co.uk
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
 End of changes. 208 change blocks. 
459 lines changed or deleted 561 lines changed or added

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