draft-ietf-mpls-bundle-mib-03.txt   draft-ietf-mpls-bundle-mib-04.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Meriton Networks Internet Draft Editor
Expires: December 2002 Expires: May 2003
Sudheer Dharanikota Sudheer Dharanikota
Nayna Networks
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Calient Networks Calient Networks
June 2002 November 2002
Link Bundling Management Information Base Link Bundling Management Information Base
draft-ietf-mpls-bundle-mib-03.txt draft-ietf-mpls-bundle-mib-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet- Drafts. groups may also distribute working documents as Internet- Drafts.
skipping to change at page 1, line 40 skipping to change at page 1, line 39
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Table of Contents Table of Contents
1. Abstract ..................................................... 2 1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction ................................................. 2 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Terminology .................................................. 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The SNMP Management Framework ................................ 3 4. The SNMP Management Framework . . . . . . . . . . . . . . . . . 3
5. Feature Checklist ............................................ 4 5. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . 4
6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Summary of Link Bundling MIB . . . . . . . . . . . . . . . . . 5
6. Outline ...................................................... 5 7. Brief Description of MIB Objects . . . . . . . . . . . . . . . 6
6.1. Summary of Link Bundling MIB ................................. 5 7.1. teLinkTable . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Brief Description of MIB Objects ............................. 6 7.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 6
7.1. teLinkTable .................................................. 6 7.3. teLinkOspfTeTable . . . . . . . . . . . . . . . . . . . . . . . 6
7.2. teLinkDescriptorTable ........................................ 6 7.4. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 6
7.3. teLinkOspfTeTable ............................................ 6 7.5. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 6
7.4. teLinkSrlgTable .............................................. 6 7.6. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 6
7.5. teLinkBandwidthTable ......................................... 7 7.7. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 6
7.6. componentLinkTable ........................................... 7 7.8. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 6
7.7. componentLinkDescriptorTable ................................. 7 8. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . 6
7.8. componentLinkBandwidthTable .................................. 7 9. Application of the Interfaces Group to TE Links . . . . . . . . 10
8. Example of Bundled Link Setup ................................ 7 9.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 11
9. Application of the Interfaces Group to TE Links .............. 11 9.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . 12
9.1 Support of the TE Link Layer by ifTable ...................... 12 10. Link Bundling MIB Definitions . . . . . . . . . . . . . . . . . 14
9.2 Using ifStackTable ........................................... 13 11. Intellectual Property Considerations . . . . . . . . . . . . . 47
10. Link Bundling MIB Definitions ................................ 15 12. Security Considerations . . . . . . . . . . . . . . . . . . . . 47
11. Security Considerations ...................................... 50 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 48
12. Acknowledgments .............................................. 51 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49
13. References ................................................... 51 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 49
14. Authors' Addresses ........................................... 54 14.2 Informative References . . . . . . . . . . . . . . . . . . . . 50
15. Full Copyright Statement ..................................... 54 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 52
16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 52
1. Abstract 1. Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling link bun- In particular, it describes managed objects for modeling link
dling as described in the Link Bundling in MPLS Traffic Engineering bundling as described in the Link Bundling in MPLS Traffic Engineer-
Internet Draft. ing Internet Draft.
2. Introduction 2. Introduction
OSPF [OSPF], Generalized MPLS (GMPLS) [GMPLS] and the Link Management OSPF [OSPF], Generalized MPLS (GMPLS) [GMPLS] and the Link Management
Protocol (LMP) [LMP] use the concept of traffic engineering (TE) Protocol (LMP) [LMP] use the concept of traffic engineering (TE)
links to abstract link properties. The effect of this approach is the links to abstract link properties. The effect of this approach is the
reduction of the amount of routing information exchanged in the net- reduction of the amount of routing information exchanged in the net-
work, which improves routing scalability. In addition, the use of TE work, which improves routing scalability. In addition, the use of TE
link allows the implementation of new capabilities such as link pro- link allows the implementation of new capabilities such as link pro-
tection. tection.
skipping to change at page 3, line 18 skipping to change at page 3, line 15
[RFC2119]. [RFC2119].
3. Terminology 3. Terminology
This document uses terminology from the documents describing link This document uses terminology from the documents describing link
bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. bundling [BUNDLING] and G-MPLS [GMPLS-ARCH].
The link bundling feature is designed to aggregate one or more simi- The link bundling feature is designed to aggregate one or more simi-
lar entities between a node pair into a bundled link [BUNDLING]. In lar entities between a node pair into a bundled link [BUNDLING]. In
the document, those entities are referred to as TE links. A TE link the document, those entities are referred to as TE links. A TE link
is a subinterface capable of carrying MPLS traffic engineered is a subinterface capable of carrying MPLS traffic engineered traf-
traffic. A TE Link may be comprised of only one underlying component fic. A TE Link may be comprised of only one underlying component
links. In cases where more than one component link is to be com- links. In cases where more than one component link is to be com-
bined, multiple component links should be created with differing bined, multiple component links should be created with differing pri-
priorities to indicate hot-standby or parallel utilization. orities to indicate hot-standby or parallel utilization.
A bundled link is just another kind of Traffic Engineering (TE) link A bundled link is just another kind of Traffic Engineering (TE) link
(see [GMPLS-OSPF]). A link bundle is a subinterface which bonds the (see [GMPLS-OSPF]). A link bundle is a subinterface which bonds the
traffic of a group of one or more TE links. There should be more than traffic of a group of one or more TE links. There should be more than
one TE Link in a link bundle, but this is not a requirement. Furth- one TE Link in a link bundle, but this is not a requirement. Fur-
ermore, if there are more than one TE link in a link bundle at some thermore, if there are more than one TE link in a link bundle at some
time, and at some point later, all but one of the links are deleted, time, and at some point later, all but one of the links are deleted,
the agent may choose to either delete the link bundle, or it may the agent may choose to either delete the link bundle, or it may
choose to leave it intact. Traffic counters on a link bundle are choose to leave it intact. Traffic counters on a link bundle are
cumulative for all subinterfaces which it binds together. cumulative for all subinterfaces which it binds together.
4. The SNMP Management Framework 4. The SNMP Management Framework
The SNMP Management Framework presently consists of five major com- The SNMP Management Framework presently consists of five major compo-
ponents: nents:
- An overall architecture, described in RFC 2571 [RFC2571]. - An overall architecture, described in RFC 2571 [RFC2571].
Mechanisms for describing and naming objects and events for the Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described 1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580]. STD 58, RFC 2580 [RFC2580].
skipping to change at page 7, line 22 skipping to change at page 6, line 47
This table enumerates the component links and their association with This table enumerates the component links and their association with
TE link. TE link.
7.7. componentLinkDescriptorTable 7.7. componentLinkDescriptorTable
This table enumerates the link descriptors that each component link This table enumerates the link descriptors that each component link
supports. supports.
7.8. componentLinkBandwidthTable 7.8. componentLinkBandwidthTable
The component link bandwidth table specifies the priority-based The component link bandwidth table specifies the priority-based band-
bandwidth values associated with the component links. width values associated with the component links.
8. Example of Bundled Link Setup 8. Example of Bundled Link Setup
In this section we provide a brief example of using the MIB In this section we provide a brief example of using the MIB
objects described in section 10 to set up a bundled link. objects described in section 10 to set up a bundled link.
While this example is not meant to illustrate every While this example is not meant to illustrate every
nuance of the MIB, it is intended as an aid to understanding some 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 of the key concepts. It is meant to be read after going through the
MIB itself. MIB itself.
skipping to change at page 15, line 36 skipping to change at page 15, line 4
2 4 2 4
3 0 3 0
4 0 4 0
10. Link Bundling MIB Definitions 10. Link Bundling MIB Definitions
LINK-BUNDLING-MIB DEFINITIONS ::= BEGIN LINK-BUNDLING-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Unsigned32 mib-2, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TruthValue, RowStatus, StorageType TruthValue, RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
skipping to change at page 16, line 4 skipping to change at page 15, line 18
FROM SNMPv2-CONF FROM SNMPv2-CONF
TruthValue, RowStatus, StorageType TruthValue, RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
RouterID RouterID
FROM OSPF-MIB FROM OSPF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
linkBundlingMIB MODULE-IDENTITY linkBundlingMIB MODULE-IDENTITY
LAST-UPDATED "200206211200Z" -- 21 June 2002 12:00:00 EST LAST-UPDATED "200211011200Z" -- 1 November 2002 12:00:00 EST
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Postal: Meriton Networks Email: dubuc.consulting@rogers.com
3026 Solandt Road
Kanata, ON, CANADA K2K 2A5
Tel: +1-613-270-9279 x253
Email: martin.dubuc@meriton.com
Sudheer Dharanikota Sudheer Dharanikota
Postal: Nayna Networks, Inc. Email: sudheer@ieee.org
157 Topaz Street
Milipitas, CA 95035
Tel: +1-408-956-8000 x357
Email: sudheer@nayna.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Tel: +1-978-244-3051 Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Postal: Calient Networks, Inc. Postal: Calient Networks, Inc.
25 Castilian Drive 25 Castilian Drive
Goleta, CA 93117 Goleta, CA 93117
Email: jplang@calient.net" Email: jplang@calient.net"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
MPLS traffic engineering link bundling as MPLS traffic engineering link bundling as
defined in: Kompella, K., Rekhter, Y., Berger, L., defined in: Kompella, K., Rekhter, Y., Berger, L.,
Link Bundling in MPLS Traffic Engineering Link Bundling in MPLS Traffic Engineering
Internet Draft <draft-ietf-mpls-bundling-03.txt>, Internet Draft <draft-ietf-mpls-bundling-04.txt>,
May 2002." July 2002."
-- Revision history. -- Revision history.
REVISION REVISION
"200206141200Z" -- 21 June 2002 12:00:00 EST "200211011200Z" -- 1 November 2002 12:00:00 EST
DESCRIPTION
"Addressed WG chair comments."
REVISION
"200205211200Z" -- 21 May 2002 12:00:00 EST
DESCRIPTION
"Addressed comments received during Last Call.
- Addressed syntax errors reports by smilint.
- Reintroduced teLinkIpAddrType.
- Replaced ifIndex in linkBundlingMismatch
notification with TE link endpoint objects."
REVISION
"200202261200Z" -- 26 February 2002 12:00:00 EST
DESCRIPTION
"- Updated MIB boiler plate and references.
- Added linkBundlingFullModuleCompliance conformance statement.
- Removed teLinkIpAddrType. Replaced numbered value with
ipV4 and ipV6 values in teLinkNumberingType.
- Updated description of all row status and storage type objects.
- Changed some of the enumerated value to start from 1 instead of 0.
- Updated references."
REVISION
"200109101200Z" -- 10 September 2001 12:00:00 EST
DESCRIPTION
"Removed teLinkRemoteId. Updated teLinkEncodingType and
componentLinkEncodingType values."
REVISION
"200105221200Z" -- 22 May 2001 12:00:00 EST
DESCRIPTION
"Replaced InetAddressIPv4 and InetAddressIPv6 with InetAddress
and InetAddrType. Changed description of entries which extend
ifEntry. Made various minor corrections."
REVISION
"200105151200Z" -- 15 May 2001 12:00:00 EST
DESCRIPTION
"Replaced componentLinkTable by componentLinkTable.
Replaced linkBundlingTable by teLinkTable. Converted TE links
into interfaces."
REVISION
"200102231200Z" -- 23 February 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial draft version." "Initial version published as RFC xxxx (to be assigned by RFC Editor)"
::= { experimental 114 } -- See [Assigned] ::= { mib-2 xxx } -- To be assigned by IANA (experimental 114 can be used
-- in the interim)
-- Textual Conventions -- Textual Conventions
-- Top level components of this MIB -- Top level components of this MIB
-- Notifications -- Notifications
linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 } linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 }
-- Tables, Scalars -- Tables, Scalars
linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 } linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 }
-- Conformance -- Conformance
linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 } linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 }
-- TE Link Table -- TE Link Table
teLinkTable OBJECT-TYPE teLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkEntry SYNTAX SEQUENCE OF TeLinkEntry
skipping to change at page 19, line 43 skipping to change at page 18, line 12
teLinkMetric OBJECT-TYPE teLinkMetric OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The traffic engineering metric for the TE link is "The traffic engineering metric for the TE link is
derived from its component links. All component links derived from its component links. All component links
within the TE link must have the same traffic within the TE link must have the same traffic
engineering metric." engineering metric."
REFERENCE REFERENCE
"draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS "[BUNDLING]"
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002."
::= { teLinkEntry 4 } ::= { teLinkEntry 4 }
teLinkMuxCapability OBJECT-TYPE teLinkMuxCapability OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
packetSwitch1(1), packetSwitch1(1),
packetSwitch2(2), packetSwitch2(2),
packetSwitch3(3), packetSwitch3(3),
packetSwitch4(4), packetSwitch4(4),
layer2Switch(51), layer2Switch(51),
tdm(100), tdm(100),
skipping to change at page 20, line 18 skipping to change at page 18, line 34
fiberSwitch(200) fiberSwitch(200)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies link multiplex capability of the "This attribute specifies link multiplex capability of the
TE link, which is derived from its component links. All TE link, which is derived from its component links. All
component links within the same TE link must have the component links within the same TE link must have the
same link multiplex capability." same link multiplex capability."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkEntry 5 } ::= { teLinkEntry 5 }
teLinkProtectionType OBJECT-TYPE teLinkProtectionType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
extraTraffic(1), extraTraffic(1),
unprotected(2), unprotected(2),
shared(3), shared(3),
dedicated1For1(4), dedicated1For1(4),
dedicated1Plus1(5), dedicated1Plus1(5),
enhanced(6) enhanced(6)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies link protection type of the "This attribute specifies link protection type of the
TE link." TE link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkEntry 6 } ::= { teLinkEntry 6 }
teLinkWorkingPriority OBJECT-TYPE teLinkWorkingPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents a priority value such that a new "This object represents a priority value such that a new
connection with a higher priority, i.e. numerically lower than connection with a higher priority, i.e. numerically lower than
this value, is guaranteed to be setup on a primary link and this value, is guaranteed to be setup on a primary link and
not on a secondary link." not on a secondary link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkEntry 7 } ::= { teLinkEntry 7 }
teLinkResourceClass OBJECT-TYPE teLinkResourceClass OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the TE link resource class. "This attribute specifies the TE link resource class.
The resource class is a 32 bit bitfield. The resource class for The resource class is a 32 bit bitfield. The resource class for
a link bundle is derived from the resource class of its a link bundle is derived from the resource class of its
skipping to change at page 21, line 34 skipping to change at page 19, line 41
teLinkIncomingIfId OBJECT-TYPE teLinkIncomingIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For unnumbered links, the incoming interface is set to the "For unnumbered links, the incoming interface is set to the
outgoing interface identifier chosen by the neighboring LSR outgoing interface identifier chosen by the neighboring LSR
for the reverse link corresponding to this TE link." for the reverse link corresponding to this TE link."
REFERENCE REFERENCE
"draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS "[BUNDLING]"
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002."
::= { teLinkEntry 9 } ::= { teLinkEntry 9 }
teLinkOutgoingIfId OBJECT-TYPE teLinkOutgoingIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the link is unnumbered, the outgoing interface identifier is "If the link is unnumbered, the outgoing interface identifier is
set to the outgoing interface identifier chosen for the TE link set to the outgoing interface identifier chosen for the TE link
by the advertising LSR." by the advertising LSR."
REFERENCE REFERENCE
"draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS "[BUNDLING]"
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002."
::= { teLinkEntry 10 } ::= { teLinkEntry 10 }
teLinkFlooding OBJECT-TYPE teLinkFlooding OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object only has significance for link bundles which "This object only has significance for link bundles which
encoding type is not clear. For these link bundles, this object encoding type is not clear. For these link bundles, this object
identifies the TE link on which to restrict flooding. If the identifies the TE link on which to restrict flooding. If the
value is zero, then flooding must be done on all TE links value is zero, then flooding must be done on all TE links
within the link bundle." within the link bundle."
REFERENCE REFERENCE
"draft-ietf-ospf-isis-flood-opt-01.txt - Flooding optimization "[FLOOD]"
in link-state routing protocols, A. Zinin, M. Shand,
March 2001."
DEFVAL { 0 } DEFVAL { 0 }
::= { teLinkEntry 11 } ::= { teLinkEntry 11 }
teLinkRowStatus OBJECT-TYPE teLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. All read-create objects
skipping to change at page 24, line 8 skipping to change at page 22, line 10
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
fiberChannel(11) fiberChannel(11)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the TE link encoding type." "This attribute specifies the TE link encoding type."
REFERENCE REFERENCE
"draft-ietf-mpls-generalized-signaling-08.txt - Generalized "[GMPLS]"
MPLS Signaling Functional Description, P. Ashwood-Smith,
A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,
E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,
V. Sharma, G. Swallow, Z. Tang, April 2002."
::= { teLinkDescriptorEntry 2 } ::= { teLinkDescriptorEntry 2 }
teLinkDescrPriority OBJECT-TYPE teLinkDescrPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the lowest priority at which that link "This object specifies the lowest priority at which that link
encoding type is available." encoding type is available."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkDescriptorEntry 3 } ::= { teLinkDescriptorEntry 3 }
teLinkMinReservableBandwidth OBJECT-TYPE teLinkMinReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the minimum reservable bandwidth on "This attribute specifies the minimum reservable bandwidth on
the TE link. This is derived from the union of the the TE link. This is derived from the union of the
minimum reservable bandwidth of all the component links minimum reservable bandwidth of all the component links
associated with the TE link that can be used to carry associated with the TE link that can be used to carry
live traffic. This value is an estimate in units of 1,000 bits live traffic. This value is an estimate in units of 1,000 bits
per second." per second."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkDescriptorEntry 4 } ::= { teLinkDescriptorEntry 4 }
teLinkMaxReservableBandwidth OBJECT-TYPE teLinkMaxReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the maximum reservable bandwidth on "This attribute specifies the maximum reservable bandwidth on
the TE link. This is the union of the maximum reservable the TE link. This is the union of the maximum reservable
bandwidth of all the component links within the bandwidth of all the component links within the
TE link that can be used to carry live traffic. This value TE link that can be used to carry live traffic. This value
is an estimate in units of 1,000 bits per second." is an estimate in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkDescriptorEntry 5 } ::= { teLinkDescriptorEntry 5 }
teLinkDescrRowStatus OBJECT-TYPE teLinkDescrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. All read-create objects
can only be changed when teLinkDescrRowStatus is active." can only be changed when teLinkDescrRowStatus is active."
skipping to change at page 26, line 40 skipping to change at page 24, line 29
teLinkOspfLinkId OBJECT-TYPE teLinkOspfLinkId OBJECT-TYPE
SYNTAX RouterID SYNTAX RouterID
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"On point-to-point link, the link identifier is the Router ID "On point-to-point link, the link identifier is the Router ID
of the neighbor. For bundled link, is derived from the link of the neighbor. For bundled link, is derived from the link
identifier associated with its TE links." identifier associated with its TE links."
REFERENCE REFERENCE
"draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS "[BUNDLING]"
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002."
::= { teLinkOspfTeEntry 2 } ::= { teLinkOspfTeEntry 2 }
-- End of teLinkOspfTeTable -- End of teLinkOspfTeTable
-- TE Link Shared Risk Link Group Table -- TE Link Shared Risk Link Group Table
teLinkSrlgTable OBJECT-TYPE teLinkSrlgTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkSrlgEntry SYNTAX SEQUENCE OF TeLinkSrlgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 27, line 38 skipping to change at page 25, line 24
srlgStorageType StorageType srlgStorageType StorageType
} }
srlg OBJECT-TYPE srlg OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This identifies a SRLG supported by the TE link." "This identifies a SRLG supported by the TE link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkSrlgEntry 1 } ::= { teLinkSrlgEntry 1 }
srlgRowStatus OBJECT-TYPE srlgRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. All read-create objects
can only be changed when srlgRowStatus is active." can only be changed when srlgRowStatus is active."
skipping to change at page 29, line 13 skipping to change at page 26, line 44
} }
teLinkPriority OBJECT-TYPE teLinkPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..8) SYNTAX Unsigned32 (1..8)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the priority. It should be mapped "This attribute specifies the priority. It should be mapped
to a number between 0 and 7" to a number between 0 and 7"
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { teLinkBandwidthEntry 1 } ::= { teLinkBandwidthEntry 1 }
teLinkUnreservedBandwidth OBJECT-TYPE teLinkUnreservedBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the TE link unreserved "This attribute specifies the TE link unreserved
bandwidth at priority p. It is the sum of the unreserved bandwidth at priority p. It is the sum of the unreserved
bandwidths at priority p of all component links associated bandwidths at priority p of all component links associated
with the TE link (excludes all links that are strictly with the TE link (excludes all links that are strictly
used as protecting links). This value is an estimate in units used as protecting links). This value is an estimate in units
of 1,000 bits per second." of 1,000 bits per second."
REFERENCE REFERENCE
"draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS "[BUNDLING]"
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002."
::= { teLinkBandwidthEntry 2 } ::= { teLinkBandwidthEntry 2 }
teLinkMaximumLspBandwidth OBJECT-TYPE teLinkMaximumLspBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the TE link maximum "This attribute specifies the TE link maximum
LSP bandwidth at priority p. It is the maximum of all LSP bandwidth at priority p. It is the maximum of all
maximum LSP bandwidth at priority p of the component links maximum LSP bandwidth at priority p of the component links
associated with the TE link (excludes all links that are associated with the TE link (excludes all links that are
strictly used as protecting links). This value is an estimate strictly used as protecting links). This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS "[BUNDLING]"
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002."
::= { teLinkBandwidthEntry 3 } ::= { teLinkBandwidthEntry 3 }
teLinkBandwidthRowStatus OBJECT-TYPE teLinkBandwidthRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. All read-create objects
can only be changed when teLinkBandwidthRowStatus is active." can only be changed when teLinkBandwidthRowStatus is active."
skipping to change at page 31, line 31 skipping to change at page 29, line 7
tdm(100), tdm(100),
lambdaSwitch(150), lambdaSwitch(150),
fiberSwitch(200) fiberSwitch(200)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies link multiplexing capabilities of the "This attribute specifies link multiplexing capabilities of the
component link." component link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { componentLinkEntry 1 } ::= { componentLinkEntry 1 }
componentLinkPreferredProtection OBJECT-TYPE componentLinkPreferredProtection OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
primary(1), primary(1),
secondary(2) secondary(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 33, line 48 skipping to change at page 31, line 21
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
fiberChannel(11) fiberChannel(11)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the component link encoding type." "This attribute specifies the component link encoding type."
REFERENCE REFERENCE
"draft-ietf-mpls-generalized-signaling-08.txt - Generalized "[GMPLS]"
MPLS Signaling Functional Description, P. Ashwood-Smith,
A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,
E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,
V. Sharma, G. Swallow, Z. Tang, April 2002."
::= { componentLinkDescriptorEntry 2 } ::= { componentLinkDescriptorEntry 2 }
componentLinkDescrPriority OBJECT-TYPE componentLinkDescrPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the lowest priority at which that link "This object specifies the lowest priority at which that link
encoding type is available for the component link." encoding type is available for the component link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { componentLinkDescriptorEntry 3 } ::= { componentLinkDescriptorEntry 3 }
componentLinkMinReservBandwidth OBJECT-TYPE componentLinkMinReservBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the minimum reservable bandwidth on "This attribute specifies the minimum reservable bandwidth on
the component link. This value is an estimate the component link. This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { componentLinkDescriptorEntry 4 } ::= { componentLinkDescriptorEntry 4 }
componentLinkMaxReservBandwidth OBJECT-TYPE componentLinkMaxReservBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the maximum reservable bandwidth on "This attribute specifies the maximum reservable bandwidth on
the component link. This value is an estimate the component link. This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { componentLinkDescriptorEntry 5 } ::= { componentLinkDescriptorEntry 5 }
componentLinkDescrRowStatus OBJECT-TYPE componentLinkDescrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. All read-create objects
can only be changed when componentLinkDescrRowStatus can only be changed when componentLinkDescrRowStatus
skipping to change at page 36, line 23 skipping to change at page 33, line 30
} }
componentLinkPriority OBJECT-TYPE componentLinkPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..8) SYNTAX Unsigned32 (1..8)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the priority. It should be mapped "This attribute specifies the priority. It should be mapped
to a number between 0 and 7." to a number between 0 and 7."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { componentLinkBandwidthEntry 1 } ::= { componentLinkBandwidthEntry 1 }
componentLinkUnreservedBandwidth OBJECT-TYPE componentLinkUnreservedBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the component link unreserved "This attribute specifies the component link unreserved
bandwidth at priority p. This value is an estimate bandwidth at priority p. This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OPSF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { componentLinkBandwidthEntry 2 } ::= { componentLinkBandwidthEntry 2 }
componentLinkMaximumLspBandwidth OBJECT-TYPE componentLinkMaximumLspBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the component link maximum "This attribute specifies the component link maximum
LSP bandwidth at priority p. This value is an estimate LSP bandwidth at priority p. This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "[GMPLS-OSPF]"
in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002."
::= { componentLinkBandwidthEntry 3 } ::= { componentLinkBandwidthEntry 3 }
componentLinkBandwidthRowStatus OBJECT-TYPE componentLinkBandwidthRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects can only delete a row in this table. All read-create objects can only
be changed when componentLinkBandwidthRowStatus is active." be changed when componentLinkBandwidthRowStatus is active."
skipping to change at page 50, line 25 skipping to change at page 47, line 24
NOTIFICATIONS { linkBundleMismatch } NOTIFICATIONS { linkBundleMismatch }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. "Set of notifications implemented in this module.
None is mandatory." None is mandatory."
::= { linkBundlingGroups 6 } ::= { linkBundlingGroups 6 }
-- End of LINK-BUNDLING-MIB -- End of LINK-BUNDLING-MIB
END END
11. Security Considerations 11. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to per-
tain to the implementation or use of the technology described in this
document or the extent to which any license under such rights might
or might not be available; neither does it represent that it has made
any effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses
to be made available, or the result of an attempt made to obtain a
general license or permission for the use of such proprietary rights
by implementers or users of this specification can be obtained from
the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
12. Security Considerations
It is clear that this MIB is potentially useful for monitoring of It is clear that this MIB is potentially useful for monitoring of
link bundling enabled devices. This MIB can also be used for confi- link bundling enabled devices. This MIB can also be used for configu-
guration of certain objects, and anything that can be configured can ration of certain objects, and anything that can be configured can be
be incorrectly configured, with potentially disastrous results. incorrectly configured, with potentially disastrous results.
At this writing, no security holes have been identified beyond those At this writing, no security holes have been identified beyond those
that SNMP Security [RFC2571] is itself intended to address. These that SNMP Security [RFC2571] is itself intended to address. These
relate to primarily controlled access to sensitive information and relate to primarily controlled access to sensitive information and
the ability to configure a device - or which might result from opera- the ability to configure a device - or which might result from opera-
tor error, which is beyond the scope of any security architecture. tor error, which is beyond the scope of any security architecture.
There are a number of management objects defined in this MIB which There are a number of management objects defined in this MIB which
have a MAX-ACCESS clause of read-write and/or read-create. Such have 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
skipping to change at page 51, line 17 skipping to change at page 48, line 36
Control [RFC2575] is recommended. It is then a customer/user respon- Control [RFC2575] is recommended. It is then a customer/user respon-
sibility to ensure that the SNMP entity giving access to an instance sibility to ensure that the SNMP entity giving access to an instance
of this MIB is properly configured to give access to the objects only of this MIB is properly configured to give access to the objects only
to those principals (users) that have legitimate rights to indeed GET to those principals (users) that have legitimate rights to indeed GET
or SET (change/create/delete) them. or SET (change/create/delete) them.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective, in information that may be sensitive from a business perspective, in
that they can be used to derive the network topology, e.g. list of that they can be used to derive the network topology, e.g. list of
nodes and their IP address (teLinkTable), list of component links nodes and their IP address (teLinkTable), list of component links
(componentLinkTable) in addition to usage of network resources (teL- (componentLinkTable) in addition to usage of network resources
inkBandwidthTable and componentLinkBandwidthTable). Allowing uncon- (teLinkBandwidthTable and componentLinkBandwidthTable). Allowing
trolled access to these objects could result in malicious and uncontrolled access to these objects could result in malicious and
unwanted disruptions of network traffic, incorrect network configura- unwanted disruptions of network traffic, incorrect network configura-
tion or theft of competitive business information. There are no tion or theft of competitive business information. There are no
objects that are particularly sensitive in their own right, such as objects that are particularly sensitive in their own right, such as
passwords or monetary amounts. passwords or monetary amounts.
12. Acknowledgments 13. Acknowledgments
The general structure of this draft has been modeled around draft- The general structure of this draft has been modeled around draft-
ietf-mpls-lsr-mib-06.txt. The authors would like to acknowlegde the ietf-mpls-lsr-mib-06.txt. The authors would like to acknowlegde the
contribution of Dmitry Ryumkin. contribution of Dmitry Ryumkin.
13. References 14. References
14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[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.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, 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.
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.iana.org/assignments/smi-numbers
[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002.
[FLOOD] Zinin, A., and Shand, M., "Flooding optimization
in link-state routing protocols, Internet Draft
<draft-ietf-ospf-isis-flood-opt-01.txt>,
March 2001."
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Functional Description",
Internet Draft
<draft-ietf-mpls-generalized-signaling-09.txt>,
August 2002.
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", Internet
Draft <draft-ietf-ccamp-ospf-gmpls-extensions-08.txt>,
August 2002.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS, (http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers),
for MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Rajagopalan, B.,
Basak, D., Sandick, H., Zinin, A.,
Rajagopalan, B., and Ramamoorthi, S.,
"Link Management Protocol",
Internet Draft <draft-ccamp-lmp-06.txt>,
September 2002.
[OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic
Engineering Extensions to OSPF", Internet Draft
<draft-katz-yeung-ospf-traffic-09.txt>, October 2002.
14.2. Informative References
[RFC1155] Rose, M., and K. McCloghrie, "Structure and [RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP- Identification of Management Information for TCP/IP-
based Internets", STD 16, RFC 1155, May 1990. based Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157, "Simple Network Management Protocol", STD 15, RFC 1157,
May 1990. May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
skipping to change at page 52, line 14 skipping to change at page 51, line 11
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, Network Management Protocol (SNMPv2)", RFC 1905,
January 1996. January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999. Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999. Frameworks", RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
skipping to change at page 52, line 45 skipping to change at page 51, line 35
Applications", RFC 2573, April 1999. Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April 1999. Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. 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.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, 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.
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.iana.org/assignments/smi-numbers
[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-03.txt>,
May 2002.
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Functional Description",
Internet Draft
<draft-ietf-mpls-generalized-signaling-08.txt>,
April 2002.
[GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D.,
Banarjee, A., Basak, D., Berger, L., Bernstein, G., Banarjee, A., Basak, D., Berger, L., Bernstein, G.,
Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., Dharanikota, S., Drake, J., Fan, Y., Fedyk, D.,
Grammel, G., Guo, D., Kompella, K., Kullberg, A., Grammel, G., Guo, D., Kompella, K., Kullberg, A.,
Lang, J., Liaw, F., Nadeau, T., Ong, L., Lang, J., Liaw, F., Nadeau, T., Ong, L.,
Papadimitriou, D., Pendarakis, D., Rajagopalan, B., Papadimitriou, D., Pendarakis, D., Rajagopalan, B.,
Rekhter, Y., Saha, D., Sandick, H., Sharma, V., Rekhter, Y., Saha, D., Sandick, H., Sharma, V.,
Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J.,
Zinin, A., "Generalized Multi-Protocol Label Switching Zinin, A., "Generalized Multi-Protocol Label Switching
(GMPLS) Architecture", Internet Draft (GMPLS) Architecture", Internet Draft
<draft-ietf-ccamp-gmpls-architecture-02.txt>, <draft-ietf-ccamp-gmpls-architecture-03.txt>,
March 2002. August 2002.
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", Internet
Draft
<draft-ietf-ccamp-ospf-gmpls-extensions-07.txt>,
May 2002.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS, (http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers),
for MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Rajagopalan, B.,
Basak, D., Sandick, H., Zinin, A., and
Banarjee, A., "Link Management Protocol",
Internet Draft <draft-ccamp-lmp-03.txt>,
March 2002.
[OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to
OSPF", Internet Draft
<draft-katz-yeung-ospf-traffic-06.txt>, October 2001.
14. Authors' Addresses 15. Authors' Addresses
Martin Dubuc Thomas D. Nadeau Martin Dubuc Thomas D. Nadeau
Meriton Networks Cisco Systems, Inc. Email: dubuc.consulting@rogers.com Cisco Systems, Inc.
3026 Solandt Road 300 Apollo Drive
Kanata, ON, CANADA K2K 2A5 Chelmsford, MA 01824 300 Apollo Drive
Phone: +1-613-270-9279 x253 Phone: +1-978-244-3051 Chelmsford, MA 01824
Email: martin.dubuc@meriton.com Email: tnadeau@cisco.com Phone: +1-978-244-3051
Email: tnadeau@cisco.com
Sudheer Dharanikota Jonathan P. Lang Sudheer Dharanikota Jonathan P. Lang
Nayna Networks, Inc. Calient Networks, Inc. Email: sudheer@ieee.org Calient Networks, Inc.
157 Topaz Street 25 Castilian Drive 25 Castilian Drive
Milipitas, CA 95035 Goleta, CA 93117 Goleta, CA 93117
Phone: +1-408-956-8000 x357 Email: jplang@calient.net Email: jplang@calient.net
Email: sudheer@nayna.com
15. Full Copyright Statement 16. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this docu- included on all such copies and derivative works. However, this docu-
ment itself may not be modified in any way, such as by removing the ment itself may not be modified in any way, such as by removing the
 End of changes. 

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