draft-ietf-ccamp-gmpls-lsr-mib-00.txt   draft-ietf-ccamp-gmpls-lsr-mib-01.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Expires: December 2002 Expires: February 2004
Cheenu Srinivasan Cheenu Srinivasan
Parama Networks, Inc. Bloomberg L.P.
Adrian Farrel Adrian Farrel
Movaz Networks, Inc. Old Dog Consulting
Tim Hall Tim Hall
Edward Harrison Ed Harrison
Data Connection Ltd. Data Connection Ltd.
June 2002 August 2003
Generalized Multiprotocol Label Switching (GMPLS) Generalized Multiprotocol Label Switching (GMPLS)
Label Switch Router Management Information Base Label Switching Router (LSR) Management Information Base
draft-ietf-ccamp-gmpls-lsr-mib-00.txt draft-ietf-ccamp-gmpls-lsr-mib-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full This document is an Internet-Draft and is in full conformance with
conformance with all provisions of Section 10 of RFC 2026 all provisions of Section 10 of RFC 2026.
[RFC2026].
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet Engineering
Engineering Task Force (IETF), its areas, and its working Task Force (IETF), its areas, and its working groups. Note that
groups. Note that other groups may also distribute other groups may also distribute working documents as Internet-
working documents as Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum Internet-Drafts are draft documents valid for a maximum of six
of six months and may be updated, replaced, or obsoleted months and may be updated, replaced, or obsoleted by other documents
by other documents at any time. It is inappropriate to at any time. It is inappropriate to use Internet-Drafts as
use Internet- Drafts as reference material or to cite reference material or to cite them other than as "work in progress."
them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be
accessed at http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information This memo defines a portion of the Management Information Base (MIB)
Base (MIB) for use with network management protocols in for use with network management protocols in the Internet community.
the Internet community. In particular, it describes In particular, it describes managed objects to configure and/or
managed objects for Generalized Multiprotocol Label monitor a Generalized Multiprotocol Label Switching (GMPLS) Label
Switching (GMPLS) Label Switched Routers (LSRs). Switching Router (LSRs).
Table of Contents Table of Contents
1. Changes and Pending Work 2 1. Introduction 2
1.1. Changes Since the Last Version 2 1.1. Migration Strategy 2
1.2. Pending Work 3 2. Terminology 3
2. Introduction 3 3. The SNMP Management Framework 3
2.1. Migration Strategy 3 4. Outline 3
3. The SNMP Management Framework 4 4.1. Summary of the GMPLS LSR MIB Module 4
4. Terminology 5 5. Bidirectional LSPs 4
5. Feature List 5 6. Example of LSP Setup 5
6. Summary of LSR MIB 5 7. GMPLS Label Switching Router MIB Definitions 6
7. Bidirectional LSPs 5 8. GMPLS Label MIB Definitions 14
8. Example of LSP Setup 6 9. Security Considerations 25
9. GMPLS Label Switching Router MIB Definitions 7 10. Acknowledgments 26
10. GMPLS Label MIB Definitions 13 11. IANA Considerations 27
11. Security Considerations 22 11.1. IANA Considerations for GMPLS-LSR-STD-MIB 27
12. Acknowledgments 23 11.2. IANA Considerations FOR GMPLS-LABEL-STD-MIB 27
13. References 23 12. References 27
13.1. Normative References 23 12.1. Normative References 27
13.2. Informational References 25 12.2. Informational References 28
14. Authors' Addresses 27 13. Authors' Addresses 29
15. Full Copyright Statement 27 14. Full Copyright Statement 30
15. Intellectual Property Notice 30
1. Changes and Pending Work 16. Changes and Pending Work 31
16.1. Pending Work 31
This section must be removed before the draft progresses
to RFC.
1.1. Changes Since the Last Version
This is the first version of this draft.
1.2. Pending Work
The following work items have been identified for this
draft. They will be addressed in a future version.
- Expand conformance statements to give one for
monitoring only, and one for monitoring and control.
- Bring references up to date, include all drafts
referenced from this document, and exclude those that
are not referenced.
-- Provide support for monitoring tunnel resources in
GMPLS systems. For example, SONET/SDH or G.709. This
might be done through an arbitrary RowPointer to an
external MIB.
- Extend mplsTrafficParamsTable from the MPLS-LSR-MIB to
support GMPLS traffic parameters for signaled and
static LSPs.
- Extendthe performance tables from the MPLS-LSR-MIB for
technology-specific GMPLS LSPs.
2. Introduction 1. Introduction
This memo defines a portion of the Management Information This memo defines a portion of the Management Information Base (MIB)
Base (MIB) for use with network management protocols in for use with network management protocols in the Internet community.
the Internet community. In particular, it describes In particular, it describes managed objects for modeling a
managed objects for Generalized Multiprotocol Label Generalized Multiprotocol Label Switching (GMPLS) [GMPLSArch] Label
Switching (GMPLS) [GMPLSArch] Label Switching Routers Switching Router (LSR).
(LSRs).
Comments should be made directly to the CCAMP mailing Comments should be made directly to the CCAMP mailing list at
list at ccamp@ops.ietf.org. ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
"MAY", and "OPTIONAL" in this document are to be document are to be interpreted as described in RFC 2119, reference
interpreted as described in RFC 2119, reference
[RFC2119]. [RFC2119].
2.1. Migration Strategy 1.1. Migration Strategy
This MIB extends the Label Switching Router MIB defined This MIB module extends the Label Switching Router MIB module defined
for use with MPLS [LSRMIB]. The only changes made are for use with MPLS [LSRMIB]. The only changes made are additions for
additions for support of GMPLS or changes that are support of GMPLS or changes that are necessary to support the
necessary to support the increased complexity of a GMPLS increased complexity of a GMPLS system.
system.
The companion document modeling and managing GMPLS based The companion document modeling and managing GMPLS based traffic
traffic engineering [GMPLSTEMIB] extends the MPLS TE MIB engineering [GMPLSTEMIB] extends the MPLS TE MIB module [TEMIB] with
[TEMIB] with the same intentions. 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 [GMPLSTCMIB] which extends the set of textual conventions originally
originally defined in [TCMIB]. defined in [TCMIB].
3. The SNMP Management Framework 2. Terminology
The SNMP Management Framework presently consists of five This document uses terminology from the document describing the MPLS
major components: architecture [RFC3031] and the GMPLS architecture [GMPLSArch].
- An overall architecture, described in RFC 2571 A label switched path (LSP) is modeled as a connection consisting of
[RFC2571]. one or more incoming segments (in-segments) and/or one or more
outgoing segments (out-segments) at an LSR. The association or
interconnection of the in-segments and out-segments is accomplished
by using a cross-connect. We use the terminology "connection" and
"LSP" interchangeably where the meaning is clear from the context.
- Mechanisms for describing and naming objects and in-segment This is analogous to a GMPLS label on an interface.
events for the purpose of management. The first out-segment This is analogous to a GMPLS label on an interface.
version of this Structure of Management Information cross-connect This describes the conceptual connection between a
(SMI) is called SMIv1 and described in STD 16, RFC set of in-segments and out-segments.
1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, Note that either set may be 0; that is, a cross-
RFC 1215 [RFC1215]. The second version, called SMIv2, connect may connect only out-segments together with
is described in STD 58, RFC 2578 [RFC2578], STD 58, no in-segments in the case where an LSP is
RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. originating on an LSR.
- Message protocols for transferring management 3. The SNMP Management Framework
information. The first version of the SNMP message
protocol is called SNMPv1 and described in STD 15, RFC
1157 [RFC1157]. A second version of the SNMP message
protocol, which is not an Internet standards track
protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version
of the message protocol is called SNMPv3 and described
in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574
[RFC2574].
- Protocol operations for accessing management For a detailed overview of the documents that describe the current
information. The first set of protocol operations and Internet-Standard Management Framework, please refer to section 7 of
associated PDU formats is described in STD 15, RFC RFC 3410 [RFC3410].
1157 [RFC1157]. A second set of protocol operations
and associated PDU formats is described in RFC 1905
[RFC1905].
- A set of fundamental applications described in RFC Managed objects are accessed via a virtual information store, termed
2573 [RFC2573] and the view-based access control the Management Information Base or MIB. MIB objects are generally
mechanism described in RFC 2575 [RFC2575]. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a
MIB 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 [RFC2580].
A more detailed introduction to the current SNMP 4. Outline
Management Framework can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information Configuring statically provisioned GMPLS LSPs through an LSR involves
store, termed the Management Information Base or MIB. the following steps:
Objects in the MIB are defined using the mechanisms
defined in the SMI.
This memo specifies a MIB module that is compliant to the - Configuring an interface using the MPLS LSR MIB module.
SMIv2. A MIB conforming to the SMIv1 can be produced
through the appropriate translations. The resulting
translated MIB must be semantically equivalent, except
where objects or events are omitted because no
translation is possible (use of Counter64). Some machine
readable information in SMIv2 will be converted into
textual descriptions in SMIv1 during the translation
process. However, this loss of machine readable
information is not considered to change the semantics of
the MIB.
4. Terminology - Enabling GMPLS on GMPLS capable interfaces using this MIB module.
This document uses terminology from the document - Configuring in-segments and out-segments using the MPLS LSR MIB
describing the MPLS architecture [RFC3031]. module.
A label switched path (LSP) is modeled as a connection - Configuring GMPLS extensions to the in-segments and out-segments
consisting of one or more incoming segments (in-segments) using this MIB module.
and/or one or more outgoing segments (out-segments) at a
Label Switching Router (LSR). The association or
interconnection of the in-segments and out-segments is
accomplished by using a cross-connect. We use the
terminology "connection" and "LSP" interchangeably where
the meaning is clear from the context.
5. Feature List - Setting up the cross-connect table in the MPLS LSR MIB module to
associate segments and/or to indicate connection origination and
termination.
The GMPLS Label Switching Router MIB is designed to - Optionally setting up labels in the label table in this MIB module
satisfy the following requirements and constraints in if the textual convention
addition to those addressed by the MPLS LSR MIB: MplsLabel 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 MIB supports both manually configured LSPs as well - Optionally specifying label stack actions in the MPLS LSR MIB
as those configured via any GMPLS signaling protocol. module.
- The MIB supports the enabling and disabling of GMPLS - Optionally specifying segment traffic parameters in the MPLS LSR
capability on MPLS capable interfaces of an LSR. MIB module.
6. Summary of LSR MIB 4.1. Summary of the GMPLS LSR MIB Module
The MIB tables in this draft are: The MIB tables in this MIB module are as follows.
- The interface configuration table - The interface configuration table (gmplsInterfaceTable), which
(gmplsInterfaceConfTable), which extends extends mplsInterfaceTable to enable the GMPLS protocol on MPLS-
mplsInterfaceConfTable to enable the GMPLS protocol on capable interfaces.
MPLS-capable interfaces.
- The in-segment (gmplsInSegmentTable) and out-segment - The in-segment (gmplsInSegmentTable) and out-segment
(gmplsOutSegmentTable) tables extend (gmplsOutSegmentTable) tables extend mplsInSegmentTable and
mplsInSegmentTable and mplsOutSegmentTable to mplsOutSegmentTable to configuring GMPLS-specific parameters for
configuring GMPLS-specific parameters for LSP segments LSP segments at an LSR.
at an LSR.
- The gmplsLabelTable extends mplsLabelTable and allows - The gmplsLabelTable extends mplsLabelTable and allows Generalized
Generalized Labels to be defined and managed in a Labels to be defined and managed in a central location.
central location. Generalized Labels can be of Generalized Labels can be of variable length and have distinct
variable length and have distinct bit-by-bit bit-by-bit interpretations according to the use that is made of
interpretations according to the use that is made of
them. them.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
7. Bidirectional LSPs 5. Bidirectional LSPs
This MIB supports bidirectional LSPs as required for
GMPLS.
A single entry in the mplsXCIndex is shared by all of the This MIB supports bidirectional LSPs as required for GMPLS.
segments for the entire bidirectional LSP. This A single value of mplsXCIndex is shared by all of the segments for
facilitates a simple reference from [TEMIB] and the entire bidirectional LSP. This facilitates a simple reference
[GMPLSTEMIB], and makes fate-sharing more obvious. from [TEMIB] and [GMPLSTEMIB], and makes fate-sharing more obvious.
It is, however, important that the direction of segments It is, however, important that the direction of segments is
is understood to avoid connecting all in-segments to all understood to avoid connecting all in-segments to all out-segments.
out-segments. This is achieved by an object in each This is achieved by an object in each segment that indicates the
segment that indicates the direction of the segment with direction of the segment with respect to data flow.
respect to data flow.
A segment that is marked as 'forward' carries data from A segment that is marked as 'forward' carries data from the 'head' of
the 'head' of the LSP to the 'tail'. A segment marked as the LSP to the 'tail'. A segment marked as 'reverse' carries data in
'reverse' carries data in the reverse direction. the reverse direction.
Where an LSP is signaled using a conventional signaling Where an LSP is signaled using a conventional signaling protocol, the
protocol, the 'head' of the LSP is the source of the 'head' of the LSP is the source of the signaling (also known as the
signaling (also known as the ingress) and the 'tail' is ingress) and the 'tail' is the destination (also known as the
the destination (also known as the egress). For manually egress). For manually configured LSPs an arbitrary decision must be
configured LSPs an arbitrary decision must be made about made about which segments are 'forward' and which 'reverse'. For
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 participate in the LSP by assigning 'head' and 'tail' ends to the
that participate in the LSP by assigning 'head' and LSP.
'tail' ends to the LSP.
8. Example of LSP Setup 6. Example of LSP Setup
In this section we provide a brief example of using the In this section we provide a brief example of using the MIB objects
MIB objects described in section 9. to set up an LSP. described in section 9 to set up an LSP. While this example is not
While this example is not meant to illustrate every meant to illustrate every nuance of the MIB, it is intended as an aid
nuance of the MIB, it is intended as an aid to to understanding some of the key concepts. It is meant to be read
understanding some of the key concepts. It is meant to after going through the MIB itself. A prerequisite is an
be read after going through the MIB itself. A understanding of [LSRMIB].
prerequisite is an understanding of [LSRMIB].
Suppose that one would like to manually create a best- Suppose that one would like to manually create a best-effort, bi-
effort, bi-directional LSP. Assume that, in the forward directional LSP. Assume that, in the forward direction, the LSP
direction, the LSP enters the LSR via MPLS interface A enters the LSR via MPLS interface A with ifIndex 12 and exits the LSR
with ifIndex 12 and exits the LSR via MPLS interface B via MPLS interface B with ifIndex 13. For the reverse direction, we
with ifIndex 13. For the reverse direction, we assume assume the LSP enters via interface B and leaves via interface A
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- interfaces). Let us also assume that we do not wish to have a label
directional interfaces). Let us also assume that we do stack beneath the top label on the outgoing labeled packets. The
not wish to have a label stack beneath the top label on following example illustrates which rows and corresponding objects
the outgoing labeled packets. The following example might be created to accomplish this.
illustrates which rows and corresponding objects might be
created to accomplish this.
First, the traffic parameter entries must be set-up for First, the traffic parameter entries must be set-up for both
both segments. These are configured entirely in the MPLS segments. These are configured entirely in the MPLS LSR MIB through
LSR MIB through the mplsTrafficParamTable. the mplsTrafficParamTable.
Note that for a bi-directional LSP, the segments in the Note that for a bi-directional LSP, the segments in the reverse
reverse direction MAY share the traffic parameter entries direction MAY share the traffic parameter entries (and hence
(and hence resources) with the segments in the forward resources) with the segments in the forward direction.
direction.
We must next create the appropriate in-segment and out- We must next create the appropriate in-segment and out-segment
segment entries with suitable traffic parameters by entries with suitable traffic parameters by pointing to the
pointing to the appropriate traffic parameter entries appropriate traffic parameter entries that we have just created. This
that we have just created. This is also done in the MPLS is also done in the MPLS LSR MIB using mplsInSegmentTable and
LSR MIB using mplsInSegmentTable and mplsOutSegmentTable. mplsOutSegmentTable.
These table entries are extended by entries in These table entries are extended by entries in gmplsInSegmentTable
gmplsInSegmentTable and gmplsOutSegmentTable. Note that and gmplsOutSegmentTable. Note that the nature of the 'extends'
the nature of the 'extends' relationship is that the relationship is that the entry in gmplsInSegmentTable has the same
entry in gmplsInSegmentTable has the same index values as index values as the entry in mplsInSegmentTable. Similarly, the entry
the entry in mplsInSegmentTable. Similarly, the entry in in gmplsOutSegmentTable has the same index values as the entry in
gmplsOutSegmentTable has the same index values as the mplsOutSegmentTable.
entry in mplsOutSegmentTable.
First for the forward direction: First for the forward direction:
In gmplsInSegmentTable In gmplsInSegmentTable
{ {
gmplsInSegmentDirection = forward (1), gmplsInSegmentDirection = forward (1),
} }
In gmplsOutSegmentTable In gmplsOutSegmentTable
{ {
gmplsOutSegmentDirection = forward (1) gmplsOutSegmentDirection = forward (1)
} }
Next for the reverse direction: Next for the reverse direction:
In gmplsInSegmentTable In gmplsInSegmentTable
{ {
gmplsInSegmentDirection = reverse (2) gmplsInSegmentDirection = reverse (2)
} }
In gmplsOutSegmentTable In gmplsOutSegmentTable
{ {
gmplsOutSegmentDirection = reverse (2) gmplsOutSegmentDirection = reverse (2)
skipping to change at page 8, line 21 skipping to change at page 6, line 16
In gmplsInSegmentTable In gmplsInSegmentTable
{ {
gmplsInSegmentDirection = reverse (2) gmplsInSegmentDirection = reverse (2)
} }
In gmplsOutSegmentTable In gmplsOutSegmentTable
{ {
gmplsOutSegmentDirection = reverse (2) gmplsOutSegmentDirection = reverse (2)
} }
Next, two cross-connect entries are created in the Next, two cross-connect entries are created in the mplsXCTable of the
mplsXCTable of the MPLS LSR MIB, thereby associating the MPLS LSR MIB, thereby associating the newly created segments
newly created segments together. together.
9. GMPLS Label Switching Router MIB Definitions 7. GMPLS Label Switching Router MIB Definitions
GMPLS-LSR-MIB DEFINITIONS ::= BEGIN GMPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32
experimental, Unsigned32,
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
GmplsSegmentDirection GmplsSegmentDirection
FROM GMPLS-TC-MIB FROM GMPLS-TC-STD-MIB
; ;
gmplsLsrMIB MODULE-IDENTITY gmplsLsrStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200206240900Z " -- 24 June 2002 9:00:00 GMT" "200308190900Z " -- 19 August 2003 9:00:00 GMT"
ORGANIZATION "Common Control And Management Protocols ORGANIZATION
(CCAMP) Working Group" "Common Control And Management Protocols (CCAMP)
Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Postal: Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan Cheenu Srinivasan
Postal: Parama Networks, Inc. Bloomberg L.P.
1030 Broad Street Email: cheenu@bloomberg.net
Shrewsbury, NJ 07702
Tel: +1-732-544-9120 x731
Email: cheenu@paramanet.com
Tel: +1-732-544-9120x731
Adrian Farrel Adrian Farrel
Postal: Movaz Networks, Inc. Old Dog Consulting
7926 Jones Branch Drive Email: adrian@olddog.co.uk
McLean, VA 22102
Tel: +1-703-847-1867
Email: afarrel@movaz.com
Edward Harrison Ed Harrison
Postal: Data Connection Ltd. Data Connection Ltd.
100 Church Street Email: ed.harrison@dataconnection.com
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: eph@dataconnection.com
Tim Hall Tim Hall
Postal: Data Connection Ltd. Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: timhall@dataconnection.com Email: timhall@dataconnection.com
Comments about this document should be emailed direct to the
Email comments to the CCAMP WG Mailing List at CCAMP working group mailing list at ccamp@ops.ietf.org"
ccamp@ops.ietf.org."
DESCRIPTION DESCRIPTION
"This MIB contains managed object "This MIB module contains managed object definitions
definitions for the Generalized for the Generalized Multiprotocol Label Switching
Multiprotocol Label Switching (GMPLS) (GMPLS) Router as defined in: Ashwood-Smith et al.,
Router." Generalized Multiprotocol Label Switching (GMPLS)
Architecture, Internet Draft <draft-many-gmpls-
architecture-01.txt>, March 2001, work in progress.
Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices."
-- Revision history. -- Revision history.
REVISION REVISION
"200206240900Z" -- 24 June 2002 9:00:00 GMT "200308190900Z" -- 19 August 2003 09:00:00 GMT
DESCRIPITION DESCRIPTION
"First revision draft version." "Initial revision, published as part of RFC XXXX."
-- Above revision history to be replaced as below ::= { gmplsStdMIB xx }
-- REVISION "yyyymmddhhmmZ"
-- DESCRIPTION "Initial version, published as RFC xxxx"
-- xxxx to be assigned by RFC Editor
::= { experimental XXX } -- To Be Assigned by IANA
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrMIB 1 -- Top level components of this MIB module.
}
-- Notifications -- Notifications
-- no notifications are currently defined.
gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 0 }
-- Tables, Scalars
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 1 }
-- Conformance -- Conformance
gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrMIB 2 gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrStdMIB 2 }
}
-- GMPLS Interface Table.
gmplsInterfaceConfTable OBJECT-TYPE gmplsInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInterfaceConfEntry SYNTAX SEQUENCE OF GmplsInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies per-interface GMPLS "This table specifies per-interface GMPLS capability
capability and associated information. It and associated information. It extends the
extends the information in information in mplsInterfaceTable."
mplsInterfaceConfTable."
::= { gmplsLsrObjects 1 } ::= { gmplsLsrObjects 1 }
gmplsInterfaceConfEntry OBJECT-TYPE gmplsInterfaceEntry OBJECT-TYPE
SYNTAX GmplsInterfaceConfEntry SYNTAX GmplsInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by an LSR "A conceptual row in this table is created
for every interface capable of supporting automatically by an LSR for every interface capable
GMPLS. Each entry in this table will exist of supporting GMPLS and which is configured to do
only if corresponding entries in so. A conceptual row in this table will exist if and
mplsInterfaceConfTable and ifTable exists. only if a corresponding entry in mplsInterfaceTable
If the associated entry in exists, and a corresponding entry in ifTable exists
mplsInterfaceConfTabel or ifTable is with ifType = mpls(166). If the associated entry in
deleted, the corresponding entry in this ifTable is operationally disabled (thus removing the
table must also be deleted shortly GMPLS capabilities on the interface) or the entry in
mplsInterfaceTable is deleted, the corresponding
entry in this table MUST be deleted shortly
thereafter. thereafter.
The indexing is the same as that for
mplsInterfaceConfTabel. 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."
INDEX { mplsInterfaceConfIndex }
::= { gmplsInterfaceConfTable 1 }
GmplsInterfaceConfEntry ::= SEQUENCE { The indexing is the same as that 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."
INDEX { mplsInterfaceIndex }
::= { gmplsInterfaceTable 1 }
gmplsInterfaceConfSignalingCaps BITS GmplsInterfaceEntry ::= SEQUENCE {
gmplsInterfaceSignalingCaps BITS
} }
""gmplsInterfaceConfSignalingCaps OBJECT-TYPE gmplsInterfaceSignalingCaps OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
rsvp-gmpls (1), rsvp-gmpls (1),
crldp-gmpls (2), crldp-gmpls (2), -- note the use of CR-LDP is deprecated
other-gmpls (3) other-gmpls (3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Defines the signaling capabilities on this "Defines the signaling capabilities on this
interface. Multiple bits may legitimately interface. Multiple bits may legitimately be set at
be set at once. Setting no bits implies once. Setting no bits implies that GMPLS signaling
that GMPLS signaling cannot be performed on cannot be performed on this interface and all LSPs
this interface and all LSPs must be must be manually provisioned."
manually provisioned." ::= { gmplsInterfaceEntry 1 }
::= { gmplsInterfaceConfEntry 1 }
-- End of gmplsInterfaceTable
-- In-segment table. -- In-segment table.
gmplsInSegmentTable OBJECT-TYPE gmplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInSegmentEntry SYNTAX SEQUENCE OF GmplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table extends the mplsInSegmentTable "This table extends the mplsInSegmentTable to provide
to provide GMPLS-specific information about GMPLS-specific information about incoming segments
incoming segments to an LSR." to an LSR."
::= { 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 "An entry in this table extends the representation of
representation of an incoming segment an incoming segment represented by an entry in
represented by an entry in mplsInSegmentTable. An entry can be created by a
mplsInSegmentTable. An entry can be network administrator or an SNMP agent, or a GMPLS
created by a network administrator or an signaling protocol.
SNMP agent, or a GMPLS signaling protocol.
" Note that the storage type for this entry SHOULD be
inherited from the corresponding entry in the
mplsInSegmentTable given by the value of the
mplsInSegmentStorageType object."
INDEX { mplsInSegmentIndex } INDEX { mplsInSegmentIndex }
::= { gmplsInSegmentTable 1 } ::= { gmplsInSegmentTable 1 }
GmplsInSegmentEntry ::= SEQUENCE { GmplsInSegmentEntry ::= SEQUENCE {
gmplsInSegmentDirection gmplsInSegmentDirection GmplsSegmentDirection
GmplsSegmentDirection
} }
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 variable indicates the direction of "This object indicates the direction of data flow on
data flow on this segment." this segment. This object cannot be modified if
mplsInSegmentRowStatus for the associated entry in
the mplsInSegmentTable is active(1)."
DEFVAL { forward } DEFVAL { forward }
::= { gmplsInSegmentEntry 1 } ::= { gmplsInSegmentEntry 1 }
-- End of gmplsInSegmentTable -- End of gmplsInSegmentTable
-- Out-segment table. -- 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 "This table extends the mplsOutSegmentTable to
to provide GMPLS-specific information about provide GMPLS-specific information about outgoing
outgoing segments from an LSR." segments from an LSR."
::= { 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 "An entry in this table extends the representation of
representation of an outgoin segment an outgoing segment represented by an entry in
represented by an entry in mplsOutSegmentTable. An entry can be created by a
mplsOutSegmentTable. An entry can be network administrator or an SNMP agent, or a GMPLS
created by a network administrator or an signaling protocol.
SNMP agent, or a GMPLS signaling protocol. Note that the storage type for this entry SHOULD be
" inherited from the corresponding entry in the
mplsOutSegmentTable given by the value of the
mplsOutSegmentStorageType object."
INDEX { mplsOutSegmentIndex } INDEX { mplsOutSegmentIndex }
::= { gmplsOutSegmentTable 1 } ::= { gmplsOutSegmentTable 1 }
GmplsOutSegmentEntry ::= SEQUENCE { GmplsOutSegmentEntry ::= SEQUENCE {
gmplsOutSegmentDirection gmplsOutSegmentDirection GmplsSegmentDirection,
GmplsSegmentDirection,
gmplsOutSegmentTTLDecrement Unsigned32 gmplsOutSegmentTTLDecrement Unsigned32
} }
"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 variable indicates the direction of "This object indicates the direction of data flow on
data flow on this segment. This object this segment. This object cannot be modified if
cannot be modified if mplsOutSegmentRowStatus for the associated entry in
mplsOutSegmentRowStatus for the associated the mplsOutSegmentTable is active(1)."
entry in the mplsOutSegmentTavle is
active(1)."
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 variable indicates the amount by which "This object indicates the amount by which to
to decrement the TTL of any payload packets decrement the TTL of any payload packets forwarded
forwarded on this segment if per-hop on this segment if per-hop decrementing is being
decrementing is being done. done.
A value of zero indicates that no decrement
should be made or that per-hop decrementing A value of zero indicates that no decrement should
is not in force. be made or that per-hop decrementing is not in
See the gmplsTunnelTTLDecrement object in force.
the gmplsTunnelTable of [GMPLSTEMIB] for a
value by which to decrement the TTL for the See the gmplsTunnelTTLDecrement object in the
whole of a tunnel. gmplsTunnelTable of [GMPLSTEMIB] for a value by
which to decrement the TTL for the whole of a
tunnel.
This object cannot be modified if This object cannot be modified if
mplsOutSegmentRowStatus for the associated mplsOutSegmentRowStatus for the associated entry in
entry in the mplsOutSegmentTavle is the mplsOutSegmentTable is active(1)."
active(1)."
DEFVAL { 0 } DEFVAL { 0 }
::= { gmplsOutSegmentEntry 2 } ::= { gmplsOutSegmentEntry 2 }
-- End of gmplsOutSegmentTable -- End of gmplsOutSegmentTable
""
-- Module compliance. -- 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.
gmplsLsrModuleCompliance MODULE-COMPLIANCE gmplsLsrModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that "Compliance statement for agents that provide full
support the GMPLS LSR MIB." support for GMPLS-LSR-STD-MIB."
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863.
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MODULE MPLS-LSR-STD-MIB û The MPLS LSR MIB
MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup,
mplsLsrNotificationGroup
}
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented MANDATORY-GROUPS {
-- by all LSRs that support GMPLS. However, they gmplsInterfaceGroup,
-- may all be supported as read-only objects in gmplsInSegmentGroup,
-- the case where manual configuration is unsupported. gmplsOutSegmentGroup
}
-- gmplsInSegmentTable
OBJECT gmplsInSegmentDirection
SYNTAX GmplsSegmentDirection
MIN-ACCESS read-write
DESCRIPTION
"Only forward(1) needs to be supported by
implementations that only support unidirectional
LSPs."
-- gmplsOutSegmentTable
OBJECT gmplsOutSegmentDirection
SYNTAX GmplsSegmentDirection
MIN-ACCESS read-write
DESCRIPTION
"Only forward(1) needs to be supported by
implementations that only support unidirectional
LSPs."
OBJECT gmplsOutSegmentTTLDecrement
SYNTAX Unsigned32 (0..255)
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { gmplsLsrCompliances 1 }
-- Compliance requirement for implementations that provide read-only
-- access.
gmplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance requirement for implementations that only
provide read-only support for GMPLS-LSR-STD-MIB. Such
devices can then be monitored but cannot be configured
using this MIB modules."
MODULE IF-MIB -- The interfaces Group MIB, RFC 2863
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MODULE MPLS-LSR-STD-MIB
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInterfaceGroup,
mplsInSegmentGroup,
mplsOutSegmentGroup,
mplsXCGroup,
mplsPerfGroup
}
MODULE -- this module
MANDATORY-GROUPS {
gmplsInterfaceGroup,
gmplsInSegmentGroup, gmplsInSegmentGroup,
gmplsOutSegmentGroup, gmplsOutSegmentGroup
gmplsInterfaceGroup
} }
"-- gmplsInSegmentTable -- gmplsInterfaceGroup
OBJECT gmplsInterfaceSignalingCaps
SYNTAX BITS
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- gmplsInSegmentTable
OBJECT gmplsInSegmentDirection OBJECT gmplsInSegmentDirection
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only forward(1) needs to be supported." "Write access is not required. Only forward(1) needs
to be supported by implementations that only support
unidirectional LSPs."
-- gmplsOutSegmentTable -- gmplsOutSegmentTable
OBJECT gmplsOutSegmentDirection OBJECT gmplsOutSegmentDirection
SYNTAX GmplsSegmentDirection SYNTAX GmplsSegmentDirection
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only forward(1) needs to be supported." "Write access is not required. Only forward(1) needs
to be supported by implementations that 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 2 }
-- Units of conformance. -- Units of conformance.
gmplsInterfaceGroup OBJECT-GROUP gmplsInterfaceGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsInterfaceConfSignalingCaps gmplsInterfaceSignalingCaps
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for GMPLS "Collection of objects needed for GMPLS interface
interface configuration and performance configuration and performance information."
information."
::= { gmplsLsrGroups 1 } ::= { gmplsLsrGroups 1 }
gmplsInSegmentGroup OBJECT-GROUP gmplsInSegmentGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsInSegmentDirection gmplsInSegmentDirection
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement a "Collection of objects needed to implement a GMPLS
GMPLS in-segment." in-segment."
::= { gmplsLsrGroups 2 } ::= { gmplsLsrGroups 2 }
gmplsOutSegmentGroup OBJECT-GROUP gmplsOutSegmentGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsOutSegmentDirection, gmplsOutSegmentDirection,
gmplsOutSegmentTTLDecrement gmplsOutSegmentTTLDecrement
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed to implement a "Collection of objects needed to implement a GMPLS
GMPLS out-segment." out-segment."
::= { gmplsLsrGroups 3 } ::= { gmplsLsrGroups 3 }
END END
10. GMPLS Label MIB Definitions 8. GMPLS Label MIB Definitions
GMPLS-LABEL-MIB DEFINITIONS ::= BEGIN GMPLS-LABEL-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32
experimental, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
GmplsGeneralizedLabelTypes, RowStatus, StorageType
GmplsGeneralizedLabelSubtypes, FROM SNMPv2-TC
GmplsFreeformLabel InterfaceIndexOrZero
FROM GMPLS-TC-MIB FROM IF-MIB
MplsLabel
FROM MPLS-TC-STD-MIB
GmplsGeneralizedLabelTypes, GmplsFreeformLabel
FROM GMPLS-TC-STD-MIB
; ;
gmplsLabelMIB MODULE-IDENTITY gmplsLabelStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200206240900Z " -- 24 June 2002 9:00:00" "200308190900Z " -- 19 August 2003 9:00:00 GMT"
ORGANIZATION ORGANIZATION
"Common Control And Management Protocols (CCAMP) "Common Control And Management Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Postal: Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan Cheenu Srinivasan
Postal: Parama Networks, Inc. Bloomberg L.P.
1030 Broad Street Email: cheenu@bloomberg.net
Shrewsbury, NJ 07702
Tel: +1-732-544-9120 x731
Email: cheenu@paramanet.comTel: +1-732-544-9120x731
Adrian Farrel Adrian Farrel
Postal: Movaz Networks, Inc. Old Dog Consulting
7926 Jones Branch Drive Email: adrian@olddog.co.uk
McLean, VA 22102
Tel: +1-703-847-1867
Email: afarrel@movaz.com
Edward Harrison Ed Harrison
Postal: Data Connection Ltd. Data Connection Ltd.
100 Church Street Email: ed.harrison@dataconnection.com
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: eph@dataconnection.com
Tim Hall Tim Hall
Postal: Data Connection Ltd. Data Connection Ltd.
100 Church Street Email: timhall@dataconnection.com
Enfield, Middlesex Comments about this document should be emailed direct to the
EN2 6BQ, United Kingdom CCAMP working group mailing list at ccamp@ops.ietf.org"
Tel: +44-20-8366-1177
Email: timhall@dataconnection.com"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object "This MIB module contains managed object definitions
definitions for labels within GMPLS for labels within GMPLS systems."
systems."
-- Revision history. -- Revision history.
REVISION REVISION
"200206240900Z " -- 24 June 2002 9:00:00 "200308190900Z" -- 19 August 2003 09:00:00 GMT
GMT"
DESCRIPTION DESCRIPTION
"Initial version." "Initial revision, published as part of RFC XXXX."
-- Above revision history to be replaced as below ::= { gmplsStdMIB 2 }
-- REVISION "yyyymmddhhmmZ"
-- DESCRIPTION "Initial version, published as RFC xxxx"
-- xxxx to be assigned by RFC Editor
::= { experimental XXX } -- To Be Assigned by IANA
-- Top level components of this MIB module.
gmplsLabelObjects OBJECT IDENTIFIER ::= { -- Notifications
gmplsLabelMIB 0 } -- no notifications are currently defined.
gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLsrNotifications OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 0 }
gmplsLabelMIB 1 }
-- Tables, Scalars
gmplsLabelObjects OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 1 }
-- Conformance
gmplsLabelConformance OBJECT IDENTIFIER ::= { gmplsLabelStdMIB 2 }
-- GMPLS Label Table. -- GMPLS Label Table.
gmplsLabelTable OBJECT-TYPE gmplsLabelTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsLabelEntry SYNTAX SEQUENCE OF GmplsLabelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of GMPLS Labels. This table extends "Table of GMPLS Labels. This table allows the
mplsLabelTable to handle the more complex representation of the more complex label forms
label forms required for GMPLS. required for GMPLS which cannot be held within the
Each entry in this table represents an textual convention MplsLabel. That is labels that
individual GMPLS label value. Labels in cannot be encoded within 32 bits. It is,
the tables in other MIBs are referred to nevertheless also capable of holding 32 bit labels
using index entries into mplsLabelTable. or regular MPLS labels if desired.
The indexing of this table is identical.
In effect, this table taken together with Each entry in this table represents an individual
mplsLabelTable provides an integer mapping GMPLS label value. Labels in the tables in other
for label values that may be more complex MIBs are referred to using row pointer into this
than simple integers." table. The indexing of this table provides for
arbitrary indexing and also for concatenation of
labels. "
::= { gmplsLabelObjects 1 } ::= { gmplsLabelObjects 1 }
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 extends the label "An entry in this table represents a single label
defintion in mplsLabelTable for use with value. There are three indexes into the table.
certain types of switching appropriate to - The interface index may be helpful to distinguish
GMPLS." which labels are in use on which interfaces or to
INDEX { mplsLabelInterface, mplsLabelIndex, handle cases where there are a very large number
gmplsSublabelIndex } of labels in use in the system. When label
representation is desired to apply to the whole
system or when it is not important to distinguish
labels by their interfaces, this index MAY be set
to zero.
- The label index provides a way of identifying the
label.
- The label sub-index is only used for concatenated
labels. It identifies each component label. When
non-concatenated labels are used, this index
SHOULD be set to zero.
A storage type object is supplied to control the
storage type for each entry, but implementations
should note that the storage type of conceptual rows
in other tables that include row 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 is more persistent."
INDEX {
gmplsLabelInterface,
gmplsLabelIndex,
gmplsLabelSubindex }
::= { gmplsLabelTable 1 } ::= { gmplsLabelTable 1 }
GmplsLabelEntry ::= SEQUENCE { GmplsLabelEntry ::= SEQUENCE {
gmplsSublabelIndex Unsigned32, gmplsLabelInterface InterfaceIndexOrZero,
gmplsLabelIndex Unsigned32,
gmplsLabelSubindex Unsigned32,
gmplsLabelType GmplsGeneralizedLabelTypes, gmplsLabelType GmplsGeneralizedLabelTypes,
gmplsLabelSubtype GmplsGeneralizedLabelSubtypes, gmplsLabelMplsLabel MplsLabel,
gmplsPortWavelengthLabel Unsigned32, gmplsLabelPortWavelength Unsigned32,
gmplsFreeformLength INTEGER, gmplsLabelFreeformLength INTEGER,
gmplsFreeformLabel GmplsFreeformLabel, gmplsLabelFreeform GmplsFreeformLabel,
gmplsSonetSdhSignalIndex INTEGER, gmplsLabelSonetSdhSignalIndex INTEGER,
gmplsSdhVc INTEGER, gmplsLabelSdhVc INTEGER,
gmplsSdhVcBranch INTEGER, gmplsLabelSdhVcBranch INTEGER,
gmplsSonetSdhBranch INTEGER, gmplsLabelSonetSdhBranch INTEGER,
gmplsSonetSdhGroupBranch INTEGER, gmplsLabelSonetSdhGroupBranch INTEGER,
gmplsWavebandId Unsigned32, gmplsLabelWavebandId Unsigned32,
gmplsWavebandStartLabel Unsigned32, gmplsLabelWavebandStartLabel Unsigned32,
gmplsWavebandEndLabel Unsigned32 gmplsLabelWavebandEndLabel Unsigned32,
gmplsLabelRowStatus RowStatus,
gmplsLabelStorageType StorageType
} }
gmplsSublabelIndex OBJECT-TYPE gmplsLabelInterface OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In conjunction with mplsLabelInterface and "The interface on which this label is used. If the
mplsLabelIndex, this object uniquely label has or could have applicability across the
identifies this row. This sub-index allows whole system, this object SHOULD be set to zero."
a single GMPLS label to be defined as a
concatenation of labels. This is
particularly useful in TDM.
The ordering of sub-labels is strict with
the sub-label with lowest
gmplsSublabelIndex appearing first. Note
that all sub-labels of a single GMPLS label
must share the same mplsLabelInterface and
mplsLabelIndex values. For labels that are
not composed of concatenated sub-labels,
this value should be set to zero."
::= { gmplsLabelEntry 1 } ::= { gmplsLabelEntry 1 }
gmplsLabelIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary index into the table to identify a
label.
Note that implementations that are representing 32
bit labels within this table MAY choose to align
this index with the value of the label, but should
be aware of the implications of sparsely populated
tables."
::= { gmplsLabelEntry 2 }
gmplsLabelSubindex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"In conjunction with gmplsLabelInterface and
gmplsLabelIndex, this object uniquely identifies
this row. This sub-index allows a single GMPLS label
to be defined as a concatenation of labels. This is
particularly useful in TDM.
The ordering of sub-labels is strict with the sub-
label with lowest gmplsLabelSubindex appearing
first. Note that all sub-labels of a single GMPLS
label must share the same gmplsLabelInterface and
gmplsLabelIndex values. For labels that are not
composed of concatenated sub-labels, this value
SHOULD be set to zero."
::= { gmplsLabelEntry 3 }
gmplsLabelType OBJECT-TYPE gmplsLabelType OBJECT-TYPE
SYNTAX GmplsGeneralizedLabelTypes SYNTAX GmplsGeneralizedLabelTypes
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifies the type of this label as it "Identifies the type of this label. Note that this
appears in a Generalized Label. This object does not determine whether MPLS or GMPLS
object has meaning only if the value of signaling is in use: a value of gmplsMplsLabel (1)
mplsLabelType is other(1)." denotes that a 23 bit MPLS packet label is present,
::= { gmplsLabelEntry 2 } but does not describe whether this is signaled using
MPLS or GMPLS.
The value of this object helps determine which of
the following objects are valid.
This object cannot be modified if
gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 4 }
gmplsLabelSubtype OBJECT-TYPE gmplsLabelMplsLabel OBJECT-TYPE
SYNTAX GmplsGeneralizedLabelSubtypes SYNTAX MplsLabel
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Subtype to help determine which of the "The value of an MPLS label (that is a packet label)
subsequent fields should be used to form if this table is used to store it. This may be used
the Generalized Label." in MPLS systems even though the label values can be
::= { gmplsLabelEntry 3 } adequately stored in the MPLS MIB modules. Further,
in mixed MPLS and GMPLS systems it may be
advantageous to store all labels in a single label
table. Lastly, in GMPLS systems where packet labels
are used (that is in systems that use GMPLS
signaling and GMPLS labels for packet switching) it
may be desirable to use this table.
This object is only valid if gmplsLabelType is set
to gmplsMplsLabel (1).
This object cannot be modified if
gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 6 }
gmplsPortWavelengthLabel 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 "The value of a Port or Wavelength Label when carried
when carried as a Generalized Label. Only as a Generalized Label. Only valid if gmplsLabelType
valid if mplsLabelType is set to other(1), is set to gmplsPortWavelengthLabel(2).
gmplsLabelType is set to This object cannot be modified if
generalizedLabel(2), and gmplsLabelSubtype gmplsLabelRowStatus is active(1)."
is set to portWavelengthLabel(2)." ::= { gmplsLabelEntry 7 }
::= { gmplsLabelEntry 4 }
gmplsFreeformLength OBJECT-TYPE gmplsLabelFreeformLength OBJECT-TYPE
SYNTAX INTEGER (1..64) SYNTAX INTEGER (1..64)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length of a freeform Generalized Label "The length of a freeform Generalized Label indicated
indicated in the gmplsFreeformLabel object. in the gmplsFreeformLabel object. Only valid if
Only valid if mplsLabelType is set to gmplsLabelType is set to
other(1), gmplsLabelType is set to gmplsFreeformGeneralizedLabel(3).
generalizedLabel(2), and gmplsLabelSubtype This object cannot be modified if
is set to freeformGeneralizedLabel(3)." gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 5 } ::= { gmplsLabelEntry 8 }
gmplsFreeformLabel 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 "The value of a freeform Generalized Label that does
that does not conform to one of the not conform to one of the standardized label
standardized label encoding or that an encoding or that an implementation chooses to
implementation chooses to represent as an
octet string without further decoding. The
length of this object is given by the value
of gmplsFreeformLength. Only valid if
mplsLabelType is set to other(1),
gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to freeformGeneralizedLabel(3)."
::= { gmplsLabelEntry 6 }
gmplsSonetSdhSignalIndex OBJECT-TYPE represent as an octet string without further
decoding. The length of this object is given by the
value of gmplsFreeformLength. Only valid if
gmplsLabelType is set to
gmplsFreeformGeneralizedLabel(3).
This object cannot be modified if
gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 9 }
gmplsLabelSonetSdhSignalIndex OBJECT-TYPE
SYNTAX INTEGER (0..4095) SYNTAX INTEGER (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 "The Signal Index value (S) of a SONET or SDH
SDH Generalized Label. 0 indicates that Generalized Label. Zero indicates that this field is
this field is non-significant. Only valid not significant. Only valid if gmplsLabelType is set
if mplsLabelType is set to other(1), to gmplsSonetLabel(4) or gmplsSdhLabel(5).
gmplsLabelType is set to This object cannot be modified if
generalizedLabel(2), and gmplsLabelSubtype gmplsLabelRowStatus is active(1)."
is set to sonetLabel(4) or sdhLabel(5)." ::= { gmplsLabelEntry 10 }
::= { gmplsLabelEntry 7 }
gmplsSdhVc OBJECT-TYPE gmplsLabelSdhVc OBJECT-TYPE
SYNTAX INTEGER (0..15) SYNTAX INTEGER (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VC Indicator (U) of an SDH Generalized "The VC Indicator (U) of an SDH Generalized Label.
Label. 0 indicates that this field is non- Zero indicates that this field is non-significant.
significant. Only valid if mplsLabelType Only valid if gmplsLabelType is set to
is set to other(1), gmplsLabelType is set gmplsSdhLabel(5).
to generalizedLabel(2), and This object cannot be modified if
gmplsLabelSubtype is set to sdhLabel(5)." gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 8 } ::= { gmplsLabelEntry 11 }
gmplsSdhVcBranch OBJECT-TYPE gmplsLabelSdhVcBranch OBJECT-TYPE
SYNTAX INTEGER (0..15) SYNTAX INTEGER (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VC Branch Indicator (K) of an SDH "The VC Branch Indicator (K) of an SDH Generalized
Generalized Label. 0 indicates that this Label. Zero indicates that this field is non-
field is non-significant. Only valid if significant. Only valid if gmplsLabelType is set to
mplsLabelType is set to other(1), gmplsSdhLabel(5).
gmplsLabelType is set to This object cannot be modified if
generalizedLabel(2), and gmplsLabelSubtype gmplsLabelRowStatus is active(1)."
is set to sdhLabel(5)." ::= { gmplsLabelEntry 12 }
::= { gmplsLabelEntry 9 }
gmplsSonetSdhBranch OBJECT-TYPE gmplsLabelSonetSdhBranch OBJECT-TYPE
SYNTAX INTEGER (0..15) SYNTAX INTEGER (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Branch Indicator (L) of a Sonet or SDH "The Branch Indicator (L) of a SONET or SDH
Generalized Label. 0 indicates that this Generalized Label. Zero indicates that this field is
field is non-significant. Only valid if non-significant. Only valid gmplsLabelType is set to
mplsLabelType is set to other(1), gmplsSonetLabel(4) or gmplsSdhLabel(5).
gmplsLabelType is set to This object cannot be modified if
generalizedLabel(2), and gmplsLabelSubtype gmplsLabelRowStatus is active(1)."
is set to sonetLabel(4) or SdhLabel(5)." ::= { gmplsLabelEntry 13 }
::= { gmplsLabelEntry 10 } gmplsLabelSonetSdhGroupBranch OBJECT-TYPE
gmplsSonetSdhGroupBranch OBJECT-TYPE
SYNTAX INTEGER (0..15) SYNTAX INTEGER (0..15)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Group Branch Indicator (M) of a Sonet "The Group Branch Indicator (M) of a SONET or SDH
or SDH Generalized Label. 0 indicates that Generalized Label. Zero indicates that this field is
this field is non-significant. Only valid non-significant. Only valid if gmplsLabelType is set
if mplsLabelType is set to other(1), to gmplsSonetLabel(4) or gmplsSdhLabel(5).
gmplsLabelType is set to This object cannot be modified if
generalizedLabel(2), and gmplsLabelSubtype gmplsLabelRowStatus is active(1)."
is set to sonetLabel(4) or sdhLabel(5)." ::= { gmplsLabelEntry 14 }
::= { gmplsLabelEntry 11 }
gmplsWavebandId OBJECT-TYPE gmplsLabelWavebandId OBJECT-TYPE
SYNTAX Uunsigned32 SYNTAX Uunsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The waveband identifier component of a "The waveband identifier component of a waveband
waveband label. Only valid if label. Only valid if gmplsLabelType is set to
mplsLabelType is set to other(1), gmplsWavebandLabel(6).
gmplsLabelType is set to This object cannot be modified if
generalizedLabel(2), and gmplsLabelSubtype gmplsLabelRowStatus is active(1)."
is set to wavebandLabel(6)." ::= { gmplsLabelEntry 15 }
::= { gmplsLabelEntry 12 }
gmplsWavebandStartLabel OBJECT-TYPE gmplsLabelWavebandStart OBJECT-TYPE
SYNTAX Uunsigned32 SYNTAX Uunsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The starting label component of a waveband "The starting label component of a waveband label.
label. Only valid if mplsLabelType is set Only valid if gmplsLabelType is set to
to other(1), gmplsLabelType is set to gmplsWavebandLabel(6).
generalizedLabel(2), and gmplsLabelSubtype This object cannot be modified if
is set to wavebandLabel(6)." gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 13 } ::= { gmplsLabelEntry 16 }
gmplsWavebandEndLabel OBJECT-TYPE gmplsLabelWavebandEnd OBJECT-TYPE
SYNTAX Uunsigned32 SYNTAX Uunsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The end label component of a waveband "The end label component of a waveband label. Only
label. Only valid if mplsLabelType is set valid if gmplsLabelType is set to
to other(1), gmplsLabelType is set to gmplsWavebandLabel(6).
generalizedLabel(2), and gmplsLabelSubtype This object cannot be modified if
is set to wavebandLabel(6)." gmplsLabelRowStatus is active(1)."
::= { gmplsLabelEntry 14 } ::= { gmplsLabelEntry 17 }
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 18 }
gmplsLabelStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object.
The agent MUST ensure that this object's value
remains consistent with the storage type of any rows
in other tables that contain 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
to it.
Conceptual rows having the value 'permanent' need
not allow write-access to any columnar objects in
the row."
REFERENCE
"See RFC2579."
DEFVAL { volatile }
::= { gmplsLabelEntry 19 }
-- End of GMPLS Label Table -- End of GMPLS Label Table
-- Module compliance. -- Module compliance.
gmplsLabelGroups gmplsLabelGroups
OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 } OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 }
gmplsLabelCompliances gmplsLabelCompliances
OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 } OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 }
gmplsLabelModuleCompliance MODULE-COMPLIANCE gmplsLabelModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that "Compliance statement for agents that support
support the GMPLS Label MIB." the GMPLS Label MIB module."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented by -- The mandatory groups have to be implemented by
-- LSRs claiming support for this MIB. This MIB itself, -- LSRs claiming support for this MIB module. This MIB module is,
-- however, is mandatory only on LSRs supporting GMPLS -- however, not mandatory for a working implementation of a GMPLS
-- LSR with full MIB support if the GMPLS labels in use can be
-- represented within a 32 bit quantity.
MANDATORY-GROUPS { MANDATORY-GROUPS {
gmplsLabelTableGroup gmplsLabelTableGroup
} }
-- Units of conformance. -- Units of conformance.
GROUP gmplsLabelTableGroup GROUP gmplsLabelTableGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for devices which "This group is mandatory for devices which support
support the gmplsLabelTable." the gmplsLabelTable."
GROUP gmplsPortWavelengthLabelGroup GROUP gmplsLabelPacketGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for "This group extends gmplsLabelTableGroup for
implementations that support port and implementations that support packet labels."
wavelength labels."
GROUP gmplsFreeformLabelGroup GROUP gmplsLabelPortWavelengthGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for "This group extends gmplsLabelTableGroup for
implementations that support freeform implementations that support port and wavelength
labels." labels."
GROUP gmplsSonetSdhLabelGroup
GROUP gmplsLabelFreeformGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup for "This group extends gmplsLabelTableGroup for
implementations that support SonetSdh implementations that support freeform labels."
labels."
GROUP gmplsWavebandLabelGroup GROUP gmplsLabelSonetSdhGroup
DESCRIPTION DESCRIPTION
"This group extends gmplsLabelTableGroup "This group extends gmplsLabelTableGroup for
for implementations that support implementations that support SONET or SDH labels."
Waveband labels."
GROUP gmplsLabelWavebandGroup
DESCRIPTION
"This group extends gmplsLabelTableGroup for
implementations that support Waveband labels."
-- gmplsLabelTable -- 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 gmplsLabelSubtype OBJECT gmplsLabelMplsLabel
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsLabelPortWavelength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsPortWavelengthLabel OBJECT gmplsLabelFreeformLength
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsFreeformLength OBJECT gmplsLabelFreeform
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsFreeformLabel OBJECT gmplsLabelSonetSdhSignalIndex
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsSonetSdhSignalIndex OBJECT gmplsLabelSdhVc
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsSdhVc OBJECT gmplsLabelSdhVcBranch
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsSdhVcBranch
OBJECT gmplsLabelSonetSdhBranch
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsSonetSdhBranch OBJECT gmplsLabelSonetSdhGroupBranch
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsSonetSdhGroupBranch OBJECT gmplsLabelWavebandId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsWavebandId OBJECT gmplsLabelWavebandStart
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsWavebandStartLabel OBJECT gmplsLabelWavebandEnd
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT gmplsLabelRowStatus
SYNTAX RowStatus {
active(1),
notInService(2)
}
WRITE-SYNTAX RowStatus {
active(1),
notInService(2),
createAndGo(4),
destroy(6)
}
DESCRIPTION
"Support for notInService, createAndWait and notReady
is not required."
OBJECT gmplsWavebandEndLabel OBJECT gmplsLabelStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { gmplsLabelCompliances 1 } ::= { gmplsLabelCompliances 1 }
-- Units of conformance. -- Units of conformance.
gmplsLabelTableGroup OBJECT-GROUP gmplsLabelTableGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsLabelType, gmplsLabelType,
gmplsLabelSubtype gmplsLabelSubtype,
gmplsLabelRowStatus,
gmplsLabelStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Necessary, but not sufficient, set of "Necessary, but not sufficient, set of objects to
objects to implement label table support. implement label table support. In addition,
In addition, depending on the type of depending on the type of labels supported (for
labels supported (for example, wavelength example, wavelength labels), the following other
labels), the following other groups defined groups defined below are mandatory:
below are mandatory: gmplsLabelPacketGroup and/or
gmplsPortWavelengthLabelGroup and/or gmplsLabelPortWavelengthGroup and/or
gmplsFreeformLabelGroup and/or gmplsLabelFreeformGroup and/or
gmplsSonetSdhLabelGroup." gmplsLabelSonetSdhGroup."
::= { gmplsLabelGroups 1 } ::= { gmplsLabelGroups 1 }
gmplsPortWavelengthLabelGroup OBJECT-GROUP gmplsLabelPacketGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsPortWavelengthLabel gmplsLabelMplsLabel
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement Port and "Object needed to implement Packet (MPLS) labels."
Wavelength labels."
::= { gmplsLabelGroups 2 } ::= { gmplsLabelGroups 2 }
gmplsLabelPortWavelengthGroup OBJECT-GROUP
gmplsFreeformLabelGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsFreeformLength, gmplsLabelPortWavelength
gmplsFreeformLabel
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement Freeform "Object needed to implement Port and Wavelength
labels." labels."
::= { gmplsLabelGroups 3 } ::= { gmplsLabelGroups 3 }
gmplsSonetSdhLabelGroup OBJECT-GROUP gmplsLabelFreeformGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsSonetSdhSignalIndex, gmplsLabelFreeformLength,
gmplsSdhVc, gmplsLabelFreeform
gmplsSdhVcBranch,
gmplsSonetSdhBranch,
gmplsSonetuSdhGroupBranch
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement SONET and SDH "Object needed to implement Freeform labels."
labels."
::= { gmplsLabelGroups 4 } ::= { gmplsLabelGroups 4 }
gmplsWavebandLabelGroup OBJECT-GROUP gmplsLabelSonetSdhGroup OBJECT-GROUP
OBJECTS { OBJECTS {
gmplsWavebandId, gmplsLabelSonetSdhSignalIndex,
gmplsWavebandStartLabel, gmplsLabelSdhVc,
gmplsWavebandEndLabel gmplsLabelSdhVcBranch,
gmplsLabelSonetSdhBranch,
gmplsLabelSonetSdhGroupBranch
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Object needed to implement Waveband "Object needed to implement SONET and SDH labels."
labels."
::= { gmplsLabelGroups 5 } ::= { gmplsLabelGroups 5 }
END gmplsLabelWavebandGroup OBJECT-GROUP
OBJECTS {
11. Security Considerations gmplsLabelWavebandId,
gmplsLabelWavebandStart,
It is clear that this MIB is potentially useful for gmplsLabelWavebandEnd
monitoring of MPLS LSRs. This MIB can also be used for }
configuration of certain objects, and anything that can STATUS current
be configured can be incorrectly configured, with DESCRIPTION
potentially disastrous results. "Object needed to implement Waveband labels."
::= { gmplsLabelGroups 6 }
There are a number of management objects defined in this
MIB that have a MAX-ACCESS clause of read-write and/or
read-create. Such objects may be considered sensitive or
vulnerable in some network environments. The support for
SET operations in a non-secure environment without proper
protection can have a negative effect on network
operations.
There are a number of managed objects in this MIB that
may contain information that may be sensitive from a
business perspective, in that they represent a customer's
interface to the MPLS network. Allowing uncontrolled
access to these objects could result in malicious and
unwanted disruptions of network traffic or incorrect
configurations for these customers. There are no objects
that are particularly sensitive in their own right, such
as passwords or monetary amounts.
It is thus important to control even GET access to these END
objects and possibly to even encrypt the values of these
object when sending them over the network via SNMP. Not
all versions of SNMP provide features for such a secure
environment.
At this writing, no security holes have been identified 9. Security Considerations
beyond those that SNMP Security [RFC2571] is itself
intended to address. These relate to primarily
controlled access to sensitive information and the
ability to configure a device - or which might result
from operator error, which is beyond the scope of any
security architecture.
SNMPv1 or SNMPv2 are by themselves not a secure It is clear that the MIB modules described in this document in
environment. Even if the network itself is secure (for association with the MPLS-LSR-STD-MIB are potentially useful for
example by using IPSec [RFC2401]), there is no control as monitoring of GMPLS LSRs. These MIB modules can also be used for
to who on the secure network is allowed to access and configuration of certain objects, and anything that can be configured
GET/SET (read, change, create and/or delete) the objects can be incorrectly configured, with potentially disastrous results.
in this MIB. It is recommended that the implementers
consider the security features as provided by the SNMPv3
framework. Specifically, the use of the User-based
Security Model [RFC2574] and the View-based Access
Control [RFC2575] is recommended. It is then a
customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB is
properly configured to give access to the objects only to
those principals (users) that have legitimate rights to
indeed GET or SET (change/create/delete) them.
12. Acknowledgments 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
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
This draft is based heavily on [LSRMIB]. The authors o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable
would like to express their gratitude to all those who and gmplsLabelTable collectively contain objects to provision
worked on that earlier MIB. GMPLS interfaces, LSPs and their associated parameters on a Label
Switching Router (LSR). Unauthorized write access to objects in
these tables, could result in disruption of traffic on the
network. This is especially true if an LSP has already been
established. The use of stronger mechanisms such as SNMPv3
security should be considered where possible. Specifically, SNMPv3
VACM and USM MUST be used with any SNMPv3 agent which implements
these MIB modules.
The authors would like to express their thanks to Dan Some of the readable objects in these MIB modules "i.e., objects with
Joyle for his careful review and comments on GMPLS a MAX-ACCESS other than not-accessible" may be considered sensitive
labels. or vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
13. References o the gmplsInterfaceTable, gmplsInSegmentTable, gmplsOutSegmentTable
and gmplsLabelTable collectively show the LSP network topology and
its capabilities. If an Administrator does not want to reveal this
information, then these tables should be considered
sensitive/vulnerable.
13.1. Normative References SNMP versions prior to SNMPv3 did not include adequate security. 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
to access and GET/SET "read/change/create/delete" the objects in
these MIB modules. It is RECOMMENDED that implementers consider the
security features as provided by the SNMPv3 framework "see [RFC3410],
section 8", including full support for the SNMPv3 cryptographic
mechanisms "for authentication and privacy".
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and Further, deployment of SNMP versions prior to SNMPv3 is NOT
J. Davin, "Simple Network Management RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
Protocol", RFC 1157, May 1990. enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to
the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 10. Acknowledgments
Definitions", RFC 1212, March 1991.
[RFC2119] Bradner, S., "Key words for use in RFCs to This draft extends [LSRMIB]. The authors would like to express their
Indicate Requirement Levels", BCP 14, RFC gratitude to all those who worked on that earlier MIB document.
2119, March 1997.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, The authors would like to express their thanks to Dan Joyle for his
J., Case, J., Rose, M., and S. Waldbusser, careful review and comments on early versions of the Label Table.
"Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The 11. IANA Considerations
Interfaces Group MIB", RFC 2863, June 2000.
[RFC3032] Rosen, E., Rekhter, Y., Tappan, D., MPLS related standards track MIB modules are rooted under the
Farinacci, D., Federokow, G., Li, T., and mplsStdMIB subtree.
A. Conta, "MPLS Label Stack Encoding", RFC
3032, January 2001.
[RFC3036] Anderson, L., Doolan, P., Feldman, N., One of the MIB modules contained in this document extends tables
Fredette, A., and B. Thomas, "LDP contained in MPLS MIB modules.
Specification", RFC 3036, January 2001.
[RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T., As requested in requested in the GMPLS-TC-STD-MIB [GMPLSTCMIB] the
Srinivasan, V., and G. Swallow, "RSVP-TE: two MIB modules contained in this document should be placed in the
Extensions to RSVP for LSP Tunnels", draft- mplsStdMIB subtree as well.
ietf-mpls-rsvp-lsp-tunnel-08.txt, February
2001, work in progress.
[CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, New assignments can only be made via a Standards Action as specified
L., Ashwood-Smith, P., Hellstrand, F., in [RFC2434].
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", draft-ietf-mpls-
cr-ldp-05.txt, February 2001, work in
progress."
[GMPLSArch] Ashwood-Smith, P., Awduche, D., Banerjee, 11.1. IANA Considerations for GMPLS-LSR-STD-MIB
A., Basak, D, Berger, L., Bernstein, G.,
Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
Kompella, K., Kullberg, A., Lang, J., Liaw,
F., Papadimitriou, D., Pendarakis, D.,
Rajagopalan, B., Rekhter, Y., Saha, D.,
Sandick, H., Sharma, V., Swallow, G., Tang,
Z., Yu, J., Zinin, A., Nadeau, T., Mannie,
E., Generalized Multiprotocol Label
Switching (GMPLS) Architecture, Internet
Draft <draft-many-gmpls-architecture-
01.txt>, March 2001, work in progress.
[GMPLSSig] Ashwood-Smith, P., Awduche, D., Banerjee, The IANA is requested to assign { mplsStdMIB xx } to the
A., Basak, D, Berger, L., Bernstein, G., GMPLS-LSR-STD-MIB module specified in this document.
Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
Kompella, K., Kullberg, A., Lang,
Rajagopalan, B., Rekhter, Y., Saha, D.,
Sharma, V., Swallow, G., Bo Tang, Z.,
Generalized MPLS - Signaling Functional
Description, <draft-ietf-mpls-generalized-
signaling-04.txt>, May 2001, work in
progress.
[GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee, 11.2. IANA Considerations for GMPLS-LABEL-STD-MIB
A., Basak, D, Berger, L., Bernstein, G.,
Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
Kompella, K., Kullberg, A., Lang,
Rajagopalan, B., Rekhter, Y., Saha, D.,
Sharma, V., Swallow, G., Bo Tang, Z.,
Generalized MPLS Signaling - CR-LDP
Extensions, Internet Draft <draft-ietf-mpls-
generalized-cr-ldp-03.txt>, May 2001, work
in progress.
[GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee, The IANA is requested to assign { mplsStdMIB xx } to the
A., Basak, D, Berger, L., Bernstein, G., GMPLS-LABEL-STD-MIB module specified in this document.
Drake, J., Fan, Y., Fedyk, D., Grammel, D.,
Kompella, K., Kullberg, A., Lang,
Rajagopalan, B., Rekhter, Y., Saha, D.,
Sharma, V., Swallow, G., Bo Tang, Z.,
Generalized MPLS Signaling - RSVP-TE
Extensions, Internet Draft <draft-ietf-mpls-
generalized-rsvp-te-03.txt>, May 2001, work
in progress.
[GMPLSSonetSDH] Mannie, E., Ansorge, S., Ashwood-Smith, 12. References
P., Banerjee, A., Berger, L., Bernstein,
G., Chiu, A., Drake, J., Fan, Y., Fontana,
M., Grammel, G., Heiles, J., Katukam, S.,
Kompella, K., Lang, J. P., Liaw, F., Lin,
Z., Mack-Crane, B., Papadimitriou, D.,
Pendarakis, D., Raftelis, M., Rajagopalan,
B., Rekhter, Y., Saha, D., Sharma, V.,
Swallow, G., Bo Tang, Z., Varma, E.,
Vissers, M., Xu, Y., GMPLS Extensions for
SONET and SDH Control, Internet Draft
<draft-ietf-ccamp-gmpls-sonet-sdh-00.txt>,
May 2001, work in progress.
[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, 12.1. Normative References
Viswanathan, A. and H. Sjostrand,
"Definition of Textual Conventions and
OBJECT-IDENTITIES for Multiprotocol Label
Switching (MPLS) Management", Internet
Draft <draft-ietf-mpls-tc-mib-03.txt>,
January 2002, work in progress.
[LSRMIB] Srinivasan, C., Viswanathan, A. and T. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Nadeau, "MPLS Label Switching Router Requirement Levels", BCP 14, RFC 2119, March 1997.
Management Information Base Using SMIv2",
Internet Draft <draft-ietf-mpls-lsr-mib-
08.txt>, January 2002, work in progress.
[GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Hall, T., and Harrison, E., "Generalized Case, J., Rose, M., and S. Waldbusser, "Structure
Multiprotocol Label Switching (GMPLS) of Management Information Version 2 (SMIv2)", STD
Traffic 58, RFC 2578, April 1999.
Engineering Management Information Base",
draft-ietf-ccamp-gmpls-te-mib-00.txt, June
2002, work in progress.
[GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Hall, T., and Harrison, E., " Definition of Case, J., Rose, M., and S. Waldbusser, "Textual
Textual Conventions and OBJECT-IDENTITIES Conventions for SMIv2", STD 58, RFC 2579, April
for Generalized Multiprotocol Label 1999.
Switching (GMPLS) Management", draft-ietf-
ccamp-gmpls-te-mib-00.txt, June 2002, work
in progress.
13.2. Informational References [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April
1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces
Identification of Management Information Group MIB", RFC 2863, June 2000.
for TCP/IP-based Internets", RFC 1155, May
1990.
[RFC1215] M. Rose, "A Convention for Defining Traps [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol
for use with the SNMP", RFC 1215, March Label Switching (GMPLS) Signaling Functional
1991. Descriptionö, RFC 3471, January 2003.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. [RFC3472] Ashwood-Smith, P., Berger, L. (Editors),
Waldbusser, "Introduction to Community- "Generalized MPLS Signaling - CR-LDP Extensions",
based SNMPv2", RFC 1901, January 1996. RFC 3472, January 2003.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
Waldbusser, "Protocol Operations for RSVP-TE Extensions", RFC 3473 January 2003.
Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol
Waldbusser, "Transport Mappings for Version Label Switching (GMPLS) Architecture", Internet
2 of the Simple Network Management Protocol Draft <draft-many-gmpls-architecture-07.txt>, May
(SNMPv2)", RFC 1906, January 1996. 2003, work in progress.
[RFC2514] Noto, et. al., "Definitions of Textual [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors),
Conventions and OBJECT-IDENTITIES for ATM "Generalized Multi-Protocol Label Switching
Management", RFC 2514, Feb. 1999 Extensions for SONET and SDH Control", Internet
Draft <draft-ietf-ccamp-gmpls-sonet-sdh-08.txt>,
February 2003, work in progress.
[RFC2515] K. Tesink, "Definitions of Managed Objects [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of
for ATM Management", RFC 2515, Feb. 1999 Textual Conventions for Multiprotocol Label
Switching (MPLS) Management", Internet Draft
<draft-ietf-mpls-tc-mib-09.txt>, August 2003, work
in progress.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau,
Stewart, "Introduction to Version 3 of the "Multiprotocol Label Switching (MPLS) Label
Internet-standard Network Management Switching Router (LSR) Management Information
Framework", RFC 2570, April 1999. Base", Internet Draft <draft-ietf-mpls-lsr-mib-
12.txt>, August 2003, work in progress.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
"An Architecture for Describing SNMP and Harrison, E., "Generalized Multiprotocol Label
Management Frameworks", RFC 2571, April Switching (GMPLS) Traffic Engineering Management
1999. Information Base", draft-ietf-ccamp-gmpls-te-mib-
01.txt, August 2003, work in progress.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. [GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
Wijnen, "Message Processing and Dispatching and Harrison, E., "Definitions of Textual
for the Simple Network Management Protocol Conventions for Multiprotocol Label Switching
(SNMP)", RFC 2572, April 1999. (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib-
01.txt, August 2003, work in progress.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, 12.2. Informational References
"SNMPv3 Applications", RFC 2573, April
1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based [RFC2026] S. Bradner, "The Internet Standards Process --
Security Model (USM) for version 3 of the Revision 3", RFC 2026, October 1996.
Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP
"View-based Access Control Model (VACM) for Applications", RFC 3413, December 2002.
the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
J., Case, J., Rose, M., and S. Waldbusser, "Introduction and Applicability Statements for
"Structure of Management Information Internet-Standard Management Framework", RFC 3410,
Version 2 (SMIv2)", STD 58, RFC 2578, April December 2002.
1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
J., Case, J., Rose, M., and S. Waldbusser, Architecture for Describing Simple Network
"Conformance Statements for SMIv2", STD 58, Management Protocol (SNMP) Management Frameworks",
RFC 2580, April 1999. RFC 3411, December 2002.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching "Multiprotocol Label Switching Architecture", RFC
Architecture", RFC 3031, January 2001. 3031, January 2001.
[RFC3034] Conta, A., Doolan, P., Malis, A., "Use of
Label Switching on Frame Relay Networks
Specification", RFC 3034, January 2001.
[RFC3035] Davie, B., Lawrence, J., McCloghrie, K., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T.,
Rosen, E., Swallow, G., Rekhter, Y., and P. Srinivasan, V., and G. Swallow, "RSVP-TE:
Doolan, "MPLS using LDP and ATM VC Extensions to RSVP for LSP Tunnels", RFC 3209,
switching", RFC 3035, January 2001. December 2001.
[IANAFamily] Internet Assigned Numbers Authority (IANA), [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L.,
ADDRESS FAMILY NUMBERS. 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."
[TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A.,
"Multiprotocol Label Switching (MPLS) "Multiprotocol Label Switching (MPLS) Traffic
Traffic Engineering Management Information Engineering Management Information Base", Internet
Base", Internet Draft <draft-ietf-mpls-te- Draft <draft-ietf-mpls-te-mib-12.txt>, August 2003,
mib-08.txt>, January 2002, work in work in progress.
progress.
14. Authors' Addresses 13. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P.
Parama Networks, Inc. 499 Park Ave.,
1030 Broad Street New York, NY 10022
Shrewsbury, NJ 07702 Phone: +1-212-893-3682
Phone: +1-732-544-9120 x731 Email: cheenu@bloomberg.net
Email: cheenu@paramanet.com
Adrian Farrel Adrian Farrel
Movaz Networks, Inc. Old Dog Consulting
7926 Jones Branch Drive, Suite 615 Phone: +44-(0)-1978-860944
McLean VA, 22102 USA Email: adrian@olddog.co.uk
Phone: +1-703-847-9847
Email: afarrel@movaz.com
Tim Hall Tim Hall
Data Connection Ltd. Data Connection Ltd.
100 Church Street 100 Church Street
Enfield, Middlesex Enfield, Middlesex
EN2 6BQ, UK EN2 6BQ, UK
Phone: +44 20 8366 1177 Phone: +44 20 8366 1177
Email: timhall@dataconnection.com Email: timhall@dataconnection.com
Ed Harrison
Edward Harrison
Data Connection Ltd. Data Connection Ltd.
100 Church Street 100 Church Street
Enfield, Middlesex Enfield, Middlesex
EN2 6BQ, UK EN2 6BQ, UK
Phone: +44 20 8366 1177 Phone: +44 20 8366 1177
Email: eph@dataconnection.com Email: ed.harrison@dataconnection.com
15. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights
Reserved.
This document and translations of it may be copied and Copyright (C) The Internet Society (2003). All Rights Reserved.
furnished to others, and derivative works that comment on
or otherwise explain it or assist in its implementation
may be prepared, copied, published and distributed, in
whole or in part, without restriction of any kind,
provided that the above copyright notice and this
paragraph are included on all such copies and derivative
works. However, this document itself may not be modified
in any way, such as by removing the copyright notice or
references to the Internet Society or other Internet
organizations, except as needed for the purpose of
developing Internet standards in which case the
procedures for copyrights defined in the Internet
Standards process must be followed, or as required to
translate it into languages other than English.
The limited permissions granted above are perpetual and This document and translations of it may be copied and furnished to
will not be revoked by the Internet Society or its others, and derivative works that comment on or otherwise explain it
successors or assigns. This document and the information or assist in its implementation may be prepared, copied, published
contained herein is provided on an "AS IS" basis and THE and distributed, in whole or in part, without restriction of any
INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE kind, provided that the above copyright notice and this paragraph
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING are included on all such copies and derivative works. However, this
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE document itself may not be modified in any way, such as by removing
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY the copyright notice or references to the Internet Society or other
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A Internet organizations, except as needed for the purpose of
PARTICULAR PURPOSE. developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. This
document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
15. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11 [RFC2028].
Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
16. Changes and Pending Work
This section must be removed before the draft progresses to RFC.
16.1. Pending Work
The following work items have been identified for this draft. They
will be addressed in a future version.
- Expand conformance statements to give one for monitoring only,
and one for monitoring and control.
- Extend mplsTrafficParamsTable from the MPLS-LSR-MIB to support
GMPLS traffic parameters for signaled and static LSPs.
- Provide support for monitoring tunnel resources in GMPLS systems.
For example, SONET/SDH or G.709. This might be done through an
arbitrary RowPointer to an external MIB.
- Extend the performance tables from the MPLS-LSR-MIB for
technology-specific GMPLS LSPs.
- Supply more and better examples, especially ones using the Label
Table.
- Provide a next index object to supply the next available
arbitrary index into the Label Table.
 End of changes. 

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