idnits 2.17.1 draft-ietf-iptel-trip-mib-02.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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([RFC3219], [RFC2578], [RFC1771]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. 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) -- Looks like a reference, but probably isn't: '1' on line 15 -- Looks like a reference, but probably isn't: '24' on line 2047 ** Obsolete normative reference: RFC 1771 (Obsoleted by RFC 4271) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** 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 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) Summary: 16 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 D. Zinman 2 Internet Draft D. Walker 3 Document: draft-ietf-iptel-trip-mib-02.txt SS8 Networks 4 Expires: July 2002 Jianping Jiang 5 SS8 Networks 7 Management Information Base 8 for Telephony Routing over IP (TRIP) 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026 [1]. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in the Internet community. 36 In particular, it describes a set of managed objects that are used 37 to manage for Telephony Routing over IP (TRIP) [RFC3219] devices. 39 Since TRIP [RFC3219] is modeled after the Border Gateway Protocol 40 (BGP-4) [RFC1771], the managed objects for TRIP are also modeled 41 after RFC1657 - Definitions of Managed Objects for the Fourth 42 Version of the Border Gateway Protocol (BGP-4) using SMIv2 43 [RFC2578]. 45 Table of Contents 47 Status of this Memo................................................1 48 Abstract...........................................................1 49 1. Introduction..................................................2 50 2. Conventions used in this document.............................2 52 Zinman/Walker/Jiang 1 53 3. The SNMP Management Framework.................................2 54 4. Overview......................................................3 55 5. Structure of TRIP MIB.........................................3 56 5.1 Textual Conventions...........................................4 57 6. TRIP MIB......................................................4 58 7. Security Considerations......................................38 59 8. Revision History.............................................39 60 8.1. Changes from ..................39 61 8.2. Changes from ..................39 62 8.3. Changes from ..............40 63 8.4. Changes from ..............40 64 9. Full Copyright Statement.....................................40 65 10. References...................................................41 66 11. Author's Addresses...........................................42 67 12. Working Group................................................43 69 1. Introduction 71 This memo defines a portion of the Management Information Base 72 (MIB)for use with network management protocols in the Internet 73 community. In particular, it describes a set of managed objects that 74 are used to schedule management operations periodically or at 75 specified dates and times. 77 2. Conventions used in this document 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 81 this document are to be interpreted as described in BCP-0014 82 [BCP0014]. 84 3. The SNMP Management Framework 86 The SNMP Management Framework presently consists of five major 87 components: 89 o An overall architecture, described in RFC 2571 [RFC2571]. 91 o Mechanisms for describing and naming objects and events for the 92 purpose of management. The first version of this Structure of 93 Management Information (SMI) is called SMIv1 and described in 94 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 95 1215 [RFC1215]. The second version, called SMIv2, is described 96 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 97 STD 58, RFC 2580 [RFC2580]. 99 o Message protocols for transferring management information. The 100 first version of the SNMP message protocol is called SNMPv1 and 101 described in STD 15, RFC 1157 [RFC1157]. A second version of 102 the SNMP message protocol, which is not an Internet standards 104 Zinman/Walker/Jiang 2 105 track protocol, is called SNMPv2c and described in RFC 1901 106 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 107 message protocol is called SNMPv3 and described in RFC 1906 108 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 110 o Protocol operations for accessing management information. The 111 first set of protocol operations and associated PDU formats is 112 described in STD 15, RFC 1157 [RFC1157]. A second set of 113 protocol operations and associated PDU formats is described in 114 RFC 1905 [RFC1905]. 116 o A set of fundamental applications described in RFC 2573 117 [RFC2573] and the view-based access control mechanism described 118 in RFC 2575 [RFC2575]. 120 A more detailed introduction to the current SNMP Management 121 Framework can be found in RFC 2570 [RFC2570]. 123 Managed objects are accessed via a virtual information store, termed 124 the Management Information Base or MIB. Objects in the MIB are 125 defined using the mechanisms defined in the SMI. 127 This memo specifies a MIB module that is compliant to the SMIv2. A 128 MIB conforming to the SMIv1 can be produced through the appropriate 129 translations. The resulting translated MIB must be semantically 130 equivalent, except where objects or events are omitted because no 131 translation is possible (use of Counter64). Some machine readable 132 information in SMIv2 will be converted into textual descriptions in 133 SMIv1 during the translation process. However, this loss of machine 134 readable information is not considered to change the semantics of 135 the MIB. 137 4. Overview 139 Telephony Routing over IP (TRIP) [RFC3219] is an inter-domain 140 application- 141 layer control protocol that exchanges information between TRIP 142 location servers to provide efficient IP telephony routing. This MIB 143 provides managed objects for TRIP devices defined in Telephony 144 Routing over IP [RFC3219]. 146 5. Structure of TRIP MIB 148 This MIB utilizes the framework described in RFC 2788 [RFC2788] for 149 management of multiple instances of TRIP from a single entity. The 150 Network Services Monitoring MIB applTable will be populated with 151 entries corresponding to each TRIP LS in the system. Each TRIP LS 152 will then have an applIndex associated with it. The value assigned 153 to applIndex will represent the distinct instance of TRIP. 155 The TRIP MIB contains the following groups of objects: 156 o The tripConfigGroup contains the common configuration objects 158 Zinman/Walker/Jiang 3 159 applicable to all TRIP applications referenced by the applIndex. 160 o The tripPeerTableConfigGroup contains the configuration objects 161 applicable to all TRIP peers of the LS referened by the applIndex. 162 o The tripRouteGroup contains the configuration objects related to 163 the routes of all TRIBs of this LS. 164 o The tripItadTopologyGroup contains information about the topology 165 of the TRIP ITADs concerning this LS. 166 o The tripPeerTableStatsGroup contains the statistical objects 167 applicable to all TRIP peers of the LS referened by the applIndex. 168 o The tripNotificationGroup contains notifications that the TRIP 169 application can generate. 170 o The tripNotifObjectGroup contains the objects needed by one or 171 more of the notifications. 173 5.1 Textual Conventions 175 The data types TripItad and TripId are used as textual conventions 176 in this document. A TRIP ITAD is described in [RFC3219]. A TRIP ID 177 is used 178 as a distinct identifier for a TRIP LS. A TripAppProtocol is 179 used to identify an application protocol. A TripAddressFamily is 180 used to define an address family. Both TripAppProtocol and 181 TripAddressFamily are OBJECT IDENTIFIERS and as such, a MIB 182 implementor can define a private object of this type of textual 183 convention. Objects defined using these conventions are always 184 encoded by means of the rules that define their primitive type. 185 Hence, no changes to the SMI or the SNMP are necessary to 186 accommodate these textual conventions which are adopted merely for 187 the convenience of readers. 189 6. TRIP MIB 191 TRIP-MIB DEFINITIONS ::= BEGIN 193 IMPORTS 194 MODULE-IDENTITY, 195 OBJECT-TYPE, 196 NOTIFICATION-TYPE, 197 OBJECT-IDENTITY, 198 Unsigned32, 199 Integer32, 200 Counter32, 201 mib-2 202 FROM SNMPv2-SMI 204 TEXTUAL-CONVENTION, 205 DateAndTime, 206 TimeInterval, 207 TruthValue, 208 TimeStamp, 209 StorageType, 210 RowStatus 212 Zinman/Walker/Jiang 4 213 FROM SNMPv2-TC 215 OBJECT-GROUP, 216 MODULE-COMPLIANCE, 217 NOTIFICATION-GROUP 218 FROM SNMPv2-CONF 220 InetAddressType, 221 InetAddress 222 FROM INET-ADDRESS-MIB 224 applIndex 225 FROM NETWORK-SERVICES-MIB; 227 tripMIB MODULE-IDENTITY 228 LAST-UPDATED "200202280000Z" -- Feb 28, 2002 229 ORGANIZATION "IETF IPTel Working Group" 230 CONTACT-INFO 231 "Co-editor David Zinman 232 email: dzinman@sympatico.ca 233 phone: +1 613 791 2841 235 Co-editor Dave Walker 236 SS8 Networks, Inc. 237 postal: 495 March Road, Suite #500 238 Ottawa, ON, K2K 3G1 Canada 239 email: drwalker@ss8.com 240 phone: +1 613 592 2100 242 Co-editor Jianping Jiang 243 SS8 Networks, Inc. 244 postal: 495 March Road, Suite #500 245 Ottawa, ON, K2K 3G1 Canada 246 email: jianping@ss8.com 247 phone: +1 613 592 2100 248 " 249 DESCRIPTION 250 "The MIB module describing Telephony Routing over IP (TRIP). 251 TRIP is a policy driven inter-administrative domain protocol 252 for advertising the reachability of telephony destinations 253 between location servers (LS), and for advertising attributes 254 of the routes to those destinations." 255 REVISION "200202280000Z" 256 DESCRIPTION 257 "The initial version, Published as RFC xxxx." 258 ::= { mib-2 xxx } -- to be assigned by IANA 260 -- 261 -- Textual Conventions 262 -- 263 TripItad ::= TEXTUAL-CONVENTION 264 STATUS current 266 Zinman/Walker/Jiang 5 267 DESCRIPTION 268 "The values for identifying the IP Telephony 269 Administrative Domain (ITAD)." 270 SYNTAX Unsigned32 (0..4294967295) 272 TripId ::= TEXTUAL-CONVENTION 273 STATUS current 274 DESCRIPTION 275 "The TRIP Identifier uniquely identifies a LS within its 276 ITAD. It is a 4 octet unsigned integer that may, but not 277 necessarily, represent the IPv4 address of a Location 278 Server (LS). For an IPv6 network, it will not represent the 279 IPv6 address." 280 SYNTAX Unsigned32 (0..4294967295) 282 TripAppProtocol ::= TEXTUAL-CONVENTION 283 STATUS current 284 DESCRIPTION 285 "The application protocol used for communication with TRIP 286 Location Servers (LS). Protocols defined in this document 287 are: 288 tripSupProtSIP 289 tripSupProtH323Q931 290 tripSupProtH323RAS 291 tripSupProtH323ANNEXG 293 Users can add their own application protocol types by 294 defining a TripAppProtocol type in a private 295 specification." 296 SYNTAX OBJECT IDENTIFIER 298 TripAddressFamily ::= TEXTUAL-CONVENTION 299 STATUS current 300 DESCRIPTION 301 "A type of address for a TRIP route. Address families 302 defined within this MIB module are: 303 tripAddrFamilyDecimal 304 tripAddrFamilyPentadecimal 305 tripAddrFamilyE164 307 Users can add their own address family types by defining a 308 TripAddressFamily type in a private specification." 309 SYNTAX OBJECT IDENTIFIER 311 TripCommunityId ::= TEXTUAL-CONVENTION 312 STATUS current 313 DESCRIPTION 314 "The range of legal values for a TRIP Community Identifier." 315 SYNTAX Unsigned32 (0..4294967295) 317 TripProtocolVersion ::= TEXTUAL-CONVENTION 318 STATUS current 320 Zinman/Walker/Jiang 6 321 DESCRIPTION 322 "The version number of the TRIP protocol." 323 SYNTAX Integer32 (1..255) 325 TripSendReceiveMode ::= TEXTUAL-CONVENTION 326 STATUS current 327 DESCRIPTION 328 "The operational mode of the TRIP application." 329 SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) } 331 tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 } 332 tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 } 333 tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 } 334 tripMIBNotifObjects OBJECT IDENTIFIER ::= { tripMIB 3 } 335 tripMIBAdmin OBJECT IDENTIFIER ::= { tripMIB 4 } 337 tripMIBCompliance OBJECT IDENTIFIER ::= 338 { tripMIBConformance 1 } 339 tripMIBGroups OBJECT IDENTIFIER ::= 340 { tripMIBConformance 2 } 342 -- 343 -- Supported protocols 344 -- 345 tripSupportedProtocols OBJECT-IDENTITY 346 STATUS current 347 DESCRIPTION 348 "Registration point for the protocols supported by 349 TRIP." 350 ::= { tripMIBAdmin 1 } 352 tripSupProtSIP 353 OBJECT IDENTIFIER ::= { tripSupportedProtocols 1 } 354 tripSupProtH323Q931 355 OBJECT IDENTIFIER ::= { tripSupportedProtocols 2 } 356 tripSupProtH323RAS 357 OBJECT IDENTIFIER ::= { tripSupportedProtocols 3 } 358 tripSupProtH323ANNEXG 359 OBJECT IDENTIFIER ::= { tripSupportedProtocols 4 } 361 -- 362 -- Address Families 363 -- 364 tripAddressFamilies OBJECT-IDENTITY 365 STATUS current 366 DESCRIPTION 367 "Registration point for the address families supported 368 by TRIP." 369 ::= { tripMIBAdmin 2 } 371 tripAddrFamilyDecimal 372 OBJECT IDENTIFIER ::= { tripAddressFamilies 1 } 374 Zinman/Walker/Jiang 7 375 tripAddrFamilyPentadecimal 376 OBJECT IDENTIFIER ::= { tripAddressFamilies 2 } 377 tripAddrFamilyE164 378 OBJECT IDENTIFIER ::= { tripAddressFamilies 3 } 380 -- 381 -- tripCfgTable 382 -- 383 tripCfgTable OBJECT-TYPE 384 SYNTAX SEQUENCE OF TripCfgEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "This table contains the common configuration objects 389 applicable to all TRIP applications referenced by the 390 applIndex. Each row represents those objects for a 391 particular TRIP LS present in this system. The 392 instances of TRIP LS's are uniquely identified by the 393 applIndex." 394 ::= { tripMIBObjects 1 } 396 tripCfgEntry OBJECT-TYPE 397 SYNTAX TripCfgEntry 398 MAX-ACCESS not-accessible 399 STATUS current 400 DESCRIPTION 401 "A row of common configuration." 402 INDEX { applIndex } 403 ::= { tripCfgTable 1 } 405 TripCfgEntry ::= 406 SEQUENCE { 407 tripCfgProtocolVersion TripProtocolVersion, 408 tripCfgItad TripItad, 409 tripCfgIdentifier TripId, 410 tripCfgOperStatus INTEGER, 411 tripCfgAdminStatus INTEGER, 412 tripCfgAddrIAddrType InetAddressType, 413 tripCfgAddr InetAddress, 414 tripCfgPort Integer32, 415 tripCfgMinItadOriginationInterval Integer32, 416 tripCfgMinRouteAdvertisementInterval Integer32, 417 tripCfgMaxPurgeTime Integer32, 418 tripCfgDisableTime Integer32, 419 tripCfgSendReceiveMode INTEGER 420 } 422 tripCfgProtocolVersion OBJECT-TYPE 423 SYNTAX TripProtocolVersion 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 428 Zinman/Walker/Jiang 8 429 "This object will reflect the version of TRIP 430 supported by this system. It follows the same 431 format as TRIP version information contained 432 in the TRIP messages generated by this TRIP entity 433 as dictated by the TRIP specification[RFC3219]." 434 ::= { tripCfgEntry 1 } 436 tripCfgItad OBJECT-TYPE 437 SYNTAX TripItad 438 MAX-ACCESS read-write 439 STATUS current 440 DESCRIPTION 441 "The Local Internet Telephony Administrative domain." 442 ::= { tripCfgEntry 2 } 444 tripCfgIdentifier OBJECT-TYPE 445 SYNTAX TripId 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION 449 "The object that identifies this TRIP Client." 450 ::= { tripCfgEntry 3 } 452 tripCfgAdminStatus OBJECT-TYPE 453 SYNTAX INTEGER { 454 up(1), 455 down(2) 456 } 457 MAX-ACCESS read-write 458 STATUS current 459 DESCRIPTION 460 "The desired TRIP state. 462 up(1) : Set the application to normal operation. 464 down(2): Set the application to a state where it will 465 not process TRIP messages." 466 ::= { tripCfgEntry 4 } 468 tripCfgOperStatus OBJECT-TYPE 469 SYNTAX INTEGER { 470 up(1), 471 down(2) 472 } 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The current operational state of the TRIP protocol. 478 up(1) : The application is operating normally, and 479 is processing (receiving and possibly 480 issuing) TRIP requests and responses. 482 Zinman/Walker/Jiang 9 483 down(2): The application is currently unable to 484 process TRIP messages due to a fault or if 485 TRIP is in an initialization state. 487 If tripAdminStatus is down(2) then tripOperStatus should 488 be down(2). If tripAdminStatus is changed to up(1) then 489 tripOperStatus should change to up(1) if there is no 490 fault that prevents the TRIP protocol from moving to the 491 up(1) state." 492 ::= { tripCfgEntry 5 } 494 tripCfgAddrIAddrType OBJECT-TYPE 495 SYNTAX InetAddressType 496 MAX-ACCESS read-only 497 STATUS current 498 DESCRIPTION 499 "The type of Inet Address of the tripAddr." 500 REFERENCE 501 "RFC 2851, section 3." 502 ::= { tripCfgEntry 6 } 504 tripCfgAddr OBJECT-TYPE 505 SYNTAX InetAddress 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "The IP address of the local LS that the peer connects 510 to." 511 REFERENCE 512 "RFC 2851, section 3." 513 ::= { tripCfgEntry 7 } 515 tripCfgPort OBJECT-TYPE 516 SYNTAX Integer32 (1..65535) 517 MAX-ACCESS read-write 518 STATUS current 519 DESCRIPTION 520 "The local tcp/udp port on the local LS that the peer 521 connects to." 522 ::= { tripCfgEntry 8 } 524 tripCfgMinItadOriginationInterval OBJECT-TYPE 525 SYNTAX Integer32 (1..2147483647) 526 UNITS "Seconds" 527 MAX-ACCESS read-write 528 STATUS current 529 DESCRIPTION 530 "The minimum amount of time that must elapse between 531 advertisement of update message that report changes 532 within the LS's own ITAD." 533 DEFVAL { 30 } 535 Zinman/Walker/Jiang 10 536 ::= { tripCfgEntry 9 } 538 tripCfgMinRouteAdvertisementInterval OBJECT-TYPE 539 SYNTAX Integer32 (1..2147483647) 540 UNITS "Seconds" 541 MAX-ACCESS read-write 542 STATUS current 543 DESCRIPTION 544 "Specifies minimal interval between successive 545 advertisements to a particular destination from an LS." 546 DEFVAL { 30 } 547 ::= { tripCfgEntry 10 } 549 tripCfgMaxPurgeTime OBJECT-TYPE 550 SYNTAX Integer32 (1..2147483647) 551 UNITS "Seconds" 552 MAX-ACCESS read-write 553 STATUS current 554 DESCRIPTION 555 "Indicate the interval that the LS must maintain routes 556 marked as withdrawn in its database." 557 DEFVAL { 10 } 558 ::= { tripCfgEntry 11 } 560 tripCfgDisableTime OBJECT-TYPE 561 SYNTAX Integer32 (1..2147483647) 562 UNITS "Seconds" 563 MAX-ACCESS read-write 564 STATUS current 565 DESCRIPTION 566 "Indicate the interval that the TRIP module of the 567 LS must be disabled while routes originated by this 568 location server with high sequence numbers can be 569 removed." 570 DEFVAL { 180 } 571 ::= { tripCfgEntry 12 } 573 tripCfgSendReceiveMode OBJECT-TYPE 574 SYNTAX INTEGER { 575 sendReceive(1), 576 sendOnly(2), 577 receiveOnly(3) 578 } 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "The operational mode of the trip entity running on this 583 system." 584 ::= { tripCfgEntry 13 } 586 -- 587 -- TripRouteTypeTable 589 Zinman/Walker/Jiang 11 590 -- 592 tripRouteTypeTable OBJECT-TYPE 593 SYNTAX SEQUENCE OF TripRouteTypeEntry 594 MAX-ACCESS not-accessible 595 STATUS current 596 DESCRIPTION 597 "The TRIP Route Type table contains one entry per 598 supported protocol - address family pair. This table 599 lists the route types supported in this peering session 600 by the transmitting LS" 601 ::= { tripMIBObjects 2 } 603 tripRouteTypeEntry OBJECT-TYPE 604 SYNTAX TripRouteTypeEntry 605 MAX-ACCESS not-accessible 606 STATUS current 607 DESCRIPTION 608 "Entry containing information about the route type that 609 the TRIP entity supports." 610 INDEX { applIndex, 611 tripRouteTypeProtocolId, 612 tripRouteTypeAddrFamilyId } 613 ::= { tripRouteTypeTable 1 } 615 TripRouteTypeEntry ::= SEQUENCE { 616 tripRouteTypeProtocolId TripAppProtocol, 617 tripRouteTypeAddrFamilyId TripAddressFamily 618 } 620 tripRouteTypeProtocolId OBJECT-TYPE 621 SYNTAX TripAppProtocol 622 MAX-ACCESS not-accessible 623 STATUS current 624 DESCRIPTION 625 "The object identifier of a protocol that this peer is 626 using." 627 ::= { tripRouteTypeEntry 1 } 629 tripRouteTypeAddrFamilyId OBJECT-TYPE 630 SYNTAX TripAddressFamily 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "The object identifier of an address family that this 635 peer belongs to." 636 ::= { tripRouteTypeEntry 2 } 638 -- 639 -- tripSupportedCommunityTable 640 -- 642 Zinman/Walker/Jiang 12 643 tripSupportedCommunityTable OBJECT-TYPE 644 SYNTAX SEQUENCE OF TripSupportedCommunityEntry 645 MAX-ACCESS not-accessible 646 STATUS current 647 DESCRIPTION 648 "The list of TRIP communities that this LS supports. A 649 TRIP community is a group of destinations that share 650 common properties. 652 The TRIP Communities attribute is used to group 653 destinations so that the routing decision can be based 654 on the identity of the group." 655 REFERENCE 656 "RFC 3219, section 5.9" 657 ::= { tripMIBObjects 3 } 659 tripSupportedCommunityEntry OBJECT-TYPE 660 SYNTAX TripSupportedCommunityEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "Entry containing information about a community. A TRIP 665 community is a group of destinations that share some 666 common property. This attribute is used so that routing 667 decisions can be based on the identity of the group" 668 INDEX { applIndex, tripSupportedCommunityId } 669 ::= { tripSupportedCommunityTable 1 } 671 TripSupportedCommunityEntry ::= SEQUENCE { 672 tripSupportedCommunityId TripCommunityId, 673 tripSupportedCommunityItad TripItad, 674 tripSupportedCommunityStorage StorageType, 675 tripSupportedCommunityRowStatus RowStatus 676 } 678 tripSupportedCommunityId OBJECT-TYPE 679 SYNTAX TripCommunityId 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "The identifier of the supported Community." 684 ::= { tripSupportedCommunityEntry 1 } 686 tripSupportedCommunityItad OBJECT-TYPE 687 SYNTAX TripItad 688 MAX-ACCESS read-create 689 STATUS current 690 DESCRIPTION 691 "The Itad of the community." 692 ::= { tripSupportedCommunityEntry 2 } 694 tripSupportedCommunityStorage OBJECT-TYPE 696 Zinman/Walker/Jiang 13 697 SYNTAX StorageType 698 MAX-ACCESS read-create 699 STATUS current 700 DESCRIPTION 701 "The storage type for this conceptual row. Conceptual 702 rows having the value 'permanent' need not allow write- 703 access to any columnar objects in the row." 704 DEFVAL { nonVolatile } 705 ::= { tripSupportedCommunityEntry 3 } 707 tripSupportedCommunityRowStatus OBJECT-TYPE 708 SYNTAX RowStatus 709 MAX-ACCESS read-create 710 STATUS current 711 DESCRIPTION 712 "The row status of the entry. This object is required 713 to create or delete rows by a manager. A value for 714 tripSupportedCommunityItad must be set for row creation 715 to be successful. If the instance already exists for a 716 particular applIndex, the row create operation will 717 fail." 718 ::= { tripSupportedCommunityEntry 4 } 720 -- 721 -- TripPeerTable 722 -- 723 tripPeerTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF TripPeerEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "The TRIP peer table. This table contains one entry per 729 TRIP peer, and information about the connection with 730 the peer." 731 ::= { tripMIBObjects 4 } 733 tripPeerEntry OBJECT-TYPE 734 SYNTAX TripPeerEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "Entry containing information about the connection with 739 a TRIP peer." 740 INDEX { applIndex, 741 tripPeerRemoteAddrInetType, 742 tripPeerRemoteAddr, 743 tripPeerRemotePort } 744 ::= {tripPeerTable 1} 746 TripPeerEntry ::= SEQUENCE { 747 tripPeerRemoteAddrInetType InetAddressType, 748 tripPeerRemoteAddr InetAddress, 750 Zinman/Walker/Jiang 14 751 tripPeerRemotePort Integer32, 752 tripPeerIdentifier TripId, 753 tripPeerState INTEGER, 754 tripPeerAdminStatus INTEGER, 755 tripPeerNegotiatedVersion TripProtocolVersion, 756 tripPeerSendReceiveMode INTEGER, 757 tripPeerRemoteItad TripItad, 758 tripPeerConnectRetryInterval Integer32, 759 tripPeerMaxRetryInterval Integer32, 760 tripPeerHoldTime Integer32, 761 tripPeerKeepAlive Integer32, 762 tripPeerHoldTimeConfigured Integer32, 763 tripPeerKeepAliveConfigured Integer32, 764 tripPeerMaxPurgeTime Integer32, 765 tripPeerDisableTime Integer32, 766 tripPeerLearned TruthValue, 767 tripPeerStorage StorageType, 768 tripPeerRowStatus RowStatus 769 } 771 tripPeerRemoteAddrInetType OBJECT-TYPE 772 SYNTAX InetAddressType 773 MAX-ACCESS not-accessible 774 STATUS current 775 DESCRIPTION 776 "The type of Inet Address of the tripPeerRemoteAddr." 777 REFERENCE 778 "RFC 2851, section 3." 779 ::= { tripPeerEntry 1 } 781 tripPeerRemoteAddr OBJECT-TYPE 782 SYNTAX InetAddress (SIZE(0..125)) 783 MAX-ACCESS not-accessible 784 STATUS current 785 DESCRIPTION 786 "The remote IP address of this entry's TRIP peer. The 787 size value of 125 has been assigned due to the sub 788 identifier of object types length limitation as 789 defined in SMIv2." 790 REFERENCE 791 "RFC 2851, section 3." 792 ::= { tripPeerEntry 2 } 794 tripPeerRemotePort OBJECT-TYPE 795 SYNTAX Integer32 (1..65535) 796 MAX-ACCESS not-accessible 797 STATUS current 798 DESCRIPTION 799 "The remote port for the TCP connection between the 800 TRIP peers." 801 ::= { tripPeerEntry 3 } 803 Zinman/Walker/Jiang 15 804 tripPeerIdentifier OBJECT-TYPE 805 SYNTAX TripId 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "TRIP identifier of the peer." 810 ::= { tripPeerEntry 4 } 812 tripPeerState OBJECT-TYPE 813 SYNTAX INTEGER { 814 idle(1), 815 connect(2), 816 active(3), 817 openSent(4), 818 openConfirm(5), 819 established(6) 820 } 821 MAX-ACCESS read-only 822 STATUS current 823 DESCRIPTION 824 "TRIP Peer Finite State Machine state. 826 idle(1) : The initial state. Local LS refuses all 827 incoming connections. No resources are 828 allocated to the peer. 830 connect(2) : Local LS waiting for a transport 831 protocol connection to be completed to 832 the peer, and is listening for inbound 833 transport connections from the peer. 835 active(3) : LS is listening for an inbound 836 connection from the peer, but is not in 837 the process of initiating a connection 838 to the peer. 840 openSent(4) : LS has sent an OPEN message to its peer 841 and is waiting for an OPEN message from 842 its peer. 844 openConfirm(5): LS has sent an OPEN to its peer, 845 received an OPEN from its peer, and sent 846 a KEEPALIVE in response to the OPEN. The 847 LS is now waiting for a KEEPALIVE or 848 NOTIFICATION message in 849 response to its OPEN. 851 established(6): LS can exchange UPDATE, NOTIFICATION,and 852 KEEPALIVE messages with its peer." 853 ::= { tripPeerEntry 5 } 855 tripPeerAdminStatus OBJECT-TYPE 857 Zinman/Walker/Jiang 16 858 SYNTAX INTEGER { 859 up(1), 860 down(2) 861 } 862 MAX-ACCESS read-create 863 STATUS current 864 DESCRIPTION 865 "This object is used to affect the TRIP connection 866 state. 868 up(1) : Allow a connection with the peer LS. 870 down(2) : disconnect the connection from the peer LS and 871 do not allow any further connections to this 872 peer." 873 ::= { tripPeerEntry 6 } 875 tripPeerNegotiatedVersion OBJECT-TYPE 876 SYNTAX TripProtocolVersion 877 MAX-ACCESS read-only 878 STATUS current 879 DESCRIPTION 880 "The negotiated version of TRIP running between this 881 local entity and this peer." 882 ::= { tripPeerEntry 7 } 884 tripPeerSendReceiveMode OBJECT-TYPE 885 SYNTAX INTEGER { 886 sendReceive(1), 887 sendOnly(2), 888 receiveOnly(3) 889 } 890 MAX-ACCESS read-only 891 STATUS current 892 DESCRIPTION 893 "The operational mode of this peer." 894 ::= { tripPeerEntry 8 } 896 tripPeerRemoteItad OBJECT-TYPE 897 SYNTAX TripItad 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION 901 "The Internet Telephony Administrative domain of 902 this peer." 903 ::= { tripPeerEntry 9 } 905 tripPeerConnectRetryInterval OBJECT-TYPE 906 SYNTAX Integer32 (0..2147483647) 907 UNITS "Seconds" 908 MAX-ACCESS read-create 910 Zinman/Walker/Jiang 17 911 STATUS current 912 DESCRIPTION 913 "Specifies the initial amount of time that will elapse 914 between connection retry. This value should double 915 after each attempt up to the value of 916 tripPeerMaxRetryInterval. This value must always be less 917 than or equal to the value of tripPeerMaxRetryInterval. 918 Attempts to set this value higher than the max retry 919 should not be allowed." 920 DEFVAL { 120 } 921 ::= { tripPeerEntry 10 } 923 tripPeerMaxRetryInterval OBJECT-TYPE 924 SYNTAX Integer32 (0..2147483647) 925 UNITS "Seconds" 926 MAX-ACCESS read-create 927 STATUS current 928 DESCRIPTION 929 "Specifies the maximum amount of time that will elapse 930 between connection retries. Once the value of 931 tripPeerConnectRetryInterval has reached this value, no 932 more retries will be attempted. Attempts to set this 933 value lower than the retry interval should not be 934 allowed." 935 DEFVAL { 360 } 936 ::= { tripPeerEntry 11 } 938 tripPeerHoldTime OBJECT-TYPE 939 SYNTAX Integer32 (1..2147483647) 940 UNITS "Seconds" 941 MAX-ACCESS read-only 942 STATUS current 943 DESCRIPTION 944 "The time interval in seconds for the hold timer that 945 is established with the peer. The value of this object 946 is the smaller of the values in 947 tripPeerHoldTimeConfigured and the hold time received 948 in the open message." 949 ::= { tripPeerEntry 12 } 951 tripPeerKeepAlive OBJECT-TYPE 952 SYNTAX Integer32 (1..2147483647) 953 UNITS "Seconds" 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "Specifies the amount of time that must elapse between 958 keep alive messages. This value is negotiated with the 959 remote when a connection is established." 960 ::= { tripPeerEntry 13 } 962 Zinman/Walker/Jiang 18 963 tripPeerHoldTimeConfigured OBJECT-TYPE 964 SYNTAX Integer32 (0 | 3..65535) 965 UNITS "Seconds" 966 MAX-ACCESS read-create 967 STATUS current 968 DESCRIPTION 969 "Specifies the maximum time that may elapse between the 970 receipt of successive keepalive or update message." 971 DEFVAL { 240 } 972 ::= { tripPeerEntry 14 } 974 tripPeerKeepAliveConfigured OBJECT-TYPE 975 SYNTAX Integer32 (1..2147483647) 976 UNITS "Seconds" 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "Specifies the amount of time that must elapse between 981 keep alive messages." 982 DEFVAL { 30 } 983 ::= { tripPeerEntry 15 } 985 tripPeerMaxPurgeTime OBJECT-TYPE 986 SYNTAX Integer32 (1..65535) 987 UNITS "Seconds" 988 MAX-ACCESS read-create 989 STATUS current 990 DESCRIPTION 991 "Indicate the interval that the LS must maintain routes 992 marked as withdrawn in its database." 993 DEFVAL { 10 } 994 ::= { tripPeerEntry 16 } 996 tripPeerDisableTime OBJECT-TYPE 997 SYNTAX Integer32 (1..65535) 998 UNITS "Seconds" 999 MAX-ACCESS read-create 1000 STATUS current 1001 DESCRIPTION 1002 "Indicate the interval that the TRIP module of the peer 1003 LS must be disabled while routes originated by the local 1004 LS with high sequence numbers can be removed." 1005 DEFVAL { 180 } 1006 ::= { tripPeerEntry 17 } 1008 tripPeerLearned OBJECT-TYPE 1009 SYNTAX TruthValue 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "Indicates whether this entry was learned or 1014 configured." 1016 Zinman/Walker/Jiang 19 1017 DEFVAL { false } 1018 ::= { tripPeerEntry 18 } 1020 tripPeerStorage OBJECT-TYPE 1021 SYNTAX StorageType 1022 MAX-ACCESS read-create 1023 STATUS current 1024 DESCRIPTION 1025 "The storage type for this conceptual row. Conceptual 1026 rows having the value 'permanent' need not allow write- 1027 access to any columnar objects in the row." 1028 DEFVAL { nonVolatile } 1029 ::= { tripPeerEntry 19 } 1031 tripPeerRowStatus OBJECT-TYPE 1032 SYNTAX RowStatus 1033 MAX-ACCESS read-create 1034 STATUS current 1035 DESCRIPTION 1036 "The row status of the entry. This object is required to 1037 create or delete rows remotely by a manager. If that 1038 method already exists for a particular applIndex, the 1039 row create operation will fail." 1040 ::= { tripPeerEntry 20 } 1042 -- 1043 -- tripPeerRouteTypeTable 1044 -- 1045 tripPeerRouteTypeTable OBJECT-TYPE 1046 SYNTAX SEQUENCE OF TripPeerRouteTypeEntry 1047 MAX-ACCESS not-accessible 1048 STATUS current 1049 DESCRIPTION 1050 "The TRIP peer Route Type table contains one entry per 1051 supported protocol - address family pair. Each instance 1052 of tripPeerRouteTypeEntry has an instance in the 1053 tripPeerTable as a parent." 1054 ::= { tripMIBObjects 5 } 1056 tripPeerRouteTypeEntry OBJECT-TYPE 1057 SYNTAX TripPeerRouteTypeEntry 1058 MAX-ACCESS not-accessible 1059 STATUS current 1060 DESCRIPTION 1061 "Entry containing information about the route type that 1062 the TRIP peer supports." 1063 INDEX { applIndex, 1064 tripPeerRemoteAddrInetType, 1065 tripPeerRemoteAddr, 1066 tripPeerRemotePort, 1067 tripPeerRtTypeProtocolId, 1068 tripPeerRtTypeAddrFamilyId } 1070 Zinman/Walker/Jiang 20 1071 ::= { tripPeerRouteTypeTable 1 } 1073 TripPeerRouteTypeEntry ::= SEQUENCE { 1074 tripPeerRtTypeProtocolId TripAppProtocol, 1075 tripPeerRtTypeAddrFamilyId TripAddressFamily 1076 } 1078 tripPeerRtTypeProtocolId OBJECT-TYPE 1079 SYNTAX TripAppProtocol 1080 MAX-ACCESS not-accessible 1081 STATUS current 1082 DESCRIPTION 1083 "The object identifier of a protocol that this peer is 1084 using." 1085 ::= { tripPeerRouteTypeEntry 1 } 1087 tripPeerRtTypeAddrFamilyId OBJECT-TYPE 1088 SYNTAX TripAddressFamily 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "The object identifier of an address family that this 1093 peer belongs to." 1094 ::= { tripPeerRouteTypeEntry 2 } 1096 -- 1097 -- TripPeerStatsTable 1098 -- 1099 tripPeerStatsTable OBJECT-TYPE 1100 SYNTAX SEQUENCE OF TripPeerStatsEntry 1101 MAX-ACCESS not-accessible 1102 STATUS current 1103 DESCRIPTION 1104 "The TRIP peer stats table. This table contains one 1105 entry per TRIP peer, and statistics related to the 1106 connection with the peer." 1107 ::= { tripMIBObjects 6 } 1109 tripPeerStatsEntry OBJECT-TYPE 1110 SYNTAX TripPeerStatsEntry 1111 MAX-ACCESS not-accessible 1112 STATUS current 1113 DESCRIPTION 1114 "Entry containing information about the connection with 1115 a TRIP peer." 1116 AUGMENTS { tripPeerEntry } 1117 ::= { tripPeerStatsTable 1 } 1119 TripPeerStatsEntry ::= SEQUENCE { 1120 tripPeerInUpdates Counter32, 1121 tripPeerOutUpdates Counter32, 1122 tripPeerInTotalMessages Counter32, 1124 Zinman/Walker/Jiang 21 1125 tripPeerOutTotalMessages Counter32, 1126 tripPeerFsmEstablishedTransitions Counter32, 1127 tripPeerFsmEstablishedTime DateAndTime, 1128 tripPeerInUpdateElapsedTime TimeInterval, 1129 tripPeerStateChangeTime TimeStamp 1130 } 1132 tripPeerInUpdates OBJECT-TYPE 1133 SYNTAX Counter32 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "The number of TRIP update messages received from this 1138 peer since the last restart of this LS." 1139 ::= { tripPeerStatsEntry 1 } 1141 tripPeerOutUpdates OBJECT-TYPE 1142 SYNTAX Counter32 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "The number of TRIP update messages sent to this peer 1147 since the last restart of this location server." 1148 ::= { tripPeerStatsEntry 2 } 1150 tripPeerInTotalMessages OBJECT-TYPE 1151 SYNTAX Counter32 1152 MAX-ACCESS read-only 1153 STATUS current 1154 DESCRIPTION 1155 "The total number of TRIP messages received from the 1156 remote peer on this connection since the last restart 1157 of this LS." 1158 ::= { tripPeerStatsEntry 3 } 1160 tripPeerOutTotalMessages OBJECT-TYPE 1161 SYNTAX Counter32 1162 MAX-ACCESS read-only 1163 STATUS current 1164 DESCRIPTION 1165 "The total number of outgoing TRIP messages sent to the 1166 remote peer since the last restart of this LS." 1167 ::= { tripPeerStatsEntry 4 } 1169 tripPeerFsmEstablishedTransitions OBJECT-TYPE 1170 SYNTAX Counter32 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "The number of times the TRIP peer has transitioned into 1175 the established state since the last restart of this 1176 LS." 1178 Zinman/Walker/Jiang 22 1179 ::= { tripPeerStatsEntry 5 } 1181 tripPeerFsmEstablishedTime OBJECT-TYPE 1182 SYNTAX DateAndTime 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "Indicates the time and date that this peer entered the 1187 established state." 1188 ::= { tripPeerStatsEntry 6 } 1190 tripPeerInUpdateElapsedTime OBJECT-TYPE 1191 SYNTAX TimeInterval 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "Elapsed time in hundredths of seconds since the last 1196 TRIP update message was received from the peer." 1197 ::= { tripPeerStatsEntry 7 } 1199 tripPeerStateChangeTime OBJECT-TYPE 1200 SYNTAX TimeStamp 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "The value of sysUpTime when the last state change of 1205 tripPeerState took place." 1206 ::= { tripPeerStatsEntry 8 } 1208 -- TRIP Received Route Table. This table contains 1209 -- all routes from all sources. Each entry consists 1210 -- of a route and its associated path attributes. 1212 tripRouteTable OBJECT-TYPE 1213 SYNTAX SEQUENCE OF TripRouteEntry 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "The TRIP route table containing information about 1218 reachable routes that are to be added to service by the 1219 receiving LS." 1220 ::= { tripMIBObjects 7 } 1222 tripRouteEntry OBJECT-TYPE 1223 SYNTAX TripRouteEntry 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "Information about a route to a called destination." 1228 INDEX { applIndex, 1229 tripRouteAppProtocol, 1230 tripRouteAddressFamily, 1232 Zinman/Walker/Jiang 23 1233 tripRouteAddress, 1234 tripRoutePeer 1235 } 1236 ::= { tripRouteTable 1 } 1238 TripRouteEntry ::= SEQUENCE { 1239 tripRouteAppProtocol TripAppProtocol, 1240 tripRouteAddressFamily TripAddressFamily, 1241 tripRouteAddress OCTET STRING, 1242 tripRoutePeer TripId, 1243 tripRouteTRIBMask BITS, 1244 tripRouteAddressSequenceNumber Integer32, 1245 tripRouteAddressOriginatorId TripId, 1246 tripRouteNextHopServerIAddrType InetAddressType, 1247 tripRouteNextHopServer InetAddress, 1248 tripRouteNextHopServerPort Integer32, 1249 tripRouteNextHopServerItad TripItad, 1250 tripRouteMultiExitDisc Unsigned32, 1251 tripRouteLocalPref Unsigned32, 1252 tripRouteAdvertisementPath OCTET STRING, 1253 tripRouteRoutedPath OCTET STRING, 1254 tripRouteAtomicAggregate TruthValue, 1255 tripRouteUnknown OCTET STRING, 1256 tripRouteWithdrawn TruthValue, 1257 tripRouteConverted TruthValue, 1258 tripRouteReceivedTime TimeStamp 1259 } 1261 tripRouteAppProtocol OBJECT-TYPE 1262 SYNTAX TripAppProtocol 1263 MAX-ACCESS not-accessible 1264 STATUS current 1265 DESCRIPTION 1266 "The protocol for which this entry of the routing table 1267 is maintained." 1268 ::= { tripRouteEntry 1 } 1270 tripRouteAddressFamily OBJECT-TYPE 1271 SYNTAX TripAddressFamily 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "Specifies the type of address for the destination 1276 route." 1277 ::= { tripRouteEntry 2 } 1279 tripRouteAddress OBJECT-TYPE 1280 SYNTAX OCTET STRING (SIZE(1..255)) 1281 MAX-ACCESS not-accessible 1282 STATUS current 1283 DESCRIPTION 1284 "This is the address (prefix) of the family type given 1286 Zinman/Walker/Jiang 24 1287 by Address Family of the destination. It is the prefix 1288 of addresses reachable from this gateway via the next 1289 hop server." 1290 REFERENCE 1291 "RFC 3219, section 5.1.1.1." 1292 ::= { tripRouteEntry 3 } 1294 tripRoutePeer OBJECT-TYPE 1295 SYNTAX TripId 1296 MAX-ACCESS not-accessible 1297 STATUS current 1298 DESCRIPTION 1299 "The identifier of the peer where the route information 1300 was learned." 1301 ::= { tripRouteEntry 4 } 1303 tripRouteTRIBMask OBJECT-TYPE 1304 SYNTAX BITS { 1305 adjTribIns(0), 1306 extTrib(1), 1307 locTrib(2), 1308 adjTribOut(3) 1309 } 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "Indicates which TRIB(s) this entry belongs to. This is 1314 a bit-map of possible types. The various bit positions 1315 are: 1316 0 adjTribIns The entry is of type adj-TRIBs-ins. 1317 1 extTrib The entry is of type ext-TRIB. 1318 2 locTrib The entry is of type loc-TRIB. 1319 3 adjTribOut The entry is of type adj-TRIBs-out." 1320 DEFVAL { { } } 1321 ::= { tripRouteEntry 5 } 1323 tripRouteAddressSequenceNumber OBJECT-TYPE 1324 SYNTAX Integer32 (1..2147483647) 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "Indicates the version of the destination route 1329 originated by the LS identified by 1330 tripRouteAddressOriginatorId intra-domain attribute." 1331 ::= { tripRouteEntry 6 } 1333 tripRouteAddressOriginatorId OBJECT-TYPE 1334 SYNTAX TripId 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "This is an intra-domain attribute indicating the 1340 Zinman/Walker/Jiang 25 1341 internal LS that originated the route into the ITAD." 1342 ::= { tripRouteEntry 7 } 1344 tripRouteNextHopServerIAddrType OBJECT-TYPE 1345 SYNTAX InetAddressType 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "The type of Inet Address of the 1350 tripRouteNextHopServer." 1351 REFERENCE 1352 "RFC 2851, section 3." 1353 ::= { tripRouteEntry 8 } 1355 tripRouteNextHopServer OBJECT-TYPE 1356 SYNTAX InetAddress 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "Indicates the next hop that messages of a given 1361 protocol destined for tripRouteAddress should 1362 be sent to." 1363 ::= { tripRouteEntry 9 } 1365 tripRouteNextHopServerPort OBJECT-TYPE 1366 SYNTAX Integer32 (1..2147483647) 1367 MAX-ACCESS read-only 1368 STATUS current 1369 DESCRIPTION 1370 "The port of the next hop server that this route 1371 will use." 1372 ::= { tripRouteEntry 10 } 1374 tripRouteNextHopServerItad OBJECT-TYPE 1375 SYNTAX TripItad 1376 MAX-ACCESS read-only 1377 STATUS current 1378 DESCRIPTION 1379 "Indicates the domain of the next hop." 1380 ::= { tripRouteEntry 11 } 1382 tripRouteMultiExitDisc OBJECT-TYPE 1383 SYNTAX Unsigned32 (0..4294967295) 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "This is used by an LS to express a preference for one 1388 link between the domains over another link between the 1389 domains. A higher value represents a more preferred 1390 routing object." 1391 ::= { tripRouteEntry 12 } 1393 Zinman/Walker/Jiang 26 1394 tripRouteLocalPref OBJECT-TYPE 1395 SYNTAX Unsigned32 (0..4294967295) 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "Indicated the local LS's degree of preference for an 1400 advertised route destination." 1401 ::= { tripRouteEntry 13 } 1403 tripRouteAdvertisementPath OBJECT-TYPE 1404 SYNTAX OCTET STRING (SIZE(4..252)) 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "Identifies the ITADs through wich routing information 1409 carried in an advertisement has passed. 1411 This object is probably best represented as sequence of 1412 integer. For SMI compatibility, though, it is 1413 represented as OCTET STRING. This object is a sequence 1414 of ITADs in network byte order." 1415 ::= { tripRouteEntry 14 } 1417 tripRouteRoutedPath OBJECT-TYPE 1418 SYNTAX OCTET STRING (SIZE(4..252)) 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 "Identifies the ITADs through which messages sent using 1423 this route would pass. These are as subset of 1424 tripRouteAdvertisementPath. 1426 This object is probably best represented as sequence of 1427 integer. For SMI compatibility, though, it is 1428 represented as OCTET STRING. This object is a sequence 1429 of ITADs in network byte order." 1430 ::= { tripRouteEntry 15 } 1432 tripRouteAtomicAggregate OBJECT-TYPE 1433 SYNTAX TruthValue 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "Indicates that a route may traverse domains not listed 1438 in tripRouteRoutedPath. If an LS selects the less 1439 specific route from a set of overlapping routes, then 1440 this value returns TRUE." 1441 ::= { tripRouteEntry 16 } 1443 tripRouteUnknown OBJECT-TYPE 1444 SYNTAX OCTET STRING (SIZE(0..255)) 1445 MAX-ACCESS read-only 1447 Zinman/Walker/Jiang 27 1448 STATUS current 1449 DESCRIPTION 1450 "One or more attributes not understood and dropped by 1451 this location server." 1452 REFERENCE 1453 "RFC 3219, section 4.3.2.3" 1454 ::= { tripRouteEntry 17 } 1456 tripRouteWithdrawn OBJECT-TYPE 1457 SYNTAX TruthValue 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "Indicates if this route is to be removed from service 1462 by the receiving LS." 1463 ::= { tripRouteEntry 18 } 1465 tripRouteConverted OBJECT-TYPE 1466 SYNTAX TruthValue 1467 MAX-ACCESS read-only 1468 STATUS current 1469 DESCRIPTION 1470 "Indicates if this route has been converted to a 1471 different application protocol than it had originally." 1472 ::= { tripRouteEntry 19 } 1474 tripRouteReceivedTime OBJECT-TYPE 1475 SYNTAX TimeStamp 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "The value of sysUpTime when this route was received." 1480 ::= { tripRouteEntry 20 } 1482 -- 1483 -- TRIP Received Route Community Table. 1484 -- 1486 tripRouteCommunityTable OBJECT-TYPE 1487 SYNTAX SEQUENCE OF TripRouteCommunityEntry 1488 MAX-ACCESS not-accessible 1489 STATUS current 1490 DESCRIPTION 1491 "A table containing a list of TRIP communities 1492 associated with a route. Each instance of 1493 tripPeerRouteTypeEntry has an instance in the 1494 tripRouteTable as a parent." 1495 REFERENCE 1496 "RFC 3219, section 5.9." 1497 ::= { tripMIBObjects 8 } 1499 tripRouteCommunityEntry OBJECT-TYPE 1501 Zinman/Walker/Jiang 28 1502 SYNTAX TripRouteCommunityEntry 1503 MAX-ACCESS not-accessible 1504 STATUS current 1505 DESCRIPTION 1506 "Information about communities associated with a route. 1507 An entry with a tripRouteAddress of 00 and a 1508 tripRoutePeer of 0 refers to the local LS." 1509 INDEX { applIndex, 1510 tripRouteAppProtocol, 1511 tripRouteAddressFamily, 1512 tripRouteAddress, 1513 tripRoutePeer, 1514 tripRouteCommunityId 1515 } 1516 ::= { tripRouteCommunityTable 1 } 1518 TripRouteCommunityEntry ::= SEQUENCE { 1519 tripRouteCommunityId TripCommunityId, 1520 tripRouteCommunityItad TripItad 1521 } 1523 tripRouteCommunityId OBJECT-TYPE 1524 SYNTAX TripCommunityId 1525 MAX-ACCESS not-accessible 1526 STATUS current 1527 DESCRIPTION 1528 "The community identifier." 1529 ::= { tripRouteCommunityEntry 1 } 1531 tripRouteCommunityItad OBJECT-TYPE 1532 SYNTAX TripItad 1533 MAX-ACCESS read-only 1534 STATUS current 1535 DESCRIPTION 1536 "The ITAD associated with this community." 1537 ::= { tripRouteCommunityEntry 2 } 1539 -- 1540 -- tripItadTopologyTable 1541 -- 1543 tripItadTopologyTable OBJECT-TYPE 1544 SYNTAX SEQUENCE OF TripItadTopologyEntry 1545 MAX-ACCESS not-accessible 1546 STATUS current 1547 DESCRIPTION 1548 "The sequence of link connections between peers within 1549 an ITAD." 1550 ::= { tripMIBObjects 9 } 1552 tripItadTopologyEntry OBJECT-TYPE 1553 SYNTAX TripItadTopologyEntry 1555 Zinman/Walker/Jiang 29 1556 MAX-ACCESS not-accessible 1557 STATUS current 1558 DESCRIPTION 1559 "Information about a peer of the LS identified by 1560 tripItadTopologyOrigId." 1561 INDEX { applIndex, tripItadTopologyOrigId } 1562 ::= { tripItadTopologyTable 1 } 1564 TripItadTopologyEntry ::= SEQUENCE { 1565 tripItadTopologyOrigId TripId, 1566 tripItadTopologySeqNum Unsigned32 1567 } 1569 tripItadTopologyOrigId OBJECT-TYPE 1570 SYNTAX TripId 1571 MAX-ACCESS not-accessible 1572 STATUS current 1573 DESCRIPTION 1574 "Indicates the internal LS that originated 1575 the ITAD topology information into the ITAD." 1576 ::= { tripItadTopologyEntry 1 } 1578 tripItadTopologySeqNum OBJECT-TYPE 1579 SYNTAX Unsigned32 (1..2147483647) 1580 MAX-ACCESS read-only 1581 STATUS current 1582 DESCRIPTION 1583 "Indicates the version of the ITAD topology 1584 originated by the LS identified by 1585 tripItadTopologyOrigId." 1586 ::= { tripItadTopologyEntry 2 } 1588 -- 1589 -- tripItadTopologyIdTable 1590 -- 1592 tripItadTopologyIdTable OBJECT-TYPE 1593 SYNTAX SEQUENCE OF TripItadTopologyIdEntry 1594 MAX-ACCESS not-accessible 1595 STATUS current 1596 DESCRIPTION 1597 "The list of other LS's within the ITAD domain that the 1598 LS identified by tripItadTopologyOrigId is currently 1599 peering. Each instance of tripItadTopologyIdEntry has an 1600 instance in the tripItadTopologyTable as a parent." 1601 ::= { tripMIBObjects 10 } 1603 tripItadTopologyIdEntry OBJECT-TYPE 1604 SYNTAX TripItadTopologyIdEntry 1605 MAX-ACCESS not-accessible 1606 STATUS current 1607 DESCRIPTION 1609 Zinman/Walker/Jiang 30 1610 "Information about a peer to the LS identified by 1611 tripItadTopologyOrigId." 1612 INDEX { applIndex, 1613 tripItadTopologyOrigId, 1614 tripItadTopologyId } 1615 ::= { tripItadTopologyIdTable 1 } 1617 TripItadTopologyIdEntry ::= SEQUENCE { 1618 tripItadTopologyId TripId 1619 } 1621 tripItadTopologyId OBJECT-TYPE 1622 SYNTAX TripId 1623 MAX-ACCESS read-only 1624 STATUS current 1625 DESCRIPTION 1626 "The index into this entry. Indicates the other location 1627 servers within the ITAD domain that this LS identified 1628 by tripItadTopologyOrigId is currently peering." 1629 ::= { tripItadTopologyIdEntry 1 } 1631 -- 1632 -- Notification objects 1633 -- 1635 tripNotifApplIndex OBJECT-TYPE 1636 SYNTAX Integer32 (1..2147483647) 1637 MAX-ACCESS accessible-for-notify 1638 STATUS current 1639 DESCRIPTION 1640 "This object contains the applIndex as described 1641 in RFC 2788. It is used to bind this notification 1642 with a specific instance of TRIP entity." 1643 ::= { tripMIBNotifObjects 1 } 1645 tripNotifPeerAddrInetType OBJECT-TYPE 1646 SYNTAX InetAddressType 1647 MAX-ACCESS accessible-for-notify 1648 STATUS current 1649 DESCRIPTION 1650 "The type of Inet Address of the tripNotifPeerAddr." 1651 REFERENCE 1652 "RFC 2851, section 3." 1653 ::= { tripMIBNotifObjects 2 } 1655 tripNotifPeerAddr OBJECT-TYPE 1656 SYNTAX InetAddress (SIZE(0..125)) 1657 MAX-ACCESS accessible-for-notify 1658 STATUS current 1659 DESCRIPTION 1660 "The remote IP address of this entry's TRIP peer. The 1661 size value of 125 has been assigned due to the sub 1663 Zinman/Walker/Jiang 31 1664 identifier of object types length limitation as 1665 defined in SMIv2." 1666 REFERENCE 1667 "RFC 2851, section 3." 1668 ::= { tripMIBNotifObjects 3 } 1670 tripNotifPeerErrCode OBJECT-TYPE 1671 SYNTAX INTEGER { 1672 messageHeader(1), 1673 openMessage(2), 1674 updateMessage(3), 1675 holdTimerExpired(4), 1676 finiteStateMachine(5), 1677 cease(6), 1678 tripNotification(7) 1679 } 1680 MAX-ACCESS accessible-for-notify 1681 STATUS current 1682 DESCRIPTION 1683 "Notification message of TRIP error. The meaning of this 1684 value is applicable to the following functions: 1686 messageHeader - All errors detected while 1687 processing the TRIP message header. 1688 openMessage - All errors detected while 1689 processing the OPEN message. 1690 updateMessage - All errors detected while 1691 processing the UPDATE message. 1692 holdTimerExpired - A notification generated when the 1693 hold timer expires. 1694 finiteStateMachine - All errors detected by the TRIP 1695 Finite State Machine. 1696 cease - Any fatal error condition that the 1697 rest of the values do not cover. 1698 tripNotification - Any error encountered while sending 1699 a notification message." 1700 ::= { tripMIBNotifObjects 4 } 1702 tripNotifPeerErrSubcode OBJECT-TYPE 1703 SYNTAX Integer32 (1..2147483647) 1704 MAX-ACCESS accessible-for-notify 1705 STATUS current 1706 DESCRIPTION 1707 "The sub error code associated with error code. The 1708 meaning of this value is dependent on the value of 1709 tripNotifPeerErrCode. 1711 Message Header (1) Error Subcodes: 1712 1 - Bad Message Length. 1713 2 - Bad Message Type. 1715 OPEN Message (2) Error Subcodes: 1717 Zinman/Walker/Jiang 32 1718 1 - Unsupported Version Number. 1719 2 - Bad Peer ITAD. 1720 3 - Bad TRIP Identifier. 1721 4 - Unsupported Optional Parameter. 1722 5 - Unacceptable Hold Time. 1723 6 - Unsupported Capability. 1724 7 - Capability Mismatch. 1726 UPDATE Message (3) Error Subcodes: 1727 1 - Malformed Attribute List. 1728 2 - Unrecognized Well-known Attribute. 1729 3 - Missing Well-known Mandatory Attribute. 1730 4 - Attribute Flags Error. 1731 5 - Attribute Length Error. 1732 6 - Invalid Attribute." 1733 ::= { tripMIBNotifObjects 5 } 1735 -- 1736 -- Notifications 1737 -- 1738 tripEstablished NOTIFICATION-TYPE 1739 OBJECTS { tripNotifApplIndex } 1740 STATUS current 1741 DESCRIPTION 1742 "The TRIP Established event is generated when the TRIP 1743 FSM enters the ESTABLISHED state." 1744 ::= { tripMIBNotifications 1 } 1746 tripFSM NOTIFICATION-TYPE 1747 OBJECTS { tripNotifApplIndex, 1748 tripNotifPeerAddrInetType, 1749 tripNotifPeerAddr, 1750 tripNotifPeerErrCode, 1751 tripNotifPeerErrSubcode, 1752 tripPeerState 1753 } 1754 STATUS current 1755 DESCRIPTION 1756 "The trip FSM Event is generated when any error is 1757 detected by the TRIP Finite State Machine." 1758 ::= { tripMIBNotifications 2 } 1760 tripOpenMessageError NOTIFICATION-TYPE 1761 OBJECTS { tripNotifApplIndex, 1762 tripNotifPeerAddrInetType, 1763 tripNotifPeerAddr, 1764 tripNotifPeerErrCode, 1765 tripNotifPeerErrSubcode, 1766 tripPeerState 1767 } 1768 STATUS current 1769 DESCRIPTION 1771 Zinman/Walker/Jiang 33 1772 "Errors detected while processing the OPEN message." 1773 ::= { tripMIBNotifications 3 } 1775 tripUpdateMessageError NOTIFICATION-TYPE 1776 OBJECTS { tripNotifApplIndex, 1777 tripNotifPeerAddrInetType, 1778 tripNotifPeerAddr, 1779 tripNotifPeerErrCode, 1780 tripNotifPeerErrSubcode, 1781 tripPeerState 1782 } 1783 STATUS current 1784 DESCRIPTION 1785 "Errors detected while processing the UPDATE message." 1786 ::= { tripMIBNotifications 4 } 1788 tripHoldTimerExpired NOTIFICATION-TYPE 1789 OBJECTS { tripNotifApplIndex, 1790 tripNotifPeerAddrInetType, 1791 tripNotifPeerAddr, 1792 tripNotifPeerErrCode, 1793 tripNotifPeerErrSubcode, 1794 tripPeerState 1795 } 1796 STATUS current 1797 DESCRIPTION 1798 "The system does not receive successive messages within 1799 the period specified by the negotiated Hold Time." 1800 ::= { tripMIBNotifications 5 } 1802 tripConnectionCollision NOTIFICATION-TYPE 1803 OBJECTS { tripNotifApplIndex } 1804 STATUS current 1805 DESCRIPTION 1806 "A pair of LSs tried to simultaneously to establish a 1807 transport connection to each other." 1808 ::= { tripMIBNotifications 6 } 1810 tripNotificationErr NOTIFICATION-TYPE 1811 OBJECTS { tripNotifApplIndex } 1812 STATUS current 1813 DESCRIPTION 1814 "Generated if there is an error detected in a TRIP 1815 notification message sent with another cause. Note that 1816 the TRIP notification refered to in this object is not 1817 an SNMP notification, it is a specific message described 1818 in the TRIP specification." 1819 REFERENCE 1820 "RFC 3219, section 6.4." 1821 ::= { tripMIBNotifications 7 } 1823 -- 1825 Zinman/Walker/Jiang 34 1826 -- Compliance Statements 1827 -- 1828 tripCompliance MODULE-COMPLIANCE 1829 STATUS current 1830 DESCRIPTION 1831 "The compliance statement for TRIP entities." 1833 MODULE -- this module 1834 MANDATORY-GROUPS { tripConfigGroup, 1835 tripPeerTableConfigGroup, 1836 tripRouteGroup, 1837 tripItadTopologyGroup, 1838 tripPeerTableStatsGroup } 1840 GROUP tripNotificationGroup 1841 DESCRIPTION 1842 "This group is optional. A TRIP entity can choose not to 1843 send any notifications. If this group is implemented, 1844 the tripNotifObjectGroup must also be implemented." 1846 GROUP tripNotifObjectGroup 1847 DESCRIPTION 1848 "This group is optional. A TRIP entity can choose not to 1849 send any notifications. If this group is implemented, 1850 the tripNotificationGroup must also be implemented." 1852 MODULE NETWORK-SERVICES-MIB 1853 MANDATORY-GROUPS { applGroup } 1855 ::= { tripMIBCompliance 1 } 1857 -- 1858 -- Object and event conformance groups 1859 -- 1861 tripConfigGroup OBJECT-GROUP 1862 OBJECTS { 1863 tripCfgProtocolVersion, 1864 tripCfgItad, 1865 tripCfgIdentifier, 1866 tripCfgOperStatus, 1867 tripCfgAdminStatus, 1868 tripCfgAddrIAddrType, 1869 tripCfgAddr, 1870 tripCfgPort, 1871 tripCfgMinItadOriginationInterval, 1872 tripCfgMinRouteAdvertisementInterval, 1873 tripCfgMaxPurgeTime, 1874 tripCfgDisableTime, 1875 tripCfgSendReceiveMode, 1876 tripSupportedCommunityItad, 1877 tripSupportedCommunityStorage, 1879 Zinman/Walker/Jiang 35 1880 tripRouteTypeAddrFamilyId, 1881 tripSupportedCommunityRowStatus 1882 } 1883 STATUS current 1884 DESCRIPTION 1885 "The global objects for configuring trip." 1886 ::= { tripMIBGroups 1 } 1888 tripPeerTableConfigGroup OBJECT-GROUP 1889 OBJECTS { 1890 tripPeerIdentifier, 1891 tripPeerState, 1892 tripPeerAdminStatus, 1893 tripPeerNegotiatedVersion, 1894 tripPeerSendReceiveMode, 1895 tripPeerRemoteItad, 1896 tripPeerConnectRetryInterval, 1897 tripPeerMaxRetryInterval, 1898 tripPeerHoldTime, 1899 tripPeerKeepAlive, 1900 tripPeerHoldTimeConfigured, 1901 tripPeerKeepAliveConfigured, 1902 tripPeerMaxPurgeTime, 1903 tripPeerDisableTime, 1904 tripPeerLearned, 1905 tripPeerStorage, 1906 tripPeerRtTypeAddrFamilyId, 1907 tripPeerRowStatus 1908 } 1910 STATUS current 1911 DESCRIPTION 1912 "The global objects for configuring the TRIP peer 1913 table." 1914 ::= { tripMIBGroups 2 } 1916 tripPeerTableStatsGroup OBJECT-GROUP 1917 OBJECTS { 1918 tripPeerInUpdates, 1919 tripPeerOutUpdates, 1920 tripPeerInTotalMessages, 1921 tripPeerOutTotalMessages, 1922 tripPeerFsmEstablishedTransitions, 1923 tripPeerFsmEstablishedTime, 1924 tripPeerInUpdateElapsedTime, 1925 tripPeerStateChangeTime 1926 } 1927 STATUS current 1928 DESCRIPTION 1929 "The global statistics the TRIP peer table." 1930 ::= { tripMIBGroups 3 } 1932 Zinman/Walker/Jiang 36 1933 tripRouteGroup OBJECT-GROUP 1934 OBJECTS { 1935 tripRouteTRIBMask, 1936 tripRouteAddressSequenceNumber, 1937 tripRouteAddressOriginatorId, 1938 tripRouteNextHopServerIAddrType, 1939 tripRouteNextHopServer, 1940 tripRouteNextHopServerPort, 1941 tripRouteNextHopServerItad, 1942 tripRouteMultiExitDisc, 1943 tripRouteLocalPref, 1944 tripRouteAdvertisementPath, 1945 tripRouteRoutedPath, 1946 tripRouteAtomicAggregate, 1947 tripRouteUnknown, 1948 tripRouteWithdrawn, 1949 tripRouteConverted, 1950 tripRouteReceivedTime, 1951 tripRouteCommunityItad 1952 } 1954 STATUS current 1955 DESCRIPTION 1956 "The global objects for configuring route attribute." 1957 ::= { tripMIBGroups 4 } 1959 tripItadTopologyGroup OBJECT-GROUP 1960 OBJECTS { 1961 tripItadTopologySeqNum, 1962 tripItadTopologyId 1963 } 1964 STATUS current 1965 DESCRIPTION 1966 "The objects that define the TRIP ITAD topology." 1967 ::= { tripMIBGroups 5 } 1969 tripNotificationGroup NOTIFICATION-GROUP 1970 NOTIFICATIONS { 1971 tripEstablished, 1972 tripFSM, 1973 tripOpenMessageError, 1974 tripUpdateMessageError, 1975 tripHoldTimerExpired, 1976 tripConnectionCollision, 1977 tripNotificationErr 1978 } 1979 STATUS current 1980 DESCRIPTION 1981 "A collection of notifications defined for TRIP." 1982 ::= { tripMIBGroups 6 } 1984 tripNotifObjectGroup OBJECT-GROUP 1986 Zinman/Walker/Jiang 37 1987 OBJECTS { 1988 tripNotifApplIndex, 1989 tripNotifPeerAddrInetType, 1990 tripNotifPeerAddr, 1991 tripNotifPeerErrCode, 1992 tripNotifPeerErrSubcode 1993 } 1994 STATUS current 1995 DESCRIPTION 1996 "The collection of objects that specify information for 1997 TRIP notifications." 1998 ::= { tripMIBGroups 7 } 2000 END 2002 7. Security Considerations 2004 There are a number of management objects defined in this MIB that 2005 have a MAX-ACCESS clause of read-write and/or read-create. Such 2006 objects may be considered sensitive or vulnerable in some network 2007 environments. The support for SET operations in a non-secure 2008 environment without proper protection can have a negative effect on 2009 network operations. 2011 The managed objects in this MIB contain sensitive information since, 2012 collectively, they allow tracing and influencing of connections in 2013 TRIP devices and provide information of their connection 2014 characteristics. 2016 It is thus important to control even GET access to these objects and 2017 possibly to even encrypt the values of these object when sending 2018 them over the network via SNMP. Not all versions of SNMP provide 2019 features for such a secure environment. 2021 SNMPv1 by itself is not a secure environment. Even if the network 2022 itself is secure (for example by using IPSec), even then, there is 2023 no control as to who on the secure network is allowed to access and 2024 GET/SET (read/change/create/delete) the objects in this MIB. 2026 It is recommended that the implementers consider the security 2027 features as provided by the SNMPv3 framework. Specifically, the use 2028 of the User-based Security Model RFC 2574 [RFC2574] and the View- 2029 based Access Control Model RFC 2575 [RFC2575] is recommended. 2031 It is then a customer/user responsibility to ensure that the SNMP 2032 entity giving access to an instance of this MIB, is properly 2033 configured to give access to the objects only to those principals 2034 users) that have legitimate rights to indeed GET or SET 2035 (change/create/delete) them. 2037 Zinman/Walker/Jiang 38 2038 8. Revision History 2040 8.1. Changes from 2042 o Removed tripRouteAddressLen from the tripRouteTable. 2043 o Made use of INET-ADDRESS-MIB and it's TC's for IPv6 compliance. 2044 o Changed order of the enumeration of tripPeerSendReceiveMode to 2045 comform to TRIP draft. 2046 o Added objects tripPeerCircuitCapacity and tripPeerDSPCapacity to 2047 support TRIP for Gateways [24]. 2048 o Removed tripPeerLastError and tripPeerState objects for 2049 tripEstablished notification. 2050 o Added local community object. 2051 o Added communities table for TRIP routes and removed community 2052 object from route table. 2053 o Added send/receive capability to local LS. 2054 o Added tripRouteAddressFamily as an Index to TripRouteEntry. 2055 o Changed enumerations in tripRouteAddressFamily to decimal(1) and 2056 hexaDecimal(2). 2057 o Support for authentication mechanism from draft-ietf-iptel-trip- 2058 authen-00.txt. 2059 o Changed name of tripRoutePathSegment to 2060 tripRouteRoutedPathSegment. 2061 o Added tripRouteConverted to the routing table to signify a 2062 Converted Route. 2063 o Changed DEFVAL of tripPeerConnectRetryInterval from 60 to 120 2064 seconds. 2065 o Added DEFVAL to tripPeerKeepAlive of 30 seconds. 2066 o Added DEFVAL to tripMaxPurgeTime and tripPeerMaxPurgeTime of 10 2067 seconds. 2068 o Added DEFVAL to tripDisableTime and tripPeerDisableTime of 180 2069 seconds. 2070 o Changed DEFVAL of tripMinItadOriginationInterval and 2071 tripPeerMinItadOriginationInterval to 30 seconds. 2072 o Removed tripHoldTimeConfigured and tripKeepAliveConfigured from 2073 TripCfgEntry. 2074 o changed names from opMode to sendReceiveMode. 2076 8.2. Changes from 2078 o Added tripOperStatus. 2079 o Changed definition of textual convention TripAppProtocol to 2080 OBJECT IDENTIFIER. See [RFC3219] section 13.4 2081 o Changed definition of textual convention TripAddressFamily to 2082 OBJECT IDENTIFIER. See [RFC3219] section 13.3 2083 o Added object identifiers for tripSupportedProtocols and 2084 tripAddressFamilies. 2085 o Removed authentication tables. 2086 o Removed textual convention TripPublicKey. 2087 o Changed the position of the MIB branches slightly. 2088 o Changed name of tripPeerLastError to tripNotifPeerErrCode and 2089 MAX-ACCESS to accessible-for-notify. 2091 Zinman/Walker/Jiang 39 2092 o Separated tripNotifPeerErrSubcode from tripNotifPeerErrCode and 2093 made them both integers. 2094 o Added compliance statements. 2095 o Changed MAX-ACCESS of tripPeerRemoteItad to read-create. 2096 o Changed DEFVAL of tripPeerHoldTimeConfigured from 90 to 240. 2098 8.3. Changes from 2100 o Changed tripSupportedProtocols and tripAddressFamilies from 2101 OBJECT IDENTIFIER to OBJECT-IDENTITY. 2102 o Added tripRouteTRIBMask with syntax BITS to identify the type of 2103 TRIB the route belongs to. 2104 o Removed tripMinItadOriginationInterval and 2105 tripMinRouteAdvertisementInterval from the tripCfgTable because 2106 they also exist in the Peer table. 2107 o TripPeerRemoteItad made read-only because either the local 2108 application will determine the value. 2109 o Add tripRouteTypeTable as a sub-table to tripCfgTable (similar to 2110 tripPeerRouteTypeTable). 2111 o Add timestamp to route table (when received), and last change 2112 of peer state. 2113 o Removed tripRouteBest since the best would be represented by 2114 LocTRIB or AdjTRIBOut 2116 8.4. Changes from 2118 o Reworded chapter 5 to reflect the use of NETWORK-SERVICES-MIB. 2119 o Removed some rowStatus objects that were not needed. 2120 o Added the branch tripMIBNotifObjects to hold the notification 2121 objects. 2122 o Added the branch tripMIBAdmin to hold TRIP address families and 2123 TRIP supported protocols. 2124 o Document now references RFC 3219 for TRIP. 2125 o General cleanup of descriptions. 2126 o Made descriptors for consistent by using the first part of the 2127 table name as a prefix. 2128 o Added objects with the StorageType textual convention for 2129 read-create tables. 2130 o Updated the references section to conform to IETF specifications. 2131 o Added full copyright statement. 2133 9. Full Copyright Statement 2135 Copyright (C) The Internet Society (2002). All Rights Reserved. 2136 This document and translations of it may be copied and furnished to 2137 others, and derivative works that comment on or otherwise explain it 2138 or assist in its implementation may be prepared, copied, published 2139 and distributed, in whole or in part, without restriction of any 2140 kind, provided that the above copyright notice and this paragraph 2141 are included on all such copies and derivative works. However, this 2142 document itself may not be modified in any way, such as by removing 2143 the copyright notice or references to the Internet Society or other 2145 Zinman/Walker/Jiang 40 2146 Internet organizations, except as needed for the purpose of 2147 developing Internet standards in which case the procedures for 2148 copyrights defined in the Internet Standards process must be 2149 followed, or as required to translate it into languages other than 2150 English. 2152 The limited permissions granted above are perpetual and will not be 2153 revoked by the Internet Society or its successors or assigns. 2155 This document and the information contained herein is provided on an 2156 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2157 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2158 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2159 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2160 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2162 10. References 2164 [RFC3219] Rosenberg, J., Salama, H. and Squire, M., "Telephony 2165 Routing over IP (TRIP)", RFC 3219 January 2002. 2167 [RFC1771] Rekhter, Y. and Li, T., "Border Gateway Protocol 4 2168 (BGP-4)", RFC 1771, March 1995. 2170 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2171 Architecture for Describing SNMP Management Frameworks", 2172 RFC 2571, April 1999. 2174 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2175 Identification of Management Information for 2176 TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 2178 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2179 STD 16, RFC 1212, March 1991. 2181 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 2182 the SNMP", RFC 1215, March 1991. 2184 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2185 Case, J., Rose, M., and S. Waldbusser, "Structure of 2186 Management Information Version 2 (SMIv2)", STD 58, 2187 RFC 2578, April 1999. 2189 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2190 J., Rose, M., and S. Waldbusser, "Textual Conventions 2191 for SMIv2", STD 58, RFC 2579, April 1999. 2193 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2194 Case, J., Rose, M., and S. Waldbusser, "Conformance 2195 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2197 Zinman/Walker/Jiang 41 2199 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2200 "Simple Network Management Protocol", STD 15, RFC 1157, 2201 May 1990. 2203 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2204 "Introduction to Community-based SNMPv2", RFC 1901, 2205 January 1996. 2207 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2208 "Transport Mappings for Version 2 of the Simple Network 2209 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2211 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2212 "Message Processing and Dispatching for the Simple 2213 Network Management Protocol (SNMP)", RFC 2572, April 2214 1999. 2216 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2217 Model (USM) for version 3 of the Simple Network 2218 Management Protocol (SNMPv3)", RFC 2574, April 1999. 2220 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2221 "Protocol Operations for Version 2 of the Simple Network 2222 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2224 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2225 Applications", RFC 2573, April 1999. 2227 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2228 Access Control Model (VACM) for the Simple Network 2229 Management Protocol (SNMP)", RFC 2575, April 1999. 2231 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2232 "Introduction to Version 3 of the Internet-standard 2233 Network Management Framework", RFC 2570, April 1999. 2235 [RFC2788] Freed, N., Kille, s., "Network Services Monitoring MIB", 2236 RFC 2788, March 2000. 2238 [BCP0014] Bradner, S., "Key words for use in RFCs to Indicate 2239 Requirement Levels", BCP 14, RFC 2119, March 1997. 2241 11. Author's Addresses 2243 David Zinman 2244 phone: +1 613 791 2841 2245 Email: dzinman@sympatico.ca 2247 Dave Walker 2248 SS8 Networks, Inc. 2250 Zinman/Walker/Jiang 42 2251 495 March Road, Suite #500 2252 Ottawa, ON K2K 3G1 2253 Canada 2254 Phone: +1 613 592 2100 2255 Email: drwalker@ss8.com 2257 Jianping Jiang 2258 SS8 Networks, Inc. 2259 495 March Road, Suite #500 2260 Ottawa, ON K2K 3G1 2261 Canada 2262 Phone: +1 613 592 2100 2263 Email: jianping@ss8.com 2265 12. Working Group 2267 IP Telephony (iptel) Working Group 2268 ================================== 2270 Mailing list: iptel@lists.bell-labs.com 2272 Chair: 2273 Jonathan Rosenberg 2275 Transport Area Directors: 2276 Scott Bradner 2277 Allison Mankin mankin@east.isi.edu 2279 Zinman/Walker/Jiang 43