idnits 2.17.1 draft-ietf-iptel-trip-mib-04.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: ---------------------------------------------------------------------------- == 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- 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) == Unused Reference: 'RFC3291' is defined on line 2101, 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) ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) -- Obsolete informational reference (is this intentional?): RFC 1771 (Obsoleted by RFC 4271) -- Obsolete informational reference (is this intentional?): RFC 2571 (Obsoleted by RFC 3411) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 7 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-04.txt Consultant 4 Expires: March 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 (10/10/2002). All Rights 36 Reserved." 38 Abstract 40 This memo defines a portion of the MIB (Management Information Base) 41 for use with network management protocols in the Internet community. 42 In particular, it describes a set of managed objects that are used 43 to manage for TRIP (Telephony Routing over IP) devices. 45 Zinman/Walker/Jiang 1 46 Table of Contents 48 Status of this Memo................................................1 49 Copyright Notice...................................................1 50 Abstract...........................................................1 51 1. Introduction..................................................3 52 2. Conventions used in this document.............................3 53 3. The SNMP Management Framework.................................3 54 4. Overview......................................................4 55 5. Structure of TRIP MIB.........................................4 56 5.1 Textual Conventions.........................................5 57 6. Definitions...................................................5 58 6.1 TRIP Textual Conventions....................................5 59 6.2 TRIP MIB....................................................7 60 7. Security Considerations......................................39 61 8. Full Copyright Statement.....................................40 62 9. Normative References.........................................40 63 10. Informative References.......................................41 64 11. Intellectual Property Notice.................................42 65 12. Acknowledgments..............................................43 66 13. Author's Addresses...........................................43 67 14. Working Group................................................43 69 Zinman/Walker/Jiang 2 70 1. Introduction 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols in the Internet community. 74 In particular, it describes a set of managed objects that are used 75 to schedule management operations periodically or at specified dates 76 and times. Since TRIP [RFC3219] is modeled after the Border Gateway 77 Protocol (BGP-4) [RFC1771], the managed objects for TRIP are also 78 modeled after RFC1657 - Definitions of Managed Objects for the 79 Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 80 [RFC1657]. 82 2. Conventions used in this document 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 86 this document are to be interpreted as described in BCP-0014 87 [BCP0014]. 89 3. The SNMP Management Framework 91 The SNMP Management Framework presently consists of five major 92 components: 94 o An overall architecture, described in RFC 2571 [RFC2571]. 96 o Mechanisms for describing and naming objects and events for the 97 purpose of management. The first version of this Structure of 98 Management Information (SMI) is called SMIv1 and described in 99 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 100 1215 [RFC1215]. The second version, called SMIv2, is described 101 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 102 STD 58, RFC 2580 [RFC2580]. 104 o Message protocols for transferring management information. The 105 first version of the SNMP message protocol is called SNMPv1 and 106 described in STD 15, RFC 1157 [RFC1157]. A second version of 107 the SNMP message protocol, which is not an Internet standards 108 track protocol, is called SNMPv2c and described in RFC 1901 109 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 110 message protocol is called SNMPv3 and described in RFC 1906 111 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 113 o Protocol operations for accessing management information. The 114 first set of protocol operations and associated PDU formats is 115 described in STD 15, RFC 1157 [RFC1157]. A second set of 116 protocol operations and associated PDU formats is described in 117 RFC 1905 [RFC1905]. 119 o A set of fundamental applications described in RFC 2573 120 [RFC2573] and the view-based access control mechanism described 122 Zinman/Walker/Jiang 3 123 in RFC 2575 [RFC2575]. 125 A more detailed introduction to the current SNMP Management 126 Framework can be found in RFC 2570 [RFC2570]. 128 Managed objects are accessed via a virtual information store, termed 129 the Management Information Base or MIB. Objects in the MIB are 130 defined using the mechanisms defined in the SMI. 132 This memo specifies a MIB module that is compliant to the SMIv2. A 133 MIB conforming to the SMIv1 can be produced through the appropriate 134 translations. The resulting translated MIB must be semantically 135 equivalent, except where objects or events are omitted because no 136 translation is possible (use of Counter64). Some machine readable 137 information in SMIv2 will be converted into textual descriptions in 138 SMIv1 during the translation process. However, this loss of machine 139 readable information is not considered to change the semantics of 140 the MIB. 142 4. Overview 144 Telephony Routing over IP (TRIP) [RFC3219] is an inter-domain 145 application-layer control protocol that exchanges information 146 between TRIP location servers to provide efficient IP telephony 147 routing. This MIB provides managed objects for TRIP devices defined 148 in Telephony Routing over IP [RFC3219]. 150 5. Structure of TRIP MIB 152 This MIB utilizes the framework described in RFC 2788 [RFC2788] for 153 management of multiple instances of TRIP from a single entity. The 154 Network Services Monitoring MIB applTable will be populated with 155 entries corresponding to each TRIP LS in the system. Each TRIP LS 156 will then have an applIndex associated with it. The value assigned 157 to applIndex will represent the distinct instance of TRIP. 159 The TRIP MIB contains the following groups of objects: 160 o The tripConfigGroup contains the common configuration objects 161 applicable to all TRIP applications referenced by the applIndex. 162 o The tripPeerTableConfigGroup contains the configuration objects 163 applicable to all TRIP peers of the LS referened by the applIndex. 164 o The tripRouteGroup contains the configuration objects related to 165 the routes of all TRIBs of this LS. 166 o The tripItadTopologyGroup contains information about the topology 167 of the TRIP ITADs concerning this LS. 168 o The tripPeerTableStatsGroup contains the statistical objects 169 applicable to all TRIP peers of the LS referened by the applIndex. 170 o The tripNotificationGroup contains notifications that the TRIP 171 application can generate. 172 o The tripNotifObjectGroup contains the objects needed by one or 173 more of the notifications. 175 Zinman/Walker/Jiang 4 176 5.1 Textual Conventions 178 The data types TripItad and TripId are used as textual conventions 179 in this document. A TRIP ITAD is described in [RFC3219]. A TRIP ID 180 is used as a distinct identifier for a TRIP LS. A TripAppProtocol 181 is used to identify an application protocol. A TripAddressFamily is 182 used to define an address family. TripCommunityId is used as a 183 distinct identifier for a TRIP community. TripProtocolVersion 184 depicts the version number of the TRIP protocol. 185 TripSendReceiveMode describes the operational mode of the TRIP 186 application. 188 6. Definitions 190 6.1 TRIP Textual Conventions 192 TRIP-TC DEFINITIONS ::= BEGIN 194 IMPORTS 195 MODULE-IDENTITY, 196 Unsigned32, 197 Integer32, 198 mib-2 199 FROM SNMPv2-SMI 201 TEXTUAL-CONVENTION 202 FROM SNMPv2-TC; 204 tripTC MODULE-IDENTITY 205 LAST-UPDATED "200210100000Z" -- Oct 10, 2002 206 ORGANIZATION "IETF IPTel Working Group. 207 Mailing list: iptel@lists.bell-labs.com" 208 CONTACT-INFO 209 "Co-editor David Zinman 210 Consultant 211 email: dzinman@sympatico.ca 212 phone: +1 613 791 2841 214 Co-editor Dave Walker 215 SS8 Networks, Inc. 216 postal: 495 March Road, Suite #500 217 Ottawa, ON, K2K 3G1 Canada 218 email: drwalker@ss8.com 219 phone: +1 613 592 2100 221 Co-editor Jianping Jiang 222 SS8 Networks, Inc. 223 postal: 495 March Road, Suite #500 224 Ottawa, ON, K2K 3G1 Canada 225 email: jianping@ss8.com 226 phone: +1 613 592 2100 227 " 229 Zinman/Walker/Jiang 5 230 DESCRIPTION 231 "Initial version of TRIP (Telephony Routing Over IP) 232 MIB Textual Conventions module used by other 233 TRIP-related MIB Modules." 234 ::= { mib-2 xxxx } -- to be assigned by IANA 236 -- 237 -- Textual Conventions 238 -- 239 TripItad ::= TEXTUAL-CONVENTION 240 STATUS current 241 DESCRIPTION 242 "The values for identifying the IP Telephony 243 Administrative Domain (ITAD)." 244 SYNTAX Unsigned32 (0..4294967295) 246 TripId ::= TEXTUAL-CONVENTION 247 STATUS current 248 DESCRIPTION 249 "The TRIP Identifier uniquely identifies a LS within its 250 ITAD. It is a 4 octet unsigned integer that may, but not 251 necessarily, represent the IPv4 address of a Location 252 Server (LS). For an IPv6 network, TripId will not represent 253 the IPv6 address." 254 SYNTAX Unsigned32 (0..4294967295) 256 TripAddressFamily ::= TEXTUAL-CONVENTION 257 STATUS current 258 DESCRIPTION 259 "A type of address for a TRIP route. Address families 260 defined within this MIB module are: 262 Code Address Family 263 1 Decimal Routing Numbers 264 2 PentaDecimal Routing Numbers 265 3 E.164 Numbers" 267 SYNTAX INTEGER { decimal(1), pentadecimal(2), e164(3) } 269 TripAppProtocol ::= TEXTUAL-CONVENTION 270 STATUS current 271 DESCRIPTION 272 "The application protocol used for communication with TRIP 273 Location Servers (LS). Protocols defined in this document 274 are: 276 Code Protocol 277 1 SIP 278 2 H.323-H.225.0-Q.931 279 3 H.323-H.225.0-RAS 280 4 H.323-H.225.0-Annex-G" 282 Zinman/Walker/Jiang 6 283 SYNTAX INTEGER { sip(1), q931(2), ras(3), annexG(4) } 285 TripCommunityId ::= TEXTUAL-CONVENTION 286 STATUS current 287 DESCRIPTION 288 "The range of legal values for a TRIP Community Identifier." 289 SYNTAX Unsigned32 (0..4294967295) 291 TripProtocolVersion ::= TEXTUAL-CONVENTION 292 STATUS current 293 DESCRIPTION 294 "The version number of the TRIP protocol." 295 SYNTAX Integer32 (1..255) 297 TripSendReceiveMode ::= TEXTUAL-CONVENTION 298 STATUS current 299 DESCRIPTION 300 "The operational mode of the TRIP application." 301 SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) } 303 END 305 6.2 TRIP MIB 307 TRIP-MIB DEFINITIONS ::= BEGIN 309 IMPORTS 310 MODULE-IDENTITY, 311 OBJECT-TYPE, 312 NOTIFICATION-TYPE, 313 Unsigned32, 314 Integer32, 315 Counter32, 316 mib-2 317 FROM SNMPv2-SMI 319 DateAndTime, 320 TimeInterval, 321 TruthValue, 322 TimeStamp, 323 StorageType, 324 RowStatus 325 FROM SNMPv2-TC 327 OBJECT-GROUP, 328 MODULE-COMPLIANCE, 329 NOTIFICATION-GROUP 330 FROM SNMPv2-CONF 332 InetAddressType, 333 InetAddress, 335 Zinman/Walker/Jiang 7 336 InetPortNumber 337 FROM INET-ADDRESS-MIB 339 applIndex 340 FROM NETWORK-SERVICES-MIB 342 TripItad, 343 TripId, 344 TripAppProtocol, 345 TripAddressFamily, 346 TripCommunityId, 347 TripProtocolVersion, 348 TripSendReceiveMode 349 FROM TRIP-TC; 351 tripMIB MODULE-IDENTITY 352 LAST-UPDATED "200210100000Z" -- Oct 10, 2002 353 ORGANIZATION "IETF IPTel Working Group. 354 Mailing list: iptel@lists.bell-labs.com" 356 CONTACT-INFO 357 "Co-editor David Zinman 358 Consultant 359 email: dzinman@sympatico.ca 360 phone: +1 613 791 2841 362 Co-editor Dave Walker 363 SS8 Networks, Inc. 364 postal: 495 March Road, Suite #500 365 Ottawa, ON, K2K 3G1 Canada 366 email: drwalker@ss8.com 367 phone: +1 613 592 2100 369 Co-editor Jianping Jiang 370 SS8 Networks, Inc. 371 postal: 495 March Road, Suite #500 372 Ottawa, ON, K2K 3G1 Canada 373 email: jianping@ss8.com 374 phone: +1 613 592 2100 375 " 376 DESCRIPTION 377 "The MIB module describing Telephony Routing over IP (TRIP). 378 TRIP is a policy driven inter-administrative domain protocol 379 for advertising the reachability of telephony destinations 380 between location servers (LS), and for advertising attributes 381 of the routes to those destinations." 382 REVISION "200210100000Z" -- Oct 10, 2002 383 DESCRIPTION 384 "The initial version, Published as RFC xxxx." 385 ::= { mib-2 xxxx } -- to be assigned by IANA 387 Zinman/Walker/Jiang 8 388 tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 } 389 tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 } 390 tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 } 391 tripMIBNotifObjects OBJECT IDENTIFIER ::= { tripMIB 3 } 393 tripMIBCompliance OBJECT IDENTIFIER ::= 394 { tripMIBConformance 1 } 395 tripMIBGroups OBJECT IDENTIFIER ::= 396 { tripMIBConformance 2 } 398 -- 399 -- tripCfgTable 400 -- 401 tripCfgTable OBJECT-TYPE 402 SYNTAX SEQUENCE OF TripCfgEntry 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "This table contains the common configuration objects 407 applicable to all TRIP applications referenced by the 408 applIndex. Each row represents those objects for a 409 particular TRIP LS present in this system. The 410 instances of TRIP LS's are uniquely identified by the 411 applIndex. The objects in this table should be 412 nonVolatile and survive a reboot." 413 ::= { tripMIBObjects 1 } 415 tripCfgEntry OBJECT-TYPE 416 SYNTAX TripCfgEntry 417 MAX-ACCESS not-accessible 418 STATUS current 419 DESCRIPTION 420 "A row of common configuration." 421 INDEX { applIndex } 422 ::= { tripCfgTable 1 } 424 TripCfgEntry ::= 425 SEQUENCE { 426 tripCfgProtocolVersion TripProtocolVersion, 427 tripCfgItad TripItad, 428 tripCfgIdentifier TripId, 429 tripCfgOperStatus INTEGER, 430 tripCfgAdminStatus INTEGER, 431 tripCfgAddrIAddrType InetAddressType, 432 tripCfgAddr InetAddress, 433 tripCfgPort InetPortNumber, 434 tripCfgMinItadOriginationInterval Integer32, 435 tripCfgMinRouteAdvertisementInterval Integer32, 436 tripCfgMaxPurgeTime Integer32, 437 tripCfgDisableTime Integer32, 438 tripCfgSendReceiveMode TripSendReceiveMode 439 } 441 Zinman/Walker/Jiang 9 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 as dictated by the TRIP specification[RFC3219]." 452 ::= { tripCfgEntry 1 } 454 tripCfgItad OBJECT-TYPE 455 SYNTAX TripItad 456 MAX-ACCESS read-write 457 STATUS current 458 DESCRIPTION 459 "The Local Internet Telephony Administrative domain." 460 ::= { tripCfgEntry 2 } 462 tripCfgIdentifier OBJECT-TYPE 463 SYNTAX TripId 464 MAX-ACCESS read-only 465 STATUS current 466 DESCRIPTION 467 "The object that identifies this TRIP Client." 468 ::= { tripCfgEntry 3 } 470 tripCfgAdminStatus OBJECT-TYPE 471 SYNTAX INTEGER { 472 up(1), 473 down(2) 474 } 475 MAX-ACCESS read-write 476 STATUS current 477 DESCRIPTION 478 "The desired TRIP state. 480 up(1) : Set the application to normal operation. 482 down(2): Set the application to a state where it will 483 not process TRIP messages." 484 ::= { tripCfgEntry 4 } 486 tripCfgOperStatus OBJECT-TYPE 487 SYNTAX INTEGER { 488 up(1), 489 down(2) 490 } 491 MAX-ACCESS read-only 492 STATUS current 494 Zinman/Walker/Jiang 10 495 DESCRIPTION 496 "The current operational state of the TRIP protocol. 498 up(1) : The application is operating normally, and 499 is processing (receiving and possibly 500 issuing) TRIP requests and responses. 502 down(2): The application is currently unable to 503 process TRIP messages due to a fault or if 504 TRIP is in an initialization state. 506 If tripAdminStatus is down(2) then tripOperStatus should 507 be down(2). If tripAdminStatus is changed to up(1) then 508 tripOperStatus should change to up(1) if there is no 509 fault that prevents the TRIP protocol from moving to the 510 up(1) state." 511 ::= { tripCfgEntry 5 } 513 tripCfgAddrIAddrType OBJECT-TYPE 514 SYNTAX InetAddressType 515 MAX-ACCESS read-only 516 STATUS current 517 DESCRIPTION 518 "The type of Inet Address of the tripAddr." 519 REFERENCE 520 "RFC 3291, section 3." 521 ::= { tripCfgEntry 6 } 523 tripCfgAddr OBJECT-TYPE 524 SYNTAX InetAddress 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "The IP address of the local LS that the peer connects 529 to." 530 REFERENCE 531 "RFC 3291, section 3." 532 ::= { tripCfgEntry 7 } 534 tripCfgPort OBJECT-TYPE 535 SYNTAX InetPortNumber 536 MAX-ACCESS read-write 537 STATUS current 538 DESCRIPTION 539 "The local tcp/udp port on the local LS that the peer 540 connects to." 541 ::= { tripCfgEntry 8 } 543 tripCfgMinItadOriginationInterval OBJECT-TYPE 544 SYNTAX Integer32 (1..2147483647) 545 UNITS "Seconds" 546 MAX-ACCESS read-write 548 Zinman/Walker/Jiang 11 549 STATUS current 550 DESCRIPTION 551 "The minimum amount of time that must elapse between 552 advertisement of update message that report changes 553 within the LS's own ITAD." 554 DEFVAL { 30 } 555 ::= { tripCfgEntry 9 } 557 tripCfgMinRouteAdvertisementInterval OBJECT-TYPE 558 SYNTAX Integer32 (1..2147483647) 559 UNITS "Seconds" 560 MAX-ACCESS read-write 561 STATUS current 562 DESCRIPTION 563 "Specifies minimal interval between successive 564 advertisements to a particular destination from an LS." 565 DEFVAL { 30 } 566 ::= { tripCfgEntry 10 } 568 tripCfgMaxPurgeTime OBJECT-TYPE 569 SYNTAX Integer32 (1..2147483647) 570 UNITS "Seconds" 571 MAX-ACCESS read-write 572 STATUS current 573 DESCRIPTION 574 "Indicate the interval that the LS must maintain routes 575 marked as withdrawn in its database." 576 DEFVAL { 10 } 577 ::= { tripCfgEntry 11 } 579 tripCfgDisableTime OBJECT-TYPE 580 SYNTAX Integer32 (1..2147483647) 581 UNITS "Seconds" 582 MAX-ACCESS read-write 583 STATUS current 584 DESCRIPTION 585 "Indicate the interval that the TRIP module of the 586 LS must be disabled while routes originated by this 587 location server with high sequence numbers can be 588 removed." 589 DEFVAL { 180 } 590 ::= { tripCfgEntry 12 } 592 tripCfgSendReceiveMode OBJECT-TYPE 593 SYNTAX TripSendReceiveMode 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "The operational mode of the trip entity running on this 598 system." 599 ::= { tripCfgEntry 13 } 601 Zinman/Walker/Jiang 12 602 -- 603 -- TripRouteTypeTable 604 -- 606 tripRouteTypeTable OBJECT-TYPE 607 SYNTAX SEQUENCE OF TripRouteTypeEntry 608 MAX-ACCESS not-accessible 609 STATUS current 610 DESCRIPTION 611 "The TRIP Route Type table contains one entry per 612 supported protocol - address family pair. This table 613 lists the route types supported in this peering session 614 by the transmitting LS. The objects in this table are 615 volatile and are refreshed after a reboot." 616 ::= { tripMIBObjects 2 } 618 tripRouteTypeEntry OBJECT-TYPE 619 SYNTAX TripRouteTypeEntry 620 MAX-ACCESS not-accessible 621 STATUS current 622 DESCRIPTION 623 "Entry containing information about the route type that 624 the TRIP entity supports." 625 INDEX { applIndex, 626 tripRouteTypeProtocolId, 627 tripRouteTypeAddrFamilyId } 628 ::= { tripRouteTypeTable 1 } 630 TripRouteTypeEntry ::= SEQUENCE { 631 tripRouteTypeProtocolId TripAppProtocol, 632 tripRouteTypeAddrFamilyId TripAddressFamily 633 } 635 tripRouteTypeProtocolId OBJECT-TYPE 636 SYNTAX TripAppProtocol 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "The object identifier of a protocol that this peer is 641 using. The size value of 116 has been assigned due to the 642 sub identifier of object types length limitation as 643 defined in SMIv2." 644 ::= { tripRouteTypeEntry 1 } 646 tripRouteTypeAddrFamilyId OBJECT-TYPE 647 SYNTAX TripAddressFamily 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "The object identifier of an address family that this 652 peer belongs to." 653 ::= { tripRouteTypeEntry 2 } 655 Zinman/Walker/Jiang 13 656 -- 657 -- tripSupportedCommunityTable 658 -- 660 tripSupportedCommunityTable OBJECT-TYPE 661 SYNTAX SEQUENCE OF TripSupportedCommunityEntry 662 MAX-ACCESS not-accessible 663 STATUS current 664 DESCRIPTION 665 "The list of TRIP communities that this LS supports. A 666 TRIP community is a group of destinations that share 667 common properties. 669 The TRIP Communities attribute is used to group 670 destinations so that the routing decision can be based 671 on the identity of the group." 672 REFERENCE 673 "RFC 3219, section 5.9" 674 ::= { tripMIBObjects 3 } 676 tripSupportedCommunityEntry OBJECT-TYPE 677 SYNTAX TripSupportedCommunityEntry 678 MAX-ACCESS not-accessible 679 STATUS current 680 DESCRIPTION 681 "Entry containing information about a community. A TRIP 682 community is a group of destinations that share some 683 common property. This attribute is used so that routing 684 decisions can be based on the identity of the group" 685 INDEX { applIndex, tripSupportedCommunityId } 686 ::= { tripSupportedCommunityTable 1 } 688 TripSupportedCommunityEntry ::= SEQUENCE { 689 tripSupportedCommunityId TripCommunityId, 690 tripSupportedCommunityItad TripItad, 691 tripSupportedCommunityStorage StorageType, 692 tripSupportedCommunityRowStatus RowStatus 693 } 695 tripSupportedCommunityId OBJECT-TYPE 696 SYNTAX TripCommunityId 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "The identifier of the supported Community." 701 ::= { tripSupportedCommunityEntry 1 } 703 tripSupportedCommunityItad OBJECT-TYPE 704 SYNTAX TripItad 705 MAX-ACCESS read-create 706 STATUS current 708 Zinman/Walker/Jiang 14 709 DESCRIPTION 710 "The Itad of the community." 711 ::= { tripSupportedCommunityEntry 2 } 713 tripSupportedCommunityStorage OBJECT-TYPE 714 SYNTAX StorageType 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "The storage type for this conceptual row. Conceptual 719 rows having the value 'permanent' need not allow write- 720 access to any columnar objects in the row." 721 DEFVAL { nonVolatile } 722 ::= { tripSupportedCommunityEntry 3 } 724 tripSupportedCommunityRowStatus OBJECT-TYPE 725 SYNTAX RowStatus 726 MAX-ACCESS read-create 727 STATUS current 728 DESCRIPTION 729 "The row status of the entry. This object is required 730 to create or delete rows by a manager. A value for 731 tripSupportedCommunityItad must be set for row creation 732 to be successful. If the instance already exists for a 733 particular applIndex, the row create operation will 734 fail. 736 The value of this object has no effect on whether 737 other objects in this conceptual row can be modified." 738 ::= { tripSupportedCommunityEntry 4 } 740 -- 741 -- TripPeerTable 742 -- 743 tripPeerTable OBJECT-TYPE 744 SYNTAX SEQUENCE OF TripPeerEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "The TRIP peer table. This table contains one entry per 749 TRIP peer, and information about the connection with 750 the peer." 751 ::= { tripMIBObjects 4 } 753 tripPeerEntry OBJECT-TYPE 754 SYNTAX TripPeerEntry 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "Entry containing information about the connection with 759 a TRIP peer." 760 INDEX { applIndex, 762 Zinman/Walker/Jiang 15 763 tripPeerRemoteAddrInetType, 764 tripPeerRemoteAddr, 765 tripPeerRemotePort } 766 ::= {tripPeerTable 1} 768 TripPeerEntry ::= SEQUENCE { 769 tripPeerRemoteAddrInetType InetAddressType, 770 tripPeerRemoteAddr InetAddress, 771 tripPeerRemotePort InetPortNumber, 772 tripPeerIdentifier TripId, 773 tripPeerState INTEGER, 774 tripPeerAdminStatus INTEGER, 775 tripPeerNegotiatedVersion TripProtocolVersion, 776 tripPeerSendReceiveMode TripSendReceiveMode, 777 tripPeerRemoteItad TripItad, 778 tripPeerConnectRetryInterval Integer32, 779 tripPeerMaxRetryInterval Integer32, 780 tripPeerHoldTime Integer32, 781 tripPeerKeepAlive Integer32, 782 tripPeerHoldTimeConfigured Integer32, 783 tripPeerKeepAliveConfigured Integer32, 784 tripPeerMaxPurgeTime Integer32, 785 tripPeerDisableTime Integer32, 786 tripPeerLearned TruthValue, 787 tripPeerStorage StorageType, 788 tripPeerRowStatus RowStatus 789 } 791 tripPeerRemoteAddrInetType OBJECT-TYPE 792 SYNTAX InetAddressType 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "The type of Inet Address of the tripPeerRemoteAddr." 797 REFERENCE 798 "RFC 3291, section 3." 799 ::= { tripPeerEntry 1 } 801 tripPeerRemoteAddr OBJECT-TYPE 802 SYNTAX InetAddress 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "The IP address of this entry's TRIP peer LS." 807 REFERENCE 808 "RFC 3291, section 3." 809 ::= { tripPeerEntry 2 } 811 tripPeerRemotePort OBJECT-TYPE 812 SYNTAX InetPortNumber 813 MAX-ACCESS not-accessible 814 STATUS current 816 Zinman/Walker/Jiang 16 817 DESCRIPTION 818 "The remote port for the TCP connection between the 819 TRIP peers." 820 ::= { tripPeerEntry 3 } 822 tripPeerIdentifier OBJECT-TYPE 823 SYNTAX TripId 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "TRIP identifier of the peer." 828 ::= { tripPeerEntry 4 } 830 tripPeerState OBJECT-TYPE 831 SYNTAX INTEGER { 832 idle(1), 833 connect(2), 834 active(3), 835 openSent(4), 836 openConfirm(5), 837 established(6) 838 } 839 MAX-ACCESS read-only 840 STATUS current 841 DESCRIPTION 842 "TRIP Peer Finite State Machine state. 844 idle(1) : The initial state. Local LS refuses all 845 incoming connections. No resources are 846 allocated to the peer. 848 connect(2) : Local LS waiting for a transport 849 protocol connection to be completed to 850 the peer, and is listening for inbound 851 transport connections from the peer. 853 active(3) : LS is listening for an inbound 854 connection from the peer, but is not in 855 the process of initiating a connection 856 to the peer. 858 openSent(4) : LS has sent an OPEN message to its peer 859 and is waiting for an OPEN message from 860 its peer. 862 openConfirm(5): LS has sent an OPEN to its peer, 863 received an OPEN from its peer, and sent 864 a KEEPALIVE in response to the OPEN. The 865 LS is now waiting for a KEEPALIVE or 866 NOTIFICATION message in 867 response to its OPEN. 869 Zinman/Walker/Jiang 17 870 established(6): LS can exchange UPDATE, NOTIFICATION,and 871 KEEPALIVE messages with its peer." 872 ::= { tripPeerEntry 5 } 874 tripPeerAdminStatus OBJECT-TYPE 875 SYNTAX INTEGER { 876 up(1), 877 down(2) 878 } 879 MAX-ACCESS read-create 880 STATUS current 881 DESCRIPTION 882 "This object is used to affect the TRIP connection 883 state. 885 up(1) : Allow a connection with the peer LS. 887 down(2) : disconnect the connection from the peer LS and 888 do not allow any further connections to this 889 peer." 890 ::= { tripPeerEntry 6 } 892 tripPeerNegotiatedVersion OBJECT-TYPE 893 SYNTAX TripProtocolVersion 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "The negotiated version of TRIP running between this 898 local entity and this peer." 899 ::= { tripPeerEntry 7 } 901 tripPeerSendReceiveMode OBJECT-TYPE 902 SYNTAX TripSendReceiveMode 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The operational mode of this peer." 907 ::= { tripPeerEntry 8 } 909 tripPeerRemoteItad OBJECT-TYPE 910 SYNTAX TripItad 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "The Internet Telephony Administrative domain of 915 this peer." 916 ::= { tripPeerEntry 9 } 918 tripPeerConnectRetryInterval OBJECT-TYPE 919 SYNTAX Integer32 (0..2147483647) 920 UNITS "Seconds" 922 Zinman/Walker/Jiang 18 923 MAX-ACCESS read-create 924 STATUS current 925 DESCRIPTION 926 "Specifies the initial amount of time that will elapse 927 between connection retry. This value should double 928 after each attempt up to the value of 929 tripPeerMaxRetryInterval. This value must always be less 930 than or equal to the value of tripPeerMaxRetryInterval. 931 Attempts to set this value higher than the max retry 932 should not be allowed." 933 DEFVAL { 120 } 934 ::= { tripPeerEntry 10 } 936 tripPeerMaxRetryInterval OBJECT-TYPE 937 SYNTAX Integer32 (0..2147483647) 938 UNITS "Seconds" 939 MAX-ACCESS read-create 940 STATUS current 941 DESCRIPTION 942 "Specifies the maximum amount of time that will elapse 943 between connection retries. Once the value of 944 tripPeerConnectRetryInterval has reached this value, no 945 more retries will be attempted. Attempts to set this 946 value lower than the retry interval should not be 947 allowed." 948 DEFVAL { 360 } 949 ::= { tripPeerEntry 11 } 951 tripPeerHoldTime OBJECT-TYPE 952 SYNTAX Integer32 (1..2147483647) 953 UNITS "Seconds" 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "The time interval in seconds for the hold timer that 958 is established with the peer. The value of this object 959 is the smaller of the values in 960 tripPeerHoldTimeConfigured and the hold time received 961 in the open message." 962 ::= { tripPeerEntry 12 } 964 tripPeerKeepAlive OBJECT-TYPE 965 SYNTAX Integer32 (1..2147483647) 966 UNITS "Seconds" 967 MAX-ACCESS read-only 968 STATUS current 969 DESCRIPTION 970 "Specifies the amount of time that must elapse between 971 keep alive messages. This value is negotiated with the 972 remote when a connection is established." 973 ::= { tripPeerEntry 13 } 975 Zinman/Walker/Jiang 19 976 tripPeerHoldTimeConfigured OBJECT-TYPE 977 SYNTAX Integer32 (0 | 3..65535) 978 UNITS "Seconds" 979 MAX-ACCESS read-create 980 STATUS current 981 DESCRIPTION 982 "Specifies the maximum time that may elapse between the 983 receipt of successive keepalive or update message." 984 DEFVAL { 240 } 985 ::= { tripPeerEntry 14 } 987 tripPeerKeepAliveConfigured OBJECT-TYPE 988 SYNTAX Integer32 (1..2147483647) 989 UNITS "Seconds" 990 MAX-ACCESS read-create 991 STATUS current 992 DESCRIPTION 993 "Specifies the amount of time that must elapse between 994 keep alive messages." 995 DEFVAL { 30 } 996 ::= { tripPeerEntry 15 } 998 tripPeerMaxPurgeTime OBJECT-TYPE 999 SYNTAX Integer32 (1..65535) 1000 UNITS "Seconds" 1001 MAX-ACCESS read-create 1002 STATUS current 1003 DESCRIPTION 1004 "Indicate the interval that the LS must maintain routes 1005 marked as withdrawn in its database." 1006 DEFVAL { 10 } 1007 ::= { tripPeerEntry 16 } 1009 tripPeerDisableTime OBJECT-TYPE 1010 SYNTAX Integer32 (1..65535) 1011 UNITS "Seconds" 1012 MAX-ACCESS read-create 1013 STATUS current 1014 DESCRIPTION 1015 "Indicate the interval that the TRIP module of the peer 1016 LS must be disabled while routes originated by the local 1017 LS with high sequence numbers can be removed." 1018 DEFVAL { 180 } 1019 ::= { tripPeerEntry 17 } 1021 tripPeerLearned OBJECT-TYPE 1022 SYNTAX TruthValue 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "Indicates whether this entry was learned or 1028 Zinman/Walker/Jiang 20 1029 configured." 1030 DEFVAL { false } 1031 ::= { tripPeerEntry 18 } 1033 tripPeerStorage OBJECT-TYPE 1034 SYNTAX StorageType 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "The storage type for this conceptual row. Conceptual 1039 rows having the value 'permanent' need not allow write- 1040 access to any columnar objects in the row." 1041 DEFVAL { nonVolatile } 1042 ::= { tripPeerEntry 19 } 1044 tripPeerRowStatus OBJECT-TYPE 1045 SYNTAX RowStatus 1046 MAX-ACCESS read-create 1047 STATUS current 1048 DESCRIPTION 1049 "The row status of the entry. This object is required to 1050 create or delete rows remotely by a manager. If the 1051 instance already exists for a particular applIndex, the 1052 row create operation will fail. 1054 The value of this object has no effect on whether 1055 other objects in this conceptual row can be modified." 1056 ::= { tripPeerEntry 20 } 1058 -- 1059 -- tripPeerRouteTypeTable 1060 -- 1061 tripPeerRouteTypeTable OBJECT-TYPE 1062 SYNTAX SEQUENCE OF TripPeerRouteTypeEntry 1063 MAX-ACCESS not-accessible 1064 STATUS current 1065 DESCRIPTION 1066 "The TRIP peer Route Type table contains one entry per 1067 supported protocol - address family pair. Each instance 1068 of tripPeerRouteTypeEntry has an instance in the 1069 tripPeerTable as a parent. The objects in this table are 1070 volatile and are refreshed after a reboot." 1071 ::= { tripMIBObjects 5 } 1073 tripPeerRouteTypeEntry OBJECT-TYPE 1074 SYNTAX TripPeerRouteTypeEntry 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "Entry containing information about the route type that 1079 the TRIP peer supports." 1080 INDEX { applIndex, 1082 Zinman/Walker/Jiang 21 1083 tripPeerRemoteAddrInetType, 1084 tripPeerRemoteAddr, 1085 tripPeerRemotePort, 1086 tripPeerRtTypeProtocolId, 1087 tripPeerRtTypeAddrFamilyId } 1088 ::= { tripPeerRouteTypeTable 1 } 1090 TripPeerRouteTypeEntry ::= SEQUENCE { 1091 tripPeerRtTypeProtocolId TripAppProtocol, 1092 tripPeerRtTypeAddrFamilyId TripAddressFamily 1093 } 1095 tripPeerRtTypeProtocolId OBJECT-TYPE 1096 SYNTAX TripAppProtocol 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "The object identifier of a protocol that this peer is 1101 using." 1102 ::= { tripPeerRouteTypeEntry 1 } 1104 tripPeerRtTypeAddrFamilyId OBJECT-TYPE 1105 SYNTAX TripAddressFamily 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "The object identifier of an address family that this 1110 peer belongs to." 1111 ::= { tripPeerRouteTypeEntry 2 } 1113 -- 1114 -- TripPeerStatsTable 1115 -- 1116 tripPeerStatsTable OBJECT-TYPE 1117 SYNTAX SEQUENCE OF TripPeerStatsEntry 1118 MAX-ACCESS not-accessible 1119 STATUS current 1120 DESCRIPTION 1121 "The TRIP peer stats table. This table contains one 1122 entry per TRIP peer, and statistics related to the 1123 connection with the peer. The objects in this table are 1124 volatile." 1125 ::= { tripMIBObjects 6 } 1127 tripPeerStatsEntry OBJECT-TYPE 1128 SYNTAX TripPeerStatsEntry 1129 MAX-ACCESS not-accessible 1130 STATUS current 1131 DESCRIPTION 1132 "Entry containing information about the connection with 1133 a TRIP peer." 1134 AUGMENTS { tripPeerEntry } 1136 Zinman/Walker/Jiang 22 1137 ::= { tripPeerStatsTable 1 } 1139 TripPeerStatsEntry ::= SEQUENCE { 1140 tripPeerInUpdates Counter32, 1141 tripPeerOutUpdates Counter32, 1142 tripPeerInTotalMessages Counter32, 1143 tripPeerOutTotalMessages Counter32, 1144 tripPeerFsmEstablishedTransitions Counter32, 1145 tripPeerFsmEstablishedTime DateAndTime, 1146 tripPeerInUpdateElapsedTime TimeInterval, 1147 tripPeerStateChangeTime TimeStamp 1148 } 1150 tripPeerInUpdates OBJECT-TYPE 1151 SYNTAX Counter32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "The number of TRIP update messages received from this 1156 peer since the last restart of this LS." 1157 ::= { tripPeerStatsEntry 1 } 1159 tripPeerOutUpdates OBJECT-TYPE 1160 SYNTAX Counter32 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "The number of TRIP update messages sent to this peer 1165 since the last restart of this location server." 1166 ::= { tripPeerStatsEntry 2 } 1168 tripPeerInTotalMessages OBJECT-TYPE 1169 SYNTAX Counter32 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "The total number of TRIP messages received from the 1174 remote peer on this connection since the last restart 1175 of this LS." 1176 ::= { tripPeerStatsEntry 3 } 1178 tripPeerOutTotalMessages OBJECT-TYPE 1179 SYNTAX Counter32 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "The total number of outgoing TRIP messages sent to the 1184 remote peer since the last restart of this LS." 1185 ::= { tripPeerStatsEntry 4 } 1187 tripPeerFsmEstablishedTransitions OBJECT-TYPE 1188 SYNTAX Counter32 1190 Zinman/Walker/Jiang 23 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "The number of times the TRIP peer has transitioned into 1195 the established state since the last restart of this 1196 LS." 1197 ::= { tripPeerStatsEntry 5 } 1199 tripPeerFsmEstablishedTime OBJECT-TYPE 1200 SYNTAX DateAndTime 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "Indicates the time and date that this peer entered the 1205 established state." 1206 ::= { tripPeerStatsEntry 6 } 1208 tripPeerInUpdateElapsedTime OBJECT-TYPE 1209 SYNTAX TimeInterval 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "Elapsed time in hundredths of seconds since the last 1214 TRIP update message was received from the peer." 1215 ::= { tripPeerStatsEntry 7 } 1217 tripPeerStateChangeTime OBJECT-TYPE 1218 SYNTAX TimeStamp 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "The value of sysUpTime when the last state change of 1223 tripPeerState took place." 1224 ::= { tripPeerStatsEntry 8 } 1226 -- TRIP Received Route Table. This table contains 1227 -- all routes from all sources. Each entry consists 1228 -- of a route and its associated path attributes. 1230 tripRouteTable OBJECT-TYPE 1231 SYNTAX SEQUENCE OF TripRouteEntry 1232 MAX-ACCESS not-accessible 1233 STATUS current 1234 DESCRIPTION 1235 "The TRIP route table containing information about 1236 reachable routes that are to be added to service by the 1237 receiving LS. The objects in this table are volatile 1238 and are refreshed when this LS rediscovers its route 1239 table." 1240 ::= { tripMIBObjects 7 } 1242 tripRouteEntry OBJECT-TYPE 1244 Zinman/Walker/Jiang 24 1245 SYNTAX TripRouteEntry 1246 MAX-ACCESS not-accessible 1247 STATUS current 1248 DESCRIPTION 1249 "Information about a route to a called destination." 1250 INDEX { applIndex, 1251 tripRouteAppProtocol, 1252 tripRouteAddressFamily, 1253 tripRouteAddress, 1254 tripRoutePeer 1255 } 1256 ::= { tripRouteTable 1 } 1258 TripRouteEntry ::= SEQUENCE { 1259 tripRouteAppProtocol TripAppProtocol, 1260 tripRouteAddressFamily TripAddressFamily, 1261 tripRouteAddress OCTET STRING, 1262 tripRoutePeer TripId, 1263 tripRouteTRIBMask BITS, 1264 tripRouteAddressSequenceNumber Integer32, 1265 tripRouteAddressOriginatorId TripId, 1266 tripRouteNextHopServerIAddrType InetAddressType, 1267 tripRouteNextHopServer InetAddress, 1268 tripRouteNextHopServerPort InetPortNumber, 1269 tripRouteNextHopServerItad TripItad, 1270 tripRouteMultiExitDisc Unsigned32, 1271 tripRouteLocalPref Unsigned32, 1272 tripRouteAdvertisementPath OCTET STRING, 1273 tripRouteRoutedPath OCTET STRING, 1274 tripRouteAtomicAggregate TruthValue, 1275 tripRouteUnknown OCTET STRING, 1276 tripRouteWithdrawn TruthValue, 1277 tripRouteConverted TruthValue, 1278 tripRouteReceivedTime TimeStamp 1279 } 1281 tripRouteAppProtocol OBJECT-TYPE 1282 SYNTAX TripAppProtocol 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "The protocol for which this entry of the routing table 1287 is maintained." 1288 ::= { tripRouteEntry 1 } 1290 tripRouteAddressFamily OBJECT-TYPE 1291 SYNTAX TripAddressFamily 1292 MAX-ACCESS not-accessible 1293 STATUS current 1294 DESCRIPTION 1295 "Specifies the type of address for the destination 1296 route." 1298 Zinman/Walker/Jiang 25 1299 ::= { tripRouteEntry 2 } 1301 tripRouteAddress OBJECT-TYPE 1302 SYNTAX OCTET STRING (SIZE(1..105)) 1303 MAX-ACCESS not-accessible 1304 STATUS current 1305 DESCRIPTION 1306 "This is the address (prefix) of the family type given 1307 by Address Family of the destination. It is the prefix 1308 of addresses reachable from this gateway via the next 1309 hop server. The size value of 105 has been assigned due 1310 to the sub identifier of object types length limitation 1311 as defined in SMIv2." 1312 REFERENCE 1313 "RFC 3219, section 5.1.1.1." 1314 ::= { tripRouteEntry 3 } 1316 tripRoutePeer OBJECT-TYPE 1317 SYNTAX TripId 1318 MAX-ACCESS not-accessible 1319 STATUS current 1320 DESCRIPTION 1321 "The identifier of the peer where the route information 1322 was learned." 1323 ::= { tripRouteEntry 4 } 1325 tripRouteTRIBMask OBJECT-TYPE 1326 SYNTAX BITS { 1327 adjTribIns(0), 1328 extTrib(1), 1329 locTrib(2), 1330 adjTribOut(3) 1331 } 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "Indicates which TRIB(s) this entry belongs to. This is 1336 a bit-map of possible types. If the bit has a value of 1337 1, then the entry is a member of the corresponding TRIB 1338 type. If the bit has a value of 0 then the entry is not 1339 a member of the TRIP type. The various bit positions 1340 are: 1342 0 adjTribIns The entry is of type adj-TRIBs-ins. 1343 1 extTrib The entry is of type ext-TRIB. 1344 2 locTrib The entry is of type loc-TRIB. 1345 3 adjTribOut The entry is of type adj-TRIBs-out." 1346 DEFVAL { { } } 1347 ::= { tripRouteEntry 5 } 1349 tripRouteAddressSequenceNumber OBJECT-TYPE 1350 SYNTAX Integer32 (1..2147483647) 1352 Zinman/Walker/Jiang 26 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "Indicates the version of the destination route 1357 originated by the LS identified by 1358 tripRouteAddressOriginatorId intra-domain attribute." 1359 ::= { tripRouteEntry 6 } 1361 tripRouteAddressOriginatorId OBJECT-TYPE 1362 SYNTAX TripId 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "This is an intra-domain attribute indicating the 1367 internal LS that originated the route into the ITAD." 1368 ::= { tripRouteEntry 7 } 1370 tripRouteNextHopServerIAddrType OBJECT-TYPE 1371 SYNTAX InetAddressType 1372 MAX-ACCESS read-only 1373 STATUS current 1374 DESCRIPTION 1375 "The type of Inet Address of the 1376 tripRouteNextHopServer." 1377 REFERENCE 1378 "RFC 3291, section 3." 1379 ::= { tripRouteEntry 8 } 1381 tripRouteNextHopServer OBJECT-TYPE 1382 SYNTAX InetAddress 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "Indicates the next hop that messages of a given 1387 protocol destined for tripRouteAddress should 1388 be sent to." 1389 ::= { tripRouteEntry 9 } 1391 tripRouteNextHopServerPort OBJECT-TYPE 1392 SYNTAX InetPortNumber 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "The port of the next hop server that this route 1397 will use." 1398 ::= { tripRouteEntry 10 } 1400 tripRouteNextHopServerItad OBJECT-TYPE 1401 SYNTAX TripItad 1402 MAX-ACCESS read-only 1403 STATUS current 1404 DESCRIPTION 1406 Zinman/Walker/Jiang 27 1407 "Indicates the domain of the next hop." 1408 ::= { tripRouteEntry 11 } 1410 tripRouteMultiExitDisc OBJECT-TYPE 1411 SYNTAX Unsigned32 (0..4294967295) 1412 MAX-ACCESS read-only 1413 STATUS current 1414 DESCRIPTION 1415 "The Multiple Exit Discriminator allows an LS to 1416 discriminate between, and indicate preference for, 1417 otherwise similar routes to a neighbouring domain. 1418 A higher value represents a more preferred routing 1419 object." 1420 REFERENCE 1421 "RFC 3219, section 5.8" 1422 ::= { tripRouteEntry 12 } 1424 tripRouteLocalPref OBJECT-TYPE 1425 SYNTAX Unsigned32 (0..4294967295) 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "Indicated the local LS's degree of preference for an 1430 advertised route destination." 1431 ::= { tripRouteEntry 13 } 1433 tripRouteAdvertisementPath OBJECT-TYPE 1434 SYNTAX OCTET STRING (SIZE(4..252)) 1435 MAX-ACCESS read-only 1436 STATUS current 1437 DESCRIPTION 1438 "Identifies the ITADs through wich routing information 1439 carried in an advertisement has passed. 1441 This object is probably best represented as sequence of 1442 integer. For SMI compatibility, though, it is 1443 represented as OCTET STRING. This object is a sequence 1444 of ITADs in network byte order." 1445 ::= { tripRouteEntry 14 } 1447 tripRouteRoutedPath OBJECT-TYPE 1448 SYNTAX OCTET STRING (SIZE(4..252)) 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "Identifies the ITADs through which messages sent using 1453 this route would pass. These are as subset of 1454 tripRouteAdvertisementPath. 1456 This object is probably best represented as sequence of 1457 integer. For SMI compatibility, though, it is 1458 represented as OCTET STRING. This object is a sequence 1460 Zinman/Walker/Jiang 28 1461 of ITADs in network byte order." 1462 ::= { tripRouteEntry 15 } 1464 tripRouteAtomicAggregate OBJECT-TYPE 1465 SYNTAX TruthValue 1466 MAX-ACCESS read-only 1467 STATUS current 1468 DESCRIPTION 1469 "Indicates that a route may traverse domains not listed 1470 in tripRouteRoutedPath. If an LS selects the less 1471 specific route from a set of overlapping routes, then 1472 this value returns TRUE." 1473 ::= { tripRouteEntry 16 } 1475 tripRouteUnknown OBJECT-TYPE 1476 SYNTAX OCTET STRING (SIZE(0..255)) 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "One or more attributes not understood and dropped by 1481 this location server." 1482 REFERENCE 1483 "RFC 3219, section 4.3.2.3" 1484 ::= { tripRouteEntry 17 } 1486 tripRouteWithdrawn OBJECT-TYPE 1487 SYNTAX TruthValue 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "Indicates if this route is to be removed from service 1492 by the receiving LS." 1493 ::= { tripRouteEntry 18 } 1495 tripRouteConverted OBJECT-TYPE 1496 SYNTAX TruthValue 1497 MAX-ACCESS read-only 1498 STATUS current 1499 DESCRIPTION 1500 "Indicates if this route has been converted to a 1501 different application protocol than it had originally." 1502 ::= { tripRouteEntry 19 } 1504 tripRouteReceivedTime OBJECT-TYPE 1505 SYNTAX TimeStamp 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "The value of sysUpTime when this route was received." 1510 ::= { tripRouteEntry 20 } 1512 -- 1514 Zinman/Walker/Jiang 29 1515 -- TRIP Received Route Community Table. 1516 -- 1518 tripRouteCommunityTable OBJECT-TYPE 1519 SYNTAX SEQUENCE OF TripRouteCommunityEntry 1520 MAX-ACCESS not-accessible 1521 STATUS current 1522 DESCRIPTION 1523 "A table containing a list of TRIP communities 1524 associated with a route. Each instance of 1525 tripPeerRouteTypeEntry has an instance in the 1526 tripRouteTable as a parent. The objects in this table 1527 are volatile and are refreshed after a reboot." 1528 REFERENCE 1529 "RFC 3219, section 5.9." 1530 ::= { tripMIBObjects 8 } 1532 tripRouteCommunityEntry OBJECT-TYPE 1533 SYNTAX TripRouteCommunityEntry 1534 MAX-ACCESS not-accessible 1535 STATUS current 1536 DESCRIPTION 1537 "Information about communities associated with a route. 1538 An entry with a tripRouteAddress of 00 and a 1539 tripRoutePeer of 0 refers to the local LS." 1540 INDEX { applIndex, 1541 tripRouteAppProtocol, 1542 tripRouteAddressFamily, 1543 tripRouteAddress, 1544 tripRoutePeer, 1545 tripRouteCommunityId 1546 } 1547 ::= { tripRouteCommunityTable 1 } 1549 TripRouteCommunityEntry ::= SEQUENCE { 1550 tripRouteCommunityId TripCommunityId, 1551 tripRouteCommunityItad TripItad 1552 } 1554 tripRouteCommunityId OBJECT-TYPE 1555 SYNTAX TripCommunityId 1556 MAX-ACCESS not-accessible 1557 STATUS current 1558 DESCRIPTION 1559 "The community identifier." 1560 ::= { tripRouteCommunityEntry 1 } 1562 tripRouteCommunityItad OBJECT-TYPE 1563 SYNTAX TripItad 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1568 Zinman/Walker/Jiang 30 1569 "The ITAD associated with this community." 1570 ::= { tripRouteCommunityEntry 2 } 1572 -- 1573 -- tripItadTopologyTable 1574 -- 1576 tripItadTopologyTable OBJECT-TYPE 1577 SYNTAX SEQUENCE OF TripItadTopologyEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "The sequence of link connections between peers within 1582 an ITAD. The objects in this table are volatile and are 1583 refreshed after a reboot." 1584 ::= { tripMIBObjects 9 } 1586 tripItadTopologyEntry OBJECT-TYPE 1587 SYNTAX TripItadTopologyEntry 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "Information about a peer of the LS identified by 1592 tripItadTopologyOrigId." 1593 INDEX { applIndex, tripItadTopologyOrigId } 1594 ::= { tripItadTopologyTable 1 } 1596 TripItadTopologyEntry ::= SEQUENCE { 1597 tripItadTopologyOrigId TripId, 1598 tripItadTopologySeqNum Unsigned32 1599 } 1601 tripItadTopologyOrigId OBJECT-TYPE 1602 SYNTAX TripId 1603 MAX-ACCESS not-accessible 1604 STATUS current 1605 DESCRIPTION 1606 "Indicates the internal LS that originated 1607 the ITAD topology information into the ITAD." 1608 ::= { tripItadTopologyEntry 1 } 1610 tripItadTopologySeqNum OBJECT-TYPE 1611 SYNTAX Unsigned32 (1..2147483647) 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "Indicates the version of the ITAD topology 1616 originated by the LS identified by 1617 tripItadTopologyOrigId." 1618 ::= { tripItadTopologyEntry 2 } 1620 -- 1622 Zinman/Walker/Jiang 31 1623 -- tripItadTopologyIdTable 1624 -- 1626 tripItadTopologyIdTable OBJECT-TYPE 1627 SYNTAX SEQUENCE OF TripItadTopologyIdEntry 1628 MAX-ACCESS not-accessible 1629 STATUS current 1630 DESCRIPTION 1631 "The list of other LS's within the ITAD domain that the 1632 LS identified by tripItadTopologyOrigId is currently 1633 peering. Each instance of tripItadTopologyIdEntry has an 1634 instance in the tripItadTopologyTable as a parent. The 1635 objects in this table are volatile and are refreshed 1636 after a reboot." 1637 ::= { tripMIBObjects 10 } 1639 tripItadTopologyIdEntry OBJECT-TYPE 1640 SYNTAX TripItadTopologyIdEntry 1641 MAX-ACCESS not-accessible 1642 STATUS current 1643 DESCRIPTION 1644 "Information about a peer to the LS identified by 1645 tripItadTopologyOrigId." 1646 INDEX { applIndex, 1647 tripItadTopologyOrigId, 1648 tripItadTopologyId } 1649 ::= { tripItadTopologyIdTable 1 } 1651 TripItadTopologyIdEntry ::= SEQUENCE { 1652 tripItadTopologyId TripId 1653 } 1655 tripItadTopologyId OBJECT-TYPE 1656 SYNTAX TripId 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "The index into this entry. Indicates the other location 1661 servers within the ITAD domain that this LS identified 1662 by tripItadTopologyOrigId is currently peering." 1663 ::= { tripItadTopologyIdEntry 1 } 1665 -- 1666 -- Notification objects 1667 -- 1669 tripNotifApplIndex OBJECT-TYPE 1670 SYNTAX Integer32 (1..2147483647) 1671 MAX-ACCESS accessible-for-notify 1672 STATUS current 1673 DESCRIPTION 1674 "This object contains the applIndex as described 1676 Zinman/Walker/Jiang 32 1677 in RFC 2788. It is used to bind this notification 1678 with a specific instance of TRIP entity." 1679 ::= { tripMIBNotifObjects 1 } 1681 tripNotifPeerAddrInetType OBJECT-TYPE 1682 SYNTAX InetAddressType 1683 MAX-ACCESS accessible-for-notify 1684 STATUS current 1685 DESCRIPTION 1686 "The type of Inet Address of the tripNotifPeerAddr." 1687 REFERENCE 1688 "RFC 3291, section 3." 1689 ::= { tripMIBNotifObjects 2 } 1691 tripNotifPeerAddr OBJECT-TYPE 1692 SYNTAX InetAddress 1693 MAX-ACCESS accessible-for-notify 1694 STATUS current 1695 DESCRIPTION 1696 "The IP address of this entry's TRIP peer LS." 1697 REFERENCE 1698 "RFC 3291, section 3." 1699 ::= { tripMIBNotifObjects 3 } 1701 tripNotifPeerErrCode OBJECT-TYPE 1702 SYNTAX INTEGER { 1703 messageHeader(1), 1704 openMessage(2), 1705 updateMessage(3), 1706 holdTimerExpired(4), 1707 finiteStateMachine(5), 1708 cease(6), 1709 tripNotification(7) 1710 } 1711 MAX-ACCESS accessible-for-notify 1712 STATUS current 1713 DESCRIPTION 1714 "Notification message of TRIP error. The meaning of this 1715 value is applicable to the following functions: 1717 messageHeader - All errors detected while 1718 processing the TRIP message header. 1719 openMessage - All errors detected while 1720 processing the OPEN message. 1721 updateMessage - All errors detected while 1722 processing the UPDATE message. 1723 holdTimerExpired - A notification generated when the 1724 hold timer expires. 1725 finiteStateMachine - All errors detected by the TRIP 1726 Finite State Machine. 1727 cease - Any fatal error condition that the 1728 rest of the values do not cover. 1730 Zinman/Walker/Jiang 33 1731 tripNotification - Any error encountered while sending 1732 a notification message." 1733 ::= { tripMIBNotifObjects 4 } 1735 tripNotifPeerErrSubcode OBJECT-TYPE 1736 SYNTAX Integer32 (1..2147483647) 1737 MAX-ACCESS accessible-for-notify 1738 STATUS current 1739 DESCRIPTION 1740 "The sub error code associated with error code. The 1741 meaning of this value is dependent on the value of 1742 tripNotifPeerErrCode. 1744 Message Header (1) Error Subcodes: 1745 1 - Bad Message Length. 1746 2 - Bad Message Type. 1748 OPEN Message (2) Error Subcodes: 1749 1 - Unsupported Version Number. 1750 2 - Bad Peer ITAD. 1751 3 - Bad TRIP Identifier. 1752 4 - Unsupported Optional Parameter. 1753 5 - Unacceptable Hold Time. 1754 6 - Unsupported Capability. 1755 7 - Capability Mismatch. 1757 UPDATE Message (3) Error Subcodes: 1758 1 - Malformed Attribute List. 1759 2 - Unrecognized Well-known Attribute. 1760 3 - Missing Well-known Mandatory Attribute. 1761 4 - Attribute Flags Error. 1762 5 - Attribute Length Error. 1763 6 - Invalid Attribute." 1764 ::= { tripMIBNotifObjects 5 } 1766 -- 1767 -- Notifications 1768 -- 1769 tripEstablished NOTIFICATION-TYPE 1770 OBJECTS { tripNotifApplIndex } 1771 STATUS current 1772 DESCRIPTION 1773 "The TRIP Established event is generated when the TRIP 1774 FSM enters the ESTABLISHED state." 1775 ::= { tripMIBNotifications 1 } 1777 tripFSM NOTIFICATION-TYPE 1778 OBJECTS { tripNotifApplIndex, 1779 tripNotifPeerAddrInetType, 1780 tripNotifPeerAddr, 1781 tripNotifPeerErrCode, 1782 tripNotifPeerErrSubcode, 1784 Zinman/Walker/Jiang 34 1785 tripPeerState 1786 } 1787 STATUS current 1788 DESCRIPTION 1789 "The trip FSM Event is generated when any error is 1790 detected by the TRIP Finite State Machine." 1791 ::= { tripMIBNotifications 2 } 1793 tripOpenMessageError NOTIFICATION-TYPE 1794 OBJECTS { tripNotifApplIndex, 1795 tripNotifPeerAddrInetType, 1796 tripNotifPeerAddr, 1797 tripNotifPeerErrCode, 1798 tripNotifPeerErrSubcode, 1799 tripPeerState 1800 } 1801 STATUS current 1802 DESCRIPTION 1803 "Errors detected while processing the OPEN message." 1804 ::= { tripMIBNotifications 3 } 1806 tripUpdateMessageError NOTIFICATION-TYPE 1807 OBJECTS { tripNotifApplIndex, 1808 tripNotifPeerAddrInetType, 1809 tripNotifPeerAddr, 1810 tripNotifPeerErrCode, 1811 tripNotifPeerErrSubcode, 1812 tripPeerState 1813 } 1814 STATUS current 1815 DESCRIPTION 1816 "Errors detected while processing the UPDATE message." 1817 ::= { tripMIBNotifications 4 } 1819 tripHoldTimerExpired NOTIFICATION-TYPE 1820 OBJECTS { tripNotifApplIndex, 1821 tripNotifPeerAddrInetType, 1822 tripNotifPeerAddr, 1823 tripNotifPeerErrCode, 1824 tripNotifPeerErrSubcode, 1825 tripPeerState 1826 } 1827 STATUS current 1828 DESCRIPTION 1829 "The system does not receive successive messages within 1830 the period specified by the negotiated Hold Time." 1831 ::= { tripMIBNotifications 5 } 1833 tripConnectionCollision NOTIFICATION-TYPE 1834 OBJECTS { tripNotifApplIndex } 1835 STATUS current 1836 DESCRIPTION 1838 Zinman/Walker/Jiang 35 1839 "A pair of LSs tried to simultaneously to establish a 1840 transport connection to each other." 1841 ::= { tripMIBNotifications 6 } 1843 tripNotificationErr NOTIFICATION-TYPE 1844 OBJECTS { tripNotifApplIndex } 1845 STATUS current 1846 DESCRIPTION 1847 "Generated if there is an error detected in a TRIP 1848 notification message sent with another cause. Note that 1849 the TRIP notification refered to in this object is not 1850 an SNMP notification, it is a specific message described 1851 in the TRIP specification." 1852 REFERENCE 1853 "RFC 3219, section 6.4." 1854 ::= { tripMIBNotifications 7 } 1856 -- 1857 -- Compliance Statements 1858 -- 1859 tripCompliance MODULE-COMPLIANCE 1860 STATUS current 1861 DESCRIPTION 1862 "The compliance statement for TRIP entities." 1864 MODULE -- this module 1865 MANDATORY-GROUPS { tripConfigGroup, 1866 tripPeerTableConfigGroup, 1867 tripRouteGroup, 1868 tripItadTopologyGroup, 1869 tripPeerTableStatsGroup } 1871 GROUP tripNotificationGroup 1872 DESCRIPTION 1873 "This group is optional. A TRIP entity can choose not to 1874 send any notifications. If this group is implemented, 1875 the tripNotifObjectGroup must also be implemented." 1877 GROUP tripNotifObjectGroup 1878 DESCRIPTION 1879 "This group is optional. A TRIP entity can choose not to 1880 send any notifications. If this group is implemented, 1881 the tripNotificationGroup must also be implemented." 1883 MODULE NETWORK-SERVICES-MIB 1884 MANDATORY-GROUPS { applGroup } 1886 ::= { tripMIBCompliance 1 } 1888 -- 1889 -- Object and event conformance groups 1890 -- 1892 Zinman/Walker/Jiang 36 1893 tripConfigGroup OBJECT-GROUP 1894 OBJECTS { 1895 tripCfgProtocolVersion, 1896 tripCfgItad, 1897 tripCfgIdentifier, 1898 tripCfgOperStatus, 1899 tripCfgAdminStatus, 1900 tripCfgAddrIAddrType, 1901 tripCfgAddr, 1902 tripCfgPort, 1903 tripCfgMinItadOriginationInterval, 1904 tripCfgMinRouteAdvertisementInterval, 1905 tripCfgMaxPurgeTime, 1906 tripCfgDisableTime, 1907 tripCfgSendReceiveMode, 1908 tripSupportedCommunityItad, 1909 tripSupportedCommunityStorage, 1910 tripRouteTypeAddrFamilyId, 1911 tripSupportedCommunityRowStatus 1912 } 1913 STATUS current 1914 DESCRIPTION 1915 "The global objects for configuring trip." 1916 ::= { tripMIBGroups 1 } 1918 tripPeerTableConfigGroup OBJECT-GROUP 1919 OBJECTS { 1920 tripPeerIdentifier, 1921 tripPeerState, 1922 tripPeerAdminStatus, 1923 tripPeerNegotiatedVersion, 1924 tripPeerSendReceiveMode, 1925 tripPeerRemoteItad, 1926 tripPeerConnectRetryInterval, 1927 tripPeerMaxRetryInterval, 1928 tripPeerHoldTime, 1929 tripPeerKeepAlive, 1930 tripPeerHoldTimeConfigured, 1931 tripPeerKeepAliveConfigured, 1932 tripPeerMaxPurgeTime, 1933 tripPeerDisableTime, 1934 tripPeerLearned, 1935 tripPeerStorage, 1936 tripPeerRtTypeAddrFamilyId, 1937 tripPeerRowStatus 1938 } 1940 STATUS current 1941 DESCRIPTION 1942 "The global objects for configuring the TRIP peer 1943 table." 1945 Zinman/Walker/Jiang 37 1946 ::= { tripMIBGroups 2 } 1948 tripPeerTableStatsGroup OBJECT-GROUP 1949 OBJECTS { 1950 tripPeerInUpdates, 1951 tripPeerOutUpdates, 1952 tripPeerInTotalMessages, 1953 tripPeerOutTotalMessages, 1954 tripPeerFsmEstablishedTransitions, 1955 tripPeerFsmEstablishedTime, 1956 tripPeerInUpdateElapsedTime, 1957 tripPeerStateChangeTime 1958 } 1959 STATUS current 1960 DESCRIPTION 1961 "The global statistics the TRIP peer table." 1962 ::= { tripMIBGroups 3 } 1964 tripRouteGroup OBJECT-GROUP 1965 OBJECTS { 1966 tripRouteTRIBMask, 1967 tripRouteAddressSequenceNumber, 1968 tripRouteAddressOriginatorId, 1969 tripRouteNextHopServerIAddrType, 1970 tripRouteNextHopServer, 1971 tripRouteNextHopServerPort, 1972 tripRouteNextHopServerItad, 1973 tripRouteMultiExitDisc, 1974 tripRouteLocalPref, 1975 tripRouteAdvertisementPath, 1976 tripRouteRoutedPath, 1977 tripRouteAtomicAggregate, 1978 tripRouteUnknown, 1979 tripRouteWithdrawn, 1980 tripRouteConverted, 1981 tripRouteReceivedTime, 1982 tripRouteCommunityItad 1983 } 1985 STATUS current 1986 DESCRIPTION 1987 "The global objects for configuring route attribute." 1988 ::= { tripMIBGroups 4 } 1990 tripItadTopologyGroup OBJECT-GROUP 1991 OBJECTS { 1992 tripItadTopologySeqNum, 1993 tripItadTopologyId 1994 } 1995 STATUS current 1996 DESCRIPTION 1997 "The objects that define the TRIP ITAD topology." 1999 Zinman/Walker/Jiang 38 2000 ::= { tripMIBGroups 5 } 2002 tripNotificationGroup NOTIFICATION-GROUP 2003 NOTIFICATIONS { 2004 tripEstablished, 2005 tripFSM, 2006 tripOpenMessageError, 2007 tripUpdateMessageError, 2008 tripHoldTimerExpired, 2009 tripConnectionCollision, 2010 tripNotificationErr 2011 } 2012 STATUS current 2013 DESCRIPTION 2014 "A collection of notifications defined for TRIP." 2015 ::= { tripMIBGroups 6 } 2017 tripNotifObjectGroup OBJECT-GROUP 2018 OBJECTS { 2019 tripNotifApplIndex, 2020 tripNotifPeerAddrInetType, 2021 tripNotifPeerAddr, 2022 tripNotifPeerErrCode, 2023 tripNotifPeerErrSubcode 2024 } 2025 STATUS current 2026 DESCRIPTION 2027 "The collection of objects that specify information for 2028 TRIP notifications." 2029 ::= { tripMIBGroups 7 } 2031 END 2033 7. Security Considerations 2035 There are a number of management objects defined in this MIB that 2036 have a MAX-ACCESS clause of read-write and/or read-create. Such 2037 objects may be considered sensitive or vulnerable in some network 2038 environments. The support for SET operations in a non-secure 2039 environment without proper protection can have a negative effect on 2040 network operations. 2042 The managed objects in this MIB contain sensitive information since, 2043 collectively, they allow tracing and influencing of connections in 2044 TRIP devices and provide information of their connection 2045 characteristics. 2047 It is thus important to control even GET access to these objects and 2048 possibly to even encrypt the values of these object when sending 2049 them over the network via SNMP. Not all versions of SNMP provide 2050 features for such a secure environment. 2052 Zinman/Walker/Jiang 39 2053 SNMPv1 by itself is not a secure environment. Even if the network 2054 itself is secure (for example by using IPSec), even then, there is 2055 no control as to who on the secure network is allowed to access and 2056 GET/SET (read/change/create/delete) the objects in this MIB. 2058 It is recommended that the implementers consider the security 2059 features as provided by the SNMPv3 framework. Specifically, the use 2060 of the User-based Security Model RFC 2574 [RFC2574] and the View- 2061 based Access Control Model RFC 2575 [RFC2575] is recommended. 2063 It is then a customer/user responsibility to ensure that the SNMP 2064 entity giving access to an instance of this MIB, is properly 2065 configured to give access to the objects only to those principals 2066 users) that have legitimate rights to indeed GET or SET 2067 (change/create/delete) them. 2069 8. Full Copyright Statement 2071 Copyright (C) The Internet Society (2002). All Rights Reserved. 2072 This document and translations of it may be copied and furnished to 2073 others, and derivative works that comment on or otherwise explain it 2074 or assist in its implementation may be prepared, copied, published 2075 and distributed, in whole or in part, without restriction of any 2076 kind, provided that the above copyright notice and this paragraph 2077 are included on all such copies and derivative works. However, this 2078 document itself may not be modified in any way, such as by removing 2079 the copyright notice or references to the Internet Society or other 2080 Internet organizations, except as needed for the purpose of 2081 developing Internet standards in which case the procedures for 2082 copyrights defined in the Internet Standards process must be 2083 followed, or as required to translate it into languages other than 2084 English. 2086 The limited permissions granted above are perpetual and will not be 2087 revoked by the Internet Society or its successors or assigns. 2089 This document and the information contained herein is provided on an 2090 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2091 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2092 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2093 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2094 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2096 9. Normative References 2098 [RFC3219] Rosenberg, J., Salama, H. and Squire, M., "Telephony 2099 Routing over IP (TRIP)", RFC 3219 January 2002. 2101 [RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, 2102 J., "Network Services Monitoring MIB", RFC 3291, May 2104 Zinman/Walker/Jiang 40 2105 2002. 2107 [RFC1657] Willis, S., Burruss, J., and Chu, J., "Definitions of 2108 Managed Objects for the Fourth Version of the Border 2109 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, July 2110 1994. 2112 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2113 "Simple Network Management Protocol", STD 15, RFC 1157, 2114 May 1990. 2116 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2117 "Message Processing and Dispatching for the Simple 2118 Network Management Protocol (SNMP)", RFC 2572, April 2119 1999. 2121 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2122 Model (USM) for version 3 of the Simple Network 2123 Management Protocol (SNMPv3)", RFC 2574, April 1999. 2125 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2126 "Protocol Operations for Version 2 of the Simple Network 2127 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2129 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2130 Access Control Model (VACM) for the Simple Network 2131 Management Protocol (SNMP)", RFC 2575, April 1999. 2133 [RFC2788] Freed, N., Kille, s., "Network Services Monitoring MIB", 2134 RFC 2788, March 2000. 2136 [BCP0014] Bradner, S., "Key words for use in RFCs to Indicate 2137 Requirement Levels", BCP 14, RFC 2119, March 1997. 2139 10. Informative References 2141 [RFC2026] Bradner, S., "The Internet Standards Process _ Revision 2142 3", BCP 9, RFC 2026, October 1996. 2144 [RFC1771] Rekhter, Y. and Li, T., "Border Gateway Protocol 4 2145 (BGP-4)", RFC 1771, March 1995. 2147 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2148 Architecture for Describing SNMP Management Frameworks", 2149 RFC 2571, April 1999. 2151 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2152 Identification of Management Information for 2153 TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 2155 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2157 Zinman/Walker/Jiang 41 2158 STD 16, RFC 1212, March 1991. 2160 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 2161 the SNMP", RFC 1215, March 1991. 2163 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2164 Case, J., Rose, M., and S. Waldbusser, "Structure of 2165 Management Information Version 2 (SMIv2)", STD 58, 2166 RFC 2578, April 1999. 2168 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2169 J., Rose, M., and S. Waldbusser, "Textual Conventions 2170 for SMIv2", STD 58, RFC 2579, April 1999. 2172 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2173 Case, J., Rose, M., and S. Waldbusser, "Conformance 2174 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2176 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2177 "Introduction to Community-based SNMPv2", RFC 1901, 2178 January 1996. 2180 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2181 "Transport Mappings for Version 2 of the Simple Network 2182 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2184 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2185 Applications", RFC 2573, April 1999. 2187 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2188 "Introduction to Version 3 of the Internet-standard 2189 Network Management Framework", RFC 2570, April 1999. 2191 11. Intellectual Property Notice 2193 The IETF takes no position regarding the validity or scope of any 2194 intellectual property or other rights that might be claimed to 2195 pertain to the implementation or use of the technology described in 2196 this document or the extent to which any license under such rights 2197 might or might not be available; neither does it represent that it 2198 has made any effort to identify any such rights. Information on the 2199 IETF's procedures with respect to rights in standards-track and 2200 standards-related documentation can be found in BCP 11. Copies of 2201 claims of rights made available for publication and any assurances 2202 of licenses to be made available, or the result of an attempt made 2203 to obtain a general license or permission for the use of such 2204 proprietary rights by implementers or users of this specification 2205 can be obtained from the IETF Secretariat. 2207 The IETF invites any interested party to bring to its attention any 2208 copyrights, patents or patent applications, or other proprietary 2210 Zinman/Walker/Jiang 42 2211 rights which may cover technology that may be required to practice 2212 this standard. Please address the information to the IETF Executive 2213 Director. 2215 The IETF has been notified of intellectual property rights claimed 2216 in regard to some or all of the specification contained in this 2217 document. For more information consult the online list of claimed 2218 rights. 2220 12. Acknowledgments 2222 The authors wish to thank Bert Wijnen, Dan Romascanu, and Jonathan 2223 Rosenberg for their insightful comments and suggestions. 2225 13. Author's Addresses 2227 David Zinman 2228 Editor 2229 phone: +1 613 791 2841 2230 Email: dzinman@sympatico.ca 2232 Dave Walker 2233 SS8 Networks, Inc. 2234 495 March Road, Suite #500 2235 Ottawa, ON K2K 3G1 2236 Canada 2237 Phone: +1 613 592 2100 2238 Email: drwalker@ss8.com 2240 Jianping Jiang 2241 SS8 Networks, Inc. 2242 495 March Road, Suite #500 2243 Ottawa, ON K2K 3G1 2244 Canada 2245 Phone: +1 613 592 2100 2246 Email: jianping@ss8.com 2248 14. Working Group 2250 IP Telephony (iptel) Working Group 2251 ================================== 2253 Mailing list: iptel@lists.bell-labs.com 2255 Chair: 2256 Jonathan Rosenberg 2258 Transport Area Directors: 2259 Scott Bradner 2260 Allison Mankin mankin@east.isi.edu 2262 Zinman/Walker/Jiang 43