draft-ietf-mpls-telink-mib-03.txt   draft-ietf-mpls-telink-mib-04.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Internet Draft
Category: Standards Track Sudheer Dharanikota Category: Standards Track Sudheer Dharanikota
Expires: February 2003 Expires: March 2004
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Rincon Networks Rincon Networks
August 2003 September 2003
Traffic Engineering Link Management Information Base Traffic Engineering Link Management Information Base
draft-ietf-mpls-telink-mib-03.txt draft-ietf-mpls-telink-mib-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line 24 skipping to change at page 2, line 24
6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4 6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4
6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 5 6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 5
6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5 6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5
6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5 6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5
7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5 7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5
8. Application of the Interfaces Group to TE Links . . . . . . . . . 9 8. Application of the Interfaces Group to TE Links . . . . . . . . . 9
8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9 8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9
8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11 8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11
9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13 9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13
10. Intellectual Property Considerations . . . . . . . . . . . . . . 50 10. Intellectual Property Considerations . . . . . . . . . . . . . . 50
11. Security Considerations . . . . . . . . . . . . . . . . . . . . 51 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 50
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 51 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 51
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 52 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 52
13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53
14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53
15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 54 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 54
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Introduction 2. Introduction
OSPF [OSPF], Generalized MPLS (GMPLS) [RFC3471] and the Link Manage- OSPF [OSPF], Generalized MPLS (GMPLS) [RFC3471] and the Link
ment Protocol (LMP) [LMP] use the concept of traffic engineering (TE) Management Protocol (LMP) [LMP] use the concept of traffic
links to abstract link properties. The effect of this approach is the engineering (TE) links to abstract link properties. The effect of
reduction of the amount of routing information exchanged in the this approach is the reduction of the amount of routing information
network, which improves routing scalability. In addition, the use of exchanged in the network, which improves routing scalability. In
TE link allows the implementation of new capabilities such as link addition, the use of TE link allows the implementation of new
protection. capabilities such as link protection.
We present in this document a MIB module that can be used to manage We present in this document a MIB module that can be used to manage
TE links and their extension, the bundled link. This MIB module TE links and their extension, the bundled link. This MIB module
enables both the configuration and the performance monitoring of TE enables both the configuration and the performance monitoring of TE
links and bundled link. links and bundled link.
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
[RFC2119]. [RFC2119].
3. Terminology 3. Terminology
This document uses terminology from the documents describing link This document uses terminology from the documents describing link
bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. bundling [BUNDLING] and G-MPLS [GMPLS-ARCH].
The link bundling feature is designed to aggregate one or more simi- The link bundling feature is designed to aggregate one or more
lar entities between a node pair into a bundled link [BUNDLING]. In similar entities between a node pair into a bundled link [BUNDLING].
the document, those entities are referred to as TE links. A TE link In the document, those entities are referred to as TE links. A TE
is a subinterface capable of carrying MPLS traffic engineered traf- link is a subinterface capable of carrying MPLS traffic engineered
fic. A TE Link may be comprised of only one underlying component traffic. A TE Link may be comprised of only one underlying component
link. In cases where more than one component links are to be com- link. In cases where more than one component links are to be
bined, multiple component links should be created with differing pri- combined, multiple component links should be created with differing
orities to indicate hot-standby or parallel utilization. priorities to indicate hot-standby or parallel utilization.
A bundled link is just another kind of Traffic Engineering (TE) link A bundled link is just another kind of Traffic Engineering (TE) link
(see [GMPLS-OSPF]). A link bundle is a subinterface which bounds the (see [GMPLS-OSPF]). A link bundle is a subinterface which bounds the
traffic of a group of one or more TE links. There should be more than traffic of a group of one or more TE links. There should be more than
one TE Link in a link bundle, but this is not a requirement. Fur- one TE Link in a link bundle, but this is not a requirement.
thermore, if there are more than one TE link in a link bundle at some Furthermore, if there are more than one TE link in a link bundle at
time, and at some point later, all but one of the links are deleted, some time, and at some point later, all but one of the links are
the agent may choose to either delete the link bundle, or it may deleted, the agent may choose to either delete the link bundle, or it
choose to leave it intact. Traffic counters on a link bundle are may 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. Feature Checklist 4. Feature Checklist
The TE Link MIB module (TE-LINK-MIB) is designed to satisfy the fol- The TE Link MIB module (TE-LINK-MIB) is designed to satisfy the
lowing requirements and constraints: following requirements and constraints:
- The MIB module supports the management of TE links, including - The MIB module supports the management of TE links, including
bundled links. bundled links.
- Support is provided for configuration of traffic engineering - Support is provided for configuration of traffic engineering
parameters associated with TE links. parameters associated with TE links.
- The MIB module is used to monitor the priority-based component - The MIB module is used to monitor the priority-based component
link and TE link bandwidth values. link and TE link bandwidth values.
skipping to change at page 4, line 27 skipping to change at page 4, line 27
the TE links. the TE links.
- Configuring the component links including the bandwidth - Configuring the component links including the bandwidth
parameters and associating the component links with the parameters and associating the component links with the
appropriate TE link. appropriate TE link.
- Associating the TE links with the appropriate bundled link. - Associating the TE links with the appropriate bundled link.
6. Brief Description of MIB Objects 6. Brief Description of MIB Objects
Sections 6.1-6.4 describe objects pertaining to TE links. The MIB Sections 6.1-6.4 describe objects pertaining to TE links while
objects were derived from the link bundling document [BUNDLING]. Sections 6.5-6.7 describe objects pertaining to component links. The
MIB objects were derived from the link bundling document [BUNDLING].
6.1. teLinkTable 6.1. teLinkTable
This table represents the TE links, including bundled links, and This table represents the TE links, including bundled links, and
their generic traffic engineering parameters. their generic traffic engineering parameters.
6.2. teLinkDescriptorTable 6.2. teLinkDescriptorTable
This table represents the TE link interface switching capability This table represents the TE link interface switching capability
descriptors. descriptors.
skipping to change at page 5, line 17 skipping to change at page 5, line 17
This table enumerates the component links and their generic traffic This table enumerates the component links and their generic traffic
engineering parameters. engineering parameters.
6.6. componentLinkDescriptorTable 6.6. componentLinkDescriptorTable
This table enumerates the interface switching capability descriptors This table enumerates the interface switching capability descriptors
that each component link supports. that each component link supports.
6.7. componentLinkBandwidthTable 6.7. componentLinkBandwidthTable
The component link bandwidth table specifies the priority-based band- The component link bandwidth table specifies the priority-based
width values associated with the component links. bandwidth values associated with the component links.
Component links that belong to the same TE link must be compatible. Component links that belong to the same TE link must be compatible.
If these two tables are managed independently, mechanisms should be If these two tables are managed independently, mechanisms should be
put in place to ensure consistency between the two tables. TE links put in place to ensure consistency between the two tables. TE links
that form a bundled link must have compatible traffic engineering that form a bundled link must have compatible traffic engineering
parameters (resource class, link metric and protection type). parameters (resource class, link metric and protection type).
The link descriptors of the teLinkDescriptorTable can be derived from The link descriptors of the teLinkDescriptorTable can be derived from
the link descriptors of the componentLinkDescrTable. the link descriptors of the componentLinkDescrTable.
Some of the bandwidth parameters of the teLinkTable, teLinkDescrip- Some of the bandwidth parameters of the teLinkTable,
torTable, teLinkBandwidthTable are derived from the bandwidth parame- teLinkDescriptorTable, teLinkBandwidthTable are derived from the
ters of the componentLinkTable, componentLinkDescriptorTable and com- bandwidth parameters of the componentLinkTable,
ponentLinkBandwidthTable (maximum reservable bandwidth, minimum LSP componentLinkDescriptorTable and componentLinkBandwidthTable (maximum
bandwidth, maximum LSP bandwidth at specified priority and unreserved reservable bandwidth, minimum LSP bandwidth, maximum LSP bandwidth at
bandwidth). specified priority and unreserved bandwidth).
7. Example of Bundled Link Setup 7. Example of Bundled Link Setup
In this section we provide a brief example of using the MIB In this section we provide a brief example of using the MIB
objects described in section 10 to set up a bundled link. objects described in section 10 to set up a bundled link.
While this example is not meant to illustrate every nuance of the While this example is not meant to illustrate every nuance of the
MIB module, it is intended as an aid to understanding some MIB module, 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 module itself. More details on the use of the ifStackTable MIB module itself. More details on the use of the ifStackTable
to establish relationship between bundled links, TE links and to establish relationship between bundled links, TE links and
skipping to change at page 9, line 17 skipping to change at page 9, line 17
The Interfaces Group [RFC2863] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing TE Link interfaces extensions to the Interfaces Group for managing TE Link interfaces
as logical interfaces. as logical interfaces.
This memo assumes the interpretation of the Interfaces Group to be This memo assumes the interpretation of the Interfaces Group to be
in accordance with [RFC2863] which states that the interfaces table in accordance with [RFC2863] which states that the interfaces table
(ifTable) contains information on the managed resource's (ifTable) contains information on the managed resource's
interfaces and that each sub-layer below the internetwork layer of interfaces and that each sub-layer below the internetwork layer of
a network interface is considered an interface. Thus, the TE Link a network interface is considered an interface. Thus, the TE Link
interface is represented as an entry in the ifTable. The inter- interface is represented as an entry in the ifTable. The
relation of entries in the ifTable is defined by Interfaces Stack interrelation of entries in the ifTable is defined by Interfaces
Group defined in [RFC2863]. Stack Group defined in [RFC2863].
When using TE Link interfaces, the interface stack table might appear When using TE Link interfaces, the interface stack table might appear
as follows: as follows:
+----------------------------------------+ +----------------------------------------+
| TE link-interface ifType = teLink(200) + | TE link-interface ifType = teLink(200) +
+----------------------------------------+ +----------------------------------------+
| Underlying Layer... + | Underlying Layer... +
+----------------------------------------+ +----------------------------------------+
skipping to change at page 13, line 26 skipping to change at page 13, line 26
TEXTUAL-CONVENTION, RowStatus, StorageType TEXTUAL-CONVENTION, RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB; FROM INET-ADDRESS-MIB;
teLinkStdMIB MODULE-IDENTITY teLinkStdMIB MODULE-IDENTITY
LAST-UPDATED "200308261200Z" -- 26 August 2003 12:00:00 EST LAST-UPDATED "200309041200Z" -- 4 September 2003 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
Email: dubuc.consulting@rogers.com Email: dubuc.consulting@rogers.com
Sudheer Dharanikota Sudheer Dharanikota
Email: sudheer@ieee.org Email: sudheer@ieee.org
Thomas D. Nadeau Thomas D. Nadeau
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
skipping to change at page 14, line 6 skipping to change at page 14, line 6
DESCRIPTION DESCRIPTION
"Copyright (C) 2003 The Internet Society. This version of "Copyright (C) 2003 The Internet Society. This version of
this MIB module is part of RFC XXXX; see the RFC this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices. itself for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
MPLS traffic engineering links as defined in MPLS traffic engineering links as defined in
'Link Bundling in MPLS Traffic Engineering'." 'Link Bundling in MPLS Traffic Engineering'."
-- Revision history. -- Revision history.
REVISION REVISION
"200308261200Z" -- 26 August 2003 12:00:00 EST "200309041200Z" -- 4 September 2003 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC "Initial version published as RFC xxxx (to be assigned by RFC
Editor)" Editor)"
::= { transmission xxx } -- To be assigned by IANA. ::= { transmission xxx } -- To be assigned by IANA.
-- Request to assign 200 which is -- Request to assign 200 which is
-- ifType value for teLink. -- ifType value for teLink.
-- Textual Conventions -- Textual Conventions
TeLinkPriority ::= TEXTUAL-CONVENTION TeLinkPriority ::= TEXTUAL-CONVENTION
skipping to change at page 15, line 26 skipping to change at page 15, line 26
sdhItuSonetAnsi(5), sdhItuSonetAnsi(5),
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
fiberChannel(11) fiberChannel(11)
} }
TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"SONET/SDH indication type." "This convention is used to indicate whether the interface
supports Standard or Arbitrary SONET/SDH. The values used
in this textual convention are as specified in the
interface switching capability specific information field."
REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to
-- [GMPLS-OSPF]
SYNTAX INTEGER { SYNTAX INTEGER {
standard(0), standard(0),
arbitrary(1) arbitrary(1)
} }
-- Top level components of this MIB module -- Top level components of this MIB module
-- Notifications -- Notifications
teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 } teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 }
-- Tables, Scalars -- Tables, Scalars
skipping to change at page 39, line 9 skipping to change at page 39, line 14
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
componentLinkBandwidthTable. Conceptual rows componentLinkBandwidthTable. Conceptual rows
having the value 'permanent' need not allow write-access having the value 'permanent' need not allow write-access
to any columnar object in the row." to any columnar object in the row."
::= { componentLinkBandwidthEntry 5 } ::= { componentLinkBandwidthEntry 5 }
-- End of componentLinkBandwidthTable -- End of componentLinkBandwidthTable
-- Module compliance -- Module compliance
teLinkGroups teLinkCompliances
OBJECT IDENTIFIER ::= { teLinkConformance 1 } OBJECT IDENTIFIER ::= { teLinkConformance 1 }
teLinkCompliances teLinkGroups
OBJECT IDENTIFIER ::= { teLinkConformance 2 } OBJECT IDENTIFIER ::= { teLinkConformance 2 }
teLinkModuleFullCompliance MODULE-COMPLIANCE teLinkModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support read-create
configuration and monitoring of TE Link MIB module." so that both configuration and monitoring of TE links can
be accomplished via this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { teLinkGroup, MANDATORY-GROUPS { teLinkGroup,
teLinkBandwidthGroup, teLinkBandwidthGroup,
componentLinkBandwidthGroup } componentLinkBandwidthGroup }
GROUP teLinkSrlgGroup GROUP teLinkSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for G-MPLS enabled devices." "This group is mandatory for G-MPLS enabled devices."
skipping to change at page 41, line 45 skipping to change at page 42, line 4
not required." not required."
::= { teLinkCompliances 1 } ::= { teLinkCompliances 1 }
teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents that support the "Compliance statement for agents that support the
monitoring of TE link MIB module." monitoring of TE link MIB module."
MODULE -- this module MODULE -- this module
-- The mandatory groups have to be implemented
-- by all devices supporting TE links. However, they may all
-- be supported as read-only objects in the case where manual
-- configuration is unsupported.
MANDATORY-GROUPS { teLinkGroup, MANDATORY-GROUPS { teLinkGroup,
teLinkBandwidthGroup, teLinkBandwidthGroup,
componentLinkBandwidthGroup } componentLinkBandwidthGroup }
GROUP teLinkSrlgGroup GROUP teLinkSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for G-MPLS enabled devices." "This group is mandatory for G-MPLS enabled devices."
GROUP teLinkPscGroup GROUP teLinkPscGroup
DESCRIPTION DESCRIPTION
skipping to change at page 45, line 4 skipping to change at page 45, line 5
"Write access is not required." "Write access is not required."
-- teLinkSrlgTable -- teLinkSrlgTable
OBJECT teLinkSrlgRowStatus OBJECT teLinkSrlgRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT teLinkSrlgStorageType OBJECT teLinkSrlgStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- teLinkBandwidthTable -- teLinkBandwidthTable
OBJECT teLinkBandwidthUnreserved
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT teLinkBandwidthRowStatus OBJECT teLinkBandwidthRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT teLinkBandwidthStorageType OBJECT teLinkBandwidthStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 48, line 33 skipping to change at page 48, line 29
componentLinkRowStatus, componentLinkRowStatus,
componentLinkStorageType, componentLinkStorageType,
componentLinkDescrSwitchingCapability, componentLinkDescrSwitchingCapability,
componentLinkDescrEncodingType, componentLinkDescrEncodingType,
componentLinkDescrRowStatus, componentLinkDescrRowStatus,
componentLinkDescrStorageType componentLinkDescrStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the management of
resources associated with TE links." resources associated with TE links."
::= { teLinkGroups 1 } ::= { teLinkGroups 1 }
teLinkSrlgGroup OBJECT-GROUP teLinkSrlgGroup OBJECT-GROUP
OBJECTS { teLinkSrlgRowStatus, OBJECTS { teLinkSrlgRowStatus,
teLinkSrlgStorageType teLinkSrlgStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the management of
SRLG resources associated with TE links." SRLG resources associated with TE links."
::= { teLinkGroups 2 } ::= { teLinkGroups 2 }
teLinkBandwidthGroup OBJECT-GROUP teLinkBandwidthGroup OBJECT-GROUP
OBJECTS { teLinkMaximumReservableBandwidth, OBJECTS { teLinkMaximumReservableBandwidth,
teLinkDescrMaxLspBandwidthPrio0, teLinkDescrMaxLspBandwidthPrio0,
teLinkDescrMaxLspBandwidthPrio1, teLinkDescrMaxLspBandwidthPrio1,
teLinkDescrMaxLspBandwidthPrio2, teLinkDescrMaxLspBandwidthPrio2,
teLinkDescrMaxLspBandwidthPrio3, teLinkDescrMaxLspBandwidthPrio3,
teLinkDescrMaxLspBandwidthPrio4, teLinkDescrMaxLspBandwidthPrio4,
teLinkDescrMaxLspBandwidthPrio5, teLinkDescrMaxLspBandwidthPrio5,
teLinkDescrMaxLspBandwidthPrio6, teLinkDescrMaxLspBandwidthPrio6,
teLinkDescrMaxLspBandwidthPrio7, teLinkDescrMaxLspBandwidthPrio7,
teLinkBandwidthUnreserved, teLinkBandwidthUnreserved,
teLinkBandwidthRowStatus, teLinkBandwidthRowStatus,
teLinkBandwidthStorageType teLinkBandwidthStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the management of
the priority-based bandwidth resources associated with the bandwidth resources associated with TE links and
TE links and component links." component links."
::= { teLinkGroups 3 } ::= { teLinkGroups 3 }
componentLinkBandwidthGroup OBJECT-GROUP componentLinkBandwidthGroup OBJECT-GROUP
OBJECTS { componentLinkMaxResBandwidth, OBJECTS { componentLinkMaxResBandwidth,
componentLinkDescrMaxLspBandwidthPrio0, componentLinkDescrMaxLspBandwidthPrio0,
componentLinkDescrMaxLspBandwidthPrio1, componentLinkDescrMaxLspBandwidthPrio1,
componentLinkDescrMaxLspBandwidthPrio2, componentLinkDescrMaxLspBandwidthPrio2,
componentLinkDescrMaxLspBandwidthPrio3, componentLinkDescrMaxLspBandwidthPrio3,
componentLinkDescrMaxLspBandwidthPrio4, componentLinkDescrMaxLspBandwidthPrio4,
componentLinkDescrMaxLspBandwidthPrio5, componentLinkDescrMaxLspBandwidthPrio5,
componentLinkDescrMaxLspBandwidthPrio6, componentLinkDescrMaxLspBandwidthPrio6,
componentLinkDescrMaxLspBandwidthPrio7, componentLinkDescrMaxLspBandwidthPrio7,
componentLinkBandwidthUnreserved, componentLinkBandwidthUnreserved,
componentLinkBandwidthRowStatus, componentLinkBandwidthRowStatus,
componentLinkBandwidthStorageType componentLinkBandwidthStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for the monitoring of "Collection of objects needed for the management of the
bandwidth parameters associated with component links." bandwidth parameters associated with component links."
::= { teLinkGroups 4 } ::= { teLinkGroups 4 }
teLinkPscGroup OBJECT-GROUP teLinkPscGroup OBJECT-GROUP
OBJECTS { teLinkDescrMinLspBandwidth, OBJECTS { teLinkDescrMinLspBandwidth,
teLinkDescrInterfaceMtu, teLinkDescrInterfaceMtu,
componentLinkDescrMinLspBandwidth, componentLinkDescrMinLspBandwidth,
componentLinkDescrInterfaceMtu componentLinkDescrInterfaceMtu
} }
skipping to change at page 50, line 26 skipping to change at page 50, line 24
"Collection of objects needed for devices that are "Collection of objects needed for devices that are
TDM switching capable." TDM switching capable."
::= { teLinkGroups 6 } ::= { teLinkGroups 6 }
-- End of TE-LINK-MIB -- End of TE-LINK-MIB
END END
10. Intellectual Property Considerations 10. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to per- intellectual property or other rights that might be claimed to
tain to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might this document or the extent to which any license under such rights
or might not be available; neither does it represent that it has made might or might not be available; neither does it represent that it
any effort to identify any such rights. Information on the IETF's has made any effort to identify any such rights. Information on the
procedures with respect to rights in standards-track and standards- IETF's procedures with respect to rights in standards-track and
related documentation can be found in BCP-11. Copies of claims of standards-related documentation can be found in BCP-11. Copies of
rights made available for publication and any assurances of licenses claims of rights made available for publication and any assurances of
to be made available, or the result of an attempt made to obtain a licenses to be made available, or the result of an attempt made to
general license or permission for the use of such proprietary rights obtain a general license or permission for the use of such
by implementers or users of this specification can be obtained from proprietary rights by implementers or users of this specification can
the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
11. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environ- environments. The support for SET operations in a non-secure
ment without proper protection can have a negative effect on network environment without proper protection can have a negative effect on
operations. These are the tables and objects and their sensitiv- network operations. These are the tables and objects and their
ity/vulnerability: sensitivity/vulnerability:
- All the tables in this MIB module have routing information in - All the tables in this MIB module have routing information in
them and so they all have the same security attributes. them and so they all have the same security attributes.
Unauthorized changes to attributes of these tables can disrupt Unauthorized changes to attributes of these tables can disrupt
resource allocation in the network. resource allocation in the network.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to con- vulnerable in some network environments. It is thus important to
trol even GET and/or NOTIFY access to these objects and possibly to control even GET and/or NOTIFY access to these objects and possibly
even encrypt the values of these objects when sending them over the to even encrypt the values of these objects when sending them over
network via SNMP. These are the tables and objects and their sensi- the network via SNMP. These are the tables and objects and their
tivity/vulnerability: sensitivity/vulnerability:
- IP address entries in the teLinkTable (teLinkLocalIpAddr and - IP address entries in the teLinkTable (teLinkLocalIpAddr and
teLinkRemoteIpAddr) may reveal the internals of a network provider teLinkRemoteIpAddr) may reveal the internals of a network provider
IP address space. IP address space.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), includ- provided by the SNMPv3 framework (see [RFC3410], section 8),
ing full support for the SNMPv3 cryptographic mechanisms (for authen- including full support for the SNMPv3 cryptographic mechanisms (for
tication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOM- Further, deployment of SNMP versions prior to SNMPv3 is NOT
MENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
cryptographic security. It is then a customer/operator responsibility enable cryptographic security. It is then a customer/operator
to ensure that the SNMP entity giving access to an instance of this responsibility to ensure that the SNMP entity giving access to an
MIB module is properly configured to give access to the objects only instance of this MIB module is properly configured to give access to
to those principals (users) that have legitimate rights to indeed GET the objects only to those principals (users) that have legitimate
or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
12. Acknowledgments 12. Acknowledgments
The authors would like to acknowledge the contribution of Dmitry The authors would like to acknowledge the contribution of Dmitry
Ryumkin. Ryumkin.
13. References 13. References
13.1. Normative References 13.1. Normative References
skipping to change at page 54, line 8 skipping to change at page 54, line 6
14. Authors' Addresses 14. Authors' Addresses
Martin Dubuc Thomas D. Nadeau Martin Dubuc Thomas D. Nadeau
Email: dubuc.consulting@rogers.com Cisco Systems, Inc. Email: dubuc.consulting@rogers.com Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Sudheer Dharanikota Jonathan P. Lang Sudheer Dharanikota Jonathan P. Lang
Email: sudheer@avici.com Rincon Networks, Inc. Email: sudheer@ieee.org Rincon Networks, Inc.
110 El Paseo 110 El Paseo
Santa Barbara, CA 93101 Santa Barbara, CA 93101
Email: jplang@ieee.org Email: jplang@ieee.org
15. Full Copyright Statement 15. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). 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
ment itself may not be modified in any way, such as by removing the document itself may not be modified in any way, such as by removing
copyright notice or references to the Internet Society or other the 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
ing Internet standards in which case the procedures for copyrights developing Internet standards in which case the procedures for
defined in the Internet Standards process must be followed, or as copyrights defined in the Internet Standards process must be
required to translate it into languages other than English. followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. This revoked by the Internet Society or its successors or assigns. This
document and the information contained herein is provided on an "AS document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE. OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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