idnits 2.17.1 draft-ietf-ccamp-gmpls-ted-mib-15.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 (November 6, 2012) is 4186 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) -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 4 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: April 5, 2013 5 Tomohiro Otani 6 Kenji Kumaki 7 KDDI Corporation 9 Thomas D. Nadeau 11 November 6, 2012 13 Traffic Engineering Database Management Information Base in support of 14 MPLS-TE/GMPLS 16 draft-ietf-ccamp-gmpls-ted-mib-15.txt 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 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. 50 This document may contain material from IETF Documents or IETF 51 Contributions published or made publicly available before November 10 52 2008. The person(s) controlling the copyright in some of this 53 material may not have granted the IETF Trust the right to allow 54 modifications of such material outside the IETF Standards Process. 56 Without obtaining an adequate license from the person(s) controlling 57 the copyright in such materials, this document may not be modified 58 outside the IETF Standards Process, and derivative works of it may 59 not be created outside the IETF Standards Process, except to format 60 it for publication as an RFC or to translate it into languages other 61 than English. 63 Abstract 65 This memo defines the Management Information Base (MIB) objects in 66 order to manage traffic engineering database (TED) information with 67 extension in support of Multi-Protocol Label Switching (MPLS) with 68 traffic engineering (TE) as well as Generalized MPLS (GMPLS) for use 69 with network management protocols. 71 Table of Contents 73 Status of this Memo ............................................... 1 74 Abstract .......................................................... 2 75 1. The Internet-Standard Management Framework ................... 3 76 2. Introduction ................................................. 3 77 3. Overview ..................................................... 3 78 3.1 Conventions used in this document ............................ 3 79 3.2 Terminology .................................................. 4 80 3.3 Acronyms ..................................................... 4 81 4. Motivations .................................................. 4 82 5. Brief Description of MIB Modules ............................. 4 83 5.1 tedTable ..................................................... 4 84 5.2 tedLocalIfAddrTable .......................................... 4 85 5.3 tedRemoteIfAddrTable ......................................... 4 86 5.4 tedSwCapTable ................................................ 5 87 5.5 tedSrlgTable ................................................. 5 88 6. Example of the TED MIB Module Usage .......................... 5 89 7. TED MIB Module Definitions in support of GMPLS ............... 6 90 8. Security Consideration ...................................... 29 91 9. IANA Considerations ......................................... 30 92 9.1 IANA Considerations for TED-MIB ............................. 30 93 10. References .................................................. 30 94 10.1 Normative References ........................................ 30 95 10.2 Informative References ...................................... 30 96 11. Acknowledgment .............................................. 32 97 12. Authors' Addresses .......................................... 33 99 1. The Internet-Standard Management Framework 101 For a detailed overview of the documents that describe the current 102 Internet-Standard Management Framework, please refer to section 7 of 103 RFC 3410 [RFC3410]. 105 Managed objects are accessed via a virtual information store, termed 106 the Management Information Base or MIB. MIB objects are generally 107 accessed through the Simple Network Management Protocol (SNMP). 108 Objects in the MIB are defined using the mechanisms defined in the 109 Structure of Management Information (SMI). This memo specifies a MIB 110 module that is compliant to the SMIv2, which is described in STD 58, 111 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 112 [RFC2580]. 114 2. Introduction 116 The OSPF MIB was originally defined for OSPF version2 in support of 117 IPv4 [RFC4750] and extended to support the Internet Protocol 118 version6(IPv6) as OSPF version3 MIB [RFC5643]. The ISIS MIB is also 119 defined as [RFC4444]. On the other side, MPLS/GMPLS based traffic 120 engineering has so far extended OSPF/ISIS routing protocol with TE 121 functionality [RFC4202], [RFC3630], [RFC5329], [RFC5307] and 122 [RFC5305]. To manage such MPLS-TE/GMPLS networks effectively, routing 123 information associated with MPLS/GMPLS TE parameters (TED) is 124 preferred for the network management; however, there is no clear 125 definition of MPLS/GMPLS TE information in existing MIBs related to 126 OSPF(v2 and v3)/ISIS. 128 This memo defines the Management Information Base (MIB) objects for 129 managing TED in support of MPLS-TE/GMPLS for use with network 130 management protocols. 132 This MIB module should be used in conjunction with OSPFv2 MIB, OSPF 133 v3 MIB and ISIS MIB as well as other MIBs defined in [RFC3812], 134 [RFC3813], [RFC4802] and [RFC4803] for the management of MPLS/GMPLS 135 based traffic engineering information. By implementing such MIB 136 modules, it is helpful to simultaneously understand entire MPLS/GMPLS 137 network such as routing information as well as LSP information using 138 a management system. But, note that this MIB module is able to be 139 implemented and performed without implementation of other MIB modules 140 when the management system, for example, only comprehends MPLS/GMPLS 141 topology information such as TE link information. 143 3. Overview 145 3.1 Conventions used in this document 147 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 148 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 149 "OPTIONAL" in this document are to be interpreted as described in 150 RFC-2119 [RFC2119]. 152 3.2 Terminology 154 Definitions of key terms for MPLS OAM and GMPLS are found in 155 [RFC4377] and [RFC3945], and the reader is assumed to be familiar 156 with those definitions which are not repeated here. 158 3.3 Acronyms 160 GMPLS: Generalized Multi-Protocol Label Switching 161 ISIS: Intermediate System to Intermediate System 162 LSA: Link state advertisement 163 LSP: Label Switching Path 164 LSR: Label Switching Router 165 MIB: Management Information Base 166 OSPF: Open Shortest Path First 167 PSC: Packet Switch Capable 168 SRLG: Shared Risk Link Group 169 TE: Traffic Engineering 170 TED: Traffic Engineering Database 171 TDM: Time Division Multiplexing 173 4. Motivations 175 The existing OSPFv2, OSPFv3, ISIS, MPLS and GMPLS MIBs do not provide 176 for the management interface to retrieve topology information of MPLS 177 and GMPLS networks. 179 5. Brief Description of MIB Modules 181 The objects described in this section support the management of TED 182 described in [RFC4202], [RFC4203] and [RFC5307] for GMPLS extensions 183 as well as in [RFC3630] and [RFC5305] for MPLS/GMPLS. 185 5.1 tedTable 187 The tedTable is basically used to indicate TED information of OSPF-TE 188 or ISIS-TE. However, this table does not contain information for 189 Local/Remote interface IP address, Interface Switching Capability 190 Descriptor and Shared Risk Link Group information within the sub-TLVs 191 for the Link-TLV. 193 5.2 tedLocalIfAddrTable 195 The tedLocalIfAddrTable is identical to the Local interface IP 196 address information in a sub-TLV for the Link-TLV. This is 197 independently defined, because the Interface IP Address sub-TLV may 198 appear more than once within the same Link-TLV. 200 5.3 tedRemoteIfAddrTable 202 The tedRemoteIfAddrTable is identical to the Remote interface IP 203 address information in a sub-TLV of the Link-TLV. This is 204 independently defined, because the Interface IP Address sub-TLV may 205 appear more than once with the same Link-TLV. 207 5.4 tedSwCapTable 209 The tedSwCapTable is identical to the Interface Switching Capability 210 Descriptor information in a sub-TLV of Link-TLV. This is 211 independently defined, because the Interface Switching Capability 212 Descriptor sub-TLV may appear more than once with same Link-TLV. 214 5.5 tedSrlgTable 216 The tedSrlgTable is identical to the Shared Risk Link Group 217 information in a sub-TLV of Link-TLV. Think is independently defined, 218 because the Shared Risk Link Group sub-TLV may appear more than once 219 with the same Link-TLV. 221 6.Example of the TED MIB Module Usage 223 In this section, we provide an example of the TED MIB module usage. 224 The following indicates the information of a numbered TE link 225 originated in a GMPLS controlled node. When TE link information is 226 retrieved in a MPLS network, GMPLS specific objects such as 227 tedLocalIfAddrTable, tedRemoteIfAddrTable, tedSwCapTable and 228 tedSrlgTable are not supported. 230 By retrieval of such information periodically, the management system 231 can comprehend the detailed topology information related to 232 MPLS/GMPLS networks. In particular, the basic TED information can be 233 collected by tedTable, local/remote interface IP address information 234 related to MPLS/GMPLS network are collected by tedLocalIfAddrTable 235 and tedRemoteIfAddrTable. And the attribute information related to 236 GMPLS TE link can be retrieved by tedSwCapTable and tedSrlgTable. 237 Regarding a fault management, there is no functionality to notify 238 network failures in this MIB module. But, if network topologies are 239 changed, the module can notify the change information to the 240 management system by using tedStatusChange, tedEntryCreated and 241 tedEntryDeleted. 243 Note that the TED MIB modules are only limited to "read-only" access 244 except for tedCreatedDeletedNotificationMaxRate and 245 tedStatusChangeNotificationMaxRate. The TED MIB module is designed to 246 be independent of OSPF or ISIS MIBs, however each TE link information 247 belongs to a node or a link which is managed by the routing protocol. 249 In tedTable: 250 { 251 tedLinkInformationData.2.3232235777.3232235778.16777264 zeroDotZero 252 tedLinkType.2.3232235777.3232235778.16777264 pointToPoint(1) 253 tedLinkState.2.3232235777.3232235778.16777264 up(1) 254 tedAreaId.2.3232235777.3232235778.16777264 0 255 tedTeRouterIdAddrType.2.3232235777.3232235778.16777264 ipv4(1) 256 tedTeRouterIdAddr.2.3232235777.3232235778.16777264 192.0.2.1 257 tedLinkIdAddrType.2.3232235777.3232235778.16777264 ipv4(1) 258 tedLinkIdAddr.2.3232235777.3232235778.16777264 192.0.2.10 259 tedMetric.2.3232235777.3232235778.16777264 1 260 tedMaxBandwidth.2.3232235777.3232235778.16777264 4d9450c0 261 tedMaxReservableBandwidth.2.3232235777.3232235778.16777264 4d9450c0 262 tedUnreservedBandwidthPri0.2.3232235777.3232235778.16777264 4d9450c0 263 tedUnreservedBandwidthPri1.2.3232235777.3232235778.16777264 4d9450c0 264 tedUnreservedBandwidthPri2.2.3232235777.3232235778.16777264 4d9450c0 265 tedUnreservedBandwidthPri3.2.3232235777.3232235778.16777264 4d9450c0 266 tedUnreservedBandwidthPri4.2.3232235777.3232235778.16777264 4d9450c0 267 tedUnreservedBandwidthPri5.2.3232235777.3232235778.16777264 4d9450c0 268 tedUnreservedBandwidthPri6.2.3232235777.3232235778.16777264 4d9450c0 269 tedUnreservedBandwidthPri7.2.3232235777.3232235778.16777264 4d9450c0 270 tedAdministrativeGroup.2.3232235777.3232235778.16777264 0 271 tedLocalId.2.3232235777.3232235778.16777264 0 272 tedRemoteId.2.3232235777.3232235778.16777264 0 273 tedLinkProtectionType.2.3232235777.3232235778.16777264 01 00 00 00 7 274 } 276 In tedLocalIfAddrTable: 277 { 278 tedLocalIfAddrType.16777264.192.0.2.21 ipv4(1) 279 } 281 In tedRemoteIfAddrTable: 282 { 283 tedRemoteIfAddrType.16777264.192.0.2.22 ipv4(1) 284 } 286 In tedSwCapTable: 287 { 288 tedSwCapType.16777264.1 lsc(150) 289 tedSwCapEncoding.16777264.1 ethernet(2) 290 tedSwCapMaxLspBandwidthPri0.16777264.1 4d9450c0 291 tedSwCapMaxLspBandwidthPri1.16777264.1 4d9450c0 292 tedSwCapMaxLspBandwidthPri2.16777264.1 4d9450c0 293 tedSwCapMaxLspBandwidthPri3.16777264.1 4d9450c0 294 tedSwCapMaxLspBandwidthPri4.16777264.1 4d9450c0 295 tedSwCapMaxLspBandwidthPri5.16777264.1 4d9450c0 296 tedSwCapMaxLspBandwidthPri6.16777264.1 4d9450c0 297 tedSwCapMaxLspBandwidthPri7.16777264.1 4d9450c0 298 tedSwCapMinLspBandwidth.16777264.1 0 299 tedSwCapIfMtu.16777264.1 0 300 tedSwCapIndication.16777264.1 standard(0) 301 } 303 In tedSrlgTable: 304 { 305 tedSrlg.16777264.1 0 306 } 308 7. TED MIB Definitions in support of GMPLS 310 This MIB module makes references to the follows documents. 312 [RFC2328], [RFC2578], [RFC2580], [RFC3630], [RFC4001], [RFC4203], 313 [RFC4220], [RFC4444], [RFC4801], [RFC4802], [RFC5305], [RFC5307], 314 [RFC5329], [RFC5340], [RFC6340] and [ISO10589]. 316 TED-MIB DEFINITIONS ::= BEGIN 318 IMPORTS 319 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission, 320 NOTIFICATION-TYPE 321 FROM SNMPv2-SMI -- RFC2578 322 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 323 FROM SNMPv2-CONF -- RFC2580 324 TEXTUAL-CONVENTION, RowPointer 325 FROM SNMPv2-TC -- RFC2579 326 IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC 327 FROM IANA-GMPLS-TC-MIB -- RFC4802 328 InetAddress, InetAddressType 329 FROM INET-ADDRESS-MIB -- RFC4001 330 Float32TC 331 FROM FLOAT-TC-MIB -- RFC6340 332 ; 334 tedMIB MODULE-IDENTITY 335 LAST-UPDATED "201211060000Z" -- 6 Nov. 2012 00:00:00 GMT 336 ORGANIZATION "IETF CCAMP Working Group." 337 CONTACT-INFO 338 " Tomohiro Otani 339 otani@kddilabs.jp 341 Masanori Miyazawa 342 ma-miyazawa@kddilabs.jp 344 Thomas D. Nadeau 345 tnadeau@lucidvision.com 347 Kenji Kumaki 348 ke-kumaki@kddilabs.jp 350 Comments and discussion to ccamp@ietf.org" 351 DESCRIPTION 352 "This MIB module contains managed object definitions for TED in 353 support of MPLS/GMPLS TE Database. 355 Copyright (C) 2012 The IETF Trust. This version of this MIB 356 module is part of RFC xxx; see the RFC itself for full legal 357 notices." 358 -- Revision history. 359 REVISION 360 "201211060000Z" -- 6 Nov. 2012 00:00:00 GMT 361 DESCRIPTION 362 "Initial version. Published as RFC xxx." 363 -- RFC-editor pls fill in yyy 364 ::= { transmission yyy } 365 -- assigned by IANA, see section 9.1 for details 367 -- Textual Conventions. 369 TedAreaIdTC ::= TEXTUAL-CONVENTION 370 STATUS current 371 DESCRIPTION 372 "The area identifier of the IGP. If OSPF is used to advertise 373 LSA, this represents an ospfArea. If ISIS is used, this 374 represents an area address." 375 SYNTAX OCTET STRING (SIZE (0..20)) 377 TedRouterIdTC ::= TEXTUAL-CONVENTION 378 STATUS current 379 DESCRIPTION 380 "The router identifier. If OSPF is used to advertise LSA, this 381 represents a Router ID. If ISIS is used, this represents a 382 System ID." 383 SYNTAX OCTET STRING (SIZE (0..6)) 385 TedLinkIndexTC ::= TEXTUAL-CONVENTION 386 STATUS current 387 DESCRIPTION 388 "The link identifier. If OSPF is used, this represents an 389 ospfLsdbID. If ISIS is used, this represents an isisLSPID. If a 390 locally configured link is used, this object represents an 391 arbitrary value which is locally defined in a router" 392 SYNTAX OCTET STRING (SIZE (0..8)) 394 -- Top level components of this MIB module. 396 tedNotifications OBJECT IDENTIFIER ::= { tedMIB 0 } 397 tedObjects OBJECT IDENTIFIER ::= { tedMIB 1 } 398 tedConformance OBJECT IDENTIFIER ::= { tedMIB 2 } 400 -- TED Table 402 tedTable OBJECT-TYPE 403 SYNTAX SEQUENCE OF TedEntry 404 MAX-ACCESS not-accessible 405 STATUS current 406 DESCRIPTION 407 "This table indicates multiple TED information which has been 408 supported by RFC3630 and RFC5305." 409 ::= { tedObjects 1 } 411 tedEntry OBJECT-TYPE 412 SYNTAX TedEntry 413 MAX-ACCESS not-accessible 414 STATUS current 415 DESCRIPTION 416 "This entry contains TED information commonly utilized in both 417 MPLS and GMPLS." 418 INDEX { tedLocalRouterId, tedRemoteRouterId, 419 tedLinkInformationSource, tedLinkIndex } 421 ::= { tedTable 1 } 423 TedEntry ::= SEQUENCE { 424 tedLinkInformationSource INTEGER, 425 tedLocalRouterId TedRouterIdTC, 426 tedRemoteRouterId TedRouterIdTC, 427 tedLinkIndex TedLinkIndexTC, 428 tedLinkInformationData RowPointer, 429 tedLinkState INTEGER, 430 tedAreaId TedAreaIdTC, 431 tedLinkType INTEGER, 432 tedTeRouterIdAddrType InetAddressType, 433 tedTeRouterIdAddr InetAddress, 434 tedLinkIdAddrType InetAddressType, 435 tedLinkIdAddr InetAddress, 436 tedMetric Integer32, 437 tedMaxBandwidth Float32TC, 438 tedMaxReservableBandwidth Float32TC, 439 tedUnreservedBandwidthPri0 Float32TC, 440 tedUnreservedBandwidthPri1 Float32TC, 441 tedUnreservedBandwidthPri2 Float32TC, 442 tedUnreservedBandwidthPri3 Float32TC, 443 tedUnreservedBandwidthPri4 Float32TC, 444 tedUnreservedBandwidthPri5 Float32TC, 445 tedUnreservedBandwidthPri6 Float32TC, 446 tedUnreservedBandwidthPri7 Float32TC, 447 tedAdministrativeGroup Integer32, 448 tedLocalId Integer32, 449 tedRemoteId Integer32, 450 tedLinkProtectionType BITS 451 } 453 tedLinkInformationSource OBJECT-TYPE 454 SYNTAX INTEGER { 455 unknown(0), 456 locallyConfigured(1), 457 ospfv2(2), 458 ospfv3(3), 459 isis(4), 460 other(5) 461 } 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "This object indicates the source of the information about the 466 TE link." 467 ::= { tedEntry 1 } 469 tedLocalRouterId OBJECT-TYPE 470 SYNTAX TedRouterIdTC 471 MAX-ACCESS not-accessible 472 STATUS current 473 DESCRIPTION 474 "This object represents the router ID of the router originating 475 the LSA. If OSPF is used to advertise LSA, this represents a 476 Router ID. If ISIS is used, this represents a System ID. 477 Otherwise, this represents zero." 478 REFERENCE 479 "OSPF Version 2, RFC2328, C.1 480 OSPF for IPv6, RFC5340, C.1 481 ISO10589, Section 7.1" 482 ::= { tedEntry 2 } 484 tedRemoteRouterId OBJECT-TYPE 485 SYNTAX TedRouterIdTC 486 MAX-ACCESS not-accessible 487 STATUS current 488 DESCRIPTION 489 "This object indicates the router at the remote end of the link 490 from the originating router. If OSPF is used to advertise LSA, 491 this represents a Link ID in the Link TLV. If ISIS is used, 492 this represents a neighbor system ID defined in RFC5305. 493 Otherwise, this represents zero." 494 REFERENCE 495 "OSPF Version 2, RFC2328, C.1 496 OSPF for IPv6, RFC5340, C.1 497 ISO10589, Section 7.1" 498 ::= { tedEntry 3 } 500 tedLinkIndex OBJECT-TYPE 501 SYNTAX TedLinkIndexTC 502 MAX-ACCESS not-accessible 503 STATUS current 504 DESCRIPTION 505 "This object indicates the link state identifier. If OSPF is 506 used, this represents an ospfLsdbID. If ISIS is used, this 507 represents an isisLSPID. Otherwise, this represents a unique 508 identifier within a node." 509 REFERENCE 510 "OSPF Version 2, RFC2328, A.4.1, 511 OSPF for IPv6, RFC5340, A.4.2 512 ISO10589, Section 9.8 " 513 ::= { tedEntry 4 } 515 tedLinkInformationData OBJECT-TYPE 516 SYNTAX RowPointer 517 MAX-ACCESS read-only 518 STATUS current 519 DESCRIPTION 520 "If tedLinkInformationSource has the value unknown(0), this 521 object MUST contain a value of zeroDotZero. 522 If tedLinkInformationSource has the value locallyConfigured(1), 523 an implementation can use this object to supply the identifier 524 of the corresponding row entry in the teLinkTable of TE-LINK- 525 STD-MIB (RFC 4220), the identifier of the corresponding row in 526 a local proprietary TE link MIB module, or the value of 527 zeroDotZero. 529 If tedLinkInformationSource has the value ospfv2(2)and 530 ospfv3(3), an implementation can use this object to supply the 531 identifier of the corresponding row entry in the 532 ospfLocalLsdbTable (OSPFv2-MIB) and the ospfv3AreaLsdbTable 533 (OSPFv3-MIB), or the value of zeroDotZero. 534 If tedLinkInformationSource has the value isis(4), an 535 implementation can use this object to supply the identifier of 536 the corresponding row entry in the isisAreaAddr of ISIS-MIB 537 (RFC4444), or the value of zeroDotZero. 538 If tedLinkInformationSource has the value other(5), an 539 implementation can use this object to supply the identifier of 540 the corresponding row entry in the local proprietary MIB module, 541 or the value of zeroDotZero." 542 ::= { tedEntry 5 } 544 tedLinkState OBJECT-TYPE 545 SYNTAX INTEGER { 546 unknown (0), 547 up (1), 548 down (2) 549 } 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "This object represents the actual operational state of this TE 554 link. For instance, if a row is created in the tedTable, but 555 the actual TE link is not available for some reason (e.g. when 556 there is not yet physical link or manually disable), then the 557 object would be down(2) state. In contrast, if a row is added 558 and the TE link is available, this would be operationally 559 up(1)." 560 ::= { tedEntry 6 } 562 tedAreaId OBJECT-TYPE 563 SYNTAX TedAreaIdTC 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "This object indicates the area identifier of the IGP. If OSPF 568 is used to advertise LSA, this represents an ospfArea. If ISIS 569 is used, this represents an area address. Otherwise, this 570 represents zero." 571 REFERENCE 572 "OSPF Version 2, RFC2328, C.2 573 OSPF for IPv6, RFC5340, C.2 574 ISO10589, Section 9.8" 575 ::= { tedEntry 7 } 577 tedLinkType OBJECT-TYPE 578 SYNTAX INTEGER { 579 pointToPoint (1), 580 multiAccess (2) 581 } 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "This indicates the type of the link such as point-to-point or 586 multi-access." 587 REFERENCE 588 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 589 3630, 2.5.1" 590 ::= { tedEntry 8 } 592 tedTeRouterIdAddrType OBJECT-TYPE 593 SYNTAX InetAddressType 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "This object indicates the TE-Router ID address type. Only 598 values unknown(0), ipv4(1) or ipv6(2) are supported. " 599 ::= { tedEntry 9 } 601 tedTeRouterIdAddr OBJECT-TYPE 602 SYNTAX InetAddress 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "This object indicates the TE-Router ID." 607 REFERENCE 608 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 609 3630, 2.4.1 610 IS-IS extensions for TE, RFC5305, 4.3" 611 ::= { tedEntry 10 } 613 tedLinkIdAddrType OBJECT-TYPE 614 SYNTAX InetAddressType 615 MAX-ACCESS read-only 616 STATUS current 617 DESCRIPTION 618 "This object indicates the address type of the TE Link ID. Only 619 values unknown(0), ipv4(1) or ipv6(2) are supported." 620 ::= { tedEntry 11 } 622 tedLinkIdAddr OBJECT-TYPE 623 SYNTAX InetAddress 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "This indicates the Router ID of the neighbor in the case of 628 point-to-point links. This also indicates the interface 629 address of the designated router in the case of multi-access 630 links." 631 REFERENCE 632 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 633 3630, 2.5.2 634 IS-IS extensions for TE, RFC5305, 4.3" 635 ::= { tedEntry 12 } 636 tedMetric OBJECT-TYPE 637 SYNTAX Integer32 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "This indicates the traffic engineering metric value of the TE 642 link." 643 REFERENCE 644 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 645 3630, 2.5.5 646 IS-IS extensions for TE, RFC5305, 3.7" 647 ::= { tedEntry 13 } 649 tedMaxBandwidth OBJECT-TYPE 650 SYNTAX Float32TC 651 UNITS "Byte per second" 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "This indicates the maximum bandwidth that can be used on this 656 link in this direction." 657 REFERENCE 658 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 659 3630, 2.5.6 660 IS-IS extensions for TE, RFC5305, 3.4" 661 ::= { tedEntry 14 } 663 tedMaxReservableBandwidth OBJECT-TYPE 664 SYNTAX Float32TC 665 UNITS "Byte per second" 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "This indicates the maximum bandwidth that may be reserved on 670 this link in this direction." 671 REFERENCE 672 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 673 3630, 2.5.7 674 IS-IS extensions for TE, RFC5305, 3.5" 675 ::= { tedEntry 15 } 677 tedUnreservedBandwidthPri0 OBJECT-TYPE 678 SYNTAX Float32TC 679 UNITS "Byte per second" 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "This indicates the amount of bandwidth not yet reserved at the 684 priority 0." 685 REFERENCE 686 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 687 3630, 2.5.8 688 IS-IS extensions for TE, RFC5305, 3.6" 689 ::= { tedEntry 16 } 690 tedUnreservedBandwidthPri1 OBJECT-TYPE 691 SYNTAX Float32TC 692 UNITS "Byte per second" 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "This indicates the amount of bandwidth not yet reserved at the 697 priority 1." 698 REFERENCE 699 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 700 3630, 2.5.8 701 IS-IS extensions for TE, RFC5305, 3.6" 702 ::= { tedEntry 17 } 704 tedUnreservedBandwidthPri2 OBJECT-TYPE 705 SYNTAX Float32TC 706 UNITS "Byte per second" 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "This indicates the amount of bandwidth not yet reserved at the 711 priority 2." 712 REFERENCE 713 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 714 3630, 2.5.8 715 IS-IS extensions for TE, RFC5305, 3.6" 716 ::= { tedEntry 18 } 718 tedUnreservedBandwidthPri3 OBJECT-TYPE 719 SYNTAX Float32TC 720 UNITS "Byte per second" 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "This indicates the amount of bandwidth not yet reserved at the 725 priority 3." 726 REFERENCE 727 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 728 3630, 2.5.8 729 IS-IS extensions for TE, RFC5305, 3.6" 730 ::= { tedEntry 19 } 732 tedUnreservedBandwidthPri4 OBJECT-TYPE 733 SYNTAX Float32TC 734 UNITS "Byte per second" 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "This indicates the amount of bandwidth not yet reserved at the 739 priority 4." 740 REFERENCE 741 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 742 3630, 2.5.8 743 IS-IS extensions for TE, RFC5305, 3.6" 744 ::= { tedEntry 20 } 746 tedUnreservedBandwidthPri5 OBJECT-TYPE 747 SYNTAX Float32TC 748 UNITS "Byte per second" 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "This indicates the amount of bandwidth not yet reserved at the 753 priority 5." 754 REFERENCE 755 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 756 3630, 2.5.8 757 IS-IS extensions for TE, RFC5305, 3.6" 758 ::= { tedEntry 21 } 760 tedUnreservedBandwidthPri6 OBJECT-TYPE 761 SYNTAX Float32TC 762 UNITS "Byte per second" 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "This indicates the amount of bandwidth not yet reserved at the 767 priority 6." 768 REFERENCE 769 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 770 3630, 2.5.8 771 IS-IS extensions for TE, RFC5305, 3.6" 772 ::= { tedEntry 22 } 774 tedUnreservedBandwidthPri7 OBJECT-TYPE 775 SYNTAX Float32TC 776 UNITS "Byte per second" 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "This indicates the amount of bandwidth not yet reserved at the 781 priority 7." 782 REFERENCE 783 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 784 3630, 2.5.8 785 IS-IS extensions for TE, RFC5305, 3.6" 786 ::= { tedEntry 23 } 788 tedAdministrativeGroup OBJECT-TYPE 789 SYNTAX Integer32 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "This indicates the Administrative Group which the link belong 794 to. Since the value is a bit mask, the link can belong to 795 multiple groups. This is also called Resource Class/Color." 796 REFERENCE 797 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 798 3630, 2.5.9 799 IS-IS extensions for TE, RFC5305, 3.1" 800 ::= { tedEntry 24 } 802 tedLocalId OBJECT-TYPE 803 SYNTAX Integer32 804 MAX-ACCESS read-only 805 STATUS current 806 DESCRIPTION 807 "This indicates the Link local identifier of an unnumbered 808 link." 809 REFERENCE 810 "OSPF Extensions in Support of GMPLS, RFC4203, 1.1 811 IS-IS Extensions in Support of GMPLS, RFC5307, 1.1" 812 ::= { tedEntry 25 } 814 tedRemoteId OBJECT-TYPE 815 SYNTAX Integer32 816 MAX-ACCESS read-only 817 STATUS current 818 DESCRIPTION 819 "This indicates the Link remote identifier of an unnumbered 820 link." 821 REFERENCE 822 "OSPF Extensions in Support of GMPLS, RFC4203, 1.1 823 IS-IS Extensions in Support of GMPLS, RFC5307, 1.1" 824 ::= { tedEntry 26 } 826 tedLinkProtectionType OBJECT-TYPE 827 SYNTAX BITS { 828 extraTraffic(0), 829 unprotected(1), 830 shared (2), 831 dedicatedOneToOne (3), 832 dedicatedOnePlusOne(4), 833 enhanced(5) 834 } 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "This object indicates the protection type of the TE link." 839 REFERENCE 840 "OSPF Extensions in Support of GMPLS, RFC4203, 1.2 841 IS-IS Extensions in Support of GMPLS, RFC5307, 1.2" 842 ::= { tedEntry 27 } 844 -- TED Local Interface IP Address Table 846 tedLocalIfAddrTable OBJECT-TYPE 847 SYNTAX SEQUENCE OF TedLocalIfAddrEntry 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "This table contains the IP address information of a local TE 852 link." 853 ::= { tedObjects 2 } 855 tedLocalIfAddrEntry OBJECT-TYPE 856 SYNTAX TedLocalIfAddrEntry 857 MAX-ACCESS not-accessible 858 STATUS current 859 DESCRIPTION 860 "This entry contains the IP address information of the local TE 861 link." 862 INDEX { tedLinkIndex, tedLocalIfAddr } 863 ::= { tedLocalIfAddrTable 1 } 865 TedLocalIfAddrEntry ::= SEQUENCE { 866 tedLocalIfAddrType InetAddressType, 867 tedLocalIfAddr InetAddress 868 } 870 tedLocalIfAddrType OBJECT-TYPE 871 SYNTAX InetAddressType 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "This object indicates the address type of the local TE link. 876 Only values unknown(0), ipv4(1) or ipv6(2) have to be 877 supported." 878 ::= { tedLocalIfAddrEntry 1 } 880 tedLocalIfAddr OBJECT-TYPE 881 SYNTAX InetAddress (SIZE (1..20)) 882 MAX-ACCESS not-accessible 883 STATUS current 884 DESCRIPTION 885 "This object indicates the address of the local TE link." 886 REFERENCE 887 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC3630, 888 2.5.3, 889 Traffic Engineering Extensions to OSPF Version3, RFC5329, 4.3 890 IS-IS extensions for TE, RFC5305, 3.4" 891 ::= { tedLocalIfAddrEntry 2 } 893 -- TED Remote Interface IP Address Table 895 tedRemoteIfAddrTable OBJECT-TYPE 896 SYNTAX SEQUENCE OF TedRemoteIfAddrEntry 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "This table contains the IP address information of a remote TE 901 link." 902 ::= { tedObjects 3 } 904 tedRemoteIfAddrEntry OBJECT-TYPE 905 SYNTAX TedRemoteIfAddrEntry 906 MAX-ACCESS not-accessible 907 STATUS current 908 DESCRIPTION 909 "This entry contains the IP address information of the remote 910 TE link." 911 INDEX { tedLinkIndex, tedRemoteIfAddr } 912 ::= { tedRemoteIfAddrTable 1 } 914 TedRemoteIfAddrEntry ::= SEQUENCE { 915 tedRemoteIfAddrType InetAddressType, 916 tedRemoteIfAddr InetAddress 917 } 919 tedRemoteIfAddrType OBJECT-TYPE 920 SYNTAX InetAddressType 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "This object indicates the address type of the remote TE link." 925 ::= { tedRemoteIfAddrEntry 1 } 927 tedRemoteIfAddr OBJECT-TYPE 928 SYNTAX InetAddress(SIZE (1..20)) 929 MAX-ACCESS not-accessible 930 STATUS current 931 DESCRIPTION 932 "This object indicates the address of the remote TE link." 933 REFERENCE 934 "Traffic Engineering (TE) Extensions to OSPF Version 2, RFC 935 3630, 2.5.4, 936 Traffic Engineering Extensions to OSPF Version3, RFC5329, 4.4 937 IS-IS extensions for TE, RFC5305, 3.3" 938 ::= { tedRemoteIfAddrEntry 2 } 940 -- TED Switching Capability Table 942 tedSwCapTable OBJECT-TYPE 943 SYNTAX SEQUENCE OF TedSwCapEntry 944 MAX-ACCESS not-accessible 945 STATUS current 946 DESCRIPTION 947 "This table contains the GMPLS TED switching capability 948 information." 949 ::= { tedObjects 4 } 951 tedSwCapEntry OBJECT-TYPE 952 SYNTAX TedSwCapEntry 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "This entry relates each TE link with its GMPLS TE switching 957 capability information. If the MIB module deals with only OSPF- 958 TE information, the value of each object related with GMPLS TE 959 extensions should be null." 960 INDEX { tedLinkIndex, tedSwCapIndex } 961 ::= { tedSwCapTable 1 } 963 TedSwCapEntry ::= SEQUENCE { 964 tedSwCapIndex Unsigned32, 965 tedSwCapType IANAGmplsSwitchingTypeTC, 966 tedSwCapEncoding IANAGmplsLSPEncodingTypeTC, 967 tedSwCapMaxLspBandwidthPri0 Float32TC, 968 tedSwCapMaxLspBandwidthPri1 Float32TC, 969 tedSwCapMaxLspBandwidthPri2 Float32TC, 970 tedSwCapMaxLspBandwidthPri3 Float32TC, 971 tedSwCapMaxLspBandwidthPri4 Float32TC, 972 tedSwCapMaxLspBandwidthPri5 Float32TC, 973 tedSwCapMaxLspBandwidthPri6 Float32TC, 974 tedSwCapMaxLspBandwidthPri7 Float32TC, 975 tedSwCapMinLspBandwidth Float32TC, 976 tedSwCapIfMtu Integer32, 977 tedSwCapIndication INTEGER 978 } 980 tedSwCapIndex OBJECT-TYPE 981 SYNTAX Unsigned32 (1..255) 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "This index is utilized to identify multiple switching 986 functions on a local or remote TE link according to definitions 987 of textual conventions of GMPLS, RFC4801." 988 ::= { tedSwCapEntry 1 } 990 tedSwCapType OBJECT-TYPE 991 SYNTAX IANAGmplsSwitchingTypeTC 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "This object indicates the GMPLS switching capability assigned 996 to the TE link according to definitions of textual conventions 997 of GMPLS, RFC4801." 998 REFERENCE 999 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1000 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1001 ::= { tedSwCapEntry 2 } 1003 tedSwCapEncoding OBJECT-TYPE 1004 SYNTAX IANAGmplsLSPEncodingTypeTC 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "This object indicates the GMPLS encoding type assigned to the 1009 TE link." 1010 REFERENCE 1011 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1012 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1013 ::= { tedSwCapEntry 3 } 1015 tedSwCapMaxLspBandwidthPri0 OBJECT-TYPE 1016 SYNTAX Float32TC 1017 UNITS "Byte per second" 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "This object indicates the maximum bandwidth of the TE link at 1022 the priority 0 for GMPLS LSP creation." 1023 REFERENCE 1024 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1025 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1026 ::= { tedSwCapEntry 4 } 1028 tedSwCapMaxLspBandwidthPri1 OBJECT-TYPE 1029 SYNTAX Float32TC 1030 UNITS "Byte per second" 1031 MAX-ACCESS read-only 1032 STATUS current 1033 DESCRIPTION 1034 "This object indicates the maximum bandwidth of the TE link at 1035 the priority 1 for GMPLS LSP creation." 1036 REFERENCE 1037 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1038 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1039 ::= { tedSwCapEntry 5 } 1041 tedSwCapMaxLspBandwidthPri2 OBJECT-TYPE 1042 SYNTAX Float32TC 1043 UNITS "Byte per second" 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "This object indicates the maximum bandwidth of the TE link at 1048 the priority 2 for GMPLS LSP creation." 1049 REFERENCE 1050 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1051 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1052 ::= { tedSwCapEntry 6 } 1054 tedSwCapMaxLspBandwidthPri3 OBJECT-TYPE 1055 SYNTAX Float32TC 1056 UNITS "Byte per second" 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "This object indicates the maximum bandwidth of the TE link at 1061 the priority 3 for GMPLS LSP creation." 1062 REFERENCE 1063 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1064 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1065 ::= { tedSwCapEntry 7 } 1066 tedSwCapMaxLspBandwidthPri4 OBJECT-TYPE 1067 SYNTAX Float32TC 1068 UNITS "Byte per second" 1069 MAX-ACCESS read-only 1070 STATUS current 1071 DESCRIPTION 1072 "This object indicates the maximum bandwidth of the TE link at 1073 the priority 4 for GMPLS LSP creation." 1074 REFERENCE 1075 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1076 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1077 ::= { tedSwCapEntry 8 } 1079 tedSwCapMaxLspBandwidthPri5 OBJECT-TYPE 1080 SYNTAX Float32TC 1081 UNITS "Byte per second" 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "This object indicates the maximum bandwidth of the TE link at 1086 the priority 5 for GMPLS LSP creation." 1087 REFERENCE 1088 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1089 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1090 ::= { tedSwCapEntry 9 } 1092 tedSwCapMaxLspBandwidthPri6 OBJECT-TYPE 1093 SYNTAX Float32TC 1094 UNITS "Byte per second" 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "This object indicates the maximum bandwidth of the TE link at 1099 the priority 6 for GMPLS LSP creation." 1100 REFERENCE 1101 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1102 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1103 ::= { tedSwCapEntry 10 } 1105 tedSwCapMaxLspBandwidthPri7 OBJECT-TYPE 1106 SYNTAX Float32TC 1107 UNITS "Byte per second" 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "This object indicates the maximum bandwidth of the TE link at 1112 the priority 7 for GMPLS LSP creation." 1113 REFERENCE 1114 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1115 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1116 ::= { tedSwCapEntry 11 } 1118 tedSwCapMinLspBandwidth OBJECT-TYPE 1119 SYNTAX Float32TC 1120 UNITS "Byte per second" 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "This object indicates the minimum bandwidth of the TE link for 1125 GMPLS LSP creation if the switching capability field is TDM, 1126 PSC-1, PSC-2, PSC-3, or PSC-4." 1127 REFERENCE 1128 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1129 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1130 ::= { tedSwCapEntry 12 } 1132 tedSwCapIfMtu OBJECT-TYPE 1133 SYNTAX Integer32 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "This object indicates the MTU of the local or remote TE link." 1138 REFERENCE 1139 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1140 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1141 ::= { tedSwCapEntry 13 } 1143 tedSwCapIndication OBJECT-TYPE 1144 SYNTAX INTEGER { 1145 standard (0), 1146 arbitrary (1) 1147 } 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "This object indicates whether the interface supports Standard 1152 or Arbitrary SONET SDH." 1153 REFERENCE 1154 "OSPF Extensions in Support of GMPLS, RFC4203, 1.4 1155 IS-IS Extensions in Support of GMPLS, RFC5307, 1.3" 1156 ::= { tedSwCapEntry 14 } 1158 -- TED SRLG Table 1160 tedSrlgTable OBJECT-TYPE 1161 SYNTAX SEQUENCE OF TedSrlgEntry 1162 MAX-ACCESS not-accessible 1163 STATUS current 1164 DESCRIPTION 1165 "This table contains the SRLG information of the TE link." 1166 ::= { tedObjects 5 } 1168 tedSrlgEntry OBJECT-TYPE 1169 SYNTAX TedSrlgEntry 1170 MAX-ACCESS not-accessible 1171 STATUS current 1172 DESCRIPTION 1173 "This entry relates each TE link with its SRLG information." 1174 INDEX { tedLinkIndex, tedSrlgIndex } 1175 ::= { tedSrlgTable 1 } 1177 TedSrlgEntry ::= SEQUENCE { 1178 tedSrlgIndex Unsigned32, 1179 tedSrlg Integer32 1180 } 1182 tedSrlgIndex OBJECT-TYPE 1183 SYNTAX Unsigned32(1..255) 1184 MAX-ACCESS not-accessible 1185 STATUS current 1186 DESCRIPTION 1187 "This index is utilized to identify multiple SRLG values on a 1188 local or remote TE link. This object represents an arbitrary 1189 value which is locally defined in a router." 1190 REFERENCE 1191 "OSPF Extensions in support of GMPLS, RFC4203, 1.3 1192 IS-IS Extensions in Support of GMPLS, RFC5307, 1.4" 1193 ::= { tedSrlgEntry 1 } 1195 tedSrlg OBJECT-TYPE 1196 SYNTAX Integer32 1197 MAX-ACCESS read-only 1198 STATUS current 1199 DESCRIPTION 1200 "This object indicate the SRLG value assigned to a local or 1201 remote TE link" 1202 REFERENCE 1203 "OSPF Extensions in Support of GMPLS, RFC4203, 1.3 1204 IS-IS Extensions in Support of GMPLS, RFC5307, 1.4" 1205 ::= { tedSrlgEntry 2 } 1207 -- Notification Configuration 1209 tedStatusChangeNotificationMaxRate OBJECT-TYPE 1210 SYNTAX Unsigned32 1211 MAX-ACCESS read-write 1212 STATUS current 1213 DESCRIPTION 1214 "A lot of notifications relating to the status change are 1215 expected to generate in a node, especially when a network 1216 failure occurs and might cause a performance degradation of the 1217 node itself. To avoid such a defect, this object provides the 1218 maximum number of notifications generated per minute. If 1219 events occur more rapidly, the implementation may simply fail 1220 to emit these notifications during that period, or may queue 1221 them until an appropriate time. A value of 0 means no 1222 throttling is applied and events may be notified at the rate at 1223 which they occur." 1224 DEFVAL {1} 1225 ::= { tedObjects 6 } 1226 tedCreatedDeletedNotificationMaxRate OBJECT-TYPE 1227 SYNTAX Unsigned32 1228 MAX-ACCESS read-write 1229 STATUS current 1230 DESCRIPTION 1231 "A lot of notifications relating to new registration in ted 1232 table by receiving new TE link information or deletion of 1233 existing entries in ted table are expected to generate in a 1234 node. This object provides the maximum number of notifications 1235 generated per minute." 1236 DEFVAL {1} 1237 ::= { tedObjects 7 } 1239 -- Notifications 1241 tedStatusChange NOTIFICATION-TYPE 1242 OBJECTS { 1243 tedLinkState 1244 } 1245 STATUS current 1246 DESCRIPTION 1247 "This notification signifies that there has been change in TE 1248 information of tedTable, tedLocalIfAddrTable, 1249 tedRemoteIfAddrTable, tedSwCapTable and/or tedSrlgTable. For 1250 example, this should be generated when tedUnreservedBandwidth 1251 is changed to create or delete LSP using registered TE link. " 1252 ::= { tedNotifications 1 } 1254 tedEntryCreated NOTIFICATION-TYPE 1255 OBJECTS { 1256 tedLinkState 1257 } 1258 STATUS current 1259 DESCRIPTION 1260 "This notification signifies that there has been new 1261 registration in ted table by receiving new TE link information. 1262 For example, this should be generated when new index 1263 (tedLinkIndex) is registered in TED table." 1264 ::= { tedNotifications 2 } 1266 tedEntryDeleted NOTIFICATION-TYPE 1267 OBJECTS { 1268 tedLinkState 1269 } 1270 STATUS current 1271 DESCRIPTION 1272 "This notification signifies that there has been deletion of an 1273 entry in the ted table. For example, this should be generated 1274 when one of existing entries is deleted in TED table." 1275 ::= { tedNotifications 3 } 1277 -- Conformance Statement 1279 tedCompliances 1280 OBJECT IDENTIFIER ::= { tedConformance 1 } 1281 tedGroups 1282 OBJECT IDENTIFIER ::= { tedConformance 2 } 1284 -- Module Compliance 1286 tedModuleFullCompliance MODULE-COMPLIANCE 1287 STATUS current 1288 DESCRIPTION 1289 "Compliance statement for agents provides full support for the 1290 TED MIB." 1291 MODULE -- this module 1292 MANDATORY-GROUPS { tedMainGroup, 1293 tedObjectsGroup, 1294 tedNotificationGroup 1295 } 1297 GROUP tedUnnumberedLinkGroup 1298 DESCRIPTION 1299 "This group is mandatory for TE links that supports the 1300 unnumbered links." 1302 GROUP tedNumberedLinkGroup 1303 DESCRIPTION 1304 "This group is mandatory for TE links that supports the 1305 numbered links." 1307 GROUP tedSwCapGroup 1308 DESCRIPTION 1309 "This group is mandatory for TE links that supports GMPLS 1310 switching capability." 1312 GROUP tedSwCapMinLspBandwidthGroup 1313 DESCRIPTION 1314 "This group is mandatory for TE links if the switching 1315 capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4." 1317 GROUP tedSwCapIfMtuGroup 1318 DESCRIPTION 1319 "This group is mandatory for TE links that supports the MTU of 1320 the local or remote TE link." 1322 GROUP tedSwCapIndicationGroup 1323 DESCRIPTION 1324 "This group is mandatory for TE links that supports Standard or 1325 Arbitrary SONET/SDH." 1327 GROUP tedSrlgGroup 1328 DESCRIPTION 1329 "This group is mandatory for TE links that supports SRLG 1330 information." 1332 ::= { tedCompliances 1 } 1333 -- 1334 -- ReadOnly Compliance 1335 -- 1337 tedModuleReadOnlyCompliance MODULE-COMPLIANCE 1338 STATUS current 1339 DESCRIPTION 1340 "Compliance requirement for implementations only provide read- 1341 only support for TED. Such devices can then be monitored but 1342 cannot be configured using this MIB module." 1343 MODULE -- this module 1344 MANDATORY-GROUPS { tedMainGroup 1345 } 1347 GROUP tedUnnumberedLinkGroup 1348 DESCRIPTION 1349 "This group is mandatory for TE links that supports the 1350 unnumbered links." 1352 GROUP tedNumberedLinkGroup 1353 DESCRIPTION 1354 "This group is mandatory for TE links that supports the 1355 numbered links." 1357 GROUP tedSwCapGroup 1358 DESCRIPTION 1359 "This group is mandatory for TE links that supports some GMPLS 1360 switching capabilities." 1362 GROUP tedSwCapMinLspBandwidthGroup 1363 DESCRIPTION 1364 "This group is mandatory for TE links if the switching 1365 capability field is TDM, PSC-1, PSC-2, PSC-3, or PSC-4." 1367 GROUP tedSwCapIfMtuGroup 1368 DESCRIPTION 1369 "This group is mandatory for TE links that supports the MTU of 1370 the local or remote TE link." 1372 GROUP tedSwCapIndicationGroup 1373 DESCRIPTION 1374 "This group is mandatory for TE links that supports Standard or 1375 Arbitrary SONET/SDH." 1377 GROUP tedSrlgGroup 1378 DESCRIPTION 1379 "This group is mandatory for TE links that supports SRLG 1380 information." 1382 ::= { tedCompliances 2 } 1384 -- Units of conformance 1386 tedMainGroup OBJECT-GROUP 1387 OBJECTS { 1388 tedLinkState , 1389 tedAreaId , 1390 tedLinkType , 1391 tedTeRouterIdAddrType , 1392 tedTeRouterIdAddr , 1393 tedLinkIdAddrType , 1394 tedLinkIdAddr , 1395 tedMetric , 1396 tedMaxBandwidth , 1397 tedMaxReservableBandwidth , 1398 tedUnreservedBandwidthPri0 , 1399 tedUnreservedBandwidthPri1 , 1400 tedUnreservedBandwidthPri2 , 1401 tedUnreservedBandwidthPri3 , 1402 tedUnreservedBandwidthPri4 , 1403 tedUnreservedBandwidthPri5 , 1404 tedUnreservedBandwidthPri6 , 1405 tedUnreservedBandwidthPri7 , 1406 tedAdministrativeGroup , 1407 tedLinkProtectionType , 1408 tedLinkInformationData 1409 } 1410 STATUS current 1411 DESCRIPTION 1412 "Collection of objects for TED management" 1413 ::= { tedGroups 1 } 1415 tedObjectsGroup OBJECT-GROUP 1416 OBJECTS { 1417 tedStatusChangeNotificationMaxRate, 1418 tedCreatedDeletedNotificationMaxRate 1419 } 1420 STATUS current 1421 DESCRIPTION 1422 "This objects needed to implement notification." 1423 ::= { tedGroups 2 } 1425 tedNotificationGroup NOTIFICATION-GROUP 1426 NOTIFICATIONS { 1427 tedStatusChange, 1428 tedEntryCreated, 1429 tedEntryDeleted 1430 } 1431 STATUS current 1432 DESCRIPTION 1433 "This group is mandatory for those implementations that can 1434 implement the notifications contained in this group." 1435 ::= { tedGroups 3 } 1437 tedUnnumberedLinkGroup OBJECT-GROUP 1438 OBJECTS { 1439 tedLocalId, 1440 tedRemoteId 1442 } 1443 STATUS current 1444 DESCRIPTION 1445 "This objects needed to implement the unnumbered links." 1446 ::= { tedGroups 4 } 1448 tedNumberedLinkGroup OBJECT-GROUP 1449 OBJECTS { 1450 tedLocalIfAddrType, 1451 tedRemoteIfAddrType 1452 } 1453 STATUS current 1454 DESCRIPTION 1455 "This objects needed to implement the numbered links." 1456 ::= { tedGroups 5 } 1458 tedSwCapGroup OBJECT-GROUP 1459 OBJECTS { 1460 tedSwCapType, 1461 tedSwCapEncoding, 1462 tedSwCapMaxLspBandwidthPri0, 1463 tedSwCapMaxLspBandwidthPri1, 1464 tedSwCapMaxLspBandwidthPri2, 1465 tedSwCapMaxLspBandwidthPri3, 1466 tedSwCapMaxLspBandwidthPri4, 1467 tedSwCapMaxLspBandwidthPri5, 1468 tedSwCapMaxLspBandwidthPri6, 1469 tedSwCapMaxLspBandwidthPri7 1470 } 1471 STATUS current 1472 DESCRIPTION 1473 "This objects needed to implement TE links with its GMPLS TE 1474 switching capability information." 1475 ::= { tedGroups 6 } 1477 tedSwCapMinLspBandwidthGroup OBJECT-GROUP 1478 OBJECTS { 1479 tedSwCapMinLspBandwidth 1480 } 1481 STATUS current 1482 DESCRIPTION 1483 "This objects needed to implement the minimum bandwidth of the 1484 TE link for GMPLS LSP creation." 1485 ::= { tedGroups 7 } 1487 tedSwCapIfMtuGroup OBJECT-GROUP 1488 OBJECTS { 1489 tedSwCapIfMtu 1490 } 1491 STATUS current 1492 DESCRIPTION 1493 "This objects needed to implement the MTU information of the 1494 local or remote TE link." 1495 ::= { tedGroups 8 } 1496 tedSwCapIndicationGroup OBJECT-GROUP 1497 OBJECTS { 1498 tedSwCapIndication 1499 } 1500 STATUS current 1501 DESCRIPTION 1502 "This objects needed to implement the indication whether the 1503 interface supports Standard or Arbitrary SONET/SDH." 1504 ::= { tedGroups 9 } 1506 tedSrlgGroup OBJECT-GROUP 1507 OBJECTS { 1508 tedSrlg 1509 } 1510 STATUS current 1511 DESCRIPTION 1512 "This objects needed to implement multiple SRLG values with 1513 GMPLS TE information." 1514 ::= { tedGroups 10 } 1516 END 1518 8. Security Consideration 1520 There are several objects defined in this MIB module that has a MAX- 1521 ACCESS clause of read-write. Such objects may be considered sensitive 1522 or vulnerable in some network environments. The support for SET 1523 operations in a non-secure environment without proper protection can 1524 have a negative effect on network operations. 1526 Some of the readable objects in this MIB module (i.e., objects with a 1527 MAX-ACCESS other than not-accessible) may be considered sensitive or 1528 vulnerable in some network environments. It is thus important to 1529 control even GET and/or NOTIFY access to these objects and possibly 1530 to even encrypt the values of these objects when sending them over 1531 the network via SNMP. These are the tables and objects and their 1532 sensitivity/vulnerability: tedTable, tedLocalIfAddrTable, 1533 tedRemoteIfAddrTable, tedSwCapTable and tedSrlgTable contain topology 1534 information for the MPLS/GMPLS network. If an administrator does not 1535 want to reveal this information, then these tables should be 1536 considered sensitive/vulnerable. 1538 There are only two write-access objects in this MIB module: 1539 tedStatusChangeNotificationMaxRate and 1540 tedCreatedDeletedNotificationMaxRate. Malicious modification of 1541 these objects could cause the management agent, the network, or the 1542 router to become overloaded with Notifications in cases of high churn 1543 within the network. 1545 SNMP versions prior to SNMPv3 did not include adequate security. Even 1546 if the network itself is secure (for example by using IPsec), even 1547 then, there is no control as to who on the secure network is allowed 1548 to access and GET/SET (read/change/create/delete) the objects in this 1549 MIB module. 1551 Implementations MUST provide the security features described by the 1552 SNMPv3 framework (see [RFC3410]), including full support for 1553 authentication and privacy via the User-based Security Model (USM) 1554 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1555 MAY also provide support for the Transport Security Model (TSM) 1556 [RFC5591] in combination with a secure transport such as SSH 1557 [RFC5592] or TLS/DTLS [RFC6353]. 1558 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1559 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1560 enable cryptographic security. It is then a customer/operator 1561 responsibility to ensure that the SNMP entity giving access to an 1562 instance of this MIB module is properly configured to give access to 1563 the objects only to those principles (users) that have legitimate 1564 rights to indeed GET or SET (change/create/delete) them. 1566 9. IANA Considerations 1568 The following "IANA Considerations" subsection requests IANA for a 1569 new assignment under the transmission subtree. New assignments can 1570 only be made via a Standards Action as specified in [RFC5226]. 1572 9.1 IANA Considerations for TED-MIB 1574 The IANA is requested to assign {transmission yyy} to the TED-MIB 1575 module specified in this document. 1577 10. References 1578 10.1 Normative References 1580 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1581 Requirement Levels", BCP 14, RFC 2119, March 1997. 1583 [RFC2328] J. Moy, " OSPF version2 ", RFC2328, April 1998. 1585 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1586 "Structure of Management Information Version 2 (SMIv2)", 1587 STD 58, RFC 2578, April 1999. 1589 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1590 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1591 1999. 1593 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1594 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1595 April 1999. 1597 [RFC4001] M. Daniele, B. Haberman, S. Routhier, J. Schoenwaelder, 1598 "Textual Conventions for Internet Network Addresses", 1599 RFC4001, Feb. 2005. 1600 [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions to 1601 OSPF Version2", RFC3630, Sep. 2003. 1603 [RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in Support 1604 of Generalized Multi-Protocol Label Switching", RFC4203, 1605 Oct. 2005. 1607 [RFC4750] Dan Joyal, et al, "OSPF Version 2 Management Information 1608 Base", RFC4750, Dec. 2006. 1610 [RFC4801] T. D. Nadeau and A. Farrel, Ed., "Definitions of Textual 1611 Conventions for Generalized Multiprotocol Label Switching 1612 (GMPLS) Management", RFC4801, Feb. 2007. 1614 [RFC5329] K. Ishiguro, V. Manral, A. Davey, A.Lindem " Traffic 1615 Engineering Extensions to OSPF Version 3 ", RFC5329, Sep. 1616 2008. 1618 [RFC5340] R. Coltun, D. Ferguson, J. Moy, A.Lindem " OSPF for IPv6", 1619 RFC5340, July 2008. 1621 [RFC5643] Dan Joyal, et al, "Management Information Base for OSPFv3 1622 ", RFC5643, August 2009. 1624 [RFC6340] R. Presuhn, "Textual Conventions for the Representation of 1625 Floating-point Number ", RFC6340, August 2011. 1627 10.2 Informative References 1629 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 1630 and Applicability Statement for Internet Standard 1631 Management Framework", RFC 3410, Dec. 2002. 1633 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 1634 (USM) for version 3 of the Simple Network Management 1635 Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. 1637 [RFC3812] Srinivasan, C., Viswanathan, A., and T. D. Nadeau, 1638 "Multiprotocol Label Switching (MPLS) Traffic Engineering 1639 (TE) Management Information Base (MIB)", RFC 3812, June 1640 2004. 1642 [RFC3813] Srinivasan, C., Viswanathan, A., and T. D. Nadeau, 1643 "Multiprotocol Label Switching (MPLS) Label Switching 1644 (LSR) Router Management Information Base (MIB)", RFC 3813, 1645 June 2004. 1647 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 1648 Advanced Encryption Standard (AES) Cipher Algorithm in the 1649 SNMP User-based Security Model", RFC 3826, June 2004. 1651 [RFC3945] E. Mannie, "Generalized Multi-Procol Label Switching 1652 (MPLS) Architecture", RFC3945, Oct. 2004. 1654 [RFC4202] K. Kompella, and Y. Rekhter, "Routing Extensions in 1655 Support of Generalized Multi-Protocol Label Switching", 1656 RFC4202, Oct. 2005. 1658 [RFC4220] M. Dubuc, T. D. Nadeau and J. Lang, "Traffic Engineering 1659 Link Management Information Base", RFC4220, Dec. 2005. 1661 [RFC4377] T. D. Nadeau, et al, "Operations and Management (OAM) 1662 Requirements for Multi-Protocol Label Switched (MPLS) 1663 Networks", RFC 4377, February 2006. 1665 [RFC4444] T. Parker, et al, "Management Information Base for 1666 Intermediate System to Intermediate System (IS-IS)", RFC 1667 4444, April 2006. 1669 [RFC4802] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 1670 Label Switching (GMPLS) Traffic Engineering Management 1671 Information Base", RFC4802, Feb. 2007. 1673 [RFC4803] T. D. Nadeau and A. Farrel, "Generalized Multiprotocol 1674 Label Switching (GMPLS) Label Switching Router (LSR) 1675 Management Information Base", RFC4803, Feb., 2007. 1677 [RFC5305] H. Smit and T. Li, "IS-IS extensions for Traffic 1678 Engineering", RFC 5305, Oct. 2008. 1680 [RFC5307] K. Kompella, and Y. Rekhter, "IS-IS Extensions in Support 1681 of Generalized Multi-Protocol Label Switching (GMPLS)", 1682 RFC5307, Oct. 2008. 1684 [RFC5226] Narten, T. and H. Alvestrand., "Guidelines for Writing an 1685 IANA Considerations Section in RFCs" BCP 26, RFC 5226, May 1686 2008. 1688 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 1689 for the Simple Network Management Protocol (SNMP)", RFC 1690 5591, June 2009. 1692 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1693 Shell Transport Model for the Simple Network Management 1694 Protocol (SNMP)", RFC 5592, June 2009. 1696 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1697 Model for the Simple Network Management Protocol (SNMP)", 1698 RFC 6353, July 2011. 1700 [ISO10589] ISO 10589, "Intermediate system to Intermediate system 1701 routeing information exchange protocol for use in 1702 conjunction with the Protocol for providing the 1703 Connectionless-mode Network Service (ISO 8473)", ISO/IEC 1704 10589:2002. 1706 11. Acknowledgment 1707 The authors wish to acknowledge and thank the following individuals 1708 for their valuable comments to this document: Ken Nagami, Shuichi 1709 Okamoto, Adrian Farrel, Diego Caviglia and Acee Lindem. 1711 12. Authors' Addresses 1713 Tomohiro Otani 1714 KDDI Corporation 1715 KDDI Bldg, 1716 2-3-2, Nishishinjuku, Shinjuku-ku, Tokyo, 163-8003, Japan 1717 Email: tm-otani@kddi.com 1719 Masanori Miyazawa 1720 KDDI R&D Laboratories, Inc. 1721 2-1-15 Ohara Fujimino, Saitama, 356-8502, Japan. 1722 Email: ma-miyazawa@kddilabs.jp 1724 Thomas D. Nadeau 1725 Email: tnadeau@lucidvision.com 1727 Kenji Kumaki 1728 KDDI Corporation 1729 Garden Air Tower 1730 Iidabashi, Chyoda-ku, Tokyo, 102-8460, Japan 1731 Email: ke-kumaki@kddi.com