draft-ietf-ccamp-gmpls-ted-mib-00.txt   draft-ietf-ccamp-gmpls-ted-mib-01.txt 
IETF Internet Draft Masanori Miyazawa IETF Internet Draft Masanori Miyazawa
Proposed status: Standards Track Tomohiro Otani Proposed status: Standards Track Tomohiro Otani
Expires: May 2007 KDDI R&D Labs Expires: September 2007 KDDI R&D Labs
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Kenji Kumaki Kenji Kumaki
KDDI Corporation KDDI Corporation
Nov. 2006
Traffic Engineering Database Management Information Base Traffic Engineering Database Management Information Base
in support of GMPLS in support of GMPLS
draft-ietf-ccamp-gmpls-ted-mib-00.txt draft-ietf-ccamp-gmpls-ted-mib-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at line 47 skipping to change at page 2, line ?
This memo defines the Management Information Base (MIB) objects in This memo defines the Management Information Base (MIB) objects in
order to manage traffic engineering database (TED) information with order to manage traffic engineering database (TED) information with
extension in support of Multi-protocol label switching (MPLS) as well extension in support of Multi-protocol label switching (MPLS) as well
as Generalized MPLS (GMPLS) for use with network management protocols. as Generalized MPLS (GMPLS) for use with network management protocols.
Table of Contents Table of Contents
Status of this Memo................................................1 Status of this Memo................................................1
Abstract...........................................................1 Abstract...........................................................1
1. Introduction....................................................3 1. The Internet-Standard Management Framework......................3
2. Terminology.....................................................3 2. Introduction....................................................3
T. Otani et al. 1 T. Otani et al. 1
2.1 Conventions used in this document..............................3 3. Overview........................................................3
2.2 Terminology....................................................3 3.1 Conventions used in this document..............................3
2.3 Acronyms.......................................................3 3.2 Terminology....................................................3
3. Motivations.....................................................4 3.3 Acronyms.......................................................3
4. Brief description of MIB Objects................................4 4. Motivations.....................................................4
4.1 teTEDTable.....................................................4 5. Brief description of MIB Objects................................4
4.2 teLocalIntIpAddrTable..........................................4 5.1 tedTable.......................................................4
4.3 teRemoteIntIpAddrTable.........................................4 5.2 teLocalIntIpAddrTable..........................................4
4.4 teSwCapTable...................................................4 5.3 teRemoteIntIpAddrTable.........................................4
4.5 teSrlgTable....................................................4 5.4 teSwCapTable...................................................5
5. TED MIB Definitions in support of GMPLS.........................4 5.5 teSrlgTable....................................................5
6. Security consideration.........................................19 6. TED MIB Definitions in support of GMPLS.........................5
7. IANA Considerations............................................19 7. Security consideration.........................................20
7.1 IANA Considerations for TED-STD-MIB...........................19 8. IANA Considerations............................................20
8. References.....................................................19 8.1 IANA Considerations for TED-MIB...............................20
8.1 Normative References..........................................19 9. References.....................................................20
8.2 Informative References........................................19 9.1 Normative References..........................................20
9. Acknowledgment.................................................21 9.2 Informative References........................................20
10. Author's Address..............................................21 10. Acknowledgment................................................22
11. Intellectual Property Statement...............................21 11. Author's Address..............................................22
12. Copyright Statement...........................................22 12. Intellectual Property Statement...............................22
13. Copyright Statement...........................................23
T. Otani et al. 2 1. The Internet-Standard Management Framework
1. Introduction For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
The OSPF MIB is defined as [OSPFMIB] being extended by [OSPFMIB Managed objects are accessed via a virtual information store, termed
UPDATE] and The ISIS MIB as [ISISMIB]. On the other side, MPLS/GMPLS the Management Information Base or MIB. MIB objects are generally
based traffic engineering has so far extended OSPF/ISIS routing accessed through the Simple Network Management Protocol (SNMP).
protocol with TE functionality [GMPLSrouting, RFC3630, GMPLSisis, Objects in the MIB are defined using the mechanisms defined in the
RFC3784]. To manage such MPLS/GMPLS networks effectively, routing Structure of Management Information (SMI). This memo specifies a MIB
information associated with MPLS/GMPLS TE parameters (TED) is module that is compliant to the SMIv2, which is described in STD 58,
preferred for the network management, however, there is no clear RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
definition of MPLS/GMPLS TE information in existing MIBs related with [RFC2580].
OSPF/ISIS.
2. Introduction
The OSPF MIB is defined as [RFC1850] being extended by [RFC4750] and
The ISIS MIB as [RFC4444]. On the other side, MPLS/GMPLS based
traffic engineering has so far extended OSPF/ISIS routing protocol
with TE functionality [RFC4202, RFC3630, RFC4205, RFC3784]. To manage
such MPLS/GMPLS networks effectively, routing information associated
with MPLS/GMPLS TE parameters (TED) is preferred for the network
management, however, there is no clear definition of MPLS/GMPLS TE
information in existing MIBs related with OSPF/ISIS.
This memo defines the Management Information Base (MIB) objects for This memo defines the Management Information Base (MIB) objects for
managing TED in support of MPLS/GMPLS for use with network management managing TED in support of MPLS/GMPLS for use with network management
protocols. protocols.
This MIB module should be used in conjunction with OSPF/ISIS MIB as This MIB module should be used in conjunction with OSPF/ISIS MIB as
well as other MIBs defined in [RFC3812, RFC3813, GMPLSLSRMIB, well as other MIBs defined in [RFC3812, RFC3813, GMPLSLSRMIB,
GMPLSTEMIB] for the management of MPLS/GMPLS based traffic GMPLSTEMIB] for the management of MPLS/GMPLS based traffic
engineering information. engineering information.
2. Terminology 3. Overview
2.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", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
2.2 Terminology 3.2 Terminology
Definitions of key terms for MPLS OAM and GMPLS are found in [MPLS- Definitions of key terms for MPLS OAM and GMPLS are found in [MPLS-
OAM, RFC3945] and the reader is assumed to be familiar with those OAM, RFC3945] and the reader is assumed to be familiar with those
definitions which are not repeated here. definitions which are not repeated here.
2.3 Acronyms 3.3 Acronyms
GMPLS: Generalized Multi-Protocol Label Switching GMPLS: Generalized Multi-Protocol Label Switching
LDP: Label Distribution Protocol LDP: Label Distribution Protocol
LSP: Label Switching Path LSP: Label Switching Path
LSR: Label Switching Router LSR: Label Switching Router
MIB: Management Information Base MIB: Management Information Base
OAM: Operations and Management OAM: Operations and Management
OA&M: Operations, Administration and Maintenance. OA&M: Operations, Administration and Maintenance.
OSPF: Open Shortest Path First OSPF: Open Shortest Path First
RSVP: Resource reSerVation Protocol RSVP: Resource reSerVation Protocol
TE: Traffic Engineering TE: Traffic Engineering
PSC: Packet switch capable PSC: Packet switch capable
LSC: Lambda switch capable LSC: Lambda switch capable
FSC: Fiber switch capable FSC: Fiber switch capable
TDM: Time Division Multiplexing TDM: Time Division Multiplexing
SRLG: Shared risk link group SRLG: Shared risk link group
LSA: Link state advertisement LSA: Link state advertisement
T. Otani et al. 3 4. Motivations
3. Motivations
The existing OSPF, MPLS and GMPLS MIBs do not provide for the The existing OSPF, MPLS and GMPLS MIBs do not provide for the
management of all of the extensions to the OSPF protocol. To manage management of all of the extensions to the OSPF protocol. To manage
GMPLS TE attributes, MIB objects to indicate such GMPLS TED is GMPLS TE attributes, MIB objects to indicate such GMPLS TED is
significant. significant.
4. Brief description of MIB Objects 5. Brief description of MIB Objects
The objects described in this section support the management of TED The objects described in this section support the management of TED
described in [GMPLSrouting], [GMPLSOSPF] and [GMPLSisis] for GMPLS described in [RFC4202], [RFC4203] and [RFC4205] for GMPLS extensions
extensions as well as in [RFC3630] and [RFC3784] for MPLS/GMPLS. as well as in [RFC3630] and [RFC3784] for MPLS/GMPLS.
4.1 teTEDTable 5.1 tedTable
The teTEDTable is basically used to indicate TED information of OSPF- The tedTable is basically used to indicate TED information of OSPF-TE
TE or ISIS-TE. However, this table does not contain the information or ISIS-TE. However, this table does not contain the information of
of Local/Remote interface IP address, Interface Switching Capcability Local/Remote interface IP address, Interface Switching Capcability
Descriptor and Shared Risk Link Group information within the sub-TLVs Descriptor and Shared Risk Link Group information within the sub-TLVs
for the Link-TLV. for the Link-TLV.
4.2 teLocalIntIpAddrTable 5.2 teLocalIntIpAddrTable
The teLocalIntIpAddrTable is identical to the Local interface IP The teLocalIntIpAddrTable 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 within the same Link-TLV.
4.3 teRemoteIntIpAddrTable 5.3 teRemoteIntIpAddrTable
The teRemoteIntIpAddrTable is identical to the Remote interface IP The teRemoteIntIpAddrTable is identical to the Remote interface IP
address information in a sub-TLV of the Link-TLV. This is also address information in a sub-TLV of the Link-TLV. This is also
independently utilized, because one or more local interface IP independently utilized, because one or more local interface IP
address sub TLVs may exist in the same Link-TLV. address sub TLVs may exist in the same Link-TLV.
4.4 teSwCapTable 5.4 teSwCapTable
The teSwCapTable represents Interface Switching Capability Descriptor The teSwCapTable represents Interface Switching Capability Descriptor
information. This is independently defined due to the possibility of information. This is independently defined due to the possibility of
multiple appearances of the sub TLV within the same Link-TLV. multiple appearances of the sub TLV within the same Link-TLV.
4.5 teSrlgTable 5.5 teSrlgTable
The teSrlgTable contains the Sub-TLV information of Shared Risk Link The teSrlgTable contains the Sub-TLV information of Shared Risk Link
Group (SRLG) information. This is separately defined, because more Group (SRLG) information. This is separately defined, because more
than one sub TLVs may appear in the same Link-TLV. than one sub TLVs may appear in the same Link-TLV.
5. TED MIB Definitions in support of GMPLS 6. TED MIB Definitions in support of GMPLS
T. Otani et al. 4 TED-MIB DEFINITIONS ::= BEGIN
TED-DRAFT01-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission, MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission,
IpAddress IpAddress
FROM SNMPv2-SMI --[RFC2578] FROM SNMPv2-SMI --[RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF --[RFC2580] FROM SNMPv2-CONF --[RFC2580]
RowPointer RowPointer
FROM SNMPv2-TC --[RFC2579] FROM SNMPv2-TC --[RFC2579]
ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId ;
FROM OSPF-MIB; --[OSPFMIB UPDATE]
IsisISLevel, IsisLinkStatePDUID, IsisSystemID
FROM ISIS-MIB; --[ISISMIB]
teMIB MODULE-IDENTITY tedMIB MODULE-IDENTITY
LAST-UPDATED "200510240000Z" -- 04 July 2005 00:00:00 GMT LAST-UPDATED "200510240000Z" -- 04 July 2005 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 otani@kddilabs.jp
Masanori Miyazawa Masanori Miyazawa
ma-miyazawa@kddilabs.jp ma-miyazawa@kddilabs.jp
Thomas D. Nadeau Thomas D. Nadeau
tnadeau@cisco.com tnadeau@cisco.com
Kenji Kumaki Kenji Kumaki
ke-kumaki@kddi.com ke-kumaki@kddi.com
Comments and discussion to ccamp@ietf.org" Comments and discussion to ccamp@ietf.org"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
TED in support of MPLS/GMPLS Traffic TED in support of MPLS/GMPLS Traffic
Engienering (TE) Database." Engienering (TE) Database.
"Copyright (C) The IETF Trust <2006>. This version of
this MIB module is part of RFC XXXX; see the RFC itself for
full legal notices."
Copyright (C) The Internet Society (2007). This
version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices."
-- Revision history. -- Revision history.
REVISION REVISION
"200506041200Z" -- 04 July 2005 12:00:00 GMT "200506041200Z" -- 04 July 2005 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." -- RFC-editor pls fill "Initial version. Published as RFC xxxx."
--in xxx -- RFC-editor pls fill in xxx
::= { transmission 9988 } -- assigned by IANA, see section 7.1 for ::= { transmission xxx }
-- details -- assigned by IANA, see section 7.1 for details
-- Textual Conventions. -- Textual Conventions.
-- Top level components of this MIB. -- Top level components of this MIB.
T. Otani et al. 5 tedNotifications OBJECT IDENTIFIER ::= { tedMIB 0 }
teNotifications OBJECT IDENTIFIER ::= { teMIB 0 } tedObjects OBJECT IDENTIFIER ::= { tedMIB 1 }
teObjects OBJECT IDENTIFIER ::= { teMIB 1 } tedScalars OBJECT IDENTIFIER ::= { tedObjects 1 }
teScalars OBJECT IDENTIFIER ::= { teObjects 1 } tedTables OBJECT IDENTIFIER ::= { tedObjects 2 }
teTables OBJECT IDENTIFIER ::= { teObjects 2 } tedConformance OBJECT IDENTIFIER ::= { tedMIB 2 }
teConformance OBJECT IDENTIFIER ::= { teMIB 2 }
-- MIB Definitions -- MIB Definitions
-- --
-- Scalar Objects -- Scalar Objects
-- --
-- --
-- TE DB Table -- TE DB Table
-- --
teTEDTable OBJECT-TYPE tedTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeTEDEntry 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 [OSPF-TE]." supported by [RFC3630]."
::= { teTables 1 } ::= { tedTables 1 }
teTEDEntry OBJECT-TYPE tedEntry OBJECT-TYPE
SYNTAX TeTEDEntry 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 { ospfAreaId, ospfLsdbLsid, ospflsdbRouterId } INDEX { teAreaId, teRouterId, teLinkStateId }
::= { teTEDTable 1 } ::= { tedTable 1 }
TeTEDEntry ::= SEQUENCE { TedEntry ::= SEQUENCE {
teAreaId Unsigned32,
teRouterId Unsigned32,
teLinkStateId Unsigned32,
teLinkInformationSource INTEGER, teLinkInformationSource INTEGER,
teAreaLevelID OCTET STRING, teLinkInformationData RowPointer,
teLSPDUID OCTET STRING,
teRouterSystemID OCTET STRING,
teLinkType INTEGER, teLinkType INTEGER,
teRouterIdAddr IpAddress,
teLinkIdAddr IpAddress, teLinkIdAddr IpAddress,
teMetric Integer32, teMetric Integer32,
teMaxBandwidth OCTET STRING, teMaxBandwidth OCTET STRING,
teMaxReservableBandwidth OCTET STRING, teMaxReservableBandwidth OCTET STRING,
teUnreservedBandwidthPri0 OCTET STRING, teUnreservedBandwidthPri0 OCTET STRING,
teUnreservedBandwidthPri1 OCTET STRING, teUnreservedBandwidthPri1 OCTET STRING,
teUnreservedBandwidthPri2 OCTET STRING, teUnreservedBandwidthPri2 OCTET STRING,
teUnreservedBandwidthPri3 OCTET STRING, teUnreservedBandwidthPri3 OCTET STRING,
teUnreservedBandwidthPri4 OCTET STRING, teUnreservedBandwidthPri4 OCTET STRING,
teUnreservedBandwidthPri5 OCTET STRING, teUnreservedBandwidthPri5 OCTET STRING,
teUnreservedBandwidthPri6 OCTET STRING, teUnreservedBandwidthPri6 OCTET STRING,
teUnreservedBandwidthPri7 OCTET STRING, teUnreservedBandwidthPri7 OCTET STRING,
T. Otani et al. 6
teAdministrativeGroup Integer32, teAdministrativeGroup Integer32,
teLocalId Integer32, teLocalId Integer32,
teRemoteId Integer32, teRemoteId Integer32,
teLinkProtectionType BITS, teLinkProtectionType BITS
teLinkInformationData RowPointer,
} }
teAreaId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the area identifier of the IGP. If
OSPF is used to advertise LSA, this represents an ospfArea. If ISIS
is used, this represents an area addres. Otherwise, this represents
zero."
::= { tedEntry 1 }
teRouterId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object indicates the router identifier. If OSPF is
used to advertise LSA, this represents a Router ID. If ISIS is used,
this represents a System ID. Otherwise, this represents zero."
::= { tedEntry 2 }
teLinkStateId OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object jndicates the link state identifier. If OSPF
is used, this represents an ospfLsdbID. If ISIS is used, this
represents an isisLSPID. Otherwise, this represents a unique
identifier within a node."
::= { tedEntry 3 }
teLinkInformationSource OBJECT-TYPE teLinkInformationSource OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
locallyConfigured(1), locallyConfigured(1),
ospf(2), ospf(2),
isis(3), isis(3),
other(4) other(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the source of the information about "This object indicates the source of the information about
the TE link" the TE link"
::= { teTEDEntry 1 } ::= { tedEntry 4 }
teAreaLevelId OBJECT-TYPE
SYNTAX Usigned32 {ospfAreaId, IsisISLevel}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is corresponding to area ID in OSPF and level ID in
ISIS"
::= { teTEDEntry 2 }
teOSPDUId OBJECT-TYPE
SYNTAX Usigned32 {ospfLsdbLsid, IsisLinkStatePDUID}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is corresponding to link state ID in OSPF and link
state PDU ID in ISIS"
::= { teTEDEntry 3 }
teRouterSystem OBJECT-TYPE teLinkInformationData OBJECT-TYPE
SYNTAX Usigned32 {ospfLsdbRouterId, IsisSystemID} SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is corresponding to the router ID in OSPF and the "This object cross-references the source of the information
system ID in ISIS" about this TE link and should be interpretted in the context of
::= { teTEDEntry 4 } teLinkInformationSource.
If teLinkInformationSource has the value unknown(0), this
object SHOULD contain a value of zeroDotZero.If
teLinkInformationSource has the value locallyConfigured(1), this
object MAY contain the identifier of the corresponding row entry in
the teLinkTable of TE-LINK-STD-MIB, the identifier of the
corresponding row in a local proprietary TE link MIB module, or the
value of zeroDotZero otherwise.
If teLinkInformationSource has the value ospf(2), this
object MAY contain the identifier of the corresponding row entry in
the ospfLocalLsdbTable of [OSPF-MIB], or the value of zeroDotZero
otherwise.
If teLinkInformationSource has the value isis(3) this object
MAY contain the identifier of the corresponding row entry in the
isisAreaAddr of [ISIS-MIB], or the value of zeroDotZero otherwise.
If teLinkInformationSource has the value other(4) this
object MAY contain the identifier of the corresponding row entry a
local proprietary MIB module, or the value of zeroDotZero otherwise."
::= { tedEntry 5 }
teLinkType OBJECT-TYPE teLinkType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pointToPoint (1), pointToPoint (1),
T. Otani et al. 7
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 "This indicates the type of the link such as point-to-point
or multi-access" or multi-access"
::= { teTEDEntry 5 } ::= { tedEntry 6 }
teRouterIdAddr OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object indicates the TE-Router ID "
::= { tedEntry 7 }
teLinkIdAddr OBJECT-TYPE teLinkIdAddr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
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 "This indicates the Router ID of the neighbor in the case
of point-to-point links. This also indicates the interface address of point-to-point links. This also indicates the interface address
of the designated router in the case of multi-access links." of the designated router in the case of multi-access links."
::= { teTEDEntry 6 } ::= { tedEntry 8 }
teMetric OBJECT-TYPE teMetric 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 "This indicates the traffic engineering metric value of the
TE link." TE link."
::= { teTEDEntry 7 } ::= { tedEntry 9 }
teMaxBandwidth OBJECT-TYPE teMaxBandwidth OBJECT-TYPE
SYNTAX OCTET STRING (SIZE( 4)) SYNTAX OCTET STRING (SIZE( 4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the maximum bandwidth that "This indicates the maximum bandwidth that
can be used on this link in this direction" can be used on this link in this direction"
::= { teTEDEntry 8 } ::= { tedEntry 10 }
teMaxReservableBandwidth OBJECT-TYPE teMaxReservableBandwidth OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
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"
::= { teTEDEntry 9 } ::= { tedEntry 11 }
teUnreservedBandwidthPri0 OBJECT-TYPE teUnreservedBandwidthPri0 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
T. Otani et al. 8
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 0" the priority 0"
::= { teTEDEntry 10 } ::= { tedEntry 12 }
teUnreservedBandwidthPri1 OBJECT-TYPE teUnreservedBandwidthPri1 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 1" the priority 1"
::= { teTEDEntry 11 } ::= { tedEntry 13 }
teUnreservedBandwidthPri2 OBJECT-TYPE teUnreservedBandwidthPri2 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 2" the priority 2"
::= { teTEDEntry 12 } ::= { tedEntry 14 }
teUnreservedBandwidthPri3 OBJECT-TYPE teUnreservedBandwidthPri3 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 3" the priority 3"
::= { teTEDEntry 13 } ::= { tedEntry 15 }
teUnreservedBandwidthPri4 OBJECT-TYPE teUnreservedBandwidthPri4 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 4" the priority 4"
::= { teTEDEntry 14 } ::= { tedEntry 16 }
teUnreservedBandwidthPri5 OBJECT-TYPE teUnreservedBandwidthPri5 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 5" the priority 5"
::= { teTEDEntry 15 } ::= { tedEntry 17 }
T. Otani et al. 9
teUnreservedBandwidthPri6 OBJECT-TYPE teUnreservedBandwidthPri6 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 6" the priority 6"
::= { teTEDEntry 16 } ::= { tedEntry 18 }
teUnreservedBandwidthPri7 OBJECT-TYPE teUnreservedBandwidthPri7 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the amount of bandwidth not yet reserved at "This indicates the amount of bandwidth not yet reserved at
the priority 7" the priority 7"
::= { teTEDEntry 17 } ::= { tedEntry 19 }
teAdministrativeGroup OBJECT-TYPE teAdministrativeGroup 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 "This indicates the Administrative Group which the link
belong to. Since the value is a bit mask, the link can belong to belong to. Since the value is a bit mask, the link can belong to
multiple groups. This is also called Resource Class/Color." multiple groups. This is also called Resource Class/Color."
::= { teTEDEntry 18 } ::= { tedEntry 20 }
teLocalId OBJECT-TYPE teLocalId 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."
::= { teTEDEntry 19 } ::= { tedEntry 21 }
teRemoteId OBJECT-TYPE teRemoteId 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."
::= { teTEDEntry 20 } ::= { tedEntry 22 }
teLinkProtectionType OBJECT-TYPE teLinkProtectionType OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
extraTraffic(0), extraTraffic(0),
unprotected(1), unprotected(1),
shared (2), shared (2),
dedicatedOneToOne (3), dedicatedOneToOne (3),
T. Otani et al. 10
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"
::= { teTEDEntry 21 } ::= { tedEntry 23 }
teLinkInformationData OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object cross-references the source of the information
about this TE link and should be interpretted in the context of
teLinkInformationSource.
If teLinkInformationSource has the value unknown(0) this
object SHOULD contain a value of zeroDotZero.
If teLinkInformationSource has the value
locallyConfigured(1), this object MAY contain the identifier of the
corresponding row entry in the teLinkTable of TE-LINK-STD-MIB, MAY
contain the identifier of the corresponding row in a local
proprietary TE link MIB module, or otherwise SHOULD contain the value
of zeroDotZero.
If teLinkInformationSource has the value ospf(2), this
object MAY contain the identifier of the corresponding row entry in
the ospfLocalLsdbTable of [OSPF-MIB], or otherwise SHOULD contain the
value of zeroDotZero.
If teLinkInformationSource has the value isis(3) this object
MAY contain the identifier of the corresponding row entry in the
isisAreaAddr of [ISIS-MIB], or otherwise SHOULD contain the value of
zeroDotZero.
If teLinkInformationSource has the value other(4) this
object MAY contain the identifier of the corresponding row entry a
local proprietary MIB module, or otherwise SHOULD contain the value
of zeroDotZero."
::= { teTEDEntry 22 }
-- --
-- TED Local Interface IP Address Table -- TED Local Interface IP Address Table
-- --
teLocalIntAddrTable OBJECT-TYPE teLocalIntAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeLocalIntAddrEntry SYNTAX SEQUENCE OF TeLocalIntAddrEntry
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
link." link."
::= { teTables 2 } ::= { tedTables 2 }
teLocalIntAddrEntry OBJECT-TYPE teLocalIntAddrEntry OBJECT-TYPE
SYNTAX TeLocalIntAddrEntry SYNTAX TeLocalIntAddrEntry
T. Otani et al. 11
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains the IP address information of the local "This entry contains the IP address information of the local
TE link." TE link."
INDEX { ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId, INDEX { teAreaId, teRouterId, teLinkStateId,
teLocalIntAddrIndex } teLocalIntAddrIndex }
::= { teLocalIntAddrTable 1 } ::= { teLocalIntAddrTable 1 }
TeLocalIntAddrEntry ::= SEQUENCE { TeLocalIntAddrEntry ::= SEQUENCE {
teLocalIntAddrIndex Unsigned32, teLocalIntAddrIndex Unsigned32,
teLocalIntAddr IpAddress, teLocalIntAddr IpAddress
} }
teLocalIntAddrIndex OBJECT-TYPE teLocalIntAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the index to identify multiple local TE links" "This indicates the index to identify multiple local TE links"
::= { teLocalIntAddrEntry 1 } ::= { teLocalIntAddrEntry 1 }
skipping to change at line 609 skipping to change at page 13, line 15
-- TED Remote Interface IP Address Table -- TED Remote Interface IP Address Table
-- --
teRemoteIntAddrTable OBJECT-TYPE teRemoteIntAddrTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeRemoteIntAddrEntry SYNTAX SEQUENCE OF TeRemoteIntAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains the IP address information of a remote "This table contains the IP address information of a remote
TE link." TE link."
::= { teTables 3 } ::= { tedTables 3 }
teRemoteIntAddrEntry OBJECT-TYPE teRemoteIntAddrEntry OBJECT-TYPE
SYNTAX TeRemoteIntAddrEntry SYNTAX TeRemoteIntAddrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry contains the IP address information of the remote "This entry contains the IP address information of the remote
TE link." TE link."
INDEX { ospfAreaId, ospfLsdbLsid, ospflsdbRouterId, INDEX { teAreaId, teRouterId, teLinkStateId, teRemoteIntAddrIndex }
teRemoteIntAddrIndex }
::= { teRemoteIntAddrTable 1 } ::= { teRemoteIntAddrTable 1 }
T. Otani et al. 12
TeRemoteIntAddrEntry ::= SEQUENCE { TeRemoteIntAddrEntry ::= SEQUENCE {
teRemoteIntAddrIndex Unsigned32, teRemoteIntAddrIndex Unsigned32,
teRemoteIntAddr IpAddress, teRemoteIntAddr IpAddress
} }
teRemoteIntAddrIndex OBJECT-TYPE teRemoteIntAddrIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This indicates the index to identify multiple remote TE "This indicates the index to identify multiple remote TE
links." links."
::= { teRemoteIntAddrEntry 1 } ::= { teRemoteIntAddrEntry 1 }
skipping to change at line 656 skipping to change at page 14, line 7
-- TED Switch Capable Table -- TED Switch Capable Table
-- --
teSwCapTable OBJECT-TYPE teSwCapTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeSwCapEntry SYNTAX SEQUENCE OF TeSwCapEntry
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."
::= { teTables 4 } ::= { tedTables 4 }
teSwCapEntry OBJECT-TYPE teSwCapEntry OBJECT-TYPE
SYNTAX TeSwCapEntry SYNTAX TeSwCapEntry
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 deals with only OSPF-TE capability information. IF the MIB deals with only OSPF-TE
information, the value of each object related with GMPLS TE information, the value of each object related with GMPLS TE
extensions should be null." extensions should be null."
INDEX { ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId, INDEX { teAreaId, teRouterId, teLinkStateId, teSwCapIndex }
teSwCapIndex }
::= { teSwCapTable 1 } ::= { teSwCapTable 1 }
TeSwCapEntry ::= SEQUENCE { TeSwCapEntry ::= SEQUENCE {
teSwCapIndex Unsigned32, teSwCapIndex Unsigned32,
teSwitchingType INTEGER, teSwitchingType INTEGER,
teEncoding INTEGER, teEncoding INTEGER,
T. Otani et al. 13
teMaxLspBandwidthPri0 OCTET STRING, teMaxLspBandwidthPri0 OCTET STRING,
teMaxLspBandwidthPri1 OCTET STRING, teMaxLspBandwidthPri1 OCTET STRING,
teMaxLspBandwidthPri2 OCTET STRING, teMaxLspBandwidthPri2 OCTET STRING,
teMaxLspBandwidthPri3 OCTET STRING, teMaxLspBandwidthPri3 OCTET STRING,
teMaxLspBandwidthPri4 OCTET STRING, teMaxLspBandwidthPri4 OCTET STRING,
teMaxLspBandwidthPri5 OCTET STRING, teMaxLspBandwidthPri5 OCTET STRING,
teMaxLspBandwidthPri6 OCTET STRING, teMaxLspBandwidthPri6 OCTET STRING,
teMaxLspBandwidthPri7 OCTET STRING, teMaxLspBandwidthPri7 OCTET STRING,
teMinLspBandwidth OCTET STRING, teMinLspBandwidth OCTET STRING,
teIntMtu Integer32, teIntMtu Integer32,
skipping to change at line 731 skipping to change at page 15, line 25
ethernet (2), ethernet (2),
ansiEtsiPdh (3), ansiEtsiPdh (3),
sdhSonet (5), sdhSonet (5),
digitalWrapper (7), digitalWrapper (7),
lambda (8), lambda (8),
fiber (9), fiber (9),
fiberChannel (11) fiberChannel (11)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
T. Otani et al. 14
DESCRIPTION DESCRIPTION
"This object indicates the GMPLS encoding type assigned to "This object indicates the GMPLS encoding type assigned to
the TE link." the TE link."
::= { teSwCapEntry 3 } ::= { teSwCapEntry 3 }
teMaxLspBandwidthPri0 OBJECT-TYPE teMaxLspBandwidthPri0 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at line 788 skipping to change at page 16, line 26
teMaxLspBandwidthPri4 OBJECT-TYPE teMaxLspBandwidthPri4 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link "This object indicates the maximum bandwidth of the TE link
at the priority 4 for GMPLS LSP creation." at the priority 4 for GMPLS LSP creation."
::= { teSwCapEntry 8 } ::= { teSwCapEntry 8 }
T. Otani et al. 15
teMaxLspBandwidthPri5 OBJECT-TYPE teMaxLspBandwidthPri5 OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (4)) SYNTAX OCTET STRING (SIZE (4))
UNITS "Byte per seconds" UNITS "Byte per seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum bandwidth of the TE link "This object indicates the maximum bandwidth of the TE link
at the priority 5 for GMPLS LSP creation." at the priority 5 for GMPLS LSP creation."
::= { teSwCapEntry 9 } ::= { teSwCapEntry 9 }
skipping to change at line 842 skipping to change at page 17, line 25
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 "This object indicates the MTU of the local or remote TE
link" link"
::= { teSwCapEntry 13 } ::= { teSwCapEntry 13 }
teIndication OBJECT-TYPE teIndication OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
T. Otani et al. 16
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 "This object indicates whether the interface supports
Standard or Arbitrary SONET/SDH." Standard or Arbitrary SONET/SDH."
::= { teSwCapEntry 14 } ::= { teSwCapEntry 14 }
-- --
-- TED SRLG Table -- TED SRLG Table
-- --
teSrlgTable OBJECT-TYPE teSrlgTable OBJECT-TYPE
SYNTAX SEQUENCE OF TeSrlgEntry SYNTAX SEQUENCE OF TeSrlgEntry
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."
::= { teTables 5 } ::= { tedTables 5 }
teSrlgEntry OBJECT-TYPE teSrlgEntry OBJECT-TYPE
SYNTAX TeSrlgEntry SYNTAX TeSrlgEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This entry relates each TE link with its SRLG information." "This entry relates each TE link with its SRLG information."
INDEX { ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId, teSrlgIndex } INDEX { teAreaId, teRouterId, teLinkStateId, teSrlgIndex }
::= { teSrlgTable 1 } ::= { teSrlgTable 1 }
TeSrlgEntry ::= SEQUENCE { TeSrlgEntry ::= SEQUENCE {
teSrlgIndex Unsigned32 teSrlgIndex Unsigned32,
teSrlg Integer32 teSrlg Integer32
} }
teSrlgIndex OBJECT-TYPE teSrlgIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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." local or remote TE link."
::= { teSrlgTableEntry 1 } ::= { teSrlgEntry 1 }
teSrlg OBJECT-TYPE teSrlg 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 indicate the SRLG value assigned to a local or
remote TE link" remote TE link"
::= { teSrlgEntry 2 } ::= { teSrlgEntry 2 }
T. Otani et al. 17
-- Conformance Statement -- Conformance Statement
teGroups tedGroups
OBJECT IDENTIFIER ::= { teConformance 1 } OBJECT IDENTIFIER ::= { tedConformance 1 }
teCompliances tedCompliances
OBJECT IDENTIFIER ::= { teConformance 2 } OBJECT IDENTIFIER ::= { tedConformance 2 }
-- Module Compliance -- Module Compliance
teModuleFullCompliance MODULE-COMPLIANCE teModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance statement for agents provides full support "Compliance statement for agents provides full support
for the TED MIB" for the TED MIB"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { teMainGroup MANDATORY-GROUPS { tedMainGroup
} }
::= { teCompliances 1 } ::= { tedCompliances 1 }
-- --
-- ReadOnly Compliance -- ReadOnly Compliance
-- --
teModuleReadOnlyCompliance MODULE-COMPLIANCE teModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations only provide "Compliance requirement for implementations only provide
read-only support for TED. Such devices can then be monitored read-only support for TED. Such devices can then be monitored
but cannot be configured using this MIB module. but cannot be configured using this MIB module.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { teMainGroup MANDATORY-GROUPS { tedMainGroup
} }
::= { teCompliances 2 } ::= { tedCompliances 2 }
-- Units of conformance. -- Units of conformance.
teMainGroup OBJECT-GROUP tedMainGroup OBJECT-GROUP
OBJECTS { OBJECTS {
teLinkInformationSource , teLinkInformationSource ,
teLinkType , teLinkType ,
teRouterIdAddr ,
teLinkIdAddr , teLinkIdAddr ,
teMetric , teMetric ,
teMaxBandwidth , teMaxBandwidth ,
teMaxReservableBandwidth , teMaxReservableBandwidth ,
teUnreservedBandwidthPri0 , teUnreservedBandwidthPri0 ,
teUnreservedBandwidthPri1 , teUnreservedBandwidthPri1 ,
teUnreservedBandwidthPri2 , teUnreservedBandwidthPri2 ,
teUnreservedBandwidthPri3 , teUnreservedBandwidthPri3 ,
teUnreservedBandwidthPri4 , teUnreservedBandwidthPri4 ,
teUnreservedBandwidthPri5 , teUnreservedBandwidthPri5 ,
teUnreservedBandwidthPri6 , teUnreservedBandwidthPri6 ,
T. Otani et al. 18
teUnreservedBandwidthPri7 , teUnreservedBandwidthPri7 ,
teAdministrativeGroup , teAdministrativeGroup ,
teLocalId , teLocalId ,
teRemoteId , teRemoteId ,
teLinkProtectionType , teLinkProtectionType ,
teLinkInformationData , teLinkInformationData ,
teLocalIntAddr , teLocalIntAddr ,
teRemoteIntAddr , teRemoteIntAddr ,
teSwitchingType , teSwitchingType ,
teEncoding , teEncoding ,
skipping to change at line 980 skipping to change at page 19, line 51
teMaxLspBandwidthPri6 , teMaxLspBandwidthPri6 ,
teMaxLspBandwidthPri7 , teMaxLspBandwidthPri7 ,
teMinLspBandwidth , teMinLspBandwidth ,
teIntMtu , teIntMtu ,
teIndication , teIndication ,
teSrlg teSrlg
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects for TED management" "Collection of objects for TED management"
::= { teGroups 1 } ::= { tedGroups 1 }
END END
6. Security consideration 7. Security consideration
This document introduces no new security issues beyond those detailed This document introduces no new security issues beyond those detailed
in the OSPF MIB. in the OSPF MIB.
7. IANA Considerations 8. IANA Considerations
The following "IANA Considerations" subsection requests IANA for a The following "IANA Considerations" subsection requests IANA for a
new assignment under the transmission subtree. New assignments can new assignment under the transmission subtree. New assignments can
only be made via a Standards Action as specified in [RFC2434]. only be made via a Standards Action as specified in [RFC2434].
7.1 IANA Considerations for TED-STD-MIB 8.1 IANA Considerations for TED-MIB
The IANA is requested to assign { teMIB XXX } to the TED-STD-MIB The IANA is requested to assign { transmission XXX } to the TED-MIB
module specified in this document. module specified in this document.
8. References 9. References
8.1 Normative References 9.1 Normative References
8.2 Informative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579,
April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
9.2 Informative References
T. Otani et al. 19
[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.
[OSPFMIB] F. Baker, et al, "OSPF Version 2 Management [RFC1850] F. Baker, et al, "OSPF Version 2 Management
Information Base", RFC1850, Nov. 1995. Information Base", RFC1850, Nov. 1995.
[OSPFMIB UPDATE]Dan Joyal, et al, "OSPF Version 2 Management [RFC 4750] Dan Joyal, et al, "OSPF Version 2 Management
Information Base", draft-ietf-ospf-mib-update-08.txt, Information Base", RFC4750, December 2006.
December 2003.
[ISISMIB] J. Parker, et al, "Management Information Base for [RFC4444] J. Parker, et al, "Management Information Base for
Intermediate System to Intermediate System (IS-IS)", Intermediate System to Intermediate System (IS-IS)",
RFC 4444, April 2006. RFC 4444, April 2006.
[GMPLSRouting] K. Kompella, and Y. Rekhter, "Routing Extensions in [RFC4202] K. Kompella, and Y. Rekhter, "Routing Extensions in
Support of Generalized Multi-Protocol Label Support of Generalized Multi-Protocol Label
Switching", RFC4202, Oct. 2005. Switching", RFC4202, Oct. 2005.
[RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions
to OSPF Version2", RFC3630, September 2003. to OSPF Version2", RFC3630, September 2003.
[GMPLSisis] K. Kompella, and Y. Rekhter, "Intermediate System to [RFC4205] K. Kompella, and Y. Rekhter, " Intermediate System to
Intermediate System (IS-IS) Extensions in Support of Intermediate System (IS-IS) Extensions in Support of
Multi-Protocol Label Switching (GMPLS)", RFC4205, Oct. Multi-Protocol Label Switching (GMPLS)", RFC4205, Oct.
2005. 2005.
[RFC3784] H. Smit and T. Li, "IS-IS extensions for Traffic [RFC3784] H. Smit and T. Li, IS-IS extensions for Traffic
Engineering”, RFC 3784, June 2004. Engineering”, RFC 3784, June 2004.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic "Multiprotocol Label Switching (MPLS) Traffic
Engineering (TE) Management Information Base (MIB)", Engineering (TE) Management Information Base (MIB)",
RFC 3812, June 2004. RFC 3812, June 2004.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Label Switching "Multiprotocol Label Switching (MPLS) Label Switching
(LSR) Router Management Information Base (MIB)", RFC (LSR) Router Management Information Base (MIB)", RFC
skipping to change at line 1060 skipping to change at page 21, line 40
[GMPLSTEMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol [GMPLSTEMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol
Label Switching (GMPLS) Traffic Engineering Label Switching (GMPLS) Traffic Engineering
Management Information Base", draft-ietf-ccamp-gmpls- Management Information Base", draft-ietf-ccamp-gmpls-
te-mib-09.txt, June 2005. te-mib-09.txt, June 2005.
[MPLS OAM] T. Nadeau, Allan D., et al., "OAM Requirements for [MPLS OAM] T. Nadeau, Allan D., et al., "OAM Requirements for
MPLS Network" MPLS Network"
draft-ietf-mpls-oam-requirements-05.txt, June 2005. draft-ietf-mpls-oam-requirements-05.txt, June 2005.
T. Otani et al. 20
[RFC3945] E. Mannie, "Generalized Multi-Protocol Label [RFC3945] E. Mannie, "Generalized Multi-Protocol Label
Switching Architecture", RFC3945, October, 2004. Switching Architecture", RFC3945, October, 2004.
[GMPLSOSPF] K. Kompella, and Y. Rekhter, "OSPF Extensions in [RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in
Support of Generalized Multi-Protocol Label Support of Generalized Multi-Protocol Label
Switching", RFC4203, Oct. 2005. Switching", RFC4203, Oct. 2005.
[OSPF-TE] Katz, D., et al, "Traffic Engineering (TE) Extensions [RFC3630] Katz, D., et al, "Traffic Engineering (TE) Extensions
to OSPF Version 2", RFC3630, September 2003. to OSPF Version 2", RFC3630, September 2003.
[RFC2434] Narten, T. and H. Alvestrand., "Guidelines for [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for
Writing an IANA Considerations Section in RFCs" BCP Writing an IANA Considerations Section in RFCs" BCP
26, RFC 2434, October 1998. 26, RFC 2434, October 1998.
9. Acknowledgment 10. 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 and Adrian Farrel. Okamoto and Adrian Farrel.
10. Author’s Address 11. Author's Address
Tomohiro Otani Tomohiro Otani
KDDI R&D Laboratories, Inc. KDDI R&D Laboratories, Inc.
2-1-15 Ohara Fujimino Phone: +81-49-278-7357 2-1-15 Ohara Fujimino Phone: +81-49-278-7357
Saitama, 356-8502. Japan Email: otani@kddilabs.jp Saitama, 356-8502. Japan Email: otani@kddilabs.jp
Masanori Miyazawa Masanori Miyazawa
KDDI R&D Laboratories, Inc. KDDI R&D Laboratories, Inc.
2-1-15 Ohara Fujimino Phone: +81-49-278-7559 2-1-15 Ohara Fujimino Phone: +81-49-278-7559
Saitama, 356-8502. Japan Email: ma-miyazawa@kddilabs.jp Saitama, 356-8502. Japan Email: ma-miyazawa@kddilabs.jp
skipping to change at line 1103 skipping to change at page 22, line 30
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road Phone: +1-978-936-1470 300 Beaver Brook Road Phone: +1-978-936-1470
Boxboro, MA 01719 Email: tnadeau@cisco.com300 Boxboro, MA 01719 Email: tnadeau@cisco.com300
Kenji Kumaki Kenji Kumaki
KDDI Corporation KDDI Corporation
GARDEN AIR TOWER,3-10-10,Iidabshi Phone: +81-3-6678-3103 GARDEN AIR TOWER,3-10-10,Iidabshi Phone: +81-3-6678-3103
Chiyoda-ku,Tokyo, 102-8460. Japan Email: ke-kumaki@kddi.com Chiyoda-ku,Tokyo, 102-8460. Japan Email: ke-kumaki@kddi.com
11. Intellectual Property Statement 12. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
T. Otani et al. 21
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
12. Copyright Statement 13. Copyright Statement
"Copyright (C) The IETF Trust (2006). This document is subject to the Copyright (C) The IETF Trust (2007).
rights, licenses and restrictions contained in BCP 78, and except as
set forth therein, the authors retain all their rights."
"This document and the information contained herein are provided on This document is subject to the rights, licenses and restrictions
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE contained in BCP 78, and except as set forth therein, the authors
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE retain all their rights.
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE."
T. Otani et al. 22 This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 118 change blocks. 
246 lines changed or deleted 242 lines changed or added

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