idnits 2.17.1 draft-ietf-iptel-trip-mib-00.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 == The page length should not exceed 58 lines per page, but there was 38 longer pages, the longest (page 2) being 59 lines 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 ([2], [3], [4]), 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 seems to have 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.) -- The document date (August 2001) is 8289 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 16 looks like a reference -- Missing reference section? '2' on line 1956 looks like a reference -- Missing reference section? '3' on line 41 looks like a reference -- Missing reference section? '4' on line 43 looks like a reference -- Missing reference section? '5' on line 80 looks like a reference -- Missing reference section? '6' on line 86 looks like a reference -- Missing reference section? '7' on line 91 looks like a reference -- Missing reference section? '8' on line 91 looks like a reference -- Missing reference section? '9' on line 91 looks like a reference -- Missing reference section? '10' on line 93 looks like a reference -- Missing reference section? '11' on line 93 looks like a reference -- Missing reference section? '12' on line 93 looks like a reference -- Missing reference section? '13' on line 107 looks like a reference -- Missing reference section? '14' on line 99 looks like a reference -- Missing reference section? '15' on line 101 looks like a reference -- Missing reference section? '21' on line 101 looks like a reference -- Missing reference section? '19' on line 1901 looks like a reference -- Missing reference section? '16' on line 109 looks like a reference -- Missing reference section? '22' on line 112 looks like a reference -- Missing reference section? '17' on line 1902 looks like a reference -- Missing reference section? '24' on line 1919 looks like a reference -- Missing reference section? '18' on line 142 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 24 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Jiang 3 Internet Draft D. Walker 4 Document: draft-ietf-iptel-trip-mib-00.txt D. Zinman 5 Expires: February 2002 SS8 Networks, Inc 6 August 2001 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 RFC2026 [1]. 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 reference 25 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 Abstract 35 This memo defines a portion of the Management Information Base (MIB) 36 for use with network management protocols in the Internet community. 37 In particular, it describes a set of managed objects that are used 38 to manage for Telephony Routing over IP (TRIP) [2] devices. 40 Since TRIP [2] is modelled after the Border Gateway Protocol (BGP-4) 41 [3], the managed objects for TRIP are also modelled after RFC1657 - 42 Definitions of Managed Objects for the Fourth Version of the Border 43 Gateway Protocol (BGP-4) using SMIv2 [4]. 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 51 3. The SNMP Management Framework....................................2 53 Jiang/Walker/Zinman 1 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.........................................35 59 8. Revision History................................................36 60 8.1. Changes from .....................36 61 8.2. Changes from .....................36 62 9. References......................................................37 63 10. Author's Address................................................38 64 11. Intellectual Property...........................................39 65 12. Full Copyright Statement........................................39 67 1. Introduction 69 This memo defines a portion of the Management Information Base 70 (MIB)for use with network management protocols in the Internet 71 community. In particular, it describes a set of managed objects that 72 are used to schedule management operations periodically or at 73 specified dates and times. 75 2. Conventions used in this document 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 79 this document are to be interpreted as described in RFC-2119 [5]. 81 3. The SNMP Management Framework 83 The SNMP Management Framework presently consists of five major 84 components: 86 o An overall architecture, described in RFC 2571 [6]. 88 o Mechanisms for describing and naming objects and events for the 89 purpose of management. The first version of this Structure of 90 Management Information (SMI) is called SMIv1 and described in 91 STD 16, RFC 1155 [7], STD 16, RFC 1212 [8] and RFC 1215 [9]. 92 The second version, called SMIv2, is described in STD 58, RFC 93 2578 [10], STD 58, RFC 2579 [11] and STD 58, RFC 2580 [12]. 95 o Message protocols for transferring management information. The 96 first version of the SNMP message protocol is called SNMPv1 and 97 described in STD 15, RFC 1157 [13]. A second version of the 98 SNMP message protocol, which is not an Internet standards track 99 protocol, is called SNMPv2c and described in RFC 1901 [14] and 100 RFC 1906 [15]. The third version of the message protocol is 101 called SNMPv3 and described in RFC 1906 [15], RFC 2572 [21] and 102 RFC 2574 [19]. 104 Jiang/Walker/Zinman 2 105 o Protocol operations for accessing management information. The 106 first set of protocol operations and associated PDU formats is 107 described in STD 15, RFC 1157 [13]. A second set of protocol 108 operations and associated PDU formats is described in RFC 1905 109 [16]. 111 o A set of fundamental applications described in RFC 2573 112 [22] and the view-based access control mechanism described 113 in RFC 2575 [17]. 115 A more detailed introduction to the current SNMP Management 116 Framework can be found in RFC 2570 [24]. 118 Managed objects are accessed via a virtual information store, termed 119 the Management Information Base or MIB. Objects in the MIB are 120 defined using the mechanisms defined in the SMI. 122 This memo specifies a MIB module that is compliant to the SMIv2. A 123 MIB conforming to the SMIv1 can be produced through the appropriate 124 translations. The resulting translated MIB must be semantically 125 equivalent, except where objects or events are omitted because no 126 translation is possible (use of Counter64). Some machine readable 127 information in SMIv2 will be converted into textual descriptions in 128 SMIv1 during the translation process. However, this loss of machine 129 readable information is not considered to change the semantics of 130 the MIB. 132 4. Overview 134 Telephony Routing over IP (TRIP) [2] is an inter-domain application- 135 layer control protocol that exchanges information with other TRIP 136 gateways to provide efficient IP telephony routing. This MIB 137 provides some managed objects for TRIP devices defined in Telephony 138 Routing over IP . 140 5. Structure of TRIP MIB 142 This MIB utilizes the framework described in RFC 2788 [18] for 143 management of multiple instances of TRIP from a single entity. The 144 Network Services Monitoring MIB applTable will be populated with 145 entries corresponding to each TRIP entity in the system. Each entity 146 will then have an applIndex associated with it. The value assigned 147 to applIndex will represent the distinct instance of TRIP. 149 The MIB defines some system-wide scalar objects local to the TRIP 150 instance, as well as 5 tables: the Trip Peer Table, the Trip Peer 151 Stats Table, the Trip Route Table, the Trip Route Community Table, 152 the Trip ITAD Topology Table, and the Trip ITAD Topology ID Table. 154 The Trip Peer Table contains information about the state and current 155 activity of the connections with TRIP peers. The Trip Peer Stats 157 Jiang/Walker/Zinman 3 158 Table augments the Trip Peer Table and contains statistics related 159 to the connections with TRIP peers. 161 The Trip Route Table contains information on the route to a peers 162 destination. The Trip Route Community Table contains information on 163 the communities associated with each route. 165 The Trip ITAD Topology Table contains information on the sequence of 166 link connections between peers within an ITAD. The Trip ITAD 167 Topology ID Table is a subtable of the Trip ITAD Topology Table and 168 contains the list of location servers within the ITAD domain that 169 the instance of this trip ITAD Topology currently peering. 171 5.1. Textual Conventions 173 The data types TripItad and TripId are used as textual conventions 174 in this document. A TRIP ITAD is described in [2]. A TRIP ID is used 175 as a distinct identifier for a TRIP entity. A TripAppProtocol is 176 used to identify an application protocol. A TripAddressFamily is 177 used to define an address family. both TripAppProtocol and 178 TripAddressFamily are OBJECT IDENTIFIERS and as such, a MIB 179 implementor can define a private object of this type of textual 180 convention. Objects defined using these conventions are always 181 encoded by means of the rules that define their primitive type. 182 Hence, no changes to the SMI or the SNMP are necessary to 183 accommodate these textual conventions which are adopted merely for 184 the convenience of readers. 186 6. TRIP MIB 188 TRIP-MIB DEFINITIONS ::= BEGIN 190 IMPORTS 191 MODULE-IDENTITY, 192 OBJECT-TYPE, 193 NOTIFICATION-TYPE, 194 Unsigned32, 195 Integer32, 196 Gauge32, 197 Counter32, 198 mib-2 199 FROM SNMPv2-SMI 201 TEXTUAL-CONVENTION, 202 DateAndTime, 203 TruthValue, 204 RowStatus 205 FROM SNMPv2-TC 207 OBJECT-GROUP, 209 Jiang/Walker/Zinman 4 210 MODULE-COMPLIANCE, 211 NOTIFICATION-GROUP 212 FROM SNMPv2-CONF 214 InetAddressType, 215 InetAddress 216 FROM INET-ADDRESS-MIB 218 applIndex 219 FROM NETWORK-SERVICES-MIB; 221 tripMIB MODULE-IDENTITY 222 LAST-UPDATED "200108200000Z" 223 ORGANIZATION "IETF IPTel Working Group" 224 CONTACT-INFO 225 "Co-editor Jianping Jiang 226 SS8 Networks, Inc. 227 postal: 55 Commerce Valley Drive West, Suite #510 228 Thornhill, ON, L3T 7B9 Canada 229 email: jianping@ss8.com 230 phone: +1 905 889 5900 232 Co-editor Dave Walker 233 SS8 Networks, Inc. 234 postal: 495 March Road, Suite #500 235 Ottawa, ON, K2K 3G1 Canada 236 email: drwalker@ss8.com 237 phone: +1 613 592 2100 239 Co-editor David Zinman 240 SS8 Networks, Inc. 241 postal: 495 March Road, Suite #500 242 Ottawa, ON, K2K 3G1 Canada 243 email: david@ss8.com 244 phone: +1 613 592 2100 246 IP Telephony (iptel) Working Group 247 ================================== 248 Chair: 249 Jonathan Rosenberg 251 Transport Area Directors: 252 Scott Bradner 253 Allison Mankin 255 Transport Area Advisor: 256 Scott Bradner 258 Mailing List 259 ============ 261 Jiang/Walker/Zinman 5 262 iptel-admin@lists.bell-labs.com 264 General information about the mailing list is at: 265 http://lists.bell-labs.com/mailman/listinfo/iptel/ 267 Archives: 268 http://lists.bell-labs.com/pipermail/iptel/" 270 DESCRIPTION 271 "The MIB module describing Telephony Routing 272 over IP (TRIP)" 273 REVISION "200102260000Z" 274 DESCRIPTION 275 "The initial revision of this MIB module was 276 published as draft-zinman-trip-mib-00.txt." 277 ::= { mib-2 } -- to be assigned by IANA 279 -- 280 -- Textual Conventions 281 -- 282 TripItad ::= TEXTUAL-CONVENTION 283 STATUS current 284 DESCRIPTION 285 "The values for identifying the IP Telephony 286 Administrative Domain." 287 SYNTAX Unsigned32 (0..4294967295) 289 TripId ::= TEXTUAL-CONVENTION 290 STATUS current 291 DESCRIPTION 292 "The range of legal values for a TRIP Identifier." 293 SYNTAX Unsigned32 (0..4294967295) 295 TripAppProtocol ::= TEXTUAL-CONVENTION 296 STATUS current 297 DESCRIPTION 298 "The application protocol used for communication with 299 TRIP LS's. Protocol defined in this document are: 300 tripSupProtSIP 301 tripSupProtH323Q931 302 tripSupProtH323RAS 303 tripSupProtH323ANNEXG. 305 Users can add their own application protocol types by defining 306 a TripAppProtocol type in a private specification." 307 SYNTAX OBJECT IDENTIFIER 309 TripAddressFamily ::= TEXTUAL-CONVENTION 310 STATUS current 311 DESCRIPTION 312 "A type of address for a TRIP route. Address families defined 313 within this document are: 314 tripAddrFamilyDecimal 316 Jiang/Walker/Zinman 6 317 tripAddrFamilyPentadecimal 318 tripAddrFamilyE164. 320 Users can add their own address family types by defining a 321 TripAddressFamily type in a private specification." 322 SYNTAX OBJECT IDENTIFIER 324 tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 } 325 tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 } 326 tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 } 327 tripMIBCompliance OBJECT IDENTIFIER ::= { tripMIBConformance 1 } 328 tripMIBGroups OBJECT IDENTIFIER ::= { tripMIBConformance 2 } 330 -- 331 -- Supported protocols 332 -- 333 tripSupportedProtocols OBJECT IDENTIFIER ::= { tripMIBObjects 100 } 335 tripSupProtSIP 336 OBJECT IDENTIFIER ::= { tripSupportedProtocols 1 } 337 tripSupProtH323Q931 338 OBJECT IDENTIFIER ::= { tripSupportedProtocols 2 } 339 tripSupProtH323RAS 340 OBJECT IDENTIFIER ::= { tripSupportedProtocols 3 } 341 tripSupProtH323ANNEXG 342 OBJECT IDENTIFIER ::= { tripSupportedProtocols 4 } 344 -- 345 -- Address Families 346 -- 347 tripAddressFamilies OBJECT IDENTIFIER ::= { tripMIBObjects 101 } 349 tripAddrFamilyDecimal 350 OBJECT IDENTIFIER ::= { tripAddressFamilies 1 } 351 tripAddrFamilyPentadecimal 352 OBJECT IDENTIFIER ::= { tripAddressFamilies 2 } 353 tripAddrFamilyE164 354 OBJECT IDENTIFIER ::= { tripAddressFamilies 3 } 356 -- 357 -- tripCfgTable 358 -- 359 tripCfgTable OBJECT-TYPE 360 SYNTAX SEQUENCE OF TripCfgEntry 361 MAX-ACCESS not-accessible 362 STATUS current 363 DESCRIPTION 364 "This table contains the common configuration objects 365 applicable to all TRIP entities. Each row represents 366 those objects for a particular TRIP LS present in 367 this system. The instances of TRIP LS's are 368 uniquely identified by applIndex." 370 Jiang/Walker/Zinman 7 371 ::= { tripMIBObjects 1 } 373 tripCfgEntry OBJECT-TYPE 374 SYNTAX TripCfgEntry 375 MAX-ACCESS not-accessible 376 STATUS current 377 DESCRIPTION 378 "A row of common configuration." 379 INDEX { applIndex } 380 ::= { tripCfgTable 1 } 382 TripCfgEntry ::= 383 SEQUENCE { 384 tripProtocolVersion Integer32, 385 tripLocalItad TripItad, 386 tripIdentifier TripId, 387 tripOperStatus INTEGER, 388 tripAdminStatus INTEGER, 389 tripLocalAddrIAddrType InetAddressType, 390 tripLocalAddr InetAddress, 391 tripLocalPort Integer32, 392 tripMinItadOriginationInterval Integer32, 393 tripMinRouteAdvertisementInterval Integer32, 394 tripMaxPurgeTime Integer32, 395 tripDisableTime Integer32, 396 tripSendReceiveMode INTEGER 397 } 399 tripProtocolVersion OBJECT-TYPE 400 SYNTAX Integer32 (1..255) 401 MAX-ACCESS read-only 402 STATUS current 403 DESCRIPTION 404 "This object will reflect the version of TRIP 405 supported by this system. It follows the same 406 format as TRIP version information contained 407 in the TRIP messages generated by this TRIP entity 408 as dictated by draft-ietf-iptel-trip-07.txt." 409 ::= { tripCfgEntry 1 } 411 tripLocalItad OBJECT-TYPE 412 SYNTAX TripItad 413 MAX-ACCESS read-write 414 STATUS current 415 DESCRIPTION 416 "The Local Internet Telephony Administrative domain." 417 ::= { tripCfgEntry 2 } 419 tripIdentifier OBJECT-TYPE 420 SYNTAX TripId 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 425 Jiang/Walker/Zinman 8 426 "The object that identifies this TRIP Client." 427 ::= { tripCfgEntry 3 } 429 tripAdminStatus OBJECT-TYPE 430 SYNTAX INTEGER { 431 up(1), 432 down(2) 433 } 434 MAX-ACCESS read-write 435 STATUS current 436 DESCRIPTION 437 "The desired TRIP state. 439 up(1) : Set the application to normal operation. 441 down(2): Set the application to a state where it will not 442 process TRIP messages." 443 ::= { tripCfgEntry 4 } 445 tripOperStatus OBJECT-TYPE 446 SYNTAX INTEGER { 447 up(1), 448 down(2) 449 } 450 MAX-ACCESS read-write 451 STATUS current 452 DESCRIPTION 453 "The current operational state of the TRIP protocol. 455 up(1) : The application is operating normally, and 456 is processing (receiving and possibly 457 issuing) TRIP requests and responses. 459 down(2): The application is currently unable to 460 process TRIP messages due to a fault or if 461 TRIP is in an initialization state. 463 If tripAdminStatus is down(2) then tripOperStatus should be 464 down(2). If tripAdminStatus is changed to up(1) then 465 tripOperStatus should change to up(1) if there is no fault 466 that prevents the TRIP protocol from moving to the up(1) 467 state." 468 ::= { tripCfgEntry 5 } 470 tripLocalAddrIAddrType OBJECT-TYPE 471 SYNTAX InetAddressType 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "The type of Inet Address of the tripLocalAddr." 476 REFERENCE 477 "RFC 2851, section 3." 478 ::= { tripCfgEntry 6 } 480 Jiang/Walker/Zinman 9 481 tripLocalAddr OBJECT-TYPE 482 SYNTAX InetAddress 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "The IP address of this entry's TRIP peer connection." 487 REFERENCE 488 "RFC 2851, section 3." 489 ::= { tripCfgEntry 7 } 491 tripLocalPort OBJECT-TYPE 492 SYNTAX Integer32 (1..65535) 493 MAX-ACCESS read-write 494 STATUS current 495 DESCRIPTION 496 "The local port that this entry's TRIP peer is using." 497 ::= { tripCfgEntry 8 } 499 tripMinItadOriginationInterval OBJECT-TYPE 500 SYNTAX Integer32 (1..2147483647) 501 UNITS "Seconds" 502 MAX-ACCESS read-write 503 STATUS current 504 DESCRIPTION 505 "Amount of time that must elapse between advertisement 506 of update message that report changes within the 507 Location Server's own ITAD." 508 DEFVAL { 30 } 509 ::= { tripCfgEntry 9 } 511 tripMinRouteAdvertisementInterval OBJECT-TYPE 512 SYNTAX Integer32 (1..2147483647) 513 UNITS "Seconds" 514 MAX-ACCESS read-write 515 STATUS current 516 DESCRIPTION 517 "Specifies minimal interval between successive 518 advertisement to a particular destination from an LS." 519 DEFVAL { 30 } 520 ::= { tripCfgEntry 10 } 522 tripMaxPurgeTime OBJECT-TYPE 523 SYNTAX Integer32 (1..65535) 524 UNITS "Seconds" 525 MAX-ACCESS read-write 526 STATUS current 527 DESCRIPTION 528 "Indicate the interval that the location server must 529 maintain routes marked as withdrawn in its database." 530 DEFVAL { 10 } 531 ::= { tripCfgEntry 11 } 533 Jiang/Walker/Zinman 10 534 tripDisableTime OBJECT-TYPE 535 SYNTAX Integer32 (1..65535) 536 UNITS "Seconds" 537 MAX-ACCESS read-write 538 STATUS current 539 DESCRIPTION 540 "Indicate the interval that the TRIP module of the 541 location server must be disabled while routes 542 originated by this location server with high 543 sequence numbers can be removed." 544 DEFVAL { 180 } 545 ::= { tripCfgEntry 12 } 547 tripSendReceiveMode OBJECT-TYPE 548 SYNTAX INTEGER { 549 sendReceive(1), 550 sendOnly(2), 551 receiveOnly(3) 552 } 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "The operational mode of this peer." 557 ::= { tripCfgEntry 13 } 559 -- 560 -- tripSupportedCommunityTable 561 -- 563 tripSupportedCommunityTable OBJECT-TYPE 564 SYNTAX SEQUENCE OF TripSupportedCommunityEntry 565 MAX-ACCESS not-accessible 566 STATUS current 567 DESCRIPTION 568 "The list of TRIP communities that this LS supports. A TRIP 569 community is a group of destinations that share some common 570 property. 572 The TRIP Communities attribute is used to group destinations 573 so that the routing decision can be based on the identity of 574 the group." 575 REFERENCE 576 "draft-ietf-iptel-trip-07.txt, J. Rosenberg et al, 577 section 5.9." 578 ::= { tripMIBObjects 2 } 580 tripSupportedCommunityEntry OBJECT-TYPE 581 SYNTAX TripSupportedCommunityEntry 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "Entry containing information a community. A TRIP 586 community is a group of destinations that share some 588 Jiang/Walker/Zinman 11 589 common property." 590 INDEX { applIndex, tripSupportedCommunityId } 591 ::= { tripSupportedCommunityTable 1 } 593 TripSupportedCommunityEntry ::= SEQUENCE { 594 tripSupportedCommunityId TripItad, 595 tripSupportedCommunityItad TripItad, 596 tripSupportedCommunityRowStatus RowStatus 597 } 599 tripSupportedCommunityId OBJECT-TYPE 600 SYNTAX TripItad 601 MAX-ACCESS not-accessible 602 STATUS current 603 DESCRIPTION 604 "The identifier of the supported Community." 605 ::= { tripSupportedCommunityEntry 1 } 607 tripSupportedCommunityItad OBJECT-TYPE 608 SYNTAX TripItad 609 MAX-ACCESS read-create 610 STATUS current 611 DESCRIPTION 612 "The Itad of the community." 613 ::= { tripSupportedCommunityEntry 2 } 615 tripSupportedCommunityRowStatus OBJECT-TYPE 616 SYNTAX RowStatus 617 MAX-ACCESS read-create 618 STATUS current 619 DESCRIPTION 620 "The row status of the entry. This object is required to 621 create or delete rows." 622 ::= { tripSupportedCommunityEntry 3 } 624 -- 625 -- TripPeerTable 626 -- 627 tripPeerTable OBJECT-TYPE 628 SYNTAX SEQUENCE OF TripPeerEntry 629 MAX-ACCESS not-accessible 630 STATUS current 631 DESCRIPTION 632 "The TRIP peer table. This table contains one entry per 633 TRIP peer, and information about the connection with 634 the peer." 635 ::= { tripMIBObjects 4 } 637 tripPeerEntry OBJECT-TYPE 638 SYNTAX TripPeerEntry 639 MAX-ACCESS not-accessible 640 STATUS current 642 Jiang/Walker/Zinman 12 643 DESCRIPTION 644 "Entry containing information about the connection with 645 a TRIP peer." 646 INDEX { applIndex, 647 tripPeerRemoteAddrInetType, 648 tripPeerRemoteAddr } 649 ::= {tripPeerTable 1} 651 TripPeerEntry ::= SEQUENCE { 652 tripPeerRemoteAddrInetType InetAddressType, 653 tripPeerRemoteAddr InetAddress, 654 tripPeerIdentifier TripId, 655 tripPeerState INTEGER, 656 tripPeerAdminStatus INTEGER, 657 tripPeerNegotiatedVersion Integer32, 658 tripPeerSendReceiveMode INTEGER, 659 tripPeerRemotePort Integer32, 660 tripPeerRemoteItad TripItad, 661 tripPeerConnectRetryInterval Integer32, 662 tripPeerMaxRetryInterval Integer32, 663 tripPeerHoldTime Integer32, 664 tripPeerKeepAlive Integer32, 665 tripPeerHoldTimeConfigured Integer32, 666 tripPeerKeepAliveConfigured Integer32, 667 tripPeerMinItadOriginationInterval Integer32, 668 tripPeerMinRouteAdvertisementInterval Integer32, 669 tripPeerMaxPurgeTime Integer32, 670 tripPeerDisableTime Integer32, 671 tripPeerRowStatus RowStatus 672 } 674 tripPeerRemoteAddrInetType OBJECT-TYPE 675 SYNTAX InetAddressType 676 MAX-ACCESS not-accessible 677 STATUS current 678 DESCRIPTION 679 "The type of Inet Address of the tripPeerRemoteAddr." 680 REFERENCE 681 "RFC 2851, section 3." 682 ::= { tripPeerEntry 1 } 684 tripPeerRemoteAddr OBJECT-TYPE 685 SYNTAX InetAddress (SIZE(0..125)) 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "The remote IP address of this entry's TRIP peer. The 690 size value of 125 has been assigned due to the sub 691 identifier of object types length limitation as 692 defined in SMIv2." 693 REFERENCE 694 "RFC 2851, section 3." 696 Jiang/Walker/Zinman 13 697 ::= { tripPeerEntry 2 } 699 tripPeerIdentifier OBJECT-TYPE 700 SYNTAX TripId 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 "TRIP identifier of this entry's TRIP peer." 705 ::= { tripPeerEntry 3 } 707 tripPeerState OBJECT-TYPE 708 SYNTAX INTEGER { 709 idle(1), 710 connect(2), 711 active(3), 712 openSent(4), 713 openConfirm(5), 714 established(6) 715 } 716 MAX-ACCESS read-only 717 STATUS current 718 DESCRIPTION 719 "TRIP Peer Finite State Machine state. 721 idle(1) : The initial state. Local LS refuses all 722 incoming connections. No resources are 723 allocated to the peer. 725 connect(2) : Local LS waiting for a transport protocol 726 connection to be completed to the peer, and 727 is listening for inbound transport 728 connections from the peer. 730 active(3) : LS is listening for an inbound connection 731 from the peer, but is not in the process of 732 initiating a connection to the peer. 734 openSent(4) : LS has sent an OPEN message to its peer and 735 is waiting for an OPEN message from its 736 peer. 738 openConfirm(5): LS has sent an OPEN to its peer, received an 739 OPEN from its peer, and sent a KEEPALIVE in 740 response to the OPEN. The LS is now waiting 741 for a KEEPALIVE or NOTIFICATION message in 742 response to its OPEN. 744 established(6): LS can exchange UPDATE, NOTIFICATION,and 745 KEEPALIVE messages with its peer." 746 ::= { tripPeerEntry 4 } 748 tripPeerAdminStatus OBJECT-TYPE 749 SYNTAX INTEGER { 751 Jiang/Walker/Zinman 14 752 up(1), 753 down(2) 754 } 755 MAX-ACCESS read-create 756 STATUS current 757 DESCRIPTION 758 "The desired TRIP connection state." 759 ::= { tripPeerEntry 5 } 761 tripPeerNegotiatedVersion OBJECT-TYPE 762 SYNTAX Integer32 (1..255) 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "The negotiated version of TRIP running between this 767 local entity and this peer." 768 ::= { tripPeerEntry 6 } 770 tripPeerSendReceiveMode OBJECT-TYPE 771 SYNTAX INTEGER { 772 sendReceive(1), 773 sendOnly(2), 774 receiveOnly(3) 775 } 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "The operational mode of this peer." 780 ::= { tripPeerEntry 7 } 782 tripPeerRemotePort OBJECT-TYPE 783 SYNTAX Integer32 (1..65535) 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The remote port for the TCP connection between the 788 TRIP peers." 789 ::= { tripPeerEntry 8 } 791 tripPeerRemoteItad OBJECT-TYPE 792 SYNTAX TripItad 793 MAX-ACCESS read-create 794 STATUS current 795 DESCRIPTION 796 "The Internet Telephony Administrative domain of 797 this peer." 798 ::= { tripPeerEntry 9 } 800 tripPeerConnectRetryInterval OBJECT-TYPE 801 SYNTAX Integer32 (0..2147483647) 802 UNITS "Seconds" 803 MAX-ACCESS read-create 804 STATUS current 806 Jiang/Walker/Zinman 15 807 DESCRIPTION 808 "Specifies the initial amount of time that will elapse 809 between connection retry. This value should double 810 after each attempt up to the value of 811 tripPeerMaxRetryInterval." 812 DEFVAL { 120 } 813 ::= { tripPeerEntry 10 } 815 tripPeerMaxRetryInterval OBJECT-TYPE 816 SYNTAX Integer32 (0..2147483647) 817 UNITS "Seconds" 818 MAX-ACCESS read-create 819 STATUS current 820 DESCRIPTION 821 "Specifies the maximum amount of time that will elapse 822 between connection retries." 823 DEFVAL { 360 } 824 ::= { tripPeerEntry 11 } 826 tripPeerHoldTime OBJECT-TYPE 827 SYNTAX Integer32 (1..2147483647) 828 UNITS "Seconds" 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "The time interval in seconds for the hold timer that 833 is established with the peer. The value of this object 834 is the smaller of the values in 835 tripPeerHoldTimeConfigured and the hold time received 836 in the open message." 837 ::= { tripPeerEntry 12 } 839 tripPeerKeepAlive OBJECT-TYPE 840 SYNTAX Integer32 (1..2147483647) 841 UNITS "Seconds" 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "Specifies the amount of time that must elapse between 846 keep alive messages." 847 ::= { tripPeerEntry 13 } 849 tripPeerHoldTimeConfigured OBJECT-TYPE 850 SYNTAX Integer32 (0 | 3..65535) 851 UNITS "Seconds" 852 MAX-ACCESS read-create 853 STATUS current 854 DESCRIPTION 855 "Specifies the maximum time that may elapse between the 856 receipt of successive keepalive or update message." 857 DEFVAL { 240 } 858 ::= { tripPeerEntry 14 } 860 Jiang/Walker/Zinman 16 861 tripPeerKeepAliveConfigured OBJECT-TYPE 862 SYNTAX Integer32 (1..2147483647) 863 UNITS "Seconds" 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "Specifies the amount of time that must elapse between 868 keep alive messages." 869 DEFVAL { 30 } 870 ::= { tripPeerEntry 15 } 872 tripPeerMinItadOriginationInterval OBJECT-TYPE 873 SYNTAX Integer32 (0..2147483647) 874 UNITS "Seconds" 875 MAX-ACCESS read-create 876 STATUS current 877 DESCRIPTION 878 "Amount of time that must elapse between advertisement 879 of update message that report changes within the Location 880 Server's own ITAD." 881 DEFVAL { 30 } 882 ::= { tripPeerEntry 16 } 884 tripPeerMinRouteAdvertisementInterval OBJECT-TYPE 885 SYNTAX Integer32 (1..2147483647) 886 UNITS "Seconds" 887 MAX-ACCESS read-create 888 STATUS current 889 DESCRIPTION 890 "Specifies minimal interval between successive 891 advertisement to a particular destination from an LS." 892 DEFVAL { 30 } 893 ::= { tripPeerEntry 17 } 895 tripPeerMaxPurgeTime OBJECT-TYPE 896 SYNTAX Integer32 (1..65535) 897 UNITS "Seconds" 898 MAX-ACCESS read-create 899 STATUS current 900 DESCRIPTION 901 "Indicate the interval that the location server must 902 maintain routes marked as withdrawn in its database." 903 DEFVAL { 10 } 904 ::= { tripPeerEntry 18 } 906 tripPeerDisableTime OBJECT-TYPE 907 SYNTAX Integer32 (1..65535) 908 UNITS "Seconds" 909 MAX-ACCESS read-create 910 STATUS current 911 DESCRIPTION 912 "Indicate the interval that the TRIP module of the 913 location server must be disabled while routes 915 Jiang/Walker/Zinman 17 916 originated by this location server with high sequence 917 numbers can be removed." 918 DEFVAL { 180 } 919 ::= { tripPeerEntry 19 } 921 tripPeerRowStatus OBJECT-TYPE 922 SYNTAX RowStatus 923 MAX-ACCESS read-create 924 STATUS current 925 DESCRIPTION 926 "This object is used to create and delete rows in the 927 tripPeerTable." 928 ::= { tripPeerEntry 20 } 930 -- 931 -- tripPeerRouteTypeTable 932 -- 933 tripPeerRouteTypeTable OBJECT-TYPE 934 SYNTAX SEQUENCE OF TripPeerRouteTypeEntry 935 MAX-ACCESS not-accessible 936 STATUS current 937 DESCRIPTION 938 "The TRIP peer Route Type table. This table contains one 939 entry per supported protocol - address family pair." 940 ::= { tripMIBObjects 5 } 942 tripPeerRouteTypeEntry OBJECT-TYPE 943 SYNTAX TripPeerRouteTypeEntry 944 MAX-ACCESS not-accessible 945 STATUS current 946 DESCRIPTION 947 "Entry containing information about the route type that 948 the TRIP peer supports." 949 INDEX { applIndex, 950 tripPeerRemoteAddrInetType, 951 tripPeerRemoteAddr, 952 tripPeerRtTypeProtocolId, 953 tripPeerRtTypeAddrFamilyId } 954 ::= { tripPeerRouteTypeTable 1 } 956 TripPeerRouteTypeEntry ::= SEQUENCE { 957 tripPeerRtTypeProtocolId TripAppProtocol, 958 tripPeerRtTypeAddrFamilyId TripAddressFamily, 959 tripPeerRtTypeRowStatus RowStatus 960 } 962 tripPeerRtTypeProtocolId OBJECT-TYPE 963 SYNTAX TripAppProtocol 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "The object identifier of a protocol that this peer is 968 using." 970 Jiang/Walker/Zinman 18 971 ::= { tripPeerRouteTypeEntry 1 } 973 tripPeerRtTypeAddrFamilyId OBJECT-TYPE 974 SYNTAX TripAddressFamily 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "The object identifier of an address family that this peer 979 belongs to." 980 ::= { tripPeerRouteTypeEntry 2 } 982 tripPeerRtTypeRowStatus OBJECT-TYPE 983 SYNTAX RowStatus 984 MAX-ACCESS read-only 985 STATUS current 986 DESCRIPTION 987 "This object is used to instantiate a row in this table. 988 The normal row status values of createAndGo(4), 989 createAndWait(5) and delete(6) have no application in this 990 table." 991 ::= { tripPeerRouteTypeEntry 3 } 993 -- 994 -- TripPeerStatsTable 995 -- 996 tripPeerStatsTable OBJECT-TYPE 997 SYNTAX SEQUENCE OF TripPeerStatsEntry 998 MAX-ACCESS not-accessible 999 STATUS current 1000 DESCRIPTION 1001 "The TRIP peer stats table. This table contains one entry 1002 per TRIP peer, and statistics related to the connection 1003 with the peer." 1004 ::= { tripMIBObjects 6 } 1006 tripPeerStatsEntry OBJECT-TYPE 1007 SYNTAX TripPeerStatsEntry 1008 MAX-ACCESS not-accessible 1009 STATUS current 1010 DESCRIPTION 1011 "Entry containing information about the connection with 1012 a TRIP peer." 1013 AUGMENTS { tripPeerEntry } 1014 ::= { tripPeerStatsTable 1 } 1016 TripPeerStatsEntry ::= SEQUENCE { 1017 tripPeerInUpdates Counter32, 1018 tripPeerOutUpdates Counter32, 1019 tripPeerInTotalMessages Counter32, 1020 tripPeerOutTotalMessages Counter32, 1021 tripPeerFsmEstablishedTransitions Counter32, 1022 tripPeerFsmEstablishedTime DateAndTime, 1023 tripPeerInUpdateElapsedTime Gauge32 1025 Jiang/Walker/Zinman 19 1026 } 1028 tripPeerInUpdates OBJECT-TYPE 1029 SYNTAX Counter32 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "The number of TRIP update messages received from this 1034 peer since the last restart of this location server." 1035 ::= { tripPeerStatsEntry 1 } 1037 tripPeerOutUpdates OBJECT-TYPE 1038 SYNTAX Counter32 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "The number of TRIP update messages transmitted to 1043 this peer since the last restart of this location 1044 server." 1045 ::= { tripPeerStatsEntry 2 } 1047 tripPeerInTotalMessages OBJECT-TYPE 1048 SYNTAX Counter32 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "The total number of TRIP messages received to the 1053 remote peer on this connection since the last restart 1054 of this location server." 1055 ::= { tripPeerStatsEntry 3 } 1057 tripPeerOutTotalMessages OBJECT-TYPE 1058 SYNTAX Counter32 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "The total number of outgoing TRIP messages sent since 1063 the last restart of this location server." 1064 ::= { tripPeerStatsEntry 4 } 1066 tripPeerFsmEstablishedTransitions OBJECT-TYPE 1067 SYNTAX Counter32 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The number of times the TRIP peer has transitioned into 1072 the established state since the last restart of this 1073 location server." 1074 ::= { tripPeerStatsEntry 5 } 1076 tripPeerFsmEstablishedTime OBJECT-TYPE 1077 SYNTAX DateAndTime 1078 MAX-ACCESS read-only 1080 Jiang/Walker/Zinman 20 1081 STATUS current 1082 DESCRIPTION 1083 "Indicates how long in seconds this peer has been in the 1084 established state." 1085 ::= { tripPeerStatsEntry 6 } 1087 tripPeerInUpdateElapsedTime OBJECT-TYPE 1088 SYNTAX Gauge32 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "Elapsed time in seconds since the last TRIP update 1093 message was received from the peer." 1094 ::= { tripPeerStatsEntry 7 } 1096 -- TRIP Received Route Table. This table contains 1097 -- all routes from all sources. Each entry consists 1098 -- of a route and its associated path attributes. 1100 tripRouteTable OBJECT-TYPE 1101 SYNTAX SEQUENCE OF TripRouteEntry 1102 MAX-ACCESS not-accessible 1103 STATUS current 1104 DESCRIPTION 1105 "The TRIP route table containing information about 1106 reachable routes that are to be added to service by the 1107 receiving LS." 1108 ::= { tripMIBObjects 7 } 1110 tripRouteEntry OBJECT-TYPE 1111 SYNTAX TripRouteEntry 1112 MAX-ACCESS not-accessible 1113 STATUS current 1114 DESCRIPTION 1115 "Information about a route to a called destination." 1116 INDEX { applIndex, 1117 tripRouteAppProtocol, 1118 tripRouteAddressFamily, 1119 tripRouteAddress, 1120 tripRoutePeer 1121 } 1122 ::= { tripRouteTable 1 } 1124 TripRouteEntry ::= SEQUENCE { 1125 tripRouteAppProtocol TripAppProtocol, 1126 tripRouteAddressFamily TripAddressFamily, 1127 tripRouteAddress OCTET STRING, 1128 tripRoutePeer TripId, 1129 tripRouteAddressSequenceNumber Integer32, 1130 tripRouteAddressOriginatorId TripItad, 1131 tripRouteNextHopServerIAddrType InetAddressType, 1132 tripRouteNextHopServer InetAddress, 1133 tripRouteNextHopServerPort Integer32, 1135 Jiang/Walker/Zinman 21 1136 tripRouteNextHopServerItad TripItad, 1137 tripRouteMultiExitDisc Unsigned32, 1138 tripRouteLocalPref Unsigned32, 1139 tripRouteAdvertisementPath OCTET STRING, 1140 tripRouteRoutedPath OCTET STRING, 1141 tripRouteAtomicAggregate TruthValue, 1142 tripRouteBest TruthValue, 1143 tripRouteUnknown OCTET STRING, 1144 tripRouteWithdrawn TruthValue, 1145 tripRouteConverted TruthValue 1146 } 1148 tripRouteAppProtocol OBJECT-TYPE 1149 SYNTAX TripAppProtocol 1150 MAX-ACCESS not-accessible 1151 STATUS current 1152 DESCRIPTION 1153 "The protocol for which this routing table is 1154 maintained." 1155 ::= { tripRouteEntry 1 } 1157 tripRouteAddressFamily OBJECT-TYPE 1158 SYNTAX TripAddressFamily 1159 MAX-ACCESS not-accessible 1160 STATUS current 1161 DESCRIPTION 1162 "Specifies the type of address for the destination 1163 route." 1164 ::= { tripRouteEntry 2 } 1166 tripRouteAddress OBJECT-TYPE 1167 SYNTAX OCTET STRING (SIZE(1..32)) 1168 MAX-ACCESS not-accessible 1169 STATUS current 1170 DESCRIPTION 1171 "This is an address (prefix) of the family type given by 1172 Address Family of the destination." 1173 ::= { tripRouteEntry 3 } 1175 tripRoutePeer OBJECT-TYPE 1176 SYNTAX TripId 1177 MAX-ACCESS not-accessible 1178 STATUS current 1179 DESCRIPTION 1180 "The identifier of the peer where the route information 1181 was learned." 1182 ::= { tripRouteEntry 4 } 1184 tripRouteAddressSequenceNumber OBJECT-TYPE 1185 SYNTAX Integer32 (1..2147483647) 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1190 Jiang/Walker/Zinman 22 1191 "Indicates the version of the destination route 1192 originated by the location server identified by 1193 tripRouteAddressOriginatorId intra-domain 1194 attribute." 1195 ::= { tripRouteEntry 5 } 1197 tripRouteAddressOriginatorId OBJECT-TYPE 1198 SYNTAX TripItad 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "This is an intra-domain attribute indicating the 1203 internal location server that originated the route 1204 into the ITAD." 1205 ::= { tripRouteEntry 6 } 1207 tripRouteNextHopServerIAddrType OBJECT-TYPE 1208 SYNTAX InetAddressType 1209 MAX-ACCESS read-only 1210 STATUS current 1211 DESCRIPTION 1212 "The type of Inet Address of the tripRouteNextHopServer." 1213 REFERENCE 1214 "RFC 2851, section 3." 1215 ::= { tripRouteEntry 7 } 1217 tripRouteNextHopServer OBJECT-TYPE 1218 SYNTAX InetAddress 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "Indicates the next hop that messages of a given 1223 protocol destined for tripRouteAddress should 1224 be sent to." 1225 ::= { tripRouteEntry 8 } 1227 tripRouteNextHopServerPort OBJECT-TYPE 1228 SYNTAX Integer32 (1..2147483647) 1229 MAX-ACCESS read-only 1230 STATUS current 1231 DESCRIPTION 1232 "The port of the next hop server that this route 1233 will use." 1234 ::= { tripRouteEntry 9 } 1236 tripRouteNextHopServerItad OBJECT-TYPE 1237 SYNTAX TripItad 1238 MAX-ACCESS read-only 1239 STATUS current 1240 DESCRIPTION 1241 "Indicates the domain of the next hop." 1242 ::= { tripRouteEntry 10 } 1244 Jiang/Walker/Zinman 23 1245 tripRouteMultiExitDisc OBJECT-TYPE 1246 SYNTAX Unsigned32 (0..4294967295) 1247 MAX-ACCESS read-only 1248 STATUS current 1249 DESCRIPTION 1250 "When two ITADs are connected by more than one set of peers, 1251 it is used to descriminate between multiple exit points to 1252 an adjacent ITAD." 1253 ::= { tripRouteEntry 11 } 1255 tripRouteLocalPref OBJECT-TYPE 1256 SYNTAX Unsigned32 (0..4294967295) 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "Indicated the local LS's degree of preference for an 1261 advertised route destination." 1262 ::= { tripRouteEntry 12 } 1264 tripRouteAdvertisementPath OBJECT-TYPE 1265 SYNTAX OCTET STRING (SIZE(4..252)) 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "Identifies the ITADs through wich routing information 1270 carried in an advertisement has passed. 1272 This object is probably best represented as sequence of 1273 integer. For SMI compatibility, though, it is represented 1274 as OCTET STRING. This object is a sequence of ITADs in 1275 network byte order." 1276 ::= { tripRouteEntry 13 } 1278 tripRouteRoutedPath OBJECT-TYPE 1279 SYNTAX OCTET STRING (SIZE(4..252)) 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "Identifies the ITADs through which messages sent using 1284 this route would pass. These are as subset of 1285 tripRouteAdvertisementPath. 1287 This object is probably best represented as sequence of 1288 integer. For SMI compatibility, though, it is represented 1289 as OCTET STRING. This object is a sequence of ITADs in 1290 network byte order." 1291 ::= { tripRouteEntry 14 } 1293 tripRouteAtomicAggregate OBJECT-TYPE 1294 SYNTAX TruthValue 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1299 Jiang/Walker/Zinman 24 1300 "Indicates that a route may traverse domains not listed in 1301 tripRouteRoutedPath. If an LS selects the less specific 1302 route from a set of overlapping routes, then this value 1303 returns TRUE." 1304 ::= { tripRouteEntry 15 } 1306 tripRouteBest OBJECT-TYPE 1307 SYNTAX TruthValue 1308 MAX-ACCESS read-only 1309 STATUS current 1310 DESCRIPTION 1311 "An indication of whether this route was chosen as the 1312 best TRIP route." 1313 ::= { tripRouteEntry 16 } 1315 tripRouteUnknown OBJECT-TYPE 1316 SYNTAX OCTET STRING (SIZE(0..255)) 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "One or more attributes not understood by this location 1321 server." 1322 ::= { tripRouteEntry 17 } 1324 tripRouteWithdrawn OBJECT-TYPE 1325 SYNTAX TruthValue 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "Indicates if this route is to be removed from service by 1330 the receiving LS." 1331 ::= { tripRouteEntry 18 } 1333 tripRouteConverted OBJECT-TYPE 1334 SYNTAX TruthValue 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "Indicates if this route has been converted to a 1339 different application protocol than it had originally." 1340 ::= { tripRouteEntry 19 } 1342 -- 1343 -- TRIP Received Route CommunityTable. 1344 -- 1346 tripRouteCommunityTable OBJECT-TYPE 1347 SYNTAX SEQUENCE OF TripRouteCommunityEntry 1348 MAX-ACCESS not-accessible 1349 STATUS current 1350 DESCRIPTION 1351 "A table containing a list of TRIP communities associated 1353 Jiang/Walker/Zinman 25 1354 with a route." 1355 REFERENCE 1356 "draft-ietf-iptel-trip-07.txt, J. Rosenberg et al, 1357 section 5.9." 1358 ::= { tripMIBObjects 8 } 1360 tripRouteCommunityEntry OBJECT-TYPE 1361 SYNTAX TripRouteCommunityEntry 1362 MAX-ACCESS not-accessible 1363 STATUS current 1364 DESCRIPTION 1365 "Information about communities associated with a route. An 1366 entry with a tripRouteAddress of 00 and a tripRoutePeer of 1367 0 refers to the local LS." 1368 INDEX { applIndex, 1369 tripRouteAppProtocol, 1370 tripRouteAddressFamily, 1371 tripRouteAddress, 1372 tripRoutePeer, 1373 tripRouteCommunityId 1374 } 1375 ::= { tripRouteCommunityTable 1 } 1377 TripRouteCommunityEntry ::= SEQUENCE { 1378 tripRouteCommunityId TripItad, 1379 tripRouteCommunityItad TripItad 1380 } 1382 tripRouteCommunityId OBJECT-TYPE 1383 SYNTAX TripItad 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "The community identifier." 1388 ::= { tripRouteCommunityEntry 1 } 1390 tripRouteCommunityItad OBJECT-TYPE 1391 SYNTAX TripItad 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "The ITAD associated with this community." 1396 ::= { tripRouteCommunityEntry 2 } 1398 -- 1399 -- tripItadTopologyTable 1400 -- 1402 tripItadTopologyTable OBJECT-TYPE 1403 SYNTAX SEQUENCE OF TripItadTopologyEntry 1404 MAX-ACCESS not-accessible 1405 STATUS current 1406 DESCRIPTION 1408 Jiang/Walker/Zinman 26 1409 "The sequence of link connections between peers within 1410 an ITAD." 1411 ::= { tripMIBObjects 9 } 1413 tripItadTopologyEntry OBJECT-TYPE 1414 SYNTAX TripItadTopologyEntry 1415 MAX-ACCESS not-accessible 1416 STATUS current 1417 DESCRIPTION 1418 "Information about a peer of the location server identified 1419 by tripOriginatorIdentifier." 1420 INDEX { applIndex, tripItadTopologyOrigId } 1421 ::= { tripItadTopologyTable 1 } 1423 TripItadTopologyEntry ::= SEQUENCE { 1424 tripItadTopologyOrigId TripItad, 1425 tripItadTopologySeqNum Integer32 1426 } 1428 tripItadTopologyOrigId OBJECT-TYPE 1429 SYNTAX TripItad 1430 MAX-ACCESS not-accessible 1431 STATUS current 1432 DESCRIPTION 1433 "Indicates the internal location server that originated 1434 the ITAD topology information into the ITAD." 1435 ::= { tripItadTopologyEntry 1 } 1437 tripItadTopologySeqNum OBJECT-TYPE 1438 SYNTAX Integer32 (1..2147483647) 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "Indicates the version of the ITAD topology 1443 originated by the location server identified by 1444 tripOriginatorIdentifier." 1445 ::= { tripItadTopologyEntry 2 } 1447 -- 1448 -- tripItadTopologyIdTable 1449 -- 1451 tripItadTopologyIdTable OBJECT-TYPE 1452 SYNTAX SEQUENCE OF TripItadTopologyIdEntry 1453 MAX-ACCESS not-accessible 1454 STATUS current 1455 DESCRIPTION 1456 "The list of other location servers within the ITAD 1457 domain that the location server identified by 1458 tripOriginatorIdentifier is currently peering." 1459 ::= { tripMIBObjects 10 } 1461 tripItadTopologyIdEntry OBJECT-TYPE 1463 Jiang/Walker/Zinman 27 1464 SYNTAX TripItadTopologyIdEntry 1465 MAX-ACCESS not-accessible 1466 STATUS current 1467 DESCRIPTION 1468 "Information about a peer to the location server 1469 identified by tripOriginatorIdentifier." 1470 INDEX { applIndex, 1471 tripItadTopologyOrigId, 1472 tripItadTopologyId } 1473 ::= { tripItadTopologyIdTable 1 } 1475 TripItadTopologyIdEntry ::= SEQUENCE { 1476 tripItadTopologyId TripId, 1477 tripItadTopologyIdRowStatus RowStatus 1478 } 1480 tripItadTopologyId OBJECT-TYPE 1481 SYNTAX TripId 1482 MAX-ACCESS not-accessible 1483 STATUS current 1484 DESCRIPTION 1485 "The index into this entry. Indicates the other location 1486 servers within the ITAD domain that this location server 1487 identified by tripOriginatorIdentifier is currently 1488 peering." 1489 ::= { tripItadTopologyIdEntry 1 } 1491 tripItadTopologyIdRowStatus OBJECT-TYPE 1492 SYNTAX RowStatus 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "This object is used to instantiate a row in this table. 1497 The normal row status values of createAndGo(4), 1498 createAndWait(5) and delete(6) have no application in this 1499 table." 1500 ::= { tripItadTopologyIdEntry 2 } 1502 -- 1503 -- Notification objects 1504 -- 1506 tripNotifApplIndex OBJECT-TYPE 1507 SYNTAX INTEGER (1..2147483647) 1508 MAX-ACCESS accessible-for-notify 1509 STATUS current 1510 DESCRIPTION 1511 "This object contains the applIndex as described 1512 in RFC 2788. It is used to bind this notification 1513 with a specific instance of TRIP entity." 1514 ::= { tripMIBNotifications 1 } 1516 tripNotifPeerAddrInetType OBJECT-TYPE 1518 Jiang/Walker/Zinman 28 1519 SYNTAX InetAddressType 1520 MAX-ACCESS accessible-for-notify 1521 STATUS current 1522 DESCRIPTION 1523 "The type of Inet Address of the tripNotifPeerAddr." 1524 REFERENCE 1525 "RFC 2851, section 3." 1526 ::= { tripMIBNotifications 2 } 1528 tripNotifPeerAddr OBJECT-TYPE 1529 SYNTAX InetAddress (SIZE(0..125)) 1530 MAX-ACCESS accessible-for-notify 1531 STATUS current 1532 DESCRIPTION 1533 "The remote IP address of this entry's TRIP peer. The 1534 size value of 125 has been assigned due to the sub 1535 identifier of object types length limitation as 1536 defined in SMIv2." 1537 REFERENCE 1538 "RFC 2851, section 3." 1539 ::= { tripMIBNotifications 3 } 1541 tripNotifPeerErrCode OBJECT-TYPE 1542 SYNTAX INTEGER { 1543 messageHeader(1), 1544 openMessage(2), 1545 updateMessage(3), 1546 holdTimerExpired(4), 1547 finiteStateMachine(5), 1548 cease(6), 1549 tripNotification(7) 1550 } 1551 MAX-ACCESS accessible-for-notify 1552 STATUS current 1553 DESCRIPTION 1554 "Notification message of TRIP error. The meaning of this 1555 value is applicable to the following functions: 1557 1 - message header. 1558 All errors detected while processing the TRIP message 1559 header. 1560 2 - open message. 1561 All errors detected while processing the OPEN message. 1562 3 - update message. 1563 All errors detected while processing the UPDATE message. 1564 4 - hold timer expired. 1565 A notification generated when the hold timer expires. 1566 5 - finite state machine. 1567 All errors detected by the TRIP Finite State Machine. 1568 6 - cease. 1569 Any fatal error condition that the rest of the values 1570 do not cover. 1571 7 - trip notification message. 1573 Jiang/Walker/Zinman 29 1574 Any error encountered while sending a notification 1575 message." 1576 ::= { tripMIBNotifications 4 } 1578 tripNotifPeerErrSubcode OBJECT-TYPE 1579 SYNTAX Integer32 (1..7) 1580 MAX-ACCESS accessible-for-notify 1581 STATUS current 1582 DESCRIPTION 1583 "The sub error code associated with error code. The meaning 1584 of this value is dependent on the value of 1585 tripNotifPeerErrCode. 1587 Message Header (1) Error Subcodes: 1588 1 - Bad Message Length. 1589 2 - Bad Message Type. 1591 OPEN Message (2) Error Subcodes: 1592 1 - Unsupported Version Number. 1593 2 - Bad Peer ITAD. 1594 3 - Bad TRIP Identifier. 1595 4 - Unsupported Optional Parameter. 1596 5 - Unacceptable Hold Time. 1597 6 - Unsupported Capability. 1598 7 - Capability Mismatch. 1600 UPDATE Message (3) Error Subcodes: 1601 1 - Malformed Attribute List. 1602 2 - Unrecognized Well-known Attribute. 1603 3 - Missing Well-known Mandatory Attribute. 1604 4 - Attribute Flags Error. 1605 5 - Attribute Length Error. 1606 6 - Invalid Attribute." 1607 ::= { tripMIBNotifications 5 } 1609 -- 1610 -- Notifications 1611 -- 1612 tripEstablished NOTIFICATION-TYPE 1613 STATUS current 1614 DESCRIPTION 1615 "The TRIP Established event is generated when the TRIP 1616 FSM enters the ESTABLISHED state." 1617 ::= { tripMIBNotifications 6 } 1619 tripFSM NOTIFICATION-TYPE 1620 OBJECTS { tripNotifApplIndex, 1621 tripNotifPeerAddrInetType, 1622 tripNotifPeerAddr, 1623 tripNotifPeerErrCode, 1624 tripNotifPeerErrSubcode, 1625 tripPeerState 1626 } 1628 Jiang/Walker/Zinman 30 1629 STATUS current 1630 DESCRIPTION 1631 "The trip FSM Event is generated when any error is detected 1632 by the TRIP Finite State Machine." 1633 ::= { tripMIBNotifications 7 } 1635 tripOpenMessageError NOTIFICATION-TYPE 1636 OBJECTS { tripNotifApplIndex, 1637 tripNotifPeerAddrInetType, 1638 tripNotifPeerAddr, 1639 tripNotifPeerErrCode, 1640 tripNotifPeerErrSubcode, 1641 tripPeerState 1642 } 1643 STATUS current 1644 DESCRIPTION 1645 "Errors detected while processing the OPEN message." 1646 ::= { tripMIBNotifications 8 } 1648 tripUpdateMessageError NOTIFICATION-TYPE 1649 OBJECTS { tripNotifApplIndex, 1650 tripNotifPeerAddrInetType, 1651 tripNotifPeerAddr, 1652 tripNotifPeerErrCode, 1653 tripNotifPeerErrSubcode, 1654 tripPeerState 1655 } 1656 STATUS current 1657 DESCRIPTION 1658 "Errors detected while processing the UPDATE message." 1659 ::= { tripMIBNotifications 9 } 1661 tripHoldTimerExpired NOTIFICATION-TYPE 1662 OBJECTS { tripNotifApplIndex, 1663 tripNotifPeerAddrInetType, 1664 tripNotifPeerAddr, 1665 tripNotifPeerErrCode, 1666 tripNotifPeerErrSubcode, 1667 tripPeerState 1668 } 1669 STATUS current 1670 DESCRIPTION 1671 "The system does not receive successive messages within the 1672 period specified by the negotiated Hold Time." 1673 ::= { tripMIBNotifications 10 } 1675 tripConnectionCollision NOTIFICATION-TYPE 1676 OBJECTS { tripNotifApplIndex } 1677 STATUS current 1678 DESCRIPTION 1679 "A pair of LSs tried to simultaneously to establish a 1680 transport connection to each other." 1681 ::= { tripMIBNotifications 11 } 1683 Jiang/Walker/Zinman 31 1684 tripNotificationErr NOTIFICATION-TYPE 1685 OBJECTS { tripNotifApplIndex } 1686 STATUS current 1687 DESCRIPTION 1688 "Generated if there is an error detected in a TRIP 1689 notification message sent with another cause. Note that 1690 the TRIP notification refered to in this object is not 1691 an SNMP notification, it is a specific message described 1692 in the TRIP specification." 1693 REFERENCE 1694 "draft-ietf-iptel-trip-07.txt, J. Rosenberg et al, 1695 section 6.4." 1696 ::= { tripMIBNotifications 12 } 1698 -- 1699 -- Compliance Statements 1700 -- 1701 tripCompliance MODULE-COMPLIANCE 1702 STATUS current 1703 DESCRIPTION 1704 "The compliance statement for TRIP entities." 1706 MODULE -- this module 1707 MANDATORY-GROUPS { tripConfigGroup, 1708 tripPeerTableConfigGroup, 1709 tripRouteGroup, 1710 tripItadTopologyGroup, 1711 tripPeerTableStatsGroup } 1713 GROUP tripNotificationGroup 1714 DESCRIPTION 1715 "This group is optional. A TRIP entity can choose not to 1716 send any notifications. If this group is implemented, the 1717 tripNotifObjectGroup must also be implemented." 1719 GROUP tripNotifObjectGroup 1720 DESCRIPTION 1721 "This group is optional. A TRIP entity can choose not to 1722 send any notifications. If this group is implemented, the 1723 tripNotificationGroup must also be implemented." 1725 MODULE NETWORK-SERVICES-MIB 1726 MANDATORY-GROUPS { applRFC1565Group } 1728 ::= { tripMIBCompliance 1 } 1730 -- 1731 -- Object and event conformance groups 1732 -- 1734 tripConfigGroup OBJECT-GROUP 1736 Jiang/Walker/Zinman 32 1737 OBJECTS { 1738 tripProtocolVersion, 1739 tripLocalItad, 1740 tripIdentifier, 1741 tripOperStatus, 1742 tripAdminStatus, 1743 tripLocalAddrIAddrType, 1744 tripLocalAddr, 1745 tripLocalPort, 1746 tripMinItadOriginationInterval, 1747 tripMinRouteAdvertisementInterval, 1748 tripMaxPurgeTime, 1749 tripDisableTime, 1750 tripSendReceiveMode, 1751 tripSupportedCommunityItad, 1752 tripSupportedCommunityRowStatus 1753 } 1754 STATUS current 1755 DESCRIPTION 1756 "The global objects for configuring trip." 1757 ::= { tripMIBGroups 1 } 1759 tripPeerTableConfigGroup OBJECT-GROUP 1760 OBJECTS { 1761 tripPeerIdentifier, 1762 tripPeerState, 1763 tripPeerAdminStatus, 1764 tripPeerNegotiatedVersion, 1765 tripPeerSendReceiveMode, 1766 tripPeerRemotePort, 1767 tripPeerRemoteItad, 1768 tripPeerConnectRetryInterval, 1769 tripPeerMaxRetryInterval, 1770 tripPeerHoldTime, 1771 tripPeerKeepAlive, 1772 tripPeerHoldTimeConfigured, 1773 tripPeerKeepAliveConfigured, 1774 tripPeerMinItadOriginationInterval, 1775 tripPeerMinRouteAdvertisementInterval, 1776 tripPeerMaxPurgeTime, 1777 tripPeerDisableTime, 1778 tripPeerRowStatus 1779 } 1781 STATUS current 1782 DESCRIPTION 1783 "The global objects for configuring the TRIP peer table." 1784 ::= { tripMIBGroups 2 } 1786 tripPeerTableStatsGroup OBJECT-GROUP 1787 OBJECTS { 1788 tripPeerInUpdates, 1789 tripPeerOutUpdates, 1791 Jiang/Walker/Zinman 33 1792 tripPeerInTotalMessages, 1793 tripPeerOutTotalMessages, 1794 tripPeerFsmEstablishedTransitions, 1795 tripPeerFsmEstablishedTime, 1796 tripPeerInUpdateElapsedTime 1797 } 1799 STATUS current 1800 DESCRIPTION 1801 "The global statistics the TRIP peer table." 1802 ::= { tripMIBGroups 3 } 1804 tripRouteGroup OBJECT-GROUP 1805 OBJECTS { 1806 tripRouteAddressSequenceNumber, 1807 tripRouteAddressOriginatorId, 1808 tripRouteNextHopServerIAddrType, 1809 tripRouteNextHopServer, 1810 tripRouteNextHopServerPort, 1811 tripRouteNextHopServerItad, 1812 tripRouteMultiExitDisc, 1813 tripRouteLocalPref, 1814 tripRouteAdvertisementPath, 1815 tripRouteRoutedPath, 1816 tripRouteAtomicAggregate, 1817 tripRouteBest, 1818 tripRouteUnknown, 1819 tripRouteWithdrawn, 1820 tripRouteConverted, 1821 tripRouteCommunityItad, 1822 tripPeerRtTypeRowStatus 1823 } 1825 STATUS current 1826 DESCRIPTION 1827 "The global objects for configuring route attribute." 1828 ::= { tripMIBGroups 4 } 1830 tripItadTopologyGroup OBJECT-GROUP 1831 OBJECTS { 1832 tripItadTopologySeqNum, 1833 tripItadTopologyIdRowStatus 1834 } 1835 STATUS current 1836 DESCRIPTION 1837 "The objects that define the TRIP ITAD topology." 1838 ::= { tripMIBGroups 5 } 1840 tripNotificationGroup NOTIFICATION-GROUP 1841 NOTIFICATIONS { 1842 tripEstablished, 1843 tripFSM, 1844 tripOpenMessageError, 1846 Jiang/Walker/Zinman 34 1847 tripUpdateMessageError, 1848 tripHoldTimerExpired, 1849 tripConnectionCollision, 1850 tripNotificationErr 1851 } 1852 STATUS current 1853 DESCRIPTION 1854 "A collection of notifications defined for TRIP." 1855 ::= { tripMIBGroups 6 } 1857 tripNotifObjectGroup OBJECT-GROUP 1858 OBJECTS { 1859 tripNotifApplIndex, 1860 tripNotifPeerAddrInetType, 1861 tripNotifPeerAddr, 1862 tripNotifPeerErrCode, 1863 tripNotifPeerErrSubcode 1864 } 1865 STATUS current 1866 DESCRIPTION 1867 "The collection of objects that specify information for 1868 TRIP notifications." 1869 ::= { tripMIBGroups 7 } 1871 END 1873 7. Security Considerations 1875 There are a number of management objects defined in this MIB that 1876 have a MAX-ACCESS clause of read-write and/or read-create. Such 1877 objects may be considered sensitive or vulnerable in some network 1878 environments. The support for SET operations in a non-secure 1879 environment without proper protection can have a negative effect on 1880 network operations. 1882 The managed objects in this MIB contain sensitive information since, 1883 collectively, they allow tracing and influencing of connections in 1884 TRIP devices and provide information of their connection 1885 characteristics. 1887 It is thus important to control even GET access to these objects and 1888 possibly to even encrypt the values of these object when sending 1889 them over the network via SNMP. Not all versions of SNMP provide 1890 features for such a secure environment. 1892 SNMPv1 by itself is not a secure environment. Even if the network 1893 itself is secure (for example by using IPSec), even then, there is 1894 no control as to who on the secure network is allowed to access and 1895 GET/SET (read/change/create/delete) the objects in this MIB. 1897 It is recommended that the implementers consider the security 1898 features as provided by the SNMPv3 framework. Specifically, the use 1900 Jiang/Walker/Zinman 35 1901 of the User-based Security Model RFC 2574 [19] and the View-based 1902 Access Control Model RFC 2575 [17] is recommended. 1904 It is then a customer/user responsibility to ensure that the SNMP 1905 entity giving access to an instance of this MIB, is properly 1906 configured to give access to the objects only to those principals 1907 users) that have legitimate rights to indeed GET or SET 1908 (change/create/delete) them. 1910 8. Revision History 1912 8.1. Changes from 1914 o Removed tripRouteAddressLen from the tripRouteTable. 1915 o Made use of INET-ADDRESS-MIB and it's TC's for IPv6 compliance. 1916 o Changed order of the enumeration of tripPeerSendReceiveMode to 1917 comform to TRIP draft. 1918 o Added objects tripPeerCircuitCapacity and tripPeerDSPCapacity to 1919 support TRIP for Gateways [24]. 1920 o Removed tripPeerLastError and tripPeerState objects for 1921 tripEstablished notification. 1922 o Added local community object. 1923 o Added communities table for TRIP routes and removed community 1924 object from route table. 1925 o Added send/receive capability to local LS. 1926 o Added tripRouteAddressFamily as an Index to TripRouteEntry. 1927 o Changed enumerations in tripRouteAddressFamily to decimal(1) and 1928 hexaDecimal(2). 1929 o Support for authentication mechanism from draft-ietf-iptel-trip- 1930 authen-00.txt. 1931 o Changed name of tripRoutePathSegment to 1932 tripRouteRoutedPathSegment. 1933 o Added tripRouteConverted to the routing table to signify a 1934 Converted Route. 1935 o Changed DEFVAL of tripPeerConnectRetryInterval from 60 to 120 1936 seconds. 1937 o Added DEFVAL to tripPeerKeepAlive of 30 seconds. 1938 o Added DEFVAL to tripMaxPurgeTime and tripPeerMaxPurgeTime of 10 1939 seconds. 1940 o Added DEFVAL to tripDisableTime and tripPeerDisableTime of 180 1941 seconds. 1942 o Changed DEFVAL of tripMinItadOriginationInterval and 1943 tripPeerMinItadOriginationInterval to 30 seconds. 1944 o Removed tripHoldTimeConfigured and tripKeepAliveConfigured from 1945 TripCfgEntry. 1946 o changed names from opMode to sendReceiveMode. 1948 8.2. Changes from 1950 o Added tripOperStatus. 1951 o Changed definition of textual convention TripAppProtocol to 1953 Jiang/Walker/Zinman 36 1954 OBJECT IDENTIFIER. See [2] section 13.4 1955 o Changed definition of textual convention TripAddressFamily to 1956 OBJECT IDENTIFIER. See [2] section 13.3 1957 o Added object identifiers for tripSupportedProtocols and 1958 tripAddressFamilies. 1959 o Removed authentication tables. 1960 o Removed textual convention TripPublicKey. 1961 o Changed the position of the MIB branches slightly. 1962 o Changed name of tripPeerLastError to tripNotifPeerErrCode and 1963 MAX-ACCESS to accessible-for-notify. 1964 o Separated tripNotifPeerErrSubcode from tripNotifPeerErrCode and 1965 made them both integers. 1966 o Added compliance statements. 1967 o Changed MAX-ACCESS of tripPeerRemoteItad to read-create. 1968 o Changed DEFVAL of tripPeerHoldTimeConfigured from 90 to 240. 1970 9. References 1972 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 1973 9, RFC 2026, October 1996. 1975 2 Rosenberg, J., Salama, H. and Squire, M., "Telephony Routing over 1976 IP (TRIP)", draft-ietf-iptel-trip-07.txt, work in progress. 1978 3 Rekhter, Y. and Li, T., "Border Gateway Protocol 4 (BGP-4)", IETF 1979 RFC 1771, March 1995. 1981 4 Willis, S., Burruss, J. and Chu, J., "Definitions of Managed 1982 Objects for the Fourth Version of the Border Gateway Protocol 1983 (BGP-4) using SMIv2" IETF RFC 1657, July 1994. 1985 5 Bradner, S., "Key words for use in RFCs to Indicate Requirement 1986 Levels", BCP 14, RFC 2119, March 1997. 1988 6 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1989 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1991 7 Rose, M. and McCloghrie, K., "Structure and Identification of 1992 Management Information for TCP/IP-based Internets", STD 16, RFC 1993 1155, May 1990. 1995 8 Rose, M. and McCloghrie, K., "Concise MIB Definitions", STD 16, 1996 RFC 1212, March 1991. 1998 9 Rose, M., "A Convention for Defining Traps for use with the 1999 SNMP", RFC 1215, March 1991. 2001 10 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2002 M. and Waldbusser, S., "Structure of Management Information 2003 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2005 11 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2007 Jiang/Walker/Zinman 37 2008 M. and Waldbusser, S., "Textual Conventions for SMIv2", STD 58, 2009 RFC 2579, April 1999. 2011 12 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 2012 M. and Waldbusser, S., "Conformance Statements for SMIv2", STD 2013 58, RFC 2580, April 1999. 2015 13 Case, J., Fedor, M., Schoffstall, M. and Davin, J.,"Simple 2016 Network Management Protocol", STD 15, RFC 1157, May 1990. 2018 14 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., 2019 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 2021 15 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Transport 2022 Mappings for Version 2 of the Simple Network Management Protocol 2023 (SNMPv2)", RFC 1906, January 1996. 2025 16 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol 2026 Operations for Version 2 of the Simple Network Management 2027 Protocol (SNMPv2)", RFC 1905, January 1996. 2029 17 Wijnen, B., Presuhn, R. and McCloghrie, K., "View-based Access 2030 Control Model (VACM) for the Simple Network Management Protocol 2031 (SNMP)", RFC 2575, April 1999. 2033 18 Freed, N. and Kille, S., "Network Services Monitoring MIB", RFC 2034 2788, March 2000. 2036 19 Blumenthal, U. and Wijnen, B., "User-based Security Model (USM) 2037 for version 3 of the Simple Network Management Protocol 2038 (SNMPv3)", RFC 2574, April 1999. 2040 20 Rosenberg, J. and Salama, H., "Usage of TRIP in Gateways for 2041 Exporting Phone Routes", draft-rs-trip-gw-01.txt, work in 2042 progress. 2044 21 Case, J., Harrington, D., Presuhn, R., and Wijnen, B. "Message 2045 Processing and Dispatching for the Simple Network Management 2046 Protocol (SNMP)", RFC 2572, April 1999. 2048 22 Levi, D., Meyer, P., and Stewart B., "SNMP Applications", 2049 RFC 2573, April 1999. 2051 24 Case, J., Mundy, R., Partain, D., and Stewart, B., "Introduction 2052 to Version 3 of the Internet-standard Network Management 2053 Framework", RFC 2570, April 1999. 2055 10. Author's Address 2057 David Zinman 2058 SS8 Networks, Inc. 2060 Jiang/Walker/Zinman 38 2061 495 March Road, Suite #500 2062 Ottawa, ON K2K 3G1 2063 Canada 2064 Phone: +1 613 592 2100 2065 Email: david@ss8.com 2067 Dave Walker 2068 SS8 Networks, Inc. 2069 495 March Road, Suite #500 2070 Ottawa, ON K2K 3G1 2071 Canada 2072 Phone: +1 613 592 2100 2073 Email: drwalker@ss8.com 2075 Jianping Jiang 2076 SS8 Networks, Inc. 2077 55 Commerce Valley Drive West, Suite #510 2078 Thornhill, ON, L3T 7B9 2079 Canada 2080 phone: +1 905 889 5900 2081 Email: jianping@ss8.com 2083 11. Intellectual Property 2085 The IETF takes no position regarding the validity or scope of any 2086 intellectual property or other rights that might be claimed to 2087 pertain to the implementation or use of the technology described in 2088 this document or the extent to which any license under such rights 2089 might or might not be available; neither does it represent that it 2090 has made any effort to identify any such rights. Information on the 2091 IETF's procedures with respect to rights in standards-track and 2092 standards-related documentation can be found in BCP-11. Copies of 2093 claims of rights made available for publication and any assurances 2094 of licenses to be made available, or the result of an attempt made 2095 to obtain a general license or permission for the use of such 2096 proprietary rights by implementors or users of this specification 2097 can be obtained from the IETF Secretariat. 2099 The IETF invites any interested party to bring to its attention any 2100 copyrights, patents or patent applications, or other proprietary 2101 rights which may cover technology that may be required to practice 2102 this standard. Please address the information to the IETF Executive 2103 Director. 2105 12. Full Copyright Statement 2107 Copyright (C) The Internet Society (2001). All Rights Reserved. 2109 This document and translations of it may be copied and furnished to 2110 others, and derivative works that comment on or otherwise explain it 2111 or assist in its implementation may be prepared, copied, published 2113 Jiang/Walker/Zinman 39 2114 and distributed, in whole or in part, without restriction of any 2115 kind, provided that the above copyright notice and this paragraph 2116 are included on all such copies and derivative works. However, this 2117 document itself may not be modified in any way, such as by removing 2118 the copyright notice or references to the Internet Society or other 2119 Internet organizations, except as needed for the purpose of 2120 developing Internet standards in which case the procedures for 2121 copyrights defined in the Internet Standards process must be 2122 followed, or as required to translate it into languages other than 2123 English. 2125 The limited permissions granted above are perpetual and will not be 2126 revoked by the Internet Society or its successors or assigns. 2128 This document and the information contained herein is provided on an 2129 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2130 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2131 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2132 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2133 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2135 Jiang/Walker/Zinman 40