IETF Internet Draft Masanori Miyazawa Proposed status: Standards Track Tomohiro Otani Expires: October 2006 KDDI R&D Labs Thomas D. Nadeau Cisco Systems Kenji Kumaki KDDI CorporationExtensions to the OSPFOctober 2006 Traffic Engineering Database Management Information Base in support of GMPLSdraft-ietf-ccamp-gmpls-ospf-mib-00.txtdraft-ietf-ccamp-gmpls-ospf-mib-01.txt Status of this Memo By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This memo defines the Management Information Base (MIB) objects in order to manageOSPF routingtraffic engineering database (TED) information with extension in support of Multi-protocol label switching (MPLS) as well as Generalized MPLS (GMPLS) for use with network management protocols. Table of Contentsin support of GMPLS................................................1Status of this Memo................................................1 Abstract...........................................................1 1. Introduction....................................................3 2. Terminology.....................................................3 T. Otani et al. 12. Terminology.....................................................32.1 Conventions used in this document..............................3 2.2 Terminology....................................................3 2.3 Acronyms.......................................................3 3. Motivations.....................................................4 4. Brief description of MIB Objects................................4 4.1ospfTeLsdbTable................................................4teTEDTable.....................................................4 4.2ospfTeLocalIntIpAddrTable......................................4teLocalIntIpAddrTable..........................................4 4.3ospfTeRemoteIntIpAddrTable.....................................4teRemoteIntIpAddrTable.........................................4 4.4ospfTeSwCapTable...............................................4teSwCapTable...................................................4 4.5ospfTeSrlgTable................................................4teSrlgTable....................................................4 5.OSPF-TETED MIB Definitionswith GMPLS extensions...................4in support of GMPLS.........................4 6. Securityconsideration.........................................18consideration.........................................19 7. IANAConsiderations............................................18Considerations............................................19 7.1 IANA Considerations forOSPF-TE-STD-MIB.......................18TED-STD-MIB...........................19 8.References.....................................................18References.....................................................19 8.1 NormativeReferences..........................................18References..........................................19 8.2 InformativeReferences........................................18References........................................19 9.Acknowledgment.................................................19Acknowledgment.................................................21 10. Author’sAddress..............................................19Address..............................................21 11. Intellectual PropertyStatement...............................20Statement...............................21 12. CopyrightStatement...........................................20Statement...........................................22 T. Otani et al. 2 1. Introduction The OSPF MIB is defined as [OSPFMIB]and isbeing extended by [OSPFMIBUPDATE].UPDATE] and The ISIS MIB as [ISISMIB]. On the other side, MPLS/GMPLS based traffic engineering has so far extendedOSPFOSPF/ISIS routing protocol with TE functionality [GMPLSrouting,RFC3630].RFC3630, GMPLSisis, RFC3784]. To manage such MPLS/GMPLS networks effectively,OSPFrouting 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 intheexistingOSPF MIB.MIBs related with OSPF/ISIS. This memo defines the Management Information Base (MIB) objects for managingOSPF extensionTED in support of MPLS/GMPLS for use with network management protocols. This MIB module should be used in conjunction withOSPFOSPF/ISIS MIB as well as other MIBs defined in [RFC3812, RFC3813, GMPLSLSRMIB, GMPLSTEMIB] for the management of MPLS/GMPLS based traffic engineering information. 2. Terminology 2.1 Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119]. 2.2 Terminology 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 definitions which are not repeated here. 2.3 Acronyms GMPLS: Generalized Multi-Protocol Label Switching LDP: Label Distribution Protocol LSP: Label Switching Path LSR: Label Switching Router MIB: Management Information Base OAM: Operations and Management OA&M: Operations, Administration and Maintenance. OSPF: Open Shortest Path First RSVP: Resource reSerVation Protocol TE: Traffic Engineering PSC: Packet switch capable LSC: Lambda switch capable FSC: Fiber switch capable TDM: Time Division Multiplexing SRLG: Shared risk link group LSA: Link state advertisement T. Otani et al. 3 3. Motivations The existing OSPF, MPLS and GMPLS MIBs do not provide for the management of all of the extensions to the OSPF protocol. To manage GMPLSroutingTE attributes, MIB objects to indicate such GMPLSOSPF-TE attributesTED is significant. 4. Brief description of MIB Objects The objects described in this section support the management ofattributesTED described in[GMPLSrouting] and[GMPLSrouting], [GMPLSOSPF] and [GMPLSisis] forOSPF-TE withGMPLS extensions as well as in [RFC3630] and [RFC3784] forOSPF-TE.MPLS/GMPLS. 4.1ospfTeLsdbTableteTEDTable TheospfTeLsdbTableteTEDTable is basically used to indicatemultiple sub-TLVsTED informationin opaque LSA which have been supported by [OSPF-TE].of OSPF- TE or ISIS-TE. However, this table does not contain the information of Local/Remote interface IP address, Interface Switching Capcability Descriptor and Shared Risk Link Group information within the sub-TLVs for theLink- TLV.Link-TLV. 4.2ospfTeLocalIntIpAddrTableteLocalIntIpAddrTable TheospfTeLocalIntIpAddrTableteLocalIntIpAddrTable is identical to the Local interface IP address information in a sub-TLV for the Link-TLV. This is independently defined, because the Interface IP Address sub-TLV may appear more than once within the same Link-TLV. 4.3ospfTeRemoteIntIpAddrTableteRemoteIntIpAddrTable TheospfTeRemoteIntIpAddrTableteRemoteIntIpAddrTable is identical to the Remote interface IP address information in a sub-TLV of the Link-TLV. This is also independently utilized, because one or more local interface IP address sub TLVs may exist in the same Link-TLV. 4.4ospfTeSwCapTableteSwCapTable TheospfTeSwCapTableteSwCapTable represents Interface Switching Capability Descriptor information. This is independently defined due to the possibility of multiple appearances of the sub TLV within the same Link-TLV. 4.5ospfTeSrlgTableteSrlgTable TheospfTeSrlgTableteSrlgTable contains the Sub-TLV information of Shared Risk Link Group (SRLG) information. This is separately defined, because more than one sub TLVs may appear in the same Link-TLV. 5.OSPF-TETED MIB Definitionswithin support of GMPLSextensionsT. Otani et al. 4OSPF-TE-DRAFT00-MIBTED-DRAFT01-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32,Unsigned32Unsigned32, transmission, IpAddress FROM SNMPv2-SMI --[RFC2578] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF --[RFC2580]InetAddressType, InetAddressRowPointer FROMINET-ADDRESS-MIB transmission FROM SNMPv2-SMI --[RFC2578]SNMPv2-TC --[RFC2579] ospfAreaId, ospfLsdbLsid,ospfRouterIdospfLsdbRouterId FROM OSPF-MIB; --[OSPFMIB UPDATE]ospfTeMIBIsisISLevel, IsisLinkStatePDUID, IsisSystemID FROM ISIS-MIB; --[ISISMIB] teMIB MODULE-IDENTITY LAST-UPDATED "200510240000Z" -- 04 July 2005 00:00:00 GMT ORGANIZATION "IETF CCAMP Working Group." CONTACT-INFO " Tomohiro Otani otani@kddilabs.jp Masanori Miyazawa ma-miyazawa@kddilabs.jp Thomas D. Nadeau tnadeau@cisco.com Kenji Kumaki ke-kumaki@kddi.com Comments and discussion to ccamp@ietf.org" DESCRIPTION "This MIB contains managed object definitions forextensions to the OSPF MIBTED in support of MPLS/GMPLS Traffic Engienering(TE).(TE) Database. Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFCXXX; see the RFC itself for full legal notices." -- Revision history. REVISION "200506041200Z" -- 04 July 2005 12:00:00 GMT DESCRIPTION "Initial version. Published as RFC xxxx." -- RFC-editor pls fillin xxx"--in xxx ::= { transmission 9988 } -- assigned by IANA, see section 7.1 for -- details -- Textual Conventions. -- Top level components of this MIB.ospfTeNotificationsteNotifications OBJECT IDENTIFIER ::= {ospfTeMIBteMIB 0 }ospfTeObjectsT. Otani et al. 5 teObjects OBJECT IDENTIFIER ::= {ospfTeMIBteMIB 1 }T. Otani et al. 5 ospfTeScalarsteScalars OBJECT IDENTIFIER ::= {ospfTeObjectsteObjects 1 }ospfTeTablesteTables OBJECT IDENTIFIER ::= {ospfTeObjectsteObjects 2 }ospfTeConformanceteConformance OBJECT IDENTIFIER ::= {ospfTeMIBteMIB 2 } -- MIB Definitions -- -- Scalar Objects -- -- --OSPFTELSDBDB Table --ospfTeLsdbTableteTEDTable OBJECT-TYPE SYNTAX SEQUENCE OFOspfTeLsdbEntryTeTEDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table indicates multiplesub-TLVsTED informationin opaque LSAwhichhavehas been supported by[OSPF-TE]. "[OSPF-TE]." ::= {ospfTeTablesteTables 1 }ospfTeLsdbEntryteTEDEntry OBJECT-TYPE SYNTAXOspfTeLsdbEntryTeTEDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry containseach sub-TLVsTED information commonly utilized in both MPLS and GMPLS" INDEX { ospfAreaId, ospfLsdbLsid, ospflsdbRouterId } ::= {ospfTeLsdbTableteTEDTable 1 }OspfTeLsdbEntryTeTEDEntry ::= SEQUENCE {ospfTeLinkTypeteLinkInformationSource INTEGER,ospfTeLinkIdAddr InetAddress, ospfTeLinkIdAddrType InetAddressType, ospfTeMetric Integer32, ospfTeMaxBandwidth Unsigned32, ospfTeMaxReservableBandwidth Unsigned32, ospfTeUnreservedBandwidthPri0 Unsigned32, ospfTeUnreservedBandwidthPri1 Unsigned32, ospfTeUnreservedBandwidthPri2 Unsigned32, ospfTeUnreservedBandwidthPri3 Unsigned32, ospfTeUnreservedBandwidthPri4 Unsigned32, ospfTeUnreservedBandwidthPri5 Unsigned32, ospfTeUnreservedBandwidthPri6 Unsigned32, ospfTeUnreservedBandwidthPri7 Unsigned32, ospfTeAdministrativeGroup Integer32, ospfTeLocalIdteAreaLevelID OCTET STRING, teLSPDUID OCTET STRING, teRouterSystemID OCTET STRING, teLinkType INTEGER, teLinkIdAddr IpAddress, teMetric Integer32,ospfTeRemoteIdteMaxBandwidth OCTET STRING, teMaxReservableBandwidth OCTET STRING, teUnreservedBandwidthPri0 OCTET STRING, teUnreservedBandwidthPri1 OCTET STRING, teUnreservedBandwidthPri2 OCTET STRING, teUnreservedBandwidthPri3 OCTET STRING, teUnreservedBandwidthPri4 OCTET STRING, teUnreservedBandwidthPri5 OCTET STRING, teUnreservedBandwidthPri6 OCTET STRING, teUnreservedBandwidthPri7 OCTET STRING, teAdministrativeGroup Integer32,ospfTeLinkProtectionType INTEGER, }T. Otani et al. 6ospfTeLinkTypeteLocalId Integer32, teRemoteId Integer32, teLinkProtectionType BITS, teLinkInformationData RowPointer, } teLinkInformationSource OBJECT-TYPE SYNTAX INTEGER { unknown(0), locallyConfigured(1), ospf(2), isis(3), other(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the source of the information about the TE link" ::= { teTEDEntry 1 } 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 SYNTAX Usigned32 {ospfLsdbRouterId, IsisSystemID} MAX-ACCESS read-only STATUS current DESCRIPTION “This is corresponding to the router ID in OSPF and the system ID in ISIS” ::= { teTEDEntry 4 } teLinkType OBJECT-TYPE SYNTAX INTEGER { pointToPoint (1), multiAccess (2) T. Otani et al. 7 } MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the type of the link such as point-to-point or multi-access" ::= {ospfTeLsdbEntry 1teTEDEntry 5 }ospfTeLinkIdAddrteLinkIdAddr OBJECT-TYPE SYNTAXInetAddressIpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the Router ID of the neighbor in the case of point-to-point links. This also indicates the interface address of the designated router in the case of multi-access links." ::= {ospfTeLsdbEntry 2 } ospfTeLinkIdAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the type of TE link ID address." ::= { ospfTeLsdbEntry 3teTEDEntry 6 }ospfTeMetricteMetric OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the traffic engineering metric value of the TE link." ::= {ospfTeLsdbEntry 4teTEDEntry 7 }ospfTeMaxBandwidthteMaxBandwidth OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE( 4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the maximum bandwidth that can be used on this link in this direction" ::= {ospfTeLsdbEntry 5teTEDEntry 8 }ospfTeMaxReservableBandwidthteMaxReservableBandwidth OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTIONT. Otani et al. 7"This indicates the maximum bandwidth that may be reserved on this link in this direction" ::= {ospfTeLsdbEntry 6teTEDEntry 9 }ospfTeUnreservedBandwidthPri0teUnreservedBandwidthPri0 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION T. Otani et al. 8 "This indicates the amount of bandwidth not yet reserved at the priority 0" ::= {ospfTeLsdbEntry 7teTEDEntry 10 }ospfTeUnreservedBandwidthPri1teUnreservedBandwidthPri1 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 1" ::= {ospfTeLsdbEntry 8teTEDEntry 11 }ospfTeUnreservedBandwidthPri2teUnreservedBandwidthPri2 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 2" ::= {ospfTeLsdbEntry 9teTEDEntry 12 }ospfTeUnreservedBandwidthPri3teUnreservedBandwidthPri3 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 3" ::= {ospfTeLsdbEntry 10teTEDEntry 13 }ospfTeUnreservedBandwidthPri4teUnreservedBandwidthPri4 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 4" ::= {ospfTeLsdbEntry 11teTEDEntry 14 }ospfTeUnreservedBandwidthPri5teUnreservedBandwidthPri5 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTIONT. Otani et al. 8"This indicates the amount of bandwidth not yet reserved at the priority 5" ::= {ospfTeLsdbEntry 12teTEDEntry 15 }ospfTeUnreservedBandwidthPri6T. Otani et al. 9 teUnreservedBandwidthPri6 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 6" ::= {ospfTeLsdbEntry 13teTEDEntry 16 }ospfTeUnreservedBandwidthPri7teUnreservedBandwidthPri7 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the amount of bandwidth not yet reserved at the priority 7" ::= {ospfTeLsdbEntry 14teTEDEntry 17 }ospfTeAdministrativeGroupteAdministrativeGroup OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the Administrative Group which the link belong to. Since the value is a bit mask, the link can belong to multiple groups. This is also called Resource Class/Color." ::= {ospfTeLsdbEntry 15teTEDEntry 18 }ospfTeLocalIdteLocalId OBJECT-TYPE SYNTAXUnsigned32Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates the Link local identifier of an unnumbered link." ::= {ospfTeLsdbEntry 16teTEDEntry 19 }ospfTeRemoteIdteRemoteId OBJECT-TYPE SYNTAXUnsigned32Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION " This indicates the Link remote identifier of an unnumbered link." ::= {ospfTeLsdbEntry 17teTEDEntry 20 }ospfTeLinkProtectionTypeteLinkProtectionType OBJECT-TYPE SYNTAXINTEGERBITS { extraTraffic(0), unprotected(1),T. Otani et al. 9shared (2), dedicatedOneToOne (3), T. Otani et al. 10 dedicatedOnePlusOne(4), enhanced(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "This objectindicatesindicates the protection type of the TE link" ::= { teTEDEntry 21 } 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 theprotection typeidentifier of theTE link"corresponding row entry a local proprietary MIB module, or otherwise SHOULD contain the value of zeroDotZero." ::= {ospfTeLsdbEntry 18teTEDEntry 22 } -- --OSPF TETED Local Interface IP Address Table --ospfTeLocalIntAddrTableteLocalIntAddrTable OBJECT-TYPE SYNTAX SEQUENCE OFOspfTeLocalIntAddrEntryTeLocalIntAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the IP address information of a local TE link." ::= {ospfTeTablesteTables 2 }ospfTeLocalIntAddrEntryteLocalIntAddrEntry OBJECT-TYPE SYNTAXOspfTeLocalIntAddrEntryTeLocalIntAddrEntry T. Otani et al. 11 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry contains the IP address information of the local TE link." INDEX { ospfAreaId, ospfLsdbLsid,ospflsdbRouterId, ospfTeLocalIntAddrIndexospfLsdbRouterId, teLocalIntAddrIndex } ::= {ospfTeLocalIntAddrTableteLocalIntAddrTable 1 }OspfTeLocalIntAddrEntryTeLocalIntAddrEntry ::= SEQUENCE {ospfTeLocalIntAddrIndexteLocalIntAddrIndex Unsigned32,ospfTeLocalIntAddr InetAddress, ospfTeLocalIntAddrType InetAddressTypeteLocalIntAddr IpAddress, }ospfTeLocalIntAddrIndexteLocalIntAddrIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This indicates the index to identify multiple local TE links" ::= {ospfTeLocalIntAddrEntryteLocalIntAddrEntry 1 }ospfTeLocalIntAddrteLocalIntAddr OBJECT-TYPE SYNTAXInetAddressIpAddress MAX-ACCESS read-only STATUS current DESCRIPTIONT. Otani et al. 10"This object indicates the address of the local TE link." ::= {ospfTeLocalIntAddrEntryteLocalIntAddrEntry 2 }ospfTeLocalIntAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the type of local TE link address." ::= { ospfTeLocalIntAddrEntry 3 }-- --OSPF TETED Remote Interface IP Address Table --ospfTeRemoteIntAddrTableteRemoteIntAddrTable OBJECT-TYPE SYNTAX SEQUENCE OFOspfTeRemoteIntAddrEntryTeRemoteIntAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the IP address information of a remote TE link." ::= {ospfTeTablesteTables 3 }ospfTeRemoteIntAddrEntryteRemoteIntAddrEntry OBJECT-TYPE SYNTAXOspfTeRemoteIntAddrEntryTeRemoteIntAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry contains the IP address information of the remote TE link." INDEX { ospfAreaId, ospfLsdbLsid, ospflsdbRouterId,ospfTeRemoteIntAddrIndexteRemoteIntAddrIndex } ::= {ospfTeRemoteIntAddrTableteRemoteIntAddrTable 1 }OspfTeRemoteIntAddrEntryT. Otani et al. 12 TeRemoteIntAddrEntry ::= SEQUENCE {ospfTeRemoteIntAddrIndexteRemoteIntAddrIndex Unsigned32,ospfTeRemoteIntAddr InetAddress, ospfTeRemoteIntAddrType InetAddressTypeteRemoteIntAddr IpAddress, }ospfTeRemoteIntAddrIndexteRemoteIntAddrIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This indicates the index to identify multiple remote TE links." ::= {ospfTeRemoteIntAddrEntryteRemoteIntAddrEntry 1 }ospfTeRemoteIntAddrteRemoteIntAddr OBJECT-TYPE SYNTAXInetAddressIpAddress MAX-ACCESS read-only STATUS currentT. Otani et al. 11DESCRIPTION "This object indicates the address of the remote TE link." ::= {ospfTeRemoteIntAddrEntryteRemoteIntAddrEntry 2 }ospfTeRemoteIntAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the type of the remote TE link address." ::= { ospfTeRemoteIntAddrEntry 3 }-- --OSPF TETED Switch Capable Table --ospfTeSwCapTableteSwCapTable OBJECT-TYPE SYNTAX SEQUENCE OFOspfTeSwCapEntryTeSwCapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the GMPLSOSPF TETED switching capability information." ::= {ospfTeTablesteTables 4 }ospfTeSwCapEntryteSwCapEntry OBJECT-TYPE SYNTAXOspfTeSwCapEntryTeSwCapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry relates each TE link with its GMPLS TE switching capability information. IF the MIB deals with only OSPF-TE information, the value of each object related with GMPLS TE extensions should be null." INDEX { ospfAreaId, ospfLsdbLsid,ospflsdbRouterId, ospfTeSwCapIndexospfLsdbRouterId, teSwCapIndex } ::= {ospfTeSwCapTableteSwCapTable 1 }OspfTeSwCapEntryTeSwCapEntry ::= SEQUENCE {ospfTeSwCapIndexteSwCapIndex Unsigned32,ospfTeSwitchingTypeteSwitchingType INTEGER,ospfTeEncodingteEncoding INTEGER,ospfTeMaxLspBandwidthPri0 Unsigned32, ospfTeMaxLspBandwidthPri1 Unsigned32, ospfTeMaxLspBandwidthPri2 Unsigned32, ospfTeMaxLspBandwidthPri3 Unsigned32, ospfTeMaxLspBandwidthPri4 Unsigned32, ospfTeMaxLspBandwidthPri5 Unsigned32, ospfTeMaxLspBandwidthPri6 Unsigned32, ospfTeMaxLspBandwidthPri7 Unsigned32, ospfTeMinLspBandwidth Unsigned32, ospfTeIntMtu Integer32, ospfTeIndication INTEGERT. Otani et al.1213 teMaxLspBandwidthPri0 OCTET STRING, teMaxLspBandwidthPri1 OCTET STRING, teMaxLspBandwidthPri2 OCTET STRING, teMaxLspBandwidthPri3 OCTET STRING, teMaxLspBandwidthPri4 OCTET STRING, teMaxLspBandwidthPri5 OCTET STRING, teMaxLspBandwidthPri6 OCTET STRING, teMaxLspBandwidthPri7 OCTET STRING, teMinLspBandwidth OCTET STRING, teIntMtu Integer32, teIndication INTEGER }ospfTeSwCapIndexteSwCapIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is utilized to identify multiple switching functions on a local or remote TE link." ::= {ospfTeSwCapEntryteSwCapEntry 1 }ospfTeSwitchingTypeteSwitchingType OBJECT-TYPE SYNTAX INTEGER { unknown (0), psc1 (1), psc2 (2), psc3 (3), psc4 (4), l2sc (51), tdm (100), lsc (150), fsc (200) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the GMPLS switching capability assigned to the TE link." ::= {ospfTeSwCapEntryteSwCapEntry 2 }ospfTeEncodingteEncoding OBJECT-TYPE SYNTAX INTEGER { packet (1), ethernet (2), ansiEtsiPdh (3), sdhSonet (5), digitalWrapper (7), lambda (8), fiber (9), fiberChannel (11) } MAX-ACCESS read-only STATUS current T. Otani et al. 14 DESCRIPTION "This object indicates the GMPLS encoding type assigned to the TE link." ::= {ospfTeSwCapEntryteSwCapEntry 3 }ospfTeMaxLspBandwidthPri0teMaxLspBandwidthPri0 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTIONT. Otani et al. 13"This object indicates the maximum bandwidth of the TE link at the priority 0 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 4 }ospfTeMaxLspBandwidthPri1teMaxLspBandwidthPri1 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 1 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 5 }ospfTeMaxLspBandwidthPri2teMaxLspBandwidthPri2 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 2 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 6 }ospfTeMaxLspBandwidthPri3teMaxLspBandwidthPri3 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 3 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 7 }ospfTeMaxLspBandwidthPri4teMaxLspBandwidthPri4 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 4 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 8 }ospfTeMaxLspBandwidthPri5T. Otani et al. 15 teMaxLspBandwidthPri5 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 5 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 9 }ospfTeMaxLspBandwidthPri6teMaxLspBandwidthPri6 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTIONT. Otani et al. 14"This object indicates the maximum bandwidth of the TE link at the priority 6 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 10 }ospfTeMaxLspBandwidthPri7teMaxLspBandwidthPri7 OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 7 for GMPLS LSP creation." ::= {ospfTeSwCapEntryteSwCapEntry 11 }ospfTeLspMinBandwidthteMinLspBandwidth OBJECT-TYPE SYNTAXUnsigned32OCTET STRING (SIZE (4)) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the minimum bandwidth of the TE link for GMPLS LSP creation if the switching capability field is TDM, PSC- 1, PSC-2, PSC-3, or PSC-4." ::= {ospfTeSwCapEntryteSwCapEntry 12 }ospfTeIntMtuteIntMtu OBJECT-TYPE SYNTAX Integer32 MAX-ACCESSread-writeread-only STATUS current DESCRIPTION "This object indicates the MTU of the local or remote TE link" ::= {ospfTeSwCapEntryteSwCapEntry 13 }ospfTeIndicationteIndication OBJECT-TYPE SYNTAX INTEGER { T. Otani et al. 16 standard (0), arbitrary (1) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether the interface supports Standard or Arbitrary SONET/SDH." ::= {ospfTeSwCapEntryteSwCapEntry 14 } -- --OSPF TETED SRLG Table --ospfTeSrlgTableteSrlgTable OBJECT-TYPE SYNTAX SEQUENCE OFOspfTeSrlgEntryTeSrlgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the SRLG information of the TE link."T. Otani et al. 15::= {ospfTeTablesteTables 5 }ospfTeSrlgEntryteSrlgEntry OBJECT-TYPE SYNTAXOspfTeSrlgEntryTeSrlgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This entry relates each TE link with its SRLG information." INDEX { ospfAreaId, ospfLsdbLsid,ospflsdbRouterId, ospfTeSrlgIndexospfLsdbRouterId, teSrlgIndex } ::= {ospfTeSrlgTableteSrlgTable 1 }OspfTeSrlgEntryTeSrlgEntry ::= SEQUENCE {ospfTeSrlgIndexteSrlgIndex Unsigned32ospfTeSrlgteSrlg Integer32 }ospfTeSrlgIndexteSrlgIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is utilized to identify multiple SRLG values on a local or remote TE link." ::= {ospfTeLsdbEntryteSrlgTableEntry 1 }ospfTeSrlgteSrlg OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicate the SRLG value assigned to a local or remote TE link" ::= {ospfTeSrlgEntryteSrlgEntry 2 } T. Otani et al. 17 -- Conformance StatementospfTeGroupsteGroups OBJECT IDENTIFIER ::= {ospfTeConformanceteConformance 1 }ospfTeCompliancesteCompliances OBJECT IDENTIFIER ::= {ospfTeConformanceteConformance 2 } -- Module ComplianceospfTeModuleFullComplianceteModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents provides full support for theOSPF-TETED MIB" MODULE -- this module MANDATORY-GROUPS {ospfTeMainGroupteMainGroup } ::= {ospfTeCompliancesteCompliances 1 }T. Otani et al. 16-- -- ReadOnly Compliance --ospfTeModuleReadOnlyComplianceteModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations only provide read-only support forOSPF-TE.TED. Such devices can then be monitored but cannot be configured using this MIB module. " MODULE -- this module MANDATORY-GROUPS {ospfTeMainGroupteMainGroup } ::= {ospfTeCompliancesteCompliances 2 } -- Units of conformance.ospfTeMainGroupteMainGroup OBJECT-GROUP OBJECTS {ospfTeLinkType , ospfTeLinkIdAddr , ospfTeLinkIdAddrTypeteLinkInformationSource ,ospfTeMetricteLinkType ,ospfTeMaxBandwidthteLinkIdAddr ,ospfTeMaxReservableBandwidthteMetric ,ospfTeUnreservedBandwidthPri0teMaxBandwidth ,ospfTeUnreservedBandwidthPri1teMaxReservableBandwidth ,ospfTeUnreservedBandwidthPri2teUnreservedBandwidthPri0 ,ospfTeUnreservedBandwidthPri3teUnreservedBandwidthPri1 ,ospfTeUnreservedBandwidthPri4teUnreservedBandwidthPri2 ,ospfTeUnreservedBandwidthPri5teUnreservedBandwidthPri3 ,ospfTeUnreservedBandwidthPri6teUnreservedBandwidthPri4 ,ospfTeUnreservedBandwidthPri7teUnreservedBandwidthPri5 ,ospfTeAdministrativeGroupteUnreservedBandwidthPri6 ,ospfTeLocalId , ospfTeRemoteId , ospfTeLinkProtectionTypeT. Otani et al. 18 teUnreservedBandwidthPri7 ,ospfTeLocalIntAddrIndexteAdministrativeGroup ,ospfTeLocalIntAddrteLocalId ,ospfTeLocalIntAddrTypeteRemoteId ,ospfTeRemoteIntAddrIndexteLinkProtectionType ,ospfTeRemoteIntAddrteLinkInformationData ,ospfTeRemoteIntAddrTypeteLocalIntAddr ,ospfTeSwCapIndexteRemoteIntAddr ,ospfTeSwitchingTypeteSwitchingType ,ospfTeEncodingteEncoding ,ospfTeMaxLspBandwidthPri0teMaxLspBandwidthPri0 ,ospfTeMaxLspBandwidthPri1teMaxLspBandwidthPri1 ,ospfTeMaxLspBandwidthPri2teMaxLspBandwidthPri2 ,ospfTeMaxLspBandwidthPri3teMaxLspBandwidthPri3 ,ospfTeMaxLspBandwidthPri4teMaxLspBandwidthPri4 ,ospfTeMaxLspBandwidthPri5teMaxLspBandwidthPri5 ,T. Otani et al. 17 ospfTeMaxLspBandwidthPri6teMaxLspBandwidthPri6 ,ospfTeMaxLspBandwidthPri7teMaxLspBandwidthPri7 ,ospfTeIntMtuteMinLspBandwidth ,ospfTeIndicationteIntMtu ,ospfTeSrlgIndexteIndication ,ospfTeSrlgteSrlg } STATUS current DESCRIPTION "Collection of objects forOSPF-TETED management" ::= {ospfTeGroupsteGroups 1 } END 6. Security consideration This document introduces no new security issues beyond those detailed in the OSPF MIB. 7. IANA Considerations The following "IANA Considerations" subsection requests IANA for a new assignment under the transmission subtree. New assignments can only be made via a Standards Action as specified in [RFC2434]. 7.1 IANA Considerations forOSPF-TE-STD-MIBTED-STD-MIB The IANA is requested to assign {ospfTeMIBteMIB XXX } to theOSPF-TE-STD- MIBTED-STD-MIB module specified in this document. 8. References 8.1 Normative References 8.2 Informative References T. Otani et al. 19 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [OSPFMIB] F. Baker, et al, "OSPF Version 2 Management Information Base", RFC1850,Nov.,Nov. 1995. [OSPFMIB UPDATE]Dan Joyal, et al, "OSPF Version 2 Management Information Base",draft-ietf-ospf-mib-update- 08.txt,Decemberdraft-ietf-ospf-mib-update-08.txt, December 2003. [ISISMIB] J. Parker, et al, "Management Information Base for Intermediate System to Intermediate System (IS-IS)”, RFC 4444, April 2006. [GMPLSRouting] K. Kompella, and Y. Rekhter, "Routing Extensions in Support of Generalized Multi-Protocol Label Switching",draft-ietf-ccamp-gmpls-routing-09.txt, October 2003. T. Otani et al. 18RFC4202, Oct. 2005. [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions to OSPF Version2", RFC3630, September 2003. [GMPLSisis] K. Kompella, and Y. Rekhter, "Intermediate System to Intermediate System (IS-IS) Extensions in Support of Multi-Protocol Label Switching (GMPLS)", RFC4205, Oct. 2005. [RFC3784] H. Smit and T. Li, "IS-IS extensions for Traffic Engineering”, RFC 3784, June 2004. [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, June 2004. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching (LSR) Router Management Information Base (MIB)", RFC 3813, June 2004. [GMPLSLSRMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", draft-ietf-ccamp-gmpls- lsr-mib-08.txt, June 2005. [GMPLSTEMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base", draft-ietf-ccamp-gmpls- te-mib-09.txt, June 2005. [MPLS OAM] T. Nadeau, Allan D., et al., "OAM Requirements for MPLS Network" draft-ietf-mpls-oam-requirements-05.txt, June 2005. T. Otani et al. 20 [RFC3945] E. Mannie, "Generalized Multi-Protocol Label Switching Architecture", RFC3945, October, 2004. [GMPLSOSPF] K. Kompella, and Y. Rekhter, "OSPF Extensions in Support of Generalized Multi-Protocol Label Switching",draft-ietf-ccamp-ospf-gmpls-extensions- 12.txt, October 2003.RFC4203, Oct. 2005. [OSPF-TE] Katz, D., et al, "Traffic Engineering (TE) Extensions to OSPF Version 2", RFC3630, September 2003. [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an IANA Considerations Section in RFCs" BCP 26, RFC 2434, October 1998. 9. Acknowledgment The authors wish to acknowledge and thank the following individuals for their valuable comments to this document: KenNagami andNagami, ShuichiOkamoto.Okamoto and Adrian Farrel. 10.Author’sAuthor's Address Tomohiro Otani KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino Phone: +81-49-278-7357 Saitama, 356-8502. Japan Email: otani@kddilabs.jpT. Otani et al. 19Masanori Miyazawa KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino Phone: +81-49-278-7559 Saitama, 356-8502. Japan Email: ma-miyazawa@kddilabs.jp Thomas D. Nadeau Cisco Systems, Inc. 300 Beaver Brook Road Phone: +1-978-936-1470 Boxboro, MA 01719 Email: tnadeau@cisco.com300 Kenji Kumaki KDDI Corporation GARDEN AIR TOWER,3-10-10,Iidabshi Phone: +81-3-6678-3103 Chiyoda-ku,Tokyo, 102-8460. Japan Email: ke-kumaki@kddi.com 11. Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in 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 made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. T. Otani et al. 21 Copies of IPR disclosures made to the IETF Secretariat and any 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 such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. 12. Copyright Statement "Copyright (C) The Internet Society (2006). This document is subject to the 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 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OFT. Otani et al. 20THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." T. Otani et al.2122