idnits 2.17.1 draft-ietf-tewg-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The abstract seems to contain references ([3]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2049 has weird spacing: '...for the purpo...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (February 2004) is 7369 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '10' is defined on line 1909, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1926, but no explicit reference was found in the text == Outdated reference: A later version (-10) exists of draft-ietf-mpls-tc-mib-09 -- Obsolete informational reference (is this intentional?): RFC 2667 (ref. '12') (Obsoleted by RFC 4087) Summary: 6 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Kompella 3 Internet Draft Juniper Networks 4 Category: Standards Track February 2004 5 Expires: August 2004 6 draft-ietf-tewg-mib-08.txt 8 A Traffic Engineering MIB 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as ``work in progress.'' 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Copyright Notice 33 Copyright (C) The Internet Society (2004). All Rights Reserved. 35 Abstract 37 This memo defines a portion of the Management Information Base (MIB) 38 for use with network management protocols in the Internet community. 39 In particular, it describes managed objects for Traffic Engineered 40 Tunnels, for example, Multi-Protocol Label Switched Paths. 42 Changes from previous version 44 (Note to RFC Editor: This section to be removed before publication.) 46 o Incorporated more of Dave Thaler's review comments 47 - Added explanation how the IF MIB module and/or the IP tunnel 48 MIB module can be extended 49 - Added explanation of how TimeTicks wraps can be dealt with 50 - Updated DESCRIPTION of teTunnelSourceAddressType and 51 teTunnelDestinationAddressType. 52 - Created two new conformance groups for path computation servers 53 that implement the full set of teTunnelSourceAddressTypes. 55 Specification of Requirements 57 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 58 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 59 document are to be interpreted as described in RFC 2119 [3]. 61 1. Introduction 63 This memo defines a portion of the Management Information Base (MIB) 64 for use with network management protocols in the Internet community. 65 In particular, it describes managed objects for Traffic Engineered 66 Tunnels, for example, Multi-Protocol Label Switched Paths ([1], [2]). 67 The MIB module that this memo defines allows one to configure TE 68 Tunnels, assign one or more paths to a Tunnel, and monitor 69 operational aspects of the Tunnel, such as the number of octets and 70 packets that have passed through the Tunnel. 72 As it stands, this MIB module can only be used to configure or 73 monitor a TE Tunnel at its ingress. The extension of this module for 74 use at other points of a Tunnel is for further study. 76 2. The Internet-Standard Management Framework 78 For a detailed overview of the documents that describe the current 79 Internet-Standard Management Framework, please refer to section 7 of 80 RFC 3410 [4]. 82 Managed objects are accessed via a virtual information store, termed 83 the Management Information Base or MIB. MIB objects are generally 84 accessed through the Simple Network Management Protocol (SNMP). 85 Objects in the MIB are defined using the mechanisms defined in the 86 Structure of Management Information (SMI). This memo specifies a MIB 87 module that is compliant to the SMIv2, which is described in STD 58, 88 RFC 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. 90 3. Overview of the MIB Module 92 The Traffic Engineering MIB module consists of four parts: 93 1) Traffic Engineering information; 94 2) a table of Traffic Engineering Tunnels; 95 3) a table of Paths that tunnels take; 96 4) a table of Hops that make up a tunnel path. 98 The MIB module also has statements for minimal and full compliance. 100 The following subsections give an overview of each part. All objects 101 are mandatory. For minimal compliance, all objects MAY be 102 implemented read only; for full compliance, all objects must be 103 implemented to their stated MAX-ACCESS capabilities. Notifications 104 are optional. 106 3.1. Traffic Engineering Information 108 This part contains information about the Link State Protocols used to 109 carry TE information, the signalling protocols used to set up Traffic 110 Tunnels, the number of Traffic Tunnels that have been configured and 111 that are operational, and a mapping of Administrative Group (called 112 Resource Classes in [1]) numbers to names. 114 3.2. Traffic Tunnel Information 116 This part contains a table of Traffic Tunnels and information about 117 each one. This information includes the Tunnel name, its 118 configuration information, its operational information, and the 119 active path(s) that the Tunnel takes. 121 Configuration information includes the end points of the Traffic 122 Tunnel, and the number of configured paths for the Traffic Tunnel. 124 Operational information includes the current state (up/down), the 125 count of octets and packets sent on the Traffic Tunnel, how long it 126 has been up, and how many state transitions the Traffic Tunnel has 127 had. 129 Operational path information includes the number of operational 130 paths, the number of path changes, and when the last path change was. 132 3.3. Path Information 134 A Tunnel is a logical entity. An instantiation of a Tunnel is one or 135 more Paths; each Path has a route (also called Explicit Route) or 136 sequence of hops. A Path is indexed by a dual index: the primary 137 index is that of the Tunnel to which this Path belongs; the secondary 138 index is of the Path itself. 140 The configured information for a Path consists of the constraints for 141 the Path and a configured route. 143 The operational information consists of the Path status, as well as 144 the computed route (i.e., the route that was computed to satisfy the 145 constraints), and the actual path as recorded by the signaling 146 protocol. 148 3.4. Hop Information 150 A path consists of a sequence of hops; a hop can be loose (meaning 151 that the path eventually traverses the specified node) or strict 152 (meaning that the specified node and possibly link must be the next 153 node in the path). A hop can be specified as an IPv4 address, an 154 IPv6 address, an Autonomous System number or an unnumbered interface 155 index [8]. 157 The Hop Table contains all hops for all paths on a given router. It 158 is organized as follows. There is a primary index that identifies a 159 list of hops and a secondary index that identifies individual hops. 160 Thus, to get the sequence of recorded hops for a path, one looks up 161 the path's tePathRecordedRoute, which is a primary index into the Hop 162 Table. Then to get the list of actual hops in order for the recorded 163 path, one uses a secondary index of 1, 2, .... 165 3.5. Relationship with Other MIB Modules 167 A TE Tunnel can extend objects from two other MIB modules; one is the 168 Interfaces MIB [11], and the other is the IP Tunnel MIB [12]. The 169 mechanism for doing so is to assign the TE Tunnel index 170 (teTunnelIndex) with a valid ifIndex value in ifTable. 172 If a TE Tunnel is deemed an interface, a new interface object is 173 created and assigned an ifIndex value in ifTable. Then a TE Tunnel 174 object is created, setting teTunnelIndex to the same value as the 175 interface index. 177 If (and only if) a TE Tunnel is considered an interface, it may also 178 be considered an IP tunnel (if the encapsulation of the TE Tunnel is 179 IP). In that case, the interface associated with the TE Tunnel 180 should have its ifType set to tunnel(131). 182 If a TE Tunnel is not considered an interface, then the TE Tunnel 183 index (teTunnelIndex) SHOULD be set to a value at least 2^24, so that 184 it is distinct from normal interfaces. 186 4. Creating, Modifying and Deleting a TE Tunnel 188 To create a TE Tunnel, one first obtains a free Tunnel index using 189 the object teNextTunnelIndex. One then creates the Tunnel, including 190 all parameters, either as createAndGo or createAndWait. Then, TE 191 Paths for this Tunnel can be created using the teTunnelNextPathIndex 192 object, again as createAndGo or createAndWait. A particular Path is 193 computed and signaled when both the Path and the enclosing Tunnel 194 have RowStatus 'active'. 196 To build a Path's configured route, one first gets a free PathHop 197 index using teNextPathHopIndex, then builds the route hop-by-hop 198 using the secondary index, setting the AddrType, Address, and HopType 199 for each Hop. Finally, one sets the tePathConfiguredRoute in the 200 Path to the PathHop index obtained. 202 Modifying certain properties of a TE Tunnel or a TE Path may require 203 setting the RowStatus of the Tunnel (or Path) to 'notInService' 204 before making the changes, and then setting the RowStatus of the 205 Tunnel (or Path) back to 'active' to re-signal all Paths of the 206 Tunnel (or the modified Path). 208 A TE Tunnel and all its Paths can be deleted by setting the Tunnel's 209 RowStatus to 'destroy'. A specific Path within a Tunnel can be 210 destroyed by setting just the Path's RowStatus to 'destroy'. 212 5. MIB Specification 214 TE-MIB DEFINITIONS ::= BEGIN 216 IMPORTS 217 MODULE-IDENTITY, OBJECT-TYPE, 218 NOTIFICATION-TYPE, mib-2, 219 Integer32, Gauge32, Counter32, 220 Counter64, Unsigned32, TimeTicks FROM SNMPv2-SMI 222 RowStatus, StorageType, TimeStamp, 223 TruthValue FROM SNMPv2-TC 225 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 227 MODULE-COMPLIANCE, OBJECT-GROUP, 228 NOTIFICATION-GROUP FROM SNMPv2-CONF 230 TeHopAddress, TeHopAddressType, 231 MplsBitRate FROM MPLS-TC-STD-MIB; 233 teMIB MODULE-IDENTITY 234 LAST-UPDATED "200401290000Z" -- 29 January 2004 235 ORGANIZATION "IETF Traffic Engineering Working Group" 236 CONTACT-INFO " 237 Editor: Kireeti Kompella 238 Postal: Juniper Networks, Inc. 239 1194 Mathilda Ave 240 Sunnyvale, CA 94089 241 Tel: +1 408 745 2000 242 E-mail: kireeti@juniper.net 244 The IETF Traffic Engineering Working Group is 245 chaired by Jim Boyle and Ed Kern. 247 WG Mailing List information: 249 General Discussion: te-wg@ops.ietf.org 250 To Subscribe: te-wg-request@ops.ietf.org 251 In Body: subscribe 252 Archive: ftp://ops.ietf.org/pub/lists 254 Comments on the MIB module should be sent to the 255 mailing list. The archives for this mailing list 256 should be consulted for previous discussion on 257 this MIB. 258 " 259 DESCRIPTION "The Traffic Engineering MIB module. 261 Copyright (C) The Internet Society (2004). This 262 version of this MIB module is part of RFC xxxx; 263 see the RFC itself for full legal notices. 264 " 265 -- RFC Editor, pls fill in RFC xxxx 267 -- revision history 269 REVISION "200401290000Z" -- 29 January 2004 270 DESCRIPTION "Initial version, published as RFC xxxx." 271 -- RFC Editor, pls assign RFC xxxx 272 ::= { mib-2 nnn } -- To be assigned by IANA 274 -- Top level objects 276 teMIBNotifications OBJECT IDENTIFIER ::= { teMIB 0 } 277 teMIBObjects OBJECT IDENTIFIER ::= { teMIB 1 } 278 teMIBConformance OBJECT IDENTIFIER ::= { teMIB 2 } 280 -- **************************************************************** 281 -- 282 -- TE MIB Objects 283 -- 285 -- TE Info 287 teInfo OBJECT IDENTIFIER ::= { teMIBObjects 1 } 289 teDistProtocol OBJECT-TYPE 290 SYNTAX BITS { 291 other(0), 292 isis(1), 293 ospf(2) 294 } 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION "IGP used to distribute Traffic Engineering 298 information and topology to each device for the 299 purpose of automatic path computation. More than 300 one IGP may be used to distribute TE information. 301 " 302 ::= { teInfo 1 } 304 teSignalingProto OBJECT-TYPE 305 SYNTAX BITS { 306 other(0), 307 rsvpte(1), 308 crldp(2), 309 static(3) -- static configuration 310 } 311 MAX-ACCESS read-only 312 STATUS current 313 DESCRIPTION "Traffic Engineering signaling protocols supported 314 by this device. More than one protocol may be 315 supported. 316 " 317 REFERENCE "For a description of RSVP-TE, see RFC 3209; 318 for CR-LDP, see RFC 3212. 319 " 320 ::= { teInfo 2 } 322 teNotificationEnable OBJECT-TYPE 323 SYNTAX TruthValue 324 MAX-ACCESS read-write 325 STATUS current 326 DESCRIPTION "If this object is true, then it enables the 327 generation of notifications from this MIB module. 328 Otherwise notifications are not generated. 329 " 330 DEFVAL { false } 331 ::= { teInfo 3 } 333 teNextTunnelIndex OBJECT-TYPE 334 SYNTAX Unsigned32 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION "An integer which may be used as a new Index in the 338 teTunnelTable. 340 The special value of 0 indicates that no more new 341 entries can be created in that table. 343 When this MIB module is used for configuration, this 344 object always contains a legal value (if non-zero) 345 for an index that is not currently used in that 346 table. The Command Generator (Network Management 347 Application) reads this variable and uses the 348 (non-zero) value read when creating a new row with 349 an SNMP SET. When the SET is performed, the Command 350 Responder (agent) must determine whether the value 351 is indeed still unused; Two Network Management 352 Applications may attempt to create a row 353 (configuration entry) simultaneously and use the 354 same value. If it is currently unused, the SET 355 succeeds and the Command Responder (agent) changes 356 the value of this object, according to an 357 implementation-specific algorithm. If the value is 358 in use, however, the SET fails. The Network 359 Management Application must then re-read this 360 variable to obtain a new usable value. 361 " 362 ::= { teInfo 4 } 364 teNextPathHopIndex OBJECT-TYPE 365 SYNTAX Unsigned32 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION "An integer which may be used as a new Index in the 369 tePathHopTable. 371 The special value of 0 indicates that no more new 372 entries can be created in that table. 374 When this MIB module is used for configuration, this 375 object always contains a legal value (if non-zero) 376 for an index that is not currently used in that 377 table. The Command Generator (Network Management 378 Application) reads this variable and uses the 379 (non-zero) value read when creating a new row with 380 an SNMP SET. When the SET is performed, the Command 381 Responder (agent) must determine whether the value 382 is indeed still unused; Two Network Management 383 Applications may attempt to create a row 384 (configuration entry) simultaneously and use the 385 same value. If it is currently unused, the SET 386 succeeds and the Command Responder (agent) changes 387 the value of this object, according to an 388 implementation-specific algorithm. If the value is 389 in use, however, the SET fails. The Network 390 Management Application must then re-read this 391 variable to obtain a new usable value. 392 " 394 ::= { teInfo 5 } 396 teConfiguredTunnels OBJECT-TYPE 397 SYNTAX Gauge32 398 MAX-ACCESS read-only 399 STATUS current 400 DESCRIPTION "Number of currently configured Tunnels." 401 ::= { teInfo 6 } 403 teActiveTunnels OBJECT-TYPE 404 SYNTAX Gauge32 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION "Number of currently active Tunnels." 408 ::= { teInfo 7 } 410 tePrimaryTunnels OBJECT-TYPE 411 SYNTAX Gauge32 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION "Number of currently active Tunnels running on 415 their primary paths. 416 " 417 ::= { teInfo 8 } 419 teAdminGroupTable OBJECT-TYPE 420 SYNTAX SEQUENCE OF TeAdminGroupEntry 421 MAX-ACCESS not-accessible 422 STATUS current 423 DESCRIPTION "A mapping of configured administrative groups. Each 424 entry represents an Administrative Group, and 425 provides a name and index for the group. 426 Administrative groups are used to label links in the 427 Traffic Engineering topology in order to place 428 constraints (include and exclude) on Tunnel paths. 430 A groupName can only be linked to one group number. 431 The groupNumber is the number assigned to the 432 administrative group which is used in constraints, 433 like tePathIncludeAny, tePathIncludeAll, etc. 434 " 435 ::= { teInfo 9 } 437 teAdminGroupEntry OBJECT-TYPE 438 SYNTAX TeAdminGroupEntry 439 MAX-ACCESS not-accessible 440 STATUS current 441 DESCRIPTION "A mapping between a configured group number and 442 its human-readable name. The group number should 443 be between 1 and 32, inclusive. Group number n 444 represents bit number (n-1) in the bit vector for 445 Include/Exclude constraints. 447 All entries in this table MUST be kept in stable 448 storage so that they will re-appear in case of a 449 restart/reboot. 450 " 451 INDEX { teAdminGroupNumber } 452 ::= { teAdminGroupTable 1 } 454 TeAdminGroupEntry ::= 455 SEQUENCE { 456 teAdminGroupNumber Integer32, 457 teAdminGroupName SnmpAdminString, 458 teAdminGroupRowStatus RowStatus 459 } 461 teAdminGroupNumber OBJECT-TYPE 462 SYNTAX Integer32 (1..32) 463 MAX-ACCESS not-accessible 464 STATUS current 465 DESCRIPTION "Index of the administrative group." 466 ::= { teAdminGroupEntry 1 } 468 teAdminGroupName OBJECT-TYPE 469 SYNTAX SnmpAdminString (SIZE (1..32)) 470 MAX-ACCESS read-create 471 STATUS current 472 DESCRIPTION "Name of the administrative group." 473 ::= { teAdminGroupEntry 2 } 475 teAdminGroupRowStatus OBJECT-TYPE 476 SYNTAX RowStatus 477 MAX-ACCESS read-create 478 STATUS current 479 DESCRIPTION "The status of this conceptual row. 481 The value of this object has no effect on whether 482 other objects in this conceptual row can be 483 modified. 484 " 485 ::= { teAdminGroupEntry 3 } 487 -- Tunnel Table 489 teTunnelTable OBJECT-TYPE 490 SYNTAX SEQUENCE OF TeTunnelEntry 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION "Table of Configured Traffic Tunnels." 494 ::= { teMIBObjects 2 } 496 teTunnelEntry OBJECT-TYPE 497 SYNTAX TeTunnelEntry 498 MAX-ACCESS not-accessible 499 STATUS current 500 DESCRIPTION "Entry containing information about a particular 501 Traffic Tunnel. 502 " 503 INDEX { teTunnelIndex } 504 ::= { teTunnelTable 1 } 506 TeTunnelEntry ::= 507 SEQUENCE { 508 teTunnelIndex Unsigned32, 509 teTunnelName SnmpAdminString, 510 teTunnelNextPathIndex Unsigned32, 511 -- Conceptual row information: 512 teTunnelRowStatus RowStatus, 513 teTunnelStorageType StorageType, 514 -- Address information: 515 teTunnelSourceAddressType TeHopAddressType, 516 teTunnelSourceAddress TeHopAddress, 517 teTunnelDestinationAddressType TeHopAddressType, 518 teTunnelDestinationAddress TeHopAddress, 519 -- State/performance information: 520 teTunnelState INTEGER, 521 teTunnelDiscontinuityTimer TimeStamp, 522 teTunnelOctets Counter64, 523 teTunnelPackets Counter64, 524 teTunnelLPOctets Counter32, 525 teTunnelLPPackets Counter32, 526 teTunnelAge TimeTicks, 527 teTunnelTimeUp TimeTicks, 528 teTunnelPrimaryTimeUp TimeTicks, 529 teTunnelTransitions Counter32, 530 teTunnelLastTransition TimeTicks, 531 teTunnelPathChanges Counter32, 532 teTunnelLastPathChange TimeTicks, 533 teTunnelConfiguredPaths Gauge32, 534 teTunnelStandbyPaths Gauge32, 535 teTunnelOperationalPaths Gauge32 536 } 538 teTunnelIndex OBJECT-TYPE 539 SYNTAX Unsigned32 (1..4294967295) 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION "A unique index that identifies a Tunnel. If the TE 543 Tunnel is considered an interface, then this index 544 must match the interface index of the corresponding 545 interface. Otherwise, this index must be at least 546 2^24, so that it does not overlap with any existing 547 interface index. 548 " 549 ::= { teTunnelEntry 1 } 551 teTunnelName OBJECT-TYPE 552 SYNTAX SnmpAdminString (SIZE (1..32)) 553 MAX-ACCESS read-create 554 STATUS current 555 DESCRIPTION "Name of the Traffic Tunnel. 557 Note that the name of a Tunnel MUST be unique. 558 When a SET request contains a name that is already 559 in use for another entry, then the implementation 560 must return an inconsistentValue error. 562 The value of this object cannot be changed if the 563 if the value of the corresponding teTunnelRowStatus 564 object is 'active'. 565 " 566 ::= { teTunnelEntry 2 } 568 teTunnelNextPathIndex OBJECT-TYPE 569 SYNTAX Unsigned32 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION "An integer which may be used as a new Index for the 573 next Path in this Tunnel. 575 The special value of 0 indicates that no more Paths 576 can be created for this Tunnel, or that no more new 577 entries can be created in tePathTable. 579 When this MIB module is used for configuration, this 580 object always contains a legal value (if non-zero) 581 for an index that is not currently used in that 582 table. The Command Generator (Network Management 583 Application) reads this variable and uses the 584 (non-zero) value read when creating a new row with 585 an SNMP SET. When the SET is performed, the Command 586 Responder (agent) must determine whether the value 587 is indeed still unused; Two Network Management 588 Applications may attempt to create a row 589 (configuration entry) simultaneously and use the 590 same value. If it is currently unused, the SET 591 succeeds and the Command Responder (agent) changes 592 the value of this object, according to an 593 implementation-specific algorithm. If the value is 594 in use, however, the SET fails. The Network 595 Management Application must then re-read this 596 variable to obtain a new usable value. 597 " 598 ::= { teTunnelEntry 3 } 600 teTunnelRowStatus OBJECT-TYPE 601 SYNTAX RowStatus 602 MAX-ACCESS read-create 603 STATUS current 604 DESCRIPTION "The status of this conceptual row. 606 When the value of this object is 'active', then 607 the values for the corresponding objects 608 teTunnelName, teTunnelSourceAddressType, 609 teTunnelSourceAddress, 610 teTunnelDestinationAddressType and 611 teTunnelDestinationAddress cannot be changed. 612 " 613 ::= { teTunnelEntry 4 } 615 teTunnelStorageType OBJECT-TYPE 616 SYNTAX StorageType 617 MAX-ACCESS read-create 618 STATUS current 619 DESCRIPTION "The storage type for this conceptual row. 621 Conceptual rows having the value 'permanent' need 622 not allow write-access to any columnar objects 623 in the row. 624 " 625 ::= { teTunnelEntry 5 } 627 teTunnelSourceAddressType OBJECT-TYPE 628 SYNTAX TeHopAddressType 629 MAX-ACCESS read-create 630 STATUS current 631 DESCRIPTION "The type of Traffic Engineered Tunnel hop address 632 for the source of this Tunnel. Typically, this 633 address type is IPv4 or IPv6, with a prefix length 634 of 32 or 128 respectively. If the TE Tunnel path 635 is being computed by a path computation server, 636 however, it is possible to use more flexible source 637 address types, such as AS numbers or prefix lengths 638 less than host address lengths. 640 The value of this object cannot be changed if the 641 if the value of the corresponding teTunnelRowStatus 642 object is 'active'. 643 " 644 ::= { teTunnelEntry 6 } 646 teTunnelSourceAddress OBJECT-TYPE 647 SYNTAX TeHopAddress 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION "Source Traffic Engineered Tunnel hop address of 651 this Tunnel. 653 The type of this address is determined by the value 654 of the corresponding teTunnelSourceAddressType. 656 Note that source and destination addresses of a 657 Tunnel can be different address types. 659 The value of this object cannot be changed if the 660 if the value of the corresponding teTunnelRowStatus 661 object is 'active'. 662 " 663 ::= { teTunnelEntry 7 } 665 teTunnelDestinationAddressType OBJECT-TYPE 666 SYNTAX TeHopAddressType 667 MAX-ACCESS read-create 668 STATUS current 669 DESCRIPTION "The type of Traffic Engineered Tunnel hop address 670 for the destination of this Tunnel. 672 The value of this object cannot be changed if the 673 if the value of the corresponding teTunnelRowStatus 674 object is 'active'. 675 " 676 ::= { teTunnelEntry 8 } 678 teTunnelDestinationAddress OBJECT-TYPE 679 SYNTAX TeHopAddress 680 MAX-ACCESS read-create 681 STATUS current 682 DESCRIPTION "Destination Traffic Engineered Tunnel hop address 683 of this Tunnel. 685 The type of this address is determined by the value 686 of the corresponding teTunnelDestinationAddressType. 688 Note that source and destination addresses of a 689 Tunnel can be different address types. 691 The value of this object cannot be changed if the 692 if the value of the corresponding teTunnelRowStatus 693 object is 'active'. 694 " 695 ::= { teTunnelEntry 9 } 697 teTunnelState OBJECT-TYPE 698 SYNTAX INTEGER { 699 unknown(1), 700 up(2), 701 down(3), 702 testing(4) 703 } 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION "The operational state of the Tunnel." 707 ::= { teTunnelEntry 10 } 709 teTunnelDiscontinuityTimer OBJECT-TYPE 710 SYNTAX TimeStamp 711 MAX-ACCESS read-only 712 STATUS current 713 DESCRIPTION "The value of sysUpTime on the most recent occasion 714 at which any one or more of this tunnel's counters 715 suffered a discontinuity. The relevant counters 716 are teTunnelOctets, teTunnelPackets, 717 teTunnelLPOctets and teTunnelLPPackets. If no such 718 discontinuities have occurred since the last 719 re-initialization of the local management subsystem, 720 then this object contains a zero value. 721 " 722 ::= { teTunnelEntry 11 } 724 teTunnelOctets OBJECT-TYPE 725 SYNTAX Counter64 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION "The number of octets that have been forwarded over 729 the Tunnel. 731 Discontinuities in the value of this counter can 732 occur at re-initialization of the management system, 733 and at other times as indicated by the value of 734 teTunnelDiscontinuityTimer. 735 " 736 ::= { teTunnelEntry 12 } 738 teTunnelPackets OBJECT-TYPE 739 SYNTAX Counter64 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION "The number of packets that have been forwarded over 743 the Tunnel. 745 Discontinuities in the value of this counter can 746 occur at re-initialization of the management system, 747 and at other times as indicated by the value of 748 teTunnelDiscontinuityTimer. 749 " 750 ::= { teTunnelEntry 13 } 752 teTunnelLPOctets OBJECT-TYPE 753 SYNTAX Counter32 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION "The number of octets that have been forwarded over 757 the Tunnel. 759 Discontinuities in the value of this counter can 760 occur at re-initialization of the management system, 761 and at other times as indicated by the value of 762 teTunnelDiscontinuityTimer. 763 " 764 ::= { teTunnelEntry 14 } 766 teTunnelLPPackets OBJECT-TYPE 767 SYNTAX Counter32 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION "The number of packets that have been forwarded over 771 the Tunnel. 773 Discontinuities in the value of this counter can 774 occur at re-initialization of the management system, 775 and at other times as indicated by the value of 776 teTunnelDiscontinuityTimer. 777 " 778 ::= { teTunnelEntry 15 } 780 teTunnelAge OBJECT-TYPE 781 SYNTAX TimeTicks 782 MAX-ACCESS read-only 783 STATUS current 784 DESCRIPTION "The age (i.e., time from creation of this conceptual 785 row till now) of this Tunnel in hundredths of a 786 second. Note that since TimeTicks wrap in about 16 787 months, this value is best used in interval 788 measurements. 789 " 790 ::= { teTunnelEntry 16 } 792 teTunnelTimeUp OBJECT-TYPE 793 SYNTAX TimeTicks 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION "The total time in hundredths of a second that this 797 Tunnel has been operational. Note that since 798 TimeTicks wrap in about 16 months, this value is 799 best used in interval measurements. 801 An example usage of this object is to compute the 802 percentage up time over a period of time, by 803 obtaining values of teTunnelAge and teTunnelTimeUp 804 at two points in time, and computing the following 805 ratio: ((teTunnelTimeUp2 - teTunnelTimeUp1)/ 806 (teTunnelAge2 - teTunnelAge1)) * 100 %. In doing 807 so, the management station must account for 808 wrapping of the values of teTunnelAge and 809 teTunnelTimeUp between the two measurements. 810 " 811 ::= { teTunnelEntry 17 } 813 teTunnelPrimaryTimeUp OBJECT-TYPE 814 SYNTAX TimeTicks 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION "The total time in hundredths of a second that this 818 Tunnel's primary path has been operational. Note 819 that since TimeTicks wrap in about 16 months, this 820 value is best used in interval measurements. 822 An example usage of this field is to compute what 823 percentage of time that a TE Tunnel was on the 824 primary path over a period of time, by computing 825 ((teTunnelPrimaryTimeUp2 - teTunnelPrimaryTimeUp1)/ 826 (teTunnelTimeUp2 - teTunnelTimeUp1))*100 %. In 827 doing so, the management station must account for 828 wrapping of the values of teTunnelPrimaryTimeUp and 829 teTunnelTimeUp between the two measurements. 830 " 831 ::= { teTunnelEntry 18 } 833 teTunnelTransitions OBJECT-TYPE 834 SYNTAX Counter32 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION "The number of operational state transitions 838 (up -> down and down -> up) this Tunnel has 839 undergone. 840 " 841 ::= { teTunnelEntry 19 } 843 teTunnelLastTransition OBJECT-TYPE 844 SYNTAX TimeTicks 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION "The time in hundredths of a second since the last 848 operational state transition occurred on this 849 Tunnel. 851 Note that if the last transition was over 16 852 months ago, this value will be inaccurate. 853 " 854 ::= { teTunnelEntry 20 } 856 teTunnelPathChanges OBJECT-TYPE 857 SYNTAX Counter32 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION "The number of path changes this Tunnel has had." 861 ::= { teTunnelEntry 21 } 863 teTunnelLastPathChange OBJECT-TYPE 864 SYNTAX TimeTicks 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION "The time in hundredths of a second since the last 868 path change occurred on this Tunnel. 870 Note that if the last transition was over 16 871 months ago, this value will be inaccurate. 872 " 873 ::= { teTunnelEntry 22 } 875 teTunnelConfiguredPaths OBJECT-TYPE 876 SYNTAX Gauge32 877 MAX-ACCESS read-only 878 STATUS current 879 DESCRIPTION "The number of paths configured for this Tunnel." 880 ::= { teTunnelEntry 23 } 882 teTunnelStandbyPaths OBJECT-TYPE 883 SYNTAX Gauge32 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION "The number of standby paths configured for this 887 Tunnel. 888 " 889 ::= { teTunnelEntry 24 } 891 teTunnelOperationalPaths OBJECT-TYPE 892 SYNTAX Gauge32 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION "The number of operational paths for this Tunnel. 896 This includes the path currently active, as 897 well as operational standby paths. 898 " 899 ::= { teTunnelEntry 25 } 901 -- **************************************************************** 902 -- 903 -- Tunnel Path Table 904 -- 906 tePathTable OBJECT-TYPE 907 SYNTAX SEQUENCE OF TePathEntry 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION "Table of Configured Traffic Tunnels." 911 ::= { teMIBObjects 3 } 913 tePathEntry OBJECT-TYPE 914 SYNTAX TePathEntry 915 MAX-ACCESS not-accessible 916 STATUS current 917 DESCRIPTION "Entry containing information about a particular 918 Traffic Tunnel. Each Traffic Tunnel can have zero 919 or more Traffic Paths. 921 Since a Traffic Path can only exist over an existing 922 Trafic Tunnel, it means that all tePathEntries with 923 a value of n for teTunnelIndex MUST be removed by 924 the implementation when the corresponding 925 teTunnelEntry with a value of n for teTunnelIndex 926 is removed. 927 " 928 INDEX { teTunnelIndex, tePathIndex } 929 ::= { tePathTable 1 } 931 TePathEntry ::= 932 SEQUENCE { 933 tePathIndex Unsigned32, 934 tePathName SnmpAdminString, 935 -- Conceptual row information 936 tePathRowStatus RowStatus, 937 tePathStorageType StorageType, 938 -- Path properties 939 tePathType INTEGER, 940 tePathConfiguredRoute Unsigned32, 941 tePathBandwidth MplsBitRate, 942 tePathIncludeAny Unsigned32, 943 tePathIncludeAll Unsigned32, 944 tePathExclude Unsigned32, 945 tePathSetupPriority Integer32, 946 tePathHoldPriority Integer32, 947 tePathProperties BITS, 948 -- Path status 949 tePathOperStatus INTEGER, 950 tePathAdminStatus INTEGER, 951 tePathComputedRoute Unsigned32, 952 tePathRecordedRoute Unsigned32 953 } 955 tePathIndex OBJECT-TYPE 956 SYNTAX Unsigned32 (1..4294967295) 957 MAX-ACCESS not-accessible 958 STATUS current 959 DESCRIPTION "An index that uniquely identifies a path within 960 a Tunnel. 962 The combination of thus 963 uniquely identifies a path among all paths on this 964 router. 965 " 966 ::= { tePathEntry 1 } 968 tePathName OBJECT-TYPE 969 SYNTAX SnmpAdminString (SIZE(0..32)) 970 MAX-ACCESS read-create 971 STATUS current 972 DESCRIPTION "The name of this path. 974 A pathName must be unique within the set of paths 975 over a single tunnel. If a SET request is received 976 with a duplicate name, then the implementation MUST 977 return an inconsistentValue error. 979 The value of this object cannot be changed if the 980 if the value of the corresponding teTunnelRowStatus 981 object is 'active'. 982 " 983 ::= { tePathEntry 2 } 985 tePathRowStatus OBJECT-TYPE 986 SYNTAX RowStatus 987 MAX-ACCESS read-create 988 STATUS current 989 DESCRIPTION "The status of this conceptual row. 991 When the value of this object is 'active', then 992 the value of tePathName cannot be changed. All 993 other writable objects may be changed; however, 994 these changes may affect traffic going over the TE 995 tunnel, or require the path to be computed and/or 996 re-signalled. 997 " 998 ::= { tePathEntry 3 } 1000 tePathStorageType OBJECT-TYPE 1001 SYNTAX StorageType 1002 MAX-ACCESS read-create 1003 STATUS current 1004 DESCRIPTION "The storage type for this conceptual row. 1006 Conceptual rows having the value 'permanent' need 1007 not allow write-access to any columnar objects 1008 in the row. 1009 " 1010 ::= { tePathEntry 4 } 1012 tePathType OBJECT-TYPE 1013 SYNTAX INTEGER { 1014 other(1), 1015 primary(2), 1016 standby(3), 1017 secondary(4) 1018 } 1019 MAX-ACCESS read-create 1020 STATUS current 1021 DESCRIPTION "The type for this PathEntry, i.e., whether this path 1022 is a primary path, a standby path, or a secondary 1023 path. 1024 " 1025 ::= { tePathEntry 5 } 1027 tePathConfiguredRoute OBJECT-TYPE 1028 SYNTAX Unsigned32 1029 MAX-ACCESS read-create 1030 STATUS current 1031 DESCRIPTION "The route that this TE path is configured to follow, 1032 i.e., an ordered list of hops. The value of this 1033 object gives the primary index into the Hop Table; 1034 the secondary index is the hop count in the path, so 1035 to get the route, one could get the first hop with 1036 index in the Hop Table, 1037 and do a getnext to get subsequent hops. 1038 " 1039 ::= { tePathEntry 6 } 1041 tePathBandwidth OBJECT-TYPE 1042 SYNTAX MplsBitRate 1043 UNITS "Kilobits per second" 1044 MAX-ACCESS read-create 1045 STATUS current 1046 DESCRIPTION "The configured bandwidth for this Tunnel, 1047 in units of thousands of bits per second (Kbps). 1048 " 1049 DEFVAL { 0 } 1050 ::= { tePathEntry 7 } 1052 tePathIncludeAny OBJECT-TYPE 1053 SYNTAX Unsigned32 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION "This is a configured set of administrative groups 1057 specified as a bit vector (i.e., bit n is 1 if group 1058 n is in the set, where n = 0 is the LSB). For each 1059 link that this path goes through, the link must have 1060 at least one of the groups specified in IncludeAny 1061 to be acceptable. If IncludeAny is zero, all links 1062 are acceptable. 1063 " 1064 DEFVAL { 0 } 1065 ::= { tePathEntry 8 } 1067 tePathIncludeAll OBJECT-TYPE 1068 SYNTAX Unsigned32 1069 MAX-ACCESS read-create 1070 STATUS current 1071 DESCRIPTION "This is a configured set of administrative groups 1072 specified as a bit vector (i.e., bit n is 1 if group 1073 n is in the set, where n = 0 is the LSB). For each 1074 link that this path goes through, the link must have 1075 all of the groups specified in IncludeAny to be 1076 acceptable. If IncludeAny is zero, all links are 1077 acceptable. 1078 " 1079 DEFVAL { 0 } 1080 ::= { tePathEntry 9 } 1082 tePathExclude OBJECT-TYPE 1083 SYNTAX Unsigned32 1084 MAX-ACCESS read-create 1085 STATUS current 1086 DESCRIPTION "This is a configured set of administrative groups 1087 specified as a bit vector (i.e., bit n is 1 if group 1088 n is in the set, where n = 0 is the LSB). For each 1089 link that this path goes through, the link MUST have 1090 groups associated with it, and the intersection of 1091 the link's groups and the 'exclude' set MUST be 1092 null. 1093 " 1094 DEFVAL { 0 } 1095 ::= { tePathEntry 10 } 1097 tePathSetupPriority OBJECT-TYPE 1098 SYNTAX Integer32 (0..7) 1099 MAX-ACCESS read-create 1100 STATUS current 1101 DESCRIPTION "The setup priority configured for this path, with 0 1102 as the highest priority and 7 the lowest. 1103 " 1104 DEFVAL { 7 } 1105 ::= { tePathEntry 11 } 1107 tePathHoldPriority OBJECT-TYPE 1108 SYNTAX Integer32 (0..7) 1109 MAX-ACCESS read-create 1110 STATUS current 1111 DESCRIPTION "The hold priority configured for this path, with 0 1112 as the highest priority and 7 the lowest. 1113 " 1114 DEFVAL { 0 } 1115 ::= { tePathEntry 12 } 1117 tePathProperties OBJECT-TYPE 1118 SYNTAX BITS { 1119 recordRoute(0), 1120 cspf(1), 1121 makeBeforeBreak(2), 1122 mergeable(3), 1123 fastReroute(4), 1124 protected(5) 1125 } 1126 MAX-ACCESS read-create 1127 STATUS current 1128 DESCRIPTION "The set of configured properties for this path, 1129 expressed as a bit map. For example, if the path 1130 supports 'make before break', then bit 2 is set. 1131 " 1132 ::= { tePathEntry 13 } 1134 tePathOperStatus OBJECT-TYPE 1135 SYNTAX INTEGER { 1136 unknown(0), 1137 down(1), 1138 testing(2), 1139 dormant(3), 1140 ready(4), 1141 operational(5) 1142 } 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION "The operational status of the path: 1146 unknown: 1147 down: signaling failed 1148 testing: administratively set aside for testing 1149 dormant: not signaled (for a backup tunnel) 1150 ready: signaled but not yet carrying traffic 1151 operational: signaled and carrying traffic. 1152 " 1153 ::= { tePathEntry 14 } 1155 tePathAdminStatus OBJECT-TYPE 1156 SYNTAX INTEGER { 1157 normal(1), 1158 testing(2) 1159 } 1160 MAX-ACCESS read-create 1161 STATUS current 1162 DESCRIPTION "The operational status of the path: 1163 normal: used normally for forwarding 1164 testing: administratively set aside for testing. 1166 " 1167 ::= { tePathEntry 15 } 1169 tePathComputedRoute OBJECT-TYPE 1170 SYNTAX Unsigned32 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION "The route computed for for this path, perhaps using 1174 some form of Constraint-based Routing. The 1175 algorithm is implementation dependent. 1177 This object returns the computed route as an ordered 1178 list of hops. The value of this object gives the 1179 primary index into the Hop Table; the secondary 1180 index is the hop count in the path, so to get the 1181 route, one could get the first hop with index 1182 in the Hop Table, and do a 1183 getnext to get subsequent hops. 1185 A value of zero (0) means there is no computedRoute. 1186 " 1187 ::= { tePathEntry 16 } 1189 tePathRecordedRoute OBJECT-TYPE 1190 SYNTAX Unsigned32 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION "The route actually used for this path, as recorded 1194 by the signaling protocol. This is again an ordered 1195 list of hops; each hop is expected to be strict. 1197 The value of this object gives the primary index 1198 into the Hop Table; the secondary index is the hop 1199 count in the path, so to get the route, one can get 1200 the first hop with index 1201 in the Hop Table, and do a getnext to get subsequent 1202 hops. 1204 A value of zero (0) means there is no recordedRoute. 1205 " 1206 ::= { tePathEntry 17 } 1208 -- **************************************************************** 1209 -- 1210 -- Tunnel Path Hop Table 1211 -- 1213 tePathHopTable OBJECT-TYPE 1214 SYNTAX SEQUENCE OF TePathHopEntry 1215 MAX-ACCESS not-accessible 1216 STATUS current 1217 DESCRIPTION "Table of Tunnel Path Hops." 1218 ::= { teMIBObjects 4 } 1220 tePathHopEntry OBJECT-TYPE 1221 SYNTAX TePathHopEntry 1222 MAX-ACCESS not-accessible 1223 STATUS current 1224 DESCRIPTION "Entry containing information about a particular 1225 hop. 1226 " 1227 INDEX { teHopListIndex, tePathHopIndex } 1228 ::= { tePathHopTable 1 } 1230 TePathHopEntry ::= 1231 SEQUENCE { 1232 teHopListIndex Unsigned32, 1233 tePathHopIndex Unsigned32, 1234 -- Conceptual row information 1235 tePathHopRowStatus RowStatus, 1236 tePathHopStorageType StorageType, 1237 tePathHopAddrType TeHopAddressType, 1238 tePathHopAddress TeHopAddress, 1239 tePathHopType INTEGER 1240 } 1242 teHopListIndex OBJECT-TYPE 1243 SYNTAX Unsigned32 (1..4294967295) 1244 MAX-ACCESS not-accessible 1245 STATUS current 1246 DESCRIPTION "An index that identifies a list of hops. This is 1247 the primary index to accesses hops. 1248 " 1249 ::= { tePathHopEntry 1 } 1251 tePathHopIndex OBJECT-TYPE 1252 SYNTAX Unsigned32 (1..4294967295) 1253 MAX-ACCESS not-accessible 1254 STATUS current 1255 DESCRIPTION "An index that identifies a particular hop among the 1256 list of hops for a path. An index of i identifies 1257 the ith hop. This is the secondary index for a hop 1258 entry. 1259 " 1260 ::= { tePathHopEntry 2 } 1262 tePathHopRowStatus OBJECT-TYPE 1263 SYNTAX RowStatus 1264 MAX-ACCESS read-create 1265 STATUS current 1266 DESCRIPTION "The status of this conceptual row. 1268 Any field in this table can be changed, even if the 1269 value of this object is 'active'. However, such a 1270 change may cause traffic to be rerouted or even 1271 disrupted. 1272 " 1273 ::= { tePathHopEntry 3 } 1275 tePathHopStorageType OBJECT-TYPE 1276 SYNTAX StorageType 1277 MAX-ACCESS read-create 1278 STATUS current 1279 DESCRIPTION "The storage type for this conceptual row. 1281 Conceptual rows having the value 'permanent' need 1282 not allow write-access to any columnar objects 1283 in the row. 1284 " 1285 ::= { tePathHopEntry 4 } 1287 tePathHopAddrType OBJECT-TYPE 1288 SYNTAX TeHopAddressType 1289 MAX-ACCESS read-create 1290 STATUS current 1291 DESCRIPTION "The type of Traffic Engineered Tunnel hop Address 1292 of this hop. 1294 The value of this object cannot be changed if the 1295 if the value of the corresponding tePathRowStatus 1296 object is 'active'. 1297 " 1298 ::= { tePathHopEntry 5 } 1300 tePathHopAddress OBJECT-TYPE 1301 SYNTAX TeHopAddress 1302 MAX-ACCESS read-create 1303 STATUS current 1304 DESCRIPTION "Traffic Engineered Tunnel hop Address of this hop. 1306 The type of this address is determined by the value 1307 of the corresponding tePathHopAddressType. 1309 The value of this object cannot be changed if the 1310 if the value of the corresponding teTunnelRowStatus 1311 object is 'active'. 1312 " 1313 ::= { tePathHopEntry 6 } 1315 tePathHopType OBJECT-TYPE 1316 SYNTAX INTEGER { 1317 unknown(0), 1318 loose(1), 1319 strict(2) 1320 } 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION "The type of hop: 1324 unknown: 1325 loose: this hop is a LOOSE hop. 1326 strict: this hop is a STRICT hop. 1327 " 1328 ::= { tePathHopEntry 7 } 1330 -- **************************************************************** 1331 -- 1332 -- TE Notifications 1333 -- 1335 teTunnelUp NOTIFICATION-TYPE 1336 OBJECTS { teTunnelName, 1337 tePathName } -- TunnelPath 1338 STATUS current 1339 DESCRIPTION "A teTunnelUp notification is generated when the 1340 Tunnel indexed by teTunnelName transitions to the 1341 'up' state. 1343 A tunnel is up when at least one of its paths is up. 1344 The tePathName is the name of the path whose 1345 transition to up made the tunnel go up. 1347 This notification MUST be limited to at most one 1348 every minute, in case the tunnel flaps up and down. 1349 " 1350 ::= { teMIBNotifications 1 } 1352 teTunnelDown NOTIFICATION-TYPE 1353 OBJECTS { teTunnelName, 1354 tePathName } -- TunnelPath 1355 STATUS current 1356 DESCRIPTION "A teTunnelDown notification is generated when the 1357 Tunnel indexed by teTunnelName transitions to the 1358 'down' state. 1360 A tunnel is up when at least one of its paths is up. 1361 The tePathName is the name of the path whose 1362 transition to down made the tunnel go down. 1364 This notification MUST be limited to at most one 1365 every minute, in case the tunnel flaps up and down. 1366 " 1367 ::= { teMIBNotifications 2 } 1369 teTunnelChanged NOTIFICATION-TYPE 1370 OBJECTS { teTunnelName, 1371 tePathName } -- toTunnelPath 1372 STATUS current 1373 DESCRIPTION "A teTunnelChanged notification is generated when an 1374 active path on the Tunnel indexed by teTunnelName 1375 changes, or a new path becomes active. The value 1376 of tePathName is the new active path. 1378 This notification MUST be limited to at most one 1379 every minute, in case the tunnel changes quickly. 1380 " 1381 ::= { teMIBNotifications 3 } 1383 teTunnelRerouted NOTIFICATION-TYPE 1384 OBJECTS { teTunnelName, 1385 tePathName } -- toTunnelPath 1386 STATUS current 1387 DESCRIPTION "A teTunnelRerouted notification is generated when 1388 an active path for the Tunnel indexed by 1389 teTunnelName stays the same, but its route changes. 1391 This notification MUST be limited to at most one 1392 every minute, in case the tunnel reroutes quickly. 1393 " 1394 ::= { teMIBNotifications 4 } 1396 -- End of TE-MIB objects 1398 -- **************************************************************** 1399 -- 1400 -- TE Compliance Statements 1401 -- 1403 teGroups 1404 OBJECT IDENTIFIER ::= { teMIBConformance 1 } 1406 teModuleCompliance 1407 OBJECT IDENTIFIER ::= { teMIBConformance 2 } 1409 -- **************************************************************** 1410 -- 1411 -- TE object groups 1412 -- 1414 teTrafficEngineeringGroup OBJECT-GROUP 1415 OBJECTS { 1416 teTunnelName, 1417 teTunnelNextPathIndex, 1418 teTunnelRowStatus, 1419 teTunnelStorageType, 1420 teTunnelSourceAddressType, 1421 teTunnelSourceAddress, 1422 teTunnelDestinationAddressType, 1423 teTunnelDestinationAddress, 1424 teTunnelState, 1425 teTunnelDiscontinuityTimer, 1426 teTunnelOctets, 1427 teTunnelPackets, 1428 teTunnelLPOctets, 1429 teTunnelLPPackets, 1430 teTunnelAge, 1431 teTunnelTimeUp, 1432 teTunnelPrimaryTimeUp, 1433 teTunnelTransitions, 1434 teTunnelLastTransition, 1435 teTunnelPathChanges, 1436 teTunnelLastPathChange, 1437 teTunnelConfiguredPaths, 1438 teTunnelStandbyPaths, 1439 teTunnelOperationalPaths, 1440 tePathBandwidth, 1441 tePathIncludeAny, 1442 tePathIncludeAll, 1443 tePathExclude, 1444 tePathSetupPriority, 1445 tePathHoldPriority, 1446 tePathProperties, 1447 tePathOperStatus, 1448 tePathAdminStatus, 1449 tePathComputedRoute, 1450 tePathRecordedRoute, 1451 teDistProtocol, 1452 teSignalingProto, 1453 teNotificationEnable, 1454 teNextTunnelIndex, 1455 teNextPathHopIndex, 1456 teAdminGroupName, 1457 teAdminGroupRowStatus, 1458 teConfiguredTunnels, 1459 teActiveTunnels, 1460 tePrimaryTunnels, 1461 tePathName, 1462 tePathType, 1463 tePathRowStatus, 1464 tePathStorageType, 1465 tePathConfiguredRoute, 1466 tePathHopRowStatus, 1467 tePathHopStorageType, 1468 tePathHopAddrType, 1469 tePathHopAddress, 1470 tePathHopType 1471 } 1472 STATUS current 1473 DESCRIPTION "Objects for Traffic Engineering in this MIB module." 1475 ::= { teGroups 1 } 1477 teNotificationGroup NOTIFICATION-GROUP 1478 NOTIFICATIONS { 1479 teTunnelUp, 1480 teTunnelDown, 1481 teTunnelChanged, 1482 teTunnelRerouted 1483 } 1484 STATUS current 1485 DESCRIPTION "Notifications specified in this MIB module." 1486 ::= { teGroups 2 } 1488 -- **************************************************************** 1489 -- 1490 -- TE compliance statements 1491 -- 1492 -- There are four compliance statements: read-only and full 1493 -- compliance for regular TE devices, and read-only and full 1494 -- compliance for path computation servers. 1495 -- 1497 teModuleReadOnlyCompliance MODULE-COMPLIANCE 1498 STATUS current 1499 DESCRIPTION "When this MIB module is implemented without support 1500 for read-create (i.e. in read-only mode), then such 1501 an implementation can claim read-only compliance. 1503 Such a device can then be monitored but can not be 1504 configured with this MIB module. 1505 " 1507 MODULE -- enclosing module, i.e., TE-MIB 1509 MANDATORY-GROUPS { 1510 teTrafficEngineeringGroup 1511 } 1513 GROUP teNotificationGroup 1514 DESCRIPTION "Implementation of this group is optional." 1516 OBJECT teNotificationEnable 1517 MIN-ACCESS read-only 1518 DESCRIPTION "Write access is not required." 1520 OBJECT teAdminGroupName 1521 MIN-ACCESS read-only 1522 DESCRIPTION "Write access is not required." 1524 OBJECT teAdminGroupRowStatus 1525 SYNTAX RowStatus { active(1) } 1526 MIN-ACCESS read-only 1527 DESCRIPTION "Write access is not required." 1529 OBJECT teTunnelName 1530 MIN-ACCESS read-only 1531 DESCRIPTION "Write access is not required." 1533 OBJECT teTunnelRowStatus 1534 SYNTAX RowStatus { active(1) } 1535 MIN-ACCESS read-only 1536 DESCRIPTION "Write access is not required." 1538 OBJECT teTunnelStorageType 1539 MIN-ACCESS read-only 1540 DESCRIPTION "Write access is not required." 1542 OBJECT teTunnelSourceAddressType 1543 SYNTAX TeHopAddressType { ipv4(1), ipv6(2) } 1544 MIN-ACCESS read-only 1545 DESCRIPTION "Write access is not required. An 1546 implementation is only required to support 1547 IPv4 and IPv6 host addresses." 1549 OBJECT teTunnelSourceAddress 1550 MIN-ACCESS read-only 1551 DESCRIPTION "Write access is not required." 1553 OBJECT teTunnelDestinationAddressType 1554 MIN-ACCESS read-only 1555 DESCRIPTION "Write access is not required." 1557 OBJECT teTunnelDestinationAddress 1558 MIN-ACCESS read-only 1559 DESCRIPTION "Write access is not required." 1561 OBJECT tePathName 1562 MIN-ACCESS read-only 1563 DESCRIPTION "Write access is not required." 1565 OBJECT tePathRowStatus 1566 SYNTAX RowStatus { active(1) } 1567 MIN-ACCESS read-only 1568 DESCRIPTION "Write access is not required." 1570 OBJECT tePathStorageType 1571 MIN-ACCESS read-only 1572 DESCRIPTION "Write access is not required." 1574 OBJECT tePathType 1575 MIN-ACCESS read-only 1576 DESCRIPTION "Write access is not required." 1578 OBJECT tePathConfiguredRoute 1579 MIN-ACCESS read-only 1580 DESCRIPTION "Write access is not required." 1582 OBJECT tePathBandwidth 1583 MIN-ACCESS read-only 1584 DESCRIPTION "Write access is not required." 1586 OBJECT tePathIncludeAny 1587 MIN-ACCESS read-only 1588 DESCRIPTION "Write access is not required." 1590 OBJECT tePathIncludeAll 1591 MIN-ACCESS read-only 1592 DESCRIPTION "Write access is not required." 1594 OBJECT tePathExclude 1595 MIN-ACCESS read-only 1596 DESCRIPTION "Write access is not required." 1598 OBJECT tePathSetupPriority 1599 MIN-ACCESS read-only 1600 DESCRIPTION "Write access is not required." 1602 OBJECT tePathHoldPriority 1603 MIN-ACCESS read-only 1604 DESCRIPTION "Write access is not required." 1606 OBJECT tePathProperties 1607 MIN-ACCESS read-only 1608 DESCRIPTION "Write access is not required." 1610 OBJECT tePathAdminStatus 1611 MIN-ACCESS read-only 1612 DESCRIPTION "Write access is not required." 1614 OBJECT tePathHopRowStatus 1615 SYNTAX RowStatus { active(1) } 1616 MIN-ACCESS read-only 1617 DESCRIPTION "Write access is not required." 1619 OBJECT tePathHopStorageType 1620 MIN-ACCESS read-only 1621 DESCRIPTION "Write access is not required." 1623 OBJECT tePathHopAddrType 1624 MIN-ACCESS read-only 1625 DESCRIPTION "Write access is not required." 1627 OBJECT tePathHopAddress 1628 MIN-ACCESS read-only 1629 DESCRIPTION "Write access is not required." 1631 ::= { teModuleCompliance 1 } 1633 teModuleFullCompliance MODULE-COMPLIANCE 1634 STATUS current 1635 DESCRIPTION "When this MIB module is implemented with support for 1636 read-create, then such an implementation can claim 1637 full compliance. Such devices can then be both 1638 monitored and configured with this MIB module. 1639 " 1641 MODULE -- enclosing module, i.e., TE-MIB 1643 MANDATORY-GROUPS { 1644 teTrafficEngineeringGroup 1645 } 1646 GROUP teNotificationGroup 1647 DESCRIPTION "Implementation of this group is optional." 1649 OBJECT teAdminGroupRowStatus 1650 SYNTAX RowStatus { active(1) } 1651 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 1652 DESCRIPTION "Support for notInService, createAndWait and 1653 notReady is not required. 1654 " 1656 OBJECT teTunnelRowStatus 1657 SYNTAX RowStatus { active(1), notInService(2) } 1658 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1659 createAndGo(4), destroy(6) 1660 } 1661 DESCRIPTION "Support for createAndWait and notReady is not 1662 required. 1663 " 1665 OBJECT teTunnelSourceAddressType 1666 SYNTAX TeHopAddressType { ipv4(1), ipv6(2) } 1667 DESCRIPTION "Write access is required. An implementation is 1668 only required to support IPv4 and IPv6 host 1669 addresses. 1670 " 1672 OBJECT tePathRowStatus 1673 SYNTAX RowStatus { active(1), notInService(2) } 1674 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1675 createAndGo(4), destroy(6) 1676 } 1677 DESCRIPTION "Support for createAndWait and notReady is not 1678 required. 1679 " 1681 OBJECT tePathHopRowStatus 1682 SYNTAX RowStatus { active(1), notInService(2) } 1683 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1684 createAndGo(4), destroy(6) 1685 } 1686 DESCRIPTION "Support for createAndWait and notReady is not 1687 required. 1688 " 1690 ::= { teModuleCompliance 2 } 1692 teModuleServerReadOnlyCompliance MODULE-COMPLIANCE 1693 STATUS current 1694 DESCRIPTION "When this MIB module is implemented by a path 1695 computation server without support for read-create 1696 (i.e. in read-only mode), then such an 1697 implementation can claim read-only compliance. Such 1698 a device can then be monitored but can not be 1699 configured with this MIB module. 1700 " 1702 MODULE -- enclosing module, i.e., TE-MIB 1704 MANDATORY-GROUPS { 1705 teTrafficEngineeringGroup 1706 } 1708 GROUP teNotificationGroup 1709 DESCRIPTION "Implementation of this group is optional." 1711 OBJECT teNotificationEnable 1712 MIN-ACCESS read-only 1713 DESCRIPTION "Write access is not required." 1715 OBJECT teAdminGroupName 1716 MIN-ACCESS read-only 1717 DESCRIPTION "Write access is not required." 1719 OBJECT teAdminGroupRowStatus 1720 SYNTAX RowStatus { active(1) } 1721 MIN-ACCESS read-only 1722 DESCRIPTION "Write access is not required." 1724 OBJECT teTunnelName 1725 MIN-ACCESS read-only 1726 DESCRIPTION "Write access is not required." 1728 OBJECT teTunnelRowStatus 1729 SYNTAX RowStatus { active(1) } 1730 MIN-ACCESS read-only 1731 DESCRIPTION "Write access is not required." 1733 OBJECT teTunnelStorageType 1734 MIN-ACCESS read-only 1735 DESCRIPTION "Write access is not required." 1737 OBJECT teTunnelSourceAddressType 1738 MIN-ACCESS read-only 1739 DESCRIPTION "Write access is not required. A path 1740 computation server SHOULD implement all types 1741 of tunnel source address types. 1742 " 1744 OBJECT teTunnelSourceAddress 1745 MIN-ACCESS read-only 1746 DESCRIPTION "Write access is not required." 1748 OBJECT teTunnelDestinationAddressType 1749 MIN-ACCESS read-only 1750 DESCRIPTION "Write access is not required." 1752 OBJECT teTunnelDestinationAddress 1753 MIN-ACCESS read-only 1754 DESCRIPTION "Write access is not required." 1756 OBJECT tePathName 1757 MIN-ACCESS read-only 1758 DESCRIPTION "Write access is not required." 1760 OBJECT tePathRowStatus 1761 SYNTAX RowStatus { active(1) } 1762 MIN-ACCESS read-only 1763 DESCRIPTION "Write access is not required." 1765 OBJECT tePathStorageType 1766 MIN-ACCESS read-only 1767 DESCRIPTION "Write access is not required." 1769 OBJECT tePathType 1770 MIN-ACCESS read-only 1771 DESCRIPTION "Write access is not required." 1773 OBJECT tePathConfiguredRoute 1774 MIN-ACCESS read-only 1775 DESCRIPTION "Write access is not required." 1777 OBJECT tePathBandwidth 1778 MIN-ACCESS read-only 1779 DESCRIPTION "Write access is not required." 1781 OBJECT tePathIncludeAny 1782 MIN-ACCESS read-only 1783 DESCRIPTION "Write access is not required." 1785 OBJECT tePathIncludeAll 1786 MIN-ACCESS read-only 1787 DESCRIPTION "Write access is not required." 1788 OBJECT tePathExclude 1789 MIN-ACCESS read-only 1790 DESCRIPTION "Write access is not required." 1792 OBJECT tePathSetupPriority 1793 MIN-ACCESS read-only 1794 DESCRIPTION "Write access is not required." 1796 OBJECT tePathHoldPriority 1797 MIN-ACCESS read-only 1798 DESCRIPTION "Write access is not required." 1800 OBJECT tePathProperties 1801 MIN-ACCESS read-only 1802 DESCRIPTION "Write access is not required." 1804 OBJECT tePathAdminStatus 1805 MIN-ACCESS read-only 1806 DESCRIPTION "Write access is not required." 1808 OBJECT tePathHopRowStatus 1809 SYNTAX RowStatus { active(1) } 1810 MIN-ACCESS read-only 1811 DESCRIPTION "Write access is not required." 1813 OBJECT tePathHopStorageType 1814 MIN-ACCESS read-only 1815 DESCRIPTION "Write access is not required." 1817 OBJECT tePathHopAddrType 1818 MIN-ACCESS read-only 1819 DESCRIPTION "Write access is not required." 1821 OBJECT tePathHopAddress 1822 MIN-ACCESS read-only 1823 DESCRIPTION "Write access is not required." 1825 ::= { teModuleCompliance 3 } 1827 teModuleServerFullCompliance MODULE-COMPLIANCE 1828 STATUS current 1829 DESCRIPTION "When this MIB module is implemented by a path 1830 computation server with support for read-create, 1831 then such an implementation can claim full 1832 compliance. 1833 " 1835 MODULE -- enclosing module, i.e., TE-MIB 1836 MANDATORY-GROUPS { 1837 teTrafficEngineeringGroup 1838 } 1840 GROUP teNotificationGroup 1841 DESCRIPTION "Implementation of this group is optional." 1843 OBJECT teAdminGroupRowStatus 1844 SYNTAX RowStatus { active(1) } 1845 WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) } 1846 DESCRIPTION "Support for notInService, createAndWait and 1847 notReady is not required. 1848 " 1850 OBJECT teTunnelRowStatus 1851 SYNTAX RowStatus { active(1), notInService(2) } 1852 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1853 createAndGo(4), destroy(6) 1854 } 1855 DESCRIPTION "Support for createAndWait and notReady is not 1856 required. 1857 " 1859 OBJECT teTunnelSourceAddressType 1860 DESCRIPTION "Write access is required. An implementation 1861 of a path computation server SHOULD support all 1862 types of tunnel source address types. 1863 " 1865 OBJECT tePathRowStatus 1866 SYNTAX RowStatus { active(1), notInService(2) } 1867 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1868 createAndGo(4), destroy(6) 1869 } 1870 DESCRIPTION "Support for createAndWait and notReady is not 1871 required. 1872 " 1874 OBJECT tePathHopRowStatus 1875 SYNTAX RowStatus { active(1), notInService(2) } 1876 WRITE-SYNTAX RowStatus { active(1), notInService(2), 1877 createAndGo(4), destroy(6) 1878 } 1879 DESCRIPTION "Support for createAndWait and notReady is not 1880 required. 1881 " 1883 ::= { teModuleCompliance 4 } 1885 END 1887 6. Normative References 1889 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1890 Levels", BCP 14, RFC 2119, March 1997. 1892 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1893 M. and S. Waldbusser, "Structure of Management Information 1894 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1896 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1897 M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, 1898 RFC 2579, April 1999. 1900 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1901 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 1902 58, RFC 2580, April 1999. 1904 [8] Nadeau, T., J. Cucchiara, C. Srinivasan, A. Viswanathan, and H. 1905 Sjostrand, "Definitions of Textual Conventions for Multiprotocol 1906 Label Switching (MPLS) Management", draft-ietf-mpls-tc- 1907 mib-09.txt 1909 [10] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for 1910 Describing SNMP Management Frameworks", RFC 3411, December 2002. 1912 7. Informative References 1914 [1] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. 1915 McManus, "Requirements for Traffic Engineering Over MPLS", RFC 1916 2702, September 1999. 1918 [2] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. 1919 Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 1920 3209, December 2001. 1922 [4] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction 1923 and Applicability Statements for Internet-Standard Management 1924 Framework", RFC 3410, December 2002. 1926 [9] Jamoussi, B. (Editor) et al, "Constraint-Based LSP Setup using 1927 LDP", RFC 3212, January 2002. 1929 [11] McCloghrie, M., and F. Kastenholz, "The Interfaces Group MIB", 1930 RFC 2863, June 2000 1932 [12] Thaler, D., "IP Tunnel MIB", RFC 2667, August 1999 1934 8. Security Considerations 1936 This MIB module relates to the configuration and management of 1937 Traffic Engineering tunnels. The unauthorized manipulation of fields 1938 in the following tables: teAdminGroupTable, teTunnelTable, 1939 tePathTable, and tePathHopTable may lead to tunnels flapping, tunnel 1940 paths being changed, or traffic being disrupted. In addition, if 1941 these tables are read by unauthorized parties, the information can be 1942 used to trace traffic patterns, traffic volumes, and tunnels paths; 1943 this may be considered proprietary and confidential information by 1944 some providers. 1946 There are a number of management objects defined in this MIB module 1947 with a MAX-ACCESS clause of read-write and/or read-create. Such 1948 objects may be considered sensitive or vulnerable in some network 1949 environments. The support for SET operations in a non-secure 1950 environment without proper protection can have a negative effect on 1951 network operations. These are the tables and objects and their 1952 sensitivity/vulnerability: 1954 teAdminGroupTable: changing this will affect the semantics of include 1955 and exclude constraints, and hence traffic taking unintended routes; 1957 teTunnelTable: changing this affects many properties of traffic 1958 tunnels; 1960 tePathTable: changing this affects the constraints (including 1961 bandwidth) of tunnel paths, as well as the status of the path; 1963 tePathHopTable: changing this affects the route followed by a traffic 1964 tunnel path. 1966 Some of the readable objects in this MIB module (i.e., objects with a 1967 MAX-ACCESS other than not-accessible) may be considered sensitive or 1968 vulnerable in some network environments. It is thus important to 1969 control even GET and/or NOTIFY access to these objects and possibly 1970 to even encrypt the values of these objects when sending them over 1971 the network via SNMP. These are the tables and objects and their 1972 sensitivity/vulnerability: 1974 teTunnelTable: describes tunnel endpoints and traffic volumes; 1975 tePathTable: describes path properties; 1976 tePathHopTable: describes path routes. 1978 SNMP versions prior to SNMPv3 did not include adequate security. 1979 Even if the network itself is secure (for example by using IPSec), 1980 even then, there is no control as to who on the secure network is 1981 allowed to access and GET/SET (read/change/create/delete) the objects 1982 in this MIB module. 1984 It is RECOMMENDED that implementers consider the security features as 1985 provided by the SNMPv3 framework (see [4], section 8), including full 1986 support for the SNMPv3 cryptographic mechanisms (for authentication 1987 and privacy). 1989 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1990 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1991 enable cryptographic security. It is then a customer/operator 1992 responsibility to ensure that the SNMP entity giving access to an 1993 instance of this MIB module is properly configured to give access to 1994 the objects only to those principals (users) that have legitimate 1995 rights to indeed GET or SET (change/create/delete) them. 1997 Acknowledgments 1999 It was Tony Li's suggestion that the author embark on this MIB. Many 2000 thanks to him and to Der-Hwa Gan for their input and help. 2002 Many thanks too to Bert Wijnen for his incredible help both with 2003 improving the correctness, structure and readability of the MIB 2004 module, as well as with the text of the RFC. Thanks also to Adrian 2005 Farrel for his detailed review. 2007 Author's Information 2009 Kireeti Kompella 2010 Juniper Networks, Inc. 2011 1194 N. Mathilda Ave 2012 Sunnyvale, CA 94089 2013 Email: kireeti@juniper.net 2015 Intellectual Property Rights Notices 2017 The IETF takes no position regarding the validity or scope of any 2018 intellectual property or other rights that might be claimed to 2019 pertain to the implementation or use of the technology described in 2020 this document or the extent to which any license under such rights 2021 might or might not be available; neither does it represent that it 2022 has made any effort to identify any such rights. Information on the 2023 IETF's procedures with respect to rights in standards-track and 2024 standards-related documentation can be found in BCP-11. Copies of 2025 claims of rights made available for publication and any assurances of 2026 licenses to be made available, or the result of an attempt made to 2027 obtain a general license or permission for the use of such 2028 proprietary rights by implementors or users of this specification can 2029 be obtained from the IETF Secretariat. 2031 The IETF invites any interested party to bring to its attention any 2032 copyrights, patents or patent applications, or other proprietary 2033 rights which may cover technology that may be required to practice 2034 this standard. Please address the information to the IETF Executive 2035 Director. 2037 Full Copyright Statement 2039 Copyright (C) The Internet Society (2004). All Rights Reserved. 2041 This document and translations of it may be copied and furnished to 2042 others, and derivative works that comment on or otherwise explain it 2043 or assist in its implmentation may be prepared, copied, published and 2044 distributed, in whole or in part, without restriction of any kind, 2045 provided that the above copyright notice and this paragraph are 2046 included on all such copies and derivative works. However, this 2047 document itself may not be modified in any way, such as by removing 2048 the copyright notice or references to the Internet Society or other 2049 Internet organizations, except as needed for the purpose of 2050 developing Internet standards in which case the procedures for 2051 copyrights defined in the Internet Standards process must be 2052 followed, or as required to translate it into languages other than 2053 English. 2055 The limited permissions granted above are perpetual and will not be 2056 revoked by the Internet Society or its successors or assigns. 2058 This document and the information contained herein is provided on an 2059 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2060 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2061 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2062 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2063 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.