Internet Engineering Task Force J. Jiang Internet Draft D. Walker Document: draft-zinman-trip-mib-02.txt D. Zinman Expires: January 2002 SS8 Networks, Inc July 2001 Management Information Base for Telephony Routing over IP (TRIP) <draft-zinman-trip-mib-02.txt> Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [1]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that are used to manage for Telephony Routing over IP (TRIP) [2] devices. Since TRIP [2] is modelled after the Border Gateway Protocol (BGP-4) [3], the managed objects for TRIP are also modelled after RFC1657 - Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 [4]. Table of Contents Status of this Memo...................................................1 Abstract..............................................................1 1. Introduction.....................................................2 2. Conventions used in this document................................2 3. The SNMP Management Framework....................................2 Jiang/Walker/Zinman 1 Internet Draft TRIP MIB July 2001 4. Overview.........................................................3 5. Structure of TRIP MIB............................................3 5.1. Textual Conventions..............................................4 6. TRIP MIB.........................................................4 7. Security Considerations.........................................35 8. Revision History................................................36 8.1. Changes from <draft-zinman-trip-mib-00.txt>.....................36 8.2. Changes from <draft-zinman-trip-mib-01.txt>.....................36 9. References......................................................37 10. Author's Address................................................38 11. Intellectual Property...........................................39 12. Full Copyright Statement........................................39 1. Introduction This memo defines a portion of the Management Information Base (MIB)for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that are used to schedule management operations periodically or at specified dates and times. 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [5]. 3. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [6]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [7], STD 16, RFC 1212 [8] and RFC 1215 [9]. The second version, called SMIv2, is described in STD 58, RFC 2578 [10], STD 58, RFC 2579 [11] and STD 58, RFC 2580 [12]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [13]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [14] and RFC 1906 [15]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [15], RFC 2572 [21] and RFC 2574 [19]. Jiang/Walker/Zinman 2 Internet Draft TRIP MIB July 2001 o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [13]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [16]. o A set of fundamental applications described in RFC 2573 [22] and the view-based access control mechanism described in RFC 2575 [17]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [24]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 4. Overview Telephony Routing over IP (TRIP) [2] is an inter-domain application- layer control protocol that exchanges information with other TRIP gateways to provide efficient IP telephony routing. This MIB provides some managed objects for TRIP devices defined in Telephony Routing over IP <draft-ietf-iptel-trip-07.txt>. 5. Structure of TRIP MIB This MIB utilizes the framework described in RFC 2788 [18] for management of multiple instances of TRIP from a single entity. The Network Services Monitoring MIB applTable will be populated with entries corresponding to each TRIP entity in the system. Each entity will then have an applIndex associated with it. The value assigned to applIndex will represent the distinct instance of TRIP. The MIB defines some system-wide scalar objects local to the TRIP instance, as well as 5 tables: the Trip Peer Table, the Trip Peer Stats Table, the Trip Route Table, the Trip Route Community Table, the Trip ITAD Topology Table, and the Trip ITAD Topology ID Table. The Trip Peer Table contains information about the state and current activity of the connections with TRIP peers. The Trip Peer Stats Jiang/Walker/Zinman 3 Internet Draft TRIP MIB July 2001 Table augments the Trip Peer Table and contains statistics related to the connections with TRIP peers. The Trip Route Table contains information on the route to a peers destination. The Trip Route Community Table contains information on the communities associated with each route. The Trip ITAD Topology Table contains information on the sequence of link connections between peers within an ITAD. The Trip ITAD Topology ID Table is a subtable of the Trip ITAD Topology Table and contains the list of location servers within the ITAD domain that the instance of this trip ITAD Topology currently peering. 5.1. Textual Conventions The data types TripItad and TripId are used as textual conventions in this document. A TRIP ITAD is described in [2]. A TRIP ID is used as a distinct identifier for a TRIP entity. A TripAppProtocol is used to identify an application protocol. A TripAddressFamily is used to define an address family. both TripAppProtocol and TripAddressFamily are OBJECT IDENTIFIERS and as such, a MIB implementor can define a private object of this type of textual convention. Objects defined using these conventions are always encoded by means of the rules that define their primitive type. Hence, no changes to the SMI or the SNMP are necessary to accommodate these textual conventions which are adopted merely for the convenience of readers. 6. TRIP MIB TRIP-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, Integer32, Gauge32, Counter32, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION, DateAndTime, TruthValue, RowStatus FROM SNMPv2-TC OBJECT-GROUP, Jiang/Walker/Zinman 4 Internet Draft TRIP MIB July 2001 MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF InetAddressType, InetAddress FROM INET-ADDRESS-MIB applIndex FROM NETWORK-SERVICES-MIB; tripMIB MODULE-IDENTITY LAST-UPDATED "200107030000Z" ORGANIZATION "IETF IPTel Working Group" CONTACT-INFO "Co-editor Jianping Jiang SS8 Networks, Inc. postal: 55 Commerce Valley Drive West, Suite #510 Thornhill, ON, L3T 7B9 Canada email: jianping@ss8.com phone: +1 905 889 5900 Co-editor Dave Walker SS8 Networks, Inc. postal: 495 March Road, Suite #500 Ottawa, ON, K2K 3G1 Canada email: drwalker@ss8.com phone: +1 613 592 2100 Co-editor David Zinman SS8 Networks, Inc. postal: 495 March Road, Suite #500 Ottawa, ON, K2K 3G1 Canada email: david@ss8.com phone: +1 613 592 2100 IP Telephony (iptel) Working Group ================================== Chair: Jonathan Rosenberg <jdrosen@dynamicsoft.com> Transport Area Directors: Scott Bradner <sob@harvard.edu> Allison Mankin <mankin@east.isi.edu> Transport Area Advisor: Scott Bradner <sob@harvard.edu> Mailing List ============ Jiang/Walker/Zinman 5 Internet Draft TRIP MIB July 2001 iptel-admin@lists.bell-labs.com General information about the mailing list is at: http://lists.bell-labs.com/mailman/listinfo/iptel/ Archives: http://lists.bell-labs.com/pipermail/iptel/" DESCRIPTION "The MIB module describing Telephony Routing over IP (TRIP)" REVISION "200102260000Z" DESCRIPTION "The initial revision of this MIB module was published as draft-zinman-trip-mib-00.txt." ::= { mib-2 } -- to be assigned by IANA -- -- Textual Conventions -- TripItad ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The values for identifying the IP Telephony Administrative Domain." SYNTAX Unsigned32 (0..4294967295) TripId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The range of legal values for a TRIP Identifier." SYNTAX Unsigned32 (0..4294967295) TripAppProtocol ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The application protocol used for communication with TRIP LS's. Protocol defined in this document are: tripSupProtSIP tripSupProtH323Q931 tripSupProtH323RAS tripSupProtH323ANNEXG. Users can add their own application protocol types by defining a TripAppProtocol type in a private specification." SYNTAX OBJECT IDENTIFIER TripAddressFamily ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A type of address for a TRIP route. Address families defined within this document are: tripAddrFamilyDecimal Jiang/Walker/Zinman 6 Internet Draft TRIP MIB July 2001 tripAddrFamilyPentadecimal tripAddrFamilyE164. Users can add their own address family types by defining a TripAddressFamily type in a private specification." SYNTAX OBJECT IDENTIFIER tripMIBNotifications OBJECT IDENTIFIER ::= { tripMIB 0 } tripMIBObjects OBJECT IDENTIFIER ::= { tripMIB 1 } tripMIBConformance OBJECT IDENTIFIER ::= { tripMIB 2 } tripMIBCompliance OBJECT IDENTIFIER ::= { tripMIBConformance 1 } tripMIBGroups OBJECT IDENTIFIER ::= { tripMIBConformance 2 } -- -- Supported protocols -- tripSupportedProtocols OBJECT IDENTIFIER ::= { tripMIBObjects 100 } tripSupProtSIP OBJECT IDENTIFIER ::= { tripSupportedProtocols 1 } tripSupProtH323Q931 OBJECT IDENTIFIER ::= { tripSupportedProtocols 2 } tripSupProtH323RAS OBJECT IDENTIFIER ::= { tripSupportedProtocols 3 } tripSupProtH323ANNEXG OBJECT IDENTIFIER ::= { tripSupportedProtocols 4 } -- -- Address Families -- tripAddressFamilies OBJECT IDENTIFIER ::= { tripMIBObjects 101 } tripAddrFamilyDecimal OBJECT IDENTIFIER ::= { tripAddressFamilies 1 } tripAddrFamilyPentadecimal OBJECT IDENTIFIER ::= { tripAddressFamilies 2 } tripAddrFamilyE164 OBJECT IDENTIFIER ::= { tripAddressFamilies 3 } -- -- tripCfgTable -- tripCfgTable OBJECT-TYPE SYNTAX SEQUENCE OF TripCfgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains the common configuration objects applicable to all TRIP entities. Each row represents those objects for a particular TRIP LS present in this system. The instances of TRIP LS's are uniquely identified by applIndex." Jiang/Walker/Zinman 7 Internet Draft TRIP MIB July 2001 ::= { tripMIBObjects 1 } tripCfgEntry OBJECT-TYPE SYNTAX TripCfgEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A row of common configuration." INDEX { applIndex } ::= { tripCfgTable 1 } TripCfgEntry ::= SEQUENCE { tripProtocolVersion Integer32, tripLocalItad TripItad, tripIdentifier TripId, tripOperStatus INTEGER, tripAdminStatus INTEGER, tripLocalAddrIAddrType InetAddressType, tripLocalAddr InetAddress, tripLocalPort Integer32, tripMinItadOriginationInterval Integer32, tripMinRouteAdvertisementInterval Integer32, tripMaxPurgeTime Integer32, tripDisableTime Integer32, tripSendReceiveMode INTEGER } tripProtocolVersion OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "This object will reflect the version of TRIP supported by this system. It follows the same format as TRIP version information contained in the TRIP messages generated by this TRIP entity as dictated by draft-ietf-iptel-trip-07.txt." ::= { tripCfgEntry 1 } tripLocalItad OBJECT-TYPE SYNTAX TripItad MAX-ACCESS read-write STATUS current DESCRIPTION "The Local Internet Telephony Administrative domain." ::= { tripCfgEntry 2 } tripIdentifier OBJECT-TYPE SYNTAX TripId MAX-ACCESS read-only STATUS current DESCRIPTION Jiang/Walker/Zinman 8 Internet Draft TRIP MIB July 2001 "The object that identifies this TRIP Client." ::= { tripCfgEntry 3 } tripAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The desired TRIP state. up(1) : Set the application to normal operation. down(2): Set the application to a state where it will not process TRIP messages." ::= { tripCfgEntry 4 } tripOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "The current operational state of the TRIP protocol. up(1) : The application is operating normally, and is processing (receiving and possibly issuing) TRIP requests and responses. down(2): The application is currently unable to process TRIP messages due to a fault or if TRIP is in an initialization state. If tripAdminStatus is down(2) then tripOperStatus should be down(2). If tripAdminStatus is changed to up(1) then tripOperStatus should change to up(1) if there is no fault that prevents the TRIP protocol from moving to the up(1) state." ::= { tripCfgEntry 5 } tripLocalAddrIAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of Inet Address of the tripLocalAddr." REFERENCE "RFC 2851, section 3." ::= { tripCfgEntry 6 } Jiang/Walker/Zinman 9 Internet Draft TRIP MIB July 2001 tripLocalAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of this entry's TRIP peer connection." REFERENCE "RFC 2851, section 3." ::= { tripCfgEntry 7 } tripLocalPort OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-write STATUS current DESCRIPTION "The local port that this entry's TRIP peer is using." ::= { tripCfgEntry 8 } tripMinItadOriginationInterval OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "Seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Amount of time that must elapse between advertisement of update message that report changes within the Location Server's own ITAD." DEFVAL { 30 } ::= { tripCfgEntry 9 } tripMinRouteAdvertisementInterval OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "Seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Specifies minimal interval between successive advertisement to a particular destination from an LS." DEFVAL { 30 } ::= { tripCfgEntry 10 } tripMaxPurgeTime OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "Seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Indicate the interval that the location server must maintain routes marked as withdrawn in its database." DEFVAL { 10 } ::= { tripCfgEntry 11 } Jiang/Walker/Zinman 10 Internet Draft TRIP MIB July 2001 tripDisableTime OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "Seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "Indicate the interval that the TRIP module of the location server must be disabled while routes originated by this location server with high sequence numbers can be removed." DEFVAL { 180 } ::= { tripCfgEntry 12 } tripSendReceiveMode OBJECT-TYPE SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The operational mode of this peer." ::= { tripCfgEntry 13 } -- -- tripSupportedCommunityTable -- tripSupportedCommunityTable OBJECT-TYPE SYNTAX SEQUENCE OF TripSupportedCommunityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The list of TRIP communities that this LS supports. A TRIP community is a group of destinations that share some common property. The TRIP Communities attribute is used to group destinations so that the routing decision can be based on the identity of the group." REFERENCE "draft-ietf-iptel-trip-07.txt, J. Rosenberg et al, section 5.9." ::= { tripMIBObjects 2 } tripSupportedCommunityEntry OBJECT-TYPE SYNTAX TripSupportedCommunityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry containing information a community. A TRIP community is a group of destinations that share some Jiang/Walker/Zinman 11 Internet Draft TRIP MIB July 2001 common property." INDEX { applIndex, tripSupportedCommunityId } ::= { tripSupportedCommunityTable 1 } TripSupportedCommunityEntry ::= SEQUENCE { tripSupportedCommunityId TripItad, tripSupportedCommunityItad TripItad, tripSupportedCommunityRowStatus RowStatus } tripSupportedCommunityId OBJECT-TYPE SYNTAX TripItad MAX-ACCESS not-accessible STATUS current DESCRIPTION "The identifier of the supported Community." ::= { tripSupportedCommunityEntry 1 } tripSupportedCommunityItad OBJECT-TYPE SYNTAX TripItad MAX-ACCESS read-create STATUS current DESCRIPTION "The Itad of the community." ::= { tripSupportedCommunityEntry 2 } tripSupportedCommunityRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The row status of the entry. This object is required to create or delete rows." ::= { tripSupportedCommunityEntry 3 } -- -- TripPeerTable -- tripPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF TripPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The TRIP peer table. This table contains one entry per TRIP peer, and information about the connection with the peer." ::= { tripMIBObjects 4 } tripPeerEntry OBJECT-TYPE SYNTAX TripPeerEntry MAX-ACCESS not-accessible STATUS current Jiang/Walker/Zinman 12 Internet Draft TRIP MIB July 2001 DESCRIPTION "Entry containing information about the connection with a TRIP peer." INDEX { applIndex, tripPeerRemoteAddrInetType, tripPeerRemoteAddr } ::= {tripPeerTable 1} TripPeerEntry ::= SEQUENCE { tripPeerRemoteAddrInetType InetAddressType, tripPeerRemoteAddr InetAddress, tripPeerIdentifier TripId, tripPeerState INTEGER, tripPeerAdminStatus INTEGER, tripPeerNegotiatedVersion Integer32, tripPeerSendReceiveMode INTEGER, tripPeerRemotePort Integer32, tripPeerRemoteItad TripItad, tripPeerConnectRetryInterval Integer32, tripPeerMaxRetryInterval Integer32, tripPeerHoldTime Integer32, tripPeerKeepAlive Integer32, tripPeerHoldTimeConfigured Integer32, tripPeerKeepAliveConfigured Integer32, tripPeerMinItadOriginationInterval Integer32, tripPeerMinRouteAdvertisementInterval Integer32, tripPeerMaxPurgeTime Integer32, tripPeerDisableTime Integer32, tripPeerRowStatus RowStatus } tripPeerRemoteAddrInetType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS not-accessible STATUS current DESCRIPTION "The type of Inet Address of the tripPeerRemoteAddr." REFERENCE "RFC 2851, section 3." ::= { tripPeerEntry 1 } tripPeerRemoteAddr OBJECT-TYPE SYNTAX InetAddress (SIZE(0..125)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The remote IP address of this entry's TRIP peer. The size value of 125 has been assigned due to the sub identifier of object types length limitation as defined in SMIv2." REFERENCE "RFC 2851, section 3." Jiang/Walker/Zinman 13 Internet Draft TRIP MIB July 2001 ::= { tripPeerEntry 2 } tripPeerIdentifier OBJECT-TYPE SYNTAX TripId MAX-ACCESS read-only STATUS current DESCRIPTION "TRIP identifier of this entry's TRIP peer." ::= { tripPeerEntry 3 } tripPeerState OBJECT-TYPE SYNTAX INTEGER { idle(1), connect(2), active(3), openSent(4), openConfirm(5), established(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "TRIP Peer Finite State Machine state. idle(1) : The initial state. Local LS refuses all incoming connections. No resources are allocated to the peer. connect(2) : Local LS waiting for a transport protocol connection to be completed to the peer, and is listening for inbound transport connections from the peer. active(3) : LS is listening for an inbound connection from the peer, but is not in the process of initiating a connection to the peer. openSent(4) : LS has sent an OPEN message to its peer and is waiting for an OPEN message from its peer. openConfirm(5): LS has sent an OPEN to its peer, received an OPEN from its peer, and sent a KEEPALIVE in response to the OPEN. The LS is now waiting for a KEEPALIVE or NOTIFICATION message in response to its OPEN. established(6): LS can exchange UPDATE, NOTIFICATION,and KEEPALIVE messages with its peer." ::= { tripPeerEntry 4 } tripPeerAdminStatus OBJECT-TYPE SYNTAX INTEGER { Jiang/Walker/Zinman 14 Internet Draft TRIP MIB July 2001 up(1), down(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired TRIP connection state." ::= { tripPeerEntry 5 } tripPeerNegotiatedVersion OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The negotiated version of TRIP running between this local entity and this peer." ::= { tripPeerEntry 6 } tripPeerSendReceiveMode OBJECT-TYPE SYNTAX INTEGER { sendReceive(1), sendOnly(2), receiveOnly(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The operational mode of this peer." ::= { tripPeerEntry 7 } tripPeerRemotePort OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The remote port for the TCP connection between the TRIP peers." ::= { tripPeerEntry 8 } tripPeerRemoteItad OBJECT-TYPE SYNTAX TripItad MAX-ACCESS read-create STATUS current DESCRIPTION "The Internet Telephony Administrative domain of this peer." ::= { tripPeerEntry 9 } tripPeerConnectRetryInterval OBJECT-TYPE SYNTAX Integer32 (0..2147483647) UNITS "Seconds" MAX-ACCESS read-create STATUS current Jiang/Walker/Zinman 15 Internet Draft TRIP MIB July 2001 DESCRIPTION "Specifies the initial amount of time that will elapse between connection retry. This value should double after each attempt up to the value of tripPeerMaxRetryInterval." DEFVAL { 120 } ::= { tripPeerEntry 10 } tripPeerMaxRetryInterval OBJECT-TYPE SYNTAX Integer32 (0..2147483647) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the maximum amount of time that will elapse between connection retries." DEFVAL { 360 } ::= { tripPeerEntry 11 } tripPeerHoldTime OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "Seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "The time interval in seconds for the hold timer that is established with the peer. The value of this object is the smaller of the values in tripPeerHoldTimeConfigured and the hold time received in the open message." ::= { tripPeerEntry 12 } tripPeerKeepAlive OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "Seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the amount of time that must elapse between keep alive messages." ::= { tripPeerEntry 13 } tripPeerHoldTimeConfigured OBJECT-TYPE SYNTAX Integer32 (0 | 3..65535) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the maximum time that may elapse between the receipt of successive keepalive or update message." DEFVAL { 240 } ::= { tripPeerEntry 14 } Jiang/Walker/Zinman 16 Internet Draft TRIP MIB July 2001 tripPeerKeepAliveConfigured OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies the amount of time that must elapse between keep alive messages." DEFVAL { 30 } ::= { tripPeerEntry 15 } tripPeerMinItadOriginationInterval OBJECT-TYPE SYNTAX Integer32 (0..2147483647) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Amount of time that must elapse between advertisement of update message that report changes within the Location Server's own ITAD." DEFVAL { 30 } ::= { tripPeerEntry 16 } tripPeerMinRouteAdvertisementInterval OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Specifies minimal interval between successive advertisement to a particular destination from an LS." DEFVAL { 30 } ::= { tripPeerEntry 17 } tripPeerMaxPurgeTime OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Indicate the interval that the location server must maintain routes marked as withdrawn in its database." DEFVAL { 10 } ::= { tripPeerEntry 18 } tripPeerDisableTime OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "Seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "Indicate the interval that the TRIP module of the location server must be disabled while routes Jiang/Walker/Zinman 17 Internet Draft TRIP MIB July 2001 originated by this location server with high sequence numbers can be removed." DEFVAL { 180 } ::= { tripPeerEntry 19 } tripPeerRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to create and delete rows in the tripPeerTable." ::= { tripPeerEntry 20 } -- -- tripPeerRouteTypeTable -- tripPeerRouteTypeTable OBJECT-TYPE SYNTAX SEQUENCE OF TripPeerRouteTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The TRIP peer Route Type table. This table contains one entry per supported protocol - address family pair." ::= { tripMIBObjects 5 } tripPeerRouteTypeEntry OBJECT-TYPE SYNTAX TripPeerRouteTypeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry containing information about the route type that the TRIP peer supports." INDEX { applIndex, tripPeerRemoteAddrInetType, tripPeerRemoteAddr, tripPeerRtTypeProtocolId, tripPeerRtTypeAddrFamilyId } ::= { tripPeerRouteTypeTable 1 } TripPeerRouteTypeEntry ::= SEQUENCE { tripPeerRtTypeProtocolId TripAppProtocol, tripPeerRtTypeAddrFamilyId TripAddressFamily, tripPeerRtTypeRowStatus RowStatus } tripPeerRtTypeProtocolId OBJECT-TYPE SYNTAX TripAppProtocol MAX-ACCESS not-accessible STATUS current DESCRIPTION "The object identifier of a protocol that this peer is using." Jiang/Walker/Zinman 18 Internet Draft TRIP MIB July 2001 ::= { tripPeerRouteTypeEntry 1 } tripPeerRtTypeAddrFamilyId OBJECT-TYPE SYNTAX TripAddressFamily MAX-ACCESS not-accessible STATUS current DESCRIPTION "The object identifier of an address family that this peer belongs to." ::= { tripPeerRouteTypeEntry 2 } tripPeerRtTypeRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-only STATUS current DESCRIPTION "This object is used to instantiate a row in this table. The normal row status values of createAndGo(4), createAndWait(5) and delete(6) have no application in this table." ::= { tripPeerRouteTypeEntry 3 } -- -- TripPeerStatsTable -- tripPeerStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF TripPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The TRIP peer stats table. This table contains one entry per TRIP peer, and statistics related to the connection with the peer." ::= { tripMIBObjects 6 } tripPeerStatsEntry OBJECT-TYPE SYNTAX TripPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry containing information about the connection with a TRIP peer." AUGMENTS { tripPeerEntry } ::= { tripPeerStatsTable 1 } TripPeerStatsEntry ::= SEQUENCE { tripPeerInUpdates Counter32, tripPeerOutUpdates Counter32, tripPeerInTotalMessages Counter32, tripPeerOutTotalMessages Counter32, tripPeerFsmEstablishedTransitions Counter32, tripPeerFsmEstablishedTime DateAndTime, tripPeerInUpdateElapsedTime Gauge32 Jiang/Walker/Zinman 19 Internet Draft TRIP MIB July 2001 } tripPeerInUpdates OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of TRIP update messages received from this peer since the last restart of this location server." ::= { tripPeerStatsEntry 1 } tripPeerOutUpdates OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of TRIP update messages transmitted to this peer since the last restart of this location server." ::= { tripPeerStatsEntry 2 } tripPeerInTotalMessages OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of TRIP messages received to the remote peer on this connection since the last restart of this location server." ::= { tripPeerStatsEntry 3 } tripPeerOutTotalMessages OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of outgoing TRIP messages sent since the last restart of this location server." ::= { tripPeerStatsEntry 4 } tripPeerFsmEstablishedTransitions OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times the TRIP peer has transitioned into the established state since the last restart of this location server." ::= { tripPeerStatsEntry 5 } tripPeerFsmEstablishedTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only Jiang/Walker/Zinman 20 Internet Draft TRIP MIB July 2001 STATUS current DESCRIPTION "Indicates how long in seconds this peer has been in the established state." ::= { tripPeerStatsEntry 6 } tripPeerInUpdateElapsedTime OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Elapsed time in seconds since the last TRIP update message was received from the peer." ::= { tripPeerStatsEntry 7 } -- TRIP Received Route Table. This table contains -- all routes from all sources. Each entry consists -- of a route and its associated path attributes. tripRouteTable OBJECT-TYPE SYNTAX SEQUENCE OF TripRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The TRIP route table containing information about reachable routes that are to be added to service by the receiving LS." ::= { tripMIBObjects 7 } tripRouteEntry OBJECT-TYPE SYNTAX TripRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a route to a called destination." INDEX { applIndex, tripRouteAppProtocol, tripRouteAddressFamily, tripRouteAddress, tripRoutePeer } ::= { tripRouteTable 1 } TripRouteEntry ::= SEQUENCE { tripRouteAppProtocol TripAppProtocol, tripRouteAddressFamily TripAddressFamily, tripRouteAddress OCTET STRING, tripRoutePeer TripId, tripRouteAddressSequenceNumber Integer32, tripRouteAddressOriginatorId TripItad, tripRouteNextHopServerIAddrType InetAddressType, tripRouteNextHopServer InetAddress, tripRouteNextHopServerPort Integer32, Jiang/Walker/Zinman 21 Internet Draft TRIP MIB July 2001 tripRouteNextHopServerItad TripItad, tripRouteMultiExitDisc Unsigned32, tripRouteLocalPref Unsigned32, tripRouteAdvertisementPath OCTET STRING, tripRouteRoutedPath OCTET STRING, tripRouteAtomicAggregate TruthValue, tripRouteBest TruthValue, tripRouteUnknown OCTET STRING, tripRouteWithdrawn TruthValue, tripRouteConverted TruthValue } tripRouteAppProtocol OBJECT-TYPE SYNTAX TripAppProtocol MAX-ACCESS not-accessible STATUS current DESCRIPTION "The protocol for which this routing table is maintained." ::= { tripRouteEntry 1 } tripRouteAddressFamily OBJECT-TYPE SYNTAX TripAddressFamily MAX-ACCESS not-accessible STATUS current DESCRIPTION "Specifies the type of address for the destination route." ::= { tripRouteEntry 2 } tripRouteAddress OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This is an address (prefix) of the family type given by Address Family of the destination." ::= { tripRouteEntry 3 } tripRoutePeer OBJECT-TYPE SYNTAX TripId MAX-ACCESS not-accessible STATUS current DESCRIPTION "The identifier of the peer where the route information was learned." ::= { tripRouteEntry 4 } tripRouteAddressSequenceNumber OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION Jiang/Walker/Zinman 22 Internet Draft TRIP MIB July 2001 "Indicates the version of the destination route originated by the location server identified by tripRouteAddressOriginatorId intra-domain attribute." ::= { tripRouteEntry 5 } tripRouteAddressOriginatorId OBJECT-TYPE SYNTAX TripItad MAX-ACCESS read-only STATUS current DESCRIPTION "This is an intra-domain attribute indicating the internal location server that originated the route into the ITAD." ::= { tripRouteEntry 6 } tripRouteNextHopServerIAddrType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of Inet Address of the tripRouteNextHopServer." REFERENCE "RFC 2851, section 3." ::= { tripRouteEntry 7 } tripRouteNextHopServer OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the next hop that messages of a given protocol destined for tripRouteAddress should be sent to." ::= { tripRouteEntry 8 } tripRouteNextHopServerPort OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The port of the next hop server that this route will use." ::= { tripRouteEntry 9 } tripRouteNextHopServerItad OBJECT-TYPE SYNTAX TripItad MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the domain of the next hop." ::= { tripRouteEntry 10 } Jiang/Walker/Zinman 23 Internet Draft TRIP MIB July 2001 tripRouteMultiExitDisc OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "When two ITADs are connected by more than one set of peers, it is used to descriminate between multiple exit points to an adjacent ITAD." ::= { tripRouteEntry 11 } tripRouteLocalPref OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "Indicated the local LS's degree of preference for an advertised route destination." ::= { tripRouteEntry 12 } tripRouteAdvertisementPath OBJECT-TYPE SYNTAX OCTET STRING (SIZE(4..252)) MAX-ACCESS read-only STATUS current DESCRIPTION "Identifies the ITADs through wich routing information carried in an advertisement has passed. This object is probably best represented as sequence of integer. For SMI compatibility, though, it is represented as OCTET STRING. This object is a sequence of ITADs in network byte order." ::= { tripRouteEntry 13 } tripRouteRoutedPath OBJECT-TYPE SYNTAX OCTET STRING (SIZE(4..252)) MAX-ACCESS read-only STATUS current DESCRIPTION "Identifies the ITADs through which messages sent using this route would pass. These are as subset of tripRouteAdvertisementPath. This object is probably best represented as sequence of integer. For SMI compatibility, though, it is represented as OCTET STRING. This object is a sequence of ITADs in network byte order." ::= { tripRouteEntry 14 } tripRouteAtomicAggregate OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION Jiang/Walker/Zinman 24 Internet Draft TRIP MIB July 2001 "Indicates that a route may traverse domains not listed in tripRouteRoutedPath. If an LS selects the less specific route from a set of overlapping routes, then this value returns TRUE." ::= { tripRouteEntry 15 } tripRouteBest OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of whether this route was chosen as the best TRIP route." ::= { tripRouteEntry 16 } tripRouteUnknown OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "One or more attributes not understood by this location server." ::= { tripRouteEntry 17 } tripRouteWithdrawn OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates if this route is to be removed from service by the receiving LS." ::= { tripRouteEntry 18 } tripRouteConverted OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates if this route has been converted to a different application protocol than it had originally." ::= { tripRouteEntry 19 } -- -- TRIP Received Route CommunityTable. -- tripRouteCommunityTable OBJECT-TYPE SYNTAX SEQUENCE OF TripRouteCommunityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table containing a list of TRIP communities associated Jiang/Walker/Zinman 25 Internet Draft TRIP MIB July 2001 with a route." REFERENCE "draft-ietf-iptel-trip-07.txt, J. Rosenberg et al, section 5.9." ::= { tripMIBObjects 8 } tripRouteCommunityEntry OBJECT-TYPE SYNTAX TripRouteCommunityEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about communities associated with a route. An entry with a tripRouteAddress of 00 and a tripRoutePeer of 0 refers to the local LS." INDEX { applIndex, tripRouteAppProtocol, tripRouteAddressFamily, tripRouteAddress, tripRoutePeer, tripRouteCommunityId } ::= { tripRouteCommunityTable 1 } TripRouteCommunityEntry ::= SEQUENCE { tripRouteCommunityId TripItad, tripRouteCommunityItad TripItad } tripRouteCommunityId OBJECT-TYPE SYNTAX TripItad MAX-ACCESS not-accessible STATUS current DESCRIPTION "The community identifier." ::= { tripRouteCommunityEntry 1 } tripRouteCommunityItad OBJECT-TYPE SYNTAX TripItad MAX-ACCESS read-only STATUS current DESCRIPTION "The ITAD associated with this community." ::= { tripRouteCommunityEntry 2 } -- -- tripItadTopologyTable -- tripItadTopologyTable OBJECT-TYPE SYNTAX SEQUENCE OF TripItadTopologyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION Jiang/Walker/Zinman 26 Internet Draft TRIP MIB July 2001 "The sequence of link connections between peers within an ITAD." ::= { tripMIBObjects 9 } tripItadTopologyEntry OBJECT-TYPE SYNTAX TripItadTopologyEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a peer of the location server identified by tripOriginatorIdentifier." INDEX { applIndex, tripItadTopologyOrigId } ::= { tripItadTopologyTable 1 } TripItadTopologyEntry ::= SEQUENCE { tripItadTopologyOrigId TripItad, tripItadTopologySeqNum Integer32 } tripItadTopologyOrigId OBJECT-TYPE SYNTAX TripItad MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the internal location server that originated the ITAD topology information into the ITAD." ::= { tripItadTopologyEntry 1 } tripItadTopologySeqNum OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the version of the ITAD topology originated by the location server identified by tripOriginatorIdentifier." ::= { tripItadTopologyEntry 2 } -- -- tripItadTopologyIdTable -- tripItadTopologyIdTable OBJECT-TYPE SYNTAX SEQUENCE OF TripItadTopologyIdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The list of other location servers within the ITAD domain that the location server identified by tripOriginatorIdentifier is currently peering." ::= { tripMIBObjects 10 } tripItadTopologyIdEntry OBJECT-TYPE Jiang/Walker/Zinman 27 Internet Draft TRIP MIB July 2001 SYNTAX TripItadTopologyIdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a peer to the location server identified by tripOriginatorIdentifier." INDEX { applIndex, tripItadTopologyOrigId, tripItadTopologyId } ::= { tripItadTopologyIdTable 1 } TripItadTopologyIdEntry ::= SEQUENCE { tripItadTopologyId TripId, tripItadTopologyIdRowStatus RowStatus } tripItadTopologyId OBJECT-TYPE SYNTAX TripId MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index into this entry. Indicates the other location servers within the ITAD domain that this location server identified by tripOriginatorIdentifier is currently peering." ::= { tripItadTopologyIdEntry 1 } tripItadTopologyIdRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-only STATUS current DESCRIPTION "This object is used to instantiate a row in this table. The normal row status values of createAndGo(4), createAndWait(5) and delete(6) have no application in this table." ::= { tripItadTopologyIdEntry 2 } -- -- Notification objects -- tripNotifApplIndex OBJECT-TYPE SYNTAX INTEGER (1..2147483647) MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "This object contains the applIndex as described in RFC 2788. It is used to bind this notification with a specific instance of TRIP entity." ::= { tripMIBNotifications 1 } tripNotifPeerAddrInetType OBJECT-TYPE Jiang/Walker/Zinman 28 Internet Draft TRIP MIB July 2001 SYNTAX InetAddressType MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The type of Inet Address of the tripNotifPeerAddr." REFERENCE "RFC 2851, section 3." ::= { tripMIBNotifications 2 } tripNotifPeerAddr OBJECT-TYPE SYNTAX InetAddress (SIZE(0..125)) MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The remote IP address of this entry's TRIP peer. The size value of 125 has been assigned due to the sub identifier of object types length limitation as defined in SMIv2." REFERENCE "RFC 2851, section 3." ::= { tripMIBNotifications 3 } tripNotifPeerErrCode OBJECT-TYPE SYNTAX INTEGER { messageHeader(1), openMessage(2), updateMessage(3), holdTimerExpired(4), finiteStateMachine(5), cease(6), tripNotification(7) } MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "Notification message of TRIP error. The meaning of this value is applicable to the following functions: 1 - message header. All errors detected while processing the TRIP message header. 2 - open message. All errors detected while processing the OPEN message. 3 - update message. All errors detected while processing the UPDATE message. 4 - hold timer expired. A notification generated when the hold timer expires. 5 - finite state machine. All errors detected by the TRIP Finite State Machine. 6 - cease. Any fatal error condition that the rest of the values do not cover. 7 - trip notification message. Jiang/Walker/Zinman 29 Internet Draft TRIP MIB July 2001 Any error encountered while sending a notification message." ::= { tripMIBNotifications 4 } tripNotifPeerErrSubcode OBJECT-TYPE SYNTAX Integer32 (1..7) MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION "The sub error code associated with error code. The meaning of this value is dependent on the value of tripNotifPeerErrCode. Message Header (1) Error Subcodes: 1 - Bad Message Length. 2 - Bad Message Type. OPEN Message (2) Error Subcodes: 1 - Unsupported Version Number. 2 - Bad Peer ITAD. 3 - Bad TRIP Identifier. 4 - Unsupported Optional Parameter. 5 - Unacceptable Hold Time. 6 - Unsupported Capability. 7 - Capability Mismatch. UPDATE Message (3) Error Subcodes: 1 - Malformed Attribute List. 2 - Unrecognized Well-known Attribute. 3 - Missing Well-known Mandatory Attribute. 4 - Attribute Flags Error. 5 - Attribute Length Error. 6 - Invalid Attribute." ::= { tripMIBNotifications 5 } -- -- Notifications -- tripEstablished NOTIFICATION-TYPE STATUS current DESCRIPTION "The TRIP Established event is generated when the TRIP FSM enters the ESTABLISHED state." ::= { tripMIBNotifications 6 } tripFSM NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex, tripNotifPeerAddrInetType, tripNotifPeerAddr, tripNotifPeerErrCode, tripNotifPeerErrSubcode, tripPeerState } Jiang/Walker/Zinman 30 Internet Draft TRIP MIB July 2001 STATUS current DESCRIPTION "The trip FSM Event is generated when any error is detected by the TRIP Finite State Machine." ::= { tripMIBNotifications 7 } tripOpenMessageError NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex, tripNotifPeerAddrInetType, tripNotifPeerAddr, tripNotifPeerErrCode, tripNotifPeerErrSubcode, tripPeerState } STATUS current DESCRIPTION "Errors detected while processing the OPEN message." ::= { tripMIBNotifications 8 } tripUpdateMessageError NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex, tripNotifPeerAddrInetType, tripNotifPeerAddr, tripNotifPeerErrCode, tripNotifPeerErrSubcode, tripPeerState } STATUS current DESCRIPTION "Errors detected while processing the UPDATE message." ::= { tripMIBNotifications 9 } tripHoldTimerExpired NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex, tripNotifPeerAddrInetType, tripNotifPeerAddr, tripNotifPeerErrCode, tripNotifPeerErrSubcode, tripPeerState } STATUS current DESCRIPTION "The system does not receive successive messages within the period specified by the negotiated Hold Time." ::= { tripMIBNotifications 10 } tripConnectionCollision NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex } STATUS current DESCRIPTION "A pair of LSs tried to simultaneously to establish a transport connection to each other." ::= { tripMIBNotifications 11 } Jiang/Walker/Zinman 31 Internet Draft TRIP MIB July 2001 tripNotificationErr NOTIFICATION-TYPE OBJECTS { tripNotifApplIndex } STATUS current DESCRIPTION "Generated if there is an error detected in a TRIP notification message sent with another cause. Note that the TRIP notification refered to in this object is not an SNMP notification, it is a specific message described in the TRIP specification." REFERENCE "draft-ietf-iptel-trip-07.txt, J. Rosenberg et al, section 6.4." ::= { tripMIBNotifications 12 } -- -- Compliance Statements -- tripCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for TRIP entities." MODULE -- this module MANDATORY-GROUPS { tripConfigGroup, tripPeerTableConfigGroup, tripRouteGroup, tripItadTopologyGroup, tripPeerTableStatsGroup } GROUP tripNotificationGroup DESCRIPTION "This group is optional. A TRIP entity can choose not to send any notifications. If this group is implemented, the tripNotifObjectGroup must also be implemented." GROUP tripNotifObjectGroup DESCRIPTION "This group is optional. A TRIP entity can choose not to send any notifications. If this group is implemented, the tripNotificationGroup must also be implemented." MODULE NETWORK-SERVICES-MIB MANDATORY-GROUPS { applRFC1565Group } ::= { tripMIBCompliance 1 } -- -- Object and event conformance groups -- tripConfigGroup OBJECT-GROUP Jiang/Walker/Zinman 32 Internet Draft TRIP MIB July 2001 OBJECTS { tripProtocolVersion, tripLocalItad, tripIdentifier, tripOperStatus, tripAdminStatus, tripLocalAddrIAddrType, tripLocalAddr, tripLocalPort, tripMinItadOriginationInterval, tripMinRouteAdvertisementInterval, tripMaxPurgeTime, tripDisableTime, tripSendReceiveMode, tripSupportedCommunityItad, tripSupportedCommunityRowStatus } STATUS current DESCRIPTION "The global objects for configuring trip." ::= { tripMIBGroups 1 } tripPeerTableConfigGroup OBJECT-GROUP OBJECTS { tripPeerIdentifier, tripPeerState, tripPeerAdminStatus, tripPeerNegotiatedVersion, tripPeerSendReceiveMode, tripPeerRemotePort, tripPeerRemoteItad, tripPeerConnectRetryInterval, tripPeerMaxRetryInterval, tripPeerHoldTime, tripPeerKeepAlive, tripPeerHoldTimeConfigured, tripPeerKeepAliveConfigured, tripPeerMinItadOriginationInterval, tripPeerMinRouteAdvertisementInterval, tripPeerMaxPurgeTime, tripPeerDisableTime, tripPeerRowStatus } STATUS current DESCRIPTION "The global objects for configuring the TRIP peer table." ::= { tripMIBGroups 2 } tripPeerTableStatsGroup OBJECT-GROUP OBJECTS { tripPeerInUpdates, tripPeerOutUpdates, Jiang/Walker/Zinman 33 Internet Draft TRIP MIB July 2001 tripPeerInTotalMessages, tripPeerOutTotalMessages, tripPeerFsmEstablishedTransitions, tripPeerFsmEstablishedTime, tripPeerInUpdateElapsedTime } STATUS current DESCRIPTION "The global statistics the TRIP peer table." ::= { tripMIBGroups 3 } tripRouteGroup OBJECT-GROUP OBJECTS { tripRouteAddressSequenceNumber, tripRouteAddressOriginatorId, tripRouteNextHopServerIAddrType, tripRouteNextHopServer, tripRouteNextHopServerPort, tripRouteNextHopServerItad, tripRouteMultiExitDisc, tripRouteLocalPref, tripRouteAdvertisementPath, tripRouteRoutedPath, tripRouteAtomicAggregate, tripRouteBest, tripRouteUnknown, tripRouteWithdrawn, tripRouteConverted, tripRouteCommunityItad, tripPeerRtTypeRowStatus } STATUS current DESCRIPTION "The global objects for configuring route attribute." ::= { tripMIBGroups 4 } tripItadTopologyGroup OBJECT-GROUP OBJECTS { tripItadTopologySeqNum, tripItadTopologyIdRowStatus } STATUS current DESCRIPTION "The objects that define the TRIP ITAD topology." ::= { tripMIBGroups 5 } tripNotificationGroup NOTIFICATION-GROUP NOTIFICATIONS { tripEstablished, tripFSM, tripOpenMessageError, Jiang/Walker/Zinman 34 Internet Draft TRIP MIB July 2001 tripUpdateMessageError, tripHoldTimerExpired, tripConnectionCollision, tripNotificationErr } STATUS current DESCRIPTION "A collection of notifications defined for TRIP." ::= { tripMIBGroups 6 } tripNotifObjectGroup OBJECT-GROUP OBJECTS { tripNotifApplIndex, tripNotifPeerAddrInetType, tripNotifPeerAddr, tripNotifPeerErrCode, tripNotifPeerErrSubcode } STATUS current DESCRIPTION "The collection of objects that specify information for TRIP notifications." ::= { tripMIBGroups 7 } END 7. Security Considerations There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. The managed objects in this MIB contain sensitive information since, collectively, they allow tracing and influencing of connections in TRIP devices and provide information of their connection characteristics. It is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use Jiang/Walker/Zinman 35 Internet Draft TRIP MIB July 2001 of the User-based Security Model RFC 2574 [19] and the View-based Access Control Model RFC 2575 [17] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 8. Revision History 8.1. Changes from <draft-zinman-trip-mib-00.txt> o Removed tripRouteAddressLen from the tripRouteTable. o Made use of INET-ADDRESS-MIB and it's TC's for IPv6 compliance. o Changed order of the enumeration of tripPeerSendReceiveMode to comform to TRIP draft. o Added objects tripPeerCircuitCapacity and tripPeerDSPCapacity to support TRIP for Gateways [24]. o Removed tripPeerLastError and tripPeerState objects for tripEstablished notification. o Added local community object. o Added communities table for TRIP routes and removed community object from route table. o Added send/receive capability to local LS. o Added tripRouteAddressFamily as an Index to TripRouteEntry. o Changed enumerations in tripRouteAddressFamily to decimal(1) and hexaDecimal(2). o Support for authentication mechanism from draft-ietf-iptel-trip- authen-00.txt. o Changed name of tripRoutePathSegment to tripRouteRoutedPathSegment. o Added tripRouteConverted to the routing table to signify a Converted Route. o Changed DEFVAL of tripPeerConnectRetryInterval from 60 to 120 seconds. o Added DEFVAL to tripPeerKeepAlive of 30 seconds. o Added DEFVAL to tripMaxPurgeTime and tripPeerMaxPurgeTime of 10 seconds. o Added DEFVAL to tripDisableTime and tripPeerDisableTime of 180 seconds. o Changed DEFVAL of tripMinItadOriginationInterval and tripPeerMinItadOriginationInterval to 30 seconds. o Removed tripHoldTimeConfigured and tripKeepAliveConfigured from TripCfgEntry. o changed names from opMode to sendReceiveMode. 8.2. Changes from <draft-zinman-trip-mib-01.txt> o Added tripOperStatus. o Changed definition of textual convention TripAppProtocol to Jiang/Walker/Zinman 36 Internet Draft TRIP MIB July 2001 OBJECT IDENTIFIER. See [2] section 13.4 o Changed definition of textual convention TripAddressFamily to OBJECT IDENTIFIER. See [2] section 13.3 o Added object identifiers for tripSupportedProtocols and tripAddressFamilies. o Removed authentication tables. o Removed textual convention TripPublicKey. o Changed the position of the MIB branches slightly. o Changed name of tripPeerLastError to tripNotifPeerErrCode and MAX-ACCESS to accessible-for-notify. o Separated tripNotifPeerErrSubcode from tripNotifPeerErrCode and made them both integers. o Added compliance statements. o Changed MAX-ACCESS of tripPeerRemoteItad to read-create. o Changed DEFVAL of tripPeerHoldTimeConfigured from 90 to 240. 9. References 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2 Rosenberg, J., Salama, H. and Squire, M., "Telephony Routing over IP (TRIP)", draft-ietf-iptel-trip-07.txt, work in progress. 3 Rekhter, Y. and Li, T., "Border Gateway Protocol 4 (BGP-4)", IETF RFC 1771, March 1995. 4 Willis, S., Burruss, J. and Chu, J., "Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2" IETF RFC 1657, July 1994. 5 Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 6 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. 7 Rose, M. and McCloghrie, K., "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 8 Rose, M. and McCloghrie, K., "Concise MIB Definitions", STD 16, RFC 1212, March 1991. 9 Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. 10 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and Waldbusser, S., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 11 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, Jiang/Walker/Zinman 37 Internet Draft TRIP MIB July 2001 M. and Waldbusser, S., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. 12 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and Waldbusser, S., "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. 13 Case, J., Fedor, M., Schoffstall, M. and Davin, J.,"Simple Network Management Protocol", STD 15, RFC 1157, May 1990. 14 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 15 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. 16 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 17 Wijnen, B., Presuhn, R. and McCloghrie, K., "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999. 18 Freed, N. and Kille, S., "Network Services Monitoring MIB", RFC 2788, March 2000. 19 Blumenthal, U. and Wijnen, B., "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. 20 Rosenberg, J. and Salama, H., "Usage of TRIP in Gateways for Exporting Phone Routes", draft-rs-trip-gw-01.txt, work in progress. 21 Case, J., Harrington, D., Presuhn, R., and Wijnen, B. "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. 22 Levi, D., Meyer, P., and Stewart B., "SNMP Applications", RFC 2573, April 1999. 24 Case, J., Mundy, R., Partain, D., and Stewart, B., "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. 10. Author's Address David Zinman SS8 Networks, Inc. Jiang/Walker/Zinman 38 Internet Draft TRIP MIB July 2001 495 March Road, Suite #500 Ottawa, ON K2K 3G1 Canada Phone: +1 613 592 2100 Email: david@ss8.com Dave Walker SS8 Networks, Inc. 495 March Road, Suite #500 Ottawa, ON K2K 3G1 Canada Phone: +1 613 592 2100 Email: drwalker@ss8.com Jianping Jiang SS8 Networks, Inc. 55 Commerce Valley Drive West, Suite #510 Thornhill, ON, L3T 7B9 Canada phone: +1 905 889 5900 Email: jianping@ss8.com 11. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 12. Full Copyright Statement Copyright (C) The Internet Society (2001). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published Jiang/Walker/Zinman 39 Internet Draft TRIP MIB July 2001 and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Jiang/Walker/Zinman 40