idnits 2.17.1 draft-ietf-iptel-trip-mib-07.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 Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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? == No 'Intended status' indicated for this document; assuming Proposed Standard 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.) == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 19: '... other groups MAY also distribute wo...' RFC 2119 keyword, line 23: '... months and MAY be updated, replaced...' RFC 2119 keyword, line 406: '...x. The objects in this table SHOULD be...' RFC 2119 keyword, line 510: '... is down(2) then tripOperStatus SHOULD...' RFC 2119 keyword, line 512: '... tripOperStatus SHOULD change to up(1...' (33 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: tripPeerMaxRetryInterval OBJECT-TYPE SYNTAX Integer32 (0..2147483647) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the maximum amount of time that will elapse between connection retries. Once the value of tripPeerConnectRetryInterval has reached this value, no more retries will be attempted. Attempts to set this value lower than the retry interval SHOULD not be allowed." DEFVAL { 360 } ::= { tripPeerEntry 11 } -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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: 'BCP0014' is mentioned on line 102, but not defined == Missing Reference: 'RFC2788' is mentioned on line 114, but not defined == Unused Reference: 'RFC3291' is defined on line 2250, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) ** Obsolete normative reference: RFC 1657 (Obsoleted by RFC 4273) -- Obsolete informational reference (is this intentional?): RFC 1771 (Obsoleted by RFC 4271) Summary: 7 errors (**), 0 flaws (~~), 7 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft D. Zinman 3 Document: draft-ietf-iptel-trip-mib-07.txt Soma Networks 4 Expires: January 2004 D. Walker 5 J. Jiang 6 SS8 Networks 8 Management Information Base 9 for Telephony Routing over IP (TRIP) 10 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC 2026 [RFC2026]. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups MAY also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and MAY be updated, replaced, or obsoleted by other documents 24 at any time. It is inappropriate to use Internet-Drafts as 25 reference material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Copyright Notice 35 Copyright (C) The Internet Society (2003). All Rights Reserved. 37 Abstract 39 This memo defines a portion of the MIB (Management Information Base) 40 module for use with network management protocols in the Internet 41 community. In particular, it describes a set of managed objects that 42 are used to manage for TRIP (Telephony Routing over IP) devices. 44 Zinman/Walker/Jiang 1 45 Table of Contents 47 Status of this Memo................................................1 48 Copyright Notice...................................................1 49 Abstract...........................................................1 50 1. The Internet-Standard Management Framework....................3 51 2. Introduction..................................................3 52 3. Conventions used in this document.............................3 53 4. Overview......................................................3 54 5. Structure of TRIP MIB.........................................3 55 5.1 Textual Conventions.........................................4 56 6. Definitions...................................................4 57 6.1 TRIP Textual Conventions....................................4 58 6.2 TRIP MIB....................................................7 59 7. Security Considerations......................................41 60 8. Full Copyright Statement.....................................42 61 9. Normative References.........................................43 62 10. Informative References.......................................44 63 11. Intellectual Property Notice.................................44 64 12. Acknowledgments..............................................44 65 13. Author's Addresses...........................................45 66 14. Working Group................................................45 68 Zinman/Walker/Jiang 2 69 1. The Internet-Standard Management Framework 71 For a detailed overview of the documents that describe the current 72 Internet-Standard Management Framework, please refer to section 7 of 73 RFC 3410 [RFC3410]. 75 Managed objects are accessed via a virtual information store, termed 76 the Management Information Base or MIB. MIB module objects are 77 generally accessed through the Simple Network Management Protocol 78 (SNMP). Objects in this MIB module are defined using the mechanisms 79 defined in the Structure of Management Information (SMI). This memo 80 specifies a MIB module that is compliant to the SMIv2, which is 81 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] 82 and STD 58, RFC 2580 [RFC2580]. 84 2. Introduction 86 This memo defines a portion of the Management Information Base (MIB) 87 for use with network management protocols in the Internet community. 88 In particular, it describes a set of managed objects that are used 89 to schedule management operations periodically or at specified dates 90 and times. Since TRIP [RFC3219] is modeled after the Border Gateway 91 Protocol (BGP-4) [RFC1771], the managed objects for TRIP are also 92 modeled after RFC1657 - Definitions of Managed Objects for the 93 Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 94 [RFC1657]. 96 3. Conventions used in this document 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 100 this document are to be interpreted as described in BCP-0014 101 [BCP0014]. 103 4. Overview 105 This MIB module provides managed objects for TRIP devices defined in 106 Telephony Routing over IP [RFC3219]. TRIP is an inter-domain 107 application-layer control protocol that exchanges information 108 between TRIP location servers (LS) to provide efficient IP telephony 109 routing. 111 5. Structure of TRIP MIB 113 This MIB module utilizes the framework described in RFC 2788 114 [RFC2788] for management of multiple instances of TRIP from a single 115 entity. The Network Services Monitoring MIB module applTable will 116 be populated with entries corresponding to each TRIP Location Server 117 in the system. Each TRIP Location Server will then have an 118 applIndex associated with it. The value assigned to applIndex will 119 represent the distinct instance of TRIP. 121 Zinman/Walker/Jiang 3 122 The TRIP MIB module contains the following groups of objects: 123 o The tripConfigGroup contains the common configuration objects 124 applicable to all TRIP applications referenced by the applIndex. 125 o The tripPeerTableConfigGroup contains the configuration objects 126 applicable to all TRIP peers of the Location Server referened by 127 the applIndex. 128 o The tripRouteGroup contains the configuration objects related to 129 the routes of all TRIBs of this Location Server. 130 o The tripItadTopologyGroup contains information about the topology 131 of the TRIP ITADs concerning this Location Server. 132 o The tripPeerTableStatsGroup contains the statistical objects 133 applicable to all TRIP peers of the Location Server referened by 134 the applIndex. 135 o The tripNotificationGroup contains notifications that the TRIP 136 application can generate. 137 o The tripNotifObjectGroup contains the objects needed by one or 138 more of the notifications. 140 5.1 Textual Conventions 142 The data types TripItad and TripId are used as textual conventions 143 in this document. A TRIP ITAD (IP Telephony Administrative Domain) 144 is described in [RFC3219]. A TRIP ID is used as a distinct 145 identifier for a TRIP Location Server. A TripAppProtocol is used to 146 identify an application protocol. A TripAddressFamily is used to 147 define an address family. TripCommunityId is used as a distinct 148 identifier for a TRIP community. TripProtocolVersion depicts the 149 version number of the TRIP protocol. TripSendReceiveMode describes 150 the operational mode of the TRIP application. 152 6. Definitions 154 6.1 TRIP Textual Conventions 156 TRIP-TC DEFINITIONS ::= BEGIN 158 IMPORTS 159 MODULE-IDENTITY, 160 Unsigned32, 161 Integer32, 162 mib-2 163 FROM SNMPv2-SMI 165 TEXTUAL-CONVENTION 166 FROM SNMPv2-TC; 168 tripTC MODULE-IDENTITY 169 LAST-UPDATED "200307090000Z" -- July 09, 2003 170 ORGANIZATION "IETF IPTel Working Group. 171 Mailing list: iptel@lists.bell-labs.com" 172 CONTACT-INFO 174 Zinman/Walker/Jiang 4 175 "Co-editor David Zinman 176 Soma Networks 177 postal: 312 Adelaide St. West Suite 700 178 Toronto ON, M5V 1R2 179 Canada 180 email: dzinman@somanetworks.com 181 phone: +1 416 348 1656 183 Co-editor Dave Walker 184 SS8 Networks, Inc. 185 postal: 495 March Road, Suite #500 186 Ottawa, ON, K2K 3G1 187 Canada 188 email: drwalker@ss8.com 189 phone: +1 613 592 2100 191 Co-editor Jianping Jiang 192 SS8 Networks, Inc. 193 postal: 495 March Road, Suite #500 194 Ottawa, ON, K2K 3G1 195 Canada 196 email: jianping@ss8.com 197 phone: +1 613 592 2100 198 " 199 DESCRIPTION 200 "Initial version of TRIP (Telephony Routing Over IP) 201 MIB Textual Conventions module used by other 202 TRIP-related MIB Modules. 204 Copyright (C) The Internet Society (2002). This version of 205 this MIB module is part of RFC xxxx, see the RFC itself 206 for full legal notices." 208 ::= { mib-2 xxxx } -- to be assigned by IANA 210 -- 211 -- Textual Conventions 212 -- 213 TripItad ::= TEXTUAL-CONVENTION 214 STATUS current 215 DESCRIPTION 216 "The values for identifying the IP Telephony 217 Administrative Domain (ITAD)." 218 SYNTAX Unsigned32 (0..4294967295) 220 TripId ::= TEXTUAL-CONVENTION 221 STATUS current 222 DESCRIPTION 223 "The TRIP Identifier uniquely identifies a LS within its 224 ITAD. It is a 4 octet unsigned integer that may, but not 225 necessarily, represent the IPv4 address of a Location 226 Server. Where bytes 1-4 of the Unsigned32 represent 228 Zinman/Walker/Jiang 5 229 1-4 bytes of the IPv4 address in network-byte order. For 230 an IPv6 network, TripId will not represent the IPv6 231 address." 232 SYNTAX Unsigned32 (0..4294967295) 234 TripAddressFamily ::= TEXTUAL-CONVENTION 235 STATUS current 236 DESCRIPTION 237 "A type of address for a TRIP route. Address families 238 defined within this MIB module are: 240 Code Address Family 241 1 Decimal Routing Numbers 242 2 PentaDecimal Routing Numbers 243 3 E.164 Numbers" 245 SYNTAX INTEGER { decimal(1), pentadecimal(2), e164(3) } 247 TripAppProtocol ::= TEXTUAL-CONVENTION 248 STATUS current 249 DESCRIPTION 250 "The application protocol used for communication with TRIP 251 Location Servers. Protocols defined in this MIB Module 252 are: 254 Code Protocol 255 1 SIP 256 2 H.323-H.225.0-Q.931 257 3 H.323-H.225.0-RAS 258 4 H.323-H.225.0-Annex-G" 260 SYNTAX INTEGER { sip(1), q931(2), ras(3), annexG(4) } 262 TripCommunityId ::= TEXTUAL-CONVENTION 263 STATUS current 264 DESCRIPTION 265 "The range of legal values for a TRIP Community 266 Identifier." 267 SYNTAX Unsigned32 (0..4294967295) 269 TripProtocolVersion ::= TEXTUAL-CONVENTION 270 STATUS current 271 DESCRIPTION 272 "The version number of the TRIP protocol." 273 SYNTAX Integer32 (1..255) 275 TripSendReceiveMode ::= TEXTUAL-CONVENTION 276 STATUS current 277 DESCRIPTION 278 "The operational mode of the TRIP application. Possible 279 values are: 280 1 - Send Receive mode 282 Zinman/Walker/Jiang 6 283 2 - Send only mode 284 3 - Receive Only mode" 285 SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) } 287 END 289 6.2 TRIP MIB 291 TRIP-MIB DEFINITIONS ::= BEGIN 293 IMPORTS 294 MODULE-IDENTITY, 295 OBJECT-TYPE, 296 NOTIFICATION-TYPE, 297 Unsigned32, 298 Integer32, 299 Counter32, 300 mib-2 301 FROM SNMPv2-SMI 303 DateAndTime, 304 TimeInterval, 305 TruthValue, 306 TimeStamp, 307 StorageType, 308 RowStatus 309 FROM SNMPv2-TC 311 OBJECT-GROUP, 312 MODULE-COMPLIANCE, 313 NOTIFICATION-GROUP 314 FROM SNMPv2-CONF 316 InetAddressType, 317 InetAddress, 318 InetPortNumber 319 FROM INET-ADDRESS-MIB 321 applIndex 322 FROM NETWORK-SERVICES-MIB 324 TripItad, 325 TripId, 326 TripAppProtocol, 327 TripAddressFamily, 328 TripCommunityId, 329 TripProtocolVersion, 330 TripSendReceiveMode 331 FROM TRIP-TC; 333 tripMIB MODULE-IDENTITY 334 LAST-UPDATED "200307090000Z" -- July 09, 2003 336 Zinman/Walker/Jiang 7 337 ORGANIZATION "IETF IPTel Working Group. 338 Mailing list: iptel@lists.bell-labs.com" 340 CONTACT-INFO 341 "Co-editor David Zinman 342 Soma Networks 343 postal: 312 Adelaide St. West Suite 700 344 Toronto ON, M5V 1R2 345 Canada 346 email: dzinman@somanetworks.com 347 phone: +1 416 348 1656 349 Co-editor Dave Walker 350 SS8 Networks, Inc. 351 postal: 495 March Road, Suite #500 352 Ottawa, ON, K2K 3G1 353 Canada 354 email: drwalker@ss8.com 355 phone: +1 613 592 2100 357 Co-editor Jianping Jiang 358 SS8 Networks, Inc. 359 postal: 495 March Road, Suite #500 360 Ottawa, ON, K2K 3G1 361 Canada 362 email: jianping@ss8.com 363 phone: +1 613 592 2100 364 " 365 DESCRIPTION 366 "The MIB module describing Telephony Routing over IP 367 (TRIP). TRIP is a policy driven inter-administrative 368 domain protocol for advertising the reachability of 369 telephony destinations between location servers (LS), and 370 for advertising attributes of the routes to those 371 destinations. 373 Copyright (C) The Internet Society (2002). This version of 374 this MIB module is part of RFC xxxx, see the RFC itself 375 for full legal notices." 376 REVISION "200307090000Z" -- July 09, 2003 377 DESCRIPTION 378 "The initial version, Published as RFC xxxx." 379 ::= { mib-2 xxxx } -- to be assigned by IANA 381 tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 } 382 tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 } 383 tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 } 384 tripMIBNotifObjects OBJECT IDENTIFIER ::= { tripMIB 3 } 386 tripMIBCompliance OBJECT IDENTIFIER ::= 387 { tripMIBConformance 1 } 388 tripMIBGroups OBJECT IDENTIFIER ::= 390 Zinman/Walker/Jiang 8 391 { tripMIBConformance 2 } 393 -- 394 -- tripCfgTable 395 -- 396 tripCfgTable OBJECT-TYPE 397 SYNTAX SEQUENCE OF TripCfgEntry 398 MAX-ACCESS not-accessible 399 STATUS current 400 DESCRIPTION 401 "This table contains the common configuration objects 402 applicable to all TRIP applications referenced by the 403 applIndex. Each row represents those objects for a 404 particular TRIP LS present in this system. The 405 instances of TRIP LS's are uniquely identified by the 406 applIndex. The objects in this table SHOULD be 407 nonVolatile and survive a reboot." 408 ::= { tripMIBObjects 1 } 410 tripCfgEntry OBJECT-TYPE 411 SYNTAX TripCfgEntry 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "A row of common configuration." 416 INDEX { applIndex } 417 ::= { tripCfgTable 1 } 419 TripCfgEntry ::= 420 SEQUENCE { 421 tripCfgProtocolVersion TripProtocolVersion, 422 tripCfgItad TripItad, 423 tripCfgIdentifier TripId, 424 tripCfgOperStatus INTEGER, 425 tripCfgAdminStatus INTEGER, 426 tripCfgAddrIAddrType InetAddressType, 427 tripCfgAddr InetAddress, 428 tripCfgPort InetPortNumber, 429 tripCfgMinItadOriginationInterval Integer32, 430 tripCfgMinRouteAdvertisementInterval Integer32, 431 tripCfgMaxPurgeTime Integer32, 432 tripCfgDisableTime Integer32, 433 tripCfgSendReceiveMode TripSendReceiveMode, 434 tripCfgStorage StorageType 435 } 437 tripCfgProtocolVersion OBJECT-TYPE 438 SYNTAX TripProtocolVersion 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "This object will reflect the version of TRIP 444 Zinman/Walker/Jiang 9 445 supported by this system. It follows the same 446 format as TRIP version information contained 447 in the TRIP messages generated by this TRIP entity." 448 REFERENCE 449 "RFC 3291, section 4.2." 450 ::= { tripCfgEntry 1 } 452 tripCfgItad OBJECT-TYPE 453 SYNTAX TripItad 454 MAX-ACCESS read-write 455 STATUS current 456 DESCRIPTION 457 "The Internet Telephony Administrative domain (ITAD) 458 of this LS." 459 ::= { tripCfgEntry 2 } 461 tripCfgIdentifier OBJECT-TYPE 462 SYNTAX TripId 463 MAX-ACCESS read-only 464 STATUS current 465 DESCRIPTION 466 "The object that identifies this TRIP Client." 467 ::= { tripCfgEntry 3 } 469 tripCfgAdminStatus OBJECT-TYPE 470 SYNTAX INTEGER { 471 up(1), 472 down(2) 473 } 474 MAX-ACCESS read-write 475 STATUS current 476 DESCRIPTION 477 "The desired TRIP state. 479 up(1) : Set the application to normal operation. 481 down(2): Set the application to a state where it will 482 not process TRIP messages." 483 ::= { tripCfgEntry 4 } 485 tripCfgOperStatus OBJECT-TYPE 486 SYNTAX INTEGER { 487 up(1), 488 down(2), 489 faulty(3) 490 } 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The current operational state of the TRIP protocol. 496 up(1): The application is operating normally, and 498 Zinman/Walker/Jiang 10 499 is processing (receiving and possibly 500 issuing) TRIP requests and responses. 502 down(2): The application is currently not processing 503 TRIP messages. This occurs if the TRIP 504 application is in an initialization state or 505 if tripCfgAdminStatus is set to down(2). 507 faulty(3): The application is not operating normally due 508 to a fault in the system. 510 If tripCfgAdminStatus is down(2) then tripOperStatus SHOULD 511 be down(2). If tripAdminStatus is changed to up(1) then 512 tripOperStatus SHOULD change to up(1) if there is no 513 fault that prevents the TRIP protocol from moving to the 514 up(1) state." 515 ::= { tripCfgEntry 5 } 517 tripCfgAddrIAddrType OBJECT-TYPE 518 SYNTAX InetAddressType 519 MAX-ACCESS read-only 520 STATUS current 521 DESCRIPTION 522 "The type of Inet Address of the tripAddr." 523 REFERENCE 524 "RFC 3291, section 3." 525 ::= { tripCfgEntry 6 } 527 tripCfgAddr OBJECT-TYPE 528 SYNTAX InetAddress 529 MAX-ACCESS read-only 530 STATUS current 531 DESCRIPTION 532 "The network address of the local LS that the peer c 533 onnects to. The type of address depends on the object 534 tripCfgAddrIAddrType." 535 REFERENCE 536 "RFC 3291, section 3." 537 ::= { tripCfgEntry 7 } 539 tripCfgPort OBJECT-TYPE 540 SYNTAX InetPortNumber 541 MAX-ACCESS read-write 542 STATUS current 543 DESCRIPTION 544 "The local tcp/udp port on the local LS that the peer 545 connects to." 546 ::= { tripCfgEntry 8 } 548 tripCfgMinItadOriginationInterval OBJECT-TYPE 549 SYNTAX Integer32 (1..2147483647) 550 UNITS "Seconds" 552 Zinman/Walker/Jiang 11 553 MAX-ACCESS read-write 554 STATUS current 555 DESCRIPTION 556 "The minimum amount of time that MUST elapse between 557 advertisement of the update message that reports changes 558 within the LS's own ITAD." 559 DEFVAL { 30 } 560 ::= { tripCfgEntry 9 } 562 tripCfgMinRouteAdvertisementInterval OBJECT-TYPE 563 SYNTAX Integer32 (1..2147483647) 564 UNITS "Seconds" 565 MAX-ACCESS read-write 566 STATUS current 567 DESCRIPTION 568 "Specifies minimal interval between successive 569 advertisements to a particular destination from an LS." 570 DEFVAL { 30 } 571 ::= { tripCfgEntry 10 } 573 tripCfgMaxPurgeTime OBJECT-TYPE 574 SYNTAX Integer32 (1..2147483647) 575 UNITS "Seconds" 576 MAX-ACCESS read-write 577 STATUS current 578 DESCRIPTION 579 "Indicates the interval that the LS MUST maintain routes 580 marked as withdrawn in its database." 581 DEFVAL { 10 } 582 ::= { tripCfgEntry 11 } 584 tripCfgDisableTime OBJECT-TYPE 585 SYNTAX Integer32 (1..2147483647) 586 UNITS "Seconds" 587 MAX-ACCESS read-write 588 STATUS current 589 DESCRIPTION 590 "Indicates the interval that the TRIP module of the 591 LS MUST be disabled while routes originated by this 592 LS with high sequence numbers can be removed." 593 DEFVAL { 180 } 594 ::= { tripCfgEntry 12 } 596 tripCfgSendReceiveMode OBJECT-TYPE 597 SYNTAX TripSendReceiveMode 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "The operational mode of the TRIP entity running on this 602 system." 603 ::= { tripCfgEntry 13 } 605 Zinman/Walker/Jiang 12 606 tripCfgStorage OBJECT-TYPE 607 SYNTAX StorageType 608 MAX-ACCESS read-write 609 STATUS current 610 DESCRIPTION 611 "The storage type for this conceptual row." 612 DEFVAL { nonVolatile } 613 ::= { tripCfgEntry 14 } 615 -- 616 -- TripRouteTypeTable 617 -- 619 tripRouteTypeTable OBJECT-TYPE 620 SYNTAX SEQUENCE OF TripRouteTypeEntry 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION 624 "The TRIP peer Route Type table contains one entry per 625 supported protocol - address family pair. The objects in 626 this table are volatile and are refreshed after a reboot." 627 ::= { tripMIBObjects 2 } 629 tripRouteTypeEntry OBJECT-TYPE 630 SYNTAX TripRouteTypeEntry 631 MAX-ACCESS not-accessible 632 STATUS current 633 DESCRIPTION 634 "An entry containing information about the route type 635 that a particular TRIP entity supports. Each entry 636 represents information about either the local or a remote 637 LS peer. The object tripRouteTypePeer is used to 638 distinguish this. In the case of a local LS, the 639 address/port information will reflect the values 640 configured in tripCfgTable. In the case of a remote 641 peer, the address/port information will reflect the 642 values of an entry in the tripPeerTable." 643 INDEX { applIndex, 644 tripRouteTypeAddrInetType, 645 tripRouteTypeAddr, 646 tripRouteTypePort, 647 tripRouteTypeProtocolId, 648 tripRouteTypeAddrFamilyId } 649 ::= { tripRouteTypeTable 1 } 651 TripRouteTypeEntry ::= SEQUENCE { 652 tripRouteTypeAddrInetType InetAddressType, 653 tripRouteTypeAddr InetAddress, 654 tripRouteTypePort InetPortNumber, 655 tripRouteTypeProtocolId TripAppProtocol, 656 tripRouteTypeAddrFamilyId TripAddressFamily, 657 tripRouteTypePeer INTEGER 659 Zinman/Walker/Jiang 13 660 } 662 tripRouteTypeAddrInetType OBJECT-TYPE 663 SYNTAX InetAddressType 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "The type of Inet Address of the tripRouteTypeAddr." 668 REFERENCE 669 "RFC 3291, section 3." 670 ::= { tripRouteTypeEntry 1 } 672 tripRouteTypeAddr OBJECT-TYPE 673 SYNTAX InetAddress (SIZE(0..117)) 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "The network address of this entry's TRIP peer LS. The 678 SIZE value of 117 has been assigned due to the sub 679 identifier of object types length limitation as 680 defined in SMIv2." 681 REFERENCE 682 "RFC 3291, section 3." 683 ::= { tripRouteTypeEntry 2 } 685 tripRouteTypePort OBJECT-TYPE 686 SYNTAX InetPortNumber 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "The port for the TCP connection between this and 691 an associated TRIP peer." 692 ::= { tripRouteTypeEntry 3 } 694 tripRouteTypeProtocolId OBJECT-TYPE 695 SYNTAX TripAppProtocol 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "The object identifier of a protocol that the associated 700 peer is using." 701 ::= { tripRouteTypeEntry 4 } 703 tripRouteTypeAddrFamilyId OBJECT-TYPE 704 SYNTAX TripAddressFamily 705 MAX-ACCESS not-accessible 706 STATUS current 707 DESCRIPTION 708 "The object identifier of an address family that the 709 associated peer belongs to." 710 ::= { tripRouteTypeEntry 5 } 712 Zinman/Walker/Jiang 14 713 tripRouteTypePeer OBJECT-TYPE 714 SYNTAX INTEGER { local(1), remote(2) } 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "This object identifies whether this entry is 719 associated with a 'local' or 'remote' LS peer." 720 ::= { tripRouteTypeEntry 6 } 722 -- 723 -- tripSupportedCommunityTable 724 -- 726 tripSupportedCommunityTable OBJECT-TYPE 727 SYNTAX SEQUENCE OF TripSupportedCommunityEntry 728 MAX-ACCESS not-accessible 729 STATUS current 730 DESCRIPTION 731 "The list of TRIP communities that this LS supports. A 732 TRIP community is a group of destinations that share 733 common properties. 735 The TRIP Supported Communities entry is used to group 736 destinations so that the routing decision can be based 737 on the identity of the group." 738 REFERENCE 739 "RFC 3219, section 5.9" 740 ::= { tripMIBObjects 3 } 742 tripSupportedCommunityEntry OBJECT-TYPE 743 SYNTAX TripSupportedCommunityEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "Entry containing information about a community. A TRIP 748 community is a group of destinations that share some 749 common property. This attribute is used so that routing 750 decisions can be based on the identity of the group." 751 INDEX { applIndex, tripSupportedCommunityId } 752 ::= { tripSupportedCommunityTable 1 } 754 TripSupportedCommunityEntry ::= SEQUENCE { 755 tripSupportedCommunityId TripCommunityId, 756 tripSupportedCommunityItad TripItad, 757 tripSupportedCommunityStorage StorageType, 758 tripSupportedCommunityRowStatus RowStatus 759 } 761 tripSupportedCommunityId OBJECT-TYPE 762 SYNTAX TripCommunityId 763 MAX-ACCESS not-accessible 764 STATUS current 766 Zinman/Walker/Jiang 15 767 DESCRIPTION 768 "The identifier of the supported Community." 769 ::= { tripSupportedCommunityEntry 1 } 771 tripSupportedCommunityItad OBJECT-TYPE 772 SYNTAX TripItad 773 MAX-ACCESS read-create 774 STATUS current 775 DESCRIPTION 776 "The ITAD of the community." 777 ::= { tripSupportedCommunityEntry 2 } 779 tripSupportedCommunityStorage OBJECT-TYPE 780 SYNTAX StorageType 781 MAX-ACCESS read-create 782 STATUS current 783 DESCRIPTION 784 "The storage type for this conceptual row. Conceptual 785 rows having the value 'permanent' need not allow write- 786 access to any columnar objects in the row. It is not a 787 requirement that this storage be non volatile." 788 DEFVAL { nonVolatile } 789 ::= { tripSupportedCommunityEntry 3 } 791 tripSupportedCommunityRowStatus OBJECT-TYPE 792 SYNTAX RowStatus 793 MAX-ACCESS read-create 794 STATUS current 795 DESCRIPTION 796 "The row status of the entry. This object is REQUIRED 797 to create or delete rows by a manager. A value for 798 tripSupportedCommunityItad MUST be set for row creation 799 to be successful. If the instance already exists for a 800 particular applIndex, the row create operation will 801 fail. 803 The value of this object has no effect on whether 804 other objects in this conceptual row can be modified." 805 ::= { tripSupportedCommunityEntry 4 } 807 -- 808 -- TripPeerTable 809 -- 810 tripPeerTable OBJECT-TYPE 811 SYNTAX SEQUENCE OF TripPeerEntry 812 MAX-ACCESS not-accessible 813 STATUS current 814 DESCRIPTION 815 "The TRIP peer table. This table contains one entry per 816 TRIP peer, and information about the connection with 817 the peer." 818 ::= { tripMIBObjects 4 } 820 Zinman/Walker/Jiang 16 821 tripPeerEntry OBJECT-TYPE 822 SYNTAX TripPeerEntry 823 MAX-ACCESS not-accessible 824 STATUS current 825 DESCRIPTION 826 "Entry containing information about the connection with 827 a TRIP peer." 828 INDEX { applIndex, 829 tripPeerRemoteAddrInetType, 830 tripPeerRemoteAddr, 831 tripPeerRemotePort } 832 ::= {tripPeerTable 1} 834 TripPeerEntry ::= SEQUENCE { 835 tripPeerRemoteAddrInetType InetAddressType, 836 tripPeerRemoteAddr InetAddress, 837 tripPeerRemotePort InetPortNumber, 838 tripPeerIdentifier TripId, 839 tripPeerState INTEGER, 840 tripPeerAdminStatus INTEGER, 841 tripPeerNegotiatedVersion TripProtocolVersion, 842 tripPeerSendReceiveMode TripSendReceiveMode, 843 tripPeerRemoteItad TripItad, 844 tripPeerConnectRetryInterval Integer32, 845 tripPeerMaxRetryInterval Integer32, 846 tripPeerHoldTime Integer32, 847 tripPeerKeepAlive Integer32, 848 tripPeerHoldTimeConfigured Integer32, 849 tripPeerKeepAliveConfigured Integer32, 850 tripPeerMaxPurgeTime Integer32, 851 tripPeerDisableTime Integer32, 852 tripPeerLearned TruthValue, 853 tripPeerStorage StorageType, 854 tripPeerRowStatus RowStatus 855 } 857 tripPeerRemoteAddrInetType OBJECT-TYPE 858 SYNTAX InetAddressType 859 MAX-ACCESS not-accessible 860 STATUS current 861 DESCRIPTION 862 "The type of Inet Address of the tripPeerRemoteAddr." 863 REFERENCE 864 "RFC 3291, section 3." 865 ::= { tripPeerEntry 1 } 867 tripPeerRemoteAddr OBJECT-TYPE 868 SYNTAX InetAddress (SIZE(0..119)) 869 MAX-ACCESS not-accessible 870 STATUS current 871 DESCRIPTION 873 Zinman/Walker/Jiang 17 874 "The IP address of this entry's TRIP peer LS. The SIZE 875 value of 119 has been assigned due to the sub identifier 876 of object types length limitation as defined in SMIv2." 877 REFERENCE 878 "RFC 3291, section 3." 879 ::= { tripPeerEntry 2 } 881 tripPeerRemotePort OBJECT-TYPE 882 SYNTAX InetPortNumber 883 MAX-ACCESS not-accessible 884 STATUS current 885 DESCRIPTION 886 "The remote port for the TCP connection between the 887 TRIP peers." 888 ::= { tripPeerEntry 3 } 890 tripPeerIdentifier OBJECT-TYPE 891 SYNTAX TripId 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "TRIP identifier of the peer." 896 ::= { tripPeerEntry 4 } 898 tripPeerState OBJECT-TYPE 899 SYNTAX INTEGER { 900 idle(1), 901 connect(2), 902 active(3), 903 openSent(4), 904 openConfirm(5), 905 established(6) 906 } 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "TRIP Peer Finite State Machine state. 912 idle(1) : The initial state. Local LS refuses all 913 incoming connections. No application 914 resources are allocated to processing 915 information about the remote peer. 917 connect(2) : Local LS waiting for a transport 918 protocol connection to be completed to 919 the peer, and is listening for inbound 920 transport connections from the peer. 922 active(3) : Local LS is listening for an inbound 923 connection from the peer, but is not in 924 the process of initiating a connection 925 to the remote peer. 927 Zinman/Walker/Jiang 18 928 openSent(4) : Local LS has sent an OPEN message to its 929 peer and is waiting for an OPEN message 930 from the remote peer. 932 openConfirm(5): Local LS has sent an OPEN message to the 933 remote peer, received an OPEN message from 934 the remote peer, and sent a KEEPALIVE 935 message in response to the OPEN. The local 936 LS is now waiting for a KEEPALIVE message 937 or a NOTIFICATION message in response to 938 its OPEN message. 940 established(6): LS can exchange UPDATE, NOTIFICATION, and 941 KEEPALIVE messages with its peer." 942 ::= { tripPeerEntry 5 } 944 tripPeerAdminStatus OBJECT-TYPE 945 SYNTAX INTEGER { 946 up(1), 947 down(2) 948 } 949 MAX-ACCESS read-create 950 STATUS current 951 DESCRIPTION 952 "This object is used to affect the TRIP connection 953 state. 955 up(1) : Allow a connection with the peer LS. 957 down(2) : disconnect the connection from the peer LS and 958 do not allow any further connections to this 959 peer. 961 If this value is set to down(2) then tripPeerState will 962 have the value of idle(1)." 963 DEFVAL { up } 964 ::= { tripPeerEntry 6 } 966 tripPeerNegotiatedVersion OBJECT-TYPE 967 SYNTAX TripProtocolVersion 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The negotiated version of TRIP running between this 972 local entity and this peer." 973 ::= { tripPeerEntry 7 } 975 tripPeerSendReceiveMode OBJECT-TYPE 976 SYNTAX TripSendReceiveMode 977 MAX-ACCESS read-only 978 STATUS current 980 Zinman/Walker/Jiang 19 981 DESCRIPTION 982 "The operational mode of this peer." 983 ::= { tripPeerEntry 8 } 985 tripPeerRemoteItad OBJECT-TYPE 986 SYNTAX TripItad 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "The Internet Telephony Administrative domain of 991 this peer." 992 ::= { tripPeerEntry 9 } 994 tripPeerConnectRetryInterval OBJECT-TYPE 995 SYNTAX Integer32 (0..2147483647) 996 UNITS "Seconds" 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "Specifies the initial amount of time that will elapse 1001 between connection retry. This value SHOULD double 1002 after each attempt up to the value of 1003 tripPeerMaxRetryInterval. This value MUST always be less 1004 than or equal to the value of tripPeerMaxRetryInterval. 1005 Attempts to set this value higher than the max retry 1006 will not be allowed." 1007 DEFVAL { 120 } 1008 ::= { tripPeerEntry 10 } 1010 tripPeerMaxRetryInterval OBJECT-TYPE 1011 SYNTAX Integer32 (0..2147483647) 1012 UNITS "Seconds" 1013 MAX-ACCESS read-create 1014 STATUS current 1015 DESCRIPTION 1016 "Specifies the maximum amount of time that will elapse 1017 between connection retries. Once the value of 1018 tripPeerConnectRetryInterval has reached this value, no 1019 more retries will be attempted. Attempts to set this 1020 value lower than the retry interval SHOULD not be 1021 allowed." 1022 DEFVAL { 360 } 1023 ::= { tripPeerEntry 11 } 1025 tripPeerHoldTime OBJECT-TYPE 1026 SYNTAX Integer32 (1..2147483647) 1027 UNITS "Seconds" 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "The time interval in seconds for the hold timer that 1032 is established with the peer. The value of this object 1034 Zinman/Walker/Jiang 20 1035 is the smaller of the values in 1036 tripPeerHoldTimeConfigured and the hold time received 1037 in the open message." 1038 ::= { tripPeerEntry 12 } 1040 tripPeerKeepAlive OBJECT-TYPE 1041 SYNTAX Integer32 (1..2147483647) 1042 UNITS "Seconds" 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "Specifies the amount of time that MUST elapse between 1047 keep alive messages. This value is negotiated with the 1048 remote when a connection is established." 1049 ::= { tripPeerEntry 13 } 1051 tripPeerHoldTimeConfigured OBJECT-TYPE 1052 SYNTAX Integer32 (0 | 3..65535) 1053 UNITS "Seconds" 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "Specifies the maximum time that MAY elapse between the 1058 receipt of successive keepalive or update message. A value 1059 of 0 means that keepalive or update messages will not be 1060 sent." 1061 DEFVAL { 240 } 1062 ::= { tripPeerEntry 14 } 1064 tripPeerKeepAliveConfigured OBJECT-TYPE 1065 SYNTAX Integer32 (1..2147483647) 1066 UNITS "Seconds" 1067 MAX-ACCESS read-create 1068 STATUS current 1069 DESCRIPTION 1070 "Specifies the amount of time that MUST elapse between 1071 keep alive messages." 1072 DEFVAL { 30 } 1073 ::= { tripPeerEntry 15 } 1075 tripPeerMaxPurgeTime OBJECT-TYPE 1076 SYNTAX Integer32 (1..65535) 1077 UNITS "Seconds" 1078 MAX-ACCESS read-create 1079 STATUS current 1080 DESCRIPTION 1081 "Indicates the interval that the LS MUST maintain routes 1082 marked as withdrawn in its database." 1083 DEFVAL { 10 } 1084 ::= { tripPeerEntry 16 } 1086 tripPeerDisableTime OBJECT-TYPE 1088 Zinman/Walker/Jiang 21 1089 SYNTAX Integer32 (1..65535) 1090 UNITS "Seconds" 1091 MAX-ACCESS read-create 1092 STATUS current 1093 DESCRIPTION 1094 "Indicate the interval that the TRIP module of the remote 1095 peer LS MUST be disabled while routes originated by the 1096 local LS with high sequence numbers can be removed." 1097 DEFVAL { 180 } 1098 ::= { tripPeerEntry 17 } 1100 tripPeerLearned OBJECT-TYPE 1101 SYNTAX TruthValue 1102 MAX-ACCESS read-only 1103 STATUS current 1104 DESCRIPTION 1105 "Indicates whether this entry was learned or 1106 configured." 1107 DEFVAL { false } 1108 ::= { tripPeerEntry 18 } 1110 tripPeerStorage OBJECT-TYPE 1111 SYNTAX StorageType 1112 MAX-ACCESS read-create 1113 STATUS current 1114 DESCRIPTION 1115 "The storage type for this conceptual row. Conceptual 1116 rows having the value 'permanent' need not allow write- 1117 access to any columnar objects in the row. It is not a 1118 requirement that this storage be non volatile." 1119 DEFVAL { nonVolatile } 1120 ::= { tripPeerEntry 19 } 1122 tripPeerRowStatus OBJECT-TYPE 1123 SYNTAX RowStatus 1124 MAX-ACCESS read-create 1125 STATUS current 1126 DESCRIPTION 1127 "The row status of the entry. This object is REQUIRED to 1128 create or delete rows remotely by a manager. If the 1129 instance already exists for a particular applIndex, the 1130 row create operation will fail. 1132 The value of this object has no effect on whether 1133 other objects in this conceptual row can be modified. 1135 Entries in this table can be learned by the TRIP 1136 application, or provisioned through this table." 1137 ::= { tripPeerEntry 20 } 1139 -- 1140 -- TripPeerStatisticsTable 1142 Zinman/Walker/Jiang 22 1143 -- 1144 tripPeerStatisticsTable OBJECT-TYPE 1145 SYNTAX SEQUENCE OF TripPeerStatisticsEntry 1146 MAX-ACCESS not-accessible 1147 STATUS current 1148 DESCRIPTION 1149 "The TRIP peer stats table. This table contains one 1150 entry per remote TRIP peer, and statistics related to the 1151 connection with the remote peer. The objects in this 1152 table are volatile." 1153 ::= { tripMIBObjects 5 } 1155 tripPeerStatisticsEntry OBJECT-TYPE 1156 SYNTAX TripPeerStatisticsEntry 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "Entry containing information about the connection with 1161 a TRIP peer." 1162 AUGMENTS { tripPeerEntry } 1163 ::= { tripPeerStatisticsTable 1 } 1165 TripPeerStatisticsEntry ::= SEQUENCE { 1166 tripPeerInUpdates Counter32, 1167 tripPeerOutUpdates Counter32, 1168 tripPeerInTotalMessages Counter32, 1169 tripPeerOutTotalMessages Counter32, 1170 tripPeerFsmEstablishedTransitions Counter32, 1171 tripPeerFsmEstablishedTime DateAndTime, 1172 tripPeerInUpdateElapsedTime TimeInterval, 1173 tripPeerStateChangeTime TimeStamp 1174 } 1176 tripPeerInUpdates OBJECT-TYPE 1177 SYNTAX Counter32 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "The number of TRIP update messages received from this 1182 remote peer since the last restart of this location 1183 server." 1184 ::= { tripPeerStatisticsEntry 1 } 1186 tripPeerOutUpdates OBJECT-TYPE 1187 SYNTAX Counter32 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "The number of TRIP update messages sent to this remote 1192 peer since the last restart of this LS." 1193 ::= { tripPeerStatisticsEntry 2 } 1195 Zinman/Walker/Jiang 23 1196 tripPeerInTotalMessages OBJECT-TYPE 1197 SYNTAX Counter32 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "The total number of TRIP messages received from the 1202 remote peer on this connection since the last restart 1203 of this LS." 1204 ::= { tripPeerStatisticsEntry 3 } 1206 tripPeerOutTotalMessages OBJECT-TYPE 1207 SYNTAX Counter32 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "The total number of outgoing TRIP messages sent to the 1212 remote peer since the last restart of this LS." 1213 ::= { tripPeerStatisticsEntry 4 } 1215 tripPeerFsmEstablishedTransitions OBJECT-TYPE 1216 SYNTAX Counter32 1217 MAX-ACCESS read-only 1218 STATUS current 1219 DESCRIPTION 1220 "The number of times the remote peer has transitioned 1221 into the established state since the last restart of this 1222 LS." 1223 ::= { tripPeerStatisticsEntry 5 } 1225 tripPeerFsmEstablishedTime OBJECT-TYPE 1226 SYNTAX DateAndTime 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "Indicates the time and date that this remote peer entered 1231 the 'established' state." 1232 ::= { tripPeerStatisticsEntry 6 } 1234 tripPeerInUpdateElapsedTime OBJECT-TYPE 1235 SYNTAX TimeInterval 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "Elapsed time in hundredths of seconds since the last 1240 TRIP update message was received from this remote peer." 1241 ::= { tripPeerStatisticsEntry 7 } 1243 tripPeerStateChangeTime OBJECT-TYPE 1244 SYNTAX TimeStamp 1245 MAX-ACCESS read-only 1246 STATUS current 1247 DESCRIPTION 1249 Zinman/Walker/Jiang 24 1250 "The value of sysUpTime when the last state change of 1251 tripPeerState took place." 1252 ::= { tripPeerStatisticsEntry 8 } 1254 -- TRIP Received Route Table. This table contains 1255 -- all routes from all sources. Each entry consists 1256 -- of a route and its associated path attributes. 1258 tripRouteTable OBJECT-TYPE 1259 SYNTAX SEQUENCE OF TripRouteEntry 1260 MAX-ACCESS not-accessible 1261 STATUS current 1262 DESCRIPTION 1263 "The TRIP route table containing information about 1264 reachable routes that are to be added to service by the 1265 receiving LS. The objects in this table are volatile 1266 and are refreshed when this LS rediscovers its route 1267 table." 1268 ::= { tripMIBObjects 6 } 1270 tripRouteEntry OBJECT-TYPE 1271 SYNTAX TripRouteEntry 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "Information about a route to a called destination." 1276 INDEX { applIndex, 1277 tripRouteAppProtocol, 1278 tripRouteAddressFamily, 1279 tripRouteAddress, 1280 tripRoutePeer 1281 } 1282 ::= { tripRouteTable 1 } 1284 TripRouteEntry ::= SEQUENCE { 1285 tripRouteAppProtocol TripAppProtocol, 1286 tripRouteAddressFamily TripAddressFamily, 1287 tripRouteAddress OCTET STRING, 1288 tripRoutePeer TripId, 1289 tripRouteTRIBMask BITS, 1290 tripRouteAddressSequenceNumber Integer32, 1291 tripRouteAddressOriginatorId TripId, 1292 tripRouteNextHopServerIAddrType InetAddressType, 1293 tripRouteNextHopServer InetAddress, 1294 tripRouteNextHopServerPort InetPortNumber, 1295 tripRouteNextHopServerItad TripItad, 1296 tripRouteMultiExitDisc Unsigned32, 1297 tripRouteLocalPref Unsigned32, 1298 tripRouteAdvertisementPath OCTET STRING, 1299 tripRouteRoutedPath OCTET STRING, 1300 tripRouteAtomicAggregate TruthValue, 1301 tripRouteUnknown OCTET STRING, 1303 Zinman/Walker/Jiang 25 1304 tripRouteWithdrawn TruthValue, 1305 tripRouteConverted TruthValue, 1306 tripRouteReceivedTime TimeStamp 1307 } 1309 tripRouteAppProtocol OBJECT-TYPE 1310 SYNTAX TripAppProtocol 1311 MAX-ACCESS not-accessible 1312 STATUS current 1313 DESCRIPTION 1314 "The protocol for which this entry of the routing table 1315 is maintained." 1316 ::= { tripRouteEntry 1 } 1318 tripRouteAddressFamily OBJECT-TYPE 1319 SYNTAX TripAddressFamily 1320 MAX-ACCESS not-accessible 1321 STATUS current 1322 DESCRIPTION 1323 "Specifies the type of address for the destination 1324 route." 1325 ::= { tripRouteEntry 2 } 1327 tripRouteAddress OBJECT-TYPE 1328 SYNTAX OCTET STRING (SIZE(1..105)) 1329 MAX-ACCESS not-accessible 1330 STATUS current 1331 DESCRIPTION 1332 "This is the address (prefix) of the family type given 1333 by Address Family of the destination. It is the prefix 1334 of addresses reachable from this gateway via the next 1335 hop server. The SIZE value of 105 has been assigned due 1336 to the sub identifier of object types length limitation 1337 as defined in SMIv2." 1338 REFERENCE 1339 "RFC 3219, section 5.1.1.1." 1340 ::= { tripRouteEntry 3 } 1342 tripRoutePeer OBJECT-TYPE 1343 SYNTAX TripId 1344 MAX-ACCESS not-accessible 1345 STATUS current 1346 DESCRIPTION 1347 "The identifier of the peer where the route information 1348 was learned." 1349 ::= { tripRouteEntry 4 } 1351 tripRouteTRIBMask OBJECT-TYPE 1352 SYNTAX BITS { 1353 adjTribIns(0), 1354 extTrib(1), 1355 locTrib(2), 1357 Zinman/Walker/Jiang 26 1358 adjTribOut(3) 1359 } 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "Indicates which Telephony Routing Information Base (TRIB) 1364 this entry belongs to. This is 1365 a bit-map of possible types. If the bit has a value of 1366 1, then the entry is a member of the corresponding TRIB 1367 type. If the bit has a value of 0 then the entry is not 1368 a member of the TRIP type. The various bit positions 1369 are: 1371 0 adjTribIns The entry is of type adj-TRIBs-ins, 1372 stores routing information that has 1373 been learned from inbound UPDATE 1374 messages. 1375 1 extTrib The entry is of type ext-TRIB, the 1376 best route for a given destination. 1377 2 locTrib The entry is of type loc-TRIB contains 1378 the local TRIP routing information 1379 that the LS has selected. 1380 3 adjTribOut The entry is of type adj-TRIBs-out, 1381 stores the information that the local 1382 LS has selected for advertisement to 1383 its external peers." 1384 REFERENCE 1385 "RFC 3291, section 3.5." 1386 ::= { tripRouteEntry 5 } 1388 tripRouteAddressSequenceNumber OBJECT-TYPE 1389 SYNTAX Integer32 (1..2147483647) 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "Indicates the version of the destination route 1394 originated by the LS identified by 1395 tripRouteAddressOriginatorId intra-domain attribute." 1396 ::= { tripRouteEntry 6 } 1398 tripRouteAddressOriginatorId OBJECT-TYPE 1399 SYNTAX TripId 1400 MAX-ACCESS read-only 1401 STATUS current 1402 DESCRIPTION 1403 "This is an intra-domain attribute indicating the 1404 internal LS that originated the route into the ITAD." 1405 ::= { tripRouteEntry 7 } 1407 tripRouteNextHopServerIAddrType OBJECT-TYPE 1408 SYNTAX InetAddressType 1409 MAX-ACCESS read-only 1411 Zinman/Walker/Jiang 27 1412 STATUS current 1413 DESCRIPTION 1414 "The type of Inet Address of the 1415 tripRouteNextHopServer." 1416 REFERENCE 1417 "RFC 3291, section 3." 1418 ::= { tripRouteEntry 8 } 1420 tripRouteNextHopServer OBJECT-TYPE 1421 SYNTAX InetAddress 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "Indicates the next hop that messages of a given 1426 protocol destined for tripRouteAddress SHOULD 1427 be sent to." 1428 ::= { tripRouteEntry 9 } 1430 tripRouteNextHopServerPort OBJECT-TYPE 1431 SYNTAX InetPortNumber 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "The port of the next hop server that this route 1436 will use." 1437 ::= { tripRouteEntry 10 } 1439 tripRouteNextHopServerItad OBJECT-TYPE 1440 SYNTAX TripItad 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "Indicates the domain of the next hop." 1445 ::= { tripRouteEntry 11 } 1447 tripRouteMultiExitDisc OBJECT-TYPE 1448 SYNTAX Unsigned32 (0..4294967295) 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "The Multiple Exit Discriminator allows an LS to 1453 discriminate between, and indicate preference for, 1454 otherwise similar routes to a neighbouring domain. 1455 A higher value represents a more preferred routing 1456 object." 1457 REFERENCE 1458 "RFC 3219, section 5.8" 1459 ::= { tripRouteEntry 12 } 1461 tripRouteLocalPref OBJECT-TYPE 1462 SYNTAX Unsigned32 (0..4294967295) 1463 MAX-ACCESS read-only 1465 Zinman/Walker/Jiang 28 1466 STATUS current 1467 DESCRIPTION 1468 "Indicated the local LS's degree of preference for an 1469 advertised route destination." 1470 REFERENCE 1471 "RFC 3219, section 4.3.4.7" 1472 ::= { tripRouteEntry 13 } 1474 tripRouteAdvertisementPath OBJECT-TYPE 1475 SYNTAX OCTET STRING (SIZE(4..252)) 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "Identifies the sequence of domains through which this 1480 advertisement has passed. 1482 This object is probably best represented as sequence of 1483 TripItads. For SMI compatibility, though, it is 1484 represented as an OCTET STRING. This object is a sequence 1485 of ITADs where each set of 4 octets corresponds to a TRIP 1486 ITAD in network byte order." 1487 REFERENCE 1488 "RFC 3219, section 4.3.4.4" 1489 ::= { tripRouteEntry 14 } 1491 tripRouteRoutedPath OBJECT-TYPE 1492 SYNTAX OCTET STRING (SIZE(4..252)) 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "Identifies the ITADs through which messages sent using 1497 this route would pass. These are a subset of 1498 tripRouteAdvertisementPath. 1500 This object is probably best represented as sequence of 1501 TripItads. For SMI compatibility, though, it is 1502 represented as OCTET STRING. This object is a sequence 1503 of ITADs where each set of 4 octets corresponds to a TRIP 1504 ITAD in network byte order." 1505 REFERENCE 1506 "RFC 3219, section 4.3.4.5" 1507 ::= { tripRouteEntry 15 } 1509 tripRouteAtomicAggregate OBJECT-TYPE 1510 SYNTAX TruthValue 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "Indicates that a route MAY traverse domains not listed 1515 in tripRouteRoutedPath. If an LS selects the less 1516 specific route from a set of overlapping routes, then 1517 this value returns TRUE." 1519 Zinman/Walker/Jiang 29 1520 REFERENCE 1521 "RFC 3219, section 4.3.4.6" 1522 ::= { tripRouteEntry 16 } 1524 tripRouteUnknown OBJECT-TYPE 1525 SYNTAX OCTET STRING (SIZE(0..255)) 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "This object contains one or more attributes that were not 1530 understood, and because they were transitive, were dropped 1531 during aggregation. They take the format of a triple 1532 , of 1533 variable length. If no attributes were dropped, this 1534 returns an OCTET STRING of size 0." 1535 REFERENCE 1536 "RFC 3219, sections 4.3.1, 4.3.2.3" 1537 ::= { tripRouteEntry 17 } 1539 tripRouteWithdrawn OBJECT-TYPE 1540 SYNTAX TruthValue 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "Indicates if this route is to be removed from service 1545 by the receiving LS." 1546 ::= { tripRouteEntry 18 } 1548 tripRouteConverted OBJECT-TYPE 1549 SYNTAX TruthValue 1550 MAX-ACCESS read-only 1551 STATUS current 1552 DESCRIPTION 1553 "Indicates if this route has been converted to a 1554 different application protocol than it had originally." 1555 ::= { tripRouteEntry 19 } 1557 tripRouteReceivedTime OBJECT-TYPE 1558 SYNTAX TimeStamp 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "The value of sysUpTime when this route was received." 1563 ::= { tripRouteEntry 20 } 1565 -- 1566 -- TRIP Received Route Community Table. 1567 -- 1569 tripRouteCommunityTable OBJECT-TYPE 1570 SYNTAX SEQUENCE OF TripRouteCommunityEntry 1571 MAX-ACCESS not-accessible 1573 Zinman/Walker/Jiang 30 1574 STATUS current 1575 DESCRIPTION 1576 "A table containing a list of TRIP communities associated 1577 with a route. Each instance of tripRouteTypeEntry that has 1578 the tripRouteTypePeer object set to remote(2) has an 1579 instance in the tripRouteTable as a parent. The objects 1580 in this table are volatile and are refreshed after a 1581 reboot." 1582 REFERENCE 1583 "RFC 3219, section 5.9." 1584 ::= { tripMIBObjects 7 } 1586 tripRouteCommunityEntry OBJECT-TYPE 1587 SYNTAX TripRouteCommunityEntry 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "Information about communities associated with a route. 1592 An entry with a tripRouteAddress of 00 and a 1593 tripRoutePeer of 0 refers to the local LS." 1594 INDEX { applIndex, 1595 tripRouteAppProtocol, 1596 tripRouteAddressFamily, 1597 tripRouteAddress, 1598 tripRoutePeer, 1599 tripRouteCommunityId 1600 } 1601 ::= { tripRouteCommunityTable 1 } 1603 TripRouteCommunityEntry ::= SEQUENCE { 1604 tripRouteCommunityId TripCommunityId, 1605 tripRouteCommunityItad TripItad 1606 } 1608 tripRouteCommunityId OBJECT-TYPE 1609 SYNTAX TripCommunityId 1610 MAX-ACCESS not-accessible 1611 STATUS current 1612 DESCRIPTION 1613 "The community identifier." 1614 ::= { tripRouteCommunityEntry 1 } 1616 tripRouteCommunityItad OBJECT-TYPE 1617 SYNTAX TripItad 1618 MAX-ACCESS read-only 1619 STATUS current 1620 DESCRIPTION 1621 "The ITAD associated with this community." 1622 ::= { tripRouteCommunityEntry 2 } 1624 -- 1625 -- tripItadTopologyTable 1627 Zinman/Walker/Jiang 31 1628 -- 1630 tripItadTopologyTable OBJECT-TYPE 1631 SYNTAX SEQUENCE OF TripItadTopologyEntry 1632 MAX-ACCESS not-accessible 1633 STATUS current 1634 DESCRIPTION 1635 "The sequence of link connections between peers within an 1636 ITAD. The objects in this table are volatile and are 1637 refreshed after a reboot." 1638 ::= { tripMIBObjects 8 } 1640 tripItadTopologyEntry OBJECT-TYPE 1641 SYNTAX TripItadTopologyEntry 1642 MAX-ACCESS not-accessible 1643 STATUS current 1644 DESCRIPTION 1645 "Information about a peer of the LS identified by 1646 tripItadTopologyOrigId." 1647 INDEX { applIndex, tripItadTopologyOrigId } 1648 ::= { tripItadTopologyTable 1 } 1650 TripItadTopologyEntry ::= SEQUENCE { 1651 tripItadTopologyOrigId TripId, 1652 tripItadTopologySeqNum Unsigned32 1653 } 1655 tripItadTopologyOrigId OBJECT-TYPE 1656 SYNTAX TripId 1657 MAX-ACCESS not-accessible 1658 STATUS current 1659 DESCRIPTION 1660 "Indicates the internal LS that originated the ITAD 1661 topology information into the ITAD." 1662 ::= { tripItadTopologyEntry 1 } 1664 tripItadTopologySeqNum OBJECT-TYPE 1665 SYNTAX Unsigned32 (1..2147483647) 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "Indicates the version of the ITAD topology originated 1670 by the LS identified by tripItadTopologyOrigId." 1671 ::= { tripItadTopologyEntry 2 } 1673 -- 1674 -- tripItadTopologyIdTable 1675 -- 1677 tripItadTopologyIdTable OBJECT-TYPE 1678 SYNTAX SEQUENCE OF TripItadTopologyIdEntry 1679 MAX-ACCESS not-accessible 1681 Zinman/Walker/Jiang 32 1682 STATUS current 1683 DESCRIPTION 1684 "The list of other LS's within the ITAD domain that the 1685 LS identified by tripItadTopologyOrigId is currently 1686 peering. Each instance of tripItadTopologyIdEntry has an 1687 instance in the tripItadTopologyTable as a parent. The 1688 objects in this table are volatile and are refreshed 1689 after a reboot." 1690 ::= { tripMIBObjects 9 } 1692 tripItadTopologyIdEntry OBJECT-TYPE 1693 SYNTAX TripItadTopologyIdEntry 1694 MAX-ACCESS not-accessible 1695 STATUS current 1696 DESCRIPTION 1697 "Information about a peer to the LS identified by 1698 tripItadTopologyOrigId." 1699 INDEX { applIndex, 1700 tripItadTopologyOrigId, 1701 tripItadTopologyId } 1702 ::= { tripItadTopologyIdTable 1 } 1704 TripItadTopologyIdEntry ::= SEQUENCE { 1705 tripItadTopologyId TripId 1706 } 1708 tripItadTopologyId OBJECT-TYPE 1709 SYNTAX TripId 1710 MAX-ACCESS read-only 1711 STATUS current 1712 DESCRIPTION 1713 "The index into this entry. Indicates the other location 1714 servers within the ITAD domain that this LS identified 1715 by tripItadTopologyOrigId is currently peering." 1716 ::= { tripItadTopologyIdEntry 1 } 1718 -- 1719 -- Notification objects 1720 -- 1722 tripNotifApplIndex OBJECT-TYPE 1723 SYNTAX Integer32 (1..2147483647) 1724 MAX-ACCESS accessible-for-notify 1725 STATUS current 1726 DESCRIPTION 1727 "This object contains the applIndex as described in 1728 RFC 2788. It is used to bind this notification with a 1729 specific instance of TRIP entity." 1730 ::= { tripMIBNotifObjects 1 } 1732 tripNotifPeerAddrInetType OBJECT-TYPE 1733 SYNTAX InetAddressType 1735 Zinman/Walker/Jiang 33 1736 MAX-ACCESS accessible-for-notify 1737 STATUS current 1738 DESCRIPTION 1739 "The type of Inet Address of the tripNotifPeerAddr." 1740 REFERENCE 1741 "RFC 3291, section 3." 1742 ::= { tripMIBNotifObjects 2 } 1744 tripNotifPeerAddr OBJECT-TYPE 1745 SYNTAX InetAddress 1746 MAX-ACCESS accessible-for-notify 1747 STATUS current 1748 DESCRIPTION 1749 "The IP address of this entry's TRIP peer LS. This object 1750 contains the value of tripPeerRemoteAddr." 1751 REFERENCE 1752 "RFC 3291, section 3." 1753 ::= { tripMIBNotifObjects 3 } 1755 tripNotifPeerErrCode OBJECT-TYPE 1756 SYNTAX INTEGER { 1757 messageHeader(1), 1758 openMessage(2), 1759 updateMessage(3), 1760 holdTimerExpired(4), 1761 finiteStateMachine(5), 1762 cease(6), 1763 tripNotification(7) 1764 } 1765 MAX-ACCESS accessible-for-notify 1766 STATUS current 1767 DESCRIPTION 1768 "Notification message of TRIP error. The meaning of this 1769 value is applicable to the following functions: 1771 messageHeader(1) 1772 - All errors detected while processing the TRIP message 1773 header. 1775 openMessage(2) 1776 - All errors detected while processing the OPEN message. 1778 updateMessage(3) 1779 - All errors detected while processing the UPDATE 1780 message. 1782 holdTimerExpired(4) 1783 - A notification generated when the hold timer expires. 1785 finiteStateMachine(5) 1786 - All errors detected by the TRIP Finite State Machine. 1788 Zinman/Walker/Jiang 34 1789 cease(6) 1790 - Any fatal error condition that the rest of the values 1791 do not cover. 1793 tripNotification(7) 1794 - Any error encountered while sending a notification 1795 message." 1796 ::= { tripMIBNotifObjects 4 } 1798 tripNotifPeerErrSubcode OBJECT-TYPE 1799 SYNTAX Integer32 (1..2147483647) 1800 MAX-ACCESS accessible-for-notify 1801 STATUS current 1802 DESCRIPTION 1803 "The sub error code associated with error code. The 1804 meaning of this value is dependent on the value of 1805 tripNotifPeerErrCode. 1807 Message Header (1) Error Subcodes: 1808 1 - Bad Message Length. 1809 2 - Bad Message Type. 1811 OPEN Message (2) Error Subcodes: 1812 1 - Unsupported Version Number. 1813 2 - Bad Peer ITAD. 1814 3 - Bad TRIP Identifier. 1815 4 - Unsupported Optional Parameter. 1816 5 - Unacceptable Hold Time. 1817 6 - Unsupported Capability. 1818 7 - Capability Mismatch. 1820 UPDATE Message (3) Error Subcodes: 1821 1 - Malformed Attribute List. 1822 2 - Unrecognized Well-known Attribute. 1823 3 - Missing Well-known Mandatory Attribute. 1824 4 - Attribute Flags Error. 1825 5 - Attribute Length Error. 1826 6 - Invalid Attribute." 1827 ::= { tripMIBNotifObjects 5 } 1829 -- 1830 -- Notifications 1831 -- 1832 tripConnectionEstablished NOTIFICATION-TYPE 1833 OBJECTS { tripNotifApplIndex, 1834 tripNotifPeerAddrInetType, 1835 tripNotifPeerAddr 1836 } 1837 STATUS current 1838 DESCRIPTION 1839 "The TRIP Connection Established event is generated when 1840 the TRIP finite state machine enters the ESTABLISHED 1842 Zinman/Walker/Jiang 35 1843 state." 1844 ::= { tripMIBNotifications 1 } 1846 tripConnectionDropped NOTIFICATION-TYPE 1847 OBJECTS { tripNotifApplIndex, 1848 tripNotifPeerAddrInetType, 1849 tripNotifPeerAddr 1850 } 1851 STATUS current 1852 DESCRIPTION 1853 "The TRIP Connection Dropped event is generated when the 1854 TRIP finite state machine leaves the ESTABLISHED state." 1855 ::= { tripMIBNotifications 2 } 1857 tripFSM NOTIFICATION-TYPE 1858 OBJECTS { tripNotifApplIndex, 1859 tripNotifPeerAddrInetType, 1860 tripNotifPeerAddr, 1861 tripNotifPeerErrCode, 1862 tripNotifPeerErrSubcode, 1863 tripPeerState 1864 } 1865 STATUS current 1866 DESCRIPTION 1867 "The trip FSM Event is generated when any error is 1868 detected by the TRIP Finite State Machine." 1869 ::= { tripMIBNotifications 3 } 1871 tripOpenMessageError NOTIFICATION-TYPE 1872 OBJECTS { tripNotifApplIndex, 1873 tripNotifPeerAddrInetType, 1874 tripNotifPeerAddr, 1875 tripNotifPeerErrCode, 1876 tripNotifPeerErrSubcode, 1877 tripPeerState 1878 } 1879 STATUS current 1880 DESCRIPTION 1881 "Errors detected while processing the OPEN message." 1882 ::= { tripMIBNotifications 4 } 1884 tripUpdateMessageError NOTIFICATION-TYPE 1885 OBJECTS { tripNotifApplIndex, 1886 tripNotifPeerAddrInetType, 1887 tripNotifPeerAddr, 1888 tripNotifPeerErrCode, 1889 tripNotifPeerErrSubcode, 1890 tripPeerState 1891 } 1892 STATUS current 1893 DESCRIPTION 1894 "Errors detected while processing the UPDATE message." 1896 Zinman/Walker/Jiang 36 1897 ::= { tripMIBNotifications 5 } 1899 tripHoldTimerExpired NOTIFICATION-TYPE 1900 OBJECTS { tripNotifApplIndex, 1901 tripNotifPeerAddrInetType, 1902 tripNotifPeerAddr, 1903 tripNotifPeerErrCode, 1904 tripNotifPeerErrSubcode, 1905 tripPeerState 1906 } 1907 STATUS current 1908 DESCRIPTION 1909 "The system does not receive successive messages within 1910 the period specified by the negotiated Hold Time." 1911 ::= { tripMIBNotifications 6 } 1913 tripConnectionCollision NOTIFICATION-TYPE 1914 OBJECTS { tripNotifApplIndex } 1915 STATUS current 1916 DESCRIPTION 1917 "A pair of LSs tried to simultaneously to establish a 1918 transport connection to each other." 1919 ::= { tripMIBNotifications 7 } 1921 tripCease NOTIFICATION-TYPE 1922 OBJECTS { tripNotifApplIndex, 1923 tripNotifPeerAddrInetType, 1924 tripNotifPeerAddr, 1925 tripNotifPeerErrCode, 1926 tripNotifPeerErrSubcode, 1927 tripPeerState 1928 } 1929 STATUS current 1930 DESCRIPTION 1931 "A TRIP peer MAY choose at any given time to close its TRIP 1932 connection by sending this notification message. However, 1933 the Cease notification message MUST NOT be used when a 1934 fatal error occurs." 1936 ::= { tripMIBNotifications 8 } 1938 tripNotificationErr NOTIFICATION-TYPE 1939 OBJECTS { tripNotifApplIndex } 1940 STATUS current 1941 DESCRIPTION 1942 "Generated if there is an error detected in a TRIP 1943 notification message sent with another cause. Note that 1944 the TRIP notification refered to in this object is not 1945 an SNMP notification, it is a specific message described 1946 in the TRIP specification." 1947 REFERENCE 1948 "RFC 3219, section 6.4." 1950 Zinman/Walker/Jiang 37 1951 ::= { tripMIBNotifications 9 } 1953 -- 1954 -- Compliance Statements 1955 -- 1956 tripCompliance MODULE-COMPLIANCE 1957 STATUS current 1958 DESCRIPTION 1959 "The compliance statement for TRIP entities." 1961 MODULE -- this module 1962 MANDATORY-GROUPS { tripConfigGroup, 1963 tripPeerTableConfigGroup, 1964 tripRouteGroup, 1965 tripItadTopologyGroup, 1966 tripPeerTableStatsGroup } 1968 GROUP tripNotificationGroup 1969 DESCRIPTION 1970 "This group is OPTIONAL. A TRIP entity can choose not to 1971 send any notifications. If this group is implemented, 1972 the tripNotifObjectGroup MUST also be implemented." 1974 GROUP tripNotifObjectGroup 1975 DESCRIPTION 1976 "This group is OPTIONAL. A TRIP entity can choose not to 1977 send any notifications. If this group is implemented, 1978 the tripNotificationGroup MUST also be implemented." 1980 MODULE NETWORK-SERVICES-MIB 1981 MANDATORY-GROUPS { applRFC2788Group } 1983 ::= { tripMIBCompliance 1 } 1985 -- 1986 -- Object and event conformance groups 1987 -- 1989 tripConfigGroup OBJECT-GROUP 1990 OBJECTS { 1991 tripCfgProtocolVersion, 1992 tripCfgItad, 1993 tripCfgIdentifier, 1994 tripCfgOperStatus, 1995 tripCfgAdminStatus, 1996 tripCfgAddrIAddrType, 1997 tripCfgAddr, 1998 tripCfgPort, 1999 tripCfgMinItadOriginationInterval, 2000 tripCfgMinRouteAdvertisementInterval, 2001 tripCfgMaxPurgeTime, 2002 tripCfgDisableTime, 2004 Zinman/Walker/Jiang 38 2005 tripCfgSendReceiveMode, 2006 tripCfgStorage, 2007 tripSupportedCommunityItad, 2008 tripSupportedCommunityStorage, 2009 tripRouteTypePeer, 2010 tripSupportedCommunityRowStatus 2011 } 2012 STATUS current 2013 DESCRIPTION 2014 "The global objects for configuring trip." 2015 ::= { tripMIBGroups 1 } 2017 tripPeerTableConfigGroup OBJECT-GROUP 2018 OBJECTS { 2019 tripPeerIdentifier, 2020 tripPeerState, 2021 tripPeerAdminStatus, 2022 tripPeerNegotiatedVersion, 2023 tripPeerSendReceiveMode, 2024 tripPeerRemoteItad, 2025 tripPeerConnectRetryInterval, 2026 tripPeerMaxRetryInterval, 2027 tripPeerHoldTime, 2028 tripPeerKeepAlive, 2029 tripPeerHoldTimeConfigured, 2030 tripPeerKeepAliveConfigured, 2031 tripPeerMaxPurgeTime, 2032 tripPeerDisableTime, 2033 tripPeerLearned, 2034 tripPeerStorage, 2035 tripPeerRowStatus 2036 } 2038 STATUS current 2039 DESCRIPTION 2040 "The global objects for configuring the TRIP peer 2041 table." 2042 ::= { tripMIBGroups 2 } 2044 tripPeerTableStatsGroup OBJECT-GROUP 2045 OBJECTS { 2046 tripPeerInUpdates, 2047 tripPeerOutUpdates, 2048 tripPeerInTotalMessages, 2049 tripPeerOutTotalMessages, 2050 tripPeerFsmEstablishedTransitions, 2051 tripPeerFsmEstablishedTime, 2052 tripPeerInUpdateElapsedTime, 2053 tripPeerStateChangeTime 2054 } 2055 STATUS current 2056 DESCRIPTION 2058 Zinman/Walker/Jiang 39 2059 "The global statistics the TRIP peer table." 2060 ::= { tripMIBGroups 3 } 2062 tripRouteGroup OBJECT-GROUP 2063 OBJECTS { 2064 tripRouteTRIBMask, 2065 tripRouteAddressSequenceNumber, 2066 tripRouteAddressOriginatorId, 2067 tripRouteNextHopServerIAddrType, 2068 tripRouteNextHopServer, 2069 tripRouteNextHopServerPort, 2070 tripRouteNextHopServerItad, 2071 tripRouteMultiExitDisc, 2072 tripRouteLocalPref, 2073 tripRouteAdvertisementPath, 2074 tripRouteRoutedPath, 2075 tripRouteAtomicAggregate, 2076 tripRouteUnknown, 2077 tripRouteWithdrawn, 2078 tripRouteConverted, 2079 tripRouteReceivedTime, 2080 tripRouteCommunityItad 2081 } 2083 STATUS current 2084 DESCRIPTION 2085 "The global objects for configuring route attribute." 2086 ::= { tripMIBGroups 4 } 2088 tripItadTopologyGroup OBJECT-GROUP 2089 OBJECTS { 2090 tripItadTopologySeqNum, 2091 tripItadTopologyId 2092 } 2093 STATUS current 2094 DESCRIPTION 2095 "The objects that define the TRIP ITAD topology." 2096 ::= { tripMIBGroups 5 } 2098 tripNotificationGroup NOTIFICATION-GROUP 2099 NOTIFICATIONS { 2100 tripConnectionEstablished, 2101 tripConnectionDropped, 2102 tripFSM, 2103 tripOpenMessageError, 2104 tripUpdateMessageError, 2105 tripHoldTimerExpired, 2106 tripConnectionCollision, 2107 tripCease, 2108 tripNotificationErr 2109 } 2110 STATUS current 2112 Zinman/Walker/Jiang 40 2113 DESCRIPTION 2114 "A collection of notifications defined for TRIP." 2115 ::= { tripMIBGroups 6 } 2117 tripNotifObjectGroup OBJECT-GROUP 2118 OBJECTS { 2119 tripNotifApplIndex, 2120 tripNotifPeerAddrInetType, 2121 tripNotifPeerAddr, 2122 tripNotifPeerErrCode, 2123 tripNotifPeerErrSubcode 2124 } 2125 STATUS current 2126 DESCRIPTION 2127 "The collection of objects that specify information for 2128 TRIP notifications." 2129 ::= { tripMIBGroups 7 } 2131 END 2133 7. Security Considerations 2135 The managed objects in this MIB module contain sensitive information 2136 since, collectively, they allow tracing and influencing of 2137 connections in TRIP devices and provide information of their 2138 connection characteristics. As such, improper manipulation of the 2139 objects represented by this MIB module MAY result in denial of 2140 service to a large number of availiable routes. 2142 There are a number of management objects defined in this MIB module 2143 that have a MAX-ACCESS clause of read-write and/or read-create. 2144 Such objects MAY be considered sensitive or vulnerable in some 2145 network environments. The support for SET operations in a non- 2146 secure environment without proper protection can have a negative 2147 effect on network operations. These objects include: 2149 tripCfgItad: 2150 Improper setting of tripCfgItad value can make all peer 2151 connections drop and not be re-established. 2153 tripCfgAdminStatus: 2154 Improper setting of tripCfgAdminStatus from up to down will 2155 cause the TRIP Location Server stop processing TRIP messages. 2157 tripCfgPort: 2158 Improper setting of tripCfgPort can cause the failure of a peer 2159 establishing a connection. 2161 tripCfgMinItadOriginationInterval, 2162 tripCfgMinRouteAdvertisementInterval: 2163 Improper configuration of these values MAY adversely affect 2164 local and global convergence of the routes advertised by this 2166 Zinman/Walker/Jiang 41 2167 TRIP Location Server. 2169 tripPeerAdminStatus: 2170 Improper setting of tripPeerAdminStatus from up to down can 2171 cause significant disruption of the connectivity to the 2172 destination via the applicable remote TRIP Location Server 2173 peer. 2175 tripPeerConnectRetryInterval,tripPeerMaxRetryInterval: 2176 Improper configuration of these values can cause connections to 2177 be disrupted for extremely long time periods when otherwise 2178 they would be restored in a relatively short period of time. 2180 tripPeerHoldTimeConfigured, tripPeerKeepAliveConfigured: 2181 Improper configuration of these value can make TRIP peer 2182 sessions more fragile and less resilient to denial of service 2183 attacks. 2185 There are a number of managed objects in this MIB module that 2186 contain sensitive information regarding the operation of a network. 2187 For example, a TRIP Location Server peer's local and remote 2188 addresses might be sensitive for ISPs who want to keep interface 2189 addresses on TRIP Location Server confidential so as to prevent TRIP 2190 Location Server addresses used for a denial of service attack or 2191 address spoofing. 2193 Therefore, it is thus important to control even GET access to these 2194 objects and possibly to even encrypt the values of these object when 2195 sending them over the network via SNMP. Not all versions of SNMP 2196 provide features for such a secure environment. 2198 SNMPv1 by itself is not a secure environment. Even if the network 2199 itself is secure (for example by using IPSec), even then, there is 2200 no control as to who on the secure network is allowed to access and 2201 GET/SET (read/change/create/delete) the objects in this MIB module. 2203 It is RECOMMENDED that the implementers consider the security 2204 features as provided by the SNMPv3 framework (see [RFC3410], section 2205 8), including full support for the SNMPv3 cryptographic mechanisms 2206 (for authentication and privacy). 2208 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2209 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2210 enable cryptographic security. It is then a customer/operator 2211 responsibility to ensure that the SNMP entity giving access to an 2212 instance of this MIB module is properly configured to give access to 2213 the objects only to those principals (users) that have legitimate 2214 rights to indeed GET or SET (change/create/delete) them. 2216 8. Full Copyright Statement 2218 Copyright (C) The Internet Society (2003). All Rights Reserved. 2220 Zinman/Walker/Jiang 42 2221 This document and translations of it MAY be copied and furnished to 2222 others, and derivative works that comment on or otherwise explain it 2223 or assist in its implementation MAY be prepared, copied, published 2224 and distributed, in whole or in part, without restriction of any 2225 kind, provided that the above copyright notice and this paragraph 2226 are included on all such copies and derivative works. However, this 2227 document itself MAY not be modified in any way, such as by removing 2228 the copyright notice or references to the Internet Society or other 2229 Internet organizations, except as needed for the purpose of 2230 developing Internet standards in which case the procedures for 2231 copyrights defined in the Internet Standards process MUST be 2232 followed, or as REQUIRED to translate it into languages other than 2233 English. 2235 The limited permissions granted above are perpetual and will not be 2236 revoked by the Internet Society or its successors or assigns. 2238 This document and the information contained herein is provided on an 2239 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2240 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2241 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2242 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2243 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2245 9. Normative References 2247 [RFC3219] Rosenberg, J., Salama, H. and Squire, M., "Telephony 2248 Routing over IP (TRIP)", RFC 3219 January 2002. 2250 [RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, 2251 J., "Textual Conventions for Internet Network 2252 Addresses", RFC 3291, May 2002. 2254 [RFC1657] Willis, S., Burruss, J., and Chu, J., "Definitions of 2255 Managed Objects for the Fourth Version of the Border 2256 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July 2257 1994. 2259 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2260 Rose, M. and S. Waldbusser, "Structure of Management 2261 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2262 1999. 2264 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2265 Rose, M. and S. Waldbusser, "Textual Conventions for 2266 SMIv2", STD 58, RFC 2579, April 1999. 2268 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2269 Rose, M. and S. Waldbusser, "Conformance Statements for 2270 SMIv2", STD 58, RFC 2580, April 1999. 2272 Zinman/Walker/Jiang 43 2274 [RFC2026] Bradner, S., "The Internet Standards Process _ Revision 2275 3", BCP 9, RFC 2026, October 1996. 2277 10. Informative References 2279 [RFC1771] Rekhter, Y. and Li, T., "Border Gateway Protocol 4 2280 (BGP-4)", RFC 1771, March 1995. 2282 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2283 "Introduction and Applicability Statements for Internet- 2284 Standard Management Framework", RFC 3410, December 2002. 2286 11. Intellectual Property Notice 2288 The IETF takes no position regarding the validity or scope of any 2289 intellectual property or other rights that might be claimed to 2290 pertain to the implementation or use of the technology described in 2291 this document or the extent to which any license under such rights 2292 might or might not be available; neither does it represent that it 2293 has made any effort to identify any such rights. Information on the 2294 IETF's procedures with respect to rights in standards-track and 2295 standards-related documentation can be found in BCP 11. Copies of 2296 claims of rights made available for publication and any assurances 2297 of licenses to be made available, or the result of an attempt made 2298 to obtain a general license or permission for the use of such 2299 proprietary rights by implementers or users of this specification 2300 can be obtained from the IETF Secretariat. 2302 The IETF invites any interested party to bring to its attention any 2303 copyrights, patents or patent applications, or other proprietary 2304 rights which MAY cover technology that MAY be REQUIRED to practice 2305 this standard. Please address the information to the IETF Executive 2306 Director. 2308 The IETF has been notified of intellectual property rights claimed 2309 in regard to some or all of the specification contained in this 2310 document. For more information consult the online list of claimed 2311 rights. 2313 12. Acknowledgments 2315 The authors wish to thank Bert Wijnen, Dan Romascanu, and Jonathan 2316 Rosenberg for their insightful comments and suggestions. 2318 Thanks to Kevin Lingle for his invaluable comments, help with MIB 2319 things and great ideas. 2321 Zinman/Walker/Jiang 44 2322 13. Author's Addresses 2324 David Zinman 2325 Editor 2326 Soma Networks 2327 312 Adelaide St. West Suite 700 2328 Toronto ON, M5V 1R2 2329 Canada 2330 phone: +1 416 348 1656 2331 email: dzinman@somanetworks.com 2333 Dave Walker 2334 SS8 Networks, Inc. 2335 495 March Road, Suite #500 2336 Ottawa, ON K2K 3G1 2337 Canada 2338 Phone: +1 613 592 2100 2339 Email: drwalker@ss8.com 2341 Jianping Jiang 2342 SS8 Networks, Inc. 2343 495 March Road, Suite #500 2344 Ottawa, ON K2K 3G1 2345 Canada 2346 Phone: +1 613 592 2100 2347 Email: jianping@ss8.com 2349 14. Working Group 2351 IP Telephony (iptel) Working Group 2352 ================================== 2354 Mailing list: iptel@lists.bell-labs.com 2356 Chair: 2357 Jonathan Rosenberg 2359 Transport Area Directors: 2360 Scott Bradner 2361 Allison Mankin mankin@east.isi.edu 2363 Zinman/Walker/Jiang 45