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