idnits 2.17.1 draft-ietf-ccamp-gmpls-ted-mib-14.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 4, 2012) is 4220 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2328' is defined on line 1552, but no explicit reference was found in the text == Unused Reference: 'RFC4001' is defined on line 1566, but no explicit reference was found in the text == Unused Reference: 'RFC4801' is defined on line 1579, but no explicit reference was found in the text == Unused Reference: 'RFC5340' is defined on line 1587, but no explicit reference was found in the text == Unused Reference: 'RFC6340' is defined on line 1593, but no explicit reference was found in the text == Unused Reference: 'ISO10589' is defined on line 1596, but no explicit reference was found in the text == Unused Reference: 'RFC4220' is defined on line 1625, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO10589' -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Masanori Miyazawa 3 Intended status: Proposed Standard KDDI R&D Labs 4 Expires: March 4, 2013 5 Tomohiro Otani 6 Kenji Kumaki 7 KDDI Corporation 9 Thomas D. Nadeau 11 October 4, 2012 13 Traffic Engineering Database Management Information Base in support of 14 MPLS-TE/GMPLS 16 draft-ietf-ccamp-gmpls-ted-mib-14.txt 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with 21 the provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that other 25 groups may also distribute working documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Copyright Notice 39 Copyright (c) 2012 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Abstract 53 This memo defines the Management Information Base (MIB) objects in 54 order to manage traffic engineering database (TED) information with 55 extension in support of Multi-Protocol Label Switching (MPLS) with 56 traffic engineering (TE) as well as Generalized MPLS (GMPLS) for use 57 with network management protocols. 59 Table of Contents 61 Status of this Memo................................................... 1 62 Abstract.............................................................. 2 63 1. The Internet-Standard Management Framework......................... 3 64 2. Introduction....................................................... 3 65 3. Overview........................................................... 3 66 3.1 Conventions used in this document................................. 3 67 3.2 Terminology....................................................... 3 68 3.3 Acronyms.......................................................... 4 69 4. Motivations........................................................ 4 70 5. Brief Description of MIB Modules................................... 4 71 5.1 tedTable.......................................................... 4 72 5.2 tedLocalIfAddrTable............................................... 4 73 5.3 tedRemoteIfAddrTable.............................................. 4 74 5.4 tedSwCapTable..................................................... 4 75 5.5 tedSrlgTable...................................................... 5 76 6. Example of the TED MIB Module Usage................................ 5 77 7. TED MIB Module Definitions in support of GMPLS..................... 6 78 8. Security Consideration............................................ 29 79 9. IANA Considerations............................................... 30 80 9.1 IANA Considerations for TED-MIB.................................. 30 81 10. References....................................................... 30 82 10.1 Normative References............................................ 30 83 10.2 Informative References.......................................... 30 84 11. Acknowledgment................................................... 32 85 12. Authors' Addresses............................................... 32 86 1. The Internet-Standard Management Framework 88 For a detailed overview of the documents that describe the current 89 Internet-Standard Management Framework, please refer to section 7 of 90 RFC 3410 [RFC3410]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. MIB objects are generally 94 accessed through the Simple Network Management Protocol (SNMP). 95 Objects in the MIB are defined using the mechanisms defined in the 96 Structure of Management Information (SMI). This memo specifies a MIB 97 module that is compliant to the SMIv2, which is described in STD 58, 98 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 99 [RFC2580]. 101 2. Introduction 103 The OSPF MIB was originally defined for OSPF version2 in support of 104 IPv4 [RFC4750] and extended to support the Internet Protocol 105 version6(IPv6) as OSPF version3 MIB [RFC5643]. The ISIS MIB is also 106 defined as [RFC4444]. On the other side, MPLS/GMPLS based traffic 107 engineering has so far extended OSPF/ISIS routing protocol with TE 108 functionality [RFC4202], [RFC3630], [RFC5329], [RFC5307], [RFC5305]. 109 To manage such MPLS-TE/GMPLS networks effectively, routing 110 information associated with MPLS/GMPLS TE parameters (TED) is 111 preferred for the network management, however, there is no clear 112 definition of MPLS/GMPLS TE information in existing MIBs related to 113 OSPF(v2 and v3)/ISIS. 115 This memo defines the Management Information Base (MIB) objects for 116 managing TED in support of MPLS-TE/GMPLS for use with network 117 management protocols. 119 This MIB module should be used in conjunction with OSPFv2 MIB, OSPF 120 v3 MIB and ISIS MIB as well as other MIBs defined in [RFC3812], 121 [RFC3813], [RFC4802], [RFC4803] for the management of MPLS/GMPLS 122 based traffic engineering information. 124 3. Overview 126 3.1 Conventions used in this document 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 130 "OPTIONAL" in this document are to be interpreted as described in 131 RFC-2119 [RFC2119]. 133 3.2 Terminology 135 Definitions of key terms for MPLS OAM and GMPLS are found in 136 [RFC4377] and [RFC3945], and the reader is assumed to be familiar 137 with those definitions which are not repeated here. 139 3.3 Acronyms 141 GMPLS: Generalized Multi-Protocol Label Switching 142 ISIS: Intermediate System to Intermediate System 143 LSA: Link state advertisement 144 LSP: Label Switching Path 145 LSR: Label Switching Router 146 MIB: Management Information Base 147 OSPF: Open Shortest Path First 148 PSC: Packet switch capable 149 SRLG: Shared risk link group 150 TE: Traffic Engineering 151 TED: Traffic Engineering Database 152 TDM: Time Division Multiplexing 154 4. Motivations 156 The existing OSPFv2, OSPFv3, ISIS, MPLS and GMPLS MIBs do not provide 157 for the management interface to retrieve topology information of MPLS 158 and GMPLS networks. 160 5. Brief Description of MIB Modules 162 The objects described in this section support the management of TED 163 described in [RFC4202], [RFC4203] and [RFC5307] for GMPLS extensions 164 as well as in [RFC3630] and [RFC5305] for MPLS/GMPLS. 166 5.1 tedTable 168 The tedTable is basically used to indicate TED information of OSPF-TE 169 or ISIS-TE. However, this table does not contain information for 170 Local/Remote interface IP address, Interface Switching Capability 171 Descriptor and Shared Risk Link Group information within the sub-TLVs 172 for the Link-TLV. 174 5.2 tedLocalIfAddrTable 176 The tedLocalIfAddrTable is identical to the Local interface IP 177 address information in a sub-TLV for the Link-TLV. This is 178 independently defined, because the Interface IP Address sub-TLV may 179 appear more than once within the same Link-TLV. 181 5.3 tedRemoteIfAddrTable 183 The tedRemoteIfAddrTable is identical to the Remote interface IP 184 address information in a sub-TLV of the Link-TLV. Also, this is 185 utilized independently because one or more local interface IP address 186 sub TLVs may exist in the same Link-TLV. 188 5.4 tedSwCapTable 189 The tedSwCapTable represents Interface Switching Capability 190 Descriptor information. This is independently defined due to the 191 possibility of multiple appearances of the sub TLV within the same 192 Link-TLV. 194 5.5 tedSrlgTable 196 The tedSrlgTable contains the Sub-TLV information of Shared Risk Link 197 Group (SRLG) information. This is separately defined, because more 198 than one sub TLVs may appear in the same Link-TLV. 200 6.Example of the TED MIB Module Usage 202 In this section, we provide an example of the TED MIB module usage. 203 The following indicates the information of a numbered TE link 204 originated in a GMPLS controlled node. When TE link information is 205 retrieved in a MPLS network, GMPLS specific objects such as 206 tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable and 207 tedSrlgTable are not supported. 209 Note that the TED MIB modules are only limited to "read-only" access 210 except for tedCreatedDeletedNotificationMaxRate and 211 tedStatusChangeNotificationMaxRate. The TED MIB module is designed to 212 be independent of OSPF or ISIS MIBs, however each TE link information 213 belongs to a node or a link which is managed by the routing protocol. 215 In tedTable: 216 { 217 tedLinkInformationData.2.3232235777.3232235778.16777264 zeroDotZero 218 tedLinkType.2.3232235777.3232235778.16777264 pointToPoint(1) 219 tedLinkState.2.3232235777.3232235778.16777264 up(1) 220 tedAreaId.2.3232235777.3232235778.16777264 0 221 tedTeRouterIdAddrType.2.3232235777.3232235778.16777264 ipv4(1) 222 tedTeRouterIdAddr.2.3232235777.3232235778.16777264 192.0.2.1 223 tedLinkIdAddrType.2.3232235777.3232235778.16777264 ipv4(1) 224 tedLinkIdAddr.2.3232235777.3232235778.16777264 192.0.2.10 225 tedMetric.2.3232235777.3232235778.16777264 1 226 tedMaxBandwidth.2.3232235777.3232235778.16777264 4d9450c0 227 tedMaxReservableBandwidth.2.3232235777.3232235778.16777264 4d9450c0 228 tedUnreservedBandwidthPri0.2.3232235777.3232235778.16777264 4d9450c0 229 tedUnreservedBandwidthPri1.2.3232235777.3232235778.16777264 4d9450c0 230 tedUnreservedBandwidthPri2.2.3232235777.3232235778.16777264 4d9450c0 231 tedUnreservedBandwidthPri3.2.3232235777.3232235778.16777264 4d9450c0 232 tedUnreservedBandwidthPri4.2.3232235777.3232235778.16777264 4d9450c0 233 tedUnreservedBandwidthPri5.2.3232235777.3232235778.16777264 4d9450c0 234 tedUnreservedBandwidthPri6.2.3232235777.3232235778.16777264 4d9450c0 235 tedUnreservedBandwidthPri7.2.3232235777.3232235778.16777264 4d9450c0 236 tedAdministrativeGroup.2.3232235777.3232235778.16777264 0 237 tedLocalId.2.3232235777.3232235778.16777264 0 238 tedRemoteId.2.3232235777.3232235778.16777264 0 239 tedLinkProtectionType.2.3232235777.3232235778.16777264 01 00 00 00 7 240 } 241 In tedLocalIfAddrTable: 242 { 243 tedLocalIfAddrType.16777264.192.0.2.21 ipv4(1) 244 } 246 In tedRemoteIfAddrTable: 247 { 248 tedRemoteIfAddrType.16777264.192.0.2.22 ipv4(1) 249 } 251 In tedSwCapTable: 252 { 253 tedSwCapType.16777264.1 lsc(150) 254 tedSwCapEncoding.16777264.1 ethernet(2) 255 tedSwCapMaxLspBandwidthPri0.16777264.1 4d9450c0 256 tedSwCapMaxLspBandwidthPri1.16777264.1 4d9450c0 257 tedSwCapMaxLspBandwidthPri2.16777264.1 4d9450c0 258 tedSwCapMaxLspBandwidthPri3.16777264.1 4d9450c0 259 tedSwCapMaxLspBandwidthPri4.16777264.1 4d9450c0 260 tedSwCapMaxLspBandwidthPri5.16777264.1 4d9450c0 261 tedSwCapMaxLspBandwidthPri6.16777264.1 4d9450c0 262 tedSwCapMaxLspBandwidthPri7.16777264.1 4d9450c0 263 tedSwCapMinLspBandwidth.16777264.1 0 264 tedSwCapIfMtu.16777264.1 0 265 tedSwCapIndication.16777264.1 standard(0) 266 } 268 In tedSrlgTable: 269 { 270 tedSrlg.16777264.1 0 271 } 273 7. TED MIB Definitions in support of GMPLS 275 TED-MIB DEFINITIONS ::= BEGIN 277 IMPORTS 278 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission, 279 NOTIFICATION-TYPE 280 FROM SNMPv2-SMI -- RFC2578 281 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 282 FROM SNMPv2-CONF -- RFC2580 283 TEXTUAL-CONVENTION, RowPointer 284 FROM SNMPv2-TC -- RFC2579 285 IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC 286 FROM IANA-GMPLS-TC-MIB -- RFC4802 287 InetAddress, InetAddressType 288 FROM INET-ADDRESS-MIB -- RFC4001 289 Float32TC 290 FROM FLOAT-TC-MIB -- RFC6340 291 ; 293 tedMIB MODULE-IDENTITY 294 LAST-UPDATED "201210040000Z" -- 4 Oct. 2012 00:00:00 GMT 295 ORGANIZATION "IETF CCAMP Working Group." 296 CONTACT-INFO 297 " Tomohiro Otani 298 otani@kddilabs.jp 300 Masanori Miyazawa 301 ma-miyazawa@kddilabs.jp 303 Thomas D. Nadeau 304 tnadeau@lucidvision.com 306 Kenji Kumaki 307 ke-kumaki@kddilabs.jp 309 Comments and discussion to ccamp@ietf.org" 310 DESCRIPTION 311 "This MIB module contains managed object definitions for TED 312 in support of MPLS/GMPLS TE Database. 314 Copyright (C) 2012 The IETF Trust. This version of this MIB 315 module is part of RFC xxx; see the RFC itself for full legal 316 notices." 317 -- Revision history. 318 REVISION 319 "201210040000Z" -- 4 Oct. 2012 00:00:00 GMT 320 DESCRIPTION 321 "Initial version. Published as RFC xxx." 322 -- RFC-editor pls fill in yyy 323 ::= { transmission yyy } 324 -- assigned by IANA, see section 9.1 for details 326 -- Textual Conventions. 328 TedAreaIdTC ::= TEXTUAL-CONVENTION 329 STATUS current 330 DESCRIPTION 331 "The area identifier of the IGP. If OSPF is used to 332 advertise LSA, this represents an ospfArea. If ISIS is used, this 333 represents an area address." 334 SYNTAX OCTET STRING (SIZE (0..20)) 336 TedRouterIdTC ::= TEXTUAL-CONVENTION 337 STATUS current 338 DESCRIPTION 339 " The router identifier. If OSPF is used to advertise LSA, 340 this represents a Router ID. If ISIS is used, this represents a 341 System ID." 342 SYNTAX OCTET STRING (SIZE (0..6)) 344 TedLinkIndexTC ::= TEXTUAL-CONVENTION 345 STATUS current 346 DESCRIPTION 347 " The link identifier. If OSPF is used, this represents an 348 ospfLsdbID. If ISIS is used, this represents an isisLSPID. If a 349 locally configured link is used, this object represents an arbitrary 350 value which is locally defined in a router" 351 SYNTAX OCTET STRING (SIZE (0..8)) 353 -- Top level components of this MIB module. 355 tedNotifications OBJECT IDENTIFIER ::= { tedMIB 0 } 356 tedObjects OBJECT IDENTIFIER ::= { tedMIB 1 } 357 tedConformance OBJECT IDENTIFIER ::= { tedMIB 2 } 359 -- 361 -- TED Table 362 -- 364 tedTable OBJECT-TYPE 365 SYNTAX SEQUENCE OF TedEntry 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "This table indicates multiple TED information which has been 370 supported by RFC3630 and RFC5305." 371 ::= { tedObjects 1 } 373 tedEntry OBJECT-TYPE 374 SYNTAX TedEntry 375 MAX-ACCESS not-accessible 376 STATUS current 377 DESCRIPTION 378 "This entry contains TED information commonly utilized in both 379 MPLS and GMPLS." 380 INDEX { tedLocalRouterId, tedRemoteRouterId, 381 tedLinkInformationSource, tedLinkIndex } 382 ::= { tedTable 1 } 384 TedEntry ::= SEQUENCE { 385 tedLinkInformationSource INTEGER, 386 tedLocalRouterId TedRouterIdTC, 387 tedRemoteRouterId TedRouterIdTC, 388 tedLinkIndex TedLinkIndexTC, 389 tedLinkInformationData RowPointer, 390 tedLinkState INTEGER, 391 tedAreaId TedAreaIdTC, 392 tedLinkType INTEGER, 393 tedTeRouterIdAddrType InetAddressType, 394 tedTeRouterIdAddr InetAddress, 395 tedLinkIdAddrType InetAddressType, 396 tedLinkIdAddr InetAddress, 397 tedMetric Integer32, 398 tedMaxBandwidth Float32TC, 399 tedMaxReservableBandwidth Float32TC, 400 tedUnreservedBandwidthPri0 Float32TC, 401 tedUnreservedBandwidthPri1 Float32TC, 402 tedUnreservedBandwidthPri2 Float32TC, 403 tedUnreservedBandwidthPri3 Float32TC, 404 tedUnreservedBandwidthPri4 Float32TC, 405 tedUnreservedBandwidthPri5 Float32TC, 406 tedUnreservedBandwidthPri6 Float32TC, 407 tedUnreservedBandwidthPri7 Float32TC, 408 tedAdministrativeGroup Integer32, 409 tedLocalId Integer32, 410 tedRemoteId Integer32, 411 tedLinkProtectionType BITS 412 } 414 tedLinkInformationSource OBJECT-TYPE 415 SYNTAX INTEGER { 416 unknown(0), 417 locallyConfigured(1), 418 ospfv2(2), 419 ospfv3(3), 420 isis(4), 421 other(5) 422 } 423 MAX-ACCESS not-accessible 424 STATUS current 425 DESCRIPTION 426 "This object indicates the source of the information about the 427 TE link." 428 ::= { tedEntry 1 } 430 tedLocalRouterId OBJECT-TYPE 431 SYNTAX TedRouterIdTC 432 MAX-ACCESS not-accessible 433 STATUS current 434 DESCRIPTION 435 "This object represents the router ID of the router originating 436 the LSA. If OSPF is used to advertise LSA, this represents a Router 437 ID. If ISIS is used, this represents a System ID. Otherwise, this 438 represents zero." 439 REFERENCE 440 " OSPF Version 2, RFC2328, C.1 441 OSPF for IPv6, RFC5340, C.1 442 ISO10589, Section 7.1 " 443 ::= { tedEntry 2 } 445 tedRemoteRouterId OBJECT-TYPE 446 SYNTAX TedRouterIdTC 447 MAX-ACCESS not-accessible 448 STATUS current 449 DESCRIPTION 450 "This object indicates the router at the remote end of the link 451 from the originating router. If OSPF is used to advertise LSA, this 452 represents a Link ID in the Link TLV. If ISIS is used, this 453 represents a neighbor system ID defined in RFC5305. Otherwise, this 454 represents zero." 455 REFERENCE 456 " OSPF Version 2, RFC2328, C.1 457 OSPF for IPv6, RFC5340, C.1 458 ISO10589, Section 7.1" 459 ::= { tedEntry 3 } 461 tedLinkIndex OBJECT-TYPE 462 SYNTAX TedLinkIndexTC 463 MAX-ACCESS not-accessible 464 STATUS current 465 DESCRIPTION 466 "This object indicates the link state identifier. If OSPF is 467 used, this represents an ospfLsdbID. If ISIS is used, this represents 468 an isisLSPID. Otherwise, this represents a unique identifier within a 469 node." 470 REFERENCE 471 "OSPF Version 2, RFC2328, A.4.1, 472 OSPF for IPv6, RFC5340, A.4.2 473 ISO10589, Section 9.8 " 474 ::= { tedEntry 4 } 476 tedLinkInformationData OBJECT-TYPE 477 SYNTAX RowPointer 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION 481 " If tedLinkInformationSource has the value unknown(0), this 482 object MUST contain a value of zeroDotZero. 483 If tedLinkInformationSource has the value 484 locallyConfigured(1), an implementation can use this object to 485 supply the identifier of the corresponding row entry in the 486 teLinkTable of TE-LINK-STD-MIB (RFC 4220), the identifier of the 487 corresponding row in a local proprietary TE link MIB module, or 488 the value of zeroDotZero. 489 If tedLinkInformationSource has the value ospfv2(2)and 490 ospfv3(3), an implementation can use this object to supply the 491 identifier of the corresponding row entry in the 492 ospfLocalLsdbTable (OSPFv2-MIB) and the ospfv3AreaLsdbTable 493 (OSPFv3-MIB), or the value of zeroDotZero. 494 If tedLinkInformationSource has the value isis(4), an 495 implementation can use this object to supply the identifier of 496 the corresponding row entry in the isisAreaAddr of ISIS-MIB 497 (RFC4444), or the value of zeroDotZero. 498 If tedLinkInformationSource has the value other(5), an 499 implementation can use this object to supply the identifier of 500 the corresponding row entry in the local proprietary MIB module, 501 or the value of zeroDotZero." 502 ::= { tedEntry 5 } 504 tedLinkState OBJECT-TYPE 505 SYNTAX INTEGER { 506 unknown (0), 507 up (1), 508 down (2) 509 } 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 " This object represents the actual operational state of this 514 TE link. For instance, if a row is created in the tedTable, but the 515 actual TE link is not available for some reason (e.g. when there is 516 not yet physical link or manually disable), then the object would be 517 down(2) state. In contrast, if a row is added and the TE link is 518 available, this would be operationally up(1)." 519 ::= { tedEntry 6 } 521 tedAreaId OBJECT-TYPE 522 SYNTAX TedAreaIdTC 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "This object indicates the area identifier of the IGP. If OSPF 527 is used to advertise LSA, this represents an ospfArea. If ISIS is 528 used, this represents an area address. Otherwise, this represents 529 zero." 530 REFERENCE 531 " OSPF Version 2, RFC2328, C.2 532 OSPF for IPv6, RFC5340, C.2 533 ISO10589, Section 9.8 " 534 ::= { tedEntry 7 } 536 tedLinkType OBJECT-TYPE 537 SYNTAX INTEGER { 538 pointToPoint (1), 539 multiAccess (2) 540 } 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "This indicates the type of the link such as point-to-point or 545 multi-access." 546 REFERENCE 547 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 548 3630, 2.5.1" 549 ::= { tedEntry 8 } 551 tedTeRouterIdAddrType OBJECT-TYPE 552 SYNTAX InetAddressType 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 " This object indicates the TE-Router ID address type. Only 557 values unknown(0), ipv4(1) or ipv6(2) are supported. " 558 ::= { tedEntry 9 } 560 tedTeRouterIdAddr OBJECT-TYPE 561 SYNTAX InetAddress 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "This object indicates the TE-Router ID." 566 REFERENCE 567 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 568 3630, 2.4.1 569 IS-IS extensions for TE, RFC5305, 4.3" 570 ::= { tedEntry 10 } 572 tedLinkIdAddrType OBJECT-TYPE 573 SYNTAX InetAddressType 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 " This object indicates the address type of the TE Link ID. 578 Only values unknown(0), ipv4(1) or ipv6(2) are supported." 579 ::= { tedEntry 11 } 581 tedLinkIdAddr OBJECT-TYPE 582 SYNTAX InetAddress 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "This indicates the Router ID of the neighbor in the case of 587 point-to-point links. This also indicates the interface address of 588 the designated router in the case of multi-access links." 589 REFERENCE 590 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 591 3630, 2.5.2 592 IS-IS extensions for TE, RFC5305, 4.3" 593 ::= { tedEntry 12 } 595 tedMetric OBJECT-TYPE 596 SYNTAX Integer32 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "This indicates the traffic engineering metric value of the TE 601 link." 602 REFERENCE 603 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 604 3630, 2.5.5 605 IS-IS extensions for TE, RFC5305, 3.7" 606 ::= { tedEntry 13 } 608 tedMaxBandwidth OBJECT-TYPE 609 SYNTAX Float32TC 610 UNITS "Byte per second" 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "This indicates the maximum bandwidth that can be used on this 615 link in this direction." 616 REFERENCE 617 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 618 3630, 2.5.6 619 IS-IS extensions for TE, RFC5305, 3.4" 620 ::= { tedEntry 14 } 622 tedMaxReservableBandwidth OBJECT-TYPE 623 SYNTAX Float32TC 624 UNITS "Byte per second" 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "This indicates the maximum bandwidth that may be reserved on 629 this link in this direction." 630 REFERENCE 631 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 632 3630, 2.5.7 633 IS-IS extensions for TE, RFC5305, 3.5" 634 ::= { tedEntry 15 } 636 tedUnreservedBandwidthPri0 OBJECT-TYPE 637 SYNTAX Float32TC 638 UNITS "Byte per second" 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "This indicates the amount of bandwidth not yet reserved at the 643 priority 0." 644 REFERENCE 645 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 646 3630, 2.5.8 647 IS-IS extensions for TE, RFC5305, 3.6" 648 ::= { tedEntry 16 } 650 tedUnreservedBandwidthPri1 OBJECT-TYPE 651 SYNTAX Float32TC 652 UNITS "Byte per second" 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "This indicates the amount of bandwidth not yet reserved at the 657 priority 1." 658 REFERENCE 659 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 660 3630, 2.5.8 661 IS-IS extensions for TE, RFC5305, 3.6" 662 ::= { tedEntry 17 } 664 tedUnreservedBandwidthPri2 OBJECT-TYPE 665 SYNTAX Float32TC 666 UNITS "Byte per second" 667 MAX-ACCESS read-only 668 STATUS current 669 DESCRIPTION 670 "This indicates the amount of bandwidth not yet reserved at the 671 priority 2." 672 REFERENCE 673 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 674 3630, 2.5.8 675 IS-IS extensions for TE, RFC5305, 3.6" 676 ::= { tedEntry 18 } 678 tedUnreservedBandwidthPri3 OBJECT-TYPE 679 SYNTAX Float32TC 680 UNITS "Byte per second" 681 MAX-ACCESS read-only 682 STATUS current 683 DESCRIPTION 684 "This indicates the amount of bandwidth not yet reserved at the 685 priority 3." 686 REFERENCE 687 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 688 3630, 2.5.8 689 IS-IS extensions for TE, RFC5305, 3.6" 690 ::= { tedEntry 19 } 692 tedUnreservedBandwidthPri4 OBJECT-TYPE 693 SYNTAX Float32TC 694 UNITS "Byte per second" 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "This indicates the amount of bandwidth not yet reserved at the 699 priority 4." 700 REFERENCE 701 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 702 3630, 2.5.8 703 IS-IS extensions for TE, RFC5305, 3.6" 704 ::= { tedEntry 20 } 706 tedUnreservedBandwidthPri5 OBJECT-TYPE 707 SYNTAX Float32TC 708 UNITS "Byte per second" 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "This indicates the amount of bandwidth not yet reserved at the 713 priority 5." 714 REFERENCE 715 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 716 3630, 2.5.8 717 IS-IS extensions for TE, RFC5305, 3.6" 718 ::= { tedEntry 21 } 720 tedUnreservedBandwidthPri6 OBJECT-TYPE 721 SYNTAX Float32TC 722 UNITS "Byte per second" 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "This indicates the amount of bandwidth not yet reserved at the 727 priority 6." 728 REFERENCE 729 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 730 3630, 2.5.8 731 IS-IS extensions for TE, RFC5305, 3.6" 732 ::= { tedEntry 22 } 734 tedUnreservedBandwidthPri7 OBJECT-TYPE 735 SYNTAX Float32TC 736 UNITS "Byte per second" 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "This indicates the amount of bandwidth not yet reserved at the 741 priority 7." 742 REFERENCE 743 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 744 3630, 2.5.8 745 IS-IS extensions for TE, RFC5305, 3.6" 746 ::= { tedEntry 23 } 748 tedAdministrativeGroup OBJECT-TYPE 749 SYNTAX Integer32 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "This indicates the Administrative Group which the link belong 754 to. Since the value is a bit mask, the link can belong to multiple 755 groups. This is also called Resource Class/Color." 756 REFERENCE 757 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 758 3630, 2.5.9 759 IS-IS extensions for TE, RFC5305, 3.1" 760 ::= { tedEntry 24 } 762 tedLocalId OBJECT-TYPE 763 SYNTAX Integer32 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "This indicates the Link local identifier of an unnumbered 768 link." 769 REFERENCE 770 " OSPF Extensions in Support of GMPLS, RFC4203, 1.1 771 IS-IS Extensions in Support of GMPLS, RFC5307, 1.1" 772 ::= { tedEntry 25 } 774 tedRemoteId OBJECT-TYPE 775 SYNTAX Integer32 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "This indicates the Link remote identifier of an unnumbered 780 link." 781 REFERENCE 782 " OSPF Extensions in Support of GMPLS, RFC4203, 1.1 783 IS-IS Extensions in Support of GMPLS, RFC5307, 1.1" 784 ::= { tedEntry 26 } 786 tedLinkProtectionType OBJECT-TYPE 787 SYNTAX BITS { 788 extraTraffic(0), 789 unprotected(1), 790 shared (2), 791 dedicatedOneToOne (3), 792 dedicatedOnePlusOne(4), 793 enhanced(5) 794 } 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "This object indicates the protection type of the TE link." 799 REFERENCE 800 " OSPF Extensions in Support of GMPLS, RFC4203, 1.2 801 IS-IS Extensions in Support of GMPLS, RFC5307, 1.2" 802 ::= { tedEntry 27 } 804 -- 805 -- TED Local Interface IP Address Table 806 -- 808 tedLocalIfAddrTable OBJECT-TYPE 809 SYNTAX SEQUENCE OF TedLocalIfAddrEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 813 "This table contains the IP address information of a local TE 814 link." 815 ::= { tedObjects 2 } 817 tedLocalIfAddrEntry OBJECT-TYPE 818 SYNTAX TedLocalIfAddrEntry 819 MAX-ACCESS not-accessible 820 STATUS current 821 DESCRIPTION 822 "This entry contains the IP address information of the local TE 823 link." 824 INDEX { tedLinkIndex, tedLocalIfAddr } 825 ::= { tedLocalIfAddrTable 1 } 827 TedLocalIfAddrEntry ::= SEQUENCE { 828 tedLocalIfAddrType InetAddressType, 829 tedLocalIfAddr InetAddress 831 } 833 tedLocalIfAddrType OBJECT-TYPE 834 SYNTAX InetAddressType 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "This object indicates the address type of the local TE link. 839 Only values unknown(0), ipv4(1) or ipv6(2) have to be supported." 840 ::= { tedLocalIfAddrEntry 1 } 842 tedLocalIfAddr OBJECT-TYPE 843 SYNTAX InetAddress (SIZE (1..20)) 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "This object indicates the address of the local TE link." 848 REFERENCE 849 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 850 3630, 2.5.3, 851 Traffic Engineering Extensions to OSPF Version3, RFC5329, 4.3 852 IS-IS extensions for TE, RFC5305, 3.4 " 853 ::= { tedLocalIfAddrEntry 2 } 855 -- 856 -- TED Remote Interface IP Address Table 857 -- 859 tedRemoteIfAddrTable OBJECT-TYPE 860 SYNTAX SEQUENCE OF TedRemoteIfAddrEntry 861 MAX-ACCESS not-accessible 862 STATUS current 863 DESCRIPTION 864 "This table contains the IP address information of a remote TE 865 link." 866 ::= { tedObjects 3 } 868 tedRemoteIfAddrEntry OBJECT-TYPE 869 SYNTAX TedRemoteIfAddrEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "This entry contains the IP address information of the remote 874 TE link." 875 INDEX { tedLinkIndex, tedRemoteIfAddr } 876 ::= { tedRemoteIfAddrTable 1 } 878 TedRemoteIfAddrEntry ::= SEQUENCE { 879 tedRemoteIfAddrType InetAddressType, 880 tedRemoteIfAddr InetAddress 881 } 883 tedRemoteIfAddrType OBJECT-TYPE 884 SYNTAX InetAddressType 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "This object indicates the address type of the remote TE link." 889 ::= { tedRemoteIfAddrEntry 1 } 891 tedRemoteIfAddr OBJECT-TYPE 892 SYNTAX InetAddress(SIZE (1..20)) 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "This object indicates the address of the remote TE link." 897 REFERENCE 898 " Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 899 3630, 2.5.4, 900 Traffic Engineering Extensions to OSPF Version3, RFC5329, 4.4 901 IS-IS extensions for TE, RFC5305, 3.3 " 902 ::= { tedRemoteIfAddrEntry 2 } 904 -- 905 -- TED Switching Capability Table 906 -- 908 tedSwCapTable OBJECT-TYPE 909 SYNTAX SEQUENCE OF TedSwCapEntry 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "This table contains the GMPLS TED switching capability 914 information." 915 ::= { tedObjects 4 } 917 tedSwCapEntry OBJECT-TYPE 918 SYNTAX TedSwCapEntry 919 MAX-ACCESS not-accessible 920 STATUS current 921 DESCRIPTION 922 "This entry relates each TE link with its GMPLS TE switching 923 capability information. If the MIB module deals with only OSPF-TE 924 information, the value of each object related with GMPLS TE 925 extensions should be null." 926 INDEX { tedLinkIndex, tedSwCapIndex } 927 ::= { tedSwCapTable 1 } 929 TedSwCapEntry ::= SEQUENCE { 930 tedSwCapIndex Unsigned32, 931 tedSwCapType IANAGmplsSwitchingTypeTC, 932 tedSwCapEncoding IANAGmplsLSPEncodingTypeTC, 933 tedSwCapMaxLspBandwidthPri0 Float32TC, 934 tedSwCapMaxLspBandwidthPri1 Float32TC, 935 tedSwCapMaxLspBandwidthPri2 Float32TC, 936 tedSwCapMaxLspBandwidthPri3 Float32TC, 937 tedSwCapMaxLspBandwidthPri4 Float32TC, 938 tedSwCapMaxLspBandwidthPri5 Float32TC, 939 tedSwCapMaxLspBandwidthPri6 Float32TC, 940 tedSwCapMaxLspBandwidthPri7 Float32TC, 941 tedSwCapMinLspBandwidth Float32TC, 942 tedSwCapIfMtu Integer32, 943 tedSwCapIndication INTEGER 944 } 946 tedSwCapIndex OBJECT-TYPE 947 SYNTAX Unsigned32 (1..255) 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 "This index is utilized to identify multiple switching 952 functions on a local or remote TE link according to definitions of 953 textual conventions of GMPLS, RFC4801." 954 ::= { tedSwCapEntry 1 } 956 tedSwCapType OBJECT-TYPE 957 SYNTAX IANAGmplsSwitchingTypeTC 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "This object indicates the GMPLS switching capability assigned 962 to the TE link according to definitions of textual conventions of 963 GMPLS, RFC4801." 964 REFERENCE 965 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 966 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 967 ::= { tedSwCapEntry 2 } 969 tedSwCapEncoding OBJECT-TYPE 970 SYNTAX IANAGmplsLSPEncodingTypeTC 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "This object indicates the GMPLS encoding type assigned to the 975 TE link." 976 REFERENCE 977 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 978 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 979 ::= { tedSwCapEntry 3 } 981 tedSwCapMaxLspBandwidthPri0 OBJECT-TYPE 982 SYNTAX Float32TC 983 UNITS "Byte per second" 984 MAX-ACCESS read-only 985 STATUS current 986 DESCRIPTION 987 "This object indicates the maximum bandwidth of the TE link at 988 the priority 0 for GMPLS LSP creation." 989 REFERENCE 990 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 991 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 992 ::= { tedSwCapEntry 4 } 993 tedSwCapMaxLspBandwidthPri1 OBJECT-TYPE 994 SYNTAX Float32TC 995 UNITS "Byte per second" 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "This object indicates the maximum bandwidth of the TE link at 1000 the priority 1 for GMPLS LSP creation." 1001 REFERENCE 1002 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1003 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1004 ::= { tedSwCapEntry 5 } 1006 tedSwCapMaxLspBandwidthPri2 OBJECT-TYPE 1007 SYNTAX Float32TC 1008 UNITS "Byte per second" 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "This object indicates the maximum bandwidth of the TE link at 1013 the priority 2 for GMPLS LSP creation." 1014 REFERENCE 1015 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1016 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1017 ::= { tedSwCapEntry 6 } 1019 tedSwCapMaxLspBandwidthPri3 OBJECT-TYPE 1020 SYNTAX Float32TC 1021 UNITS "Byte per second" 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "This object indicates the maximum bandwidth of the TE link at 1026 the priority 3 for GMPLS LSP creation." 1027 REFERENCE 1028 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1029 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1030 ::= { tedSwCapEntry 7 } 1032 tedSwCapMaxLspBandwidthPri4 OBJECT-TYPE 1033 SYNTAX Float32TC 1034 UNITS "Byte per second" 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "This object indicates the maximum bandwidth of the TE link at 1039 the priority 4 for GMPLS LSP creation." 1040 REFERENCE 1041 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1042 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1043 ::= { tedSwCapEntry 8 } 1045 tedSwCapMaxLspBandwidthPri5 OBJECT-TYPE 1046 SYNTAX Float32TC 1047 UNITS "Byte per second" 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "This object indicates the maximum bandwidth of the TE link at 1052 the priority 5 for GMPLS LSP creation." 1053 REFERENCE 1054 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1055 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1056 ::= { tedSwCapEntry 9 } 1058 tedSwCapMaxLspBandwidthPri6 OBJECT-TYPE 1059 SYNTAX Float32TC 1060 UNITS "Byte per second" 1061 MAX-ACCESS read-only 1062 STATUS current 1063 DESCRIPTION 1064 "This object indicates the maximum bandwidth of the TE link at 1065 the priority 6 for GMPLS LSP creation." 1066 REFERENCE 1067 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1068 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1069 ::= { tedSwCapEntry 10 } 1071 tedSwCapMaxLspBandwidthPri7 OBJECT-TYPE 1072 SYNTAX Float32TC 1073 UNITS "Byte per second" 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "This object indicates the maximum bandwidth of the TE link at 1078 the priority 7 for GMPLS LSP creation." 1079 REFERENCE 1080 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1081 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1082 ::= { tedSwCapEntry 11 } 1084 tedSwCapMinLspBandwidth OBJECT-TYPE 1085 SYNTAX Float32TC 1086 UNITS "Byte per second" 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "This object indicates the minimum bandwidth of the TE link for 1091 GMPLS LSP creation if the switching capability field is TDM, PSC-1, 1092 PSC-2, PSC-3, or PSC-4." 1093 REFERENCE 1094 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1095 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1096 ::= { tedSwCapEntry 12 } 1098 tedSwCapIfMtu OBJECT-TYPE 1099 SYNTAX Integer32 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "This object indicates the MTU of the local or remote TE link." 1104 REFERENCE 1105 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1106 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1107 ::= { tedSwCapEntry 13 } 1109 tedSwCapIndication OBJECT-TYPE 1110 SYNTAX INTEGER { 1111 standard (0), 1112 arbitrary (1) 1113 } 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION 1117 "This object indicates whether the interface supports Standard 1118 or Arbitrary SONET SDH." 1119 REFERENCE 1120 " OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1121 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3 " 1122 ::= { tedSwCapEntry 14 } 1124 -- 1125 -- TED SRLG Table 1126 -- 1128 tedSrlgTable OBJECT-TYPE 1129 SYNTAX SEQUENCE OF TedSrlgEntry 1130 MAX-ACCESS not-accessible 1131 STATUS current 1132 DESCRIPTION 1133 "This table contains the SRLG information of the TE link." 1134 ::= { tedObjects 5 } 1136 tedSrlgEntry OBJECT-TYPE 1137 SYNTAX TedSrlgEntry 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "This entry relates each TE link with its SRLG information." 1142 INDEX { tedLinkIndex, tedSrlgIndex } 1143 ::= { tedSrlgTable 1 } 1145 TedSrlgEntry ::= SEQUENCE { 1146 tedSrlgIndex Unsigned32, 1147 tedSrlg Integer32 1148 } 1150 tedSrlgIndex OBJECT-TYPE 1151 SYNTAX Unsigned32(1..255) 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 " This index is utilized to identify multiple SRLG values on a 1156 local or remote TE link. This object represents an arbitrary value 1157 which is locally defined in a router." 1158 REFERENCE 1159 " OSPF Extensions in support of GMPLS, RFC4203, 1.3 1160 IS-IS Extensions in Support of GMPLS, RFC5307, 1.4 " 1161 ::= { tedSrlgEntry 1 } 1163 tedSrlg OBJECT-TYPE 1164 SYNTAX Integer32 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "This object indicate the SRLG value assigned to a local or 1169 remote TE link" 1170 REFERENCE 1171 " OSPF Extensions in Support of GMPLS, RFC4203, 1.3 1172 IS-IS Extensions in Support of GMPLS, RFC5307, 1.4 " 1173 ::= { tedSrlgEntry 2 } 1175 -- 1176 -- Notification Configuration 1177 -- 1179 tedStatusChangeNotificationMaxRate OBJECT-TYPE 1180 SYNTAX Unsigned32 1181 MAX-ACCESS read-write 1182 STATUS current 1183 DESCRIPTION 1184 "A lot of notifications relating to the status change are 1185 expected to generate in a node, especially when a network failure 1186 occurs and might cause a performance degradation of the node itself. 1187 To avoid such a defect, this object provides the maximum number of 1188 notifications generated per minute. If events occur more rapidly, 1189 the implementation may simply fail to emit these notifications during 1190 that period, or may queue them until an appropriate time. A value of 1191 0 means no throttling is applied and events may be notified at the 1192 rate at which they occur." 1193 DEFVAL {1} 1194 ::= { tedObjects 6 } 1196 tedCreatedDeletedNotificationMaxRate OBJECT-TYPE 1197 SYNTAX Unsigned32 1198 MAX-ACCESS read-write 1199 STATUS current 1200 DESCRIPTION 1201 "A lot of notifications relating to new registration in ted 1202 table by receiving new TE link information or deletion of existing 1203 entries in ted table are expected to generate in a node. This object 1204 provides the maximum number of notifications generated per minute. " 1205 DEFVAL {1} 1206 ::= { tedObjects 7 } 1207 -- 1208 -- Notifications 1209 -- 1211 tedStatusChange NOTIFICATION-TYPE 1212 OBJECTS { 1213 tedLinkState 1214 } 1215 STATUS current 1216 DESCRIPTION 1217 "This notification signifies that there has been change in TE 1218 information of tedTable, tedLocalIfAddrTable, tedRemoteIfAddrTable, 1219 tedSwCapTable and/or tedSrlgTable. For example, this should be 1220 generated when tedUnreservedBandwidth is changed to create or delete 1221 LSP using registered TE link. " 1222 ::= { tedNotifications 1 } 1224 tedEntryCreated NOTIFICATION-TYPE 1225 OBJECTS { 1226 tedLinkState 1227 } 1228 STATUS current 1229 DESCRIPTION 1230 " This notification signifies that there has been new 1231 registration in ted table by receiving new TE link information. For 1232 example, this should be generated when new index (tedLinkIndex) is 1233 registered in TED table." 1234 ::= { tedNotifications 2 } 1236 tedEntryDeleted NOTIFICATION-TYPE 1237 OBJECTS { 1238 tedLinkState 1239 } 1240 STATUS current 1241 DESCRIPTION 1242 "This notification signifies that there has been deletion of an 1243 entry in the ted table. For example, this should be generated when 1244 one of existing entries is deleted in TED table." 1245 ::= { tedNotifications 3 } 1247 -- Conformance Statement 1249 tedCompliances 1250 OBJECT IDENTIFIER ::= { tedConformance 1 } 1251 tedGroups 1252 OBJECT IDENTIFIER ::= { tedConformance 2 } 1254 -- Module Compliance 1256 tedModuleFullCompliance MODULE-COMPLIANCE 1257 STATUS current 1258 DESCRIPTION 1259 "Compliance statement for agents provides full support for the 1260 TED MIB." 1261 MODULE -- this module 1262 MANDATORY-GROUPS { tedMainGroup, 1263 tedObjectsGroup, 1264 tedNotificationGroup 1265 } 1267 GROUP tedUnnumberedLinkGroup 1268 DESCRIPTION 1269 "This group is mandatory for TE links that supports the 1270 unnumbered links." 1272 GROUP tedNumberedLinkGroup 1273 DESCRIPTION 1274 "This group is mandatory for TE links that supports the numbered 1275 links." 1277 GROUP tedSwCapGroup 1278 DESCRIPTION 1279 "This group is mandatory for TE links that supports GMPLS 1280 switching capability." 1282 GROUP tedSwCapMinLspBandwidthGroup 1283 DESCRIPTION 1284 "This group is mandatory for TE links if the switching 1285 capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4." 1287 GROUP tedSwCapIfMtuGroup 1288 DESCRIPTION 1289 "This group is mandatory for TE links that supports the MTU of 1290 the local or remote TE link." 1292 GROUP tedSwCapIndicationGroup 1293 DESCRIPTION 1294 "This group is mandatory for TE links that supports Standard or 1295 Arbitrary SONET/SDH." 1297 GROUP tedSrlgGroup 1298 DESCRIPTION 1299 "This group is mandatory for TE links that supports SRLG 1300 information." 1302 ::= { tedCompliances 1 } 1304 -- 1305 -- ReadOnly Compliance 1306 -- 1308 tedModuleReadOnlyCompliance MODULE-COMPLIANCE 1309 STATUS current 1310 DESCRIPTION 1311 "Compliance requirement for implementations only provide read- 1312 only support for TED. Such devices can then be monitored but cannot 1313 be configured using this MIB module." 1314 MODULE -- this module 1315 MANDATORY-GROUPS { tedMainGroup 1316 } 1318 GROUP tedUnnumberedLinkGroup 1319 DESCRIPTION 1320 "This group is mandatory for TE links that supports the 1321 unnumbered links." 1323 GROUP tedNumberedLinkGroup 1324 DESCRIPTION 1325 "This group is mandatory for TE links that supports the numbered 1326 links." 1328 GROUP tedSwCapGroup 1329 DESCRIPTION 1330 "This group is mandatory for TE links that supports some GMPLS 1331 switching capabilities." 1333 GROUP tedSwCapMinLspBandwidthGroup 1334 DESCRIPTION 1335 "This group is mandatory for TE links if the switching 1336 capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4." 1338 GROUP tedSwCapIfMtuGroup 1339 DESCRIPTION 1340 "This group is mandatory for TE links that supports the MTU of 1341 the local or remote TE link." 1343 GROUP tedSwCapIndicationGroup 1344 DESCRIPTION 1345 "This group is mandatory for TE links that supports Standard or 1346 Arbitrary SONET/SDH." 1348 GROUP tedSrlgGroup 1349 DESCRIPTION 1350 "This group is mandatory for TE links that supports SRLG 1351 information." 1353 ::= { tedCompliances 2 } 1355 -- Units of conformance 1357 tedMainGroup OBJECT-GROUP 1358 OBJECTS { 1359 tedLinkState , 1360 tedAreaId , 1361 tedLinkType , 1362 tedTeRouterIdAddrType , 1363 tedTeRouterIdAddr , 1364 tedLinkIdAddrType , 1365 tedLinkIdAddr , 1366 tedMetric , 1367 tedMaxBandwidth , 1368 tedMaxReservableBandwidth , 1369 tedUnreservedBandwidthPri0 , 1370 tedUnreservedBandwidthPri1 , 1371 tedUnreservedBandwidthPri2 , 1372 tedUnreservedBandwidthPri3 , 1373 tedUnreservedBandwidthPri4 , 1374 tedUnreservedBandwidthPri5 , 1375 tedUnreservedBandwidthPri6 , 1376 tedUnreservedBandwidthPri7 , 1377 tedAdministrativeGroup , 1378 tedLinkProtectionType , 1379 tedLinkInformationData 1380 } 1381 STATUS current 1382 DESCRIPTION 1383 "Collection of objects for TED management" 1384 ::= { tedGroups 1 } 1386 tedObjectsGroup OBJECT-GROUP 1387 OBJECTS { 1388 tedStatusChangeNotificationMaxRate, 1389 tedCreatedDeletedNotificationMaxRate 1390 } 1391 STATUS current 1392 DESCRIPTION 1393 "This objects needed to implement notification." 1394 ::= { tedGroups 2 } 1396 tedNotificationGroup NOTIFICATION-GROUP 1397 NOTIFICATIONS { 1398 tedStatusChange, 1399 tedEntryCreated, 1400 tedEntryDeleted 1401 } 1402 STATUS current 1403 DESCRIPTION 1404 " This group is mandatory for those implementations that can 1405 implement the notifications contained in this group. " 1406 ::= { tedGroups 3 } 1408 tedUnnumberedLinkGroup OBJECT-GROUP 1409 OBJECTS { 1410 tedLocalId, 1411 tedRemoteId 1412 } 1413 STATUS current 1414 DESCRIPTION 1415 "This objects needed to implement the unnumbered links." 1416 ::= { tedGroups 4 } 1418 tedNumberedLinkGroup OBJECT-GROUP 1419 OBJECTS { 1420 tedLocalIfAddrType, 1421 tedRemoteIfAddrType 1422 } 1423 STATUS current 1424 DESCRIPTION 1425 "This objects needed to implement the numbered links." 1426 ::= { tedGroups 5 } 1428 tedSwCapGroup OBJECT-GROUP 1429 OBJECTS { 1430 tedSwCapType, 1431 tedSwCapEncoding, 1432 tedSwCapMaxLspBandwidthPri0, 1433 tedSwCapMaxLspBandwidthPri1, 1434 tedSwCapMaxLspBandwidthPri2, 1435 tedSwCapMaxLspBandwidthPri3, 1436 tedSwCapMaxLspBandwidthPri4, 1437 tedSwCapMaxLspBandwidthPri5, 1438 tedSwCapMaxLspBandwidthPri6, 1439 tedSwCapMaxLspBandwidthPri7 1440 } 1441 STATUS current 1442 DESCRIPTION 1443 "This objects needed to implement TE links with its GMPLS TE 1444 switching capability information." 1445 ::= { tedGroups 6 } 1447 tedSwCapMinLspBandwidthGroup OBJECT-GROUP 1448 OBJECTS { 1449 tedSwCapMinLspBandwidth 1450 } 1451 STATUS current 1452 DESCRIPTION 1453 "This objects needed to implement the minimum bandwidth of the 1454 TE link for GMPLS LSP creation." 1455 ::= { tedGroups 7 } 1457 tedSwCapIfMtuGroup OBJECT-GROUP 1458 OBJECTS { 1459 tedSwCapIfMtu 1460 } 1461 STATUS current 1462 DESCRIPTION 1463 "This objects needed to implement the MTU information of the 1464 local or remote TE link." 1465 ::= { tedGroups 8 } 1467 tedSwCapIndicationGroup OBJECT-GROUP 1468 OBJECTS { 1469 tedSwCapIndication 1470 } 1471 STATUS current 1472 DESCRIPTION 1473 "This objects needed to implement the indication whether the 1474 interface supports Standard or Arbitrary SONET/SDH." 1475 ::= { tedGroups 9 } 1476 tedSrlgGroup OBJECT-GROUP 1477 OBJECTS { 1478 tedSrlg 1479 } 1480 STATUS current 1481 DESCRIPTION 1482 "This objects needed to implement multiple SRLG values with 1483 GMPLS TE information." 1484 ::= { tedGroups 10 } 1486 END 1488 8. Security Consideration 1490 There is a number of management objects defined in this MIB module 1491 that has a MAX-ACCESS clause of read-write. Such objects may be 1492 considered sensitive or vulnerable in some network environments. The 1493 support for SET operations in a non-secure environment without proper 1494 protection can have a negative effect on network operations. 1496 Some of the readable objects in this MIB module (i.e., objects with a 1497 MAX-ACCESS other than not-accessible) may be considered sensitive or 1498 vulnerable in some network environments. It is thus important to 1499 control even GET and/or NOTIFY access to these objects and possibly 1500 to even encrypt the values of these objects when sending them over 1501 the network via SNMP. These are the tables and objects and their 1502 sensitivity/vulnerability: tedTable, tedLocalIfAddrTable, 1503 tedRemoteIfAddrTable, tedSwCapTable and tedSrlgTable contain topology 1504 information for the MPLS/GMPLS network. If an administrator does not 1505 want to reveal this information, then these tables should be 1506 considered sensitive/vulnerable. 1508 There are only two write-access objects in this MIB module: 1509 tedStatusChangeNotificationMaxRate and 1510 tedCreatedDeletedNotificationMaxRate. Malicious modification of 1511 these objects could cause the management agent, the network, or the 1512 router to become overloaded with Notifications in cases of high churn 1513 within the network. 1515 SNMP versions prior to SNMPv3 did not include adequate security. Even 1516 if the network itself is secure (for example by using IPsec), even 1517 then, there is no control as to who on the secure network is allowed 1518 to access and GET/SET (read/change/create/delete) the objects in this 1519 MIB module. 1521 It is RECOMMENDED that implementers consider the security features as 1522 provided by the SNMPv3 framework (see [RFC3410], section 8), 1523 including full supports for the SNMPv3 cryptographic mechanisms (for 1524 authentication and privacy). 1526 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1527 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1528 enable cryptographic security. It is then a customer/operator 1529 responsibility to ensure that the SNMP entity giving access to an 1530 instance of this MIB module is properly configured to give access to 1531 the objects only to those principles (users) that have legitimate 1532 rights to indeed GET or SET (change/create/delete) them. 1534 9. IANA Considerations 1536 The following "IANA Considerations" subsection requests IANA for a 1537 new assignment under the transmission subtree. New assignments can 1538 only be made via a Standards Action as specified in [RFC5226]. 1540 9.1 IANA Considerations for TED-MIB 1542 The IANA is requested to assign {transmission XXX } to the TED-MIB 1543 module specified in this document. 1545 10. References 1547 10.1 Normative References 1549 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1550 Requirement Levels", BCP 14, RFC 2119, March 1997. 1552 [RFC2328] J. Moy, " OSPF version2 ", RFC2328, April 1998. 1554 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1555 "Structure of Management Information Version 2 (SMIv2)", 1556 STD 58, RFC 2578, April 1999. 1558 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1559 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1560 1999. 1562 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1563 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1564 April 1999. 1566 [RFC4001] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder, 1567 "Textual Conventions for Internet Network Addresses", 1568 RFC4001, Feb. 2005. 1569 [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions to 1570 OSPF Version2", RFC3630, Sep. 2003. 1572 [RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in Support 1573 of Generalized Multi-Protocol Label Switching", RFC4203, 1574 Oct. 2005. 1576 [RFC4750] Dan Joyal, et al, "OSPF Version 2 Management Information 1577 Base", RFC4750, Dec. 2006. 1579 [RFC4801] T. D. Nadeau and A. Farrel, Ed., "Definitions of Textual 1580 Conventions for Generalized Multiprotocol Label Switching 1581 (GMPLS) Management", RFC4801, Feb. 2007. 1583 [RFC5329] K. Ishiguro, V. Manral, A. Davey, A.Lindem " Traffic 1584 Engineering Extensions to OSPF Version 3 ", RFC5329, Sep. 1585 2008. 1587 [RFC5340] R. Coltun, D. Ferguson, J. Moy, A.Lindem " OSPF for IPv6", 1588 RFC5340, July 2008. 1590 [RFC5643] Dan Joyal, et al, "Management Information Base for OSPFv3 1591 ", RFC5643, August 2009. 1593 [RFC6340] R. Presuhn, "Textual Conventions for the Representation of 1594 Floating-point Number ", RFC6340, August 2011. 1596 [ISO10589] ISO 10589, "Intermediate system to Intermediate system 1597 routeing information exchange protocol for use in 1598 conjunction with the Protocol for providing the 1599 Connectionless-mode Network Service (ISO 8473)", ISO/IEC 1600 10589:2002. 1602 10.2 Informative References 1604 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1605 and Applicability Statement for Internet Standard 1606 Management Framework", RFC 3410, Dec. 2002. 1608 [RFC3812] Srinivasan, C., Viswanathan, A., and T. D. Nadeau, 1609 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1610 (TE) Management Information Base (MIB)", RFC 3812, June 1611 2004. 1613 [RFC3813] Srinivasan, C., Viswanathan, A., and T. D. Nadeau, 1614 "Multiprotocol Label Switching (MPLS) Label Switching 1615 (LSR) Router Management Information Base (MIB)", RFC 3813, 1616 June 2004. 1618 [RFC3945] E. Mannie, "Generalized Multi-Procol Label Switching 1619 (MPLS) Architecture", RFC3945, Oct. 2004. 1621 [RFC4202] K. Kompella, and Y. Rekhter, "Routing Extensions in 1622 Support of Generalized Multi-Protocol Label Switching", 1623 RFC4202, Oct. 2005. 1625 [RFC4220] M. Dubuc, T. D. Nadeau and J. Lang, " Traffic Engineering 1626 Link Management Information Base ", RFC4220, Dec. 2005. 1628 [RFC4377] T. D. Nadeau, et al, "Operations and Management (OAM) 1629 Requirements for Multi-Protocol Label Switched (MPLS) 1630 Networks", RFC 4377, February 2006. 1632 [RFC4444] T. Parker, et al, "Management Information Base for 1633 Intermediate System to Intermediate System (IS-IS)", RFC 1634 4444, April 2006. 1636 [RFC4802] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 1637 Label Switching (GMPLS) Traffic Engineering Management 1638 Information Base", RFC4802, Feb. 2007. 1640 [RFC4803] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 1641 Label Switching (GMPLS) Label Switching Router (LSR) 1642 Management Information Base", RFC4803, Feb., 2007. 1644 [RFC5305] H. Smit and T. Li, "IS-IS extensions for Traffic 1645 Engineering", RFC 5305, Oct. 2008. 1647 [RFC5307] K. Kompella, and Y. Rekhter, "IS-IS Extensions in Support 1648 of Generalized Multi-Protocol Label Switching (GMPLS)", 1649 RFC5307, Oct. 2008. 1651 [RFC5226] Narten, T. and H. Alvestrand., " Guidelines for Writing an 1652 IANA Considerations Section in RFCs" BCP 26, RFC 5226, May 1653 2008. 1655 11. Acknowledgment 1657 The authors wish to acknowledge and thank the following individuals 1658 for their valuable comments to this document: Ken Nagami, Shuichi 1659 Okamoto, Adrian Farrel, Diego Caviglia and Acee Lindem. 1661 12. Authors' Addresses 1663 Tomohiro Otani 1664 KDDI Corporation 1665 KDDI Bldg, 1666 2-3-2, Nishishinjuku, Shinjuku-ku, Tokyo, 1667 163-8003, Japan 1668 Email: tm-otani@kddi.com 1670 Masanori Miyazawa 1671 KDDI R&D Laboratories, Inc. 1672 2-1-15 Ohara Fujimino, Saitama, 1673 356-8502, Japan. 1674 Email: ma-miyazawa@kddilabs.jp 1676 Thomas D. Nadeau 1677 Email: tnadeau@lucidvision.com 1679 Kenji Kumaki 1680 KDDI Corporation 1681 Garden Air Tower 1682 Iidabashi, Chyoda-ku, Tokyo, 1683 102-8460, Japan 1684 Email: ke-kumaki@kddi.com