AAA Working Group J. Koehler Internet-Draft M. Eklund Category: Standards Track H. Li Cisco Systems, Inc. expires December 2001 June 2001 Diameter Base Protocol MIB Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Koehler et al. expires December 2001 [Page 1] Internet-Draft Diameter Base Protocol MIB June 2001 Abstract The Diameter base protocol is intended to provide a AAA framework for Mobile-IP [17, 18] , NASREQ [16] and ROAMOPS [21]. This draft defines the Management Information Base (MIB) module which describes the minimum amount of objects needed to manage the implementation of the Diameter base protocol. 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 managed objects used for managing Diameter base protocol. The Diameter base protocol provides the minimum requirements needed for an AAA transport protocol, as required by NASREQ [16], Mobile IP [17, 18], and ROAMOPS [21]. Over time, routers and network access servers (NAS) have increased in complexity and density, making the historically used RADIUS protocol increasingly unsuitable. The basic concept behind Diameter is to provide a base protocol that can be extended in order to provide AAA services to new access technologies. Currently, the protocol only concerns itself with Internet access, both in the traditional PPP sense as well as taking into account the ROAMOPS model, and Mobile-IP. 2. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [1]. 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 15, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 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 [8]. A second version of the Koehler et al. expires December 2001 [Page 2] Internet-Draft Diameter Base Protocol MIB June 2001 SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13]. o A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [22]. 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. 3. Overview The base Diameter protocol is never used on its own. It is always extended for a particular application. Three Diameter applications are defined by companion documents: NASREQ [16], Mobile IP [17, 18], End-to-End Security [19]. This MIB supports objects which are defined in the base Diameter protocol as described in [20]. Objects related to the additional applications mentioned above will be implemented in separate MIBS as well as any additional applications added in the future. Koehler et al. expires December 2001 [Page 3] Internet-Draft Diameter Base Protocol MIB June 2001 4. Definitions DIAMETER-BASE-PROTOCOL-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Counter32, Integer32, Unsigned32, IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI SnmpAdminString FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; diameterBaseProtocolMIB MODULE-IDENTITY LAST-UPDATED "200106280000Z" ORGANIZATION "IETF AAA Working Group." CONTACT-INFO " Mark Eklund Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 US Phone: +1 865 671 6255 Email: meklund@cisco.com Jay Koehler Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 US Phone: +1 865 671 0429 EMail: koehler@cisco.com Hai Li Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 US Phone: +1 865 671 0429 EMail: haili@cisco.com" DESCRIPTION "The MIB module is based on the Diameter base protocol, draft-ietf-aaa-diameter-06.txt." ::= { mib-2 TBD } Koehler et al. expires December 2001 [Page 4] ^L Internet-Draft Diameter Base Protocol MIB June 2001 diameterBaseProtocolMIBObjects OBJECT IDENTIFIER ::= { diameterBaseProtocolMIB 1 } diameterBaseTables OBJECT IDENTIFIER ::= { diameterBaseProtocolMIBObjects 1 } diameterBaseHostConfigs OBJECT IDENTIFIER ::= { diameterBaseProtocolMIBObjects 2 } diameterBaseHostStats OBJECT IDENTIFIER ::= { diameterBaseProtocolMIBObjects 3 } diameterServerID OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The implementation identification string for the Diameter authentication server software in use on the system, for example; `FNS-2.1'" ::= {diameterBaseHostConfigs 1} diameterHostAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The Host-IP-Address used for connections that span multiple interfaces, hence multiple IP addresses." ::= {diameterBaseHostConfigs 2} diameterTcpListenPort OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Diameter Tcp listen port." ::= {diameterBaseHostConfigs 3 } diameterSctpListenPort OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "Diameter Sctp listen port." ::= {diameterBaseHostConfigs 4 } diameterServerStatsTotalPacketsIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current Koehler et al. expires December 2001 [Page 5] ^L Internet-Draft Diameter Base Protocol MIB June 2001 DESCRIPTION "The total number of packets in." ::= { diameterBaseHostStats 1 } diameterServerStatsTotalPacketsOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of packets out." ::= { diameterBaseHostStats 2 } diameterServerStatsTotalUpTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The total server up time." ::= { diameterBaseHostStats 3 } diameterApplicationsTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter supported applications." ::= { diameterBaseTables 1 } diameterApplicationsEntry OBJECT-TYPE SYNTAX DiameterApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter server." INDEX { diameterApplicationsIndex } ::= { diameterApplicationsTable 1 } DiameterApplicationsEntry ::= SEQUENCE { diameterApplicationsIndex Unsigned32 } diameterApplicationsIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number uniquely identifying the Diameter server supported applications." Koehler et al. expires December 2001 [Page 6] ^L Internet-Draft Diameter Base Protocol MIB June 2001 ::= { diameterApplicationsEntry 1 } diameterPeerServerTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerServerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Discovered and Configured Peer Servers information." ::= { diameterBaseTables 2 } diameterPeerServerEntry OBJECT-TYPE SYNTAX DiameterPeerServerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex } ::= { diameterPeerServerTable 1 } DiameterPeerServerEntry ::= SEQUENCE { diameterPeerServerIndex Unsigned32, diameterPeerServerId SnmpAdminString, diameterPeerServerAddress IpAddress, diameterPeerServerPortConnect Integer32, diameterPeerServerPortListen Integer32, diameterPeerServerProtocol INTEGER, diameterPeerServerSecurity INTEGER, diameterPeerServerVendorId Unsigned32 } diameterPeerServerIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying each Diameter Peer with which the host server communicates." ::= { diameterPeerServerEntry 1 } diameterPeerServerId OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The server identifier for the Diameter Peer." ::= { diameterPeerServerEntry 2 } Koehler et al. expires December 2001 [Page 7] ^L Internet-Draft Diameter Base Protocol MIB June 2001 diameterPeerServerAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IpAddress for the Diameter Peer." ::= { diameterPeerServerEntry 3 } diameterPeerServerPortConnect OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The connection port for the Diameter Peer. If there is no active connection, this value will be zero(0)." ::= { diameterPeerServerEntry 4 } diameterPeerServerPortListen OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The port the Diameter Peer is listening on." ::= { diameterPeerServerEntry 5 } diameterPeerServerProtocol OBJECT-TYPE SYNTAX INTEGER { tcp(1), sctp(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The protocol the Diameter Peer is using." ::= { diameterPeerServerEntry 6 } diameterPeerServerSecurity OBJECT-TYPE SYNTAX INTEGER { tls(1) } MAX-ACCESS read-only STATUS current DESCRIPTION "The security the Diameter Peer is using." ::= { diameterPeerServerEntry 7 } diameterPeerServerVendorId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The IANA Enterprise Codes value assigned to the vendor of the Diameter device." Koehler et al. expires December 2001 [Page 8] ^L Internet-Draft Diameter Base Protocol MIB June 2001 ::= { diameterPeerServerEntry 8 } diameterPeerIpAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerIpAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter peer Ip Addresses." ::= { diameterBaseTables 3 } diameterPeerIpAddrEntry OBJECT-TYPE SYNTAX DiameterPeerIpAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Peer Diameter server." INDEX { diameterPeerServerIndex, diameterIteratorIndex } ::= { diameterPeerIpAddrTable 1 } DiameterPeerIpAddrEntry ::= SEQUENCE { diameterIteratorIndex Unsigned32, diameterIpAddress IpAddress } Koehler et al. expires December 2001 [Page 9] ^L Internet-Draft Diameter Base Protocol MIB June 2001 diameterIteratorIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying the number of Ip Addresses supported by all Peer Diameter Servers." ::= { diameterPeerIpAddrEntry 1 } diameterIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The Ip Address used for connections." ::= {diameterPeerIpAddrEntry 2} diameterAdvToPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterAdvToPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the advertised applications from host to peer and the type of services supported, accounting, authentication or both." ::= { diameterBaseTables 4 } diameterAdvToPeerEntry OBJECT-TYPE SYNTAX DiameterAdvToPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex, diameterAdvToPeerIndex } ::= { diameterAdvToPeerTable 1 } DiameterAdvToPeerEntry ::= SEQUENCE { diameterAdvToPeerIndex Unsigned32, diameterAdvToPeerTypes INTEGER } diameterAdvToPeerIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current Koehler et al. expires December 2001 [Page 10] ^L Internet-Draft Diameter Base Protocol MIB June 2001 DESCRIPTION "A number uniquely identifying the applications advertised to be supported to each Diameter Peer." ::= { diameterAdvToPeerEntry 1 } diameterAdvToPeerTypes OBJECT-TYPE SYNTAX INTEGER { accounting(1), auth(2), both(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type of services supported for each application, accounting, authentication or both." ::= { diameterAdvToPeerEntry 2 } diameterAdvFromPeerTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterAdvFromPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the advertised applications to peer from host and the type of services supported, accounting, authentication or both." ::= { diameterBaseTables 5 } diameterAdvFromPeerEntry OBJECT-TYPE SYNTAX DiameterAdvFromPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex, diameterAdvFromPeerIndex } ::= { diameterAdvFromPeerTable 1 } DiameterAdvFromPeerEntry ::= SEQUENCE { diameterAdvFromPeerIndex Unsigned32, diameterAdvFromPeerTypes INTEGER } diameterAdvFromPeerIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying the applications Koehler et al. expires December 2001 [Page 11] ^L Internet-Draft Diameter Base Protocol MIB June 2001 advertised to be supported from each Diameter Peer." ::= { diameterAdvFromPeerEntry 1 } diameterAdvFromPeerTypes OBJECT-TYPE SYNTAX INTEGER { accounting(1), auth(2), both(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type of services supported for each application, accounting, authentication or both." ::= { diameterAdvFromPeerEntry 2 } diameterPeerVendorIdTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerVendorIdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the supported vendor identifiers which may be use in order to know which vendor specific attributes may be sent to the peer." ::= { diameterBaseTables 6 } diameterPeerVendorIdEntry OBJECT-TYPE SYNTAX DiameterPeerVendorIdEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Discovered and Configured Peer Server." INDEX { diameterPeerServerIndex, diameterPeerVendorIdIndex} ::= { diameterPeerVendorIdTable 1 } DiameterPeerVendorIdEntry ::= SEQUENCE { diameterPeerVendorIdIndex Unsigned32 } diameterPeerVendorIdIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The IANA Enterprise Codes value assigned to the vendor of the Diameter device." ::= { diameterPeerVendorIdEntry 1 } Koehler et al. expires December 2001 [Page 12] ^L Internet-Draft Diameter Base Protocol MIB June 2001 diameterPerPeerStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPerPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Peer Statistics." ::= { diameterBaseTables 7 } diameterPerPeerStatsEntry OBJECT-TYPE SYNTAX DiameterPerPeerStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Peer." INDEX { diameterPeerServerIndex } ::= { diameterPerPeerStatsTable 1 } DiameterPerPeerStatsEntry ::= SEQUENCE { diameterPerPeerStatsASRIn Counter32, diameterPerPeerStatsASROut Counter32, diameterPerPeerStatsASAIn Counter32, diameterPerPeerStatsASAOut Counter32, diameterPerPeerStatsACRIn Counter32, diameterPerPeerStatsACROut Counter32, diameterPerPeerStatsACAIn Counter32, diameterPerPeerStatsACAOut Counter32, diameterPerPeerStatsCERIn Counter32, diameterPerPeerStatsCEROut Counter32, diameterPerPeerStatsCEAIn Counter32, diameterPerPeerStatsCEAOut Counter32, diameterPerPeerStatsDWRIn Counter32, diameterPerPeerStatsDWROut Counter32, diameterPerPeerStatsDWAIn Counter32, diameterPerPeerStatsDWAOut Counter32, diameterPerPeerStatsMRAIn Counter32, diameterPerPeerStatsMRAOut Counter32, diameterPerPeerStatsSTRIn Counter32, diameterPerPeerStatsSTROut Counter32, diameterPerPeerStatsSTAIn Counter32, diameterPerPeerStatsSTAOut Counter32, diameterPerPeerStatsDWReqTimer TimeTicks, diameterPeerStatsAccSessState INTEGER, diameterPeerStatsFailAccRequests Counter32, diameterPeerStatsState INTEGER, diameterPeerStatsStateDuration TimeTicks, diameterPeerStatsEndToEndErrors Counter32, diameterPeerStatsTransientFailure Counter32, Koehler et al. expires December 2001 [Page 13] ^L Internet-Draft Diameter Base Protocol MIB June 2001 diameterPeerStatsPermanentFailure Counter32, diameterPeerStatsInfoEvent Counter32, diameterPeerStatsRedirectEvent Counter32, diameterPeerStatsSessTerminSent Counter32, diameterPeerStatsConnectionUpTime TimeTicks } diameterPerPeerStatsASRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Request's in per peer." ::= { diameterPerPeerStatsEntry 1 } diameterPerPeerStatsASROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Request's out per peer." ::= { diameterPerPeerStatsEntry 2 } diameterPerPeerStatsASAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Answer in per peer." ::= { diameterPerPeerStatsEntry 3 } diameterPerPeerStatsASAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Abort-Session-Answer out per peer." ::= { diameterPerPeerStatsEntry 4 } diameterPerPeerStatsACRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Request in per peer." ::= { diameterPerPeerStatsEntry 5 } diameterPerPeerStatsACROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only Koehler et al. expires December 2001 [Page 14] ^L Internet-Draft Diameter Base Protocol MIB June 2001 STATUS current DESCRIPTION "Accounting-Request out per peer." ::= { diameterPerPeerStatsEntry 6 } diameterPerPeerStatsACAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Answer in per peer." ::= { diameterPerPeerStatsEntry 7 } diameterPerPeerStatsACAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Accounting-Answer out per peer." ::= { diameterPerPeerStatsEntry 8 } diameterPerPeerStatsCERIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Capabilities-Exchange-Request in per peer." ::= { diameterPerPeerStatsEntry 9 } diameterPerPeerStatsCEROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Capabilities-Exchange-Request out per peer." ::= { diameterPerPeerStatsEntry 10 } diameterPerPeerStatsCEAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Capabilities-Exchange-Answer in per peer." ::= { diameterPerPeerStatsEntry 11 } diameterPerPeerStatsCEAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current Koehler et al. expires December 2001 [Page 15] ^L Internet-Draft Diameter Base Protocol MIB June 2001 DESCRIPTION "Capabilities-Exchange-Answer out per peer." ::= { diameterPerPeerStatsEntry 12 } diameterPerPeerStatsDWRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Request in per peer." ::= { diameterPerPeerStatsEntry 13 } diameterPerPeerStatsDWROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Request out per peer." ::= { diameterPerPeerStatsEntry 14 } diameterPerPeerStatsDWAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Answer in per peer." ::= { diameterPerPeerStatsEntry 15 } diameterPerPeerStatsDWAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog-Answer out per peer." ::= { diameterPerPeerStatsEntry 16 } diameterPerPeerStatsMRAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Message-Reject-Answer in per peer." ::= { diameterPerPeerStatsEntry 17 } diameterPerPeerStatsMRAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current Koehler et al. expires December 2001 [Page 16] ^L Internet-Draft Diameter Base Protocol MIB June 2001 DESCRIPTION "Message-Reject-Answer out per peer." ::= { diameterPerPeerStatsEntry 18 } diameterPerPeerStatsSTRIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Request in per peer." ::= { diameterPerPeerStatsEntry 19 } diameterPerPeerStatsSTROut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Request out per peer." ::= { diameterPerPeerStatsEntry 20 } diameterPerPeerStatsSTAIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Answer in per peer." ::= { diameterPerPeerStatsEntry 21 } diameterPerPeerStatsSTAOut OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session-Termination-Answer out per peer." ::= { diameterPerPeerStatsEntry 22 } diameterPerPeerStatsDWReqTimer OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "Device-Watchdog Request Timer per peer." ::= { diameterPerPeerStatsEntry 23 } diameterPeerStatsAccSessState OBJECT-TYPE SYNTAX INTEGER { idle(1), pending(2), open(3), discon(4), closed(5) } Koehler et al. expires December 2001 [Page 17] ^L Internet-Draft Diameter Base Protocol MIB June 2001 MAX-ACCESS read-only STATUS current DESCRIPTION "State of accounting services." ::= { diameterPerPeerStatsEntry 24 } diameterPeerStatsFailAccRequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Failed accounting requests in and out per peer." ::= { diameterPerPeerStatsEntry 25 } diameterPeerStatsState OBJECT-TYPE SYNTAX INTEGER { closed(1), wait-conn-ack(2), wait-r-cer(3), wait-r-cea(4), i-open(5), elect(6), wait-returns(7), r-open(8), wait-i-cea-2(9), wait-conn-ack-2(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "State of peer that Diameter server is communicating with." ::= { diameterPerPeerStatsEntry 26 } diameterPeerStatsStateDuration OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "Peer state duration." ::= { diameterPerPeerStatsEntry 27 } diameterPeerStatsEndToEndErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "End to End error count." ::= { diameterPerPeerStatsEntry 28 } Koehler et al. expires December 2001 [Page 18] ^L Internet-Draft Diameter Base Protocol MIB June 2001 diameterPeerStatsTransientFailure OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Transient Failure count." ::= { diameterPerPeerStatsEntry 29 } diameterPeerStatsPermanentFailure OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Permanent Failure count." ::= { diameterPerPeerStatsEntry 30 } diameterPeerStatsInfoEvent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Information Event count." ::= { diameterPerPeerStatsEntry 31 } diameterPeerStatsRedirectEvent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Redirect Event count." ::= { diameterPerPeerStatsEntry 32 } diameterPeerStatsSessTerminSent OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Session Terminate Sent count." ::= { diameterPerPeerStatsEntry 33 } diameterPeerStatsConnectionUpTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "Peer session connection up time." ::= { diameterPerPeerStatsEntry 34 } Koehler et al. expires December 2001 [Page 19] Internet-Draft Diameter Base Protocol MIB June 2001 diameterPeerApplicationsTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterPeerApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Peer supported applications." ::= { diameterBaseTables 8 } diameterPeerApplicationsEntry OBJECT-TYPE SYNTAX DiameterPeerApplicationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Peer." INDEX { diameterPeerServerIndex, diameterPeerApplicationsIndex } ::= { diameterPeerApplicationsTable 1 } DiameterPeerApplicationsEntry ::= SEQUENCE { diameterPeerApplicationsIndex Unsigned32, diameterPeerApplicationsSupported Unsigned32 } diameterPeerApplicationsIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number uniquely identifying the application with which this peer server supports." ::= { diameterPeerApplicationsEntry 1 } diameterPeerApplicationsSupported OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "A number uniquely identifying the application with which this peer server supports." ::= { diameterPeerApplicationsEntry 2 } diameterRealmBasedMessageRouteTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterRealmBasedMessageRouteEntry MAX-ACCESS not-accessible STATUS current Koehler et al. expires December 2001 [Page 20] ^L Internet-Draft Diameter Base Protocol MIB June 2001 DESCRIPTION "The (conceptual) table listing the Diameter Realm Based Message Route information." ::= { diameterBaseTables 9 } diameterRealmBasedMessageRouteEntry OBJECT-TYPE SYNTAX DiameterRealmBasedMessageRouteEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Realm Based Message Route server." INDEX { diameterRealmBasedMessageRouteIndex } ::= { diameterRealmBasedMessageRouteTable 1 } DiameterRealmBasedMessageRouteEntry ::= SEQUENCE { diameterRealmBasedMessageRouteIndex Unsigned32, diameterRealmBasedMessageRouteRealm SnmpAdminString, diameterRealmBasedMessageRouteApplication Unsigned32, diameterRealmBasedMessageRouteType INTEGER, diameterRealmBasedMessageRouteLocalAction INTEGER } diameterRealmBasedMessageRouteIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying each Realm." ::= { diameterRealmBasedMessageRouteEntry 1 } diameterRealmBasedMessageRouteRealm OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "Realm name" ::= { diameterRealmBasedMessageRouteEntry 2 } diameterRealmBasedMessageRouteApplication OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "Application requested by the user." ::= { diameterRealmBasedMessageRouteEntry 3 } diameterRealmBasedMessageRouteType OBJECT-TYPE SYNTAX INTEGER { accounting(1), auth(2), both(3) } Koehler et al. expires December 2001 [Page 21] ^L Internet-Draft Diameter Base Protocol MIB June 2001 MAX-ACCESS read-only STATUS current DESCRIPTION "The type of services supported for each application, accounting, authentication or both." ::= { diameterRealmBasedMessageRouteEntry 4 } diameterRealmBasedMessageRouteLocalAction OBJECT-TYPE SYNTAX INTEGER { local(1), relay(2), proxy(3), redirect(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The local action is used to identify how a message should be treated based on the realm, application and type." ::= { diameterRealmBasedMessageRouteEntry 5 } diameterRealmKnownPeersTable OBJECT-TYPE SYNTAX SEQUENCE OF DiameterRealmKnownPeersEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing the Diameter Realms and known peers ." ::= { diameterBaseTables 10 } diameterRealmKnownPeersEntry OBJECT-TYPE SYNTAX DiameterRealmKnownPeersEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a Diameter Realm and known peers." INDEX { diameterRealmBasedMessageRouteIndex, diameterRealmKnownPeersIndex } ::= { diameterRealmKnownPeersTable 1 } DiameterRealmKnownPeersEntry ::= SEQUENCE { diameterRealmKnownPeersIndex Unsigned32, diameterRealmKnownPeersMapToPeerServer Unsigned32 } diameterRealmKnownPeersIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION Koehler et al. expires December 2001 [Page 22] ^L Internet-Draft Diameter Base Protocol MIB June 2001 "A sequential identifier number." ::= { diameterRealmKnownPeersEntry 1 } diameterRealmKnownPeersMapToPeerServer OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index of the peer this realm knows about. Same as the diameterPeerServerIndex." ::= { diameterRealmKnownPeersEntry 2 } END 5. References [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 2001. [2] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, Performance Systems International, March 1991. [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2001. [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 2001. [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 2001. [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990. [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. Koehler et al. expires December 2001 [Page 23] ^L Internet-Draft Diameter Base Protocol MIB June 2001 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 2001. [12] Blumenthal, U., and B. Wijnen, "User-based Security Model for Version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 2001. [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC 2573, April 2001. [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2575, April 2001. [16] P. Calhoun, W. Bulley, A. Rubens, J. Haag, "Diameter NASREQ Application", draft-ietf-aaa-diameter-nasreq-05.txt, IETF work in progress, June 2001. [17] P. Calhoun, C. Perkins, "Diameter Mobile IP Application", draft-ietf-aaa-diameter-mobileip-05.txt, IETF work in progress, June 2001. [18] T. Hiller and al, "CDMA2000 Wireless Data Requirements for AAA", draft-hiller-cdma2000-aaa-02.txt, IETF work in progress, Sep- tember 2000. [19] P. Calhoun, W. Bulley, S. Farrell, "Diameter CMS Security appli- cation", draft-ietf-aaa-diameter-cms-sec-00.txt (work in pro- gress), June 2001. [20] P. Calhoun, H. Akhtar, J. Arkko, E. Guttman, A. Rubens, G. Zorn, "Diameter Base Protocol", draft-ietf-aaa-diameter-06.txt, IETF work in progress, May 2001. [21] B. Aboba, G. Zorn, "Criteria for Evaluating Roaming Protocols", RFC 2477, January 1999. [22] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. Koehler et al. expires December 2001 [Page 24] ^L Internet-Draft Diameter Base Protocol MIB June 2001 6. Acknowledgements The authors would like to thank David Battle for his participation and suggestions in designing the table structures. 7. Security Considerations There are no management objects defined in this MIB that have a MAX- ACCESS clause of read-write and/or read-create. So, if this MIB is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET operations. There are a number of managed objects in this MIB that may contain sensitive information. These are: diameterHostAddress, diameterPeerServerAddress, diameterPeerIpAddress, This can be used to determine the address of the Diameter host server, peer server, etc with which the servers are communicating. This information could be useful in impersonating the peer server. It is thus important to control 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), there is no control as to who on the secure network is allowed to access and GET (read) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [12] and the View-based Access Control Model RFC 2575 [15] 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. Authors' Addresses Mark Eklund Cisco Systems, Inc. Koehler et al. expires December 2001 [Page 25] ^L Internet-Draft Diameter Base Protocol MIB June 2001 10850 Murdock Road Knoxville, TN 37932 Phone: 865-671-6255 Knoxville, TN 37932 Jay Koehler Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 Phone: 865-671-0429 EMail: jkoehler@cisco.com Hai Li Cisco Systems, Inc. 10850 Murdock Road Knoxville, TN 37932 Phone: 865-777-1563 EMail: hali@cisco.com 9. 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 implmentation may be prepared, copied, published 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. Koehler et al. expires December 2001 [Page 26] Internet-Draft Diameter Base Protocol MIB June 2001 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.