draft-ietf-mpls-bundle-mib-02.txt   draft-ietf-mpls-bundle-mib-03.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Meriton Networks Internet Draft Meriton Networks
Expires: November 2002 Expires: December 2002
Sudheer Dharanikota Sudheer Dharanikota
Nayna Networks Nayna Networks
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Calient Networks Calient Networks
May 2002 June 2002
Link Bundling Management Information Base Link Bundling Management Information Base
draft-ietf-mpls-bundle-mib-02.txt draft-ietf-mpls-bundle-mib-03.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 2, line 13 skipping to change at page 2, line 13
5. Feature Checklist ............................................ 4 5. Feature Checklist ............................................ 4
6. Outline ...................................................... 5 6. Outline ...................................................... 5
6.1. Summary of Link Bundling MIB ................................. 5 6.1. Summary of Link Bundling MIB ................................. 5
7. Brief Description of MIB Objects ............................. 6 7. Brief Description of MIB Objects ............................. 6
7.1. teLinkTable .................................................. 6 7.1. teLinkTable .................................................. 6
7.2. teLinkDescriptorTable ........................................ 6 7.2. teLinkDescriptorTable ........................................ 6
7.3. teLinkOspfTeTable ............................................ 6 7.3. teLinkOspfTeTable ............................................ 6
7.4. teLinkSrlgTable .............................................. 6 7.4. teLinkSrlgTable .............................................. 6
7.5. teLinkBandwidthTable ......................................... 7 7.5. teLinkBandwidthTable ......................................... 7
7.6. dataBearingChannelTable ...................................... 7 7.6. componentLinkTable ........................................... 7
7.7. dataBearingChannelDescriptorTable ............................ 7 7.7. componentLinkDescriptorTable ................................. 7
7.8. dataBearingChannelBandwidthTable ............................. 7 7.8. componentLinkBandwidthTable .................................. 7
8. Example of Bundled Link Setup ................................ 7 8. Example of Bundled Link Setup ................................ 7
9. Application of the Interfaces Group to TE Links .............. 11 9. Application of the Interfaces Group to TE Links .............. 11
9.1 Support of the TE Link Layer by ifTable ...................... 12 9.1 Support of the TE Link Layer by ifTable ...................... 12
9.2 Using ifStackTable ........................................... 13 9.2 Using ifStackTable ........................................... 13
10. Link Bundling MIB Definitions ................................ 15 10. Link Bundling MIB Definitions ................................ 15
11. Security Considerations ...................................... 50 11. Security Considerations ...................................... 50
12. Acknowledgments .............................................. 51 12. Acknowledgments .............................................. 51
13. References ................................................... 51 13. References ................................................... 51
14. Authors' Addresses ........................................... 54 14. Authors' Addresses ........................................... 54
15. Full Copyright Statement ..................................... 54 15. Full Copyright Statement ..................................... 54
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Informa- This memo defines a portion of the Management Information Base (MIB)
tion Base (MIB) for use with network management protocols in the for use with network management protocols in the Internet community.
Internet community. In particular, it describes managed objects for In particular, it describes managed objects for modeling link bun-
modeling link bundling as described in [BUNDLING]. dling as described in the Link Bundling in MPLS Traffic Engineering
Internet Draft.
2. Introduction 2. Introduction
OSPF, G-MPLS and LMP use the concept of traffic engineering (TE) OSPF [OSPF], Generalized MPLS (GMPLS) [GMPLS] and the Link Management
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.
We present in this document a MIB that can be used to manage TE links We present in this document a MIB that can be used to manage TE links
and their extension, the bundled link. This MIB enable both the con- and their extension, the bundled link. This MIB enable both the con-
figuration and the performance monitoring of TE links and bundled figuration and the performance monitoring of TE links and bundled
link. link.
Comments should be made directly to the MPLS mailing list at
mpls@uu.net.
This memo does not, in its draft form, specify a standard for the
Internet community.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference document are to be interpreted as described in RFC 2119, reference
[BCP14]. [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
traffic. A TE Link may be comprised of only one underlying data- traffic. A TE Link may be comprised of only one underlying component
bearing channels. In cases where more than one data-bearing channel links. In cases where more than one component link is to be com-
is to be combined, multiple data-bearing links should be created with bined, multiple component links should be created with differing
differing priorities to indicate hot-standby or parallel utilization. priorities 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. Furth-
ermore, if there are more than one TE link in a link bundle at some ermore, 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.
skipping to change at page 5, line 8 skipping to change at page 5, line 5
The link bundling MIB (LINK-BUNDLING-MIB) is designed to satisfy the The link bundling MIB (LINK-BUNDLING-MIB) is designed to satisfy the
following requirements and constraints: following requirements and constraints:
- The MIB supports the management of TE links, including bundled - The MIB supports the management of TE links, including bundled
links. links.
- Support is provided for configuration of traffic engineering - Support is provided for configuration of traffic engineering
parameters associated with TE links. parameters associated with TE links.
- The MIB is used to monitor the priority-based data-bearing channel - The MIB is used to monitor the priority-based component link
and TE link bandwidth values. and TE link bandwidth values.
6. Outline 6. Outline
Configuring bundled links involves the following steps: Configuring bundled links involves the following steps:
- Creating a bundled link. - Creating a bundled link.
- Creating TE links. - Creating TE links.
- Optionally specifying the shared risk link groups associated with - Optionally specifying the shared risk link groups associated with
the TE links. the TE links.
- Configuring the data-bearing channels including the bandwidth - Configuring the component links including the bandwidth
parameters and associating the data-bearing channels with the parameters and associating the component links with the
appropriate TE link. appropriate TE link.
- Associating the TE links with the appropriate bundled link. - Associating the TE links with the appropriate bundled link.
6.1. Summary of Link Bundling MIB 6.1. Summary of Link Bundling MIB
The MIB objects for performing these actions consist of the following The MIB objects for performing these actions consist of the following
tables: tables:
- The TE link table (teLinkTable), which is used to - The TE link table (teLinkTable), which is used to
skipping to change at page 6, line 6 skipping to change at page 5, line 48
(teLinkOspfTeTable), which is used for configuring OSPF (teLinkOspfTeTable), which is used for configuring OSPF
traffic engineering parameters associated with TE links. traffic engineering parameters associated with TE links.
- The shared risk link group (SRLG) table (teLinkSrlgTable), - The shared risk link group (SRLG) table (teLinkSrlgTable),
which is used to specify the SRLGs associated with TE links. which is used to specify the SRLGs associated with TE links.
- The TE link bandwidth table (teLinkBandwidthTable), - The TE link bandwidth table (teLinkBandwidthTable),
which is used for reporting priority-based bandwidth values which is used for reporting priority-based bandwidth values
associated with TE links. associated with TE links.
- The data-bearing channel table (dataBearingChannelTable), which is - The component link table (componentLinkTable), which is
used to identify the data-bearing channels that are associated used to identify the component links that are associated
with the TE links and specify the data-bearing channel generic with the TE links and specify the component link generic
traffic engineering parameters. traffic engineering parameters.
- The data-bearing channel link descriptor table - The component link descriptor table
(dataBearingChannelDescriptorTable), which is used to enumerate (componentLinkDescriptorTable), which is used to enumerate
the data-bearing channel link descriptors. the component link descriptors.
- The data-bearing channel bandwidth table - The component link bandwidth table
(dataBearingChannelBandwidthTable), which is used to report (componentLinkBandwidthTable), which is used to report
priority-based bandwidth values associated with data-bearing priority-based bandwidth values associated with component links.
channels.
These tables are described in the subsequent sections. These tables are described in the subsequent sections.
7. Brief Description of MIB Objects 7. Brief Description of MIB Objects
Sections 7.1-7.5 describe objects pertaining to TE links. The MIB Sections 7.1-7.5 describe objects pertaining to TE links. The MIB
objects were derived from the link bundling document [BUNDLING]. objects were derived from the link bundling document [BUNDLING].
7.1. teLinkTable 7.1. teLinkTable
skipping to change at page 7, line 11 skipping to change at page 7, line 10
7.4. teLinkSrlgTable 7.4. teLinkSrlgTable
This table represents the shared risk link groups (SRLGs) associated This table represents the shared risk link groups (SRLGs) associated
with TE links. with TE links.
7.5. teLinkBandwidthTable 7.5. teLinkBandwidthTable
This table specifies the priority-based bandwidth traffic engineering This table specifies the priority-based bandwidth traffic engineering
parameters associated with TE links. parameters associated with TE links.
7.6. dataBearingChannelTable 7.6. componentLinkTable
This table enumerates the data-bearing channels and their association This table enumerates the component links and their association with
with TE link. TE link.
7.7. dataBearingChannelDescriptorTable 7.7. componentLinkDescriptorTable
This table enumerates the link descriptors that each data-bearing This table enumerates the link descriptors that each component link
channel supports. supports.
7.8. dataBearingChannelBandwidthTable 7.8. componentLinkBandwidthTable
The data-bearing channel bandwidth table specifies the priority-based The component link bandwidth table specifies the priority-based
bandwidth values associated with the data-bearing channels. bandwidth 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.
Suppose that one would like to manually create a bundled link Suppose that one would like to manually create a bundled link
out of two 1:1 TE links. Assume that the bundled link is associated out of two 1:1 TE links. Assume that the bundled link is associated
with SRLGs 10 and 50. Finally, let the data-bearing channels be port with SRLGs 10 and 50. Finally, let the component links be port
entity interfaces (lambdas). The following example illustrates which entity interfaces (lambdas). The following example illustrates which
rows and corresponding objects might be created to accomplish this. rows and corresponding objects might be created to accomplish this.
First, a bundled link entry is created. An ifEntry with the same First, a bundled link entry is created. An ifEntry with the same
ifIndex and with ifType teLink needs to be created beforehand. ifIndex and with ifType teLink needs to be created beforehand.
In teLinkTable: In teLinkTable:
{ {
ifIndex = 25, ifIndex = 25,
teLinkIpAddrType = unknown(0), teLinkIpAddrType = unknown(0),
skipping to change at page 9, line 42 skipping to change at page 9, line 38
In the teLinkSrlgTable: In the teLinkSrlgTable:
{ {
ifIndex = 21, ifIndex = 21,
srlg = 50, srlg = 50,
srlgRowStatus = createAndGo(4) srlgRowStatus = createAndGo(4)
} }
The bundled link inherits the OSPF and SRLG properties from the The bundled link inherits the OSPF and SRLG properties from the
associated TE links. associated TE links.
Next, for each TE link, two data-bearing channels are created. Next, for each TE link, two component links are created.
An ifEntry with the same ifIndex needs to be created beforehand. An ifEntry with the same ifIndex needs to be created beforehand.
In dataBearingChannelTable: In componentLinkTable:
{ {
ifIndex = 40, ifIndex = 40,
dataBearingChannelPreferredProtection = primary(1), componentLinkPreferredProtection = primary(1),
dataBearingChannelRowStatus = createAndGo(4) componentLinkRowStatus = createAndGo(4)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 20, ifStackHigherLayer = 20,
ifStackLowerLayer = 40, ifStackLowerLayer = 40,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In dataBearingChannelTable: In componentLinkTable:
{ {
ifIndex = 43, ifIndex = 43,
dataBearingChannelPreferredProtection = secondary(2), componentLinkPreferredProtection = secondary(2),
dataBearingChannelRowStatus = createAndGo(4) componentLinkRowStatus = createAndGo(4)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 20, ifStackHigherLayer = 20,
ifStackLowerLayer = 43, ifStackLowerLayer = 43,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In dataBearingChannelTable: In componentLinkTable:
{ {
ifIndex = 44, ifIndex = 44,
dataBearingChannelPreferredProtection = primary(1), componentLinkPreferredProtection = primary(1),
dataBearingChannelRowStatus = createAndGo(4) componentLinkRowStatus = createAndGo(4)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 21, ifStackHigherLayer = 21,
ifStackLowerLayer = 44, ifStackLowerLayer = 44,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In dataBearingChannelTable: In componentLinkTable:
{ {
ifIndex = 48, ifIndex = 48,
dataBearingChannelPreferredProtection = secondary(2), componentLinkPreferredProtection = secondary(2),
dataBearingChannelRowStatus = createAndGo(4) componentLinkRowStatus = createAndGo(4)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 21, ifStackHigherLayer = 21,
ifStackLowerLayer = 48, ifStackLowerLayer = 48,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In this example, once a data-bearing channel is added to the
dataBearingChannelTable, the associated link descriptors are
implicitly added to the dataBearingChannelDescriptorTable.
TE link link descriptors are derived from their data-bearing channel In this example, once a component link is added to the
link descriptors. componentLinkTable, the associated link descriptors are
implicitly added to the componentLinkDescriptorTable.
TE link link descriptors are derived from their component link
descriptors.
Note that the bandwidth attributes in teLinkDescriptorTable, Note that the bandwidth attributes in teLinkDescriptorTable,
dataBearingChannelDescriptorTable, teLinkBandwidthTable componentLinkDescriptorTable, teLinkBandwidthTable
and dataBearingChannelBandwidthTable are maintained by the and componentLinkBandwidthTable are maintained by the
device according to LSP creation/deletion at different priorities. device according to LSP creation/deletion at different priorities.
The values in the teLinkBandwidthTable are an aggregation The values in the teLinkBandwidthTable are an aggregation
of the values for the data-bearing channels of the TE links and of the values for the component links of the TE links and
the TE links of the bundled link. the TE links of the bundled link.
9. Application of the Interfaces Group to TE Links 9. Application of the Interfaces Group to TE Links
The Interfaces Group [IFMIB] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing TE Link interfaces extensions to the Interfaces Group for managing TE Link interfaces
as logical interfaces. as logical interfaces.
This memo assumes the interpretation of the Interfaces Group to be This memo assumes the interpretation of the Interfaces Group to be
in accordance with [IFMIB] which states that the interfaces table in accordance with [RFC2863] which states that the interfaces table
(ifTable) contains information on the managed resource's (ifTable) contains information on the managed resource's
interfaces and that each sub-layer below the internetwork layer of interfaces and that each sub-layer below the internetwork layer of
a network interface is considered an interface. Thus, the TE Link a network interface is considered an interface. Thus, the TE Link
interface is represented as an entry in the ifTable. The inter- interface is represented as an entry in the ifTable. The inter-
relation of entries in the ifTable is defined by Interfaces Stack relation of entries in the ifTable is defined by Interfaces Stack
Group defined in [IFMIB]. Group defined in [RFC2863].
When using TE Link interfaces, the interface stack table might appear When using TE Link interfaces, the interface stack table might appear
as follows: as follows:
+----------------------------------------+ +----------------------------------------+
| TE link-interface ifType = teLink(200) + | TE link-interface ifType = teLink(200) +
+----------------------------------------+ +----------------------------------------+
| Underlying Layer... + | Underlying Layer... +
+----------------------------------------+ +----------------------------------------+
skipping to change at page 12, line 16 skipping to change at page 12, line 11
Some specific interpretations of ifTable for the TE Link layer Some specific interpretations of ifTable for the TE Link layer
follow. follow.
Object Use for the TE Link layer Object Use for the TE Link layer
ifIndex Each TE Link interface is represented by an ifEntry. ifIndex Each TE Link interface is represented by an ifEntry.
ifDescr Description of the TE Link interface. ifDescr Description of the TE Link interface.
ifType The value that is allocated for TE Link is 200. ifType The value that is allocated for TE Link is 200
[IANAFamily].
ifSpeed The total bandwidth in bits per second for use by ifSpeed The total bandwidth in bits per second for use by
the TE Link layer. the TE Link layer.
ifPhysAddress Unused. ifPhysAddress Unused.
ifAdminStatus This variable indicates the administrator's intent ifAdminStatus This variable indicates the administrator's intent
as to whether TE Link should be enabled, disabled, or as to whether TE Link should be enabled, disabled, or
running in some diagnostic testing mode on this running in some diagnostic testing mode on this
interface. Also see [IFMIB]. interface. Also see [RFC2863].
ifOperStatus This value reflects the actual or operational ifOperStatus This value reflects the actual or operational
status of TE Link on this interface. status of TE Link on this interface.
ifLastChange See [IFMIB]. ifLastChange See [RFC2863].
ifInOctets The number of received octets over the interface, ifInOctets The number of received octets over the interface,
i.e., the number of received octets in all data-bearing i.e., the number of received octets in all component
channels associated with the interface. links associated with the interface.
ifOutOctets The number of transmitted octets over the ifOutOctets The number of transmitted octets over the
interface, i.e., the number of octets transmitted interface, i.e., the number of octets transmitted
over all data-bearing channels associated with the over all component links associated with the
interface. interface.
ifInErrors The number of packets dropped due to ifInErrors The number of packets dropped due to
uncorrectable errors. uncorrectable errors.
ifInUnknownProtos ifInUnknownProtos
The number of received packets discarded during The number of received packets discarded during
packet header validation. packet header validation.
ifOutErrors See [IFMIB]. ifOutErrors See [RFC2863].
ifName Textual name (unique on this system) of the ifName Textual name (unique on this system) of the
interface or an octet string of zero length. interface or an octet string of zero length.
ifLinkUpDownTrapEnable ifLinkUpDownTrapEnable
Default is disabled (2). Default is disabled (2).
ifConnectorPresent ifConnectorPresent
Set to false (2). Set to false (2).
ifHighSpeed See [IFMIB]. ifHighSpeed See [RFC2863].
ifHCInOctets The 64-bit version of ifInOctets; supported if ifHCInOctets The 64-bit version of ifInOctets; supported if
required by the compliance statements in [IFMIB]. required by the compliance statements in [RFC2863].
ifHCOutOctets The 64-bit version of ifOutOctets; supported if ifHCOutOctets The 64-bit version of ifOutOctets; supported if
required by the compliance statements in [IFMIB]. 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 [IFMIB]. See [RFC2863].
Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos,
ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required
if encoding type is clear. For other encoding types, traffic if encoding type is clear. For other encoding types, traffic
counters on a TE link are cumulative for all subinterfaces which it counters on a TE link are cumulative for all subinterfaces which it
binds together. binds together.
9.2. Using ifStackTable 9.2. Using ifStackTable
This section describes by example how to use ifStackTable to This section describes by example how to use ifStackTable to
skipping to change at page 16, line 4 skipping to change at page 15, line 47
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
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 "200205211200Z" -- 21 May 2002 12:00:00 EST LAST-UPDATED "200206211200Z" -- 21 June 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 Postal: Meriton Networks
3026 Solandt Road 3026 Solandt Road
Kanata, ON, CANADA K2K 2A5 Kanata, ON, CANADA K2K 2A5
Tel: +1-613-270-9279 x253 Tel: +1-613-270-9279 x253
Email: martin.dubuc@meriton.com Email: martin.dubuc@meriton.com
Sudheer Dharanikota Sudheer Dharanikota
skipping to change at page 17, line 4 skipping to change at page 16, line 48
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-03.txt>,
May 2002." May 2002."
-- Revision history. -- Revision history.
REVISION REVISION
"200206141200Z" -- 21 June 2002 12:00:00 EST
DESCRIPTION
"Addressed WG chair comments."
REVISION
"200205211200Z" -- 21 May 2002 12:00:00 EST "200205211200Z" -- 21 May 2002 12:00:00 EST
DESCRIPTION DESCRIPTION
"Addressed comments received during Last Call. "Addressed comments received during Last Call.
- Addressed syntax errors reports by smilint. - Addressed syntax errors reports by smilint.
- Reintroduced teLinkIpAddrType. - Reintroduced teLinkIpAddrType.
- Replaced ifIndex in linkBundlingMismatch - Replaced ifIndex in linkBundlingMismatch
notification with TE link endpoint objects." notification with TE link endpoint objects."
REVISION REVISION
"200202261200Z" -- 26 February 2002 12:00:00 EST "200202261200Z" -- 26 February 2002 12:00:00 EST
DESCRIPTION DESCRIPTION
skipping to change at page 17, line 25 skipping to change at page 17, line 26
- Added linkBundlingFullModuleCompliance conformance statement. - Added linkBundlingFullModuleCompliance conformance statement.
- Removed teLinkIpAddrType. Replaced numbered value with - Removed teLinkIpAddrType. Replaced numbered value with
ipV4 and ipV6 values in teLinkNumberingType. ipV4 and ipV6 values in teLinkNumberingType.
- Updated description of all row status and storage type objects. - Updated description of all row status and storage type objects.
- Changed some of the enumerated value to start from 1 instead of 0. - Changed some of the enumerated value to start from 1 instead of 0.
- Updated references." - Updated references."
REVISION REVISION
"200109101200Z" -- 10 September 2001 12:00:00 EST "200109101200Z" -- 10 September 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Removed teLinkRemoteId. Updated teLinkEncodingType and "Removed teLinkRemoteId. Updated teLinkEncodingType and
dataBearingChannelEncodingType values." componentLinkEncodingType values."
REVISION REVISION
"200105221200Z" -- 22 May 2001 12:00:00 EST "200105221200Z" -- 22 May 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Replaced InetAddressIPv4 and InetAddressIPv6 with InetAddress "Replaced InetAddressIPv4 and InetAddressIPv6 with InetAddress
and InetAddrType. Changed description of entries which extend and InetAddrType. Changed description of entries which extend
ifEntry. Made various minor corrections." ifEntry. Made various minor corrections."
REVISION REVISION
"200105151200Z" -- 15 May 2001 12:00:00 EST "200105151200Z" -- 15 May 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Replaced componentLinkTable by dataBearingChannelTable. "Replaced componentLinkTable by componentLinkTable.
Replaced linkBundlingTable by teLinkTable. Converted TE links Replaced linkBundlingTable by teLinkTable. Converted TE links
into interfaces." into interfaces."
REVISION REVISION
"200102231200Z" -- 23 February 2001 12:00:00 EST "200102231200Z" -- 23 February 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial draft version." "Initial draft version."
::= { experimental 114 } ::= { experimental 114 } -- See [Assigned]
-- 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
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the grouping of data-bearing channels into "This table specifies the grouping of component links into
TE links and grouping of TE links into bundled links." TE links and grouping of TE links into bundled links."
::= { linkBundlingObjects 1 } ::= { linkBundlingObjects 1 }
teLinkEntry OBJECT-TYPE teLinkEntry OBJECT-TYPE
SYNTAX TeLinkEntry SYNTAX TeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry with an "An entry in this table exists for each ifEntry with an
ifType of teLink(TBD), i.e. for every TE link. An ifEntry ifType of teLink(TBD), i.e. for every TE link. An ifEntry
skipping to change at page 19, line 39 skipping to change at page 19, line 39
"The remote IP address associated with the TE link (IPv4 and "The remote IP address associated with the TE link (IPv4 and
IPv6 numbered links)." IPv6 numbered links)."
::= { teLinkEntry 3 } ::= { teLinkEntry 3 }
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 data-bearing channels. All data-bearing derived from its component links. All component links
channels 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 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002." May 2002."
::= { teLinkEntry 4 } ::= { teLinkEntry 4 }
teLinkMuxCapability OBJECT-TYPE teLinkMuxCapability OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
packetSwitch1(1), packetSwitch1(1),
skipping to change at page 20, line 14 skipping to change at page 20, line 14
packetSwitch4(4), packetSwitch4(4),
layer2Switch(51), layer2Switch(51),
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 multiplex capability of the "This attribute specifies link multiplex capability of the
TE link, which is derived from its data-bearing channels. All TE link, which is derived from its component links. All
data-bearing channels 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { teLinkEntry 5 } ::= { teLinkEntry 5 }
teLinkProtectionType OBJECT-TYPE teLinkProtectionType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 21, line 4 skipping to change at page 21, line 4
D. Saha, V. Sharma, May 2002." 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 channel and this value, is guaranteed to be setup on a primary link and
not on a secondary channel." not on a secondary link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." 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
skipping to change at page 24, line 36 skipping to change at page 24, line 36
D. Saha, V. Sharma, May 2002." 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 data-bearing minimum reservable bandwidth of all the component links
channels 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." 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 data-bearing channels 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { teLinkDescriptorEntry 5 } ::= { teLinkDescriptorEntry 5 }
teLinkDescrRowStatus OBJECT-TYPE teLinkDescrRowStatus OBJECT-TYPE
skipping to change at page 29, line 26 skipping to change at page 29, line 26
D. Saha, V. Sharma, May 2002." 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 data-bearing channel associated bandwidths at priority p of all component links associated
with the TE link (excludes all channels that are strictly with the TE link (excludes all links that are strictly
used as protecting channels). 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 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002." 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 data-bearing channels maximum LSP bandwidth at priority p of the component links
associated with the TE link (excludes all channels that are associated with the TE link (excludes all links that are
strictly used as protecting channels). 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 "draft-ietf-mpls-bundle-03.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
May 2002." May 2002."
::= { teLinkBandwidthEntry 3 } ::= { teLinkBandwidthEntry 3 }
teLinkBandwidthRowStatus OBJECT-TYPE teLinkBandwidthRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 30, line 28 skipping to change at page 30, line 28
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
teLinkBandwidthTable. Conceptual rows having the value teLinkBandwidthTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
columnar object in the row." columnar object in the row."
::= { teLinkBandwidthEntry 5 } ::= { teLinkBandwidthEntry 5 }
-- End of teLinkBandwidthTable -- End of teLinkBandwidthTable
-- Component Link Table
dataBearingChannelTable OBJECT-TYPE componentLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF DataBearingChannelEntry SYNTAX SEQUENCE OF ComponentLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the data-bearing channel "This table specifies the component link parameters."
parameters."
::= { linkBundlingObjects 6 } ::= { linkBundlingObjects 6 }
dataBearingChannelEntry OBJECT-TYPE componentLinkEntry OBJECT-TYPE
SYNTAX DataBearingChannelEntry SYNTAX ComponentLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry that represents "An entry in this table exists for each ifEntry that represents
a data-bearing channel. An ifEntry must exist in the ifTable a component link. An ifEntry must exist in the ifTable
before a dataBearingChannelEntry is created with the before a componentLinkEntry is created with the
corresponding ifIndex. If an entry representing a data-bearing corresponding ifIndex. If an entry representing a component
channel is destroyed in the ifTable, then so is the link is destroyed in the ifTable, then so is the
corresponding entry in the dataBearingChannelTable. The corresponding entry in the componentLinkTable. The
administrative and operational status values are controlled administrative and operational status values are controlled
from the ifEntry." from the ifEntry."
INDEX { ifIndex } INDEX { ifIndex }
::= { dataBearingChannelTable 1 } ::= { componentLinkTable 1 }
DataBearingChannelEntry ::= SEQUENCE { ComponentLinkEntry ::= SEQUENCE {
dataBearingChannelLinkMuxCapability INTEGER, componentLinkMuxCapability INTEGER,
dataBearingChannelPreferredProtection INTEGER, componentLinkPreferredProtection INTEGER,
dataBearingChannelCurrentProtection INTEGER, componentLinkCurrentProtection INTEGER,
dataBearingChannelRowStatus RowStatus, componentLinkRowStatus RowStatus,
dataBearingChannelStorageType StorageType componentLinkStorageType StorageType
} }
dataBearingChannelLinkMuxCapability OBJECT-TYPE componentLinkMuxCapability 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),
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
data-bearing channel." component link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { dataBearingChannelEntry 1 } ::= { componentLinkEntry 1 }
dataBearingChannelPreferredProtection 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
"This attribute specifies whether this data-bearing channel is "This attribute specifies whether this component link is
a primary or secondary entity." a primary or secondary entity."
::= { dataBearingChannelEntry 2 } ::= { componentLinkEntry 2 }
dataBearingChannelCurrentProtection OBJECT-TYPE componentLinkCurrentProtection OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
primary(1), primary(1),
secondary(2) secondary(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies whether this data-bearing channel is "This attribute specifies whether this component link is
currently used as primary or secondary channel." currently used as primary or secondary link."
::= { dataBearingChannelEntry 3 } ::= { componentLinkEntry 3 }
dataBearingChannelRowStatus OBJECT-TYPE componentLinkRowStatus 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 dataBearingChannelRowStatus is active." can only be changed when componentLinkRowStatus is active."
::= { dataBearingChannelEntry 4 } ::= { componentLinkEntry 4 }
dataBearingChannelStorageType OBJECT-TYPE componentLinkStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
dataBearingChannelTable. Conceptual rows having the value componentLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
columnar object in the row." columnar object in the row."
::= { dataBearingChannelEntry 5 } ::= { componentLinkEntry 5 }
-- End of componentLinkTable
-- Component Link Descriptor Table
dataBearingChannelDescriptorTable OBJECT-TYPE componentLinkDescriptorTable OBJECT-TYPE
SYNTAX SEQUENCE OF DataBearingChannelDescriptorEntry SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the link descriptors associated with the "This table specifies the link descriptors associated with the
data-bearing channels." component links."
::= { linkBundlingObjects 7 } ::= { linkBundlingObjects 7 }
dataBearingChannelDescriptorEntry OBJECT-TYPE componentLinkDescriptorEntry OBJECT-TYPE
SYNTAX DataBearingChannelDescriptorEntry SYNTAX ComponentLinkDescriptorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created for every data-bearing channel "An entry in this table is created for every component link
descriptor. An ifEntry in the ifTable must exist before a descriptor. An ifEntry in the ifTable must exist before a
dataBearingChannelDescriptorEntry using the same ifIndex is created. componentLinkDescriptorEntry using the same ifIndex is created.
If a data-bearing channel entry in the ifTable is destroyed, If a component link entry in the ifTable is destroyed,
then so are all entries in the then so are all entries in the componentLinkDescriptorTable
dataBearingChannelDescriptorTable that use the ifIndex of that use the ifIndex of this component link."
this data-bearing channel." INDEX { ifIndex, componentLinkDescrId }
INDEX { ifIndex, dataBearingChannelDescrId } ::= { componentLinkDescriptorTable 1 }
::= { dataBearingChannelDescriptorTable 1 }
DataBearingChannelDescriptorEntry ::= SEQUENCE { ComponentLinkDescriptorEntry ::= SEQUENCE {
dataBearingChannelDescrId Unsigned32, componentLinkDescrId Unsigned32,
dataBearingChannelEncodingType INTEGER, componentLinkEncodingType INTEGER,
dataBearingChannelDescrPriority Unsigned32, componentLinkDescrPriority Unsigned32,
dataBearingChannelMinReservableBandwidth Unsigned32, componentLinkMinReservBandwidth Unsigned32,
dataBearingChannelMaxReservableBandwidth Unsigned32, componentLinkMaxReservBandwidth Unsigned32,
dataBearingChannelDescrRowStatus RowStatus, componentLinkDescrRowStatus RowStatus,
dataBearingChannelDescrStorageType StorageType componentLinkDescrStorageType StorageType
} }
dataBearingChannelDescrId OBJECT-TYPE componentLinkDescrId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the link descriptor identifier." "This object specifies the link descriptor identifier."
::= { dataBearingChannelDescriptorEntry 1 } ::= { componentLinkDescriptorEntry 1 }
dataBearingChannelEncodingType OBJECT-TYPE componentLinkEncodingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
packet(1), packet(1),
ethernet(2), ethernet(2),
ansiEtsiPdh(3), ansiEtsiPdh(3),
sdhItuSonetAnsi(5), sdhItuSonetAnsi(5),
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 data-bearing channel encoding type." "This attribute specifies the component link encoding type."
REFERENCE REFERENCE
"draft-ietf-mpls-generalized-signaling-08.txt - Generalized "draft-ietf-mpls-generalized-signaling-08.txt - Generalized
MPLS Signaling Functional Description, P. Ashwood-Smith, MPLS Signaling Functional Description, P. Ashwood-Smith,
A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,
E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,
V. Sharma, G. Swallow, Z. Tang, April 2002." V. Sharma, G. Swallow, Z. Tang, April 2002."
::= { dataBearingChannelDescriptorEntry 2 } ::= { componentLinkDescriptorEntry 2 }
dataBearingChannelDescrPriority 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 data-bearing channel." encoding type is available for the component link."
REFERENCE REFERENCE
"draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { dataBearingChannelDescriptorEntry 3 } ::= { componentLinkDescriptorEntry 3 }
dataBearingChannelMinReservableBandwidth 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 data-bearing channel. 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { dataBearingChannelDescriptorEntry 4 } ::= { componentLinkDescriptorEntry 4 }
dataBearingChannelMaxReservableBandwidth 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 data-bearing channel. 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { dataBearingChannelDescriptorEntry 5 } ::= { componentLinkDescriptorEntry 5 }
dataBearingChannelDescrRowStatus 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 dataBearingChannelDescrRowStatus can only be changed when componentLinkDescrRowStatus
is active." is active."
::= { dataBearingChannelDescriptorEntry 6 } ::= { componentLinkDescriptorEntry 6 }
dataBearingChannelDescrStorageType OBJECT-TYPE componentLinkDescrStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
dataBearingChannelDescriptorTable. Conceptual rows componentLinkDescriptorTable. Conceptual rows
having the value 'permanent' need not allow write-access having the value 'permanent' need not allow write-access
to any columnar object in the row." to any columnar object in the row."
::= { dataBearingChannelDescriptorEntry 7 } ::= { componentLinkDescriptorEntry 7 }
-- End of componentLinkDescriptorTable
-- Component Link Bandwidth Table
dataBearingChannelBandwidthTable OBJECT-TYPE componentLinkBandwidthTable OBJECT-TYPE
SYNTAX SEQUENCE OF DataBearingChannelBandwidthEntry SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the priority-based bandwidth "This table specifies the priority-based bandwidth
for data-bearing channels." for component links."
::= { linkBundlingObjects 8 } ::= { linkBundlingObjects 8 }
dataBearingChannelBandwidthEntry OBJECT-TYPE componentLinkBandwidthEntry OBJECT-TYPE
SYNTAX DataBearingChannelBandwidthEntry SYNTAX ComponentLinkBandwidthEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table contains information about "An entry in this table contains information about
the priority-based bandwidth on data-bearing channels. the priority-based bandwidth on component links.
An ifEntry in the ifTable must exist before a An ifEntry in the ifTable must exist before a
dataBearingChannelBandwidthEntry using the same ifIndex is componentLinkBandwidthEntry using the same ifIndex is
created. If a data-bearing channel entry in the ifTable is created. If a component link entry in the ifTable is
destroyed, then so are all entries in the destroyed, then so are all entries in the
dataBearingChannelBandwidthTable that use the ifIndex of componentLinkBandwidthTable that use the ifIndex of
this data-bearing channel." this component link."
INDEX { ifIndex, dataBearingChannelPriority } INDEX { ifIndex, componentLinkPriority }
::= { dataBearingChannelBandwidthTable 1 } ::= { componentLinkBandwidthTable 1 }
DataBearingChannelBandwidthEntry ::= SEQUENCE { ComponentLinkBandwidthEntry ::= SEQUENCE {
dataBearingChannelPriority Unsigned32, componentLinkPriority Unsigned32,
dataBearingChannelUnreservedBandwidth Unsigned32, componentLinkUnreservedBandwidth Unsigned32,
dataBearingChannelMaximumLspBandwidth Unsigned32, componentLinkMaximumLspBandwidth Unsigned32,
dataBearingChannelBwRowStatus RowStatus, componentLinkBandwidthRowStatus RowStatus,
dataBearingChannelBwStorageType StorageType componentLinkBwStorageType StorageType
} }
dataBearingChannelPriority 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { dataBearingChannelBandwidthEntry 1 } ::= { componentLinkBandwidthEntry 1 }
dataBearingChannelUnreservedBandwidth 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 data-bearing channel 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { dataBearingChannelBandwidthEntry 2 } ::= { componentLinkBandwidthEntry 2 }
dataBearingChannelMaximumLspBandwidth 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 data-bearing channel 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 "draft-ietf-ccamp-ospf-gmpls-extensions-07.txt - OSPF Extensions
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, in Support of Generalized MPLS, K. Kompella, Y. Rekhter,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
D. Saha, V. Sharma, May 2002." D. Saha, V. Sharma, May 2002."
::= { dataBearingChannelBandwidthEntry 3 } ::= { componentLinkBandwidthEntry 3 }
dataBearingChannelBwRowStatus 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 delete a row in this table. All read-create objects can only
can only be changed when dataBearingChannelBwRowStatus is active." be changed when componentLinkBandwidthRowStatus is active."
::= { dataBearingChannelBandwidthEntry 4 } ::= { componentLinkBandwidthEntry 4 }
dataBearingChannelBwStorageType OBJECT-TYPE componentLinkBwStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
dataBearingChannelBandwidthTable. Conceptual rows componentLinkBandwidthTable. Conceptual rows
having the value 'permanent' need not allow write-access having the value 'permanent' need not allow write-access
to any columnar object in the row." to any columnar object in the row."
::= { dataBearingChannelBandwidthEntry 5 } ::= { componentLinkBandwidthEntry 5 }
-- End of componentLinkBandwidthTable
-- Notification Configuration -- Notification Configuration
linkBundlingNotifEnable OBJECT-TYPE linkBundlingNotifEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this object is true, then it enables the "If this object is true, then it enables the
generation of the link bundling notifications, generation of the link bundling notifications,
skipping to change at page 38, line 42 skipping to change at page 38, line 42
configuration and monitoring of link bundling MIB." configuration and monitoring of link bundling MIB."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented -- The mandatory groups have to be implemented
-- by all devices supporting link bundling. However, they may all -- by all devices supporting link bundling. However, they may all
-- be supported as read-only objects in the case where automatic -- be supported as read-only objects in the case where automatic
-- configuration is supported. -- configuration is supported.
MANDATORY-GROUPS { linkBundlingGroup, MANDATORY-GROUPS { linkBundlingGroup,
teLinkBandwidthGroup, teLinkBandwidthGroup,
dataBearingChannelBandwidthGroup } componentLinkBandwidthGroup }
GROUP teLinkOspfTeGroup GROUP teLinkOspfTeGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for OSPF enabled devices." "This group is mandatory for OSPF enabled devices."
GROUP teLinkSrlgGroup GROUP teLinkSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for G-MPLS enabled devices." "This group is mandatory for G-MPLS enabled devices."
GROUP linkBundlingNotificationGroup GROUP linkBundlingNotificationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for equipment that support "This group is mandatory for equipment that support
link bundling notifications." link bundling notifications."
-- teLinkTable -- teLinkTable
OBJECT teLinkIpAddrType OBJECT teLinkIpAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The dns(16) address type need not be supported. "The dns(16) address type need not be supported.
The ipv4(1) and ipv6(2) address types need not be The ipv4(1) and ipv6(2) address types need not be
supported if numbered links are not supported. The supported if numbered links are not supported. The
unknown(0) address type need not be supported if unknown(0) address type need not be supported if
unnumbered links are not supported." unnumbered links are not supported."
OBJECT teLinkIpAddr OBJECT teLinkIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
skipping to change at page 41, line 40 skipping to change at page 41, line 40
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT teLinkBandwidthStorageType OBJECT teLinkBandwidthStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- dataBearingChannelTable -- componentLinkTable
OBJECT dataBearingChannelLinkMuxCapability OBJECT componentLinkMuxCapability
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelMaxReservableBandwidth OBJECT componentLinkMaxReservBandwidth
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelRowStatus OBJECT componentLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT dataBearingChannelStorageType OBJECT componentLinkStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- dataBearingChannelDescriptorTable -- componentLinkDescriptorTable
OBJECT dataBearingChannelDescrRowStatus OBJECT componentLinkDescrRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) state need not be supported." "The notReady(3) state need not be supported."
OBJECT dataBearingChannelDescrStorageType OBJECT componentLinkDescrStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- dataBearingChannelBandwidthTable -- componentLinkBandwidthTable
OBJECT dataBearingChannelMaximumLspBandwidth OBJECT componentLinkMaximumLspBandwidth
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelBwRowStatus OBJECT componentLinkBandwidthRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT dataBearingChannelBwStorageType OBJECT componentLinkBwStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
::= { linkBundlingCompliances 1 } ::= { linkBundlingCompliances 1 }
linkBundlingMonitoringModuleCompliance MODULE-COMPLIANCE linkBundlingMonModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
monitoring of link bundling MIB." monitoring of link bundling MIB."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented -- The mandatory groups have to be implemented
-- by all devices supporting link bundling. However, they may all -- by all devices supporting link bundling. However, they may all
-- be supported as read-only objects in the case where manual -- be supported as read-only objects in the case where manual
-- configuration is unsupported. -- configuration is unsupported.
MANDATORY-GROUPS { linkBundlingGroup, MANDATORY-GROUPS { linkBundlingGroup,
teLinkBandwidthGroup, teLinkBandwidthGroup,
dataBearingChannelBandwidthGroup } componentLinkBandwidthGroup }
GROUP teLinkOspfTeGroup GROUP teLinkOspfTeGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for OSPF enabled devices." "This group is mandatory for OSPF enabled devices."
GROUP teLinkSrlgGroup GROUP teLinkSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for G-MPLS enabled devices." "This group is mandatory for G-MPLS enabled devices."
GROUP linkBundlingNotificationGroup GROUP linkBundlingNotificationGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
-- teLinkTable -- teLinkTable
OBJECT teLinkIpAddrType OBJECT teLinkIpAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The dns(16) address type need not be supported. "The dns(16) address type need not be supported.
The ipv4(1) and ipv6(2) address types need not be The ipv4(1) and ipv6(2) address types need not be
supported if numbered links are not supported. The supported if numbered links are not supported. The
unknown(0) address type need not be supported if unknown(0) address type need not be supported if
unnumbered links are not supported." unnumbered links are not supported."
OBJECT teLinkIpAddr OBJECT teLinkIpAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
skipping to change at page 46, line 31 skipping to change at page 46, line 31
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT teLinkBandwidthStorageType OBJECT teLinkBandwidthStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- dataBearingChannelTable -- componentLinkTable
OBJECT dataBearingChannelLinkMuxCapability OBJECT componentLinkMuxCapability
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelPreferredProtection OBJECT componentLinkPreferredProtection
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelMaxReservableBandwidth OBJECT componentLinkMaxReservBandwidth
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelRowStatus OBJECT componentLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT dataBearingChannelStorageType OBJECT componentLinkStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- dataBearingChannelDescriptorTable -- componentLinkDescriptorTable
OBJECT dataBearingChannelEncodingType OBJECT componentLinkEncodingType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelDescrPriority OBJECT componentLinkDescrPriority
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelMinReservableBandwidth OBJECT componentLinkMinReservBandwidth
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelDescrRowStatus OBJECT componentLinkDescrRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) state need not be supported." "The notReady(3) state need not be supported."
OBJECT dataBearingChannelDescrStorageType OBJECT componentLinkDescrStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
-- dataBearingChannelBandwidthTable -- componentLinkBandwidthTable
OBJECT dataBearingChannelMaximumLspBandwidth OBJECT componentLinkMaximumLspBandwidth
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT dataBearingChannelBwRowStatus OBJECT componentLinkBandwidthRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
not be supported." not be supported."
OBJECT dataBearingChannelBwStorageType OBJECT componentLinkBwStorageType
SYNTAX INTEGER { other(1) } SYNTAX INTEGER { other(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Only other(1) needs to be supported." "Only other(1) needs to be supported."
::= { linkBundlingCompliances 2 } ::= { linkBundlingCompliances 2 }
-- Units of conformance -- Units of conformance
linkBundlingGroup OBJECT-GROUP linkBundlingGroup OBJECT-GROUP
skipping to change at page 48, line 41 skipping to change at page 48, line 41
teLinkOutgoingIfId, teLinkOutgoingIfId,
teLinkFlooding, teLinkFlooding,
teLinkRowStatus, teLinkRowStatus,
teLinkStorageType, teLinkStorageType,
teLinkEncodingType, teLinkEncodingType,
teLinkDescrPriority, teLinkDescrPriority,
teLinkMinReservableBandwidth, teLinkMinReservableBandwidth,
teLinkMaxReservableBandwidth, teLinkMaxReservableBandwidth,
teLinkDescrRowStatus, teLinkDescrRowStatus,
teLinkDescrStorageType, teLinkDescrStorageType,
dataBearingChannelLinkMuxCapability, componentLinkMuxCapability,
dataBearingChannelPreferredProtection, componentLinkPreferredProtection,
dataBearingChannelCurrentProtection, componentLinkCurrentProtection,
dataBearingChannelRowStatus, componentLinkRowStatus,
dataBearingChannelStorageType, componentLinkStorageType,
linkBundlingNotifEnable linkBundlingNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the monitoring of
resources associated with TE links." resources associated with TE links."
::= { linkBundlingGroups 1 } ::= { linkBundlingGroups 1 }
teLinkOspfTeGroup OBJECT-GROUP teLinkOspfTeGroup OBJECT-GROUP
skipping to change at page 49, line 40 skipping to change at page 49, line 40
OBJECTS { teLinkUnreservedBandwidth, OBJECTS { teLinkUnreservedBandwidth,
teLinkMaximumLspBandwidth, teLinkMaximumLspBandwidth,
teLinkBandwidthRowStatus, teLinkBandwidthRowStatus,
teLinkBandwidthStorageType teLinkBandwidthStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the monitoring of
the priority-based bandwidth resources associated with the priority-based bandwidth resources associated with
TE links and data-bearing channels." TE links and component links."
::= { linkBundlingGroups 4 } ::= { linkBundlingGroups 4 }
dataBearingChannelBandwidthGroup OBJECT-GROUP componentLinkBandwidthGroup OBJECT-GROUP
OBJECTS { dataBearingChannelEncodingType, OBJECTS { componentLinkEncodingType,
dataBearingChannelDescrPriority, componentLinkDescrPriority,
dataBearingChannelMinReservableBandwidth, componentLinkMinReservBandwidth,
dataBearingChannelMaxReservableBandwidth, componentLinkMaxReservBandwidth,
dataBearingChannelDescrRowStatus, componentLinkDescrRowStatus,
dataBearingChannelDescrStorageType, componentLinkDescrStorageType,
dataBearingChannelUnreservedBandwidth, componentLinkUnreservedBandwidth,
dataBearingChannelMaximumLspBandwidth, componentLinkMaximumLspBandwidth,
dataBearingChannelBwRowStatus, componentLinkBandwidthRowStatus,
dataBearingChannelBwStorageType componentLinkBwStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the monitoring of
bandwidth parameters associated with data-bearing channels." bandwidth parameters associated with component links."
::= { linkBundlingGroups 5 } ::= { linkBundlingGroups 5 }
linkBundlingNotificationGroup NOTIFICATION-GROUP linkBundlingNotificationGroup NOTIFICATION-GROUP
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 }
skipping to change at page 50, line 47 skipping to change at page 50, line 47
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
environments. The support for SET operations in a non-secure environ- environments. The support for SET operations in a non-secure environ-
ment without proper protection can have a negative effect on network ment without proper protection can have a negative effect on network
operations. The use of SNMP Version 3 is recommended over prior ver- operations. The use of SNMP Version 3 is recommended over prior ver-
sions, for configuration control, as its security model is improved. sions, for configuration control, as its security model is improved.
SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if
the network itself is secure (for example by using IPSec [IPSEC]), the network itself is secure (for example by using IPSec [RFC2401]),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB. It is recommended that the implementers consider the security MIB. It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [RFC2574] and the View-based Access of the User-based Security Model [RFC2574] and the View-based Access
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 data-bearing chan- nodes and their IP address (teLinkTable), list of component links
nels (dataBearingChannelTable) in addition to usage of network (componentLinkTable) in addition to usage of network resources (teL-
resources (teLinkBandwidthTable and dataBearingChannelBandwidthT- inkBandwidthTable and componentLinkBandwidthTable). Allowing uncon-
able). Allowing uncontrolled access to these objects could result in trolled access to these objects could result in malicious and
malicious and unwanted disruptions of network traffic, incorrect net- unwanted disruptions of network traffic, incorrect network configura-
work configuration or theft of competitive business information. tion or theft of competitive business information. There are no
There are no objects that are particularly sensitive in their own objects that are particularly sensitive in their own right, such as
right, such as passwords or monetary amounts. passwords or monetary amounts.
12. Acknowledgments 12. 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 13. References
[RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-
based Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905,
January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[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,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April
1999.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[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., [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering", "Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-03.txt>, Internet Draft <draft-ietf-mpls-bundle-03.txt>,
May 2002. May 2002.
[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.
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K., Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z., Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Functional Description", "Generalized MPLS Signaling Functional Description",
Internet Draft Internet Draft
<draft-ietf-mpls-generalized-signaling-08.txt>, <draft-ietf-mpls-generalized-signaling-08.txt>,
April 2002. April 2002.
[GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D.,
skipping to change at page 52, line 21 skipping to change at page 53, line 43
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-02.txt>,
March 2002. March 2002.
[OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to
OSPF", Internet Draft
<draft-katz-yeung-ospf-traffic-06.txt>, October 2001.
[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
Extensions in Support of Generalized MPLS", Internet Extensions in Support of Generalized MPLS", Internet
Draft Draft
<draft-ietf-ccamp-ospf-gmpls-extensions-07.txt>, <draft-ietf-ccamp-ospf-gmpls-extensions-07.txt>,
May 2002. May 2002.
[LSP-HIER] Kompella, K., Rekhter, Y., LSP Hierarchy with MPLS TE,
Internet Draft <draft-ietf-mpls-lsp-hierarchy-03.txt>,
May 2001.
[ZININ] Zinin, A., SHand, M., "Flooding optimizations in link-
state routing protocols", Internet Draft,
<draft-ietf-ospf-isis-flood-opt-01.txt>, March 2001.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.isi.edu/in-notes/iana/assignments/smi-
numbers
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS, (http://www.isi.edu/in- FAMILY NUMBERS, (http://www.isi.edu/in-
notes/iana/assignements/address-family-numbers), notes/iana/assignements/address-family-numbers),
for MIB see: for MIB see:
ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-
based Internets", STD 16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[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.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, April
1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905,
January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999.
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Group MIB", RFC 2863, June 2000. 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.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate [OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to
Requirement Levels", BCP 14, RFC 2119, March 1997. OSPF", Internet Draft
<draft-katz-yeung-ospf-traffic-06.txt>, October 2001.
14. Authors' Addresses 14. Authors' Addresses
Martin Dubuc Thomas D. Nadeau Martin Dubuc Thomas D. Nadeau
Meriton Networks Cisco Systems, Inc. Meriton Networks Cisco Systems, Inc.
3026 Solandt Road 300 Apollo Drive 3026 Solandt Road 300 Apollo Drive
Kanata, ON, CANADA K2K 2A5 Chelmsford, MA 01824 Kanata, ON, CANADA K2K 2A5 Chelmsford, MA 01824
Phone: +1-613-270-9279 x253 Phone: +1-978-244-3051 Phone: +1-613-270-9279 x253 Phone: +1-978-244-3051
Email: martin.dubuc@meriton.com Email: tnadeau@cisco.com Email: martin.dubuc@meriton.com Email: tnadeau@cisco.com
 End of changes. 

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