draft-ietf-mpls-lsr-mib-14.txt   rfc3813.txt 
Network Working Group Cheenu Srinivasan Network Working Group C. Srinivasan
Internet Draft Bloomberg L.P. Request for Comments: 3813 Bloomberg L.P.
Expires: May 2004 Category: Standard Track A. Viswanathan
Arun Viswanathan Force10 Networks, Inc.
Force10 Networks, Inc. T. Nadeau
Cisco Systems, Inc.
Thomas D. Nadeau June 2004
Cisco Systems, Inc.
November 2003
Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base
draft-ietf-mpls-lsr-mib-14.txt Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base (MIB)
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC 2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the In ternet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that and status of this protocol. Distribution of this memo is unlimited.
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 Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2004).
http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines an portion of the Management This memo defines an portion of the Management Information Base (MIB)
Information Base (MIB) for use with network management protocols for use with network management protocols in the Internet community.
in the Internet community. In particular, it describes managed In particular, it describes managed objects to configure and/or
objects to configure and/or monitor a Multi-Protocol Label monitor a Multiprotocol Label Switching (MPLS) Label Switching Router
Switching (MPLS) Label Switching Router (LSR). (LSR).
Table of Contents Table of Contents
Abstract .................................................1 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
1. Introduction .............................................2 2. Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology ..............................................2 3. The SNMP Management Framework. . . . . . . . . . . . . . . . . 3
3. The SNMP Management Framework ............................3 4. Outline. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Outline ..................................................3 4.1. Summary of LSR MIB Module. . . . . . . . . . . . . . . . 4
4.1 Summary of LSR MIB Module ................................3 5. Brief Description of MIB Module Objects. . . . . . . . . . . . 4
5. Brief Description of MIB Module Objects ..................4 5.1. mplsInterfaceTable . . . . . . . . . . . . . . . . . . . 4
5.1. mplsInterfaceTable .......................................4 5.2. mplsInterfacePerfTable . . . . . . . . . . . . . . . . . 4
5.2. mplsInterfacePerfTable ...................................4 5.3. mplsInSegmentTable . . . . . . . . . . . . . . . . . . . 5
5.3. mplsInSegmentTable .......................................4 5.4. mplsInSegmentPerfTable . . . . . . . . . . . . . . . . . 5
5.4. mplsInSegmentPerfTable ...................................5 5.5. mplsOutSegmentTable. . . . . . . . . . . . . . . . . . . 5
5.5. mplsOutSegmentTable ......................................5 5.6. mplsOutSegmentPerfTable. . . . . . . . . . . . . . . . . 5
5.6. mplsOutSegmentPerfTable ..................................5 5.7. mplsXCTable. . . . . . . . . . . . . . . . . . . . . . . 5
5.7. mplsXCTable ..............................................5 5.8. mplsLabelStackTable. . . . . . . . . . . . . . . . . . . 6
5.8. mplsLabelStackTable ......................................6 5.9. mplsInSegmentMapTable. . . . . . . . . . . . . . . . . . 6
5.9 mplsInSegmentMapTable ....................................6 6. Use of 32-bit and 64-bit Counters. . . . . . . . . . . . . . . 6
6. Use of 32-bit and 64-bit Counters ........................6 7. Example of LSP Setup . . . . . . . . . . . . . . . . . . . . . 6
7. Example of LSP Setup .....................................6 8. Application of the Interface Group to MPLS . . . . . . . . . . 8
8. Application of the Interface Group to MPLS ...............8 8.1. Support of the MPLS Layer by ifTable . . . . . . . . . . 9
8.1. Support of the MPLS Layer by ifTable .....................8 9. The Use of RowPointer. . . . . . . . . . . . . . . . . . . . . 10
9. The Use of RowPointer ....................................10 10. MPLS Label Switching Router MIB Module Definitions . . . . . . 11
10. MPLS Label Switching Router MIB Module Definitions .......10 11. Security Considerations. . . . . . . . . . . . . . . . . . . . 55
11. Security Considerations ..................................52 12. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 56
12. Acknowledgments ..........................................54 13. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 56
13. IANA Considerations ......................................54 13.1. IANA Considerations for MPLS-LSR-STD-MIB . . . . . . . . 56
13.1. IANA Considerations for MPLS-LSR-STD-MIB ................54 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57
14. References ...............................................54 14.1. Normative References . . . . . . . . . . . . . . . . . . 57
14.1. Normative References ....................................54 14.2. Informative References . . . . . . . . . . . . . . . . . 58
14.2. Informative References ..................................55 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 59
15. Authors' Addresses .........................................56 16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 60
16. Full Copyright Statement ...................................56
17. Intellectual Property Notice ...............................57
1. Introduction 1. Introduction
This memo defines an portion of the Management This memo defines an portion of the Management Information Base (MIB)
Information Base (MIB) for use with network management protocols for use with network management protocols in the Internet community.
in the Internet community. In particular, it describes managed In particular, it describes managed objects for modeling a
objects for modeling a Multi-Protocol Label Switching (MPLS) Multiprotocol Label Switching (MPLS) [RFC3031] Label Switching Router
[RFC3031] Label Switching Router (LSR). (LSR).
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list at
mpls@uu.net. mpls@uu.net.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
"OPTIONAL" in this document are to be interpreted as described in document are to be interpreted as described in BCP 14, RFC 2119,
RFC 2119, reference [RFC2119]. reference [RFC2119].
2. Terminology 2. Terminology
This document uses terminology from the document describing the This document uses terminology from the document describing the MPLS
MPLS architecture [RFC3031]. A label switched path (LSP) is architecture [RFC3031]. A label switched path (LSP) is modeled as a
modeled as a connection consisting of one or more incoming connection consisting of one or more incoming segments (in-segments)
segments (in-segments) and/or one or more outgoing segments (out- and/or one or more outgoing segments (out-segments) at a LSR. The
segments) at a LSR. The association or interconnection association or interconnection of the in-segments and out-segments is
of the in-segments and out-segments is accomplished by accomplished by using a cross-connect. We use the terminology
using a cross-connect. We use the terminology
"connection" and "LSP" interchangeably where the meaning is clear "connection" and "LSP" interchangeably where the meaning is clear
from the context. from the context.
in-segment This is analagous to an MPLS label. in-segment This is analogous to an MPLS label.
out-segment This is analagous to an MPLS label. out-segment This is analogous to an MPLS label.
cross-connect This describes the conceptual connection cross-connect This describes the conceptual connection
between a set of in-segments and out-segments. between a set of in-segments and out-segments.
Note that either set may be 0; that is, a Note that either set may be 0; that is, a
cross-connect may connect only out-segments cross-connect may connect only out-segments
together with no in-segments in the case together with no in-segments in the case
where an LSP is originating on an LSR. where an LSP is originating on an LSR.
3. The SNMP Management Framework 3. The SNMP Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. Outline 4. Outline
Configuring LSPs through an LSR involves the following steps: Configuring LSPs through an LSR involves the following steps:
- Enabling MPLS on MPLS capable interfaces. - Enabling MPLS on MPLS capable interfaces.
- Configuring in-segments and out-segments. - Configuring in-segments and out-segments.
- Setting up the cross-connect table to associate segments and/or - Setting up the cross-connect table to associate segments and/or to
to indicate connection origination and termination. indicate connection origination and termination.
- Optionally specifying label stack actions. - Optionally specifying label stack actions.
- Optionally specifying segment traffic parameters. - Optionally specifying segment traffic parameters.
4.1. Summary of LSR MIB Module 4.1. Summary of LSR MIB Module
The MIB objects for performing these actions consist of the The MIB objects for performing these actions consist of the following
following tables: tables:
- The interface table (mplsInterfaceTable), - The interface table (mplsInterfaceTable), which is used for
which is used for revealing the MPLS protocol on revealing the MPLS protocol on MPLS-capable interfaces.
MPLS-capable interfaces.
- The in-segment (mplsInSegmentTable) and out-segment - The in-segment (mplsInSegmentTable) and out-segment
(mplsOutSegmentTable) tables, which are used for configuring (mplsOutSegmentTable) tables, which are used for configuring LSP
LSP segments at an LSR. segments at an LSR.
- The cross-connect table (mplsXCTable), which is used to - The cross-connect table (mplsXCTable), which is used to associate
associate in and out segments together, in order to form a in and out segments together, in order to form a cross-connect.
cross-connect.
- The label stack table (mplsLabelStackTable), which is used for - The label stack table (mplsLabelStackTable), which is used for
specifying label stack operations. specifying label stack operations.
Further, the MPLS in-segment and out-segment performance tables, Further, the MPLS in-segment and out-segment performance tables,
mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the
objects necessary to measure the performance of LSPs, and objects necessary to measure the performance of LSPs, and
mplsInterfacePerfTable has objects to measure MPLS performance on mplsInterfacePerfTable has objects to measure MPLS performance on a
a per-interface basis. per-interface basis.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
5. Brief Description of MIB Module Objects 5. Brief Description of MIB Module Objects
Sections 5.1-5.2 describe objects pertaining to MPLS-capable Sections 5.1-5.2 describe objects pertaining to MPLS-capable
interfaces of an LSR. The objects described in Sections 5.3-5.8, interfaces of an LSR. The objects described in Sections 5.3-5.8,
were derived from the Incoming Label Map (ILM) and Next Hop Label were derived from the Incoming Label Map (ILM) and Next Hop Label
Forwarding Entry (NHLFE) as specified in the MPLS architecture Forwarding Entry (NHLFE) as specified in the MPLS architecture
document [RFC3031]. It is appropriate to note that the in-segment, document [RFC3031]. It is appropriate to note that the in-segment,
out-segment, and cross-connect tables were modeled after similar out-segment, and cross-connect tables were modeled after similar
tables found in [RFC2515]. tables found in [RFC2515].
5.1. mplsInterfaceTable 5.1. mplsInterfaceTable
This table represents the interfaces that are MPLS capable. An This table represents the interfaces that are MPLS capable. An LSR
LSR creates an entry in this table for every MPLS capable creates an entry in this table for every MPLS capable interface on
interface on that LSR. that LSR.
5.2. mplsInterfacePerfTable 5.2. mplsInterfacePerfTable
This table contains objects to measure the MPLS performance of This table contains objects to measure the MPLS performance of MPLS
MPLS capable interfaces and is an AUGMENT to capable interfaces and is an AUGMENT to mplsInterfaceTable.
mplsInterfaceTable.
5.3. mplsInSegmentTable 5.3. mplsInSegmentTable
This table contains a description of the incoming MPLS segments This table contains a description of the incoming MPLS segments to an
to an LSR and their associated parameters. This index for this LSR and their associated parameters. This index for this table is
table is mplsInSegmentIndex. The index structure of this mplsInSegmentIndex. The index structure of this table is
table is specifically designed to handle many different specifically designed to handle many different MPLS implementations
MPLS implementations that manage their labels both in a that manage their labels both in a distributed and centralized
distributed and centralized manner. manner.
The table is designed to handle existing MPLS labels as The table is designed to handle existing MPLS labels as well as
well as future label strategies that may require labels future label strategies that may require labels longer than the ones
longer than the ones defined in RFC3031. In these cases, defined in RFC3031. In these cases, the object mplsInSegmentLabelPtr
the object mplsInSegmentLabelPtr may be used indicate may be used indicate the first accessible object in a separate table
the first accessible object in a separate table that can be that can be used to represent the label because it is too long to be
used to represent the label because it is too long to represented in a single 32-bit value (mplsInSegmentLabel).
be represented in a single 32-bit value (mplsInSegmentLabel).
5.4. mplsInSegmentPerfTable 5.4. mplsInSegmentPerfTable
The MPLS in-Segment Performance Table has objects to measure The MPLS in-Segment Performance Table has objects to measure the
the performance of an incoming segment configured on an LSR. It performance of an incoming segment configured on an LSR. It is an
is an AUGMENT to mplsInSegmentTable. High capacity counters are AUGMENT to mplsInSegmentTable. High capacity counters are provided
provided for objects that are likely to wrap around quickly on for objects that are likely to wrap around quickly on high-speed
high-speed interfaces. interfaces.
5.5. mplsOutSegmentTable 5.5. mplsOutSegmentTable
The out-Segment Table contains a description of the outgoing MPLS The out-Segment Table contains a description of the outgoing MPLS
segments at an LSR and their associated parameters. segments at an LSR and their associated parameters.
5.6. mplsOutSegmentPerfTable 5.6. mplsOutSegmentPerfTable
The MPLS out-Segment Table contains objects to measure the The MPLS out-Segment Table contains objects to measure the
performance of an outgoing segment configured on an LSR. It is performance of an outgoing segment configured on an LSR. It is an
an AUGMENT to mplsOutSegmentTable. High capacity counters are AUGMENT to mplsOutSegmentTable. High capacity counters are provided
provided for objects that are likely to wrap around quickly on for objects that are likely to wrap around quickly on high-speed
high-speed interfaces. interfaces.
5.7. mplsXCTable 5.7. mplsXCTable
The mplsXCTable specifies information for associating segments The mplsXCTable specifies information for associating segments
together in order to instruct the LSR to switch between the together in order to instruct the LSR to switch between the specified
specified segments. It supports point-to-point, point-to-multi- segments. It supports point-to-point, point-to-multipoint and
point and multi-point-to-point connections. multipoint-to-point connections.
The operational status object indicates the packet forwarding The operational status object indicates the packet forwarding state
state of a cross-connect entry. For example, when the operational of a cross-connect entry. For example, when the operational status
status objects is 'down' it indicates that the specified cross- objects is 'down' it indicates that the specified cross-connect entry
connect entry will not forward packets. Likewise, when it is set will not forward packets. Likewise, when it is set to 'up' it
to 'up' it indicates that packets will be forwarded. indicates that packets will be forwarded.
The administrative status object indicates the forwarding state The administrative status object indicates the forwarding state
desired by the operator. desired by the operator.
5.8. mplsLabelStackTable 5.8. mplsLabelStackTable
The mplsLabelStackTable specifies the label stack to be pushed The mplsLabelStackTable specifies the label stack to be pushed onto a
onto a packet, beneath the top label. Entries to this table are packet, beneath the top label. Entries to this table are referred to
referred to from mplsXCTable. from mplsXCTable.
5.9 mplsInSegmentMapTable 5.9 mplsInSegmentMapTable
The mplsInSegmentMapTable specifies the mapping from the The mplsInSegmentMapTable specifies the mapping from the
mplsInSegmentIndex to the corresponding mplsInSegmentInterface mplsInSegmentIndex to the corresponding mplsInSegmentInterface and
and mplsInSegmentLabel objects. The purpose of this table is mplsInSegmentLabel objects. The purpose of this table is to provide
to provide the manager with an alternative means by which to the manager with an alternative means by which to locate in-segments.
locate in-segments. For instance, this table can be useful For instance, this table can be useful when tracing LSPs from LSR to
when tracing LSPs from LSR to LSR by first following the LSR by first following the in-segment to out-segment, retrieving the
in-segment to out-segment, retrieving the outgoing label outgoing label and out-going interface, and then proceeding to
and out-going interface, and then proceeding to interrogate interrogate this table at the next-hop LSR to continue the trace.
this table at the next-hop LSR to continue the trace.
6. Use of 32-bit and 64-bit Counters 6. Use of 32-bit and 64-bit Counters
64-bit counters are provided in this MIB module for high speed 64-bit counters are provided in this MIB module for high speed
interfaces where the use of 32-bit counters might be impractical. interfaces where the use of 32-bit counters might be impractical. The
The requirements on the use of 32-bit and 64-bit counters (copied requirements on the use of 32-bit and 64-bit counters (copied
verbatim from [RFC2863]) are as follows. verbatim from [RFC2863]) are as follows.
For interfaces that operate at 20,000,000 (20 million) bits per For interfaces that operate at 20,000,000 (20 million) bits per
second or less, 32-bit byte and packet counters MUST be supported. second or less, 32-bit byte and packet counters MUST be supported.
For interfaces that operate faster than 20,000,000 bits/second, For interfaces that operate faster than 20,000,000 bits/second, and
and slower than 650,000,000 bits/second, 32-bit packet counters slower than 650,000,000 bits/second, 32-bit packet counters MUST be
MUST be supported and 64-bit octet counters MUST be supported. supported and 64-bit octet counters MUST be supported. For
For interfaces that operate at 650,000,000 bits/second or faster, interfaces that operate at 650,000,000 bits/second or faster, 64-bit
64-bit packet counters AND 64-bit octet counters MUST be packet counters AND 64-bit octet counters MUST be supported.
supported.
7. Example of LSP Setup 7. Example of LSP Setup
In this section we provide a brief example of setting up an LSP In this section we provide a brief example of setting up an LSP using
using this MIB module's objects. While this example this MIB module's objects. While this example is not meant to
is not meant to illustrate every nuance of the MIB module, it illustrate every nuance of the MIB module, it is intended as an aid
is intended as an aid to understanding some of the key concepts. to understanding some of the key concepts. It is meant to be read
It is meant to be read after going through the MIB module itself. after going through the MIB module itself.
Suppose that one would like to manually create a best-effort, Suppose that one would like to manually create a best-effort,
unidirectional LSP. Assume that the LSP enters the LSR via MPLS unidirectional LSP. Assume that the LSP enters the LSR via MPLS
interface A with ifIndex 12 and exits the LSR via MPLS interface B interface A with ifIndex 12 and exits the LSR via MPLS interface B
with ifIndex 13. Let us assume that we do not wish to impose any with ifIndex 13. Let us assume that we do not wish to impose any
additional label stack beneath the top label on the outgoing additional label stack beneath the top label on the outgoing labeled
labeled packets. The following example illustrates which rows and packets. The following example illustrates which rows and
corresponding objects might be created to accomplish this. Those corresponding objects might be created to accomplish this. Those
objects relevant to illustrating the relationships amongst objects relevant to illustrating the relationships amongst different
different tables are shown here. Other objects may be needed tables are shown here. Other objects may be needed before conceptual
before conceptual row activation can happen. row activation can happen.
The RowStatus values shown in this section are those to be used in The RowStatus values shown in this section are those to be used in
the set request, typically createAndGo(4) which is used to create the set request, typically createAndGo(4) which is used to create the
the conceptual row and have its status immediately set to active. conceptual row and have its status immediately set to active. Note
Note that the proper use of createAndGo(4) requires that all that the proper use of createAndGo(4) requires that all columns that
columns that do not have a DEFVAL to be specified in order for do not have a DEFVAL to be specified in order for the SET to succeed.
the SET to succeed. In the example below we have not specify all In the example below we have not specify all such columns for the
such columns for the sake of keeping the example short. Please sake of keeping the example short. Please keep in mind that all such
keep in mind that all such fields must be send during a real SET fields must be send during a real SET operation. A subsequent
operation. A subsequent retrieval operation on the conceptual retrieval operation on the conceptual row will return a different
row will return a different value, such as active(1). Please see value, such as active(1). Please see [RFC2579] for a detailed
[RFC2579] for a detailed discussion on the use of RowStatus. discussion on the use of RowStatus.
We first create a cross-connect entry that associates the We first create a cross-connect entry that associates the desired
desired segments together. segments together.
In mplsXCTable: In mplsXCTable:
{ {
mplsXCIndex = 0x02, mplsXCIndex = 0x02,
mplsXCInSegmentIndex = 0x00000015, mplsXCInSegmentIndex = 0x00000015,
mplsXCOutSegmentIndex = 0x01, mplsXCOutSegmentIndex = 0x01,
mplsXCLspId = 0x0102 -- unique ID mplsXCLspId = 0x0102 -- unique ID
mplsXCLabelStackIndex = 0x00, -- only a single mplsXCLabelStackIndex = 0x00, -- only a single
-- outgoing label -- outgoing label
mplsXCRowStatus = createAndGo(4) mplsXCRowStatus = createAndGo(4)
} }
Next, we create the appropriate in-segment and out-segment Next, we create the appropriate in-segment and out-segment entries
entries based on the cross-connect. Note that some agents based on the cross-connect. Note that some agents may wish to
may wish to automatically create the in and out-segments automatically create the in and out-segments based on the cross-
based on the cross-connect creation. connect creation.
In mplsInSegmentTable: In mplsInSegmentTable:
{ {
mplsInSegmentIndex = 0x00000015 mplsInSegmentIndex = 0x00000015
mplsInSegmentLabel = 21, -- incoming label mplsInSegmentLabel = 21, -- incoming label
mplsInSegmentNPop = 1, mplsInSegmentNPop = 1,
mplsInSegmentInterface = 12, -- incoming interface mplsInSegmentInterface = 12, -- incoming interface
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accessible column.
mplsInSegmentLabelPtr = 0.0, mplsInSegmentLabelPtr = 0.0,
mplsInSegmentTrafficParamPtr = 0.0, mplsInSegmentTrafficParamPtr = 0.0,
mplsInSegmentRowStatus = createAndGo(4) mplsInSegmentRowStatus = createAndGo(4)
} }
In mplsOutSegmentTable: In mplsOutSegmentTable:
{ {
mplsOutSegmentIndex = 0x01, mplsOutSegmentIndex = 0x01,
mplsOutSegmentInterface = 13, -- outgoing interface mplsOutSegmentInterface = 13, -- outgoing interface
mplsOutSegmentPushTopLabel = true(1), mplsOutSegmentPushTopLabel = true(1),
mplsOutSegmentTopLabel = 22, -- outgoing label mplsOutSegmentTopLabel = 22, -- outgoing label
-- RowPointer MUST point to the first accesible column. -- RowPointer MUST point to the first accessible column.
mplsOutSegmentTrafficParamPtr = 0.0, mplsOutSegmentTrafficParamPtr = 0.0,
mplsOutSegmentLabelPtr = 0.0, mplsOutSegmentLabelPtr = 0.0,
mplsOutSegmentRowStatus = createAndGo(4) mplsOutSegmentRowStatus = createAndGo(4)
} }
Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex objects
objects will automatically be populated with the string 0x02 will automatically be populated with the string 0x02 when these
when these segments are referred to from the corresponding segments are referred to from the corresponding cross-connect entry.
cross- connect entry.
8. Application of the Interface Group to MPLS 8. Application of the Interface Group to MPLS
RFC2863 defines generic managed objects for managing RFC2863 defines generic managed objects for managing interfaces.
interfaces. This memo contains the media-specific This memo contains the media-specific extensions to the Interfaces
extensions to the Interfaces Group for managing MPLS interfaces. Group for managing MPLS interfaces.
This memo assumes the interpretation of the Interfaces Group to be This memo assumes the interpretation of the Interfaces Group to be in
in accordance with [RFC2863] which states that the interfaces accordance with [RFC2863] which states that the interfaces table
table (ifTable) contains information on the managed resource's (ifTable) contains information on the managed resource's interfaces
interfaces and that each sub-layer below the internetwork layer of and that each sub-layer below the internetwork layer of a network
a network interface is considered an interface. Thus, the MPLS interface is considered an interface. Thus, the MPLS interface is
interface is represented as an entry in the ifTable. The inter- represented as an entry in the ifTable. The inter-relation of
relation of entries in the ifTable is defined by Interfaces Stack entries in the ifTable is defined by Interfaces Stack Group defined
Group defined in [RFC2863]. in [RFC2863].
When using MPLS interfaces, the interface stack table might appear When using MPLS interfaces, the interface stack table might appear as
as follows: follows:
+----------------------------------------+ +----------------------------------------+
| MPLS interface; ifType = mpls(166) + | MPLS interface; ifType = mpls(166) +
+----------------------------------------+ +----------------------------------------+
| Underlying Layer + | Underlying Layer +
+----------------------------------------+ +----------------------------------------+
In the above diagram, "Underlying Layer" refers to the ifIndex of In the above diagram, "Underlying Layer" refers to the ifIndex of any
any interface type for which MPLS interworking has been defined. interface type for which MPLS interworking has been defined.
Examples include ATM, Frame Relay, Ethernet, etc. Examples include ATM, Frame Relay, Ethernet, etc.
8.1. Support of the MPLS Layer by ifTable 8.1. Support of the MPLS Layer by ifTable
Some specific interpretations of ifTable for the MPLS layer
follow. Some specific interpretations of ifTable for the MPLS layer follow.
Object Use for the MPLS layer Object Use for the MPLS layer
ifIndex Each MPLS interface is represented by an ifEntry. ifIndex Each MPLS interface is represented by an ifEntry.
ifDescr Description of the MPLS interface. ifDescr Description of the MPLS interface.
ifType The value that is allocated for MPLS is 166. ifType The value that is allocated for MPLS is 166.
ifSpeed The total bandwidth in bits per second for use by ifSpeed The total bandwidth in bits per second for use by
skipping to change at page 10, line 22 skipping to change at page 10, line 38
ifHCOutOctets The 64-bit version of ifOutOctets; supported if ifHCOutOctets The 64-bit version of ifOutOctets; supported if
required by the compliance statements in [RFC2863]. required by the compliance statements in [RFC2863].
ifAlias The non-volatile 'alias' name for the interface as ifAlias The non-volatile 'alias' name for the interface as
specified by a network manager. specified by a network manager.
ifCounterDiscontinuityTime ifCounterDiscontinuityTime
See [RFC2863]. See [RFC2863].
9. The Use of RowPointer 9. The Use of RowPointer
RowPointer is a textual convention used to identify a conceptual RowPointer is a textual convention used to identify a conceptual row
row in a MIB Table by pointing to the first accessible object in a MIB Table by pointing to the first accessible object in that
in that row. In this MIB module, the trafficParamPtr object from row. In this MIB module, the trafficParamPtr object from either the
either the mplsInSegmentTable or mplsOutSegmentTable SHOULD mplsInSegmentTable or mplsOutSegmentTable SHOULD indicate the first
indicate the first accessible column in an entry in the accessible column in an entry in the MplsTunnelResourceEntry in the
MplsTunnelResourceEntry in the MPLS-TE-STD-MIB [TEMIB] MPLS-TE-STD-MIB [RFC3812] to indicate the traffic parameter settings
to indicate the traffic parameter settings for this for this segment, if it represents an LSP used for a TE tunnel.
segment, if it represents an LSP used for a TE tunnel.
The trafficParamPtr object may optionally point at an The trafficParamPtr object may optionally point at an externally
externally defined traffic parameter specification defined traffic parameter specification table. A value of
table. A value of zeroDotZero indicates best-effort zeroDotZero indicates best-effort treatment. By having the same
treatment. By having the same value of this object, value of this object, two or more segments can indicate resource
two or more segments can indicate resource sharing sharing of such things as LSP queue space, etc.
of such things as LSP queue space, etc.
10. MPLS Label Switching Router MIB Module Definitions 10. MPLS Label Switching Router MIB Module Definitions
MPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN MPLS-LSR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Integer32, Counter32, Unsigned32, Counter64, Gauge32, Integer32, Counter32, Unsigned32, Counter64, Gauge32,
zeroDotZero zeroDotZero
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF -- [RFC2580]
TruthValue, RowStatus, StorageType, RowPointer, TruthValue, RowStatus, StorageType, RowPointer,
TimeStamp, TEXTUAL-CONVENTION TimeStamp, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
InterfaceIndexOrZero, ifGeneralInformationGroup, InterfaceIndexOrZero, ifGeneralInformationGroup,
ifCounterDiscontinuityGroup ifCounterDiscontinuityGroup
FROM IF-MIB FROM IF-MIB -- [RFC2863]
mplsStdMIB, MplsLSPID, MplsLabel, MplsBitRate, mplsStdMIB, MplsLSPID, MplsLabel, MplsBitRate,
MplsOwner MplsOwner
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- [RFC3811]
AddressFamilyNumbers AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB -- [IANAFamily]
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB -- [RFC3291]
; ;
mplsLsrStdMIB MODULE-IDENTITY mplsLsrStdMIB MODULE-IDENTITY
LAST-UPDATED "200310191200Z" -- 19 October 2003 12:00:00 GMT LAST-UPDATED "200406030000Z" -- June 3, 2004
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Cheenu Srinivasan " Cheenu Srinivasan
Blomberg L.P. Bloomberg L.P.
Email: cheenu@bloomberg.net Email: cheenu@bloomberg.net
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
Email: arunv@force10networks.com Email: arunv@force10networks.com
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
skipping to change at page 11, line 44 skipping to change at page 12, line 8
directly to the MPLS working group mailing list at directly to the MPLS working group mailing list at
mpls@uu.net." mpls@uu.net."
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
the Multiprotocol Label Switching (MPLS) Router as the Multiprotocol Label Switching (MPLS) Router as
defined in: Rosen, E., Viswanathan, A., and R. defined in: Rosen, E., Viswanathan, A., and R.
Callon, Multiprotocol Label Switching Architecture, Callon, Multiprotocol Label Switching Architecture,
RFC 3031, January 2001. RFC 3031, January 2001.
Copyright (C) The Internet Society (2003). This Copyright (C) The Internet Society (2004). The
version of this MIB module is part of RFCXXX; see initial version of this MIB module was published
the RFC itself for full legal notices." in RFC 3812. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html"
-- Revision history. -- Revision history.
REVISION REVISION
"200310191200Z" -- 19 October 2003 12:00:00 GMT "200406030000Z" -- June 3, 2004
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC 3813."
::= { mplsStdMIB XXX } -- Please see IANA considerations section ::= { mplsStdMIB 2 }
-- the requested mplsStdMIB subId is 2.
-- TEXTUAL-CONVENTIONs
MplsIndexType ::= TEXTUAL-CONVENTION MplsIndexType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is an octet string that can be used as a table "This is an octet string that can be used as a table
index in cases where a large addressable space is index in cases where a large addressable space is
required such as on an LSR where many applications required such as on an LSR where many applications
may be provisioning labels. may be provisioning labels.
Note that the string containing the single octet with Note that the string containing the single octet with
the value 0x00 is a reserved value used to represent the value 0x00 is a reserved value used to represent
special cases. When this textual convention is used special cases. When this TEXTUAL-CONVENTION is used
as the SYNTAX of an object, the DESCRITPION clause as the SYNTAX of an object, the DESCRIPTION clause
MUST specify if this special value is valid and if so MUST specify if this special value is valid and if so
what the special meaning is. what the special meaning is.
In systems that provide write access to the MPLS-LSR-STD In systems that provide write access to the MPLS-LSR-STD
MIB, mplsIndexType SHOULD be used as a simple multi-digit MIB, mplsIndexType SHOULD be used as a simple multi-digit
integer encoded as an octet string. integer encoded as an octet string.
No further overloading of the meaning of an index SHOULD No further overloading of the meaning of an index SHOULD
be made. be made.
In systems that do not offer write access to the MPLS-LSR-STD In systems that do not offer write access to the MPLS-LSR-STD
skipping to change at page 13, line 16 skipping to change at page 13, line 34
Responder (agent) changes the value of this object, according Responder (agent) changes the value of this object, according
to an implementation-specific algorithm. If the value is in to an implementation-specific algorithm. If the value is in
use, however, the SET fails. The Network Management use, however, the SET fails. The Network Management
Application must then re-read this variable to obtain a new Application must then re-read this variable to obtain a new
usable value. usable value.
Note that the string containing the single octet with Note that the string containing the single octet with
the value 0x00 is a reserved value used to represent the value 0x00 is a reserved value used to represent
the special case where no additional indexes can be the special case where no additional indexes can be
provisioned, or in systems that do not offer provisioned, or in systems that do not offer
write access, objects defined using this textual write access, objects defined using this TEXTUAL-CONVENTION
convention MUST return the string containing the single MUST return the string containing the single
octet with the value 0x00." octet with the value 0x00."
SYNTAX OCTET STRING (SIZE(1..24)) SYNTAX OCTET STRING (SIZE(1..24))
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Notifications -- Notifications
mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrStdMIB 0 } mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrStdMIB 0 }
-- Tables, Scalars -- Tables, Scalars
mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrStdMIB 1 } mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrStdMIB 1 }
skipping to change at page 13, line 50 skipping to change at page 14, line 20
::= { mplsLsrObjects 1 } ::= { mplsLsrObjects 1 }
mplsInterfaceEntry OBJECT-TYPE mplsInterfaceEntry OBJECT-TYPE
SYNTAX MplsInterfaceEntry SYNTAX MplsInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row in this table is created "A conceptual row in this table is created
automatically by an LSR for every interface capable automatically by an LSR for every interface capable
of supporting MPLS and which is configured to do so. of supporting MPLS and which is configured to do so.
A conceptual row in this table will exist iff a A conceptual row in this table will exist if and only if
corresponding entry in ifTable exists with ifType = a corresponding entry in ifTable exists with ifType =
mpls(166). If this associated entry in ifTable is mpls(166). If this associated entry in ifTable is
operationally disabled (thus removing MPLS operationally disabled (thus removing MPLS
capabilities on that interface), the corresponding capabilities on that interface), the corresponding
entry in this table MUST be deleted shortly thereafter. entry in this table MUST be deleted shortly thereafter.
An conceptual row with index 0 is created if the LSR An conceptual row with index 0 is created if the LSR
supports per-platform labels. This conceptual row supports per-platform labels. This conceptual row
represents the per-platform label space and contains represents the per-platform label space and contains
parameters that apply to all interfaces that participate parameters that apply to all interfaces that participate
in the per-platform label space. Other conceptual rows in the per-platform label space. Other conceptual rows
in this table represent MPLS interfaces that may in this table represent MPLS interfaces that may
participate in either the per-platform or per- participate in either the per-platform or per-
interface label spaces, or both. Implementations interface label spaces, or both. Implementations
that either only support per-platform labels, that either only support per-platform labels,
or have only them configured, may choose to return or have only them configured, may choose to return
just the mplsInterfaceEntry of 0 and not return just the mplsInterfaceEntry of 0 and not return
the other rows. This will greatly reduce the numebr the other rows. This will greatly reduce the number
of objects returned. Further information about label of objects returned. Further information about label
space participation of an interface is provided in space participation of an interface is provided in
the DESCRIPTION clause of the DESCRIPTION clause of
mplsInterfaceLabelParticipationType." mplsInterfaceLabelParticipationType."
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsInterfaceTable 1 } ::= { mplsInterfaceTable 1 }
MplsInterfaceEntry ::= SEQUENCE { MplsInterfaceEntry ::= SEQUENCE {
mplsInterfaceIndex InterfaceIndexOrZero, mplsInterfaceIndex InterfaceIndexOrZero,
mplsInterfaceLabelMinIn MplsLabel, mplsInterfaceLabelMinIn MplsLabel,
skipping to change at page 18, line 18 skipping to change at page 18, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of labels that are in "This object counts the number of labels that are in
use at this point in time on this interface in the use at this point in time on this interface in the
incoming direction. If the interface participates in incoming direction. If the interface participates in
only the per-platform label space, then the value of only the per-platform label space, then the value of
the instance of this object MUST be identical to the instance of this object MUST be identical to
the value of the instance with index 0. If the the value of the instance with index 0. If the
interface participates in the per-interface label interface participates in the per-interface label
space, then the instance of this object MUST space, then the instance of this object MUST
represent the number of of per-interface labels that represent the number of per-interface labels that
are in use on this interface." are in use on this interface."
::= { mplsInterfacePerfEntry 1 } ::= { mplsInterfacePerfEntry 1 }
mplsInterfacePerfInLabelLookupFailures OBJECT-TYPE mplsInterfacePerfInLabelLookupFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of labeled packets "This object counts the number of labeled packets
that have been received on this interface and which that have been received on this interface and which
skipping to change at page 19, line 19 skipping to change at page 19, line 49
-- mplsInterfacePerf Table end. -- mplsInterfacePerf Table end.
mplsInSegmentIndexNext OBJECT-TYPE mplsInSegmentIndexNext OBJECT-TYPE
SYNTAX MplsIndexNextType SYNTAX MplsIndexNextType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the next available value to "This object contains the next available value to
be used for mplsInSegmentIndex when creating entries be used for mplsInSegmentIndex when creating entries
in the mplsInSegmentTable. The special value of a in the mplsInSegmentTable. The special value of a
a string containing the single octet 0x00 indicates string containing the single octet 0x00 indicates
that no new entries can be created in this table. that no new entries can be created in this table.
Agents not allowing managers to create entries Agents not allowing managers to create entries
in this table MUST set this object to this special in this table MUST set this object to this special
value." value."
::= { mplsLsrObjects 3 } ::= { mplsLsrObjects 3 }
-- in-segment table. -- in-segment table.
mplsInSegmentTable OBJECT-TYPE mplsInSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsInSegmentEntry SYNTAX SEQUENCE OF MplsInSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 20, line 48 skipping to change at page 21, line 33
mplsInSegmentTrafficParamPtr RowPointer, mplsInSegmentTrafficParamPtr RowPointer,
mplsInSegmentRowStatus RowStatus, mplsInSegmentRowStatus RowStatus,
mplsInSegmentStorageType StorageType mplsInSegmentStorageType StorageType
} }
mplsInSegmentIndex OBJECT-TYPE mplsInSegmentIndex OBJECT-TYPE
SYNTAX MplsIndexType SYNTAX MplsIndexType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for for this in-segment. The "The index for this in-segment. The
string containing the single octet 0x00 string containing the single octet 0x00
MUST not be used as an index." MUST not be used as an index."
::= { mplsInSegmentEntry 1 } ::= { mplsInSegmentEntry 1 }
mplsInSegmentInterface OBJECT-TYPE mplsInSegmentInterface OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the "This object represents the
skipping to change at page 22, line 18 skipping to change at page 23, line 6
be set to that number. This object cannot be modified be set to that number. This object cannot be modified
if mplsInSegmentRowStatus is active(1)." if mplsInSegmentRowStatus is active(1)."
DEFVAL { 1 } DEFVAL { 1 }
::= { mplsInSegmentEntry 5 } ::= { mplsInSegmentEntry 5 }
mplsInSegmentAddrFamily OBJECT-TYPE mplsInSegmentAddrFamily OBJECT-TYPE
SYNTAX AddressFamilyNumbers SYNTAX AddressFamilyNumbers
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IANA address family of packets "The IANA address family [IANAFamily] of packets
received on this segment, which is used at an egress received on this segment, which is used at an egress
LSR to deliver them to the appropriate layer 3 entity. LSR to deliver them to the appropriate layer 3 entity.
A value of other(0) indicates that the family type is A value of other(0) indicates that the family type is
either unknown or undefined; this SHOULD NOT be used either unknown or undefined; this SHOULD NOT be used
at an egress LSR. This object cannot be at an egress LSR. This object cannot be
modified if mplsInSegmentRowStatus is active(1)." modified if mplsInSegmentRowStatus is active(1)."
REFERENCE REFERENCE
"See Internet Assigned Numbers Authority (IANA), "Internet Assigned Numbers Authority (IANA), ADDRESS
ADDRESS FAMILY NUMBERS." FAMILY NUMBERS, (http://www.iana.org/assignments/
address-family-numbers), for MIB see:
http://www.iana.org/assignments/
ianaaddressfamilynumbers-mib
"
DEFVAL { other } DEFVAL { other }
::= { mplsInSegmentEntry 6 } ::= { mplsInSegmentEntry 6 }
mplsInSegmentXCIndex OBJECT-TYPE mplsInSegmentXCIndex OBJECT-TYPE
SYNTAX MplsIndexType SYNTAX MplsIndexType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Index into mplsXCTable which identifies which cross- "Index into mplsXCTable which identifies which cross-
connect entry this segment is part of. The string connect entry this segment is part of. The string
skipping to change at page 23, line 11 skipping to change at page 24, line 5
"Denotes the entity that created and is responsible "Denotes the entity that created and is responsible
for managing this segment." for managing this segment."
::= { mplsInSegmentEntry 8 } ::= { mplsInSegmentEntry 8 }
mplsInSegmentTrafficParamPtr OBJECT-TYPE mplsInSegmentTrafficParamPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable represents a pointer to the traffic "This variable represents a pointer to the traffic
parameter specification for this out-segment. This parameter specification for this in-segment. This
value may point at an entry in the value may point at an entry in the
mplsTunnelResourceTable in the MPLS-TE-STD-MIB (RFCnnnn) mplsTunnelResourceTable in the MPLS-TE-STD-MIB (RFC3812)
RFC Editor: Please fill in RFC number.
to indicate which traffic parameter settings for this to indicate which traffic parameter settings for this
segment if it represents an LSP used for a TE tunnel. segment if it represents an LSP used for a TE tunnel.
This value may optionally point at an This value may optionally point at an
externally defined traffic parameter specification externally defined traffic parameter specification
table. A value of zeroDotZero indicates best-effort table. A value of zeroDotZero indicates best-effort
treatment. By having the same value of this object, treatment. By having the same value of this object,
two or more segments can indicate resource sharing two or more segments can indicate resource sharing
of such things as LSP queue space, etc. of such things as LSP queue space, etc.
skipping to change at page 26, line 33 skipping to change at page 27, line 30
-- out-segment table. -- out-segment table.
mplsOutSegmentIndexNext OBJECT-TYPE mplsOutSegmentIndexNext OBJECT-TYPE
SYNTAX MplsIndexNextType SYNTAX MplsIndexNextType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the next available value to "This object contains the next available value to
be used for mplsOutSegmentIndex when creating entries be used for mplsOutSegmentIndex when creating entries
in the mplsOutSegmentTable. The special value of a in the mplsOutSegmentTable. The special value of a
a string containing the single octet 0x00 indicates string containing the single octet 0x00
indicates that no new entries can be created in this indicates that no new entries can be created in this
table. Agents not allowing managers to create entries table. Agents not allowing managers to create entries
in this table MUST set this object to this special in this table MUST set this object to this special
value." value."
::= { mplsLsrObjects 6 } ::= { mplsLsrObjects 6 }
mplsOutSegmentTable OBJECT-TYPE mplsOutSegmentTable OBJECT-TYPE
SYNTAX SEQUENCE OF MplsOutSegmentEntry SYNTAX SEQUENCE OF MplsOutSegmentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 27, line 35 skipping to change at page 28, line 33
the index for this table." the index for this table."
INDEX { mplsOutSegmentIndex } INDEX { mplsOutSegmentIndex }
::= { mplsOutSegmentTable 1 } ::= { mplsOutSegmentTable 1 }
MplsOutSegmentEntry ::= SEQUENCE { MplsOutSegmentEntry ::= SEQUENCE {
mplsOutSegmentIndex MplsIndexType, mplsOutSegmentIndex MplsIndexType,
mplsOutSegmentInterface InterfaceIndexOrZero, mplsOutSegmentInterface InterfaceIndexOrZero,
mplsOutSegmentPushTopLabel TruthValue, mplsOutSegmentPushTopLabel TruthValue,
mplsOutSegmentTopLabel MplsLabel, mplsOutSegmentTopLabel MplsLabel,
mplsOutSegmentTopLabelPtr RowPointer, mplsOutSegmentTopLabelPtr RowPointer,
mplsOutSegmentNextHopAddrType InetAddressType, mplsOutSegmentNextHopAddrType InetAddressType,
mplsOutSegmentNextHopAddr InetAddress, mplsOutSegmentNextHopAddr InetAddress,
mplsOutSegmentXCIndex MplsIndexType, mplsOutSegmentXCIndex MplsIndexType,
mplsOutSegmentOwner MplsOwner, mplsOutSegmentOwner MplsOwner,
mplsOutSegmentTrafficParamPtr RowPointer, mplsOutSegmentTrafficParamPtr RowPointer,
mplsOutSegmentRowStatus RowStatus, mplsOutSegmentRowStatus RowStatus,
mplsOutSegmentStorageType StorageType mplsOutSegmentStorageType StorageType
} }
mplsOutSegmentIndex OBJECT-TYPE mplsOutSegmentIndex OBJECT-TYPE
SYNTAX MplsIndexType SYNTAX MplsIndexType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 30, line 36 skipping to change at page 31, line 40
::= { mplsOutSegmentEntry 9 } ::= { mplsOutSegmentEntry 9 }
mplsOutSegmentTrafficParamPtr OBJECT-TYPE mplsOutSegmentTrafficParamPtr OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable represents a pointer to the traffic "This variable represents a pointer to the traffic
parameter specification for this out-segment. This parameter specification for this out-segment. This
value may point at an entry in the value may point at an entry in the
MplsTunnelResourceEntry in the MPLS-TE-STD-MIB (RFCnnnn) MplsTunnelResourceEntry in the MPLS-TE-STD-MIB (RFC3812)
RFC Editor: Please fill in RFC number. RFC Editor: Please fill in RFC number.
to indicate which traffic parameter settings for this to indicate which traffic parameter settings for this
segment if it represents an LSP used for a TE tunnel. segment if it represents an LSP used for a TE tunnel.
This value may optionally point at an This value may optionally point at an
externally defined traffic parameter specification externally defined traffic parameter specification
table. A value of zeroDotZero indicates best-effort table. A value of zeroDotZero indicates best-effort
treatment. By having the same value of this object, treatment. By having the same value of this object,
skipping to change at page 35, line 51 skipping to change at page 37, line 16
group of cross-connect segments. The string group of cross-connect segments. The string
containing a single octet 0x00 is an invalid index." containing a single octet 0x00 is an invalid index."
::= { mplsXCEntry 1 } ::= { mplsXCEntry 1 }
mplsXCInSegmentIndex OBJECT-TYPE mplsXCInSegmentIndex OBJECT-TYPE
SYNTAX MplsIndexType SYNTAX MplsIndexType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Incoming label index. "Incoming label index.
If this object is set to the string containing If this object is set to the string containing
a single octet 0x00, this indicates a special a single octet 0x00, this indicates a special
case outlined in the table's description above. case outlined in the table's description above.
In this case no corresponding mplsInSegmentEntry In this case no corresponding mplsInSegmentEntry
shall exist." shall exist."
::= { mplsXCEntry 2 } ::= { mplsXCEntry 2 }
mplsXCOutSegmentIndex OBJECT-TYPE mplsXCOutSegmentIndex OBJECT-TYPE
SYNTAX MplsIndexType SYNTAX MplsIndexType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 43, line 25 skipping to change at page 45, line 8
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is set to true(1), then it enables "If this object is set to true(1), then it enables
the emission of mplsXCUp and mplsXCDown the emission of mplsXCUp and mplsXCDown
notifications; otherwise these notifications are not notifications; otherwise these notifications are not
emitted." emitted."
REFERENCE REFERENCE
"See also RFC3413 for explanation that "See also RFC3413 for explanation that
notifications are under the ultimate control of the notifications are under the ultimate control of the
MIB modules in this document." MIB module in this document."
DEFVAL { false } DEFVAL { false }
::= { mplsLsrObjects 15 } ::= { mplsLsrObjects 15 }
-- Cross-connect. -- Cross-connect.
mplsXCUp NOTIFICATION-TYPE mplsXCUp NOTIFICATION-TYPE
OBJECTS { mplsXCOperStatus, -- start of range OBJECTS { mplsXCOperStatus, -- start of range
mplsXCOperStatus -- end of range mplsXCOperStatus -- end of range
} }
STATUS current STATUS current
skipping to change at page 46, line 48 skipping to change at page 48, line 35
::= { mplsLsrCompliances 1 } ::= { mplsLsrCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE mplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance requirement for implementations that only DESCRIPTION "Compliance requirement for implementations that only
provide read-only support for MPLS-LSR-STD-MIB. Such provide read-only support for MPLS-LSR-STD-MIB. Such
devices can then be monitored but cannot be configured devices can then be monitored but cannot be configured
using this MIB modules. using this MIB module.
" "
MODULE IF-MIB -- The interfaces Group MIB, RFC 2863 MODULE IF-MIB -- The interfaces Group MIB, RFC 2863
MANDATORY-GROUPS { MANDATORY-GROUPS {
ifGeneralInformationGroup, ifGeneralInformationGroup,
ifCounterDiscontinuityGroup ifCounterDiscontinuityGroup
} }
MODULE -- This module MODULE -- This module
MANDATORY-GROUPS { MANDATORY-GROUPS {
mplsInterfaceGroup, mplsInterfaceGroup,
mplsInSegmentGroup, mplsInSegmentGroup,
mplsOutSegmentGroup, mplsOutSegmentGroup,
mplsXCGroup, mplsXCGroup,
mplsPerfGroup mplsPerfGroup
} }
skipping to change at page 52, line 49 skipping to change at page 55, line 4
NOTIFICATIONS { NOTIFICATIONS {
mplsXCUp, mplsXCUp,
mplsXCDown mplsXCDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this "Set of notifications implemented in this
module." module."
::= { mplsLsrGroups 9 } ::= { mplsLsrGroups 9 }
END END
11. Security Considerations
11. Security Considerations It is clear that this MIB module is potentially useful for monitoring
of MPLS LSRs. This MIB can also be used for configuration of certain
It is clear that this MIB module is potentially useful for objects, and anything that can be configured can be incorrectly
monitoring of MPLS LSRs. This MIB can also be used for configured, with potentially disastrous results.
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 module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLsrInSegmentTable, mplsLsrOutSegmentTable, o the mplsLsrInSegmentTable, mplsLsrOutSegmentTable, mplsXCTable,
mplsXCTable, mplsOutSegmentPerfTable, mplsInterfacePerfTable, mplsOutSegmentPerfTable, mplsInterfacePerfTable, and
and mplsInSegmentPerfTable collectively contain objects to mplsInSegmentPerfTable collectively contain objects to provision
provision MPLS interfaces, LSPs and their associated parameters MPLS interfaces, LSPs and their associated parameters on an Label
on an Label Switching Router (LSR). Unauthorized access to Switching Router (LSR). Unauthorized access to objects in these
objects in these tables, could result in disruption of traffic tables, could result in disruption of traffic on the network.
on the network. This is especially true if an LSP has been This is especially true if an LSP has been established. The use
established. The use of stronger mechanisms such as SNMPv3 of stronger mechanisms such as SNMPv3 security should be
security should be considered where possible. Specifically, considered where possible. Specifically, SNMPv3 VACM and USM MUST
SNMPv3 VACM and USM MUST be used with any v3 agent which be used with any v3 agent which implements this MIB module.
implements this MIB module. Administrators should consider Administrators should consider whether read access to these
whether read access to these objects should be allowed, objects should be allowed, since read access may be undesirable
since read access may be undesirable under certain under certain circumstances.
circumstances.
Some of the readable objects in this MIB module "i.e., objects with a Some of the readable objects in this MIB module "i.e., objects with a
MAX-ACCESS other than not-accessible" may be considered sensitive or MAX-ACCESS other than not-accessible" may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the mplsLsrInSegmentTable, mplsLsrOutSegmentTable, o the mplsLsrInSegmentTable, mplsLsrOutSegmentTable, mplsXCTable,
mplsXCTable, mplsOutSegmentPerfTable, mplsInterfacePerfTable, mplsOutSegmentPerfTable, mplsInterfacePerfTable, and
and mplsInSegmentPerfTable collectively show the LSP network mplsInSegmentPerfTable collectively show the LSP network topology
topology and its performance characteristics. and its performance characteristics. If an Administrator does not
If an Administrator does not want to reveal this want to reveal this information, then these tables should be
information, then these tables should be considered sensitive/vulnerable.
considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure "for example by using IPSec", Even if the network itself is secure "for example by using IPSec",
even then, there is no control as to who on the secure network is 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 allowed to access and GET/SET "read/change/create/delete" the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework "see [RFC3410], section 8", provided by the SNMPv3 framework "see [RFC3410], section 8",
including full support for the SNMPv3 cryptographic mechanisms "for including full support for the SNMPv3 cryptographic mechanisms "for
authentication and privacy". authentication and privacy".
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access instance of this MIB module, is properly configured to give access to
to the objects only to those principals "users" that have legitimate the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET "change/create/delete" them.
12. Acknowledgments 12. Acknowledgments
We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim Mancour,
Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, Vasanthi Keith McCloghrie, Bala Rajagopalan, Dan Tappan, Vasanthi Thirumalai,
Thirumalai, Joseph Benoit, Mike Piecuch, Joan Cucchiara. Joseph Benoit, Mike Piecuch, Joan Cucchiara. A special thanks to Bert
A special thanks to Bert Wijnen and Mike MacFaden for really Wijnen and Mike MacFaden for really getting the MIB module into
getting the MIB module into shape. shape.
13. IANA Considerations 13. IANA Considerations
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB
[MPLSTCMIB], MPLS related standards track MIB modules should be [RFC3811], MPLS related standards track MIB modules should be rooted
rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules under the mplsStdMIB subtree. There are 4 MPLS MIB Modules contained
contained in this document, each of the following "IANA in this document, each of the following "IANA Considerations"
Considerations" subsections requests IANA for a new assignment under subsections requests IANA for a new assignment under the mplsStdMIB
the mplsStdMIB subtree. New assignments can only be made via a subtree. New assignments can only be made via a Standards Action as
Standards Action as specified in [RFC2434]. specified in [RFC2434].
13.1. IANA Considerations for MPLS-LSR-STD-MIB 13.1. IANA Considerations for MPLS-LSR-STD-MIB
The IANA is requested to assign { mplsStdMIB 2 } to the
MPLS-LSR-STD-MIB module specified in this document.
14. References The IANA has assigned { mplsStdMIB 2 } to the MPLS-LSR-STD-MIB module
specified in this document.
14.1. Normative References 14. References
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate 14.1. Normative References
[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. Requirement Levels", RFC 2119, BCP 14, March 1997.
[RFC2515] Tesink, K., et al., "Definitions of Managed Objects [RFC2515] Tesink, K., Ed., "Definitions of Managed Objects for
for ATM Management", RFC 2515, February 1999. ATM Management", RFC 2515, February 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Structure of "Structure of Management Information Version 2
Management Information Version 2 (SMIv2)", STD 58, RFC (SMIv2)", STD 58, RFC 2578, April 1999.
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Textual Conventions "Textual Conventions for SMIv2", STD 58, RFC 2579,
for SMIv2", STD 58, RFC 2579, April 1999. April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Conformance "Conformance Statements for SMIv2", STD 58, RFC 2580,
Statements for SMIv2", STD 58, RFC 2580, April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
Group MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC "Multiprotocol Label Switching Architecture", RFC 3031,
3031, January 2001. January 2001.
[RFC3291] Daniele, M., Haberman, B., Routhier., S., [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder., J., "Textual Conventions Schoenwaelder, "Textual Conventions for Internet
for Internet Network Addresses", RFC3291, Network Addresses", RFC 3291, May 2002.
May 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC
December 2002. 3411, December 2002.
[TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS [RFC3811] Nadeau, T. and J. Cucchiara, Eds., "Definition of
Traffic Engineering Management Information Base ", Textual Conventions (TCs) for Multiprotocol Label
Internet Draft <draft-ietf-mpls-te-mib-09.txt>, Switching (MPLS) Management", RFC 3811, June 2004.
November 2002.
[TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
Viswanathan, A., Sjostrand, H. and K. Kompella, "Multiprotocol Label Switching (MPLS) Traffic
"Definition of Textual Conventions and OBJECT- Engineering (TE) Management Information Base (MIB)",
IDENTITIES for Multi-Protocol Label Switching (MPLS) RFC 3812, June 2004.
Management", Internet Draft <draft-ietf-mpls-tc-mib-
06.txt>, April 2003.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS [IANAFamiy] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS, (http://www.isi.edu/in- FAMILY NUMBERS,
notes/iana/assignements/address-family-numbers), (http://www.iana.org/assignments/address-family-
for MIB see: numbers), for MIB see:
ftp://ftp.isi.edu/mib/iana.mib/ianaaddressfamilynum http://www.iana.org/assignments/
bers.mib ianaaddressfamilynumbers-mib
14.2. Informative References 14.2. Informative References
[RFC2026] S. Bradner, "The Internet Standards Process -- [MPLSMGMT] Nadeau, T., Srinivasan, C., and A. Farrel,
Revision 3", RFC 2026, October 1996. "Multiprotocol Label Switching (MPLS) Management
Overview", Work in Progress, September 2003.
[RFC3413] Levi, D., Meyer, P., Stewart, B., [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing
"SNMP Applications", RFC 3413, December 2002. an IANA Considerations Section in RFCs", BCP 26, RFC
2434, October 1998.
[RFC3413] Levi, D., Meyer, P. and B. Stewart, "Simple Network
Management Protocol (SNMP) Applications", STD 62, RFC
3413, December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
15. Authors' Addresses 15. Authors' Addresses
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P. Bloomberg L.P.
499 Park Ave., New York, NY 10022 499 Park Ave., New York, NY 10022
Phone: +1-212-893-3682
Email: cheenu@bloomberg.net
Arun Viswanathan Phone: +1-212-893-3682
Force10 Networks, Inc. EMail: cheenu@bloomberg.net
1440 McCarthy Blvd
Milpitas, CA 95035
Phone: +1-408-571-3516
Email: arunv@force10networks.com
Thomas D. Nadeau Arun Viswanathan
Cisco Systems, Inc. Force10 Networks, Inc.
300 Beaver Brook Road 1440 McCarthy Blvd
Boxboro, MA 01719 Milpitas, CA 95035
Phone: +1-978-936-1470
Email: tnadeau@cisco.com
16. Full Copyright Statement Phone: +1-408-571-3516
EMail: arunv@force10networks.com
Copyright (C) The Internet Society (2003). All Rights Reserved. Thomas D. Nadeau
Cisco Systems, Inc.
300 Beaver Brook Road
Boxboro, MA 01719
This document and translations of it may be copied and furnished Phone: +1-978-936-1470
to others, and derivative works that comment on or otherwise EMail: tnadeau@cisco.com
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 16. Full Copyright Statement
be revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on Copyright (C) The Internet Society (2004). This document is subject
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET to the rights, licenses and restrictions contained in BCP 78, and
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR except as set forth therein, the authors retain all their rights.
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
17. Intellectual Property Notice Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11 [RFC2028]. found in BCP 78 and BCP 79.
Copies of claims of rights made available for publication and any
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementors or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 130 change blocks. 
421 lines changed or deleted 386 lines changed or added

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