idnits 2.17.1 draft-ietf-iptel-trip-mib-06.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.) ** 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 224: '...tet unsigned integer that MAY, but not...' RFC 2119 keyword, line 406: '...x. The objects in this table SHOULD be...' RFC 2119 keyword, line 509: '... is down(2) then tripOperStatus SHOULD...' (34 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 2238, 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 (~~), 6 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-06.txt Soma Networks 4 Expires: December 2003 D. Walker 5 Jianping 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.......................................43 63 11. Intellectual Property Notice.................................44 64 12. Acknowledgments..............................................44 65 13. Author's Addresses...........................................44 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 Telephony Routing over IP (TRIP) [RFC3219] is an inter-domain 106 application-layer control protocol that exchanges information 107 between TRIP location servers (LS) to provide efficient IP telephony 108 routing. This MIB module provides managed objects for TRIP devices 109 defined in Telephony Routing over IP [RFC3219]. 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 "200306080000Z" -- June 08, 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 module 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 "200306080000Z" -- June 08, 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 "200306080000Z" -- June 08, 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 } 389 Zinman/Walker/Jiang 8 390 tripMIBGroups OBJECT IDENTIFIER ::= 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 443 Zinman/Walker/Jiang 9 444 "This object will reflect the version of TRIP 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 Local Internet Telephony Administrative domain." 458 ::= { tripCfgEntry 2 } 460 tripCfgIdentifier OBJECT-TYPE 461 SYNTAX TripId 462 MAX-ACCESS read-only 463 STATUS current 464 DESCRIPTION 465 "The object that identifies this TRIP Client." 466 ::= { tripCfgEntry 3 } 468 tripCfgAdminStatus OBJECT-TYPE 469 SYNTAX INTEGER { 470 up(1), 471 down(2) 472 } 473 MAX-ACCESS read-write 474 STATUS current 475 DESCRIPTION 476 "The desired TRIP state. 478 up(1) : Set the application to normal operation. 480 down(2): Set the application to a state where it will 481 not process TRIP messages." 482 ::= { tripCfgEntry 4 } 484 tripCfgOperStatus OBJECT-TYPE 485 SYNTAX INTEGER { 486 up(1), 487 down(2), 488 faulty(3) 489 } 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "The current operational state of the TRIP protocol. 495 up(1): The application is operating normally, and 497 Zinman/Walker/Jiang 10 498 is processing (receiving and possibly 499 issuing) TRIP requests and responses. 501 down(2): The application is currently not processing 502 TRIP messages. This occurs if the TRIP 503 application is in an initialization state or 504 if tripCfgAdminStatus is set to down(2). 506 faulty(3): The application is not operating normally due 507 to a fault in the system. 509 If tripCfgAdminStatus is down(2) then tripOperStatus SHOULD 510 be down(2). If tripAdminStatus is changed to up(1) then 511 tripOperStatus SHOULD change to up(1) if there is no 512 fault that prevents the TRIP protocol from moving to the 513 up(1) state." 514 ::= { tripCfgEntry 5 } 516 tripCfgAddrIAddrType OBJECT-TYPE 517 SYNTAX InetAddressType 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The type of Inet Address of the tripAddr." 522 REFERENCE 523 "RFC 3291, section 3." 524 ::= { tripCfgEntry 6 } 526 tripCfgAddr OBJECT-TYPE 527 SYNTAX InetAddress 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "The network address of the local LS that the peer c 532 onnects to. The type of address depends on the object 533 tripCfgAddrIAddrType." 534 REFERENCE 535 "RFC 3291, section 3." 536 ::= { tripCfgEntry 7 } 538 tripCfgPort OBJECT-TYPE 539 SYNTAX InetPortNumber 540 MAX-ACCESS read-write 541 STATUS current 542 DESCRIPTION 543 "The local tcp/udp port on the local LS that the peer 544 connects to." 545 ::= { tripCfgEntry 8 } 547 tripCfgMinItadOriginationInterval OBJECT-TYPE 548 SYNTAX Integer32 (1..2147483647) 549 UNITS "Seconds" 551 Zinman/Walker/Jiang 11 552 MAX-ACCESS read-write 553 STATUS current 554 DESCRIPTION 555 "The minimum amount of time that MUST elapse between 556 advertisement of the update message that reports changes 557 within the LS's own ITAD." 558 DEFVAL { 30 } 559 ::= { tripCfgEntry 9 } 561 tripCfgMinRouteAdvertisementInterval OBJECT-TYPE 562 SYNTAX Integer32 (1..2147483647) 563 UNITS "Seconds" 564 MAX-ACCESS read-write 565 STATUS current 566 DESCRIPTION 567 "Specifies minimal interval between successive 568 advertisements to a particular destination from an LS." 569 DEFVAL { 30 } 570 ::= { tripCfgEntry 10 } 572 tripCfgMaxPurgeTime OBJECT-TYPE 573 SYNTAX Integer32 (1..2147483647) 574 UNITS "Seconds" 575 MAX-ACCESS read-write 576 STATUS current 577 DESCRIPTION 578 "Indicates the interval that the LS MUST maintain routes 579 marked as withdrawn in its database." 580 DEFVAL { 10 } 581 ::= { tripCfgEntry 11 } 583 tripCfgDisableTime 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 TRIP module of the 590 LS MUST be disabled while routes originated by this 591 location server with high sequence numbers can be 592 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, 658 Zinman/Walker/Jiang 13 659 tripRouteTypePeer INTEGER 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 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "The network address of this entry's TRIP peer LS." 678 REFERENCE 679 "RFC 3291, section 3." 680 ::= { tripRouteTypeEntry 2 } 682 tripRouteTypePort OBJECT-TYPE 683 SYNTAX InetPortNumber 684 MAX-ACCESS not-accessible 685 STATUS current 686 DESCRIPTION 687 "The port for the TCP connection between this and 688 an associated TRIP peer." 689 ::= { tripRouteTypeEntry 3 } 691 tripRouteTypeProtocolId OBJECT-TYPE 692 SYNTAX TripAppProtocol 693 MAX-ACCESS not-accessible 694 STATUS current 695 DESCRIPTION 696 "The object identifier of a protocol that the associated 697 peer is using." 698 ::= { tripRouteTypeEntry 4 } 700 tripRouteTypeAddrFamilyId OBJECT-TYPE 701 SYNTAX TripAddressFamily 702 MAX-ACCESS not-accessible 703 STATUS current 704 DESCRIPTION 705 "The object identifier of an address family that the 706 associated peer belongs to." 707 ::= { tripRouteTypeEntry 5 } 709 tripRouteTypePeer OBJECT-TYPE 710 SYNTAX INTEGER { local(1), remote(2) } 712 Zinman/Walker/Jiang 14 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "This object identifies whether this entry is 717 associated with a 'local' or 'remote' LS peer." 718 ::= { tripRouteTypeEntry 6 } 720 -- 721 -- tripSupportedCommunityTable 722 -- 724 tripSupportedCommunityTable OBJECT-TYPE 725 SYNTAX SEQUENCE OF TripSupportedCommunityEntry 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "The list of TRIP communities that this LS supports. A 730 TRIP community is a group of destinations that share 731 common properties. 733 The TRIP Supported Communities entry is used to group 734 destinations so that the routing decision can be based 735 on the identity of the group." 736 REFERENCE 737 "RFC 3219, section 5.9" 738 ::= { tripMIBObjects 3 } 740 tripSupportedCommunityEntry OBJECT-TYPE 741 SYNTAX TripSupportedCommunityEntry 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "Entry containing information about a community. A TRIP 746 community is a group of destinations that share some 747 common property. This attribute is used so that routing 748 decisions can be based on the identity of the group." 749 INDEX { applIndex, tripSupportedCommunityId } 750 ::= { tripSupportedCommunityTable 1 } 752 TripSupportedCommunityEntry ::= SEQUENCE { 753 tripSupportedCommunityId TripCommunityId, 754 tripSupportedCommunityItad TripItad, 755 tripSupportedCommunityStorage StorageType, 756 tripSupportedCommunityRowStatus RowStatus 757 } 759 tripSupportedCommunityId OBJECT-TYPE 760 SYNTAX TripCommunityId 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "The identifier of the supported Community." 766 Zinman/Walker/Jiang 15 767 ::= { tripSupportedCommunityEntry 1 } 769 tripSupportedCommunityItad OBJECT-TYPE 770 SYNTAX TripItad 771 MAX-ACCESS read-create 772 STATUS current 773 DESCRIPTION 774 "The Itad of the community." 775 ::= { tripSupportedCommunityEntry 2 } 777 tripSupportedCommunityStorage OBJECT-TYPE 778 SYNTAX StorageType 779 MAX-ACCESS read-create 780 STATUS current 781 DESCRIPTION 782 "The storage type for this conceptual row. Conceptual 783 rows having the value 'permanent' need not allow write- 784 access to any columnar objects in the row. It is not a 785 requirement that this storage be non volatile." 786 DEFVAL { nonVolatile } 787 ::= { tripSupportedCommunityEntry 3 } 789 tripSupportedCommunityRowStatus OBJECT-TYPE 790 SYNTAX RowStatus 791 MAX-ACCESS read-create 792 STATUS current 793 DESCRIPTION 794 "The row status of the entry. This object is REQUIRED 795 to create or delete rows by a manager. A value for 796 tripSupportedCommunityItad MUST be set for row creation 797 to be successful. If the instance already exists for a 798 particular applIndex, the row create operation will 799 fail. 801 The value of this object has no effect on whether 802 other objects in this conceptual row can be modified." 803 ::= { tripSupportedCommunityEntry 4 } 805 -- 806 -- TripPeerTable 807 -- 808 tripPeerTable OBJECT-TYPE 809 SYNTAX SEQUENCE OF TripPeerEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 813 "The TRIP peer table. This table contains one entry per 814 TRIP peer, and information about the connection with 815 the peer." 816 ::= { tripMIBObjects 4 } 818 tripPeerEntry OBJECT-TYPE 820 Zinman/Walker/Jiang 16 821 SYNTAX TripPeerEntry 822 MAX-ACCESS not-accessible 823 STATUS current 824 DESCRIPTION 825 "Entry containing information about the connection with 826 a TRIP peer." 827 INDEX { applIndex, 828 tripPeerRemoteAddrInetType, 829 tripPeerRemoteAddr, 830 tripPeerRemotePort } 831 ::= {tripPeerTable 1} 833 TripPeerEntry ::= SEQUENCE { 834 tripPeerRemoteAddrInetType InetAddressType, 835 tripPeerRemoteAddr InetAddress, 836 tripPeerRemotePort InetPortNumber, 837 tripPeerIdentifier TripId, 838 tripPeerState INTEGER, 839 tripPeerAdminStatus INTEGER, 840 tripPeerNegotiatedVersion TripProtocolVersion, 841 tripPeerSendReceiveMode TripSendReceiveMode, 842 tripPeerRemoteItad TripItad, 843 tripPeerConnectRetryInterval Integer32, 844 tripPeerMaxRetryInterval Integer32, 845 tripPeerHoldTime Integer32, 846 tripPeerKeepAlive Integer32, 847 tripPeerHoldTimeConfigured Integer32, 848 tripPeerKeepAliveConfigured Integer32, 849 tripPeerMaxPurgeTime Integer32, 850 tripPeerDisableTime Integer32, 851 tripPeerLearned TruthValue, 852 tripPeerStorage StorageType, 853 tripPeerRowStatus RowStatus 854 } 856 tripPeerRemoteAddrInetType OBJECT-TYPE 857 SYNTAX InetAddressType 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION 861 "The type of Inet Address of the tripPeerRemoteAddr." 862 REFERENCE 863 "RFC 3291, section 3." 864 ::= { tripPeerEntry 1 } 866 tripPeerRemoteAddr OBJECT-TYPE 867 SYNTAX InetAddress 868 MAX-ACCESS not-accessible 869 STATUS current 870 DESCRIPTION 871 "The IP address of this entry's TRIP peer LS." 872 REFERENCE 874 Zinman/Walker/Jiang 17 875 "RFC 3291, section 3." 876 ::= { tripPeerEntry 2 } 878 tripPeerRemotePort OBJECT-TYPE 879 SYNTAX InetPortNumber 880 MAX-ACCESS not-accessible 881 STATUS current 882 DESCRIPTION 883 "The remote port for the TCP connection between the 884 TRIP peers." 885 ::= { tripPeerEntry 3 } 887 tripPeerIdentifier OBJECT-TYPE 888 SYNTAX TripId 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION 892 "TRIP identifier of the peer." 893 ::= { tripPeerEntry 4 } 895 tripPeerState OBJECT-TYPE 896 SYNTAX INTEGER { 897 idle(1), 898 connect(2), 899 active(3), 900 openSent(4), 901 openConfirm(5), 902 established(6) 903 } 904 MAX-ACCESS read-only 905 STATUS current 906 DESCRIPTION 907 "TRIP Peer Finite State Machine state. 909 idle(1) : The initial state. Local LS refuses all 910 incoming connections. No application 911 resources are allocated to processing 912 information about the remote peer. 914 connect(2) : Local LS waiting for a transport 915 protocol connection to be completed to 916 the peer, and is listening for inbound 917 transport connections from the peer. 919 active(3) : Local LS is listening for an inbound 920 connection from the peer, but is not in 921 the process of initiating a connection 922 to the remote peer. 924 openSent(4) : Local LS has sent an OPEN message to its 925 peer and is waiting for an OPEN message 926 from the remote peer. 928 Zinman/Walker/Jiang 18 929 openConfirm(5): Local LS has sent an OPEN message to the 930 remote peer, received an OPEN message from 931 the remote peer, and sent a KEEPALIVE 932 message in response to the OPEN. The local 933 LS is now waiting for a KEEPALIVE message 934 or a NOTIFICATION message in response to 935 its OPEN message. 937 established(6): LS can exchange UPDATE, NOTIFICATION, and 938 KEEPALIVE messages with its peer." 939 ::= { tripPeerEntry 5 } 941 tripPeerAdminStatus OBJECT-TYPE 942 SYNTAX INTEGER { 943 up(1), 944 down(2) 945 } 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "This object is used to affect the TRIP connection 950 state. 952 up(1) : Allow a connection with the peer LS. 954 down(2) : disconnect the connection from the peer LS and 955 do not allow any further connections to this 956 peer. 958 If this value is set to down(2) then tripPeerState will 959 have the value of idle(1)." 960 DEFVAL { up } 961 ::= { tripPeerEntry 6 } 963 tripPeerNegotiatedVersion OBJECT-TYPE 964 SYNTAX TripProtocolVersion 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "The negotiated version of TRIP running between this 969 local entity and this peer." 970 ::= { tripPeerEntry 7 } 972 tripPeerSendReceiveMode OBJECT-TYPE 973 SYNTAX TripSendReceiveMode 974 MAX-ACCESS read-only 975 STATUS current 976 DESCRIPTION 977 "The operational mode of this peer." 978 ::= { tripPeerEntry 8 } 980 Zinman/Walker/Jiang 19 981 tripPeerRemoteItad OBJECT-TYPE 982 SYNTAX TripItad 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "The Internet Telephony Administrative domain of 987 this peer." 988 ::= { tripPeerEntry 9 } 990 tripPeerConnectRetryInterval OBJECT-TYPE 991 SYNTAX Integer32 (0..2147483647) 992 UNITS "Seconds" 993 MAX-ACCESS read-create 994 STATUS current 995 DESCRIPTION 996 "Specifies the initial amount of time that will elapse 997 between connection retry. This value SHOULD double 998 after each attempt up to the value of 999 tripPeerMaxRetryInterval. This value MUST always be less 1000 than or equal to the value of tripPeerMaxRetryInterval. 1001 Attempts to set this value higher than the max retry 1002 will not be allowed." 1003 DEFVAL { 120 } 1004 ::= { tripPeerEntry 10 } 1006 tripPeerMaxRetryInterval OBJECT-TYPE 1007 SYNTAX Integer32 (0..2147483647) 1008 UNITS "Seconds" 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 "Specifies the maximum amount of time that will elapse 1013 between connection retries. Once the value of 1014 tripPeerConnectRetryInterval has reached this value, no 1015 more retries will be attempted. Attempts to set this 1016 value lower than the retry interval SHOULD not be 1017 allowed." 1018 DEFVAL { 360 } 1019 ::= { tripPeerEntry 11 } 1021 tripPeerHoldTime OBJECT-TYPE 1022 SYNTAX Integer32 (1..2147483647) 1023 UNITS "Seconds" 1024 MAX-ACCESS read-only 1025 STATUS current 1026 DESCRIPTION 1027 "The time interval in seconds for the hold timer that 1028 is established with the peer. The value of this object 1029 is the smaller of the values in 1030 tripPeerHoldTimeConfigured and the hold time received 1032 Zinman/Walker/Jiang 20 1033 in the open message." 1034 ::= { tripPeerEntry 12 } 1036 tripPeerKeepAlive OBJECT-TYPE 1037 SYNTAX Integer32 (1..2147483647) 1038 UNITS "Seconds" 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "Specifies the amount of time that MUST elapse between 1043 keep alive messages. This value is negotiated with the 1044 remote when a connection is established." 1045 ::= { tripPeerEntry 13 } 1047 tripPeerHoldTimeConfigured OBJECT-TYPE 1048 SYNTAX Integer32 (0 | 3..65535) 1049 UNITS "Seconds" 1050 MAX-ACCESS read-create 1051 STATUS current 1052 DESCRIPTION 1053 "Specifies the maximum time that MAY elapse between the 1054 receipt of successive keepalive or update message. A value 1055 of 0 means that keepalive or update messages will not be 1056 sent." 1057 DEFVAL { 240 } 1058 ::= { tripPeerEntry 14 } 1060 tripPeerKeepAliveConfigured OBJECT-TYPE 1061 SYNTAX Integer32 (1..2147483647) 1062 UNITS "Seconds" 1063 MAX-ACCESS read-create 1064 STATUS current 1065 DESCRIPTION 1066 "Specifies the amount of time that MUST elapse between 1067 keep alive messages." 1068 DEFVAL { 30 } 1069 ::= { tripPeerEntry 15 } 1071 tripPeerMaxPurgeTime OBJECT-TYPE 1072 SYNTAX Integer32 (1..65535) 1073 UNITS "Seconds" 1074 MAX-ACCESS read-create 1075 STATUS current 1076 DESCRIPTION 1077 "Indicates the interval that the LS MUST maintain routes 1078 marked as withdrawn in its database." 1079 DEFVAL { 10 } 1080 ::= { tripPeerEntry 16 } 1082 tripPeerDisableTime OBJECT-TYPE 1083 SYNTAX Integer32 (1..65535) 1084 UNITS "Seconds" 1086 Zinman/Walker/Jiang 21 1087 MAX-ACCESS read-create 1088 STATUS current 1089 DESCRIPTION 1090 "Indicate the interval that the TRIP module of the remote 1091 peer LS MUST be disabled while routes originated by the 1092 local LS with high sequence numbers can be removed." 1093 DEFVAL { 180 } 1094 ::= { tripPeerEntry 17 } 1096 tripPeerLearned OBJECT-TYPE 1097 SYNTAX TruthValue 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "Indicates whether this entry was learned or 1102 configured." 1103 DEFVAL { false } 1104 ::= { tripPeerEntry 18 } 1106 tripPeerStorage OBJECT-TYPE 1107 SYNTAX StorageType 1108 MAX-ACCESS read-create 1109 STATUS current 1110 DESCRIPTION 1111 "The storage type for this conceptual row. Conceptual 1112 rows having the value 'permanent' need not allow write- 1113 access to any columnar objects in the row. It is not a 1114 requirement that this storage be non volatile." 1115 DEFVAL { nonVolatile } 1116 ::= { tripPeerEntry 19 } 1118 tripPeerRowStatus OBJECT-TYPE 1119 SYNTAX RowStatus 1120 MAX-ACCESS read-create 1121 STATUS current 1122 DESCRIPTION 1123 "The row status of the entry. This object is REQUIRED to 1124 create or delete rows remotely by a manager. If the 1125 instance already exists for a particular applIndex, the 1126 row create operation will fail. 1128 The value of this object has no effect on whether 1129 other objects in this conceptual row can be modified. 1131 Entries in this table can be learned by the TRIP 1132 application, or provisioned through this table." 1133 ::= { tripPeerEntry 20 } 1135 -- 1136 -- TripPeerStatisticsTable 1137 -- 1138 tripPeerStatisticsTable OBJECT-TYPE 1140 Zinman/Walker/Jiang 22 1141 SYNTAX SEQUENCE OF TripPeerStatisticsEntry 1142 MAX-ACCESS not-accessible 1143 STATUS current 1144 DESCRIPTION 1145 "The TRIP peer stats table. This table contains one 1146 entry per remote TRIP peer, and statistics related to the 1147 connection with the remote peer. The objects in this 1148 table are volatile." 1149 ::= { tripMIBObjects 5 } 1151 tripPeerStatisticsEntry OBJECT-TYPE 1152 SYNTAX TripPeerStatisticsEntry 1153 MAX-ACCESS not-accessible 1154 STATUS current 1155 DESCRIPTION 1156 "Entry containing information about the connection with 1157 a TRIP peer." 1158 AUGMENTS { tripPeerEntry } 1159 ::= { tripPeerStatisticsTable 1 } 1161 TripPeerStatisticsEntry ::= SEQUENCE { 1162 tripPeerInUpdates Counter32, 1163 tripPeerOutUpdates Counter32, 1164 tripPeerInTotalMessages Counter32, 1165 tripPeerOutTotalMessages Counter32, 1166 tripPeerFsmEstablishedTransitions Counter32, 1167 tripPeerFsmEstablishedTime DateAndTime, 1168 tripPeerInUpdateElapsedTime TimeInterval, 1169 tripPeerStateChangeTime TimeStamp 1170 } 1172 tripPeerInUpdates OBJECT-TYPE 1173 SYNTAX Counter32 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "The number of TRIP update messages received from this 1178 remote peer since the last restart of this LS." 1179 ::= { tripPeerStatisticsEntry 1 } 1181 tripPeerOutUpdates OBJECT-TYPE 1182 SYNTAX Counter32 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "The number of TRIP update messages sent to this remote 1187 peer since the last restart of this location server." 1188 ::= { tripPeerStatisticsEntry 2 } 1190 tripPeerInTotalMessages OBJECT-TYPE 1191 SYNTAX Counter32 1192 MAX-ACCESS read-only 1194 Zinman/Walker/Jiang 23 1195 STATUS current 1196 DESCRIPTION 1197 "The total number of TRIP messages received from the 1198 remote peer on this connection since the last restart 1199 of this LS." 1200 ::= { tripPeerStatisticsEntry 3 } 1202 tripPeerOutTotalMessages OBJECT-TYPE 1203 SYNTAX Counter32 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "The total number of outgoing TRIP messages sent to the 1208 remote peer since the last restart of this LS." 1209 ::= { tripPeerStatisticsEntry 4 } 1211 tripPeerFsmEstablishedTransitions OBJECT-TYPE 1212 SYNTAX Counter32 1213 MAX-ACCESS read-only 1214 STATUS current 1215 DESCRIPTION 1216 "The number of times the remote peer has transitioned 1217 into the established state since the last restart of this 1218 LS." 1219 ::= { tripPeerStatisticsEntry 5 } 1221 tripPeerFsmEstablishedTime OBJECT-TYPE 1222 SYNTAX DateAndTime 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "Indicates the time and date that this remote peer entered 1227 the 'established' state." 1228 ::= { tripPeerStatisticsEntry 6 } 1230 tripPeerInUpdateElapsedTime OBJECT-TYPE 1231 SYNTAX TimeInterval 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "Elapsed time in hundredths of seconds since the last 1236 TRIP update message was received from this remote peer." 1237 ::= { tripPeerStatisticsEntry 7 } 1239 tripPeerStateChangeTime OBJECT-TYPE 1240 SYNTAX TimeStamp 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "The value of sysUpTime when the last state change of 1245 tripPeerState took place." 1246 ::= { tripPeerStatisticsEntry 8 } 1248 Zinman/Walker/Jiang 24 1249 -- TRIP Received Route Table. This table contains 1250 -- all routes from all sources. Each entry consists 1251 -- of a route and its associated path attributes. 1253 tripRouteTable OBJECT-TYPE 1254 SYNTAX SEQUENCE OF TripRouteEntry 1255 MAX-ACCESS not-accessible 1256 STATUS current 1257 DESCRIPTION 1258 "The TRIP route table containing information about 1259 reachable routes that are to be added to service by the 1260 receiving LS. The objects in this table are volatile 1261 and are refreshed when this LS rediscovers its route 1262 table." 1263 ::= { tripMIBObjects 6 } 1265 tripRouteEntry OBJECT-TYPE 1266 SYNTAX TripRouteEntry 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "Information about a route to a called destination." 1271 INDEX { applIndex, 1272 tripRouteAppProtocol, 1273 tripRouteAddressFamily, 1274 tripRouteAddress, 1275 tripRoutePeer 1276 } 1277 ::= { tripRouteTable 1 } 1279 TripRouteEntry ::= SEQUENCE { 1280 tripRouteAppProtocol TripAppProtocol, 1281 tripRouteAddressFamily TripAddressFamily, 1282 tripRouteAddress OCTET STRING, 1283 tripRoutePeer TripId, 1284 tripRouteTRIBMask BITS, 1285 tripRouteAddressSequenceNumber Integer32, 1286 tripRouteAddressOriginatorId TripId, 1287 tripRouteNextHopServerIAddrType InetAddressType, 1288 tripRouteNextHopServer InetAddress, 1289 tripRouteNextHopServerPort InetPortNumber, 1290 tripRouteNextHopServerItad TripItad, 1291 tripRouteMultiExitDisc Unsigned32, 1292 tripRouteLocalPref Unsigned32, 1293 tripRouteAdvertisementPath OCTET STRING, 1294 tripRouteRoutedPath OCTET STRING, 1295 tripRouteAtomicAggregate TruthValue, 1296 tripRouteUnknown OCTET STRING, 1297 tripRouteWithdrawn TruthValue, 1298 tripRouteConverted TruthValue, 1299 tripRouteReceivedTime TimeStamp 1301 Zinman/Walker/Jiang 25 1302 } 1304 tripRouteAppProtocol OBJECT-TYPE 1305 SYNTAX TripAppProtocol 1306 MAX-ACCESS not-accessible 1307 STATUS current 1308 DESCRIPTION 1309 "The protocol for which this entry of the routing table 1310 is maintained." 1311 ::= { tripRouteEntry 1 } 1313 tripRouteAddressFamily OBJECT-TYPE 1314 SYNTAX TripAddressFamily 1315 MAX-ACCESS not-accessible 1316 STATUS current 1317 DESCRIPTION 1318 "Specifies the type of address for the destination 1319 route." 1320 ::= { tripRouteEntry 2 } 1322 tripRouteAddress OBJECT-TYPE 1323 SYNTAX OCTET STRING (SIZE(1..105)) 1324 MAX-ACCESS not-accessible 1325 STATUS current 1326 DESCRIPTION 1327 "This is the address (prefix) of the family type given 1328 by Address Family of the destination. It is the prefix 1329 of addresses reachable from this gateway via the next 1330 hop server. The size value of 105 has been assigned due 1331 to the sub identifier of object types length limitation 1332 as defined in SMIv2." 1333 REFERENCE 1334 "RFC 3219, section 5.1.1.1." 1335 ::= { tripRouteEntry 3 } 1337 tripRoutePeer OBJECT-TYPE 1338 SYNTAX TripId 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "The identifier of the peer where the route information 1343 was learned." 1344 ::= { tripRouteEntry 4 } 1346 tripRouteTRIBMask OBJECT-TYPE 1347 SYNTAX BITS { 1348 adjTribIns(0), 1349 extTrib(1), 1350 locTrib(2), 1351 adjTribOut(3) 1352 } 1353 MAX-ACCESS read-only 1355 Zinman/Walker/Jiang 26 1356 STATUS current 1357 DESCRIPTION 1358 "Indicates which Telephony Routing Information Base (TRIB) 1359 this entry belongs to. This is 1360 a bit-map of possible types. If the bit has a value of 1361 1, then the entry is a member of the corresponding TRIB 1362 type. If the bit has a value of 0 then the entry is not 1363 a member of the TRIP type. The various bit positions 1364 are: 1366 0 adjTribIns The entry is of type adj-TRIBs-ins, 1367 stores routing information that has 1368 been learned from inbound UPDATE 1369 messages. 1370 1 extTrib The entry is of type ext-TRIB, the 1371 best route for a given destination. 1372 2 locTrib The entry is of type loc-TRIB contains 1373 the local TRIP routing information 1374 that the LS has selected. 1375 3 adjTribOut The entry is of type adj-TRIBs-out, 1376 stores the information that the local 1377 LS has selected for advertisement to 1378 its external peers." 1379 REFERENCE 1380 "RFC 3291, section 3.5." 1381 ::= { tripRouteEntry 5 } 1383 tripRouteAddressSequenceNumber OBJECT-TYPE 1384 SYNTAX Integer32 (1..2147483647) 1385 MAX-ACCESS read-only 1386 STATUS current 1387 DESCRIPTION 1388 "Indicates the version of the destination route 1389 originated by the LS identified by 1390 tripRouteAddressOriginatorId intra-domain attribute." 1391 ::= { tripRouteEntry 6 } 1393 tripRouteAddressOriginatorId OBJECT-TYPE 1394 SYNTAX TripId 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "This is an intra-domain attribute indicating the 1399 internal LS that originated the route into the ITAD." 1400 ::= { tripRouteEntry 7 } 1402 tripRouteNextHopServerIAddrType OBJECT-TYPE 1403 SYNTAX InetAddressType 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The type of Inet Address of the 1409 Zinman/Walker/Jiang 27 1410 tripRouteNextHopServer." 1411 REFERENCE 1412 "RFC 3291, section 3." 1413 ::= { tripRouteEntry 8 } 1415 tripRouteNextHopServer OBJECT-TYPE 1416 SYNTAX InetAddress 1417 MAX-ACCESS read-only 1418 STATUS current 1419 DESCRIPTION 1420 "Indicates the next hop that messages of a given 1421 protocol destined for tripRouteAddress SHOULD 1422 be sent to." 1423 ::= { tripRouteEntry 9 } 1425 tripRouteNextHopServerPort OBJECT-TYPE 1426 SYNTAX InetPortNumber 1427 MAX-ACCESS read-only 1428 STATUS current 1429 DESCRIPTION 1430 "The port of the next hop server that this route 1431 will use." 1432 ::= { tripRouteEntry 10 } 1434 tripRouteNextHopServerItad OBJECT-TYPE 1435 SYNTAX TripItad 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "Indicates the domain of the next hop." 1440 ::= { tripRouteEntry 11 } 1442 tripRouteMultiExitDisc OBJECT-TYPE 1443 SYNTAX Unsigned32 (0..4294967295) 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "The Multiple Exit Discriminator allows an LS to 1448 discriminate between, and indicate preference for, 1449 otherwise similar routes to a neighbouring domain. 1450 A higher value represents a more preferred routing 1451 object." 1452 REFERENCE 1453 "RFC 3219, section 5.8" 1454 ::= { tripRouteEntry 12 } 1456 tripRouteLocalPref OBJECT-TYPE 1457 SYNTAX Unsigned32 (0..4294967295) 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "Indicated the local LS's degree of preference for an 1463 Zinman/Walker/Jiang 28 1464 advertised route destination." 1465 REFERENCE 1466 "RFC 3219, section 4.3.4.7" 1467 ::= { tripRouteEntry 13 } 1469 tripRouteAdvertisementPath OBJECT-TYPE 1470 SYNTAX OCTET STRING (SIZE(4..252)) 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "Identifies the sequence of domains through which this 1475 advertisement has passed. 1477 This object is probably best represented as sequence of 1478 TripItads. For SMI compatibility, though, it is 1479 represented as an OCTET STRING. This object is a sequence 1480 of ITADs where each set of 4 octets corresponds to a TRIP 1481 ITAD in network byte order." 1482 REFERENCE 1483 "RFC 3219, section 4.3.4.4" 1484 ::= { tripRouteEntry 14 } 1486 tripRouteRoutedPath OBJECT-TYPE 1487 SYNTAX OCTET STRING (SIZE(4..252)) 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "Identifies the ITADs through which messages sent using 1492 this route would pass. These are a subset of 1493 tripRouteAdvertisementPath. 1495 This object is probably best represented as sequence of 1496 TripItads. For SMI compatibility, though, it is 1497 represented as OCTET STRING. This object is a sequence 1498 of ITADs where each set of 4 octets corresponds to a TRIP 1499 ITAD in network byte order." 1500 REFERENCE 1501 "RFC 3219, section 4.3.4.5" 1502 ::= { tripRouteEntry 15 } 1504 tripRouteAtomicAggregate OBJECT-TYPE 1505 SYNTAX TruthValue 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "Indicates that a route MAY traverse domains not listed 1510 in tripRouteRoutedPath. If an LS selects the less 1511 specific route from a set of overlapping routes, then 1512 this value returns TRUE." 1513 REFERENCE 1514 "RFC 3219, section 4.3.4.6" 1515 ::= { tripRouteEntry 16 } 1517 Zinman/Walker/Jiang 29 1518 tripRouteUnknown OBJECT-TYPE 1519 SYNTAX OCTET STRING (SIZE(0..255)) 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "One or more attributes not understood and dropped by 1524 this location server." 1525 REFERENCE 1526 "RFC 3219, section 4.3.2.3" 1527 ::= { tripRouteEntry 17 } 1529 tripRouteWithdrawn OBJECT-TYPE 1530 SYNTAX TruthValue 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "Indicates if this route is to be removed from service 1535 by the receiving location server." 1536 ::= { tripRouteEntry 18 } 1538 tripRouteConverted OBJECT-TYPE 1539 SYNTAX TruthValue 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "Indicates if this route has been converted to a 1544 different application protocol than it had originally." 1545 ::= { tripRouteEntry 19 } 1547 tripRouteReceivedTime OBJECT-TYPE 1548 SYNTAX TimeStamp 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "The value of sysUpTime when this route was received." 1553 ::= { tripRouteEntry 20 } 1555 -- 1556 -- TRIP Received Route Community Table. 1557 -- 1559 tripRouteCommunityTable OBJECT-TYPE 1560 SYNTAX SEQUENCE OF TripRouteCommunityEntry 1561 MAX-ACCESS not-accessible 1562 STATUS current 1563 DESCRIPTION 1564 "A table containing a list of TRIP communities associated 1565 with a route. Each instance of tripRouteTypeEntry that has 1566 the tripRouteTypePeer object set to remote(2) has an 1567 instance in the tripRouteTable as a parent. The objects 1568 in this table are volatile and are refreshed after a 1570 Zinman/Walker/Jiang 30 1571 reboot." 1572 REFERENCE 1573 "RFC 3219, section 5.9." 1574 ::= { tripMIBObjects 7 } 1576 tripRouteCommunityEntry OBJECT-TYPE 1577 SYNTAX TripRouteCommunityEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "Information about communities associated with a route. 1582 An entry with a tripRouteAddress of 00 and a 1583 tripRoutePeer of 0 refers to the local LS." 1584 INDEX { applIndex, 1585 tripRouteAppProtocol, 1586 tripRouteAddressFamily, 1587 tripRouteAddress, 1588 tripRoutePeer, 1589 tripRouteCommunityId 1590 } 1591 ::= { tripRouteCommunityTable 1 } 1593 TripRouteCommunityEntry ::= SEQUENCE { 1594 tripRouteCommunityId TripCommunityId, 1595 tripRouteCommunityItad TripItad 1596 } 1598 tripRouteCommunityId OBJECT-TYPE 1599 SYNTAX TripCommunityId 1600 MAX-ACCESS not-accessible 1601 STATUS current 1602 DESCRIPTION 1603 "The community identifier." 1604 ::= { tripRouteCommunityEntry 1 } 1606 tripRouteCommunityItad OBJECT-TYPE 1607 SYNTAX TripItad 1608 MAX-ACCESS read-only 1609 STATUS current 1610 DESCRIPTION 1611 "The ITAD associated with this community." 1612 ::= { tripRouteCommunityEntry 2 } 1614 -- 1615 -- tripItadTopologyTable 1616 -- 1618 tripItadTopologyTable OBJECT-TYPE 1619 SYNTAX SEQUENCE OF TripItadTopologyEntry 1620 MAX-ACCESS not-accessible 1621 STATUS current 1622 DESCRIPTION 1624 Zinman/Walker/Jiang 31 1625 "The sequence of link connections between peers within an 1626 ITAD. The objects in this table are volatile and are 1627 refreshed after a reboot." 1628 ::= { tripMIBObjects 8 } 1630 tripItadTopologyEntry OBJECT-TYPE 1631 SYNTAX TripItadTopologyEntry 1632 MAX-ACCESS not-accessible 1633 STATUS current 1634 DESCRIPTION 1635 "Information about a peer of the LS identified by 1636 tripItadTopologyOrigId." 1637 INDEX { applIndex, tripItadTopologyOrigId } 1638 ::= { tripItadTopologyTable 1 } 1640 TripItadTopologyEntry ::= SEQUENCE { 1641 tripItadTopologyOrigId TripId, 1642 tripItadTopologySeqNum Unsigned32 1643 } 1645 tripItadTopologyOrigId OBJECT-TYPE 1646 SYNTAX TripId 1647 MAX-ACCESS not-accessible 1648 STATUS current 1649 DESCRIPTION 1650 "Indicates the internal LS that originated the ITAD 1651 topology information into the ITAD." 1652 ::= { tripItadTopologyEntry 1 } 1654 tripItadTopologySeqNum OBJECT-TYPE 1655 SYNTAX Unsigned32 (1..2147483647) 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "Indicates the version of the ITAD topology originated 1660 by the LS identified by tripItadTopologyOrigId." 1661 ::= { tripItadTopologyEntry 2 } 1663 -- 1664 -- tripItadTopologyIdTable 1665 -- 1667 tripItadTopologyIdTable OBJECT-TYPE 1668 SYNTAX SEQUENCE OF TripItadTopologyIdEntry 1669 MAX-ACCESS not-accessible 1670 STATUS current 1671 DESCRIPTION 1672 "The list of other LS's within the ITAD domain that the 1673 LS identified by tripItadTopologyOrigId is currently 1674 peering. Each instance of tripItadTopologyIdEntry has an 1675 instance in the tripItadTopologyTable as a parent. The 1676 objects in this table are volatile and are refreshed 1678 Zinman/Walker/Jiang 32 1679 after a reboot." 1680 ::= { tripMIBObjects 9 } 1682 tripItadTopologyIdEntry OBJECT-TYPE 1683 SYNTAX TripItadTopologyIdEntry 1684 MAX-ACCESS not-accessible 1685 STATUS current 1686 DESCRIPTION 1687 "Information about a peer to the LS identified by 1688 tripItadTopologyOrigId." 1689 INDEX { applIndex, 1690 tripItadTopologyOrigId, 1691 tripItadTopologyId } 1692 ::= { tripItadTopologyIdTable 1 } 1694 TripItadTopologyIdEntry ::= SEQUENCE { 1695 tripItadTopologyId TripId 1696 } 1698 tripItadTopologyId OBJECT-TYPE 1699 SYNTAX TripId 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "The index into this entry. Indicates the other location 1704 servers within the ITAD domain that this LS identified 1705 by tripItadTopologyOrigId is currently peering." 1706 ::= { tripItadTopologyIdEntry 1 } 1708 -- 1709 -- Notification objects 1710 -- 1712 tripNotifApplIndex OBJECT-TYPE 1713 SYNTAX Integer32 (1..2147483647) 1714 MAX-ACCESS accessible-for-notify 1715 STATUS current 1716 DESCRIPTION 1717 "This object contains the applIndex as described in 1718 RFC 2788. It is used to bind this notification with a 1719 specific instance of TRIP entity." 1720 ::= { tripMIBNotifObjects 1 } 1722 tripNotifPeerAddrInetType OBJECT-TYPE 1723 SYNTAX InetAddressType 1724 MAX-ACCESS accessible-for-notify 1725 STATUS current 1726 DESCRIPTION 1727 "The type of Inet Address of the tripNotifPeerAddr." 1728 REFERENCE 1729 "RFC 3291, section 3." 1730 ::= { tripMIBNotifObjects 2 } 1732 Zinman/Walker/Jiang 33 1733 tripNotifPeerAddr OBJECT-TYPE 1734 SYNTAX InetAddress 1735 MAX-ACCESS accessible-for-notify 1736 STATUS current 1737 DESCRIPTION 1738 "The IP address of this entry's TRIP peer LS. This object 1739 contains the value of tripPeerRemoteAddr." 1740 REFERENCE 1741 "RFC 3291, section 3." 1742 ::= { tripMIBNotifObjects 3 } 1744 tripNotifPeerErrCode OBJECT-TYPE 1745 SYNTAX INTEGER { 1746 messageHeader(1), 1747 openMessage(2), 1748 updateMessage(3), 1749 holdTimerExpired(4), 1750 finiteStateMachine(5), 1751 cease(6), 1752 tripNotification(7) 1753 } 1754 MAX-ACCESS accessible-for-notify 1755 STATUS current 1756 DESCRIPTION 1757 "Notification message of TRIP error. The meaning of this 1758 value is applicable to the following functions: 1760 messageHeader(1) 1761 - All errors detected while processing the TRIP message 1762 header. 1764 openMessage(2) 1765 - All errors detected while processing the OPEN message. 1767 updateMessage(3) 1768 - All errors detected while processing the UPDATE 1769 message. 1771 holdTimerExpired(4) 1772 - A notification generated when the hold timer expires. 1774 finiteStateMachine(5) 1775 - All errors detected by the TRIP Finite State Machine. 1777 cease(6) 1778 - Any fatal error condition that the rest of the values 1779 do not cover. 1781 tripNotification(7) 1782 - Any error encountered while sending a notification 1783 message." 1785 Zinman/Walker/Jiang 34 1786 ::= { tripMIBNotifObjects 4 } 1788 tripNotifPeerErrSubcode OBJECT-TYPE 1789 SYNTAX Integer32 (1..2147483647) 1790 MAX-ACCESS accessible-for-notify 1791 STATUS current 1792 DESCRIPTION 1793 "The sub error code associated with error code. The 1794 meaning of this value is dependent on the value of 1795 tripNotifPeerErrCode. 1797 Message Header (1) Error Subcodes: 1798 1 - Bad Message Length. 1799 2 - Bad Message Type. 1801 OPEN Message (2) Error Subcodes: 1802 1 - Unsupported Version Number. 1803 2 - Bad Peer ITAD. 1804 3 - Bad TRIP Identifier. 1805 4 - Unsupported Optional Parameter. 1806 5 - Unacceptable Hold Time. 1807 6 - Unsupported Capability. 1808 7 - Capability Mismatch. 1810 UPDATE Message (3) Error Subcodes: 1811 1 - Malformed Attribute List. 1812 2 - Unrecognized Well-known Attribute. 1813 3 - Missing Well-known Mandatory Attribute. 1814 4 - Attribute Flags Error. 1815 5 - Attribute Length Error. 1816 6 - Invalid Attribute." 1817 ::= { tripMIBNotifObjects 5 } 1819 -- 1820 -- Notifications 1821 -- 1822 tripConnectionEstablished NOTIFICATION-TYPE 1823 OBJECTS { tripNotifApplIndex, 1824 tripNotifPeerAddrInetType, 1825 tripNotifPeerAddr 1826 } 1827 STATUS current 1828 DESCRIPTION 1829 "The TRIP Connection Established event is generated when 1830 the TRIP finite state machine enters the ESTABLISHED 1831 state." 1832 ::= { tripMIBNotifications 1 } 1834 tripConnectionDropped NOTIFICATION-TYPE 1835 OBJECTS { tripNotifApplIndex, 1836 tripNotifPeerAddrInetType, 1837 tripNotifPeerAddr 1839 Zinman/Walker/Jiang 35 1840 } 1841 STATUS current 1842 DESCRIPTION 1843 "The TRIP Connection Dropped event is generated when the 1844 TRIP finite state machine leaves the ESTABLISHED state." 1845 ::= { tripMIBNotifications 2 } 1847 tripFSM NOTIFICATION-TYPE 1848 OBJECTS { tripNotifApplIndex, 1849 tripNotifPeerAddrInetType, 1850 tripNotifPeerAddr, 1851 tripNotifPeerErrCode, 1852 tripNotifPeerErrSubcode, 1853 tripPeerState 1854 } 1855 STATUS current 1856 DESCRIPTION 1857 "The trip FSM Event is generated when any error is 1858 detected by the TRIP Finite State Machine." 1859 ::= { tripMIBNotifications 3 } 1861 tripOpenMessageError NOTIFICATION-TYPE 1862 OBJECTS { tripNotifApplIndex, 1863 tripNotifPeerAddrInetType, 1864 tripNotifPeerAddr, 1865 tripNotifPeerErrCode, 1866 tripNotifPeerErrSubcode, 1867 tripPeerState 1868 } 1869 STATUS current 1870 DESCRIPTION 1871 "Errors detected while processing the OPEN message." 1872 ::= { tripMIBNotifications 4 } 1874 tripUpdateMessageError NOTIFICATION-TYPE 1875 OBJECTS { tripNotifApplIndex, 1876 tripNotifPeerAddrInetType, 1877 tripNotifPeerAddr, 1878 tripNotifPeerErrCode, 1879 tripNotifPeerErrSubcode, 1880 tripPeerState 1881 } 1882 STATUS current 1883 DESCRIPTION 1884 "Errors detected while processing the UPDATE message." 1885 ::= { tripMIBNotifications 5 } 1887 tripHoldTimerExpired NOTIFICATION-TYPE 1888 OBJECTS { tripNotifApplIndex, 1889 tripNotifPeerAddrInetType, 1890 tripNotifPeerAddr, 1891 tripNotifPeerErrCode, 1893 Zinman/Walker/Jiang 36 1894 tripNotifPeerErrSubcode, 1895 tripPeerState 1896 } 1897 STATUS current 1898 DESCRIPTION 1899 "The system does not receive successive messages within 1900 the period specified by the negotiated Hold Time." 1901 ::= { tripMIBNotifications 6 } 1903 tripConnectionCollision NOTIFICATION-TYPE 1904 OBJECTS { tripNotifApplIndex } 1905 STATUS current 1906 DESCRIPTION 1907 "A pair of LSs tried to simultaneously to establish a 1908 transport connection to each other." 1909 ::= { tripMIBNotifications 7 } 1911 tripCease NOTIFICATION-TYPE 1912 OBJECTS { tripNotifApplIndex, 1913 tripNotifPeerAddrInetType, 1914 tripNotifPeerAddr, 1915 tripNotifPeerErrCode, 1916 tripNotifPeerErrSubcode, 1917 tripPeerState 1918 } 1919 STATUS current 1920 DESCRIPTION 1921 "A TRIP peer MAY choose at any given time to close its TRIP 1922 connection by sending this notification message. However, 1923 the Cease notification message MUST NOT be used when a 1924 fatal error occurs." 1925 ::= { tripMIBNotifications 8 } 1927 tripNotificationErr NOTIFICATION-TYPE 1928 OBJECTS { tripNotifApplIndex } 1929 STATUS current 1930 DESCRIPTION 1931 "Generated if there is an error detected in a TRIP 1932 notification message sent with another cause. Note that 1933 the TRIP notification refered to in this object is not 1934 an SNMP notification, it is a specific message described 1935 in the TRIP specification." 1936 REFERENCE 1937 "RFC 3219, section 6.4." 1938 ::= { tripMIBNotifications 9 } 1940 -- 1941 -- Compliance Statements 1942 -- 1943 tripCompliance MODULE-COMPLIANCE 1944 STATUS current 1945 DESCRIPTION 1947 Zinman/Walker/Jiang 37 1948 "The compliance statement for TRIP entities." 1950 MODULE -- this module 1951 MANDATORY-GROUPS { tripConfigGroup, 1952 tripPeerTableConfigGroup, 1953 tripRouteGroup, 1954 tripItadTopologyGroup, 1955 tripPeerTableStatsGroup } 1957 GROUP tripNotificationGroup 1958 DESCRIPTION 1959 "This group is OPTIONAL. A TRIP entity can choose not to 1960 send any notifications. If this group is implemented, 1961 the tripNotifObjectGroup MUST also be implemented." 1963 GROUP tripNotifObjectGroup 1964 DESCRIPTION 1965 "This group is OPTIONAL. A TRIP entity can choose not to 1966 send any notifications. If this group is implemented, 1967 the tripNotificationGroup MUST also be implemented." 1969 MODULE NETWORK-SERVICES-MIB 1970 MANDATORY-GROUPS { applRFC2788Group } 1972 ::= { tripMIBCompliance 1 } 1974 -- 1975 -- Object and event conformance groups 1976 -- 1978 tripConfigGroup OBJECT-GROUP 1979 OBJECTS { 1980 tripCfgProtocolVersion, 1981 tripCfgItad, 1982 tripCfgIdentifier, 1983 tripCfgOperStatus, 1984 tripCfgAdminStatus, 1985 tripCfgAddrIAddrType, 1986 tripCfgAddr, 1987 tripCfgPort, 1988 tripCfgMinItadOriginationInterval, 1989 tripCfgMinRouteAdvertisementInterval, 1990 tripCfgMaxPurgeTime, 1991 tripCfgDisableTime, 1992 tripCfgSendReceiveMode, 1993 tripCfgStorage, 1994 tripSupportedCommunityItad, 1995 tripSupportedCommunityStorage, 1996 tripRouteTypePeer, 1997 tripSupportedCommunityRowStatus 1998 } 1999 STATUS current 2001 Zinman/Walker/Jiang 38 2002 DESCRIPTION 2003 "The global objects for configuring trip." 2004 ::= { tripMIBGroups 1 } 2006 tripPeerTableConfigGroup OBJECT-GROUP 2007 OBJECTS { 2008 tripPeerIdentifier, 2009 tripPeerState, 2010 tripPeerAdminStatus, 2011 tripPeerNegotiatedVersion, 2012 tripPeerSendReceiveMode, 2013 tripPeerRemoteItad, 2014 tripPeerConnectRetryInterval, 2015 tripPeerMaxRetryInterval, 2016 tripPeerHoldTime, 2017 tripPeerKeepAlive, 2018 tripPeerHoldTimeConfigured, 2019 tripPeerKeepAliveConfigured, 2020 tripPeerMaxPurgeTime, 2021 tripPeerDisableTime, 2022 tripPeerLearned, 2023 tripPeerStorage, 2024 tripPeerRowStatus 2025 } 2027 STATUS current 2028 DESCRIPTION 2029 "The global objects for configuring the TRIP peer 2030 table." 2031 ::= { tripMIBGroups 2 } 2033 tripPeerTableStatsGroup OBJECT-GROUP 2034 OBJECTS { 2035 tripPeerInUpdates, 2036 tripPeerOutUpdates, 2037 tripPeerInTotalMessages, 2038 tripPeerOutTotalMessages, 2039 tripPeerFsmEstablishedTransitions, 2040 tripPeerFsmEstablishedTime, 2041 tripPeerInUpdateElapsedTime, 2042 tripPeerStateChangeTime 2043 } 2044 STATUS current 2045 DESCRIPTION 2046 "The global statistics the TRIP peer table." 2047 ::= { tripMIBGroups 3 } 2049 tripRouteGroup OBJECT-GROUP 2050 OBJECTS { 2051 tripRouteTRIBMask, 2052 tripRouteAddressSequenceNumber, 2053 tripRouteAddressOriginatorId, 2055 Zinman/Walker/Jiang 39 2056 tripRouteNextHopServerIAddrType, 2057 tripRouteNextHopServer, 2058 tripRouteNextHopServerPort, 2059 tripRouteNextHopServerItad, 2060 tripRouteMultiExitDisc, 2061 tripRouteLocalPref, 2062 tripRouteAdvertisementPath, 2063 tripRouteRoutedPath, 2064 tripRouteAtomicAggregate, 2065 tripRouteUnknown, 2066 tripRouteWithdrawn, 2067 tripRouteConverted, 2068 tripRouteReceivedTime, 2069 tripRouteCommunityItad 2070 } 2072 STATUS current 2073 DESCRIPTION 2074 "The global objects for configuring route attribute." 2075 ::= { tripMIBGroups 4 } 2077 tripItadTopologyGroup OBJECT-GROUP 2078 OBJECTS { 2079 tripItadTopologySeqNum, 2080 tripItadTopologyId 2081 } 2082 STATUS current 2083 DESCRIPTION 2084 "The objects that define the TRIP ITAD topology." 2085 ::= { tripMIBGroups 5 } 2087 tripNotificationGroup NOTIFICATION-GROUP 2088 NOTIFICATIONS { 2089 tripConnectionEstablished, 2090 tripConnectionDropped, 2091 tripFSM, 2092 tripOpenMessageError, 2093 tripUpdateMessageError, 2094 tripHoldTimerExpired, 2095 tripConnectionCollision, 2096 tripCease, 2097 tripNotificationErr 2098 } 2099 STATUS current 2100 DESCRIPTION 2101 "A collection of notifications defined for TRIP." 2102 ::= { tripMIBGroups 6 } 2104 tripNotifObjectGroup OBJECT-GROUP 2105 OBJECTS { 2106 tripNotifApplIndex, 2107 tripNotifPeerAddrInetType, 2109 Zinman/Walker/Jiang 40 2110 tripNotifPeerAddr, 2111 tripNotifPeerErrCode, 2112 tripNotifPeerErrSubcode 2113 } 2114 STATUS current 2115 DESCRIPTION 2116 "The collection of objects that specify information for 2117 TRIP notifications." 2118 ::= { tripMIBGroups 7 } 2120 END 2122 7. Security Considerations 2124 The managed objects in this MIB module contain sensitive information 2125 since, collectively, they allow tracing and influencing of 2126 connections in TRIP devices and provide information of their 2127 connection characteristics. As such, improper manipulation of the 2128 objects represented by this MIB module MAY result in denial of 2129 service to a large number of availiable routes. 2131 There are a number of management objects defined in this MIB module 2132 that have a MAX-ACCESS clause of read-write and/or read-create. 2133 Such objects MAY be considered sensitive or vulnerable in some 2134 network environments. The support for SET operations in a non- 2135 secure environment without proper protection can have a negative 2136 effect on network operations. These objects include: 2138 tripCfgItad: 2139 Improper setting of tripCfgItad value can make all peer 2140 connections drop and not be re-established. 2142 tripCfgAdminStatus: 2143 Improper setting of tripCfgAdminStatus from up to down will 2144 cause the TRIP Location Server stop processing TRIP messages. 2146 tripCfgPort: 2147 Improper setting of tripCfgPort can cause the failure of a peer 2148 establishing a connection. 2150 tripCfgMinItadOriginationInterval, 2151 tripCfgMinRouteAdvertisementInterval: 2152 Improper configuration of these values MAY adversely affect 2153 local and global convergence of the routes advertised by this 2154 TRIP Location Server. 2156 tripPeerAdminStatus: 2157 Improper setting of tripPeerAdminStatus from up to down can 2158 cause significant disruption of the connectivity to the 2159 destination via the applicable remote TRIP Location Server 2160 peer. 2162 Zinman/Walker/Jiang 41 2163 tripPeerConnectRetryInterval,tripPeerMaxRetryInterval: 2164 Improper configuration of these values can cause connections to 2165 be disrupted for extremely long time periods when otherwise 2166 they would be restored in a relatively short period of time. 2168 tripPeerHoldTimeConfigured, tripPeerKeepAliveConfigured: 2169 Improper configuration of these value can make TRIP peer 2170 sessions more fragile and less resilient to denial of service 2171 attacks. 2173 There are a number of managed objects in this MIB module that 2174 contain sensitive information regarding the operation of a network. 2175 For example, a TRIP Location Server peer's local and remote 2176 addresses might be sensitive for ISPs who want to keep interface 2177 addresses on TRIP Location Server confidential so as to prevent TRIP 2178 Location Server addresses used for a denial of service attack or 2179 address spoofing. 2181 Therefore, it is thus important to control even GET access to these 2182 objects and possibly to even encrypt the values of these object when 2183 sending them over the network via SNMP. Not all versions of SNMP 2184 provide features for such a secure environment. 2186 SNMPv1 by itself is not a secure environment. Even if the network 2187 itself is secure (for example by using IPSec), even then, there is 2188 no control as to who on the secure network is allowed to access and 2189 GET/SET (read/change/create/delete) the objects in this MIB module. 2191 It is RECOMMENDED that the implementers consider the security 2192 features as provided by the SNMPv3 framework (see [RFC3410], section 2193 8), including full support for the SNMPv3 cryptographic mechanisms 2194 (for authentication and privacy). 2196 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2197 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2198 enable cryptographic security. It is then a customer/operator 2199 responsibility to ensure that the SNMP entity giving access to an 2200 instance of this MIB module is properly configured to give access to 2201 the objects only to those principals (users) that have legitimate 2202 rights to indeed GET or SET (change/create/delete) them. 2204 8. Full Copyright Statement 2206 Copyright (C) The Internet Society (2002). All Rights Reserved. 2207 This document and translations of it MAY be copied and furnished to 2208 others, and derivative works that comment on or otherwise explain it 2209 or assist in its implementation MAY be prepared, copied, published 2210 and distributed, in whole or in part, without restriction of any 2211 kind, provided that the above copyright notice and this paragraph 2212 are included on all such copies and derivative works. However, this 2213 document itself MAY not be modified in any way, such as by removing 2214 the copyright notice or references to the Internet Society or other 2216 Zinman/Walker/Jiang 42 2217 Internet organizations, except as needed for the purpose of 2218 developing Internet standards in which case the procedures for 2219 copyrights defined in the Internet Standards process MUST be 2220 followed, or as REQUIRED to translate it into languages other than 2221 English. 2223 The limited permissions granted above are perpetual and will not be 2224 revoked by the Internet Society or its successors or assigns. 2226 This document and the information contained herein is provided on an 2227 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2228 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2229 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2230 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2231 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2233 9. Normative References 2235 [RFC3219] Rosenberg, J., Salama, H. and Squire, M., "Telephony 2236 Routing over IP (TRIP)", RFC 3219 January 2002. 2238 [RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, 2239 J., "Textual Conventions for Internet Network 2240 Addresses", RFC 3291, May 2002. 2242 [RFC1657] Willis, S., Burruss, J., and Chu, J., "Definitions of 2243 Managed Objects for the Fourth Version of the Border 2244 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July 2245 1994. 2247 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2248 Rose, M. and S. Waldbusser, "Structure of Management 2249 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2250 1999. 2252 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2253 Rose, M. and S. Waldbusser, "Textual Conventions for 2254 SMIv2", STD 58, RFC 2579, April 1999. 2256 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2257 Rose, M. and S. Waldbusser, "Conformance Statements for 2258 SMIv2", STD 58, RFC 2580, April 1999. 2260 [RFC2026] Bradner, S., "The Internet Standards Process _ Revision 2261 3", BCP 9, RFC 2026, October 1996. 2263 10. Informative References 2265 [RFC1771] Rekhter, Y. and Li, T., "Border Gateway Protocol 4 2266 (BGP-4)", RFC 1771, March 1995. 2268 Zinman/Walker/Jiang 43 2270 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2271 "Introduction and Applicability Statements for Internet- 2272 Standard Management Framework", RFC 3410, December 2002. 2274 11. Intellectual Property Notice 2276 The IETF takes no position regarding the validity or scope of any 2277 intellectual property or other rights that might be claimed to 2278 pertain to the implementation or use of the technology described in 2279 this document or the extent to which any license under such rights 2280 might or might not be available; neither does it represent that it 2281 has made any effort to identify any such rights. Information on the 2282 IETF's procedures with respect to rights in standards-track and 2283 standards-related documentation can be found in BCP 11. Copies of 2284 claims of rights made available for publication and any assurances 2285 of licenses to be made available, or the result of an attempt made 2286 to obtain a general license or permission for the use of such 2287 proprietary rights by implementers or users of this specification 2288 can be obtained from the IETF Secretariat. 2290 The IETF invites any interested party to bring to its attention any 2291 copyrights, patents or patent applications, or other proprietary 2292 rights which MAY cover technology that MAY be REQUIRED to practice 2293 this standard. Please address the information to the IETF Executive 2294 Director. 2296 The IETF has been notified of intellectual property rights claimed 2297 in regard to some or all of the specification contained in this 2298 document. For more information consult the online list of claimed 2299 rights. 2301 12. Acknowledgments 2303 The authors wish to thank Bert Wijnen, Dan Romascanu, and Jonathan 2304 Rosenberg for their insightful comments and suggestions. 2306 Thanks to Kevin Lingle for his invaluable comments, help with MIB 2307 things and great ideas. 2309 13. Author's Addresses 2311 David Zinman 2312 Editor 2313 312 Adelaide St. West Suite 700 2314 Toronto ON, M5V 1R2 2315 Canada 2316 phone: +1 416 348 1656 2317 email: dzinman@somanetworks.com 2319 Dave Walker 2321 Zinman/Walker/Jiang 44 2322 SS8 Networks, Inc. 2323 495 March Road, Suite #500 2324 Ottawa, ON K2K 3G1 2325 Canada 2326 Phone: +1 613 592 2100 2327 Email: drwalker@ss8.com 2329 Jianping Jiang 2330 SS8 Networks, Inc. 2331 495 March Road, Suite #500 2332 Ottawa, ON K2K 3G1 2333 Canada 2334 Phone: +1 613 592 2100 2335 Email: jianping@ss8.com 2337 14. Working Group 2339 IP Telephony (iptel) Working Group 2340 ================================== 2342 Mailing list: iptel@lists.bell-labs.com 2344 Chair: 2345 Jonathan Rosenberg 2347 Transport Area Directors: 2348 Scott Bradner 2349 Allison Mankin mankin@east.isi.edu 2351 Zinman/Walker/Jiang 45