draft-ietf-mpls-bundle-mib-00.txt   draft-ietf-mpls-bundle-mib-01.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft edgeflow, Inc. Internet Draft Meriton Networks
Expires: March 2002 Expires: August 2002
Sudheer Dharanikota Sudheer Dharanikota
Nayna Networks, Inc. Nayna Networks
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Calient Networks, Inc. Calient Networks
Link Bundling Management Information Base Using SMIv2 February 2002
draft-ietf-mpls-bundle-mib-00.txt Link Bundling Management Information Base
draft-ietf-mpls-bundle-mib-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet- Drafts. groups may also distribute working documents as Internet- Drafts.
skipping to change at page 1, line 45 skipping to change at page 1, line 47
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Table of Contents Table of Contents
1. Abstract ..................................................... 2 1. Abstract ..................................................... 2
2. Introduction ................................................. 2 2. Introduction ................................................. 2
3. Terminology .................................................. 3 3. Terminology .................................................. 3
4. The SNMP Management Framework ................................ 3 4. The SNMP Management Framework ................................ 3
4.1. Object Definitions ........................................... 4
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 .............................................. 7 7.4. teLinkSrlgTable .............................................. 6
7.5. teLinkBandwidthTable ......................................... 7 7.5. teLinkBandwidthTable ......................................... 7
7.6. dataBearingChannelTable ...................................... 7 7.6. dataBearingChannelTable ...................................... 7
7.7. dataBearingChannelDescriptorTable ............................ 7 7.7. dataBearingChannelDescriptorTable ............................ 7
7.8. dataBearingChannelBandwidthTable ............................. 7 7.8. dataBearingChannelBandwidthTable ............................. 7
8. Example of Bundled Link Setup ................................ 7 8. Example of Bundled Link Setup ................................ 7
9. Application of the Interface 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 ...................................... 43 11. Security Considerations ...................................... 47
12. Acknowledgments .............................................. 44 12. Acknowledgments .............................................. 48
13. References ................................................... 45 13. References ................................................... 48
14. Authors' Addresses ........................................... 48 14. Authors' Addresses ........................................... 51
15. Full Copyright Statement ..................................... 48 15. Full Copyright Statement ..................................... 51
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Informa- This memo defines an experimental portion of the Management Informa-
tion Base (MIB) for use with network management protocols in the tion Base (MIB) for use with network management protocols in the
Internet community. In particular, it describes managed objects for Internet community. In particular, it describes managed objects for
modeling link bundling as described in [BUNDLING]. modeling link bundling as described in [BUNDLING].
2. Introduction 2. Introduction
This memo defines an experimental portion of the Management Informa- OSPF, G-MPLS and LMP use the concept of traffic engineering (TE)
tion Base (MIB) for use with network management protocols in the links to abstract link properties. The effect of this approach is the
Internet community. In particular, it describes managed objects for reduction of the amount of routing information exchanged in the net-
modeling link bundling as described in [BUNDLING]. work, which improves routing scalability. In addition, the use of TE
link allows the implementation of new capabilities such as link pro-
tection.
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-
figuration and the performance monitoring of TE links and bundled
link.
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list at
mpls@uu.net. mpls@uu.net.
This memo does not, in its draft form, specify a standard for the This memo does not, in its draft form, specify a standard for the
Internet community. 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
skipping to change at page 3, line 35 skipping to change at page 3, line 42
time, and at some point later, all but one of the links are deleted, time, and at some point later, all but one of the links are deleted,
the agent may choose to either delete the link bundle, or it may the agent may choose to either delete the link bundle, or it may
choose to leave it intact. Traffic counters on a link bundle are choose to leave it intact. Traffic counters on a link bundle are
cumulative for all subinterfaces which it binds together. cumulative for all subinterfaces which it binds together.
4. The SNMP Management Framework 4. The SNMP Management Framework
The SNMP Management Framework presently consists of five major com- The SNMP Management Framework presently consists of five major com-
ponents: ponents:
- An overall architecture, described in RFC 2571 [SNMPArch]. - An overall architecture, described in RFC 2571 [RFC2571].
- Mechanisms for describing and naming objects and events for the Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
[SNMPv1Traps]. The second version, called SMIv2, is described 1215 [RFC1215]. The second version, called SMIv2, is described
in RFC 2578 [SMIv2], RFC 2579 [SNMPv2TC] and RFC 2580 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
[SNMPv2Conf]. STD 58, RFC 2580 [RFC2580].
- Message protocols for transferring management information. The - Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 first version of the SNMP message protocol is called SNMPv1 and
and described in RFC 1157 [SNMPv1]. A second version of the described in STD 15, RFC 1157 [RFC1157]. A second version of
SNMP message protocol, which is not an Internet standards the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901 track protocol, is called SNMPv2c and described in RFC 1901
[SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the [RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906 message protocol is called SNMPv3 and described in RFC 1906
[SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
- Protocol operations for accessing management information. The - Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [SNMPv1]. A second set of protocol described in STD 15, RFC 1157 [RFC1157]. A second set of
operations and associated PDU formats is described in RFC 1905 protocol operations and associated PDU formats is described in
[SNMPv2PO]. RFC 1905 [RFC1905].
- A set of fundamental applications described in RFC 2273
[SNMPv3App] and the view-based access control mechanism
described in RFC 2575 [SNMPv3VACM].
Managed objects are accessed via a virtual information store, termed - A set of fundamental applications described in RFC 2573
the Management Information Base or MIB. Objects in the MIB are [RFC2573] and the view-based access control mechanism described
defined using the mechanisms defined in the SMI. This memo specifies in RFC 2575 [RFC2575].
a MIB module that is compliant to the SMIv2. A MIB conforming to the
SMIv1 can be produced through the appropriate translations. The
resulting translated MIB must be semantically equivalent, except
where objects or events are omitted because no translation is possi-
ble (use of Counter64). Some machine-readable information in SMIv2
will be converted into textual descriptions in SMIv1 during the
translation process. However, this loss of machine-readable informa-
tion is not considered to change the semantics of the MIB.
4.1. Object Definitions A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) defined using the mechanisms defined in the SMI.
defined in the SMI. In particular, each object type is named by an
OBJECT IDENTIFIER, an administratively assigned name. The object This memo specifies a MIB module that is compliant to the SMIv2. A
type together with an object instance serves to uniquely identify a MIB conforming to the SMIv1 can be produced through the appropriate
specific instantiation of the object. For human convenience, we often translations. The resulting translated MIB must be semantically
use a textual string, termed the descriptor, to also refer to the equivalent, except where objects or events are omitted because no
object type. translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
5. Feature Checklist 5. Feature Checklist
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
skipping to change at page 7, line 33 skipping to change at page 7, line 29
channel supports. channel supports.
7.8. dataBearingChannelBandwidthTable 7.8. dataBearingChannelBandwidthTable
The data-bearing channel bandwidth table specifies the priority-based The data-bearing channel bandwidth table specifies the priority-based
bandwidth values associated with the data-bearing channels. bandwidth values associated with the data-bearing channels.
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 9 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 data-bearing channels 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,
teLinkNumberingType = unnumbered(1), teLinkNumberingType = unnumbered(2),
teLinkRowStatus = createAndGo(4) teLinkRowStatus = createAndGo(4)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 0, ifStackHigherLayer = 0,
ifStackLowerLayer = 25, ifStackLowerLayer = 25,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
Next, the two TE links are created. Next, the two TE links are created.
In teLinkTable: In teLinkTable:
{ {
ifIndex = 20, ifIndex = 20,
teLinkNumberingType = unnumbered(1), teLinkNumberingType = unnumbered(2),
teLinkMetric = 5, teLinkMetric = 5,
teLinkResourceClass = 3, teLinkResourceClass = 3,
teLinkRowStatus = createAndWait(5) teLinkRowStatus = createAndWait(5)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 25, ifStackHigherLayer = 25,
ifStackLowerLayer = 20, ifStackLowerLayer = 20,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
} }
In teLinkTable: In teLinkTable:
{ {
ifIndex = 21, ifIndex = 21,
teLinkNumberingType = unnumbered(1), teLinkNumberingType = unnumbered(2),
teLinkMetric = 5, teLinkMetric = 5,
teLinkResourceClass = 3, teLinkResourceClass = 3,
teLinkRowStatus = createAndWait(5) teLinkRowStatus = createAndWait(5)
} }
In ifStackTable: In ifStackTable:
{ {
ifStackHigherLayer = 25, ifStackHigherLayer = 25,
ifStackLowerLayer = 21, ifStackLowerLayer = 21,
ifStackStatus = createAndGo(4) ifStackStatus = createAndGo(4)
skipping to change at page 11, line 23 skipping to change at page 11, line 19
link descriptors. link descriptors.
Note that the bandwidth attributes in teLinkDescriptorTable, Note that the bandwidth attributes in teLinkDescriptorTable,
dataBearingChannelDescriptorTable, teLinkBandwidthTable dataBearingChannelDescriptorTable, teLinkBandwidthTable
and dataBearingChannelBandwidthTable are maintained by the and dataBearingChannelBandwidthTable 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 data-bearing channels of the TE links and
the TE links of the bundled link. the TE links of the bundled link.
9. Application of the Interface Group to TE Links 9. Application of the Interfaces Group to TE Links
The Interfaces Group of MIB II defines generic managed objects for The Interfaces Group [IFMIB] 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.
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 [IFMIB] 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 [IFMIB].
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(TBD) + | TE link-interface ifType = teLink(200) +
+----------------------------------------+ +----------------------------------------+
| Underlying Layer... + | Underlying Layer... +
+----------------------------------------+ +----------------------------------------+
In the above diagram, "Underlying Layer..." refers to the ifIndex In the above diagram, "Underlying Layer..." refers to the ifIndex
of any interface type, which has been defined for TE Link of any interface type, which has been defined for TE Link
interworking. Examples include ATM, Frame Relay, Ethernet, etc. interworking. Examples include ATM, Frame Relay, Ethernet, etc.
9.1. Support of the TE Link Layer by ifTable 9.1. Support of the TE Link Layer by ifTable
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 TBD. ifType The value that is allocated for TE Link is 200.
This number will be assigned by the IANA.
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 [IFMIB].
skipping to change at page 16, line 14 skipping to change at page 16, line 13
InterfaceIndex, InterfaceIndexOrZero, ifIndex InterfaceIndex, 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 "200109101200Z" -- 10 September 2001 12:00:00 EST LAST-UPDATED "200202261200Z" -- 26 February 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: edgeflow, Inc. Postal: Meriton Networks
329 March Rd. 3026 Solandt Road
Kanata, ON, CANADA K2K 2E1 Kanata, ON, CANADA K2K 2A5
Tel: +1-613-270-9279 x253 Tel: +1-613-270-9279 x253
Email: martin.dubuc@edgeflow.com Email: martin.dubuc@meriton.com
Sudheer Dharanikota Sudheer Dharanikota
Postal: Nayna Networks, Inc. Postal: Nayna Networks, Inc.
157 Topaz Street 157 Topaz Street
Milipitas, CA 95035 Milipitas, CA 95035
Tel: +1-408-956-8000 x357 Tel: +1-408-956-8000 x357
Email: sudheer@nayna.com Email: sudheer@nayna.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
skipping to change at page 16, line 49 skipping to change at page 16, line 48
Postal: Calient Networks, Inc. Postal: Calient Networks, Inc.
25 Castilian Drive 25 Castilian Drive
Goleta, CA 93117 Goleta, CA 93117
Email: jplang@calient.net" Email: jplang@calient.net"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
MPLS traffic engineering link bundling as MPLS traffic engineering link bundling as
defined in: Kompella, K., Rekhter, Y., Berger, L., defined in: Kompella, K., Rekhter, Y., Berger, L.,
Link Bundling in MPLS Traffic Engineering Link Bundling in MPLS Traffic Engineering
Internet Draft <draft-ietf-mpls-bundling-05.txt>, Internet Draft <draft-ietf-mpls-bundling-01.txt>,
February 2001." November 2001."
-- Revision history. -- Revision history.
REVISION REVISION
"200202261200Z" -- 26 February 2002 12:00:00 EST
DESCRIPTION
"- Updated MIB boiler plate and references.
- Added linkBundlingFullModuleCompliance conformance statement.
- Removed teLinkIpAddrType. Replaced numbered value with
ipV4 and ipV6 values in teLinkNumberingType.
- Updated description of all row status and storage type objects.
- Changed some of the enumerated value to start from 1 instead of 0.
- Updated references."
REVISION
"200109101200Z" -- 10 September 2001 12:00:00 EST "200109101200Z" -- 10 September 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Removed teLinkRemoteId. Updated teLinkEncodingType and "Removed teLinkRemoteId. Updated teLinkEncodingType and
dataBearingChannelEncodingType values." dataBearingChannelEncodingType values."
REVISION REVISION
"200105221200Z" -- 22 May 2001 12:00:00 EST "200105223200Z" -- 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
"200105141200Z" -- 14 May 2001 12:00:00 EST "200105141200Z" -- 14 May 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Replaced componentLinkTable by dataBearingChannelTable. "Replaced componentLinkTable by dataBearingChannelTable.
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 }
-- Textual Conventions -- Textual Conventions
-- Top level components of this MIB -- Top level components of this MIB
-- Notifications
linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 } linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 }
-- Tables, Scalars -- Tables, Scalars
linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 } linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 }
-- Conformance -- Conformance
linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 } linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 }
-- TE Link Table -- TE Link Table
teLinkTable OBJECT-TYPE teLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkEntry SYNTAX SEQUENCE OF TeLinkEntry
skipping to change at page 18, line 24 skipping to change at page 18, line 32
the corresponding ifIndex. If a TE link entry in the ifTable is the corresponding ifIndex. If a TE link entry in the ifTable is
destroyed, then so is the corresponding entry in the destroyed, then so is the corresponding entry in the
teLinkTable. The administrative and operational status values teLinkTable. The administrative and operational status values
are controlled from the ifEntry. If the link is unnumbered, are controlled from the ifEntry. If the link is unnumbered,
ifIndex is also used as the outgoing interface identifier." ifIndex is also used as the outgoing interface identifier."
INDEX { ifIndex } INDEX { ifIndex }
::= { teLinkTable 1 } ::= { teLinkTable 1 }
TeLinkEntry ::= SEQUENCE { TeLinkEntry ::= SEQUENCE {
teLinkNumberingType INTEGER, teLinkNumberingType INTEGER,
teLinkIpAddrType InetAddressType,
teLinkIpAddr InetAddress, teLinkIpAddr InetAddress,
teLinkRemoteIpAddr InetAddress, teLinkRemoteIpAddr InetAddress,
teLinkMetric Unsigned32, teLinkMetric Unsigned32,
teLinkMuxCapability INTEGER, teLinkMuxCapability INTEGER,
teLinkProtectionType INTEGER, teLinkProtectionType INTEGER,
teLinkWorkingPriority Unsigned32, teLinkWorkingPriority Unsigned32,
teLinkResourceClass Unsigned32, teLinkResourceClass Unsigned32,
teLinkIncomingIfId InterfaceIndexOrZero, teLinkIncomingIfId InterfaceIndexOrZero,
teLinkOutgoingIfId InterfaceIndexOrZero, teLinkOutgoingIfId InterfaceIndexOrZero,
teLinkFlooding InterfaceIndexOrZero, teLinkFlooding InterfaceIndexOrZero,
teLinkRowStatus RowStatus, teLinkRowStatus RowStatus,
teLinkStorageType StorageType teLinkStorageType StorageType
} }
teLinkNumberingType OBJECT-TYPE teLinkNumberingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
numbered(0), unnumbered(1),
unnumbered(1) ipV4(2),
ipV6(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TE link identifier type (numbered or unnumbered)." "The TE link identifier address numbering type."
::= { teLinkEntry 1 } ::= { teLinkEntry 1 }
teLinkIpAddrType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates whether the TE link address is IPv4 or
IPv6 (numbered link)."
::= { teLinkEntry 2 }
teLinkIpAddr OBJECT-TYPE teLinkIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For numbered links, this object represents the IP address "For IPv4 and IPv6 numbered links, this object represents the
associated with the TE link." IP address associated with the TE link."
::= { teLinkEntry 3 } ::= { teLinkEntry 2 }
teLinkRemoteIpAddr OBJECT-TYPE teLinkRemoteIpAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote IP address associated with the TE link (numbered "The remote IP address associated with the TE link (IPv4 and
links)." IPv6 numbered links)."
::= { teLinkEntry 4 } ::= { 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 data-bearing channels. All data-bearing
channels within the TE link must have the same traffic channels within the TE link must have the same traffic
engineering metric." engineering metric."
REFERENCE REFERENCE
"draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
February 2001." February 2001."
::= { teLinkEntry 5 } ::= { teLinkEntry 4 }
teLinkMuxCapability OBJECT-TYPE teLinkMuxCapability OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
packetSwitch1(1), packetSwitch1(1),
packetSwitch2(2), packetSwitch2(2),
packetSwitch3(3), packetSwitch3(3),
packetSwitch4(4), packetSwitch4(4),
layer2Switch(51), layer2Switch(51),
tdm(100), tdm(100),
lambdaSwitch(150), lambdaSwitch(150),
fiberSwitch(200) fiberSwitch(200)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
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 data-bearing channels. All
data-bearing channels within the same TE link must have the data-bearing channels within the same TE link must have the
same link multiplex capability." same link multiplex capability."
REFERENCE REFERENCE
"draft-ietf-mpls-lsp-hierarchy-02.txt - LSP Hierarchy with "draft-ietf-mpls-lsp-hierarchy-03.txt - LSP Hierarchy with
MPLS TE, K. Kompella, Y. Rekhter, February 2001." MPLS TE, K. Kompella, Y. Rekhter, May 2001."
::= { teLinkEntry 6 } ::= { teLinkEntry 5 }
teLinkProtectionType OBJECT-TYPE teLinkProtectionType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unprotected(0), unprotected(1),
shared(1), shared(2),
dedicated1For1(2), dedicated1For1(3),
dedicated1Plus1(3), dedicated1Plus1(4),
enhanced(4) enhanced(5)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies link protection type of the "This attribute specifies link protection type of the
TE link." TE link."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, February 2001." D. Saha, V. Sharma, February 2002."
::= { teLinkEntry 7 } ::= { 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 channel and
not on a secondary channel." not on a secondary channel."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, Februrary 2002."
::= { teLinkEntry 8 } ::= { teLinkEntry 7 }
teLinkResourceClass OBJECT-TYPE teLinkResourceClass OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the TE link resource class. "This attribute specifies the TE link resource class.
The resource class is a 32 bit bitfield. The resource class for The resource class is a 32 bit bitfield. The resource class for
a link bundle is derived from the resource class of its a link bundle is derived from the resource class of its
TE links. All TE links within a link bundle must have the TE links. All TE links within a link bundle must have the
same resource class." same resource class."
::= { teLinkEntry 9 } ::= { teLinkEntry 8 }
teLinkIncomingIfId OBJECT-TYPE teLinkIncomingIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For unnumbered links, the incoming interface is set to the "For unnumbered links, the incoming interface is set to the
outgoing interface identifier chosen by the neighboring LSR outgoing interface identifier chosen by the neighboring LSR
for the reverse link corresponding to this TE link." for the reverse link corresponding to this TE link."
REFERENCE REFERENCE
"draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS "draft-ietf-mpls-bundle-01.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
February 2001." November 2001."
::= { teLinkEntry 10 } ::= { teLinkEntry 9 }
teLinkOutgoingIfId OBJECT-TYPE teLinkOutgoingIfId OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the link is unnumbered, the outgoing interface identifier is "If the link is unnumbered, the outgoing interface identifier is
set to the outgoing interface identifier chosen for the TE link set to the outgoing interface identifier chosen for the TE link
by the advertising LSR." by the advertising LSR."
REFERENCE REFERENCE
"draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS "draft-ietf-mpls-bundle-01.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
February 2001." November 2001."
::= { teLinkEntry 11 } ::= { teLinkEntry 10 }
teLinkFlooding OBJECT-TYPE teLinkFlooding OBJECT-TYPE
SYNTAX InterfaceIndexOrZero SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object only has significance for link bundles which "This object only has significance for link bundles which
encoding type is not clear. For these link bundles, this object encoding type is not clear. For these link bundles, this object
identifies the TE link on which to restrict flooding. If the identifies the TE link on which to restrict flooding. If the
value is zero, then flooding must be done on all TE links value is zero, then flooding must be done on all TE links
skipping to change at page 22, line 22 skipping to change at page 22, line 19
March 2001." March 2001."
DEFVAL { 0 } DEFVAL { 0 }
::= { teLinkEntry 12 } ::= { teLinkEntry 12 }
teLinkRowStatus OBJECT-TYPE teLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table. All read-create objects
can be changed when teLinkRowStatus is active."
::= { teLinkEntry 13 } ::= { teLinkEntry 13 }
teLinkStorageType OBJECT-TYPE teLinkStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." teLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
::= { teLinkEntry 14 } ::= { teLinkEntry 14 }
-- End of teLinkTable -- End of teLinkTable
-- TE Link Descriptor Table -- TE Link Descriptor Table
teLinkDescriptorTable OBJECT-TYPE teLinkDescriptorTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkDescriptorEntry SYNTAX SEQUENCE OF TeLinkDescriptorEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 23, line 35 skipping to change at page 23, line 35
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."
::= { teLinkDescriptorEntry 1 } ::= { teLinkDescriptorEntry 1 }
teLinkEncodingType OBJECT-TYPE teLinkEncodingType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
packet(1), packet(1),
ethernetV2(2), ethernetV2Dix(2),
ansiPdh(3), ansiPdh(3),
etsiPdh(4), etsiPdh(4),
sdhItu1996(5), sdhItuG707(5),
sonetAnsi1995(6), sonetAnsiT1105(6),
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
ethernet8023(10), ethernet8023(10),
sdhItu2000(11), fiberChannel(11)
sonetAnsi2000(12)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the TE link encoding type." "This attribute specifies the TE link encoding type."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-mpls-generalized-signaling-07.txt - Generalized
in Support of Generalized MPLS, K. Kompella, Y. Rekhter, MPLS Signaling Functional Description, P. Ashwood-Smith,
A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,
D. Saha, V. Sharma, July 2001." E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,
V. Sharma, G. Swallow, Z. Tang, November 2001."
::= { teLinkDescriptorEntry 2 } ::= { teLinkDescriptorEntry 2 }
teLinkDescrPriority OBJECT-TYPE teLinkDescrPriority OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the lowest priority at which that link "This object specifies the lowest priority at which that link
encoding type is available." encoding type is available."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { teLinkDescriptorEntry 3 } ::= { teLinkDescriptorEntry 3 }
teLinkMinReservableBandwidth OBJECT-TYPE teLinkMinReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
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 data-bearing
channels associated with the TE link that can be used to carry channels 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-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { teLinkDescriptorEntry 4 } ::= { teLinkDescriptorEntry 4 }
teLinkMaxReservableBandwidth OBJECT-TYPE teLinkMaxReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
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 data-bearing channels 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-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { teLinkDescriptorEntry 5 } ::= { teLinkDescriptorEntry 5 }
teLinkDescrRowStatus OBJECT-TYPE teLinkDescrRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table. All read-create objects
can be changed when teLinkDescrRowStatus is active."
::= { teLinkDescriptorEntry 6 } ::= { teLinkDescriptorEntry 6 }
teLinkDescrStorageType OBJECT-TYPE teLinkDescrStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." teLinkDescriptorTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
::= { teLinkDescriptorEntry 7 } ::= { teLinkDescriptorEntry 7 }
-- End of teLinkDescriptorTable
-- OSPF Traffic Engineering Parameters for TE Links -- OSPF Traffic Engineering Parameters for TE Links
teLinkOspfTeTable OBJECT-TYPE teLinkOspfTeTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkOspfTeEntry SYNTAX SEQUENCE OF TeLinkOspfTeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table specifies the OSPF traffic engineering information "This table specifies the OSPF traffic engineering information
associated with TE links." associated with TE links."
skipping to change at page 26, line 32 skipping to change at page 26, line 35
teLinkOspfLinkId OBJECT-TYPE teLinkOspfLinkId OBJECT-TYPE
SYNTAX RouterID SYNTAX RouterID
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"On point-to-point link, the link identifier is the Router ID "On point-to-point link, the link identifier is the Router ID
of the neighbor. For bundled link, is derived from the link of the neighbor. For bundled link, is derived from the link
identifier associated with its TE links." identifier associated with its TE links."
REFERENCE REFERENCE
"draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS "draft-ietf-mpls-bundle-01.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
February 2001." November 2001."
::= { teLinkOspfTeEntry 2 } ::= { teLinkOspfTeEntry 2 }
-- End of teLinkOspfTeTable -- End of teLinkOspfTeTable
-- TE Link Shared Risk Link Group Table -- TE Link Shared Risk Link Group Table
teLinkSrlgTable OBJECT-TYPE teLinkSrlgTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkSrlgEntry SYNTAX SEQUENCE OF TeLinkSrlgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 27, line 29 skipping to change at page 27, line 33
srlgStorageType StorageType srlgStorageType StorageType
} }
srlg OBJECT-TYPE srlg OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This identifies a SRLG supported by the TE link." "This identifies a SRLG supported by the TE link."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { teLinkSrlgEntry 1 } ::= { teLinkSrlgEntry 1 }
srlgRowStatus OBJECT-TYPE srlgRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table. All read-create objects
can be changed when srlgRowStatus is active."
::= { teLinkSrlgEntry 2 } ::= { teLinkSrlgEntry 2 }
srlgStorageType OBJECT-TYPE srlgStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." teLinkSrlgTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
::= { teLinkSrlgEntry 3 } ::= { teLinkSrlgEntry 3 }
-- End of teLinkSrlgTable -- End of teLinkSrlgTable
-- TE Link Bandwidth Table -- TE Link Bandwidth Table
teLinkBandwidthTable OBJECT-TYPE teLinkBandwidthTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLinkBandwidthEntry SYNTAX SEQUENCE OF TeLinkBandwidthEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 28, line 48 skipping to change at page 29, line 7
} }
teLinkPriority OBJECT-TYPE teLinkPriority OBJECT-TYPE
SYNTAX Unsigned32 (1..8) SYNTAX Unsigned32 (1..8)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the priority. It should be mapped "This attribute specifies the priority. It should be mapped
to a number between 0 and 7" to a number between 0 and 7"
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 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 data-bearing channel associated
with the TE link (excludes all channels that are strictly with the TE link (excludes all channels that are strictly
used as protecting channels). This value is an estimate in units used as protecting channels). This value is an estimate in units
of 1,000 bits per second." of 1,000 bits per second."
REFERENCE REFERENCE
"draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS "draft-ietf-mpls-bundle-05.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
February 2001." November 2001."
::= { teLinkBandwidthEntry 2 } ::= { teLinkBandwidthEntry 2 }
teLinkMaximumLspBandwidth OBJECT-TYPE teLinkMaximumLspBandwidth 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 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 data-bearing channels
associated with the TE link (excludes all channels that are associated with the TE link (excludes all channels that are
strictly used as protecting channels). This value is an estimate strictly used as protecting channels). This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS "draft-ietf-mpls-bundle-05.txt - Link Bundling in MPLS
Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger,
February 2001." November 2001."
::= { teLinkBandwidthEntry 3 } ::= { teLinkBandwidthEntry 3 }
teLinkBandwidthRowStatus OBJECT-TYPE teLinkBandwidthRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table." delete a row in this table. All read-create objects
can be changed when teLinkBandwidthRowStatus is active."
::= { teLinkBandwidthEntry 4 } ::= { teLinkBandwidthEntry 4 }
teLinkBandwidthStorageType OBJECT-TYPE teLinkBandwidthStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." teLinkBandwidthTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
::= { teLinkBandwidthEntry 5 } ::= { teLinkBandwidthEntry 5 }
-- End of teLinkBandwidthTable -- End of teLinkBandwidthTable
-- Data-bearing Channel Table -- Data-bearing Channel Table
dataBearingChannelTable OBJECT-TYPE dataBearingChannelTable OBJECT-TYPE
SYNTAX SEQUENCE OF DataBearingChannelEntry SYNTAX SEQUENCE OF DataBearingChannelEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 31, line 51 skipping to change at page 32, line 13
"This attribute specifies whether this data-bearing channel is "This attribute specifies whether this data-bearing channel is
currently used as primary or secondary channel." currently used as primary or secondary channel."
::= { dataBearingChannelEntry 3 } ::= { dataBearingChannelEntry 3 }
dataBearingChannelRowStatus OBJECT-TYPE dataBearingChannelRowStatus 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." delete a row in this table. All read-create objects
can be changed when dataBearingChannelRowStatus is active."
::= { dataBearingChannelEntry 4 } ::= { dataBearingChannelEntry 4 }
dataBearingChannelStorageType OBJECT-TYPE dataBearingChannelStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." dataBearingChannelTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
::= { dataBearingChannelEntry 5 } ::= { dataBearingChannelEntry 5 }
-- End of dataBearingChannelTable -- End of dataBearingChannelTable
-- Data-bearing Channel Link Descriptor Table -- Data-bearing Channel Link Descriptor Table
dataBearingChannelDescriptorTable OBJECT-TYPE dataBearingChannelDescriptorTable OBJECT-TYPE
SYNTAX SEQUENCE OF DataBearingChannelDescrEntry SYNTAX SEQUENCE OF DataBearingChannelDescrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 33, line 35 skipping to change at page 33, line 47
fiber(9), fiber(9),
ethernet8023(10), ethernet8023(10),
sdhItu2000(11), sdhItu2000(11),
sonetAnsi2000(12) sonetAnsi2000(12)
} }
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 data-bearing channel encoding type."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { dataBearingChannelDescrEntry 2 } ::= { dataBearingChannelDescrEntry 2 }
dataBearingChannelDescrPriority OBJECT-TYPE dataBearingChannelDescrPriority 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 data-bearing channel."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { dataBearingChannelDescrEntry 3 } ::= { dataBearingChannelDescrEntry 3 }
dataBearingChannelMinReservableBandwidth OBJECT-TYPE dataBearingChannelMinReservableBandwidth 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 data-bearing channel. This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { dataBearingChannelDescrEntry 4 } ::= { dataBearingChannelDescrEntry 4 }
dataBearingChannelMaxReservableBandwidth OBJECT-TYPE dataBearingChannelMaxReservableBandwidth OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
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 data-bearing channel. This value is an estimate
in units of 1,000 bits per second." in units of 1,000 bits per second."
REFERENCE REFERENCE
"draft-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { dataBearingChannelDescrEntry 5 } ::= { dataBearingChannelDescrEntry 5 }
dataBearingChannelDescrRowStatus OBJECT-TYPE dataBearingChannelDescrRowStatus 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." delete a row in this table. All read-create objects
can be changed when dataBearingChannelDescrRowStatus is active."
::= { dataBearingChannelDescrEntry 6 } ::= { dataBearingChannelDescrEntry 6 }
dataBearingChannelDescrStorageType OBJECT-TYPE dataBearingChannelDescrStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." dataBearingChannelDescriptorTable. Conceptual rows
having the value 'permanent' need not allow write-access
to any columnar object in the row."
::= { dataBearingChannelDescrEntry 7 } ::= { dataBearingChannelDescrEntry 7 }
-- End of dataBearingChannelDescriptorTable
-- Data-bearing Channel Bandwidth Table -- Data-bearing Channel Bandwidth Table
dataBearingChannelBandwidthTable OBJECT-TYPE dataBearingChannelBandwidthTable OBJECT-TYPE
SYNTAX SEQUENCE OF DataBearingChannelBandwidthEntry SYNTAX SEQUENCE OF DataBearingChannelBandwidthEntry
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 data-bearing channels."
skipping to change at page 36, line 4 skipping to change at page 36, line 19
} }
dataBearingChannelPriority OBJECT-TYPE dataBearingChannelPriority 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-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { dataBearingChannelBandwidthEntry 1 } ::= { dataBearingChannelBandwidthEntry 1 }
dataBearingChannelUnreservedBandwidth OBJECT-TYPE dataBearingChannelUnreservedBandwidth 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 data-bearing channel 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-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { dataBearingChannelBandwidthEntry 2 } ::= { dataBearingChannelBandwidthEntry 2 }
dataBearingChannelMaximumLspBandwidth OBJECT-TYPE dataBearingChannelMaximumLspBandwidth 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 maximum "This attribute specifies the data-bearing channel 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-kompella-ospf-gmpls-extensions-02.txt - OSPF Extensions "draft-ietf-ccamp-ospf-gmpls-extensions-04.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, July 2001." D. Saha, V. Sharma, February 2002."
::= { dataBearingChannelBandwidthEntry 3 } ::= { dataBearingChannelBandwidthEntry 3 }
dataBearingChannelBwRowStatus OBJECT-TYPE dataBearingChannelBwRowStatus 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." delete a row in this table. All read-create objects
can be changed when dataBearingChannelBwRowStatus is active."
::= { dataBearingChannelBandwidthEntry 4 } ::= { dataBearingChannelBandwidthEntry 4 }
dataBearingChannelBwStorageType OBJECT-TYPE dataBearingChannelBwStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "The storage type for this conceptual row in the
object." dataBearingChannelBandwidthTable. Conceptual rows
having the value 'permanent' need not allow write-access
to any columnar object in the row."
::= { dataBearingChannelBandwidthEntry 5 } ::= { dataBearingChannelBandwidthEntry 5 }
-- End of dataBearingChannelBandwidthTable -- End of dataBearingChannelBandwidthTable
-- Notification Configuration -- Notification Configuration
linkBundlingTrapEnable 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 traps, generation of the link bundling notifications,
otherwise these traps are not emitted." otherwise these notifications are not emitted."
DEFVAL { false } DEFVAL { false }
::= { linkBundlingObjects 9 } ::= { linkBundlingObjects 9 }
-- Notifications -- Notifications
-- Bundled Link Notifications
linkBundleMismatch NOTIFICATION-TYPE linkBundleMismatch NOTIFICATION-TYPE
OBJECTS { ifIndex } OBJECTS { ifIndex }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a mismatch is found on a "This notification is generated when a mismatch is found on a
bundled link. Such mismatch can be detected for instance if one bundled link. Such mismatch can be detected for instance if one
of the traffic engineering parameters is not consistent across of the traffic engineering parameters is not consistent across
all TE links within a bundled link (resource class, all TE links within a bundled link (resource class,
OSPF link type, etc.)." OSPF link type, etc.)."
skipping to change at page 38, line 6 skipping to change at page 38, line 23
-- End of notifications -- End of notifications
-- Module compliance -- Module compliance
linkBundlingGroups linkBundlingGroups
OBJECT IDENTIFIER ::= { linkBundlingConformance 1 } OBJECT IDENTIFIER ::= { linkBundlingConformance 1 }
linkBundlingCompliances linkBundlingCompliances
OBJECT IDENTIFIER ::= { linkBundlingConformance 2 } OBJECT IDENTIFIER ::= { linkBundlingConformance 2 }
linkBundlingModuleCompliance MODULE-COMPLIANCE linkBundlingFullModuleCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
link bundling MIB." configuration and monitoring of link bundling MIB."
MODULE -- this module
-- The mandatory groups have to be implemented
-- by all devices supporting link bundling. However, they may all
-- be supported as read-only objects in the case where manual
-- configuration is unsupported.
MANDATORY-GROUPS { linkBundlingGroup,
teLinkBandwidthGroup }
GROUP teLinkOspfTeGroup
DESCRIPTION
"This group is mandatory for OSPF enabled devices."
GROUP teLinkSrlgGroup
DESCRIPTION
"This group is mandatory for G-MPLS enabled devices."
-- teLinkTable
OBJECT teLinkRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) state need not be supported."
OBJECT teLinkStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- teLinkDescriptorTable
OBJECT teLinkDescrRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) state need not be supported."
OBJECT teLinkDescrStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- teLinkOspfTeTable
OBJECT teLinkOspfLinkId
SYNTAX INTEGER { pointToPoint(1) }
MIN-ACCESS read-create
DESCRIPTION
"A value of multiAccess(2) need not be supported."
-- teLinkSrlgTable
OBJECT srlgRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT srlgStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- teLinkBandwidthTable
OBJECT teLinkBandwidthRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT teLinkBandwidthStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- dataBearingChannelTable
OBJECT dataBearingChannelRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT dataBearingChannelStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- dataBearingChannelDescriptorTable
OBJECT dataBearingChannelDescrRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) state need not be supported."
OBJECT dataBearingChannelDescrStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
-- dataBearingChannelBandwidthTable
OBJECT dataBearingChannelBwRowStatus
SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) }
MIN-ACCESS read-create
DESCRIPTION
"The notReady(3) and createAndWait(5) states need
not be supported."
OBJECT dataBearingChannelBwStorageType
SYNTAX INTEGER { other(1) }
MIN-ACCESS read-create
DESCRIPTION
"Only other(1) needs to be supported."
::= { linkBundlingCompliances 1 }
linkBundlingMonitoringModuleCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that support the
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 }
skipping to change at page 41, line 36 skipping to change at page 44, line 50
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 dataBearingChannelBwStorageType
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 1 } ::= { linkBundlingCompliances 2 }
-- Units of conformance -- Units of conformance
linkBundlingGroup OBJECT-GROUP linkBundlingGroup OBJECT-GROUP
OBJECTS { teLinkNumberingType, OBJECTS { teLinkNumberingType,
teLinkIpAddrType,
teLinkIpAddr, teLinkIpAddr,
teLinkRemoteIpAddr, teLinkRemoteIpAddr,
teLinkMetric, teLinkMetric,
teLinkMuxCapability, teLinkMuxCapability,
teLinkProtectionType, teLinkProtectionType,
teLinkWorkingPriority, teLinkWorkingPriority,
teLinkResourceClass, teLinkResourceClass,
teLinkIncomingIfId, teLinkIncomingIfId,
teLinkOutgoingIfId, teLinkOutgoingIfId,
teLinkFlooding, teLinkFlooding,
skipping to change at page 42, line 18 skipping to change at page 45, line 32
teLinkDescrPriority, teLinkDescrPriority,
teLinkMinReservableBandwidth, teLinkMinReservableBandwidth,
teLinkMaxReservableBandwidth, teLinkMaxReservableBandwidth,
teLinkDescrRowStatus, teLinkDescrRowStatus,
teLinkDescrStorageType, teLinkDescrStorageType,
dataBearingChannelLinkMuxCapability, dataBearingChannelLinkMuxCapability,
dataBearingChannelPreferredProtection, dataBearingChannelPreferredProtection,
dataBearingChannelCurrentProtection, dataBearingChannelCurrentProtection,
dataBearingChannelRowStatus, dataBearingChannelRowStatus,
dataBearingChannelStorageType, dataBearingChannelStorageType,
linkBundlingTrapEnable 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
OBJECTS { teLinkOspfLinkType, OBJECTS { teLinkOspfLinkType,
skipping to change at page 44, line 7 skipping to change at page 47, line 19
END END
11. Security Considerations 11. Security Considerations
It is clear that this MIB is potentially useful for monitoring of It is clear that this MIB is potentially useful for monitoring of
link bundling enabled devices. This MIB can also be used for confi- link bundling enabled devices. This MIB can also be used for confi-
guration of certain objects, and anything that can be configured can guration of certain objects, and anything that can be configured can
be incorrectly configured, with potentially disastrous results. be incorrectly configured, with potentially disastrous results.
At this writing, no security holes have been identified beyond those At this writing, no security holes have been identified beyond those
that SNMP Security [SNMPArch] is itself intended to address. These that SNMP Security [RFC2571] is itself intended to address. These
relate to primarily controlled access to sensitive information and relate to primarily controlled access to sensitive information and
the ability to configure a device - or which might result from opera- the ability to configure a device - or which might result from opera-
tor error, which is beyond the scope of any security architecture. tor error, which is beyond the scope of any security architecture.
There are a number of management objects defined in this MIB which There are a number of management objects defined in this MIB which
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
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 [IPSEC]),
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 [SNMPv3USM] and the View-based of the User-based Security Model [RFC2574] and the View-based Access
Access Control [SNMPv3VACM] is recommended. It is then a Control [RFC2575] is recommended. It is then a customer/user respon-
customer/user responsibility to ensure that the SNMP entity giving sibility to ensure that the SNMP entity giving access to an instance
access to an instance of this MIB is properly configured to give of this MIB is properly configured to give access to the objects only
access to the objects only to those principals (users) that have leg- to those principals (users) that have legitimate rights to indeed GET
itimate 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 represent a customer's interface to the OSPF/MPLS network. that they can be used to derive the network topology, e.g. list of
Allowing uncontrolled access to these objects could result in mali- nodes and their IP address (teLinkTable), list of data-bearing chan-
cious and unwanted disruptions of network traffic or incorrect confi- nels (dataBearingChannelTable) in addition to usage of network
gurations for these customers. There are no objects that are particu- resources (teLinkBandwidthTable and
dataBearingChannelBandwidthTable). Allowing uncontrolled access to
these objects could result in malicious and unwanted disruptions of
network traffic, incorrect network configuration or theft of competi-
tive business information. There are no objects that are particu-
larly sensitive in their own right, such as passwords or monetary larly sensitive in their own right, such as passwords or monetary
amounts. 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
[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-kompella-mpls-bundle-05.txt>, Internet Draft <draft-ietf-mpls-bundle-01.txt>,
February 2001. November 2001.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Rajagopalan, B., Rekhter, Y., Berger, L., Rajagopalan, B.,
Basak, D., Sandick, H., Zinin, A., and Basak, D., Sandick, H., Zinin, A., and
Banarjee, A., "Link Management Protocol", Banarjee, A., "Link Management Protocol",
Internet Draft <draft-ietf-mpls-lmp-02.txt>, Internet Draft <draft-ccamp-lmp-02.txt>,
March 2001. November 2001.
[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-04.txt>, <draft-ietf-mpls-generalized-signaling-07.txt>,
May 2001. November 2001.
[GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D.,
Banarjee, A., Basak, D., Berger, L., Bernstein, G., Banarjee, A., Basak, D., Berger, L., Bernstein, G.,
Drake, J., Fan, Y., Fedyk, D., Grammel, G., Kompella, Dharanikota, S., Drake, J., Fan, Y., Fedyk, D.,
K., Grammel, G., Guo, D., Kompella, K., Kullberg, A.,
Kullberg, A., Lang, J., Liaw, F., Nadeau, T., Lang, J., Liaw, F., Nadeau, T., Ong, L.,
Papadimitriou, D., Pendarakis, D., Rajagopalan, B., Papadimitriou, D., Pendarakis, D., Rajagopalan, B.,
Rekhter, Y., Saha, Sandick, H., D., Sharma, V., Rekhter, Y., Saha, D., Sandick, H., Sharma, V.,
Swallow, G., Tang, Z., Yu, J., Zinin, A., Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J.,
"Generalized Multi-Protocol Label Switching (GMPLS) Zinin, A., "Generalized Multi-Protocol Label Switching
Architecture", Internet Draft (GMPLS) Architecture", Internet Draft
<draft-ietf-ccamp-gmpls-architecture-00.txt>, <draft-ietf-ccamp-gmpls-architecture-01.txt>,
June 2001. November 2001.
[OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to [OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to
OSPF", Internet Draft OSPF", Internet Draft
<draft-katz-yeung-ospf-traffic-05.txt>, June 2001. <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-kompella-ospf-gmpls-extensions-02.txt>, <draft-ietf-ccamp-ospf-gmpls-extensions-04.txt>,
July 2001. February 2002.
[LSP-HIER] Kompella, K., Rekhter, Y., LSP Hierarchy with MPLS TE, [LSP-HIER] Kompella, K., Rekhter, Y., LSP Hierarchy with MPLS TE,
Internet Draft <draft-ietf-mpls-lsp-hierarchy-02.txt>, Internet Draft <draft-ietf-mpls-lsp-hierarchy-03.txt>,
February 2001. May 2001.
[ZININ] Zinin, A., SHand, M., "Flooding optimizations in link- [ZININ] Zinin, A., SHand, M., "Flooding optimizations in link-
state routing protocols", Internet Draft, state routing protocols", Internet Draft,
<draft-ietf-ospf-isis-flood-opt-01.txt>, March 2001. <draft-ietf-ospf-isis-flood-opt-01.txt>, March 2001.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also: RFC 1700, October 1994. See also:
http://www.isi.edu/in-notes/iana/assignments/smi- http://www.isi.edu/in-notes/iana/assignments/smi-
numbers 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 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib
[SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999. Frameworks", RFC 2571, April 1999.
[SMIv1] Rose, M., and K. McCloghrie, "Structure and [RFC1155] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP- Identification of Management Information for TCP/IP-
based Internets", RFC 1155, May 1990. based Internets", STD 16, RFC 1155, May 1990.
[SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions",
Definitions", RFC 1212, March 1991. STD 16, RFC 1212, March 1991.
[SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use [RFC1215] M. Rose, "A Convention for Defining Traps for use with
with the SNMP", RFC 1215, March 1991. 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,
"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, [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, Network Management Protocol (SNMP)", RFC 2572, April
April 1999. 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April Management Protocol (SNMPv3)", RFC 2574, April 1999.
1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Waldbusser, "Protocol Operations for Version 2 of "Protocol Operations for Version 2 of the Simple
the Simple Network Management Protocol (SNMPv2)", Network Management Protocol (SNMPv2)", RFC 1905,
RFC 1905, January 1996. January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2573, April 1999. Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
based Access Control Model (VACM) for the Simple Access Control Model (VACM) for the Simple Network
Network Management Protocol (SNMP)", RFC 2575, Management Protocol (SNMP)", RFC 2575, April 1999.
April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April Network Management Framework", RFC 2570, April 1999.
1999.
[SMIv2] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser,
"Structure of Management Information
Version 2 (SMIv2)", RFC 2578, April 1999.
[SNMPv2TC] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser,
"Textual Conventions for SMIv2",
RFC 2579, April 1999.
[SNMPv2Conf] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M., and S. Waldbusser,
"Conformance Statements for SMIv2",
RFC 2580, April 1999.
[SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", RFC 1157, May
1990.
[SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S.
Waldbusser, "Introduction to Community-based
SNMPv2", RFC 1901, January 1996.
[SNMPv2TM] 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.
[SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2272,
January 1998.
[SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April
1999.
[SNMPv2PO] 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.
[SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3
Applications", RFC 2273, January 1998.
[SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-
based Access Control Model (VACM) for the Simple
Network Management Protocol (SNMP)", RFC 2575,
April 1999.
[IPSEC] Kent, S., and Atkinson, R., "Security Architecture [IPSEC] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November for the Internet Protocol", RFC 2401, November
1998. 1998.
[IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate [BCP14] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
14. Authors' Addresses 14. Authors' Addresses
Martin Dubuc Thomas D. Nadeau Martin Dubuc Thomas D. Nadeau
edgeflow, Inc. Cisco Systems, Inc. Meriton Networks Cisco Systems, Inc.
329 March Rd. 300 Apollo Drive 3026 Solandt Road 300 Apollo Drive
Kanata, ON, CANADA K2K 2E1 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@edgeflow.com Email: tnadeau@cisco.com Email: martin.dubuc@meriton.com Email: tnadeau@cisco.com
Sudheer Dharanikota Jonathan P. Lang Sudheer Dharanikota Jonathan P. Lang
Nayna Networks, Inc. Calient Networks, Inc. Nayna Networks, Inc. Calient Networks, Inc.
157 Topaz Street 25 Castilian Drive 157 Topaz Street 25 Castilian Drive
Milipitas, CA 95035 Goleta, CA 93117 Milipitas, CA 95035 Goleta, CA 93117
Phone: +1-408-956-8000 x357 Email: jplang@calient.net Phone: +1-408-956-8000 x357 Email: jplang@calient.net
Email: sudheer@nayna.com Email: sudheer@nayna.com
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this docu- included on all such copies and derivative works. However, this docu-
ment itself may not be modified in any way, such as by removing the ment itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop- Internet organizations, except as needed for the purpose of develop-
 End of changes. 

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