draft-ietf-ccamp-gmpls-ted-mib-15.txt   rfc6825.txt 
INTERNET-DRAFT Masanori Miyazawa Internet Engineering Task Force (IETF) M. Miyazawa
Intended status: Proposed Standard KDDI R&D Labs Request for Comments: 6825 KDDI R&D Labs
Expires: April 5, 2013 Category: Standards Track T. Otani
Tomohiro Otani ISSN: 2070-1721 K. Kumaki
Kenji Kumaki KDDI Corporation
KDDI Corporation T. Nadeau
Juniper Networks
Thomas D. Nadeau January 2013
November 6, 2012
Traffic Engineering Database Management Information Base in support of Traffic Engineering Database Management Information Base
MPLS-TE/GMPLS in Support of MPLS-TE/GMPLS
draft-ietf-ccamp-gmpls-ted-mib-15.txt Abstract
Status of this Memo This memo defines the Management Information Base (MIB) objects for
managing the Traffic Engineering Database (TED) information with
extensions in support of the Multiprotocol Label Switching (MPLS)
with Traffic Engineering (TE) as well as Generalized MPLS (GMPLS) for
use with network management protocols.
This Internet-Draft is submitted to IETF in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
The list of current Internet-Drafts can be accessed at Information about the current status of this document, any errata,
http://www.ietf.org/ietf/1id-abstracts.txt and how to provide feedback on it may be obtained at
The list of Internet-Draft Shadow Directories can be accessed at http://www.rfc-editor.org/info/rfc6825.
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November 10 Contributions published or made publicly available before November
2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Abstract
This memo defines the Management Information Base (MIB) objects in
order to manage traffic engineering database (TED) information with
extension in support of Multi-Protocol Label Switching (MPLS) with
traffic engineering (TE) as well as Generalized MPLS (GMPLS) for use
with network management protocols.
Table of Contents Table of Contents
Status of this Memo ............................................... 1 1. The Internet-Standard Management Framework ......................3
Abstract .......................................................... 2 2. Introduction ....................................................3
1. The Internet-Standard Management Framework ................... 3 3. Overview ........................................................4
2. Introduction ................................................. 3 3.1. Conventions Used in This Document ..........................4
3. Overview ..................................................... 3 3.2. Terminology ................................................4
3.1 Conventions used in this document ............................ 3 3.3. Acronyms ...................................................5
3.2 Terminology .................................................. 4 4. Motivations .....................................................5
3.3 Acronyms ..................................................... 4 5. Brief Description of MIB Module .................................5
4. Motivations .................................................. 4 5.1. tedTable ...................................................5
5. Brief Description of MIB Modules ............................. 4 5.2. tedLocalIfAddrTable ........................................5
5.1 tedTable ..................................................... 4 5.3. tedRemoteIfAddrTable .......................................5
5.2 tedLocalIfAddrTable .......................................... 4 5.4. tedSwCapTable ..............................................6
5.3 tedRemoteIfAddrTable ......................................... 4 5.5. tedSrlgTable ...............................................6
5.4 tedSwCapTable ................................................ 5 6. Example of the TED MIB Module Usage .............................6
5.5 tedSrlgTable ................................................. 5 7. TED MIB Module Definitions in Support of GMPLS ..................9
6. Example of the TED MIB Module Usage .......................... 5 8. Security Considerations ........................................35
7. TED MIB Module Definitions in support of GMPLS ............... 6 9. IANA Considerations ............................................36
8. Security Consideration ...................................... 29 10. References ....................................................36
9. IANA Considerations ......................................... 30 10.1. Normative References .....................................36
9.1 IANA Considerations for TED-MIB ............................. 30 10.2. Informative References ...................................37
10. References .................................................. 30 11. Acknowledgments ...............................................39
10.1 Normative References ........................................ 30
10.2 Informative References ...................................... 30
11. Acknowledgment .............................................. 32
12. Authors' Addresses .......................................... 33
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
The OSPF MIB was originally defined for OSPF version2 in support of The OSPF MIB was originally defined for OSPF version 2 in support of
IPv4 [RFC4750] and extended to support the Internet Protocol IPv4 [RFC4750] and extended to support the Internet Protocol
version6(IPv6) as OSPF version3 MIB [RFC5643]. The ISIS MIB is also version 6 (IPv6) as OSPF version 3 MIB [RFC5643]. The IS-IS MIB is
defined as [RFC4444]. On the other side, MPLS/GMPLS based traffic also defined in [RFC4444]. On the other side, MPLS-/GMPLS-based
engineering has so far extended OSPF/ISIS routing protocol with TE traffic engineering has so far extended the OSPF/IS-IS routing
functionality [RFC4202], [RFC3630], [RFC5329], [RFC5307] and protocol with TE functionality [RFC4202] [RFC3630] [RFC5329]
[RFC5305]. To manage such MPLS-TE/GMPLS networks effectively, routing [RFC5307] [RFC5305]. To manage such MPLS-TE/GMPLS networks
information associated with MPLS/GMPLS TE parameters (TED) is effectively, routing information associated with MPLS/GMPLS TE
preferred for the network management; however, there is no clear parameters is preferred for network management; however, there is no
definition of MPLS/GMPLS TE information in existing MIBs related to clear definition of MPLS/GMPLS TE information in existing MIBs
OSPF(v2 and v3)/ISIS. related to OSPF(v2 and v3)/IS-IS.
This memo defines the Management Information Base (MIB) objects for This memo defines the MIB objects for managing TED in support of
managing TED in support of MPLS-TE/GMPLS for use with network MPLS-TE/GMPLS for use with network management protocols.
management protocols.
This MIB module should be used in conjunction with OSPFv2 MIB, OSPF This MIB module should be used in conjunction with the OSPFv2 MIB,
v3 MIB and ISIS MIB as well as other MIBs defined in [RFC3812], OSPF v3 MIB, and IS-IS MIB, as well as other MIBs defined in
[RFC3813], [RFC4802] and [RFC4803] for the management of MPLS/GMPLS [RFC3812], [RFC3813], [RFC4802], and [RFC4803] for the management of
based traffic engineering information. By implementing such MIB MPLS-/GMPLS-based traffic engineering information. By implementing
modules, it is helpful to simultaneously understand entire MPLS/GMPLS such MIB modules, it is helpful to simultaneously understand the
network such as routing information as well as LSP information using entire MPLS/GMPLS network, for example, understanding routing
a management system. But, note that this MIB module is able to be information as well as LSP information using a management system.
implemented and performed without implementation of other MIB modules However, note that this MIB module is able to be implemented and
when the management system, for example, only comprehends MPLS/GMPLS performed without implementation of other MIB modules when the
topology information such as TE link information. management system, for example, only comprehends MPLS/GMPLS topology
information such as TE link information.
3. Overview 3. Overview
3.1 Conventions used in this document 3.1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
RFC-2119 [RFC2119]. RFC 2119 [RFC2119].
3.2 Terminology 3.2. Terminology
Definitions of key terms for MPLS OAM and GMPLS are found in Definitions of key terms for MPLS Operations, Administration, and
[RFC4377] and [RFC3945], and the reader is assumed to be familiar Maintenance (OAM) and GMPLS are found in [RFC4377] and [RFC3945], and
with those definitions which are not repeated here. the reader is assumed to be familiar with those definitions, which
are not repeated here.
3.3 Acronyms 3.3. Acronyms
GMPLS: Generalized Multi-Protocol Label Switching GMPLS: Generalized Multiprotocol Label Switching
ISIS: Intermediate System to Intermediate System IS-IS: Intermediate System to Intermediate System
LSA: Link state advertisement LSA: Link State Advertisement
LSP: Label Switching Path LSP: Label Switching Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base MIB: Management Information Base
OSPF: Open Shortest Path First OSPF: Open Shortest Path First
PSC: Packet Switch Capable PSC: Packet Switch Capable
SRLG: Shared Risk Link Group SRLG: Shared Risk Link Group
TE: Traffic Engineering TE: Traffic Engineering
TED: Traffic Engineering Database TED: Traffic Engineering Database
TDM: Time Division Multiplexing TDM: Time Division Multiplexing
4. Motivations 4. Motivations
The existing OSPFv2, OSPFv3, ISIS, MPLS and GMPLS MIBs do not provide The existing OSPFv2, OSPFv3, IS-IS, MPLS, and GMPLS MIBs do not
for the management interface to retrieve topology information of MPLS provide for the management interface to retrieve topology information
and GMPLS networks. of MPLS and GMPLS networks.
5. Brief Description of MIB Modules 5. Brief Description of MIB Module
The objects described in this section support the management of TED The objects described in this section support the management of TED
described in [RFC4202], [RFC4203] and [RFC5307] for GMPLS extensions as described in [RFC4202], [RFC4203], and [RFC5307] for GMPLS
as well as in [RFC3630] and [RFC5305] for MPLS/GMPLS. extensions as well as in [RFC3630] and [RFC5305] for MPLS/GMPLS.
5.1 tedTable 5.1. tedTable
The tedTable is basically used to indicate TED information of OSPF-TE The TED table is basically used to indicate TED information of OSPF-
or ISIS-TE. However, this table does not contain information for TE or ISIS-TE. However, this table does not contain information for
Local/Remote interface IP address, Interface Switching Capability the Local/Remote Interface IP Address, Interface Switching Capability
Descriptor and Shared Risk Link Group information within the sub-TLVs Descriptor, or Shared Risk Link Group information within the sub-TLVs
for the Link-TLV. for the Link-TLV.
5.2 tedLocalIfAddrTable 5.2. tedLocalIfAddrTable
The tedLocalIfAddrTable is identical to the Local interface IP The tedLocalIfAddrTable is identical to the Local Interface IP
address information in a sub-TLV for the Link-TLV. This is Address information in a sub-TLV for the Link-TLV. This is
independently defined, because the Interface IP Address sub-TLV may independently defined, because the Interface IP Address sub-TLV may
appear more than once within the same Link-TLV. appear more than once with the same Link-TLV.
5.3 tedRemoteIfAddrTable 5.3. tedRemoteIfAddrTable
The tedRemoteIfAddrTable is identical to the Remote interface IP The tedRemoteIfAddrTable is identical to the Remote Interface IP
address information in a sub-TLV of the Link-TLV. This is Address information in a sub-TLV of the Link-TLV. This is
independently defined, because the Interface IP Address sub-TLV may independently defined, because the Interface IP Address sub-TLV may
appear more than once with the same Link-TLV. appear more than once with the same Link-TLV.
5.4 tedSwCapTable 5.4. tedSwCapTable
The tedSwCapTable is identical to the Interface Switching Capability The tedSwCapTable is identical to the Interface Switching Capability
Descriptor information in a sub-TLV of Link-TLV. This is Descriptor information in a sub-TLV of the Link-TLV. This is
independently defined, because the Interface Switching Capability independently defined, because the Interface Switching Capability
Descriptor sub-TLV may appear more than once with same Link-TLV. Descriptor sub-TLV may appear more than once with the same Link-TLV.
5.5 tedSrlgTable 5.5. tedSrlgTable
The tedSrlgTable is identical to the Shared Risk Link Group The tedSrlgTable is identical to the Shared Risk Link Group
information in a sub-TLV of Link-TLV. Think is independently defined, information in a sub-TLV of the Link-TLV. This table is
because the Shared Risk Link Group sub-TLV may appear more than once independently defined because the Shared Risk Link Group sub-TLV may
with the same Link-TLV. appear more than once with the same Link-TLV.
6.Example of the TED MIB Module Usage 6. Example of the TED MIB Module Usage
In this section, we provide an example of the TED MIB module usage. In this section, we provide an example of the TED MIB module usage.
The following indicates the information of a numbered TE link The following indicates the information of a numbered TE link
originated in a GMPLS controlled node. When TE link information is originated in a GMPLS-controlled node. When TE link information is
retrieved in a MPLS network, GMPLS specific objects such as retrieved in an MPLS network, GMPLS-specific objects such as
tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable and tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable, and
tedSrlgTable are not supported. tedSrlgTable are not supported.
By retrieval of such information periodically, the management system By retrieval of such information periodically, the management system
can comprehend the detailed topology information related to can comprehend the detailed topology information related to
MPLS/GMPLS networks. In particular, the basic TED information can be MPLS/GMPLS networks. In particular, the basic TED information can be
collected by tedTable, local/remote interface IP address information collected by tedTable, and Local/Remote Interface IP Address
related to MPLS/GMPLS network are collected by tedLocalIfAddrTable information related to MPLS/GMPLS networks are collected by
and tedRemoteIfAddrTable. And the attribute information related to tedLocalIfAddrTable and tedRemoteIfAddrTable, and the attribute
GMPLS TE link can be retrieved by tedSwCapTable and tedSrlgTable. information related to GMPLS TE links can be retrieved by
Regarding a fault management, there is no functionality to notify tedSwCapTable and tedSrlgTable. Regarding fault management, there is
network failures in this MIB module. But, if network topologies are no functionality to notify network failures in this MIB module.
changed, the module can notify the change information to the However, if network topologies are changed, the module can notify the
management system by using tedStatusChange, tedEntryCreated and management system of the change information by using tedStatusChange,
tedEntryDeleted. tedEntryCreated, and tedEntryDeleted.
Note that the TED MIB modules are only limited to "read-only" access Note that the TED MIB module is limited to "read-only" access except
except for tedCreatedDeletedNotificationMaxRate and for tedCreatedDeletedNotificationMaxRate and
tedStatusChangeNotificationMaxRate. The TED MIB module is designed to tedStatusChangeNotificationMaxRate. The TED MIB module is designed
be independent of OSPF or ISIS MIBs, however each TE link information to be independent of OSPF or IS-IS MIBs; however, information for
belongs to a node or a link which is managed by the routing protocol. each TE link belongs to a node or a link that is managed by the
routing protocol.
In tedTable: In tedTable:
{ {
tedLinkInformationData.2.3232235777.3232235778.16777264 zeroDotZero tedLinkInformationData.2.3232235777.3232235778.16777264 zeroDotZero
tedLinkType.2.3232235777.3232235778.16777264 pointToPoint(1) tedLinkType.2.3232235777.3232235778.16777264 pointToPoint(1)
tedLinkState.2.3232235777.3232235778.16777264 up(1) tedLinkState.2.3232235777.3232235778.16777264 up(1)
tedAreaId.2.3232235777.3232235778.16777264 0 tedAreaId.2.3232235777.3232235778.16777264 0
tedTeRouterIdAddrType.2.3232235777.3232235778.16777264 ipv4(1) tedTeRouterIdAddrType.2.3232235777.3232235778.16777264 ipv4(1)
tedTeRouterIdAddr.2.3232235777.3232235778.16777264 192.0.2.1 tedTeRouterIdAddr.2.3232235777.3232235778.16777264 192.0.2.1
tedLinkIdAddrType.2.3232235777.3232235778.16777264 ipv4(1) tedLinkIdAddrType.2.3232235777.3232235778.16777264 ipv4(1)
tedLinkIdAddr.2.3232235777.3232235778.16777264 192.0.2.10 tedLinkIdAddr.2.3232235777.3232235778.16777264 192.0.2.10
tedMetric.2.3232235777.3232235778.16777264 1 tedMetric.2.3232235777.3232235778.16777264 1
tedMaxBandwidth.2.3232235777.3232235778.16777264 4d9450c0 tedMaxBandwidth.2.3232235777.3232235778.16777264 4d9450c0
tedMaxReservableBandwidth.2.3232235777.3232235778.16777264 4d9450c0 tedMaxReservableBandwidth.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri0.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri0.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri1.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri1.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri2.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri2.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri3.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri3.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri4.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri4.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri5.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri5.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri6.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri6.2.3232235777.3232235778.16777264 4d9450c0
tedUnreservedBandwidthPri7.2.3232235777.3232235778.16777264 4d9450c0 tedUnreservedBandwidthPri7.2.3232235777.3232235778.16777264 4d9450c0
tedAdministrativeGroup.2.3232235777.3232235778.16777264 0 tedAdministrativeGroup.2.3232235777.3232235778.16777264 0
tedLocalId.2.3232235777.3232235778.16777264 0 tedLocalId.2.3232235777.3232235778.16777264 0
tedRemoteId.2.3232235777.3232235778.16777264 0 tedRemoteId.2.3232235777.3232235778.16777264 0
tedLinkProtectionType.2.3232235777.3232235778.16777264 01 00 00 00 7 tedLinkProtectionType.2.3232235777.3232235778.16777264 01 00 00 00 7
} }
In tedLocalIfAddrTable: In tedLocalIfAddrTable:
{ {
tedLocalIfAddrType.16777264.192.0.2.21 ipv4(1) tedLocalIfAddrType.16777264.192.0.2.21 ipv4(1)
} }
In tedRemoteIfAddrTable: In tedRemoteIfAddrTable:
{ {
skipping to change at page 6, line 30 skipping to change at page 8, line 4
In tedLocalIfAddrTable: In tedLocalIfAddrTable:
{ {
tedLocalIfAddrType.16777264.192.0.2.21 ipv4(1) tedLocalIfAddrType.16777264.192.0.2.21 ipv4(1)
} }
In tedRemoteIfAddrTable: In tedRemoteIfAddrTable:
{ {
tedRemoteIfAddrType.16777264.192.0.2.22 ipv4(1) tedRemoteIfAddrType.16777264.192.0.2.22 ipv4(1)
} }
In tedSwCapTable: In tedSwCapTable:
{ {
tedSwCapType.16777264.1 lsc(150) tedSwCapType.16777264.1 lsc(150)
tedSwCapEncoding.16777264.1 ethernet(2) tedSwCapEncoding.16777264.1 ethernet(2)
tedSwCapMaxLspBandwidthPri0.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri0.16777264.1 4d9450c0
tedSwCapMaxLspBandwidthPri1.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri1.16777264.1 4d9450c0
tedSwCapMaxLspBandwidthPri2.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri2.16777264.1 4d9450c0
tedSwCapMaxLspBandwidthPri3.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri3.16777264.1 4d9450c0
tedSwCapMaxLspBandwidthPri4.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri4.16777264.1 4d9450c0
tedSwCapMaxLspBandwidthPri5.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri5.16777264.1 4d9450c0
tedSwCapMaxLspBandwidthPri6.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri6.16777264.1 4d9450c0
tedSwCapMaxLspBandwidthPri7.16777264.1 4d9450c0 tedSwCapMaxLspBandwidthPri7.16777264.1 4d9450c0
tedSwCapMinLspBandwidth.16777264.1 0 tedSwCapMinLspBandwidth.16777264.1 0
tedSwCapIfMtu.16777264.1 0 tedSwCapIfMtu.16777264.1 0
tedSwCapIndication.16777264.1 standard(0) tedSwCapIndication.16777264.1 standard(0)
} }
In tedSrlgTable: In tedSrlgTable:
{ {
tedSrlg.16777264.1 0 tedSrlg.16777264.1 0
} }
7. TED MIB Definitions in support of GMPLS 7. TED MIB Module Definitions in Support of GMPLS
This MIB module makes references to the follows documents. This MIB module makes references to the following documents:
[RFC2328], [RFC2578], [RFC2580], [RFC3630], [RFC4001], [RFC4203], [RFC2328], [RFC2578], [RFC2580], [RFC3630], [RFC4001], [RFC4203],
[RFC4220], [RFC4444], [RFC4801], [RFC4802], [RFC5305], [RFC5307], [RFC4220], [RFC4444], [RFC4801], [RFC4802], [RFC5305], [RFC5307],
[RFC5329], [RFC5340], [RFC6340] and [ISO10589]. [RFC5329], [RFC5340], [RFC6340], and [ISO10589].
TED-MIB DEFINITIONS ::= BEGIN TED-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission, MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission,
NOTIFICATION-TYPE NOTIFICATION-TYPE
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC 2580
TEXTUAL-CONVENTION, RowPointer TEXTUAL-CONVENTION, RowPointer
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC 2579
IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC
FROM IANA-GMPLS-TC-MIB -- RFC4802 FROM IANA-GMPLS-TC-MIB -- RFC 4802
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB -- RFC4001 FROM INET-ADDRESS-MIB -- RFC 4001
Float32TC Float32TC
FROM FLOAT-TC-MIB -- RFC6340 FROM FLOAT-TC-MIB -- RFC 6340
; ;
tedMIB MODULE-IDENTITY tedMIB MODULE-IDENTITY
LAST-UPDATED "201211060000Z" -- 6 Nov. 2012 00:00:00 GMT LAST-UPDATED "201212210000Z" -- 21 Dec. 2012 00:00:00 GMT
ORGANIZATION "IETF CCAMP Working Group." ORGANIZATION "IETF CCAMP Working Group."
CONTACT-INFO CONTACT-INFO
" Tomohiro Otani " Tomohiro Otani
otani@kddilabs.jp Tm-otani@kddi.com
Masanori Miyazawa Masanori Miyazawa
ma-miyazawa@kddilabs.jp ma-miyazawa@kddilabs.jp
Thomas D. Nadeau Thomas D. Nadeau
tnadeau@lucidvision.com tnadeau@juniper.net
Kenji Kumaki Kenji Kumaki
ke-kumaki@kddilabs.jp ke-kumaki@kddi.com
Comments and discussion to ccamp@ietf.org" Comments and discussion to ccamp@ietf.org"
DESCRIPTION
"This MIB module contains managed object definitions for TED in
support of MPLS/GMPLS TE Database.
Copyright (C) 2012 The IETF Trust. This version of this MIB DESCRIPTION
module is part of RFC xxx; see the RFC itself for full legal "This MIB module contains managed object definitions for TED in
notices." support of MPLS/GMPLS TE Database.
Copyright (c) 2013 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, is permitted pursuant to, and subject to the license
terms contained in, the Simplified BSD License set forth in
Section 4.c of the IETF Trust's Legal Provisions Relating to IETF
Documents (http://trustee.ietf.org/license-info)."
-- Revision history. -- Revision history.
REVISION REVISION
"201211060000Z" -- 6 Nov. 2012 00:00:00 GMT "201212210000Z" -- 21 Dec. 2012 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxx." "Initial version. Published as RFC 6825."
-- RFC-editor pls fill in yyy ::= { transmission 273 }
::= { transmission yyy } -- assigned by IANA; see Section 9 for details.
-- assigned by IANA, see section 9.1 for details
-- Textual Conventions. -- Textual Conventions.
TedAreaIdTC ::= TEXTUAL-CONVENTION TedAreaIdTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The area identifier of the IGP. If OSPF is used to advertise "The area identifier of the IGP. If OSPF is used to advertise
LSA, this represents an ospfArea. If ISIS is used, this LSA, this represents an ospfArea. If IS-IS is used, this
represents an area address." represents an area address."
SYNTAX OCTET STRING (SIZE (0..20)) SYNTAX OCTET STRING (SIZE (0..20))
TedRouterIdTC ::= TEXTUAL-CONVENTION TedRouterIdTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The router identifier. If OSPF is used to advertise LSA, this "The router identifier. If OSPF is used to advertise LSA, this
represents a Router ID. If ISIS is used, this represents a represents a Router ID. If IS-IS is used, this represents a
System ID." System ID."
SYNTAX OCTET STRING (SIZE (0..6)) SYNTAX OCTET STRING (SIZE (0..6))
TedLinkIndexTC ::= TEXTUAL-CONVENTION TedLinkIndexTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The link identifier. If OSPF is used, this represents an "The link identifier. If OSPF is used, this represents an
ospfLsdbID. If ISIS is used, this represents an isisLSPID. If a ospfLsdbID. If IS-IS is used, this represents an isisLSPID.
locally configured link is used, this object represents an If a locally configured link is used, this object represents an
arbitrary value which is locally defined in a router" arbitrary value, which is locally defined in a router."
SYNTAX OCTET STRING (SIZE (0..8)) SYNTAX OCTET STRING (SIZE (0..8))
-- Top level components of this MIB module. -- Top-level components of this MIB module.
tedNotifications OBJECT IDENTIFIER ::= { tedMIB 0 } tedNotifications OBJECT IDENTIFIER ::= { tedMIB 0 }
tedObjects OBJECT IDENTIFIER ::= { tedMIB 1 } tedObjects OBJECT IDENTIFIER ::= { tedMIB 1 }
tedConformance OBJECT IDENTIFIER ::= { tedMIB 2 } tedConformance OBJECT IDENTIFIER ::= { tedMIB 2 }
-- TED Table -- TED Table
tedTable OBJECT-TYPE tedTable OBJECT-TYPE
SYNTAX SEQUENCE OF TedEntry SYNTAX SEQUENCE OF TedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table indicates multiple TED information which has been "This table indicates multiple TED information, which has been
supported by RFC3630 and RFC5305." supported by RFC 3630 and RFC 5305."
::= { tedObjects 1 } ::= { tedObjects 1 }
tedEntry OBJECT-TYPE tedEntry OBJECT-TYPE
SYNTAX TedEntry SYNTAX TedEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains TED information commonly utilized in both "This entry contains TED information commonly utilized in both
MPLS and GMPLS." MPLS and GMPLS."
INDEX { tedLocalRouterId, tedRemoteRouterId, INDEX { tedLocalRouterId, tedRemoteRouterId,
skipping to change at page 10, line 4 skipping to change at page 12, line 36
DESCRIPTION DESCRIPTION
"This object indicates the source of the information about the "This object indicates the source of the information about the
TE link." TE link."
::= { tedEntry 1 } ::= { tedEntry 1 }
tedLocalRouterId OBJECT-TYPE tedLocalRouterId OBJECT-TYPE
SYNTAX TedRouterIdTC SYNTAX TedRouterIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the router ID of the router originating "This object represents the Router ID of the router originating
the LSA. If OSPF is used to advertise LSA, this represents a the LSA. If OSPF is used to advertise LSA, this represents a
Router ID. If ISIS is used, this represents a System ID. Router ID. If IS-IS is used, this represents a System ID.
Otherwise, this represents zero." Otherwise, this represents zero."
REFERENCE REFERENCE
"OSPF Version 2, RFC2328, C.1 "OSPF Version 2, RFC 2328, Appendix C.1
OSPF for IPv6, RFC5340, C.1 OSPF for IPv6, RFC 5340, Appendix C.1
ISO10589, Section 7.1" ISO10589, Section 7.1"
::= { tedEntry 2 } ::= { tedEntry 2 }
tedRemoteRouterId OBJECT-TYPE tedRemoteRouterId OBJECT-TYPE
SYNTAX TedRouterIdTC SYNTAX TedRouterIdTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the router at the remote end of the link "This object indicates the router at the remote end of the link
from the originating router. If OSPF is used to advertise LSA, from the originating router. If OSPF is used to advertise LSA,
this represents a Link ID in the Link TLV. If ISIS is used, this represents a Link ID in the Link TLV. If IS-IS is used,
this represents a neighbor system ID defined in RFC5305. this represents a neighbor System ID defined in RFC 5305.
Otherwise, this represents zero." Otherwise, this represents zero."
REFERENCE REFERENCE
"OSPF Version 2, RFC2328, C.1 "OSPF Version 2, RFC 2328, Appendix C.1
OSPF for IPv6, RFC5340, C.1 OSPF for IPv6, RFC 5340, Appendix C.1
ISO10589, Section 7.1" ISO10589, Section 7.1"
::= { tedEntry 3 } ::= { tedEntry 3 }
tedLinkIndex OBJECT-TYPE tedLinkIndex OBJECT-TYPE
SYNTAX TedLinkIndexTC SYNTAX TedLinkIndexTC
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the link state identifier. If OSPF is "This object indicates the link state identifier. If OSPF is
used, this represents an ospfLsdbID. If ISIS is used, this used, this represents an ospfLsdbID. If IS-IS is used, this
represents an isisLSPID. Otherwise, this represents a unique represents an isisLSPID. Otherwise, this represents a unique
identifier within a node." identifier within a node."
REFERENCE REFERENCE
"OSPF Version 2, RFC2328, A.4.1, "OSPF Version 2, RFC 2328, Appendix A.4.1,
OSPF for IPv6, RFC5340, A.4.2 OSPF for IPv6, RFC 5340, Appendix A.4.2
ISO10589, Section 9.8 " ISO10589, Section 9.8 "
::= { tedEntry 4 } ::= { tedEntry 4 }
tedLinkInformationData OBJECT-TYPE tedLinkInformationData OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If tedLinkInformationSource has the value unknown(0), this "If tedLinkInformationSource has the value unknown(0), this
object MUST contain a value of zeroDotZero. object MUST contain a value of zeroDotZero.
If tedLinkInformationSource has the value locallyConfigured(1), If tedLinkInformationSource has the value locallyConfigured(1),
an implementation can use this object to supply the identifier an implementation can use this object to supply the identifier
of the corresponding row entry in the teLinkTable of TE-LINK- of the corresponding row entry in the teLinkTable of TE-LINK-
STD-MIB (RFC 4220), the identifier of the corresponding row in STD-MIB (RFC 4220), the identifier of the corresponding row in
a local proprietary TE link MIB module, or the value of a local proprietary TE link MIB module, or the value of
zeroDotZero. zeroDotZero.
If tedLinkInformationSource has the value ospfv2(2)and If tedLinkInformationSource has the value ospfv2(2) and
ospfv3(3), an implementation can use this object to supply the ospfv3(3), an implementation can use this object to supply the
identifier of the corresponding row entry in the identifier of the corresponding row entry in the
ospfLocalLsdbTable (OSPFv2-MIB) and the ospfv3AreaLsdbTable ospfLocalLsdbTable (OSPFv2-MIB) and the ospfv3AreaLsdbTable
(OSPFv3-MIB), or the value of zeroDotZero. (OSPFv3-MIB), or the value of zeroDotZero.
If tedLinkInformationSource has the value isis(4), an If tedLinkInformationSource has the value isis(4), an
implementation can use this object to supply the identifier of implementation can use this object to supply the identifier of
the corresponding row entry in the isisAreaAddr of ISIS-MIB the corresponding row entry in the isisAreaAddr of ISIS-MIB
(RFC4444), or the value of zeroDotZero. (RFC 4444), or the value of zeroDotZero.
If tedLinkInformationSource has the value other(5), an If tedLinkInformationSource has the value other(5), an
implementation can use this object to supply the identifier of implementation can use this object to supply the identifier of
the corresponding row entry in the local proprietary MIB module, the corresponding row entry in the local proprietary MIB module,
or the value of zeroDotZero." or the value of zeroDotZero."
::= { tedEntry 5 } ::= { tedEntry 5 }
tedLinkState OBJECT-TYPE tedLinkState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown (0), unknown (0),
up (1), up (1),
down (2) down (2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the actual operational state of this TE "This object represents the actual operational state of this TE
link. For instance, if a row is created in the tedTable, but link. For instance, if a row is created in the TED table, but
the actual TE link is not available for some reason (e.g. when the actual TE link is not available for some reason (e.g., when
there is not yet physical link or manually disable), then the there is not yet a physical link or the link has been manually
object would be down(2) state. In contrast, if a row is added disabled), then the object would be down(2) state.
and the TE link is available, this would be operationally In contrast, if a row is added and the TE link is available,
up(1)." this would be operationally up(1)."
::= { tedEntry 6 } ::= { tedEntry 6 }
tedAreaId OBJECT-TYPE tedAreaId OBJECT-TYPE
SYNTAX TedAreaIdTC SYNTAX TedAreaIdTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the area identifier of the IGP. If OSPF "This object indicates the area identifier of the IGP. If OSPF
is used to advertise LSA, this represents an ospfArea. If ISIS is used to advertise LSA, this represents an ospfArea. If IS-IS
is used, this represents an area address. Otherwise, this is used, this represents an area address. Otherwise, this
represents zero." represents zero."
REFERENCE REFERENCE
"OSPF Version 2, RFC2328, C.2 "OSPF Version 2, RFC 2328, Appendix C.2
OSPF for IPv6, RFC5340, C.2 OSPF for IPv6, RFC 5340, Appendix C.2
ISO10589, Section 9.8" ISO10589, Section 9.8"
::= { tedEntry 7 } ::= { tedEntry 7 }
tedLinkType OBJECT-TYPE tedLinkType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pointToPoint (1), pointToPoint (1),
multiAccess (2) multiAccess (2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the type of the link such as point-to-point or "This indicates the type of the link, such as point to point or
multi-access." multi-access."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.1" RFC 3630, Section 2.5.1"
::= { tedEntry 8 } ::= { tedEntry 8 }
tedTeRouterIdAddrType OBJECT-TYPE tedTeRouterIdAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the TE-Router ID address type. Only "This object indicates the TE-Router ID address type. Only
values unknown(0), ipv4(1) or ipv6(2) are supported. " values unknown(0), ipv4(1), or ipv6(2) are supported."
::= { tedEntry 9 } ::= { tedEntry 9 }
tedTeRouterIdAddr OBJECT-TYPE tedTeRouterIdAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the TE-Router ID." "This object indicates the TE-Router ID."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.4.1 RFC 3630, Section 2.4.1
IS-IS extensions for TE, RFC5305, 4.3" IS-IS extensions for TE, RFC 5305, Section 4.3"
::= { tedEntry 10 } ::= { tedEntry 10 }
tedLinkIdAddrType OBJECT-TYPE tedLinkIdAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the address type of the TE Link ID. Only "This object indicates the address type of the TE Link ID. Only
values unknown(0), ipv4(1) or ipv6(2) are supported." values unknown(0), ipv4(1), or ipv6(2) are supported."
::= { tedEntry 11 } ::= { tedEntry 11 }
tedLinkIdAddr OBJECT-TYPE tedLinkIdAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the Router ID of the neighbor in the case of "This indicates the Router ID of the neighbor in the case of
point-to-point links. This also indicates the interface point-to-point links. This also indicates the interface
address of the designated router in the case of multi-access address of the designated router in the case of multi-access
links." links."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.2 RFC 3630, Section 2.5.2
IS-IS extensions for TE, RFC5305, 4.3" IS-IS extensions for TE, RFC 5305, Section 4.3"
::= { tedEntry 12 } ::= { tedEntry 12 }
tedMetric OBJECT-TYPE tedMetric OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the traffic engineering metric value of the TE "This indicates the traffic engineering metric value of the TE
link." link."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.5 RFC 3630, Section 2.5.5
IS-IS extensions for TE, RFC5305, 3.7" IS-IS extensions for TE, RFC 5305, Section 3.7"
::= { tedEntry 13 } ::= { tedEntry 13 }
tedMaxBandwidth OBJECT-TYPE tedMaxBandwidth OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the maximum bandwidth that can be used on this "This indicates the maximum bandwidth that can be used on this
link in this direction." link in this direction."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.6 RFC 3630, Section 2.5.6
IS-IS extensions for TE, RFC5305, 3.4" IS-IS extensions for TE, RFC 5305, Section 3.4"
::= { tedEntry 14 } ::= { tedEntry 14 }
tedMaxReservableBandwidth OBJECT-TYPE tedMaxReservableBandwidth OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the maximum bandwidth that may be reserved on "This indicates the maximum bandwidth that may be reserved on
this link in this direction." this link in this direction."
skipping to change at page 13, line 39 skipping to change at page 17, line 4
::= { tedEntry 14 } ::= { tedEntry 14 }
tedMaxReservableBandwidth OBJECT-TYPE tedMaxReservableBandwidth OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the maximum bandwidth that may be reserved on "This indicates the maximum bandwidth that may be reserved on
this link in this direction." this link in this direction."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.7 RFC 3630, Section 2.5.7
IS-IS extensions for TE, RFC5305, 3.5" IS-IS extensions for TE, RFC 5305, Section 3.5"
::= { tedEntry 15 } ::= { tedEntry 15 }
tedUnreservedBandwidthPri0 OBJECT-TYPE tedUnreservedBandwidthPri0 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 0." priority 0."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, Section 3.6"
::= { tedEntry 16 } ::= { tedEntry 16 }
tedUnreservedBandwidthPri1 OBJECT-TYPE tedUnreservedBandwidthPri1 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 1." priority 1."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, Section 3.6"
::= { tedEntry 17 } ::= { tedEntry 17 }
tedUnreservedBandwidthPri2 OBJECT-TYPE tedUnreservedBandwidthPri2 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 2." priority 2."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, Section 3.6"
::= { tedEntry 18 } ::= { tedEntry 18 }
tedUnreservedBandwidthPri3 OBJECT-TYPE tedUnreservedBandwidthPri3 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 3." priority 3."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, Section 3.6"
::= { tedEntry 19 } ::= { tedEntry 19 }
tedUnreservedBandwidthPri4 OBJECT-TYPE tedUnreservedBandwidthPri4 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 4." priority 4."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, Section 3.6"
::= { tedEntry 20 } ::= { tedEntry 20 }
tedUnreservedBandwidthPri5 OBJECT-TYPE tedUnreservedBandwidthPri5 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 5." priority 5."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, Section 3.6"
::= { tedEntry 21 } ::= { tedEntry 21 }
tedUnreservedBandwidthPri6 OBJECT-TYPE tedUnreservedBandwidthPri6 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 6." priority 6."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, 3.6"
::= { tedEntry 22 } ::= { tedEntry 22 }
tedUnreservedBandwidthPri7 OBJECT-TYPE tedUnreservedBandwidthPri7 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at the "This indicates the amount of bandwidth not yet reserved at the
priority 7." priority 7."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.8 RFC 3630, Section 2.5.8
IS-IS extensions for TE, RFC5305, 3.6" IS-IS extensions for TE, RFC 5305, Section 3.6"
::= { tedEntry 23 } ::= { tedEntry 23 }
tedAdministrativeGroup OBJECT-TYPE tedAdministrativeGroup OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the Administrative Group which the link belong "This indicates the Administrative Group to which the link
to. Since the value is a bit mask, the link can belong to belongs. Since the value is a bit mask, the link can belong
multiple groups. This is also called Resource Class/Color." to multiple groups. This is also called Resource Class/Color."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.9 RFC 3630, Section 2.5.9
IS-IS extensions for TE, RFC5305, 3.1" IS-IS extensions for TE, RFC 5305, Section 3.1"
::= { tedEntry 24 } ::= { tedEntry 24 }
tedLocalId OBJECT-TYPE tedLocalId OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the Link local identifier of an unnumbered "This indicates the Link Local Identifier of an unnumbered
link." link."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.1 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.1
IS-IS Extensions in Support of GMPLS, RFC5307, 1.1" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.1"
::= { tedEntry 25 } ::= { tedEntry 25 }
tedRemoteId OBJECT-TYPE tedRemoteId OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the Link remote identifier of an unnumbered "This indicates the Link Remote Identifier of an unnumbered
link." link."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.1 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.1
IS-IS Extensions in Support of GMPLS, RFC5307, 1.1" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.1"
::= { tedEntry 26 } ::= { tedEntry 26 }
tedLinkProtectionType OBJECT-TYPE tedLinkProtectionType OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
extraTraffic(0), extraTraffic(0),
unprotected(1), unprotected(1),
shared (2), shared (2),
dedicatedOneToOne (3), dedicatedOneToOne (3),
dedicatedOnePlusOne(4), dedicatedOnePlusOne(4),
enhanced(5) enhanced(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the protection type of the TE link." "This object indicates the protection type of the TE link."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.2 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.2
IS-IS Extensions in Support of GMPLS, RFC5307, 1.2" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.2"
::= { tedEntry 27 } ::= { tedEntry 27 }
-- TED Local Interface IP Address Table -- TED Local Interface IP Address Table
tedLocalIfAddrTable OBJECT-TYPE tedLocalIfAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF TedLocalIfAddrEntry SYNTAX SEQUENCE OF TedLocalIfAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the IP address information of a local TE "This table contains the IP address information of a local TE
skipping to change at page 17, line 29 skipping to change at page 21, line 19
tedLocalIfAddrType InetAddressType, tedLocalIfAddrType InetAddressType,
tedLocalIfAddr InetAddress tedLocalIfAddr InetAddress
} }
tedLocalIfAddrType OBJECT-TYPE tedLocalIfAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the address type of the local TE link. "This object indicates the address type of the local TE link.
Only values unknown(0), ipv4(1) or ipv6(2) have to be Only values unknown(0), ipv4(1), or ipv6(2) have to be
supported." supported."
::= { tedLocalIfAddrEntry 1 } ::= { tedLocalIfAddrEntry 1 }
tedLocalIfAddr OBJECT-TYPE tedLocalIfAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE (1..20)) SYNTAX InetAddress (SIZE (1..20))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the address of the local TE link." "This object indicates the address of the local TE link."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC3630, "Traffic Engineering (TE) Extensions to OSPF Version 2,
2.5.3, RFC 3630, Section 2.5.3,
Traffic Engineering Extensions to OSPF Version3, RFC5329, 4.3 Traffic Engineering Extensions to OSPF Version 3, RFC 5329,
IS-IS extensions for TE, RFC5305, 3.4" Section 4.3
IS-IS extensions for TE, RFC 5305, Section 3.4"
::= { tedLocalIfAddrEntry 2 } ::= { tedLocalIfAddrEntry 2 }
-- TED Remote Interface IP Address Table -- TED Remote Interface IP Address Table
tedRemoteIfAddrTable OBJECT-TYPE tedRemoteIfAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF TedRemoteIfAddrEntry SYNTAX SEQUENCE OF TedRemoteIfAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the IP address information of a remote TE "This table contains the IP address information of a remote TE
skipping to change at page 18, line 33 skipping to change at page 22, line 30
"This object indicates the address type of the remote TE link." "This object indicates the address type of the remote TE link."
::= { tedRemoteIfAddrEntry 1 } ::= { tedRemoteIfAddrEntry 1 }
tedRemoteIfAddr OBJECT-TYPE tedRemoteIfAddr OBJECT-TYPE
SYNTAX InetAddress(SIZE (1..20)) SYNTAX InetAddress(SIZE (1..20))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the address of the remote TE link." "This object indicates the address of the remote TE link."
REFERENCE REFERENCE
"Traffic Engineering (TE) Extensions to OSPF Version 2, RFC "Traffic Engineering (TE) Extensions to OSPF Version 2,
3630, 2.5.4, RFC 3630, Section 2.5.4,
Traffic Engineering Extensions to OSPF Version3, RFC5329, 4.4 Traffic Engineering Extensions to OSPF Version3, RFC 5329,
IS-IS extensions for TE, RFC5305, 3.3" Section 4.4
IS-IS extensions for TE, RFC 5305, Section 3.3"
::= { tedRemoteIfAddrEntry 2 } ::= { tedRemoteIfAddrEntry 2 }
-- TED Switching Capability Table -- TED Switching Capability Table
tedSwCapTable OBJECT-TYPE tedSwCapTable OBJECT-TYPE
SYNTAX SEQUENCE OF TedSwCapEntry SYNTAX SEQUENCE OF TedSwCapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the GMPLS TED switching capability "This table contains the GMPLS TED switching capability
information." information."
::= { tedObjects 4 } ::= { tedObjects 4 }
tedSwCapEntry OBJECT-TYPE tedSwCapEntry OBJECT-TYPE
SYNTAX TedSwCapEntry SYNTAX TedSwCapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry relates each TE link with its GMPLS TE switching "This entry relates each TE link with its GMPLS TE switching
capability information. If the MIB module deals with only OSPF- capability information. If the MIB module deals with only OSPF-
TE information, the value of each object related with GMPLS TE TE information, the value of each object related with GMPLS TE
extensions should be null." extensions should be null."
INDEX { tedLinkIndex, tedSwCapIndex } INDEX { tedLinkIndex, tedSwCapIndex }
::= { tedSwCapTable 1 } ::= { tedSwCapTable 1 }
TedSwCapEntry ::= SEQUENCE { TedSwCapEntry ::= SEQUENCE {
tedSwCapIndex Unsigned32, tedSwCapIndex Unsigned32,
tedSwCapType IANAGmplsSwitchingTypeTC, tedSwCapType IANAGmplsSwitchingTypeTC,
tedSwCapEncoding IANAGmplsLSPEncodingTypeTC, tedSwCapEncoding IANAGmplsLSPEncodingTypeTC,
tedSwCapMaxLspBandwidthPri0 Float32TC, tedSwCapMaxLspBandwidthPri0 Float32TC,
skipping to change at page 19, line 33 skipping to change at page 23, line 36
tedSwCapIndication INTEGER tedSwCapIndication INTEGER
} }
tedSwCapIndex OBJECT-TYPE tedSwCapIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This index is utilized to identify multiple switching "This index is utilized to identify multiple switching
functions on a local or remote TE link according to definitions functions on a local or remote TE link according to definitions
of textual conventions of GMPLS, RFC4801." of textual conventions of GMPLS, RFC 4801."
::= { tedSwCapEntry 1 } ::= { tedSwCapEntry 1 }
tedSwCapType OBJECT-TYPE tedSwCapType OBJECT-TYPE
SYNTAX IANAGmplsSwitchingTypeTC SYNTAX IANAGmplsSwitchingTypeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the GMPLS switching capability assigned "This object indicates the GMPLS switching capability assigned
to the TE link according to definitions of textual conventions to the TE link according to definitions of textual conventions
of GMPLS, RFC4801." of GMPLS, RFC 4801."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 2 } ::= { tedSwCapEntry 2 }
tedSwCapEncoding OBJECT-TYPE tedSwCapEncoding OBJECT-TYPE
SYNTAX IANAGmplsLSPEncodingTypeTC SYNTAX IANAGmplsLSPEncodingTypeTC
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the GMPLS encoding type assigned to the "This object indicates the GMPLS encoding type assigned to the
TE link." TE link."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 3 } ::= { tedSwCapEntry 3 }
tedSwCapMaxLspBandwidthPri0 OBJECT-TYPE tedSwCapMaxLspBandwidthPri0 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 0 for GMPLS LSP creation." the priority 0 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 4 } ::= { tedSwCapEntry 4 }
tedSwCapMaxLspBandwidthPri1 OBJECT-TYPE tedSwCapMaxLspBandwidthPri1 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 1 for GMPLS LSP creation." the priority 1 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 5 } ::= { tedSwCapEntry 5 }
tedSwCapMaxLspBandwidthPri2 OBJECT-TYPE tedSwCapMaxLspBandwidthPri2 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 2 for GMPLS LSP creation." the priority 2 for GMPLS LSP creation."
skipping to change at page 20, line 41 skipping to change at page 25, line 4
::= { tedSwCapEntry 5 } ::= { tedSwCapEntry 5 }
tedSwCapMaxLspBandwidthPri2 OBJECT-TYPE tedSwCapMaxLspBandwidthPri2 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 2 for GMPLS LSP creation." the priority 2 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 6 } ::= { tedSwCapEntry 6 }
tedSwCapMaxLspBandwidthPri3 OBJECT-TYPE tedSwCapMaxLspBandwidthPri3 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 3 for GMPLS LSP creation." the priority 3 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 7 } ::= { tedSwCapEntry 7 }
tedSwCapMaxLspBandwidthPri4 OBJECT-TYPE tedSwCapMaxLspBandwidthPri4 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 4 for GMPLS LSP creation." the priority 4 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 8 } ::= { tedSwCapEntry 8 }
tedSwCapMaxLspBandwidthPri5 OBJECT-TYPE tedSwCapMaxLspBandwidthPri5 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 5 for GMPLS LSP creation." the priority 5 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 9 } ::= { tedSwCapEntry 9 }
tedSwCapMaxLspBandwidthPri6 OBJECT-TYPE tedSwCapMaxLspBandwidthPri6 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 6 for GMPLS LSP creation." the priority 6 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 10 } ::= { tedSwCapEntry 10 }
tedSwCapMaxLspBandwidthPri7 OBJECT-TYPE tedSwCapMaxLspBandwidthPri7 OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link at "This object indicates the maximum bandwidth of the TE link at
the priority 7 for GMPLS LSP creation." the priority 7 for GMPLS LSP creation."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 11 } ::= { tedSwCapEntry 11 }
tedSwCapMinLspBandwidth OBJECT-TYPE tedSwCapMinLspBandwidth OBJECT-TYPE
SYNTAX Float32TC SYNTAX Float32TC
UNITS "Byte per second" UNITS "Byte per second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the minimum bandwidth of the TE link for "This object indicates the minimum bandwidth of the TE link for
GMPLS LSP creation if the switching capability field is TDM, GMPLS LSP creation if the switching capability field is TDM,
PSC-1, PSC-2, PSC-3, or PSC-4." PSC-1, PSC-2, PSC-3, or PSC-4."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 12 } ::= { tedSwCapEntry 12 }
tedSwCapIfMtu OBJECT-TYPE tedSwCapIfMtu OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the MTU of the local or remote TE link." "This object indicates the MTU of the local or remote TE link."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 13 } ::= { tedSwCapEntry 13 }
tedSwCapIndication OBJECT-TYPE tedSwCapIndication OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
standard (0), standard (0),
arbitrary (1) arbitrary (1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the interface supports Standard "This object indicates whether the interface supports Standard
or Arbitrary SONET SDH." or Arbitrary SONET/SDH."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.4 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.4
IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.3"
::= { tedSwCapEntry 14 } ::= { tedSwCapEntry 14 }
-- TED SRLG Table -- TED SRLG Table
tedSrlgTable OBJECT-TYPE tedSrlgTable OBJECT-TYPE
SYNTAX SEQUENCE OF TedSrlgEntry SYNTAX SEQUENCE OF TedSrlgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the SRLG information of the TE link." "This table contains the SRLG information of the TE link."
skipping to change at page 23, line 19 skipping to change at page 27, line 49
tedSrlgIndex Unsigned32, tedSrlgIndex Unsigned32,
tedSrlg Integer32 tedSrlg Integer32
} }
tedSrlgIndex OBJECT-TYPE tedSrlgIndex OBJECT-TYPE
SYNTAX Unsigned32(1..255) SYNTAX Unsigned32(1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This index is utilized to identify multiple SRLG values on a "This index is utilized to identify multiple SRLG values on a
local or remote TE link. This object represents an arbitrary local or remote TE link. This object represents an arbitrary
value which is locally defined in a router." value, which is locally defined in a router."
REFERENCE REFERENCE
"OSPF Extensions in support of GMPLS, RFC4203, 1.3 "OSPF Extensions in support of GMPLS, RFC 4203, Section 1.3
IS-IS Extensions in Support of GMPLS, RFC5307, 1.4" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.4"
::= { tedSrlgEntry 1 } ::= { tedSrlgEntry 1 }
tedSrlg OBJECT-TYPE tedSrlg OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicate the SRLG value assigned to a local or "This object indicates the SRLG value assigned to a local or
remote TE link" remote TE link."
REFERENCE REFERENCE
"OSPF Extensions in Support of GMPLS, RFC4203, 1.3 "OSPF Extensions in Support of GMPLS, RFC 4203, Section 1.3
IS-IS Extensions in Support of GMPLS, RFC5307, 1.4" IS-IS Extensions in Support of GMPLS, RFC 5307, Section 1.4"
::= { tedSrlgEntry 2 } ::= { tedSrlgEntry 2 }
-- Notification Configuration -- Notification Configuration
tedStatusChangeNotificationMaxRate OBJECT-TYPE tedStatusChangeNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A lot of notifications relating to the status change are "A lot of notifications relating to the status change are
expected to generate in a node, especially when a network expected to generate in a node, especially when a network
failure occurs and might cause a performance degradation of the failure occurs and might cause a performance degradation of the
node itself. To avoid such a defect, this object provides the node itself. To avoid such a defect, this object provides the
maximum number of notifications generated per minute. If maximum number of notifications generated per minute. If
events occur more rapidly, the implementation may simply fail events occur more rapidly, the implementation may simply fail
to emit these notifications during that period, or may queue to emit these notifications during that period, or may queue
them until an appropriate time. A value of 0 means no them until an appropriate time. A value of 0 means no
throttling is applied and events may be notified at the rate at throttling is applied and events may be notified at the rate at
which they occur." which they occur."
DEFVAL {1} DEFVAL {1}
::= { tedObjects 6 } ::= { tedObjects 6 }
tedCreatedDeletedNotificationMaxRate OBJECT-TYPE tedCreatedDeletedNotificationMaxRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A lot of notifications relating to new registration in ted "A lot of notifications relating to new registration in the TED
table by receiving new TE link information or deletion of table by receiving new TE link information or deletion of
existing entries in ted table are expected to generate in a existing entries in the TED table are expected to generate in a
node. This object provides the maximum number of notifications node. This object provides the maximum number of notifications
generated per minute." generated per minute."
DEFVAL {1} DEFVAL {1}
::= { tedObjects 7 } ::= { tedObjects 7 }
-- Notifications -- Notifications
tedStatusChange NOTIFICATION-TYPE tedStatusChange NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tedLinkState tedLinkState
} }
STATUS current STATUS current
skipping to change at page 24, line 25 skipping to change at page 29, line 16
::= { tedObjects 7 } ::= { tedObjects 7 }
-- Notifications -- Notifications
tedStatusChange NOTIFICATION-TYPE tedStatusChange NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tedLinkState tedLinkState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that there has been change in TE "This notification signifies that there has been change in the
information of tedTable, tedLocalIfAddrTable, TE information of tedTable, tedLocalIfAddrTable,
tedRemoteIfAddrTable, tedSwCapTable and/or tedSrlgTable. For tedRemoteIfAddrTable, tedSwCapTable, and/or tedSrlgTable. For
example, this should be generated when tedUnreservedBandwidth example, this should be generated when tedUnreservedBandwidth is
is changed to create or delete LSP using registered TE link. " changed to create or delete LSP using the registered TE link."
::= { tedNotifications 1 } ::= { tedNotifications 1 }
tedEntryCreated NOTIFICATION-TYPE tedEntryCreated NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tedLinkState tedLinkState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that there has been new "This notification signifies that there has been new
registration in ted table by receiving new TE link information. registration in the TED table by receiving new TE link
For example, this should be generated when new index information. For example, this should be generated when a new
(tedLinkIndex) is registered in TED table." index (tedLinkIndex) is registered in the TED table."
::= { tedNotifications 2 } ::= { tedNotifications 2 }
tedEntryDeleted NOTIFICATION-TYPE tedEntryDeleted NOTIFICATION-TYPE
OBJECTS { OBJECTS {
tedLinkState tedLinkState
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification signifies that there has been deletion of an "This notification signifies that there has been deletion of an
entry in the ted table. For example, this should be generated entry in the TED table. For example, this should be generated
when one of existing entries is deleted in TED table." when one of the existing entries is deleted in the TED table."
::= { tedNotifications 3 } ::= { tedNotifications 3 }
-- Conformance Statement -- Conformance Statement
tedCompliances tedCompliances
OBJECT IDENTIFIER ::= { tedConformance 1 } OBJECT IDENTIFIER ::= { tedConformance 1 }
tedGroups tedGroups
OBJECT IDENTIFIER ::= { tedConformance 2 } OBJECT IDENTIFIER ::= { tedConformance 2 }
-- Module Compliance -- Module Compliance
tedModuleFullCompliance MODULE-COMPLIANCE tedModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents provides full support for the "Compliance statement for agents provides full support for the
TED MIB." TED MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { tedMainGroup, MANDATORY-GROUPS { tedMainGroup,
tedObjectsGroup, tedObjectsGroup,
tedNotificationGroup tedNotificationGroup
} }
GROUP tedUnnumberedLinkGroup GROUP tedUnnumberedLinkGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports the "This group is mandatory for TE links that support the
unnumbered links." unnumbered links."
GROUP tedNumberedLinkGroup GROUP tedNumberedLinkGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports the "This group is mandatory for TE links that support the
numbered links." numbered links."
GROUP tedSwCapGroup GROUP tedSwCapGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports GMPLS "This group is mandatory for TE links that support GMPLS
switching capability." switching capability."
GROUP tedSwCapMinLspBandwidthGroup GROUP tedSwCapMinLspBandwidthGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links if the switching "This group is mandatory for TE links if the switching
capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4." capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4."
GROUP tedSwCapIfMtuGroup GROUP tedSwCapIfMtuGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports the MTU of "This group is mandatory for TE links that support the MTU of
the local or remote TE link." the local or remote TE link."
GROUP tedSwCapIndicationGroup GROUP tedSwCapIndicationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports Standard or "This group is mandatory for TE links that support Standard or
Arbitrary SONET/SDH." Arbitrary SONET/SDH."
GROUP tedSrlgGroup GROUP tedSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports SRLG "This group is mandatory for TE links that support SRLG
information." information."
::= { tedCompliances 1 } ::= { tedCompliances 1 }
-- --
-- ReadOnly Compliance -- ReadOnly Compliance
-- --
tedModuleReadOnlyCompliance MODULE-COMPLIANCE tedModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations only provide read- "Compliance requirement for implementations only provides read-
only support for TED. Such devices can then be monitored but only support for TED. Such devices can then be monitored but
cannot be configured using this MIB module." cannot be configured using this MIB module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { tedMainGroup MANDATORY-GROUPS { tedMainGroup
} }
GROUP tedUnnumberedLinkGroup GROUP tedUnnumberedLinkGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports the "This group is mandatory for TE links that support the
unnumbered links." unnumbered links."
GROUP tedNumberedLinkGroup GROUP tedNumberedLinkGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports the "This group is mandatory for TE links that support the
numbered links." numbered links."
GROUP tedSwCapGroup GROUP tedSwCapGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports some GMPLS "This group is mandatory for TE links that support some GMPLS
switching capabilities." switching capabilities."
GROUP tedSwCapMinLspBandwidthGroup GROUP tedSwCapMinLspBandwidthGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links if the switching "This group is mandatory for TE links if the switching
capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4." capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4."
GROUP tedSwCapIfMtuGroup GROUP tedSwCapIfMtuGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports the MTU of "This group is mandatory for TE links that support the MTU of
the local or remote TE link." the local or remote TE link."
GROUP tedSwCapIndicationGroup GROUP tedSwCapIndicationGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports Standard or "This group is mandatory for TE links that support Standard or
Arbitrary SONET/SDH." Arbitrary SONET/SDH."
GROUP tedSrlgGroup GROUP tedSrlgGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for TE links that supports SRLG "This group is mandatory for TE links that support SRLG
information." information."
::= { tedCompliances 2 } ::= { tedCompliances 2 }
-- Units of conformance -- Units of conformance
tedMainGroup OBJECT-GROUP tedMainGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedLinkState , tedLinkState,
tedAreaId , tedAreaId,
tedLinkType , tedLinkType,
tedTeRouterIdAddrType , tedTeRouterIdAddrType,
tedTeRouterIdAddr , tedTeRouterIdAddr,
tedLinkIdAddrType , tedLinkIdAddrType,
tedLinkIdAddr , tedLinkIdAddr,
tedMetric , tedMetric,
tedMaxBandwidth , tedMaxBandwidth,
tedMaxReservableBandwidth , tedMaxReservableBandwidth,
tedUnreservedBandwidthPri0 , tedUnreservedBandwidthPri0,
tedUnreservedBandwidthPri1 , tedUnreservedBandwidthPri1,
tedUnreservedBandwidthPri2 , tedUnreservedBandwidthPri2,
tedUnreservedBandwidthPri3 , tedUnreservedBandwidthPri3,
tedUnreservedBandwidthPri4 , tedUnreservedBandwidthPri4,
tedUnreservedBandwidthPri5 , tedUnreservedBandwidthPri5,
tedUnreservedBandwidthPri6 , tedUnreservedBandwidthPri6,
tedUnreservedBandwidthPri7 , tedUnreservedBandwidthPri7,
tedAdministrativeGroup , tedAdministrativeGroup,
tedLinkProtectionType , tedLinkProtectionType,
tedLinkInformationData tedLinkInformationData
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects for TED management" "Collection of objects for TED management"
::= { tedGroups 1 } ::= { tedGroups 1 }
tedObjectsGroup OBJECT-GROUP tedObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedStatusChangeNotificationMaxRate, tedStatusChangeNotificationMaxRate,
tedCreatedDeletedNotificationMaxRate tedCreatedDeletedNotificationMaxRate
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement notification." "The objects needed to implement notification."
::= { tedGroups 2 } ::= { tedGroups 2 }
tedNotificationGroup NOTIFICATION-GROUP tedNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
tedStatusChange, tedStatusChange,
tedEntryCreated, tedEntryCreated,
tedEntryDeleted tedEntryDeleted
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 28, line 4 skipping to change at page 33, line 25
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for those implementations that can "This group is mandatory for those implementations that can
implement the notifications contained in this group." implement the notifications contained in this group."
::= { tedGroups 3 } ::= { tedGroups 3 }
tedUnnumberedLinkGroup OBJECT-GROUP tedUnnumberedLinkGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedLocalId, tedLocalId,
tedRemoteId tedRemoteId
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement the unnumbered links." "The objects needed to implement the unnumbered links."
::= { tedGroups 4 } ::= { tedGroups 4 }
tedNumberedLinkGroup OBJECT-GROUP tedNumberedLinkGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedLocalIfAddrType, tedLocalIfAddrType,
tedRemoteIfAddrType tedRemoteIfAddrType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement the numbered links." "The objects needed to implement the numbered links."
::= { tedGroups 5 } ::= { tedGroups 5 }
tedSwCapGroup OBJECT-GROUP tedSwCapGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedSwCapType, tedSwCapType,
tedSwCapEncoding, tedSwCapEncoding,
tedSwCapMaxLspBandwidthPri0, tedSwCapMaxLspBandwidthPri0,
tedSwCapMaxLspBandwidthPri1, tedSwCapMaxLspBandwidthPri1,
tedSwCapMaxLspBandwidthPri2, tedSwCapMaxLspBandwidthPri2,
tedSwCapMaxLspBandwidthPri3, tedSwCapMaxLspBandwidthPri3,
tedSwCapMaxLspBandwidthPri4, tedSwCapMaxLspBandwidthPri4,
tedSwCapMaxLspBandwidthPri5, tedSwCapMaxLspBandwidthPri5,
tedSwCapMaxLspBandwidthPri6, tedSwCapMaxLspBandwidthPri6,
tedSwCapMaxLspBandwidthPri7 tedSwCapMaxLspBandwidthPri7
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement TE links with its GMPLS TE "The objects needed to implement the TE links with GMPLS TE
switching capability information." switching capability information."
::= { tedGroups 6 } ::= { tedGroups 6 }
tedSwCapMinLspBandwidthGroup OBJECT-GROUP tedSwCapMinLspBandwidthGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedSwCapMinLspBandwidth tedSwCapMinLspBandwidth
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement the minimum bandwidth of the "The objects needed to implement the minimum bandwidth of the
TE link for GMPLS LSP creation." TE link for GMPLS LSP creation."
::= { tedGroups 7 } ::= { tedGroups 7 }
tedSwCapIfMtuGroup OBJECT-GROUP tedSwCapIfMtuGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedSwCapIfMtu tedSwCapIfMtu
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement the MTU information of the "The objects needed to implement the MTU information of the
local or remote TE link." local or remote TE link."
::= { tedGroups 8 } ::= { tedGroups 8 }
tedSwCapIndicationGroup OBJECT-GROUP tedSwCapIndicationGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedSwCapIndication tedSwCapIndication
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement the indication whether the "The objects needed to implement the indication of whether the
interface supports Standard or Arbitrary SONET/SDH." interface supports Standard or Arbitrary SONET/SDH."
::= { tedGroups 9 } ::= { tedGroups 9 }
tedSrlgGroup OBJECT-GROUP tedSrlgGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tedSrlg tedSrlg
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This objects needed to implement multiple SRLG values with "The objects needed to implement multiple SRLG values with
GMPLS TE information." GMPLS TE information."
::= { tedGroups 10 } ::= { tedGroups 10 }
END END
8. Security Consideration 8. Security Considerations
There are several objects defined in this MIB module that has a MAX- There are several objects defined in this MIB module that have a MAX-
ACCESS clause of read-write. Such objects may be considered sensitive ACCESS clause of read-write. Such objects may be considered
or vulnerable in some network environments. The support for SET sensitive or vulnerable in some network environments. The support
operations in a non-secure environment without proper protection can for SET operations in a non-secure environment without proper
have a negative effect on network operations. protection can have a negative effect on network operations.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: tedTable, tedLocalIfAddrTable, sensitivity/vulnerability: tedTable, tedLocalIfAddrTable,
tedRemoteIfAddrTable, tedSwCapTable and tedSrlgTable contain topology tedRemoteIfAddrTable, tedSwCapTable, and tedSrlgTable contain
information for the MPLS/GMPLS network. If an administrator does not topology information for the MPLS/GMPLS network. If an administrator
want to reveal this information, then these tables should be does not want to reveal this information, then these tables should be
considered sensitive/vulnerable. considered sensitive/vulnerable.
There are only two write-access objects in this MIB module: There are only two write-access objects in this MIB module:
tedStatusChangeNotificationMaxRate and tedStatusChangeNotificationMaxRate and
tedCreatedDeletedNotificationMaxRate. Malicious modification of tedCreatedDeletedNotificationMaxRate. Malicious modification of
these objects could cause the management agent, the network, or the these objects could cause the management agent, the network, or the
router to become overloaded with Notifications in cases of high churn router to become overloaded with notifications in cases of high churn
within the network. within the network.
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security.
if the network itself is secure (for example by using IPsec), even Even if the network itself is secure (for example by using IPsec),
then, there is no control as to who on the secure network is allowed even then, there is no control as to who on the secure network is
to access and GET/SET (read/change/create/delete) the objects in this allowed to access and GET/SET (read/change/create/delete) the objects
MIB module. in this MIB module.
Implementations MUST provide the security features described by the
SNMPv3 framework (see [RFC3410]), including full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Implementations MUST provide the security features described by the
SNMPv3 framework (see [RFC3410]), including full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principles (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. IANA Considerations 9. IANA Considerations
The following "IANA Considerations" subsection requests IANA for a IANA has assigned 273 to the TED-MIB module specified in this
new assignment under the transmission subtree. New assignments can document in the "Internet-standard MIB - Transmission Group"
only be made via a Standards Action as specified in [RFC5226]. registry. New assignments can only be made via Specification
Required as specified in [RFC5226].
9.1 IANA Considerations for TED-MIB In addition, the IANA has marked value 273 (the corresponding
transmission value allocated according to this document) as
"Reserved" in the "ifType definitions" registry.
The IANA is requested to assign {transmission yyy} to the TED-MIB 10. References
module specified in this document.
10. References 10.1. Normative References
10.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] 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.
[RFC2328] J. Moy, " OSPF version2 ", RFC2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Structure of Management Information Version 2 (SMIv2)", Schoenwaelder, Ed., "Structure of Management Information
STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Textual Conventions for SMIv2", STD 58, RFC 2579, April Schoenwaelder, Ed., "Textual Conventions for SMIv2",
1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Conformance Statements for SMIv2", STD 58, RFC 2580, Schoenwaelder, Ed., "Conformance Statements for SMIv2",
April 1999. STD 58, RFC 2580, April 1999.
[RFC4001] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder, [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
"Textual Conventions for Internet Network Addresses", Schoenwaelder, "Textual Conventions for Internet Network
RFC4001, Feb. 2005. Addresses", RFC 4001, February 2005.
[RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions to
OSPF Version2", RFC3630, Sep. 2003.
[RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in Support [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
of Generalized Multi-Protocol Label Switching", RFC4203, (TE) Extensions to OSPF Version 2", RFC 3630,
Oct. 2005. September 2003.
[RFC4750] Dan Joyal, et al, "OSPF Version 2 Management Information [RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions
Base", RFC4750, Dec. 2006. in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005.
[RFC4801] T. D. Nadeau and A. Farrel, Ed., "Definitions of Textual [RFC4750] Joyal, D., Ed., Galecki, P., Ed., Giacalone, S., Ed.,
Conventions for Generalized Multiprotocol Label Switching Coltun, R., and F. Baker, "OSPF Version 2 Management
(GMPLS) Management", RFC4801, Feb. 2007. Information Base", RFC 4750, December 2006.
[RFC5329] K. Ishiguro, V. Manral, A. Davey, A.Lindem " Traffic [RFC4801] Nadeau, T., Ed., and A. Farrel, Ed., "Definitions of
Engineering Extensions to OSPF Version 3 ", RFC5329, Sep. Textual Conventions for Generalized Multiprotocol Label
2008. Switching (GMPLS) Management", RFC 4801, February 2007.
[RFC5340] R. Coltun, D. Ferguson, J. Moy, A.Lindem " OSPF for IPv6", [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed.,
RFC5340, July 2008. "Traffic Engineering Extensions to OSPF Version 3",
RFC 5329, September 2008.
[RFC5643] Dan Joyal, et al, "Management Information Base for OSPFv3 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
", RFC5643, August 2009. for IPv6", RFC 5340, July 2008.
[RFC6340] R. Presuhn, "Textual Conventions for the Representation of [RFC5643] Joyal, D., Ed., and V. Manral, Ed., "Management
Floating-point Number ", RFC6340, August 2011. Information Base for OSPFv3", RFC 5643, August 2009.
10.2 Informative References [RFC6340] Presuhn, R., "Textual Conventions for the Representation
of Floating-Point Numbers", RFC 6340, August 2011.
[RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 10.2. Informative References
and Applicability Statement for Internet Standard
Management Framework", RFC 3410, Dec. 2002.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
(USM) for version 3 of the Simple Network Management "Introduction and Applicability Statements for
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. D. Nadeau, [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
"Multiprotocol Label Switching (MPLS) Traffic Engineering (USM) for version 3 of the Simple Network Management
(TE) Management Information Base (MIB)", RFC 3812, June Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. D. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Traffic Engineering
(LSR) Router Management Information Base (MIB)", RFC 3813, (TE) Management Information Base (MIB)", RFC 3812,
June 2004. June 2004.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
Advanced Encryption Standard (AES) Cipher Algorithm in the "Multiprotocol Label Switching (MPLS) Label Switching
SNMP User-based Security Model", RFC 3826, June 2004. Router (LSR) Management Information Base (MIB)", RFC 3813,
June 2004.
[RFC3945] E. Mannie, "Generalized Multi-Procol Label Switching [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
(MPLS) Architecture", RFC3945, Oct. 2004. Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, June 2004.
[RFC4202] K. Kompella, and Y. Rekhter, "Routing Extensions in [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label
Support of Generalized Multi-Protocol Label Switching", Switching (GMPLS) Architecture", RFC 3945, October 2004.
RFC4202, Oct. 2005.
[RFC4220] M. Dubuc, T. D. Nadeau and J. Lang, "Traffic Engineering [RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing
Link Management Information Base", RFC4220, Dec. 2005. Extensions in Support of Generalized Multi-Protocol Label
Switching (GMPLS)", RFC 4202, October 2005.
[RFC4377] T. D. Nadeau, et al, "Operations and Management (OAM) [RFC4220] Dubuc, M., Nadeau, T., and J. Lang, "Traffic Engineering
Requirements for Multi-Protocol Label Switched (MPLS) Link Management Information Base", RFC 4220,
Networks", RFC 4377, February 2006. November 2005.
[RFC4444] T. Parker, et al, "Management Information Base for [RFC4377] Nadeau, T., Morrow, M., Swallow, G., Allan, D., and S.
Intermediate System to Intermediate System (IS-IS)", RFC Matsushima, "Operations and Management (OAM) Requirements
4444, April 2006. for Multi-Protocol Label Switched (MPLS) Networks",
RFC 4377, February 2006.
[RFC4802] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol [RFC4444] Parker, J., Ed., "Management Information Base for
Label Switching (GMPLS) Traffic Engineering Management Intermediate System to Intermediate System (IS-IS)",
Information Base", RFC4802, Feb. 2007. RFC 4444, April 2006.
[RFC4803] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol [RFC4802] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized
Label Switching (GMPLS) Label Switching Router (LSR) Multiprotocol Label Switching (GMPLS) Traffic Engineering
Management Information Base", RFC4803, Feb., 2007. Management Information Base", RFC 4802, February 2007.
[RFC5305] H. Smit and T. Li, "IS-IS extensions for Traffic [RFC4803] Nadeau, T., Ed., and A. Farrel, Ed., "Generalized
Engineering", RFC 5305, Oct. 2008. Multiprotocol Label Switching (GMPLS) Label Switching
Router (LSR) Management Information Base", RFC 4803,
February 2007.
[RFC5307] K. Kompella, and Y. Rekhter, "IS-IS Extensions in Support [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
of Generalized Multi-Protocol Label Switching (GMPLS)", Engineering", RFC 5305, October 2008.
RFC5307, Oct. 2008.
[RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an [RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions
IANA Considerations Section in RFCs" BCP 26, RFC 5226, May in Support of Generalized Multi-Protocol Label Switching
2008. (GMPLS)", RFC 5307, October 2008.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
for the Simple Network Management Protocol (SNMP)", RFC IANA Considerations Section in RFCs", BCP 26, RFC 5226,
5591, June 2009. May 2008.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
Shell Transport Model for the Simple Network Management for the Simple Network Management Protocol (SNMP)",
Protocol (SNMP)", RFC 5592, June 2009. RFC 5591, June 2009.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Model for the Simple Network Management Protocol (SNMP)", Shell Transport Model for the Simple Network Management
RFC 6353, July 2011. Protocol (SNMP)", RFC 5592, June 2009.
[ISO10589] ISO 10589, "Intermediate system to Intermediate system [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
routeing information exchange protocol for use in Model for the Simple Network Management Protocol (SNMP)",
conjunction with the Protocol for providing the RFC 6353, July 2011.
Connectionless-mode Network Service (ISO 8473)", ISO/IEC
10589:2002. [ISO10589] ISO 10589, "Intermediate System to Intermediate System
intra-domain routeing information exchange protocol for
use in conjunction with the protocol for providing the
connectionless-mode network service (ISO 8473)",
ISO/IEC 10589:2002.
11. Acknowledgments
11. Acknowledgment
The authors wish to acknowledge and thank the following individuals The authors wish to acknowledge and thank the following individuals
for their valuable comments to this document: Ken Nagami, Shuichi for their valuable comments to this document: Ken Nagami, Shuichi
Okamoto, Adrian Farrel, Diego Caviglia and Acee Lindem. Okamoto, Adrian Farrel, Diego Caviglia, and Acee Lindem.
12. Authors' Addresses Authors' Addresses
Masanori Miyazawa
KDDI R&D Laboratories, Inc.
2-1-15 Ohara Fujimino
Saitama, 356-8502
Japan
EMail: ma-miyazawa@kddilabs.jp
Tomohiro Otani Tomohiro Otani
KDDI Corporation KDDI Corporation
KDDI Bldg, KDDI Bldg,
2-3-2, Nishishinjuku, Shinjuku-ku, Tokyo, 163-8003, Japan 2-3-2, Nishishinjuku, Shinjuku-ku
Email: tm-otani@kddi.com Tokyo, 163-8003
Japan
Masanori Miyazawa
KDDI R&D Laboratories, Inc.
2-1-15 Ohara Fujimino, Saitama, 356-8502, Japan.
Email: ma-miyazawa@kddilabs.jp
Thomas D. Nadeau EMail: Tm-otani@kddi.com
Email: tnadeau@lucidvision.com
Kenji Kumaki Kenji Kumaki
KDDI Corporation KDDI Corporation
Garden Air Tower Garden Air Tower
Iidabashi, Chyoda-ku, Tokyo, 102-8460, Japan Iidabashi, Chyoda-ku
Email: ke-kumaki@kddi.com Tokyo, 102-8460
Japan
EMail: ke-kumaki@kddi.com
Thomas D. Nadeau
Juniper Networks
10 Technology Park Drive
Westford, MA
USA
EMail: tnadeau@juniper.net
 End of changes. 235 change blocks. 
558 lines changed or deleted 573 lines changed or added

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