idnits 2.17.1 draft-ietf-ccamp-gmpls-ospf-mib-01.txt: -(67): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1072. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1079. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1085. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** The document seems to lack an RFC 3978 Section 5.5 (updated by RFC 4748) Disclaimer. == In addition to a regular copyright notice, the document also has a copyright notice embedded in the text. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page == There are 9 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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 2006) is 6396 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) == Missing Reference: 'GMPLSrouting' is mentioned on line 133, but not defined == Missing Reference: 'OSPF-MIB' is mentioned on line 517, but not defined == Missing Reference: 'ISIS-MIB' is mentioned on line 521, but not defined == Unused Reference: 'GMPLSRouting' is defined on line 982, but no explicit reference was found in the text == Unused Reference: 'RFC3812' is defined on line 997, but no explicit reference was found in the text == Unused Reference: 'RFC3813' is defined on line 1002, but no explicit reference was found in the text == Unused Reference: 'GMPLSLSRMIB' is defined on line 1007, but no explicit reference was found in the text == Unused Reference: 'GMPLSTEMIB' is defined on line 1012, but no explicit reference was found in the text == Unused Reference: 'MPLS OAM' is defined on line 1017, but no explicit reference was found in the text == Unused Reference: 'RFC3945' is defined on line 1021, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 1850 (ref. 'OSPFMIB') (Obsoleted by RFC 4750) -- Obsolete informational reference (is this intentional?): RFC 4205 (ref. 'GMPLSisis') (Obsoleted by RFC 5307) -- Obsolete informational reference (is this intentional?): RFC 3784 (Obsoleted by RFC 5305) == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-lsr-mib-08 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-09 == Outdated reference: A later version (-07) exists of draft-ietf-mpls-oam-requirements-05 -- Duplicate reference: RFC3630, mentioned in 'OSPF-TE', was also mentioned in 'RFC3630'. -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 6 errors (**), 0 flaws (~~), 17 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF Internet Draft Masanori Miyazawa 3 Proposed status: Standards Track Tomohiro Otani 4 Expires: October 2006 KDDI R&D Labs 5 Thomas D. Nadeau 6 Cisco Systems 7 Kenji Kumaki 8 KDDI Corporation 9 October 2006 11 Traffic Engineering Database Management Information Base 12 in support of GMPLS 13 draft-ietf-ccamp-gmpls-ospf-mib-01.txt 15 Status of this Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This memo defines the Management Information Base (MIB) objects in 39 order to manage traffic engineering database (TED) information with 40 extension in support of Multi-protocol label switching (MPLS) as well 41 as Generalized MPLS (GMPLS) for use with network management protocols. 43 Table of Contents 45 Status of this Memo................................................1 46 Abstract...........................................................1 47 1. Introduction....................................................3 48 2. Terminology.....................................................3 49 2.1 Conventions used in this document..............................3 50 2.2 Terminology....................................................3 51 2.3 Acronyms.......................................................3 52 3. Motivations.....................................................4 53 4. Brief description of MIB Objects................................4 54 4.1 teTEDTable.....................................................4 55 4.2 teLocalIntIpAddrTable..........................................4 56 4.3 teRemoteIntIpAddrTable.........................................4 57 4.4 teSwCapTable...................................................4 58 4.5 teSrlgTable....................................................4 59 5. TED MIB Definitions in support of GMPLS.........................4 60 6. Security consideration.........................................19 61 7. IANA Considerations............................................19 62 7.1 IANA Considerations for TED-STD-MIB...........................19 63 8. References.....................................................19 64 8.1 Normative References..........................................19 65 8.2 Informative References........................................19 66 9. Acknowledgment.................................................21 67 10. Author�s Address..............................................21 68 11. Intellectual Property Statement...............................21 69 12. Copyright Statement...........................................22 70 1. Introduction 72 The OSPF MIB is defined as [OSPFMIB] being extended by [OSPFMIB 73 UPDATE] and The ISIS MIB as [ISISMIB]. On the other side, MPLS/GMPLS 74 based traffic engineering has so far extended OSPF/ISIS routing 75 protocol with TE functionality [GMPLSrouting, RFC3630, GMPLSisis, 76 RFC3784]. To manage such MPLS/GMPLS networks effectively, routing 77 information associated with MPLS/GMPLS TE parameters (TED) is 78 preferred for the network management, however, there is no clear 79 definition of MPLS/GMPLS TE information in existing MIBs related with 80 OSPF/ISIS. 82 This memo defines the Management Information Base (MIB) objects for 83 managing TED in support of MPLS/GMPLS for use with network management 84 protocols. 86 This MIB module should be used in conjunction with OSPF/ISIS MIB as 87 well as other MIBs defined in [RFC3812, RFC3813, GMPLSLSRMIB, 88 GMPLSTEMIB] for the management of MPLS/GMPLS based traffic 89 engineering information. 91 2. Terminology 93 2.1 Conventions used in this document 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in RFC-2119 [RFC2119]. 99 2.2 Terminology 101 Definitions of key terms for MPLS OAM and GMPLS are found in [MPLS- 102 OAM, RFC3945] and the reader is assumed to be familiar with those 103 definitions which are not repeated here. 105 2.3 Acronyms 107 GMPLS: Generalized Multi-Protocol Label Switching 108 LDP: Label Distribution Protocol 109 LSP: Label Switching Path 110 LSR: Label Switching Router 111 MIB: Management Information Base 112 OAM: Operations and Management 113 OA&M: Operations, Administration and Maintenance. 114 OSPF: Open Shortest Path First 115 RSVP: Resource reSerVation Protocol 116 TE: Traffic Engineering 117 PSC: Packet switch capable 118 LSC: Lambda switch capable 119 FSC: Fiber switch capable 120 TDM: Time Division Multiplexing 121 SRLG: Shared risk link group 122 LSA: Link state advertisement 123 3. Motivations 125 The existing OSPF, MPLS and GMPLS MIBs do not provide for the 126 management of all of the extensions to the OSPF protocol. To manage 127 GMPLS TE attributes, MIB objects to indicate such GMPLS TED is 128 significant. 130 4. Brief description of MIB Objects 132 The objects described in this section support the management of TED 133 described in [GMPLSrouting], [GMPLSOSPF] and [GMPLSisis] for GMPLS 134 extensions as well as in [RFC3630] and [RFC3784] for MPLS/GMPLS. 136 4.1 teTEDTable 138 The teTEDTable is basically used to indicate TED information of OSPF- 139 TE or ISIS-TE. However, this table does not contain the information 140 of Local/Remote interface IP address, Interface Switching Capcability 141 Descriptor and Shared Risk Link Group information within the sub-TLVs 142 for the Link-TLV. 144 4.2 teLocalIntIpAddrTable 146 The teLocalIntIpAddrTable is identical to the Local interface IP 147 address information in a sub-TLV for the Link-TLV. This is 148 independently defined, because the Interface IP Address sub-TLV may 149 appear more than once within the same Link-TLV. 151 4.3 teRemoteIntIpAddrTable 153 The teRemoteIntIpAddrTable is identical to the Remote interface IP 154 address information in a sub-TLV of the Link-TLV. This is also 155 independently utilized, because one or more local interface IP 156 address sub TLVs may exist in the same Link-TLV. 158 4.4 teSwCapTable 160 The teSwCapTable represents Interface Switching Capability Descriptor 161 information. This is independently defined due to the possibility of 162 multiple appearances of the sub TLV within the same Link-TLV. 164 4.5 teSrlgTable 166 The teSrlgTable contains the Sub-TLV information of Shared Risk Link 167 Group (SRLG) information. This is separately defined, because more 168 than one sub TLVs may appear in the same Link-TLV. 170 5. TED MIB Definitions in support of GMPLS 171 TED-DRAFT01-MIB DEFINITIONS ::= BEGIN 173 IMPORTS 174 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission, 175 IpAddress 176 FROM SNMPv2-SMI --[RFC2578] 177 MODULE-COMPLIANCE, OBJECT-GROUP 178 FROM SNMPv2-CONF --[RFC2580] 179 RowPointer 180 FROM SNMPv2-TC --[RFC2579] 181 ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId 182 FROM OSPF-MIB; --[OSPFMIB UPDATE] 183 IsisISLevel, IsisLinkStatePDUID, IsisSystemID 184 FROM ISIS-MIB; --[ISISMIB] 186 teMIB MODULE-IDENTITY 187 LAST-UPDATED "200510240000Z" -- 04 July 2005 00:00:00 GMT 188 ORGANIZATION "IETF CCAMP Working Group." 189 CONTACT-INFO 190 " Tomohiro Otani 191 otani@kddilabs.jp 193 Masanori Miyazawa 194 ma-miyazawa@kddilabs.jp 196 Thomas D. Nadeau 197 tnadeau@cisco.com 199 Kenji Kumaki 200 ke-kumaki@kddi.com 202 Comments and discussion to ccamp@ietf.org" 203 DESCRIPTION 204 "This MIB contains managed object definitions for 205 TED in support of MPLS/GMPLS Traffic 206 Engienering (TE) Database. 208 Copyright (C) The Internet Society (2006). This 209 version of this MIB module is part of RFCXXX; see 210 the RFC itself for full legal notices." 211 -- Revision history. 212 REVISION 213 "200506041200Z" -- 04 July 2005 12:00:00 GMT 214 DESCRIPTION 215 "Initial version. Published as RFC xxxx." -- RFC-editor pls fill 216 --in xxx 217 ::= { transmission 9988 } -- assigned by IANA, see section 7.1 for 218 -- details 220 -- Textual Conventions. 222 -- Top level components of this MIB. 224 teNotifications OBJECT IDENTIFIER ::= { teMIB 0 } 225 teObjects OBJECT IDENTIFIER ::= { teMIB 1 } 226 teScalars OBJECT IDENTIFIER ::= { teObjects 1 } 227 teTables OBJECT IDENTIFIER ::= { teObjects 2 } 228 teConformance OBJECT IDENTIFIER ::= { teMIB 2 } 230 -- MIB Definitions 232 -- 233 -- Scalar Objects 234 -- 236 -- 237 -- TE DB Table 238 -- 240 teTEDTable OBJECT-TYPE 241 SYNTAX SEQUENCE OF TeTEDEntry 242 MAX-ACCESS not-accessible 243 STATUS current 244 DESCRIPTION 245 "This table indicates multiple TED information which has been 246 supported by [OSPF-TE]." 247 ::= { teTables 1 } 249 teTEDEntry OBJECT-TYPE 250 SYNTAX TeTEDEntry 251 MAX-ACCESS not-accessible 252 STATUS current 253 DESCRIPTION 254 "This entry contains TED information commonly utilized in both 255 MPLS and GMPLS" 256 INDEX { ospfAreaId, ospfLsdbLsid, ospflsdbRouterId } 257 ::= { teTEDTable 1 } 259 TeTEDEntry ::= SEQUENCE { 260 teLinkInformationSource INTEGER, 261 teAreaLevelID OCTET STRING, 262 teLSPDUID OCTET STRING, 263 teRouterSystemID OCTET STRING, 264 teLinkType INTEGER, 265 teLinkIdAddr IpAddress, 266 teMetric Integer32, 267 teMaxBandwidth OCTET STRING, 268 teMaxReservableBandwidth OCTET STRING, 269 teUnreservedBandwidthPri0 OCTET STRING, 270 teUnreservedBandwidthPri1 OCTET STRING, 271 teUnreservedBandwidthPri2 OCTET STRING, 272 teUnreservedBandwidthPri3 OCTET STRING, 273 teUnreservedBandwidthPri4 OCTET STRING, 274 teUnreservedBandwidthPri5 OCTET STRING, 275 teUnreservedBandwidthPri6 OCTET STRING, 276 teUnreservedBandwidthPri7 OCTET STRING, 277 teAdministrativeGroup Integer32, 278 teLocalId Integer32, 279 teRemoteId Integer32, 280 teLinkProtectionType BITS, 281 teLinkInformationData RowPointer, 282 } 284 teLinkInformationSource OBJECT-TYPE 285 SYNTAX INTEGER { 286 unknown(0), 287 locallyConfigured(1), 288 ospf(2), 289 isis(3), 290 other(4) 291 } 292 MAX-ACCESS read-only 293 STATUS current 294 DESCRIPTION 295 "This object indicates the source of the information about 296 the TE link" 297 ::= { teTEDEntry 1 } 299 teAreaLevelId OBJECT-TYPE 300 SYNTAX Usigned32 {ospfAreaId, IsisISLevel} 301 MAX-ACCESS read-only 302 STATUS current 303 DESCRIPTION 304 �This is corresponding to area ID in OSPF and level ID in 305 ISIS� 306 ::= { teTEDEntry 2 } 308 teOSPDUId OBJECT-TYPE 309 SYNTAX Usigned32 {ospfLsdbLsid, IsisLinkStatePDUID} 310 MAX-ACCESS read-only 311 STATUS current 312 DESCRIPTION 313 �This is corresponding to link state ID in OSPF and link 314 state PDU ID in ISIS� 315 ::= { teTEDEntry 3 } 317 teRouterSystem OBJECT-TYPE 318 SYNTAX Usigned32 {ospfLsdbRouterId, IsisSystemID} 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 �This is corresponding to the router ID in OSPF and the 323 system ID in ISIS� 324 ::= { teTEDEntry 4 } 326 teLinkType OBJECT-TYPE 327 SYNTAX INTEGER { 328 pointToPoint (1), 329 multiAccess (2) 330 } 331 MAX-ACCESS read-only 332 STATUS current 333 DESCRIPTION 334 "This indicates the type of the link such as point-to-point 335 or multi-access" 336 ::= { teTEDEntry 5 } 338 teLinkIdAddr OBJECT-TYPE 339 SYNTAX IpAddress 340 MAX-ACCESS read-only 341 STATUS current 342 DESCRIPTION 343 "This indicates the Router ID of the neighbor in the case 344 of point-to-point links. This also indicates the interface address 345 of the designated router in the case of multi-access links." 346 ::= { teTEDEntry 6 } 348 teMetric OBJECT-TYPE 349 SYNTAX Integer32 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "This indicates the traffic engineering metric value of the 354 TE link." 355 ::= { teTEDEntry 7 } 357 teMaxBandwidth OBJECT-TYPE 358 SYNTAX OCTET STRING (SIZE( 4)) 359 UNITS "Byte per seconds" 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "This indicates the maximum bandwidth that 364 can be used on this link in this direction" 365 ::= { teTEDEntry 8 } 367 teMaxReservableBandwidth OBJECT-TYPE 368 SYNTAX OCTET STRING (SIZE (4)) 369 UNITS "Byte per seconds" 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "This indicates the maximum bandwidth that may be reserved on 374 this link in this direction" 375 ::= { teTEDEntry 9 } 377 teUnreservedBandwidthPri0 OBJECT-TYPE 378 SYNTAX OCTET STRING (SIZE (4)) 379 UNITS "Byte per seconds" 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "This indicates the amount of bandwidth not yet reserved at 384 the priority 0" 385 ::= { teTEDEntry 10 } 387 teUnreservedBandwidthPri1 OBJECT-TYPE 388 SYNTAX OCTET STRING (SIZE (4)) 389 UNITS "Byte per seconds" 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "This indicates the amount of bandwidth not yet reserved at 394 the priority 1" 395 ::= { teTEDEntry 11 } 397 teUnreservedBandwidthPri2 OBJECT-TYPE 398 SYNTAX OCTET STRING (SIZE (4)) 399 UNITS "Byte per seconds" 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "This indicates the amount of bandwidth not yet reserved at 404 the priority 2" 405 ::= { teTEDEntry 12 } 407 teUnreservedBandwidthPri3 OBJECT-TYPE 408 SYNTAX OCTET STRING (SIZE (4)) 409 UNITS "Byte per seconds" 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "This indicates the amount of bandwidth not yet reserved at 414 the priority 3" 415 ::= { teTEDEntry 13 } 417 teUnreservedBandwidthPri4 OBJECT-TYPE 418 SYNTAX OCTET STRING (SIZE (4)) 419 UNITS "Byte per seconds" 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "This indicates the amount of bandwidth not yet reserved at 424 the priority 4" 425 ::= { teTEDEntry 14 } 427 teUnreservedBandwidthPri5 OBJECT-TYPE 428 SYNTAX OCTET STRING (SIZE (4)) 429 UNITS "Byte per seconds" 430 MAX-ACCESS read-only 431 STATUS current 432 DESCRIPTION 433 "This indicates the amount of bandwidth not yet reserved at 434 the priority 5" 435 ::= { teTEDEntry 15 } 436 teUnreservedBandwidthPri6 OBJECT-TYPE 437 SYNTAX OCTET STRING (SIZE (4)) 438 UNITS "Byte per seconds" 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "This indicates the amount of bandwidth not yet reserved at 443 the priority 6" 444 ::= { teTEDEntry 16 } 446 teUnreservedBandwidthPri7 OBJECT-TYPE 447 SYNTAX OCTET STRING (SIZE (4)) 448 UNITS "Byte per seconds" 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "This indicates the amount of bandwidth not yet reserved at 453 the priority 7" 454 ::= { teTEDEntry 17 } 456 teAdministrativeGroup OBJECT-TYPE 457 SYNTAX Integer32 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "This indicates the Administrative Group which the link 462 belong to. Since the value is a bit mask, the link can belong to 463 multiple groups. This is also called Resource Class/Color." 464 ::= { teTEDEntry 18 } 466 teLocalId OBJECT-TYPE 467 SYNTAX Integer32 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "This indicates the Link local identifier of an unnumbered 472 link." 473 ::= { teTEDEntry 19 } 475 teRemoteId OBJECT-TYPE 476 SYNTAX Integer32 477 MAX-ACCESS read-only 478 STATUS current 479 DESCRIPTION 480 " This indicates the Link remote identifier of an unnumbered 481 link." 482 ::= { teTEDEntry 20 } 484 teLinkProtectionType OBJECT-TYPE 485 SYNTAX BITS { 486 extraTraffic(0), 487 unprotected(1), 488 shared (2), 489 dedicatedOneToOne (3), 490 dedicatedOnePlusOne(4), 491 enhanced(5) 492 } 493 MAX-ACCESS read-only 494 STATUS current 495 DESCRIPTION 496 "This object indicates the protection type of the TE link" 497 ::= { teTEDEntry 21 } 499 teLinkInformationData OBJECT-TYPE 500 SYNTAX RowPointer 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "This object cross-references the source of the information 505 about this TE link and should be interpretted in the context of 506 teLinkInformationSource. 507 If teLinkInformationSource has the value unknown(0) this 508 object SHOULD contain a value of zeroDotZero. 509 If teLinkInformationSource has the value 510 locallyConfigured(1), this object MAY contain the identifier of the 511 corresponding row entry in the teLinkTable of TE-LINK-STD-MIB, MAY 512 contain the identifier of the corresponding row in a local 513 proprietary TE link MIB module, or otherwise SHOULD contain the value 514 of zeroDotZero. 515 If teLinkInformationSource has the value ospf(2), this 516 object MAY contain the identifier of the corresponding row entry in 517 the ospfLocalLsdbTable of [OSPF-MIB], or otherwise SHOULD contain the 518 value of zeroDotZero. 519 If teLinkInformationSource has the value isis(3) this object 520 MAY contain the identifier of the corresponding row entry in the 521 isisAreaAddr of [ISIS-MIB], or otherwise SHOULD contain the value of 522 zeroDotZero. 523 If teLinkInformationSource has the value other(4) this 524 object MAY contain the identifier of the corresponding row entry a 525 local proprietary MIB module, or otherwise SHOULD contain the value 526 of zeroDotZero." 527 ::= { teTEDEntry 22 } 529 -- 530 -- TED Local Interface IP Address Table 531 -- 533 teLocalIntAddrTable OBJECT-TYPE 534 SYNTAX SEQUENCE OF TeLocalIntAddrEntry 535 MAX-ACCESS not-accessible 536 STATUS current 537 DESCRIPTION 538 "This table contains the IP address information of a local TE 539 link." 540 ::= { teTables 2 } 542 teLocalIntAddrEntry OBJECT-TYPE 543 SYNTAX TeLocalIntAddrEntry 544 MAX-ACCESS not-accessible 545 STATUS current 546 DESCRIPTION 547 "This entry contains the IP address information of the local 548 TE link." 549 INDEX { ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId, 550 teLocalIntAddrIndex } 551 ::= { teLocalIntAddrTable 1 } 553 TeLocalIntAddrEntry ::= SEQUENCE { 554 teLocalIntAddrIndex Unsigned32, 555 teLocalIntAddr IpAddress, 556 } 558 teLocalIntAddrIndex OBJECT-TYPE 559 SYNTAX Unsigned32 560 MAX-ACCESS not-accessible 561 STATUS current 562 DESCRIPTION 563 "This indicates the index to identify multiple local TE links" 564 ::= { teLocalIntAddrEntry 1 } 566 teLocalIntAddr OBJECT-TYPE 567 SYNTAX IpAddress 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "This object indicates the address of the local TE link." 572 ::= { teLocalIntAddrEntry 2 } 574 -- 575 -- TED Remote Interface IP Address Table 576 -- 578 teRemoteIntAddrTable OBJECT-TYPE 579 SYNTAX SEQUENCE OF TeRemoteIntAddrEntry 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "This table contains the IP address information of a remote 584 TE link." 585 ::= { teTables 3 } 587 teRemoteIntAddrEntry OBJECT-TYPE 588 SYNTAX TeRemoteIntAddrEntry 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "This entry contains the IP address information of the remote 593 TE link." 594 INDEX { ospfAreaId, ospfLsdbLsid, ospflsdbRouterId, 595 teRemoteIntAddrIndex } 596 ::= { teRemoteIntAddrTable 1 } 597 TeRemoteIntAddrEntry ::= SEQUENCE { 598 teRemoteIntAddrIndex Unsigned32, 599 teRemoteIntAddr IpAddress, 600 } 602 teRemoteIntAddrIndex OBJECT-TYPE 603 SYNTAX Unsigned32 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "This indicates the index to identify multiple remote TE 608 links." 609 ::= { teRemoteIntAddrEntry 1 } 611 teRemoteIntAddr OBJECT-TYPE 612 SYNTAX IpAddress 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "This object indicates the address of the remote TE link." 617 ::= { teRemoteIntAddrEntry 2 } 619 -- 620 -- TED Switch Capable Table 621 -- 623 teSwCapTable OBJECT-TYPE 624 SYNTAX SEQUENCE OF TeSwCapEntry 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "This table contains the GMPLS TED switching capability 629 information." 630 ::= { teTables 4 } 632 teSwCapEntry OBJECT-TYPE 633 SYNTAX TeSwCapEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "This entry relates each TE link with its GMPLS TE switching 638 capability information. IF the MIB deals with only OSPF-TE 639 information, the value of each object related with GMPLS TE 640 extensions should be null." 641 INDEX { ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId, 642 teSwCapIndex } 643 ::= { teSwCapTable 1 } 645 TeSwCapEntry ::= SEQUENCE { 646 teSwCapIndex Unsigned32, 647 teSwitchingType INTEGER, 648 teEncoding INTEGER, 649 teMaxLspBandwidthPri0 OCTET STRING, 650 teMaxLspBandwidthPri1 OCTET STRING, 651 teMaxLspBandwidthPri2 OCTET STRING, 652 teMaxLspBandwidthPri3 OCTET STRING, 653 teMaxLspBandwidthPri4 OCTET STRING, 654 teMaxLspBandwidthPri5 OCTET STRING, 655 teMaxLspBandwidthPri6 OCTET STRING, 656 teMaxLspBandwidthPri7 OCTET STRING, 657 teMinLspBandwidth OCTET STRING, 658 teIntMtu Integer32, 659 teIndication INTEGER 660 } 662 teSwCapIndex OBJECT-TYPE 663 SYNTAX Unsigned32 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "This index is utilized to identify multiple switching 668 functions on a local or remote TE link." 669 ::= { teSwCapEntry 1 } 671 teSwitchingType OBJECT-TYPE 672 SYNTAX INTEGER { 673 unknown (0), 674 psc1 (1), 675 psc2 (2), 676 psc3 (3), 677 psc4 (4), 678 l2sc (51), 679 tdm (100), 680 lsc (150), 681 fsc (200) 682 } 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "This object indicates the GMPLS switching capability 687 assigned to the TE link." 688 ::= { teSwCapEntry 2 } 690 teEncoding OBJECT-TYPE 691 SYNTAX INTEGER { 692 packet (1), 693 ethernet (2), 694 ansiEtsiPdh (3), 695 sdhSonet (5), 696 digitalWrapper (7), 697 lambda (8), 698 fiber (9), 699 fiberChannel (11) 700 } 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 "This object indicates the GMPLS encoding type assigned to 705 the TE link." 706 ::= { teSwCapEntry 3 } 708 teMaxLspBandwidthPri0 OBJECT-TYPE 709 SYNTAX OCTET STRING (SIZE (4)) 710 UNITS "Byte per seconds" 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION 714 "This object indicates the maximum bandwidth of the TE link 715 at the priority 0 for GMPLS LSP creation." 716 ::= { teSwCapEntry 4 } 718 teMaxLspBandwidthPri1 OBJECT-TYPE 719 SYNTAX OCTET STRING (SIZE (4)) 720 UNITS "Byte per seconds" 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "This object indicates the maximum bandwidth of the TE link 725 at the priority 1 for GMPLS LSP creation." 726 ::= { teSwCapEntry 5 } 728 teMaxLspBandwidthPri2 OBJECT-TYPE 729 SYNTAX OCTET STRING (SIZE (4)) 730 UNITS "Byte per seconds" 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "This object indicates the maximum bandwidth of the TE link 735 at the priority 2 for GMPLS LSP creation." 736 ::= { teSwCapEntry 6 } 738 teMaxLspBandwidthPri3 OBJECT-TYPE 739 SYNTAX OCTET STRING (SIZE (4)) 740 UNITS "Byte per seconds" 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "This object indicates the maximum bandwidth of the TE link 745 at the priority 3 for GMPLS LSP creation." 746 ::= { teSwCapEntry 7 } 748 teMaxLspBandwidthPri4 OBJECT-TYPE 749 SYNTAX OCTET STRING (SIZE (4)) 750 UNITS "Byte per seconds" 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "This object indicates the maximum bandwidth of the TE link 755 at the priority 4 for GMPLS LSP creation." 756 ::= { teSwCapEntry 8 } 757 teMaxLspBandwidthPri5 OBJECT-TYPE 758 SYNTAX OCTET STRING (SIZE (4)) 759 UNITS "Byte per seconds" 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION 764 "This object indicates the maximum bandwidth of the TE link 765 at the priority 5 for GMPLS LSP creation." 766 ::= { teSwCapEntry 9 } 768 teMaxLspBandwidthPri6 OBJECT-TYPE 769 SYNTAX OCTET STRING (SIZE (4)) 770 UNITS "Byte per seconds" 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "This object indicates the maximum bandwidth of the TE link 775 at the priority 6 for GMPLS LSP creation." 776 ::= { teSwCapEntry 10 } 778 teMaxLspBandwidthPri7 OBJECT-TYPE 779 SYNTAX OCTET STRING (SIZE (4)) 780 UNITS "Byte per seconds" 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "This object indicates the maximum bandwidth of the TE link 785 at the priority 7 for GMPLS LSP creation." 786 ::= { teSwCapEntry 11 } 788 teMinLspBandwidth OBJECT-TYPE 789 SYNTAX OCTET STRING (SIZE (4)) 790 UNITS "Byte per seconds" 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "This object indicates the minimum bandwidth of the TE link 795 for GMPLS LSP creation if the switching capability field is TDM, PSC- 796 1, PSC-2, PSC-3, or PSC-4." 797 ::= { teSwCapEntry 12 } 799 teIntMtu OBJECT-TYPE 800 SYNTAX Integer32 801 MAX-ACCESS read-only 802 STATUS current 803 DESCRIPTION 804 "This object indicates the MTU of the local or remote TE 805 link" 806 ::= { teSwCapEntry 13 } 808 teIndication OBJECT-TYPE 809 SYNTAX INTEGER { 810 standard (0), 811 arbitrary (1) 812 } 813 MAX-ACCESS read-only 814 STATUS current 815 DESCRIPTION 816 "This object indicates whether the interface supports 817 Standard or Arbitrary SONET/SDH." 818 ::= { teSwCapEntry 14 } 820 -- 821 -- TED SRLG Table 822 -- 824 teSrlgTable OBJECT-TYPE 825 SYNTAX SEQUENCE OF TeSrlgEntry 826 MAX-ACCESS not-accessible 827 STATUS current 828 DESCRIPTION 829 "This table contains the SRLG information of the TE link." 830 ::= { teTables 5 } 832 teSrlgEntry OBJECT-TYPE 833 SYNTAX TeSrlgEntry 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "This entry relates each TE link with its SRLG information." 838 INDEX { ospfAreaId, ospfLsdbLsid, ospfLsdbRouterId, teSrlgIndex } 839 ::= { teSrlgTable 1 } 841 TeSrlgEntry ::= SEQUENCE { 842 teSrlgIndex Unsigned32 843 teSrlg Integer32 844 } 846 teSrlgIndex OBJECT-TYPE 847 SYNTAX Unsigned32 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "This index is utilized to identify multiple SRLG values on a 852 local or remote TE link." 853 ::= { teSrlgTableEntry 1 } 855 teSrlg OBJECT-TYPE 856 SYNTAX Integer32 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "This object indicate the SRLG value assigned to a local or 861 remote TE link" 862 ::= { teSrlgEntry 2 } 863 -- Conformance Statement 864 teGroups 865 OBJECT IDENTIFIER ::= { teConformance 1 } 867 teCompliances 868 OBJECT IDENTIFIER ::= { teConformance 2 } 870 -- Module Compliance 872 teModuleFullCompliance MODULE-COMPLIANCE 873 STATUS current 874 DESCRIPTION 875 "Compliance statement for agents provides full support 876 for the TED MIB" 877 MODULE -- this module 878 MANDATORY-GROUPS { teMainGroup 879 } 881 ::= { teCompliances 1 } 883 -- 884 -- ReadOnly Compliance 885 -- 887 teModuleReadOnlyCompliance MODULE-COMPLIANCE 888 STATUS current 889 DESCRIPTION 890 "Compliance requirement for implementations only provide 891 read-only support for TED. Such devices can then be monitored 892 but cannot be configured using this MIB module. 893 " 894 MODULE -- this module 895 MANDATORY-GROUPS { teMainGroup 896 } 898 ::= { teCompliances 2 } 900 -- Units of conformance. 901 teMainGroup OBJECT-GROUP 902 OBJECTS { 903 teLinkInformationSource , 904 teLinkType , 905 teLinkIdAddr , 906 teMetric , 907 teMaxBandwidth , 908 teMaxReservableBandwidth , 909 teUnreservedBandwidthPri0 , 910 teUnreservedBandwidthPri1 , 911 teUnreservedBandwidthPri2 , 912 teUnreservedBandwidthPri3 , 913 teUnreservedBandwidthPri4 , 914 teUnreservedBandwidthPri5 , 915 teUnreservedBandwidthPri6 , 916 teUnreservedBandwidthPri7 , 917 teAdministrativeGroup , 918 teLocalId , 919 teRemoteId , 920 teLinkProtectionType , 921 teLinkInformationData , 922 teLocalIntAddr , 923 teRemoteIntAddr , 924 teSwitchingType , 925 teEncoding , 926 teMaxLspBandwidthPri0 , 927 teMaxLspBandwidthPri1 , 928 teMaxLspBandwidthPri2 , 929 teMaxLspBandwidthPri3 , 930 teMaxLspBandwidthPri4 , 931 teMaxLspBandwidthPri5 , 932 teMaxLspBandwidthPri6 , 933 teMaxLspBandwidthPri7 , 934 teMinLspBandwidth , 935 teIntMtu , 936 teIndication , 937 teSrlg 938 } 939 STATUS current 940 DESCRIPTION 941 "Collection of objects for TED management" 942 ::= { teGroups 1 } 944 END 946 6. Security consideration 948 This document introduces no new security issues beyond those detailed 949 in the OSPF MIB. 951 7. IANA Considerations 953 The following "IANA Considerations" subsection requests IANA for a 954 new assignment under the transmission subtree. New assignments can 955 only be made via a Standards Action as specified in [RFC2434]. 957 7.1 IANA Considerations for TED-STD-MIB 959 The IANA is requested to assign { teMIB XXX } to the TED-STD-MIB 960 module specified in this document. 962 8. References 964 8.1 Normative References 966 8.2 Informative References 968 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 969 Requirement Levels", BCP 14, RFC 2119, March 1997. 971 [OSPFMIB] F. Baker, et al, "OSPF Version 2 Management 972 Information Base", RFC1850, Nov. 1995. 974 [OSPFMIB UPDATE]Dan Joyal, et al, "OSPF Version 2 Management 975 Information Base", draft-ietf-ospf-mib-update-08.txt, 976 December 2003. 978 [ISISMIB] J. Parker, et al, "Management Information Base for 979 Intermediate System to Intermediate System (IS-IS)�, 980 RFC 4444, April 2006. 982 [GMPLSRouting] K. Kompella, and Y. Rekhter, "Routing Extensions in 983 Support of Generalized Multi-Protocol Label 984 Switching", RFC4202, Oct. 2005. 986 [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions 987 to OSPF Version2", RFC3630, September 2003. 989 [GMPLSisis] K. Kompella, and Y. Rekhter, "Intermediate System to 990 Intermediate System (IS-IS) Extensions in Support of 991 Multi-Protocol Label Switching (GMPLS)", RFC4205, Oct. 992 2005. 994 [RFC3784] H. Smit and T. Li, "IS-IS extensions for Traffic 995 Engineering�, RFC 3784, June 2004. 997 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 998 "Multiprotocol Label Switching (MPLS) Traffic 999 Engineering (TE) Management Information Base (MIB)", 1000 RFC 3812, June 2004. 1002 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1003 "Multiprotocol Label Switching (MPLS) Label Switching 1004 (LSR) Router Management Information Base (MIB)", RFC 1005 3813, June 2004. 1007 [GMPLSLSRMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol 1008 Label Switching (GMPLS) Label Switching Router (LSR) 1009 Management Information Base", draft-ietf-ccamp-gmpls- 1010 lsr-mib-08.txt, June 2005. 1012 [GMPLSTEMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol 1013 Label Switching (GMPLS) Traffic Engineering 1014 Management Information Base", draft-ietf-ccamp-gmpls- 1015 te-mib-09.txt, June 2005. 1017 [MPLS OAM] T. Nadeau, Allan D., et al., "OAM Requirements for 1018 MPLS Network" 1019 draft-ietf-mpls-oam-requirements-05.txt, June 2005. 1021 [RFC3945] E. Mannie, "Generalized Multi-Protocol Label 1022 Switching Architecture", RFC3945, October, 2004. 1024 [GMPLSOSPF] K. Kompella, and Y. Rekhter, "OSPF Extensions in 1025 Support of Generalized Multi-Protocol Label 1026 Switching", RFC4203, Oct. 2005. 1028 [OSPF-TE] Katz, D., et al, "Traffic Engineering (TE) Extensions 1029 to OSPF Version 2", RFC3630, September 2003. 1031 [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for 1032 Writing an IANA Considerations Section in RFCs" BCP 1033 26, RFC 2434, October 1998. 1035 9. Acknowledgment 1037 The authors wish to acknowledge and thank the following individuals 1038 for their valuable comments to this document: Ken Nagami, Shuichi 1039 Okamoto and Adrian Farrel. 1041 10. Author's Address 1043 Tomohiro Otani 1044 KDDI R&D Laboratories, Inc. 1045 2-1-15 Ohara Fujimino Phone: +81-49-278-7357 1046 Saitama, 356-8502. Japan Email: otani@kddilabs.jp 1048 Masanori Miyazawa 1049 KDDI R&D Laboratories, Inc. 1050 2-1-15 Ohara Fujimino Phone: +81-49-278-7559 1051 Saitama, 356-8502. Japan Email: ma-miyazawa@kddilabs.jp 1053 Thomas D. Nadeau 1054 Cisco Systems, Inc. 1055 300 Beaver Brook Road Phone: +1-978-936-1470 1056 Boxboro, MA 01719 Email: tnadeau@cisco.com300 1058 Kenji Kumaki 1059 KDDI Corporation 1060 GARDEN AIR TOWER,3-10-10,Iidabshi Phone: +81-3-6678-3103 1061 Chiyoda-ku,Tokyo, 102-8460. Japan Email: ke-kumaki@kddi.com 1063 11. Intellectual Property Statement 1065 The IETF takes no position regarding the validity or scope of any 1066 Intellectual Property Rights or other rights that might be claimed to 1067 pertain to the implementation or use of the technology described in 1068 this document or the extent to which any license under such rights 1069 might or might not be available; nor does it represent that it has 1070 made any independent effort to identify any such rights. Information 1071 on the procedures with respect to rights in RFC documents can be 1072 found in BCP 78 and BCP 79. 1074 Copies of IPR disclosures made to the IETF Secretariat and any 1075 assurances of licenses to be made available, or the result of an 1076 attempt made to obtain a general license or permission for the use of 1077 such proprietary rights by implementers or users of this 1078 specification can be obtained from the IETF on-line IPR repository at 1079 http://www.ietf.org/ipr. 1081 The IETF invites any interested party to bring to its attention any 1082 copyrights, patents or patent applications, or other proprietary 1083 rights that may cover technology that may be required to implement 1084 this standard. Please address the information to the IETF at ietf- 1085 ipr@ietf.org. 1087 12. Copyright Statement 1089 "Copyright (C) The Internet Society (2006). This document is subject 1090 to the rights, licenses and restrictions contained in BCP 78, and 1091 except as set forth therein, the authors retain all their rights." 1093 "This document and the information contained herein are provided on 1094 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1095 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 1096 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 1097 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1098 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1099 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."