Network Working Group S. De Cnodder Internet-Draft Alcatel Expires: December 8, 2004 N. Jonnala Future Soft M. Chiba Cisco Systems, Inc. June 9, 2004 Dynamic Authorization Client MIB draft-decnodder-radext-dynauth-client-mib-01.txt 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. This Internet-Draft will expire on December 8, 2004. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. 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 the RADIUS dynamic authorization client (DAC) functions that support the dynamic authorization extensions as defined in RFC3576. De Cnodder, et al. Expires December 8, 2004 [Page 1] Internet-Draft Dynamic Authorization Client MIB June 2004 Table of Contents 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. The Internet-Standard Management Framework . . . . . . . . . . 5 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. RADIUS Dynamic Authorization Client MIB Definitions . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 21 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 22 9.2 Informative References . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . 24 De Cnodder, et al. Expires December 8, 2004 [Page 2] Internet-Draft Dynamic Authorization Client MIB June 2004 1. Requirements notation 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 [RFC2119]. De Cnodder, et al. Expires December 8, 2004 [Page 3] Internet-Draft Dynamic Authorization Client MIB June 2004 2. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. It is becoming unavoidable to support Dynamic Authorization extensions to send the Disconnect and CoA requests to the NAS devices as described in [RFC3576] . As a result, the effective management of RADIUS Dynamic Authorization entities is of considerable importance. It complements the managed objects used for managing RADIUS authentication and accounting servers as described in [RFC2619] and [RFC2621], respectively. De Cnodder, et al. Expires December 8, 2004 [Page 4] Internet-Draft Dynamic Authorization Client MIB June 2004 3. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC2578 [RFC2578], STD 58, RFC2579 [RFC2579] and STD 58, RFC2580 [RFC2580]. De Cnodder, et al. Expires December 8, 2004 [Page 5] Internet-Draft Dynamic Authorization Client MIB June 2004 4. Terminology Dynamic Authorization Server (DAS) The component that resides on the NAS which processes the Disconnect and CoA requests sent by the Dynamic Authorization Client as described in [RFC3576]. Dynamic Authorization Client (DAC) The component which sends the Disconnect and CoA requests to the Dynamic Authorization Server as described in [RFC3576]. Dynamic Authorization Server Port The UDP port on which the Dynamic Authorization server listens for the Disconnect and CoA requests sent by the Dynamic Authorization Client. De Cnodder, et al. Expires December 8, 2004 [Page 6] Internet-Draft Dynamic Authorization Client MIB June 2004 5. Overview The RADIUS dynamic authorization extensions defined in [RFC3576], distinguishes between the client function and the server function. In RADIUS dynamic authorization, clients send Disconnect-Requests and CoA-Requests, and servers reply with Disconnect-Acks, CoA-Acks, and CoA-NAKs. Typically NAS devices implement the DAS function, and thus would be expected to implement the RADIUS dynamic authorization server MIB, while DACs implement the client function, and thus would be expected to implement the RADIUS dynamic authorization client MIB. However, it is possible for a RADIUS dynamic authorization entity to perform both client and server functions. For example, a RADIUS proxy may act as a DAS to one or more DACs, while simultaneously acting as a DAC to one or more DASs. In such situations, it is expected that RADIUS entities combining client and server functionality will support both the client and server MIBs. This memo describes the MIB for dynamic authorization clients and relates to the following document as follows: [RFC2618] describes the MIB for a RADIUS authentication client. [RFC2619] describes the MIB for a RADIUS authentication server. [RFC2620] describes the MIB for a RADIUS accounting client. [RFC2621] describes the MIB for a RADIUS accounting server. [DYNSERV] describes the MIB for a RADIUS dynamic authorization server. +---------------+ +---------------+ User 1----| | Disconnect-Request | | | Dynamic | CoA-Request | Dynamic | user 2----| Authorization |<---------------------| Authorization | | Server |--------------------->| Client | User 3----| (DAS) | Disconnect-Ack | (DAC) | | | Disconnect-NAK | | +---------------+ CoA-Ack/CoA-NAK +---------------+ Figure 1: Mapping of clients and servers. This MIB module contains the following. 1. two scalar objects De Cnodder, et al. Expires December 8, 2004 [Page 7] Internet-Draft Dynamic Authorization Client MIB June 2004 2. One Dynamic Authorization Server Table. This table contains one row for each DAS that the DAC shares a secret with. De Cnodder, et al. Expires December 8, 2004 [Page 8] Internet-Draft Dynamic Authorization Client MIB June 2004 6. RADIUS Dynamic Authorization Client MIB Definitions RADIUS-DYNAUTH-CLIENT-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Counter32, Gauge32, Integer32, mib-2 FROM SNMPv2-SMI SnmpAdminString FROM SNMP-FRAMEWORK-MIB InetAddressType, InetAddress FROM INET-ADDRESS-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; radiusDynAuthClientMIB MODULE-IDENTITY LAST-UPDATED "200404260000Z" -- 26 April 2004 ORGANIZATION "IETF RADEXT Working Group" CONTACT-INFO " Stefaan De Cnodder Alcatel Francis Wellesplein 1 B-2018 Antwerp Belgium Phone: +32 3 240 85 15 EMail: stefaan.de_cnodder@alcatel.be Nagi Reddy Jonnala Future Soft 480 - 481, Anna Salai Nandanam, Chennai India EMail: nagi_reddy.jonnala@alcatel.be Murtaza Chiba Cisco Systems, Inc. 170 West Tasman Dr. San Jose CA, 95134 Phone: +1 408 525 7198 EMail: mchiba@cisco.com " DESCRIPTION "The MIB module for entities implementing the client side of the Dynamic Authorization extensions Remote Access Dialin User Service (RADIUS) protocol. Copyright (C) The Internet Society (date). This version De Cnodder, et al. Expires December 8, 2004 [Page 9] Internet-Draft Dynamic Authorization Client MIB June 2004 of this MIB module is part of RFC yyyy; see the RFC itself for full legal notices." -- RFC Ed.: replace yyyy with actual RFC number & remove this note REVISION "200404260000Z" -- 26 April 2004 DESCRIPTION "Initial version as published in RFC XXXX" ::= { radiusDynamicAuthorization 2 } radiusMIB OBJECT-IDENTITY STATUS current DESCRIPTION "The OID assigned to RADIUS MIB work by the IANA." ::= { mib-2 67 } -- Ed. Note: The next available OID 3 is picked for -- radiusDynamicAuthorization. radiusDynamicAuthorization OBJECT IDENTIFIER ::= { radiusMIB 3 } radiusDynAuthClientMIBObjects OBJECT IDENTIFIER ::= { radiusDynAuthClientMIB 1 } radiusDynAuthClient OBJECT IDENTIFIER ::= { radiusDynAuthClientMIBObjects 1 } radiusDynAuthClientInvalidServerAddresses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Dynamic Authorization messages (both Disconnect and CoA) received from unknown addresses." ::= { radiusDynAuthClient 1 } radiusDynAuthClientIdentifier OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The implementation identification string for the RADIUS dynamic authorization client software in use on the system." ::= { radiusDynAuthClient 2 } radiusDynAuthServerTable OBJECT-TYPE SYNTAX SEQUENCE OF RadiusDynAuthServerEntry MAX-ACCESS not-accessible De Cnodder, et al. Expires December 8, 2004 [Page 10] Internet-Draft Dynamic Authorization Client MIB June 2004 STATUS current DESCRIPTION "The (conceptual) table listing the RADIUS Dynamic Authorization servers with which the client shares a secret." ::= { radiusDynAuthClient 3 } radiusDynAuthServerEntry OBJECT-TYPE SYNTAX RadiusDynAuthServerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing the Dynamic Authorization Server with which the server shares a secret." INDEX { radiusDynAuthServerIndex } ::= { radiusDynAuthServerTable 1 } RadiusDynAuthServerEntry ::= SEQUENCE { radiusDynAuthServerIndex Integer32, radiusDynAuthServerAddressType InetAddressType, radiusDynAuthServerAddress InetAddress, radiusDynAuthServerClientPortNumber Integer32, radiusDynAuthServerID SnmpAdminString, radiusDynAuthClientRoundTripTime TimeTicks, radiusDynAuthClientDisconRequests Counter32, radiusDynAuthClientDisconRetransmissions Counter32, radiusDynAuthClientDisconAcks Counter32, radiusDynAuthClientDisconNaks Counter32, radiusDynAuthClientMalformedDisconResponses Counter32, radiusDynAuthClientDisconBadAuthenticators Counter32, radiusDynAuthClientDisconPendingRequests Gauge32, radiusDynAuthClientDisconTimeouts Counter32, radiusDynAuthClientDisconPacketsDropped Counter32, radiusDynAuthClientCoARequests Counter32, radiusDynAuthClientCoARetransmissions Counter32, radiusDynAuthClientCoAAcks Counter32, radiusDynAuthClientCoANaks Counter32, radiusDynAuthClientMalformedCoAResponses Counter32, radiusDynAuthClientCoABadAuthenticators Counter32, radiusDynAuthClientCoAPendingRequests Gauge32, radiusDynAuthClientCoATimeouts Counter32, radiusDynAuthClientCoAPacketsDropped Counter32, radiusDynAuthClientUnknownTypes Counter32 -- Ed. Note : Do we need counters for error causes defined in -- RFC-3576. Error-cause should be logged in the log file. It is De Cnodder, et al. Expires December 8, 2004 [Page 11] Internet-Draft Dynamic Authorization Client MIB June 2004 -- not clear if the individual counters for each error cause per -- server make sense. */ } radiusDynAuthServerIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number uniquely identifying each RADIUS Dynamic Authorization server with which this Dynamic Authorization client communicates." ::= { radiusDynAuthServerEntry 1 } radiusDynAuthServerAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-only STATUS current DESCRIPTION "The type of IP-Address of the RADIUS Dynamic Authorization server referred to in this table entry." ::= { radiusDynAuthServerEntry 2 } radiusDynAuthServerAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP-Address value of the RADIUS Dynamic Authorization server referred to in this table entry." ::= { radiusDynAuthServerEntry 3 } radiusDynAuthServerClientPortNumber OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The UDP port the RADIUS Dynamic Authorization client is using to send requests to this server." ::= { radiusDynAuthServerEntry 4 } radiusDynAuthServerID OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current De Cnodder, et al. Expires December 8, 2004 [Page 12] Internet-Draft Dynamic Authorization Client MIB June 2004 DESCRIPTION "The NAS-Identifier of the RADIUS Dynamic Authorization server referred to in this table entry." ::= { radiusDynAuthServerEntry 5 } radiusDynAuthClientRoundTripTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The time interval (in hundredths of a second) between the most recent Disconnect-reply/CoA-reply and the Disconnect or CoA request that matched it from this RADIUS Dynamic Authorization server." ::= { radiusDynAuthServerEntry 6 } radiusDynAuthClientDisconRequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Disconnect-Requests sent to this Dynamic Authorization server." ::= { radiusDynAuthServerEntry 7 } radiusDynAuthClientDisconRetransmissions OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Disconnect-request packets retransmitted to this RADIUS Dynamic authorization server." ::= { radiusDynAuthServerEntry 8 } radiusDynAuthClientDisconAcks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Disconnect-ACK packets received from this Dynamic Authorization server" ::= { radiusDynAuthServerEntry 9 } radiusDynAuthClientDisconNaks OBJECT-TYPE SYNTAX Counter32 De Cnodder, et al. Expires December 8, 2004 [Page 13] Internet-Draft Dynamic Authorization Client MIB June 2004 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Disconnect-NAK packets received from this Dynamic Authorization server." ::= { radiusDynAuthServerEntry 10 } radiusDynAuthClientMalformedDisconResponses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of malformed RADIUS Disconnect-Response packets received from this Dynamic Authorization server. Bad authenticators and unknown types are not included as malformed Disconnect-Responses." ::= { radiusDynAuthServerEntry 11 } radiusDynAuthClientDisconBadAuthenticators OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Disconnect-Response packets which contained invalid Signature attributes received from this Dynamic Authorization server." ::= { radiusDynAuthServerEntry 12 } radiusDynAuthClientDisconPendingRequests OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Disconnect-request packets destined for this server that have not yet timed out or received a response. This variable is incremented when an Disconnect-Request is sent and decremented due to receipt of an Disconnect-Ack, Disconnect-NAK or a timeout or a retransmission." ::= { radiusDynAuthServerEntry 13 } radiusDynAuthClientDisconTimeouts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Disconnect request timeouts to this server. After a timeout the client may retry to the De Cnodder, et al. Expires December 8, 2004 [Page 14] Internet-Draft Dynamic Authorization Client MIB June 2004 same server or give up. A retry to the same server is counted as a retransmit as well as a timeout. A send to a different server is counted as a Disconnect-Request as well as a timeout." ::= { radiusDynAuthServerEntry 14 } radiusDynAuthClientDisconPacketsDropped OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of incoming Disconnect-Responses from this Dynamic Authorization server silently discarded for some reason other than malformed, bad authenticators or unknown types." ::= { radiusDynAuthServerEntry 15 } radiusDynAuthClientCoARequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS CoA-Requests sent to this Dynamic Authorization server." ::= { radiusDynAuthServerEntry 16 } radiusDynAuthClientCoARetransmissions OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS CoA-request packets retransmitted to this RADIUS Dynamic authorization server." ::= { radiusDynAuthServerEntry 17 } radiusDynAuthClientCoAAcks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS CoA-ACK packets received from this Dynamic Authorization server" ::= { radiusDynAuthServerEntry 18 } radiusDynAuthClientCoANaks OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only De Cnodder, et al. Expires December 8, 2004 [Page 15] Internet-Draft Dynamic Authorization Client MIB June 2004 STATUS current DESCRIPTION "The number of RADIUS CoA-NAK packets received from this Dynamic Authorization server." ::= { radiusDynAuthServerEntry 19 } radiusDynAuthClientMalformedCoAResponses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of malformed RADIUS CoA-Response packets received from this Dynamic Authorization server. Bad authenticators and unknown types are not included as malformed CoA-Responses." ::= { radiusDynAuthServerEntry 20 } radiusDynAuthClientCoABadAuthenticators OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS CoA-Response packets which contained invalid Signature attributes received from this Dynamic Authorization server." ::= { radiusDynAuthServerEntry 21 } radiusDynAuthClientCoAPendingRequests OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS CoA-request packets destined for this server that have not yet timed out or received a response. This variable is incremented when an CoA-Request is sent and decremented due to receipt of a CoA-Ack, CoA -NAK or a timeout or a retransmission." ::= { radiusDynAuthServerEntry 22 } radiusDynAuthClientCoATimeouts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of CoA request timeouts to this server. After a timeout the client may retry to the same server or give up. A retry to the same server is counted as a retransmit as well as a timeout. A send to De Cnodder, et al. Expires December 8, 2004 [Page 16] Internet-Draft Dynamic Authorization Client MIB June 2004 a different server is counted as a CoA-Request as well as a timeout." ::= { radiusDynAuthServerEntry 23 } radiusDynAuthClientCoAPacketsDropped OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of incoming CoA-Responses from this Dynamic Authorization server silently discarded for some reason other than malformed, bad authenticators or unknown types." ::= { radiusDynAuthServerEntry 24 } radiusDynAuthClientUnknownTypes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of incoming packets of unknown types which were received on the Dynamic Authorization port." ::= { radiusDynAuthServerEntry 25} -- conformance information radiusDynAuthClientMIBConformance OBJECT IDENTIFIER ::= { radiusDynAuthClientMIB 2 } radiusDynAuthClientMIBCompliances OBJECT IDENTIFIER ::= { radiusDynAuthClientMIBConformance 1 } radiusDynAuthClientMIBGroups OBJECT IDENTIFIER ::= { radiusDynAuthClientMIBConformance 2 } -- compliance statements radiusDynAuthClientMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities implementing the RADIUS Dynamic Authorization Client." MODULE -- this module MANDATORY-GROUPS { radiusDynAuthClientMIBGroup } ::= { radiusDynAuthClientMIBCompliances 1 } -- units of conformance radiusDynAuthClientMIBGroup OBJECT-GROUP OBJECTS { radiusDynAuthClientInvalidServerAddresses, De Cnodder, et al. Expires December 8, 2004 [Page 17] Internet-Draft Dynamic Authorization Client MIB June 2004 radiusDynAuthClientIdentifier, radiusDynAuthServerAddressType, radiusDynAuthServerAddress, radiusDynAuthServerClientPortNumber, radiusDynAuthServerID, radiusDynAuthClientRoundTripTime, radiusDynAuthClientDisconRequests, radiusDynAuthClientDisconRetransmissions, radiusDynAuthClientDisconAcks, radiusDynAuthClientDisconNaks, radiusDynAuthClientMalformedDisconResponses, radiusDynAuthClientDisconBadAuthenticators, radiusDynAuthClientDisconPendingRequests, radiusDynAuthClientDisconTimeouts, radiusDynAuthClientDisconPacketsDropped, radiusDynAuthClientCoARequests, radiusDynAuthClientCoARetransmissions, radiusDynAuthClientCoAAcks, radiusDynAuthClientCoANaks, radiusDynAuthClientMalformedCoAResponses, radiusDynAuthClientCoABadAuthenticators, radiusDynAuthClientCoAPendingRequests, radiusDynAuthClientCoATimeouts, radiusDynAuthClientCoAPacketsDropped, radiusDynAuthClientUnknownTypes } STATUS current DESCRIPTION "The collection of objects providing management of a RADIUS Dynamic Authorization Client." ::= { radiusDynAuthClientMIBGroups 1 } END De Cnodder, et al. Expires December 8, 2004 [Page 18] Internet-Draft Dynamic Authorization Client MIB June 2004 7. Security Considerations There are no management objects defined in this MIB module that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB module is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB module via direct SNMP SET operations Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: radiusDynAuthServerAddress and radiusDynAuthServerAddressType This can be used to determine the address of the DAS with which the DAC is communicating. This information could be useful in mounting an attack on the DAS. radiusDynAuthServerID This can be used to determine the Identifier of the DAS. This information could be useful in impersonating the DAS. radiusDynAuthServerClientPortNumber This can be used to determine the port number on which the DAC is sending. This information could be useful in mounting an attack on the DAS. The other readable objects are not really considered as being sensitive or vulnerable. These objects are: De Cnodder, et al. Expires December 8, 2004 [Page 19] Internet-Draft Dynamic Authorization Client MIB June 2004 radiusDynAuthClientInvalidServerAddresses, radiusDynAuthClientIdentifier, radiusDynAuthClientRoundTripTime, radiusDynAuthClientDisconRequests, radiusDynAuthClientDisconRetransmissions, radiusDynAuthClientDisconAcks, radiusDynAuthClientDisconNaks, radiusDynAuthClientMalformedDisconResponses, radiusDynAuthClientDisconBadAuthenticators, radiusDynAuthClientDisconPendingRequests, radiusDynAuthClientDisconTimeouts, radiusDynAuthClientDisconPacketsDropped, radiusDynAuthClientCoARequests, radiusDynAuthClientCoARetransmissions, radiusDynAuthClientCoAAcks, radiusDynAuthClientCoANaks, radiusDynAuthClientMalformedCoAResponses, radiusDynAuthClientCoABadAuthenticators, radiusDynAuthClientCoAPendingRequests, radiusDynAuthClientCoATimeouts, radiusDynAuthClientCoAPacketsDropped, and radiusDynAuthClientUnknownTypes. SNMP versions prior to SNMPv3 did not include adequate security. 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 module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy). Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module 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. De Cnodder, et al. Expires December 8, 2004 [Page 20] Internet-Draft Dynamic Authorization Client MIB June 2004 8. Acknowledgements This document reuses some of the work done in earlier RADIUS MIB specifications [RFC2619] and [RFC2621]. The authors would also like to acknowledge the following people for their contributions to this document: Anjaneyulu Pata. De Cnodder, et al. Expires December 8, 2004 [Page 21] Internet-Draft Dynamic Authorization Client MIB June 2004 9. References 9.1 Normative References [DYNSERV] De Cnodder, S., Jonnala, N. and M. Chiba, "RADIUS Dynamic Auhtorization Server MIB", draft-decnodder-radext-dynauth-server-mib-01.txt, work in progress, June 2004. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. [RFC2578] 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 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2618] Aboba, B. and G. Zorn, "RADIUS Authentication Client MIB", RFC 2618, June 1999. [RFC2619] Zorn, G. and B. Aboba, "RADIUS Authentication Server MIB", RFC 2619, June 1999. [RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB", RFC 2620, June 1999. [RFC2621] Zorn, G. and B. Aboba, "RADIUS Accounting Server MIB", RFC 2621, June 1999. [RFC3576] Chiba, M., Dommety, G., Eklund, M., Mitton, D. and B. Aboba, "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)", RFC 3576, July 2003. 9.2 Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet Standard Management Framework", RFC 3410, December 2002. De Cnodder, et al. Expires December 8, 2004 [Page 22] Internet-Draft Dynamic Authorization Client MIB June 2004 Authors' Addresses Stefaan De Cnodder Alcatel Francis Wellesplein 1 B-2018 Antwerp Belgium Phone: +32 3 240 85 15 EMail: stefaan.de_cnodder@alcatel.be Nagi Reddy Jonnala Future Soft 480 - 481, Anna Salai Nandanam, Chennai India EMail: nagi_reddy.jonnala@alcatel.be Murtaza Chiba Cisco Systems, Inc. 170 West Tasman Dr. San Jose CA, 95134 Phone: +1 408 525 7198 EMail: mchiba@cisco.com De Cnodder, et al. Expires December 8, 2004 [Page 23] Internet-Draft Dynamic Authorization Client MIB June 2004 Intellectual Property Statement 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. Full Copyright Statement Copyright (C) The Internet Society (2004). 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 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 assignees. 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 De Cnodder, et al. Expires December 8, 2004 [Page 24] Internet-Draft Dynamic Authorization Client MIB June 2004 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. De Cnodder, et al. Expires December 8, 2004 [Page 25]