Network Working Group Thomas D. Nadeau
Internet Draft Cisco Systems, Inc.
Expires: December 2002
Cheenu Srinivasan
Parama Networks, Inc.
Adrian Farrel
Movaz Networks, Inc.
Tim Hall
Edward Harrison
Data Connection Ltd.
June 2002
Generalized Multiprotocol Label Switching (GMPLS)
Label Switch Router Management Information Base
draft-ietf-ccamp-gmpls-lsr-mib-00.txt
Status of this Memo
This document is an Internet-Draft and is in full
conformance with all provisions of Section 10 of RFC 2026
[RFC2026].
Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum
of six months and may be updated, replaced, or obsoleted
by other documents at any time. It is inappropriate to
use Internet- Drafts as reference material or to cite
them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
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
This memo defines a portion of the Management Information
Base (MIB) for use with network management protocols in
the Internet community. In particular, it describes
managed objects for Generalized Multiprotocol Label
CCAMP Working Group Expires December 2002 [Page 1]
Internet Draft GMPLS-LSR-MIB June 24, 2002
Switching (GMPLS) Label Switched Routers (LSRs).
Table of Contents
1. Changes and Pending Work 2
1.1. Changes Since the Last Version 2
1.2. Pending Work 3
2. Introduction 3
2.1. Migration Strategy 3
3. The SNMP Management Framework 4
4. Terminology 5
5. Feature List 5
6. Summary of LSR MIB 5
7. Bidirectional LSPs 5
8. Example of LSP Setup 6
9. GMPLS Label Switching Router MIB Definitions 7
10. GMPLS Label MIB Definitions 13
11. Security Considerations 22
12. Acknowledgments 23
13. References 23
13.1. Normative References 23
13.2. Informational References 25
14. Authors' Addresses 27
15. Full Copyright Statement 27
1. Changes and Pending Work
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.
CCAMP Working Group Expires December 2002 [Page 2]
Internet Draft GMPLS-LSR-MIB June 24, 2002
- 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
This memo defines a portion of the Management Information
Base (MIB) for use with network management protocols in
the Internet community. In particular, it describes
managed objects for Generalized Multiprotocol Label
Switching (GMPLS) [GMPLSArch] Label Switching Routers
(LSRs).
Comments should be made directly to the CCAMP mailing
list at ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be
interpreted as described in RFC 2119, reference
[RFC2119].
2.1. Migration Strategy
This MIB extends the Label Switching Router MIB defined
for use with MPLS [LSRMIB]. The only changes made are
additions for support of GMPLS or changes that are
necessary to support the increased complexity of a GMPLS
system.
The companion document modeling and managing GMPLS based
traffic engineering [GMPLSTEMIB] extends the MPLS TE MIB
[TEMIB] with the same intentions.
Textual conventions and OBJECT-IDENTIFIERS are defined in
[GMPLSTCMIB] which extends the set of textual conventions
CCAMP Working Group Expires December 2002 [Page 3]
Internet Draft GMPLS-LSR-MIB June 24, 2002
originally defined in [TCMIB].
3. The SNMP Management Framework
The SNMP Management Framework presently consists of five
major components:
- An overall architecture, described in RFC 2571
[RFC2571].
- Mechanisms for describing and naming objects and
events for the purpose of management. The first
version of this Structure of Management Information
(SMI) is called SMIv1 and described in STD 16, RFC
1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16,
RFC 1215 [RFC1215]. The second version, called SMIv2,
is described in STD 58, RFC 2578 [RFC2578], STD 58,
RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
- Message protocols for transferring management
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
information. The first set of protocol operations and
associated PDU formats is described in STD 15, RFC
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
2573 [RFC2573] and the view-based access control
mechanism described in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP
Management Framework can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information
store, termed the Management Information Base or MIB.
Objects in the MIB are defined using the mechanisms
defined in the SMI.
CCAMP Working Group Expires December 2002 [Page 4]
Internet Draft GMPLS-LSR-MIB June 24, 2002
This memo specifies a MIB module that is compliant to the
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
This document uses terminology from the document
describing the MPLS architecture [RFC3031].
A label switched path (LSP) is modeled as a connection
consisting of one or more incoming segments (in-segments)
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
The GMPLS Label Switching Router MIB is designed to
satisfy the following requirements and constraints in
addition to those addressed by the MPLS LSR MIB:
- The MIB supports both manually configured LSPs as well
as those configured via any GMPLS signaling protocol.
- The MIB supports the enabling and disabling of GMPLS
capability on MPLS capable interfaces of an LSR.
6. Summary of LSR MIB
The MIB tables in this draft are:
- The interface configuration table
(gmplsInterfaceConfTable), which extends
mplsInterfaceConfTable to enable the GMPLS protocol on
MPLS-capable interfaces.
CCAMP Working Group Expires December 2002 [Page 5]
Internet Draft GMPLS-LSR-MIB June 24, 2002
- The in-segment (gmplsInSegmentTable) and out-segment
(gmplsOutSegmentTable) tables extend
mplsInSegmentTable and mplsOutSegmentTable to
configuring GMPLS-specific parameters for LSP segments
at an LSR.
- The gmplsLabelTable extends mplsLabelTable and allows
Generalized Labels to be defined and managed in a
central location. Generalized Labels can be of
variable length and have distinct bit-by-bit
interpretations according to the use that is made of
them.
These tables are described in the subsequent sections.
7. Bidirectional LSPs
This MIB supports bidirectional LSPs as required for
GMPLS.
A single entry in the mplsXCIndex is shared by all of the
segments for the entire bidirectional LSP. This
facilitates a simple reference from [TEMIB] and
[GMPLSTEMIB], and makes fate-sharing more obvious.
It is, however, important that the direction of segments
is understood to avoid connecting all in-segments to all
out-segments. This is achieved by an object in each
segment that indicates the direction of the segment with
respect to data flow.
A segment that is marked as 'forward' carries data from
the 'head' of the LSP to the 'tail'. A segment marked as
'reverse' carries data in the reverse direction.
Where an LSP is signaled using a conventional signaling
protocol, the 'head' of the LSP is the source of the
signaling (also known as the ingress) and the 'tail' is
the destination (also known as the egress). For manually
configured LSPs an arbitrary decision must be made about
which segments are 'forward' and which 'reverse'. For
consistency this decision should be made across all LSRs
that participate in the LSP by assigning 'head' and
'tail' ends to the LSP.
8. Example of LSP Setup
In this section we provide a brief example of using the
CCAMP Working Group Expires December 2002 [Page 6]
Internet Draft GMPLS-LSR-MIB June 24, 2002
MIB objects described in section 9. to set up an LSP.
While this example is not meant to illustrate every
nuance of the MIB, it is intended as an aid to
understanding some of the key concepts. It is meant to
be read after going through the MIB itself. A
prerequisite is an understanding of [LSRMIB].
Suppose that one would like to manually create a best-
effort, bi-directional LSP. Assume that, in the forward
direction, the LSP enters the LSR via MPLS interface A
with ifIndex 12 and exits the LSR via MPLS interface B
with ifIndex 13. For the reverse direction, we assume
the LSP enters via interface B and leaves via interface A
(i.e. the forward and reverse directions use the same bi-
directional interfaces). Let us also assume that we do
not wish to have a label stack beneath the top label on
the outgoing labeled packets. The following example
illustrates which rows and corresponding objects might be
created to accomplish this.
First, the traffic parameter entries must be set-up for
both segments. These are configured entirely in the MPLS
LSR MIB through the mplsTrafficParamTable.
Note that for a bi-directional LSP, the segments in the
reverse direction MAY share the traffic parameter entries
(and hence resources) with the segments in the forward
direction.
We must next create the appropriate in-segment and out-
segment entries with suitable traffic parameters by
pointing to the appropriate traffic parameter entries
that we have just created. This is also done in the MPLS
LSR MIB using mplsInSegmentTable and mplsOutSegmentTable.
These table entries are extended by entries in
gmplsInSegmentTable and gmplsOutSegmentTable. Note that
the nature of the 'extends' relationship is that the
entry in gmplsInSegmentTable has the same index values as
the entry in mplsInSegmentTable. Similarly, the entry in
gmplsOutSegmentTable has the same index values as the
entry in mplsOutSegmentTable.
First for the forward direction:
In gmplsInSegmentTable
{
gmplsInSegmentDirection = forward (1),
}
CCAMP Working Group Expires December 2002 [Page 7]
Internet Draft GMPLS-LSR-MIB June 24, 2002
In gmplsOutSegmentTable
{
gmplsOutSegmentDirection = forward (1)
}
Next for the reverse direction:
In gmplsInSegmentTable
{
gmplsInSegmentDirection = reverse (2)
}
In gmplsOutSegmentTable
{
gmplsOutSegmentDirection = reverse (2)
}
Next, two cross-connect entries are created in the
mplsXCTable of the MPLS LSR MIB, thereby associating the
newly created segments together.
9. GMPLS Label Switching Router MIB Definitions
GMPLS-LSR-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Unsigned32,
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
GmplsSegmentDirection
FROM GMPLS-TC-MIB
;
gmplsLsrMIB MODULE-IDENTITY
LAST-UPDATED
"200206240900Z " -- 24 June 2002 9:00:00 GMT"
ORGANIZATION "Common Control And Management Protocols
(CCAMP) Working Group"
CONTACT-INFO
" Thomas D. Nadeau
Postal: Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com
CCAMP Working Group Expires December 2002 [Page 8]
Internet Draft GMPLS-LSR-MIB June 24, 2002
Cheenu Srinivasan
Postal: Parama Networks, Inc.
1030 Broad Street
Shrewsbury, NJ 07702
Tel: +1-732-544-9120 x731
Email: cheenu@paramanet.com
Tel: +1-732-544-9120x731
Adrian Farrel
Postal: Movaz Networks, Inc.
7926 Jones Branch Drive
McLean, VA 22102
Tel: +1-703-847-1867
Email: afarrel@movaz.com
Edward Harrison
Postal: Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: eph@dataconnection.com
Tim Hall
Postal: Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: timhall@dataconnection.com
Email comments to the CCAMP WG Mailing List at
ccamp@ops.ietf.org."
DESCRIPTION
"This MIB contains managed object
definitions for the Generalized
Multiprotocol Label Switching (GMPLS)
Router."
-- Revision history.
REVISION
"200206240900Z" -- 24 June 2002 9:00:00 GMT
DESCRIPITION
"First revision draft version."
-- Above revision history to be replaced as below
-- REVISION "yyyymmddhhmmZ"
-- DESCRIPTION "Initial version, published as RFC xxxx"
-- xxxx to be assigned by RFC Editor
::= { experimental XXX } -- To Be Assigned by IANA
-- Tables, Scalars
gmplsLsrObjects OBJECT IDENTIFIER ::= { gmplsLsrMIB 1
CCAMP Working Group Expires December 2002 [Page 9]
Internet Draft GMPLS-LSR-MIB June 24, 2002
}
-- Notifications
-- Conformance
gmplsLsrConformance OBJECT IDENTIFIER ::= { gmplsLsrMIB 2
}
-- GMPLS Interface Configuration Table.
gmplsInterfaceConfTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInterfaceConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table specifies per-interface GMPLS
capability and associated information. It
extends the information in
mplsInterfaceConfTable."
::= { gmplsLsrObjects 1 }
gmplsInterfaceConfEntry OBJECT-TYPE
SYNTAX GmplsInterfaceConfEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created by an LSR
for every interface capable of supporting
GMPLS. Each entry in this table will exist
only if corresponding entries in
mplsInterfaceConfTable and ifTable exists.
If the associated entry in
mplsInterfaceConfTabel or ifTable is
deleted, the corresponding entry in this
table must also be deleted shortly
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 {
gmplsInterfaceConfSignalingCaps BITS
}
""gmplsInterfaceConfSignalingCaps OBJECT-TYPE
CCAMP Working Group Expires December 2002 [Page 10]
Internet Draft GMPLS-LSR-MIB June 24, 2002
SYNTAX BITS {
rsvp-gmpls (1),
crldp-gmpls (2),
other-gmpls (3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defines the signaling capabilities on this
interface. Multiple bits may legitimately
be set at once. Setting no bits implies
that GMPLS signaling cannot be performed on
this interface and all LSPs must be
manually provisioned."
::= { gmplsInterfaceConfEntry 1 }
-- End of gmplsInterfaceConfTable
-- In-segment table.
gmplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsInSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table extends the mplsInSegmentTable
to provide GMPLS-specific information about
incoming segments to an LSR."
::= { gmplsLsrObjects 2 }
gmplsInSegmentEntry OBJECT-TYPE
SYNTAX GmplsInSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table extends the
representation of an incoming segment
represented by an entry in
mplsInSegmentTable. An entry can be
created by a network administrator or an
SNMP agent, or a GMPLS signaling protocol.
"
INDEX { mplsInSegmentIndex }
::= { gmplsInSegmentTable 1 }
GmplsInSegmentEntry ::= SEQUENCE {
gmplsInSegmentDirection
GmplsSegmentDirection
}
CCAMP Working Group Expires December 2002 [Page 11]
Internet Draft GMPLS-LSR-MIB June 24, 2002
gmplsInSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirection
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the direction of
data flow on this segment."
DEFVAL { forward }
::= { gmplsInSegmentEntry 1 }
-- End of gmplsInSegmentTable
-- Out-segment table.
gmplsOutSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsOutSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table extends the mplsOutSegmentTable
to provide GMPLS-specific information about
outgoing segments from an LSR."
::= { gmplsLsrObjects 3 }
gmplsOutSegmentEntry OBJECT-TYPE
SYNTAX GmplsOutSegmentEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table extends the
representation of an outgoin segment
represented by an entry in
mplsOutSegmentTable. An entry can be
created by a network administrator or an
SNMP agent, or a GMPLS signaling protocol.
"
INDEX { mplsOutSegmentIndex }
::= { gmplsOutSegmentTable 1 }
GmplsOutSegmentEntry ::= SEQUENCE {
gmplsOutSegmentDirection
GmplsSegmentDirection,
gmplsOutSegmentTTLDecrement Unsigned32
}
"gmplsOutSegmentDirection OBJECT-TYPE
SYNTAX GmplsSegmentDirection
MAX-ACCESS read-create
CCAMP Working Group Expires December 2002 [Page 12]
Internet Draft GMPLS-LSR-MIB June 24, 2002
STATUS current
DESCRIPTION
"This variable indicates the direction of
data flow on this segment. This object
cannot be modified if
mplsOutSegmentRowStatus for the associated
entry in the mplsOutSegmentTavle is
active(1)."
DEFVAL { forward }
::= { gmplsOutSegmentEntry 1 }
gmplsOutSegmentTTLDecrement OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the amount by which
to decrement the TTL of any payload packets
forwarded on this segment if per-hop
decrementing is being done.
A value of zero indicates that no decrement
should be made or that per-hop decrementing
is not in force.
See the gmplsTunnelTTLDecrement object in
the gmplsTunnelTable of [GMPLSTEMIB] for a
value by which to decrement the TTL for the
whole of a tunnel.
This object cannot be modified if
mplsOutSegmentRowStatus for the associated
entry in the mplsOutSegmentTavle is
active(1)."
DEFVAL { 0 }
::= { gmplsOutSegmentEntry 2 }
-- End of gmplsOutSegmentTable
""
-- Module compliance.
gmplsLsrGroups
OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 }
gmplsLsrCompliances
OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 }
gmplsLsrModuleCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that
support the GMPLS LSR MIB."
CCAMP Working Group Expires December 2002 [Page 13]
Internet Draft GMPLS-LSR-MIB June 24, 2002
MODULE -- this module
-- The mandatory groups have to be implemented
-- by all LSRs that support GMPLS. However, they
-- may all be supported as read-only objects in
-- the case where manual configuration is unsupported.
MANDATORY-GROUPS {
gmplsInSegmentGroup,
gmplsOutSegmentGroup,
gmplsInterfaceGroup
}
"-- gmplsInSegmentTable
OBJECT gmplsInSegmentDirection
SYNTAX GmplsSegmentDirection
MIN-ACCESS read-only
DESCRIPTION
"Only forward(1) needs to be supported."
-- gmplsOutSegmentTable
OBJECT gmplsOutSegmentDirection
SYNTAX GmplsSegmentDirection
MIN-ACCESS read-only
DESCRIPTION
"Only forward(1) needs to be supported."
OBJECT gmplsOutSegmentTTLDecrement
SYNTAX Unsigned32 (0..255)
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { gmplsLsrCompliances 1 }
-- Units of conformance.
gmplsInterfaceGroup OBJECT-GROUP
OBJECTS {
gmplsInterfaceConfSignalingCaps
}
STATUS current
DESCRIPTION
"Collection of objects needed for GMPLS
interface configuration and performance
CCAMP Working Group Expires December 2002 [Page 14]
Internet Draft GMPLS-LSR-MIB June 24, 2002
information."
::= { gmplsLsrGroups 1 }
gmplsInSegmentGroup OBJECT-GROUP
OBJECTS {
gmplsInSegmentDirection
}
STATUS current
DESCRIPTION
"Collection of objects needed to implement a
GMPLS in-segment."
::= { gmplsLsrGroups 2 }
gmplsOutSegmentGroup OBJECT-GROUP
OBJECTS {
gmplsOutSegmentDirection,
gmplsOutSegmentTTLDecrement
}
STATUS current
DESCRIPTION
"Collection of objects needed to implement a
GMPLS out-segment."
::= { gmplsLsrGroups 3 }
END
10. GMPLS Label MIB Definitions
GMPLS-LABEL-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
GmplsGeneralizedLabelTypes,
GmplsGeneralizedLabelSubtypes,
GmplsFreeformLabel
FROM GMPLS-TC-MIB
;
gmplsLabelMIB MODULE-IDENTITY
LAST-UPDATED
"200206240900Z " -- 24 June 2002 9:00:00"
ORGANIZATION
"Common Control And Management Protocols (CCAMP)
Working Group"
CCAMP Working Group Expires December 2002 [Page 15]
Internet Draft GMPLS-LSR-MIB June 24, 2002
CONTACT-INFO
" Thomas D. Nadeau
Postal: Cisco Systems, Inc.
250 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com
Cheenu Srinivasan
Postal: Parama Networks, Inc.
1030 Broad Street
Shrewsbury, NJ 07702
Tel: +1-732-544-9120 x731
Email: cheenu@paramanet.comTel: +1-732-544-9120x731
Adrian Farrel
Postal: Movaz Networks, Inc.
7926 Jones Branch Drive
McLean, VA 22102
Tel: +1-703-847-1867
Email: afarrel@movaz.com
Edward Harrison
Postal: Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: eph@dataconnection.com
Tim Hall
Postal: Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, United Kingdom
Tel: +44-20-8366-1177
Email: timhall@dataconnection.com"
DESCRIPTION
"This MIB module contains managed object
definitions for labels within GMPLS
systems."
-- Revision history.
REVISION
"200206240900Z " -- 24 June 2002 9:00:00
GMT"
DESCRIPTION
"Initial version."
-- Above revision history to be replaced as below
CCAMP Working Group Expires December 2002 [Page 16]
Internet Draft GMPLS-LSR-MIB June 24, 2002
-- 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.
-- tables, scalars
gmplsLabelObjects OBJECT IDENTIFIER ::= {
gmplsLabelMIB 0 }
gmplsLabelConformance OBJECT IDENTIFIER ::= {
gmplsLabelMIB 1 }
-- GMPLS Label Table.
gmplsLabelTable OBJECT-TYPE
SYNTAX SEQUENCE OF GmplsLabelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of GMPLS Labels. This table extends
mplsLabelTable to handle the more complex
label forms required for GMPLS.
Each entry in this table represents an
individual GMPLS label value. Labels in
the tables in other MIBs are referred to
using index entries into mplsLabelTable.
The indexing of this table is identical.
In effect, this table taken together with
mplsLabelTable provides an integer mapping
for label values that may be more complex
than simple integers."
::= { gmplsLabelObjects 1 }
gmplsLabelEntry OBJECT-TYPE
SYNTAX GmplsLabelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table extends the label
defintion in mplsLabelTable for use with
certain types of switching appropriate to
GMPLS."
INDEX { mplsLabelInterface, mplsLabelIndex,
gmplsSublabelIndex }
::= { gmplsLabelTable 1 }
GmplsLabelEntry ::= SEQUENCE {
gmplsSublabelIndex Unsigned32,
gmplsLabelType GmplsGeneralizedLabelTypes,
CCAMP Working Group Expires December 2002 [Page 17]
Internet Draft GMPLS-LSR-MIB June 24, 2002
gmplsLabelSubtype GmplsGeneralizedLabelSubtypes,
gmplsPortWavelengthLabel Unsigned32,
gmplsFreeformLength INTEGER,
gmplsFreeformLabel GmplsFreeformLabel,
gmplsSonetSdhSignalIndex INTEGER,
gmplsSdhVc INTEGER,
gmplsSdhVcBranch INTEGER,
gmplsSonetSdhBranch INTEGER,
gmplsSonetSdhGroupBranch INTEGER,
gmplsWavebandId Unsigned32,
gmplsWavebandStartLabel Unsigned32,
gmplsWavebandEndLabel Unsigned32
}
gmplsSublabelIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"In conjunction with mplsLabelInterface and
mplsLabelIndex, 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
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 }
gmplsLabelType OBJECT-TYPE
SYNTAX GmplsGeneralizedLabelTypes
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Identifies the type of this label as it
appears in a Generalized Label. This
object has meaning only if the value of
mplsLabelType is other(1)."
::= { gmplsLabelEntry 2 }
gmplsLabelSubtype OBJECT-TYPE
SYNTAX GmplsGeneralizedLabelSubtypes
MAX-ACCESS read-create
STATUS current
CCAMP Working Group Expires December 2002 [Page 18]
Internet Draft GMPLS-LSR-MIB June 24, 2002
DESCRIPTION
"Subtype to help determine which of the
subsequent fields should be used to form
the Generalized Label."
::= { gmplsLabelEntry 3 }
gmplsPortWavelengthLabel OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of a Port or Wavelength Label
when carried as a Generalized Label. Only
valid if mplsLabelType is set to other(1),
gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to portWavelengthLabel(2)."
::= { gmplsLabelEntry 4 }
gmplsFreeformLength OBJECT-TYPE
SYNTAX INTEGER (1..64)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The length of a freeform Generalized Label
indicated in the gmplsFreeformLabel object.
Only valid if mplsLabelType is set to
other(1), gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to freeformGeneralizedLabel(3)."
::= { gmplsLabelEntry 5 }
gmplsFreeformLabel OBJECT-TYPE
SYNTAX GmplsFreeformLabel
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of a freeform Generalized Label
that does not conform to one of the
standardized label encoding or that an
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 }
CCAMP Working Group Expires December 2002 [Page 19]
Internet Draft GMPLS-LSR-MIB June 24, 2002
gmplsSonetSdhSignalIndex OBJECT-TYPE
SYNTAX INTEGER (0..4095)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Signal Index value (S) of a Sonet or
SDH Generalized Label. 0 indicates that
this field is non-significant. Only valid
if mplsLabelType is set to other(1),
gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to sonetLabel(4) or sdhLabel(5)."
::= { gmplsLabelEntry 7 }
gmplsSdhVc OBJECT-TYPE
SYNTAX INTEGER (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VC Indicator (U) of an SDH Generalized
Label. 0 indicates that this field is non-
significant. Only valid if mplsLabelType
is set to other(1), gmplsLabelType is set
to generalizedLabel(2), and
gmplsLabelSubtype is set to sdhLabel(5)."
::= { gmplsLabelEntry 8 }
gmplsSdhVcBranch OBJECT-TYPE
SYNTAX INTEGER (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VC Branch Indicator (K) of an SDH
Generalized Label. 0 indicates that this
field is non-significant. Only valid if
mplsLabelType is set to other(1),
gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to sdhLabel(5)."
::= { gmplsLabelEntry 9 }
gmplsSonetSdhBranch OBJECT-TYPE
SYNTAX INTEGER (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Branch Indicator (L) of a Sonet or SDH
Generalized Label. 0 indicates that this
field is non-significant. Only valid if
mplsLabelType is set to other(1),
CCAMP Working Group Expires December 2002 [Page 20]
Internet Draft GMPLS-LSR-MIB June 24, 2002
gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to sonetLabel(4) or SdhLabel(5)."
::= { gmplsLabelEntry 10 }
gmplsSonetSdhGroupBranch OBJECT-TYPE
SYNTAX INTEGER (0..15)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The Group Branch Indicator (M) of a Sonet
or SDH Generalized Label. 0 indicates that
this field is non-significant. Only valid
if mplsLabelType is set to other(1),
gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to sonetLabel(4) or sdhLabel(5)."
::= { gmplsLabelEntry 11 }
gmplsWavebandId OBJECT-TYPE
SYNTAX Uunsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The waveband identifier component of a
waveband label. Only valid if
mplsLabelType is set to other(1),
gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to wavebandLabel(6)."
::= { gmplsLabelEntry 12 }
gmplsWavebandStartLabel OBJECT-TYPE
SYNTAX Uunsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The starting label component of a waveband
label. Only valid if mplsLabelType is set
to other(1), gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to wavebandLabel(6)."
::= { gmplsLabelEntry 13 }
gmplsWavebandEndLabel OBJECT-TYPE
SYNTAX Uunsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The end label component of a waveband
CCAMP Working Group Expires December 2002 [Page 21]
Internet Draft GMPLS-LSR-MIB June 24, 2002
label. Only valid if mplsLabelType is set
to other(1), gmplsLabelType is set to
generalizedLabel(2), and gmplsLabelSubtype
is set to wavebandLabel(6)."
::= { gmplsLabelEntry 14 }
-- End of GMPLS Label Table
-- Module compliance.
gmplsLabelGroups
OBJECT IDENTIFIER ::= { gmplsLabelConformance 1 }
gmplsLabelCompliances
OBJECT IDENTIFIER ::= { gmplsLabelConformance 2 }
gmplsLabelModuleCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that
support the GMPLS Label MIB."
MODULE -- this module
-- The mandatory groups have to be implemented by
-- LSRs claiming support for this MIB. This MIB itself,
-- however, is mandatory only on LSRs supporting GMPLS
MANDATORY-GROUPS {
gmplsLabelTableGroup
}
-- Units of conformance.
GROUP gmplsLabelTableGroup
DESCRIPTION
"This group is mandatory for devices which
support the gmplsLabelTable."
GROUP gmplsPortWavelengthLabelGroup
DESCRIPTION
"This group extends gmplsLabelTableGroup for
implementations that support port and
wavelength labels."
GROUP gmplsFreeformLabelGroup
DESCRIPTION
"This group extends gmplsLabelTableGroup for
implementations that support freeform
labels."
CCAMP Working Group Expires December 2002 [Page 22]
Internet Draft GMPLS-LSR-MIB June 24, 2002
GROUP gmplsSonetSdhLabelGroup
DESCRIPTION
"This group extends gmplsLabelTableGroup for
implementations that support SonetSdh
labels."
GROUP gmplsWavebandLabelGroup
DESCRIPTION
"This group extends gmplsLabelTableGroup
for implementations that support
Waveband labels."
-- gmplsLabelTable
OBJECT gmplsLabelType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsLabelSubtype
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsPortWavelengthLabel
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsFreeformLength
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsFreeformLabel
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsSonetSdhSignalIndex
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsSdhVc
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
CCAMP Working Group Expires December 2002 [Page 23]
Internet Draft GMPLS-LSR-MIB June 24, 2002
OBJECT gmplsSdhVcBranch
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsSonetSdhBranch
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsSonetSdhGroupBranch
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsWavebandId
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsWavebandStartLabel
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT gmplsWavebandEndLabel
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { gmplsLabelCompliances 1 }
-- Units of conformance.
gmplsLabelTableGroup OBJECT-GROUP
OBJECTS {
gmplsLabelType,
gmplsLabelSubtype
}
STATUS current
DESCRIPTION
"Necessary, but not sufficient, set of
objects to implement label table support.
In addition, depending on the type of
labels supported (for example, wavelength
labels), the following other groups defined
below are mandatory:
gmplsPortWavelengthLabelGroup and/or
gmplsFreeformLabelGroup and/or
gmplsSonetSdhLabelGroup."
CCAMP Working Group Expires December 2002 [Page 24]
Internet Draft GMPLS-LSR-MIB June 24, 2002
::= { gmplsLabelGroups 1 }
gmplsPortWavelengthLabelGroup OBJECT-GROUP
OBJECTS {
gmplsPortWavelengthLabel
}
STATUS current
DESCRIPTION
"Object needed to implement Port and
Wavelength labels."
::= { gmplsLabelGroups 2 }
gmplsFreeformLabelGroup OBJECT-GROUP
OBJECTS {
gmplsFreeformLength,
gmplsFreeformLabel
}
STATUS current
DESCRIPTION
"Object needed to implement Freeform
labels."
::= { gmplsLabelGroups 3 }
gmplsSonetSdhLabelGroup OBJECT-GROUP
OBJECTS {
gmplsSonetSdhSignalIndex,
gmplsSdhVc,
gmplsSdhVcBranch,
gmplsSonetSdhBranch,
gmplsSonetuSdhGroupBranch
}
STATUS current
DESCRIPTION
"Object needed to implement SONET and SDH
labels."
::= { gmplsLabelGroups 4 }
gmplsWavebandLabelGroup OBJECT-GROUP
OBJECTS {
gmplsWavebandId,
gmplsWavebandStartLabel,
gmplsWavebandEndLabel
}
STATUS current
DESCRIPTION
"Object needed to implement Waveband
labels."
::= { gmplsLabelGroups 5 }
END
CCAMP Working Group Expires December 2002 [Page 25]
Internet Draft GMPLS-LSR-MIB June 24, 2002
11. Security Considerations
It is clear that this MIB is potentially useful for
monitoring of MPLS LSRs. This MIB can also be used for
configuration of certain objects, and anything that can
be configured can be incorrectly configured, with
potentially disastrous results.
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
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
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
environment. Even if the network itself is secure (for
example by using IPSec [RFC2401]), there is no control as
to who on the secure network is allowed to access and
GET/SET (read, change, create and/or delete) the objects
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
CCAMP Working Group Expires December 2002 [Page 26]
Internet Draft GMPLS-LSR-MIB June 24, 2002
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
This draft is based heavily on [LSRMIB]. The authors
would like to express their gratitude to all those who
worked on that earlier MIB.
The authors would like to express their thanks to Dan
Joyle for his careful review and comments on GMPLS
labels.
13. References
13.1. Normative References
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and
J. Davin, "Simple Network Management
Protocol", RFC 1157, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB
Definitions", RFC 1212, March 1991.
[RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, RFC
2119, March 1997.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser,
"Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholtz, "The
Interfaces Group MIB", RFC 2863, June 2000.
[RFC3032] Rosen, E., Rekhter, Y., Tappan, D.,
Farinacci, D., Federokow, G., Li, T., and
A. Conta, "MPLS Label Stack Encoding", RFC
3032, January 2001.
[RFC3036] Anderson, L., Doolan, P., Feldman, N.,
CCAMP Working Group Expires December 2002 [Page 27]
Internet Draft GMPLS-LSR-MIB June 24, 2002
Fredette, A., and B. Thomas, "LDP
Specification", RFC 3036, January 2001.
[RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T.,
Srinivasan, V., and G. Swallow, "RSVP-TE:
Extensions to RSVP for LSP Tunnels", draft-
ietf-mpls-rsvp-lsp-tunnel-08.txt, February
2001, work in progress.
[CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson,
L., 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", draft-ietf-mpls-
cr-ldp-05.txt, February 2001, work in
progress."
[GMPLSArch] Ashwood-Smith, P., Awduche, D., Banerjee,
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,
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 Functional
Description, <draft-ietf-mpls-generalized-
signaling-04.txt>, May 2001, work in
progress.
[GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee,
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.,
CCAMP Working Group Expires December 2002 [Page 28]
Internet Draft GMPLS-LSR-MIB June 24, 2002
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,
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 - 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,
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,
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.
Nadeau, "MPLS Label Switching Router
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.,
Hall, T., and Harrison, E., "Generalized
Multiprotocol Label Switching (GMPLS)
Traffic
Engineering Management Information Base",
draft-ietf-ccamp-gmpls-te-mib-00.txt, June
CCAMP Working Group Expires December 2002 [Page 29]
Internet Draft GMPLS-LSR-MIB June 24, 2002
2002, work in progress.
[GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A.,
Hall, T., and Harrison, E., " Definition of
Textual Conventions and OBJECT-IDENTITIES
for Generalized Multiprotocol Label
Switching (GMPLS) Management", draft-ietf-
ccamp-gmpls-te-mib-00.txt, June 2002, work
in progress.
13.2. Informational References
[RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information
for TCP/IP-based Internets", RFC 1155, May
1990.
[RFC1215] M. Rose, "A Convention for Defining Traps
for use with the SNMP", RFC 1215, March
1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-
based SNMPv2", RFC 1901, January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Protocol Operations for
Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Transport Mappings for Version
2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996.
[RFC2514] Noto, et. al., "Definitions of Textual
Conventions and OBJECT-IDENTITIES for ATM
Management", RFC 2514, Feb. 1999
[RFC2515] K. Tesink, "Definitions of Managed Objects
for ATM Management", RFC 2515, Feb. 1999
[RFC2570] Case, J., Mundy, R., Partain, D., and B.
Stewart, "Introduction to Version 3 of the
Internet-standard Network Management
Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen,
"An Architecture for Describing SNMP
CCAMP Working Group Expires December 2002 [Page 30]
Internet Draft GMPLS-LSR-MIB June 24, 2002
Management Frameworks", RFC 2571, April
1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B.
Wijnen, "Message Processing and Dispatching
for the Simple Network Management Protocol
(SNMP)", RFC 2572, April 1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart,
"SNMPv3 Applications", RFC 2573, April
1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based
Security Model (USM) for version 3 of the
Simple Network Management Protocol
(SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie,
"View-based Access Control Model (VACM) for
the Simple Network Management Protocol
(SNMP)", RFC 2575, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser,
"Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder,
J., Case, J., Rose, M., and S. Waldbusser,
"Conformance Statements for SMIv2", STD 58,
RFC 2580, April 1999.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching
Architecture", RFC 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.,
Rosen, E., Swallow, G., Rekhter, Y., and P.
Doolan, "MPLS using LDP and ATM VC
switching", RFC 3035, January 2001.
[IANAFamily] Internet Assigned Numbers Authority (IANA),
ADDRESS FAMILY NUMBERS.
[TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A.,
CCAMP Working Group Expires December 2002 [Page 31]
Internet Draft GMPLS-LSR-MIB June 24, 2002
"Multiprotocol Label Switching (MPLS)
Traffic Engineering Management Information
Base", Internet Draft <draft-ietf-mpls-te-
mib-08.txt>, January 2002, work in
progress.
14. Authors' Addresses
Thomas D. Nadeau
Cisco Systems, Inc.
300 Apollo Drive
Chelmsford, MA 01824
Phone: +1-978-244-3051
Email: tnadeau@cisco.com
Cheenu Srinivasan
Parama Networks, Inc.
1030 Broad Street
Shrewsbury, NJ 07702
Phone: +1-732-544-9120 x731
Email: cheenu@paramanet.com
Adrian Farrel
Movaz Networks, Inc.
7926 Jones Branch Drive, Suite 615
McLean VA, 22102 USA
Phone: +1-703-847-9847
Email: afarrel@movaz.com
Tim Hall
Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, UK
Phone: +44 20 8366 1177
Email: timhall@dataconnection.com
Edward Harrison
Data Connection Ltd.
100 Church Street
Enfield, Middlesex
EN2 6BQ, UK
Phone: +44 20 8366 1177
Email: eph@dataconnection.com
15. Full Copyright Statement
CCAMP Working Group Expires December 2002 [Page 32]
Internet Draft GMPLS-LSR-MIB June 24, 2002
Copyright (C) The Internet Society (2002). All Rights
Reserved.
This document and translations of it may be copied and
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
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.
CCAMP Working Group Expires December 2002 [Page 33]
