draft-ietf-radius-auth-clientmib-04.txt   rfc2618.txt 
RADIUS Working Group Bernard Aboba Network Working Group B. Aboba
INTERNET-DRAFT Microsoft Request for Comments: 2618 G. Zorn
Category: Standards Track Glen Zorn Category: Standards Track Microsoft
<draft-ietf-radius-auth-clientmib-04.txt> Microsoft June 1999
10 February 1999
RADIUS Authentication Client MIB RADIUS Authentication Client MIB
1. Status of this Memo 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
To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.
The distribution of this memo is unlimited. It is filed as <draft-ietf- This document specifies an Internet standards track protocol for the
radius-auth-clientmib-04.txt>, and expires August 1, 1999. Please send Internet community, and requests discussion and suggestions for
comments to the authors. improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
2. Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
3. Abstract Abstract
This memo defines a set of extensions which instrument RADIUS This memo defines a set of extensions which instrument RADIUS
authentication client functions. These extensions represent a portion of authentication client functions. These extensions represent a portion
the Management Information Base (MIB) for use with network management of the Management Information Base (MIB) for use with network
protocols in the Internet community. Using these extensions IP-based management protocols in the Internet community. Using these
management stations can manage RADIUS authentication clients. extensions IP-based management stations can manage RADIUS
authentication clients.
4. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community. In for use with network management protocols in the Internet community.
particular, it describes managed objects used for managing RADIUS In particular, it describes managed objects used for managing RADIUS
authentication clients. authentication clients.
Today a wide range of network devices, including routers and NASes, act Today a wide range of network devices, including routers and NASes,
as RADIUS authentication clients in order to provide authentication and act as RADIUS authentication clients in order to provide
authorization services. As a result, the effective management of RADIUS authentication and authorization services. As a result, the effective
authentication clients is of considerable importance. management of RADIUS authentication clients is of considerable
importance.
5. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC The second version, called SMIv2, is described in STD 58, RFC
1904 [7]. 2578 [5], RFC 2579 [6] and RFC 2580 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the
protocol, which is not an Internet standards track protocol, is SNMP message protocol, which is not an Internet standards
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. track protocol, is called SNMPv2c and described in RFC 1901
The third version of the message protocol is called SNMPv3 and [9] and RFC 1906 [10]. The third version of the message
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 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 o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [8]. A second set of protocol
and associated PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2273 [14] and o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2275 the view-based access control mechanism described in RFC 2575
[15]. [15].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined the Management Information Base or MIB. Objects in the MIB are
using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A
conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
6. Overview 3. Overview
The RADIUS authentication protocol, described in [16], distinguishes The RADIUS authentication protocol, described in [16], distinguishes
between the client function and the server function. In RADIUS between the client function and the server function. In RADIUS
authentication, clients send Access-Requests, and servers reply with authentication, clients send Access-Requests, and servers reply with
Access-Accepts, Access-Rejects, and Access-Challenges. Typically NAS Access-Accepts, Access-Rejects, and Access-Challenges. Typically NAS
devices implement the client function, and thus would be expected to devices implement the client function, and thus would be expected to
implement the RADIUS authentication client MIB, while RADIUS implement the RADIUS authentication client MIB, while RADIUS
authentication servers implement the server function, and thus would be authentication servers implement the server function, and thus would
expected to implement the RADIUS authentication server MIB. be expected to implement the RADIUS authentication server MIB.
However, it is possible for a RADIUS authentication entity to perform However, it is possible for a RADIUS authentication entity to perform
both client and server functions. For example, a RADIUS proxy may act as both client and server functions. For example, a RADIUS proxy may act
a server to one or more RADIUS authentication clients, while as a server to one or more RADIUS authentication clients, while
simultaneously acting as an authentication client to one or more simultaneously acting as an authentication client to one or more
authentication servers. In such situations, it is expected that RADIUS authentication servers. In such situations, it is expected that
entities combining client and server functionality will support both the RADIUS entities combining client and server functionality will
client and server MIBs. support both the client and server MIBs.
6.1. Selected objects 3.1. Selected objects
This MIB module contains two scalars as well as a single table:
(1) the RADIUS Authentication Server Table contains one row for each This MIB module contains two scalars as well as a single table:
RADIUS authentication server that the client shares a secret with.
Each entry in the RADIUS Authentication Server Table includes fifteen (1) the RADIUS Authentication Server Table contains one row for
columns presenting a view of the activity of the RADIUS authentication each RADIUS authentication server that the client shares a
client. secret with.
7. Definitions Each entry in the RADIUS Authentication Server Table includes fifteen
columns presenting a view of the activity of the RADIUS
authentication client.
4. Definitions
RADIUS-AUTH-CLIENT-MIB DEFINITIONS ::= BEGIN RADIUS-AUTH-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32, Gauge32, Counter32, Integer32, Gauge32,
IpAddress, TimeTicks FROM SNMPv2-SMI IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
mib-2 FROM RFC1213-MIB;
radiusAuthClientMIB MODULE-IDENTITY radiusAuthClientMIB MODULE-IDENTITY
LAST-UPDATED "9901290000Z" LAST-UPDATED "9906110000Z" -- 11 Jun 1999
ORGANIZATION "IETF RADIUS Working Group." ORGANIZATION "IETF RADIUS Working Group."
CONTACT-INFO CONTACT-INFO
" Bernard Aboba " Bernard Aboba
Microsoft Microsoft
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
US US
Phone: +1 425 936 6605 Phone: +1 425 936 6605
EMail: bernarda@microsoft.com" EMail: bernarda@microsoft.com"
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the client side of "The MIB module for entities implementing the client
the Remote Access Dialin User Service (RADIUS) authentication side of the Remote Access Dialin User Service (RADIUS)
protocol." authentication protocol."
REVISION "9901290000Z" -- 29 Jan 1999 REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC xxxx" DESCRIPTION "Initial version as published in RFC 2618"
-- RCC xxxx to be assigned by IANA
::= { radiusAuthentication 2 } ::= { radiusAuthentication 2 }
radiusMIB OBJECT-IDENTITY radiusMIB OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA." "The OID assigned to RADIUS MIB work by the IANA."
::= { mib-2 xxx } -- To be assigned by IANA ::= { mib-2 67 }
radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1} radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1}
radiusAuthClientMIBObjects OBJECT IDENTIFIER ::= { radiusAuthClientMIB 1 } radiusAuthClientMIBObjects OBJECT IDENTIFIER ::=
{ radiusAuthClientMIB 1 }
radiusAuthClient OBJECT IDENTIFIER ::= { radiusAuthClientMIBObjects 1 } radiusAuthClient OBJECT IDENTIFIER ::= { radiusAuthClientMIBObjects 1 }
radiusAuthClientInvalidServerAddresses OBJECT-TYPE radiusAuthClientInvalidServerAddresses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Access-Response packets "The number of RADIUS Access-Response packets
received from unknown addresses." received from unknown addresses."
::= { radiusAuthClient 1 } ::= { radiusAuthClient 1 }
radiusAuthClientIdentifier OBJECT-TYPE radiusAuthClientIdentifier OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NAS-Identifier of the RADIUS authentication client. "The NAS-Identifier of the RADIUS authentication client.
This is not necessarily the same as sysName in MIB II." This is not necessarily the same as sysName in MIB II."
::= { radiusAuthClient 2 } ::= { radiusAuthClient 2 }
radiusAuthServerTable OBJECT-TYPE radiusAuthServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAuthServerEntry SYNTAX SEQUENCE OF RadiusAuthServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS authentication "The (conceptual) table listing the RADIUS authentication
servers with which the client shares a secret." servers with which the client shares a secret."
::= { radiusAuthClient 3 } ::= { radiusAuthClient 3 }
radiusAuthServerEntry OBJECT-TYPE radiusAuthServerEntry OBJECT-TYPE
SYNTAX RadiusAuthServerEntry SYNTAX RadiusAuthServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) representing a RADIUS "An entry (conceptual row) representing a RADIUS
authentication server with which the client shares a secret." authentication server with which the client shares
a secret."
INDEX { radiusAuthServerIndex } INDEX { radiusAuthServerIndex }
::= { radiusAuthServerTable 1 } ::= { radiusAuthServerTable 1 }
RadiusAuthServerEntry ::= SEQUENCE { RadiusAuthServerEntry ::= SEQUENCE {
radiusAuthServerIndex Integer32, radiusAuthServerIndex Integer32,
radiusAuthServerAddress IpAddress, radiusAuthServerAddress IpAddress,
radiusAuthClientServerPortNumber Integer32, radiusAuthClientServerPortNumber Integer32,
radiusAuthClientRoundTripTime TimeTicks, radiusAuthClientRoundTripTime TimeTicks,
radiusAuthClientAccessRequests Counter32, radiusAuthClientAccessRequests Counter32,
radiusAuthClientAccessRetransmissions Counter32, radiusAuthClientAccessRetransmissions Counter32,
skipping to change at page 5, line 52 skipping to change at page 5, line 40
radiusAuthClientAccessChallenges Counter32, radiusAuthClientAccessChallenges Counter32,
radiusAuthClientMalformedAccessResponses Counter32, radiusAuthClientMalformedAccessResponses Counter32,
radiusAuthClientBadAuthenticators Counter32, radiusAuthClientBadAuthenticators Counter32,
radiusAuthClientPendingRequests Gauge32, radiusAuthClientPendingRequests Gauge32,
radiusAuthClientTimeouts Counter32, radiusAuthClientTimeouts Counter32,
radiusAuthClientUnknownTypes Counter32, radiusAuthClientUnknownTypes Counter32,
radiusAuthClientPacketsDropped Counter32 radiusAuthClientPacketsDropped Counter32
} }
radiusAuthServerIndex OBJECT-TYPE radiusAuthServerIndex OBJECT-TYPE
SYNTAX Integer32 (1..MAX) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number uniquely identifying each RADIUS "A number uniquely identifying each RADIUS
Authentication server with which this client Authentication server with which this client
communicates." communicates."
::= { radiusAuthServerEntry 1 } ::= { radiusAuthServerEntry 1 }
radiusAuthServerAddress OBJECT-TYPE radiusAuthServerAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the RADIUS authentication server "The IP address of the RADIUS authentication server
referred to in this table entry." referred to in this table entry."
::= { radiusAuthServerEntry 2 } ::= { radiusAuthServerEntry 2 }
radiusAuthClientServerPortNumber OBJECT-TYPE radiusAuthClientServerPortNumber OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The UDP port the client is using to send requests to "The UDP port the client is using to send requests to
this server." this server."
::= { radiusAuthServerEntry 3 } ::= { radiusAuthServerEntry 3 }
radiusAuthClientRoundTripTime OBJECT-TYPE radiusAuthClientRoundTripTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 6, line 48 skipping to change at page 6, line 37
authentication server." authentication server."
::= { radiusAuthServerEntry 4 } ::= { radiusAuthServerEntry 4 }
-- Request/Response statistics -- Request/Response statistics
-- --
-- TotalIncomingPackets = Accepts + Rejects + Challenges + UnknownTypes -- TotalIncomingPackets = Accepts + Rejects + Challenges + UnknownTypes
-- --
-- TotalIncomingPackets - MalformedResponses - BadAuthenticators - -- TotalIncomingPackets - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received -- UnknownTypes - PacketsDropped = Successfully received
-- --
-- AccessRequests + PendingRequests + ClientTimeouts =
-- Successfully Received
-- --
-- --
radiusAuthClientAccessRequests OBJECT-TYPE radiusAuthClientAccessRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Access-Request packets sent "The number of RADIUS Access-Request packets sent
to this server. This does not include retransmissions." to this server. This does not include retransmissions."
::= { radiusAuthServerEntry 5 } ::= { radiusAuthServerEntry 5 }
radiusAuthClientAccessRetransmissions OBJECT-TYPE radiusAuthClientAccessRetransmissions OBJECT-TYPE
skipping to change at page 8, line 36 skipping to change at page 8, line 26
radiusAuthClientPendingRequests OBJECT-TYPE radiusAuthClientPendingRequests OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Access-Request packets "The number of RADIUS Access-Request packets
destined for this server that have not yet timed out destined for this server that have not yet timed out
or received a response. This variable is incremented or received a response. This variable is incremented
when an Access-Request is sent and decremented due to when an Access-Request is sent and decremented due to
receipt of an Acess-Accept, Access-Reject or Access-Challenge, receipt of an Acess-Accept, Access-Reject or
a timeout or retransmission." Access-Challenge, a timeout or retransmission."
::= { radiusAuthServerEntry 12 } ::= { radiusAuthServerEntry 12 }
radiusAuthClientTimeouts OBJECT-TYPE radiusAuthClientTimeouts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of authentication timeouts to this server. "The number of authentication timeouts to this server.
After a timeout the client may retry to the same After a timeout the client may retry to the same
server, send to a different server, or server, send to a different server, or
skipping to change at page 10, line 27 skipping to change at page 10, line 18
radiusAuthClientPacketsDropped radiusAuthClientPacketsDropped
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The basic collection of objects providing management of "The basic collection of objects providing management of
RADIUS Authentication Clients." RADIUS Authentication Clients."
::= { radiusAuthClientMIBGroups 1 } ::= { radiusAuthClientMIBGroups 1 }
END END
8. References 5. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2571, April 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, Management Information for TCP/IP-based Internets", STD 16, RFC
Performance Systems International, Hughes LAN Systems, May 1990. 1155, May 1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
Performance Systems International, Hughes LAN Systems, March 1991. RFC 1212, March 1991.
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [4] Rose, M., "A Convention for Defining Traps for use with the
RFC 1215, Performance Systems International, March 1991. SNMP", RFC 1215, Performance Systems International, March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
of Management Information for Version 2 of the Simple Network M. and S. Waldbusser, "Structure of Management Information
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Conventions for Version 2 of the Simple Network Management Protocol M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., RFC 2579, April 1999.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Statements for Version 2 of the Simple Network Management Protocol M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 58, RFC 2580, April 1999.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Management Protocol", RFC 1157, SNMP Research, Performance Systems Network Management Protocol", STD 15, RFC 1157, May 1990.
International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, "Introduction to Community-based SNMPv2", RFC 1901, January
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1996.
International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Mappings for Version 2 of the Simple Network Management Protocol "Transport Mappings for Version 2 of the Simple Network
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Management Protocol (SNMPv2)", RFC 1906, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, Protocol (SNMP)", RFC 2572, April 1999.
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [12] Blumenthal, U., and B. Wijnen, "User-based Security Model for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC Version 3 of the Simple Network Management Protocol (SNMPv3)",
2274, IBM T. J. Watson Research, January 1998. RFC 2574, April 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Protocol (SNMPv2)", RFC 1905, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 196.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2573, April 1999.
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., (SNMP)", RFC 2575, April 1999.
Cisco Systems, Inc., January 1998
[16] Rigney, C., Rubens, A., Simpson W., and S. Willens, "Remote [16] Rigney, C., Rubens, A., Simpson W. and S. Willens, "Remote
Authentication Dial In User Service (RADIUS)", RFC 2138, April Authentication Dial In User Service (RADIUS)", RFC 2138, April
1997. 1997.
9. Security considerations 6. Security Considerations
There are no management objects defined in this MIB that have a MAX- 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 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 implemented correctly, then there is no risk that an intruder can
or create any management objects of this MIB via direct SNMP SET alter or create any management objects of this MIB via direct SNMP
operations. SET operations.
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
sensitive information. These are: sensitive information. These are:
radiusAuthServerAddress radiusAuthServerAddress
This can be used to determine the address of the RADIUS This can be used to determine the address of the RADIUS
authentication server with which the client is communicating. authentication server with which the client is
This information could be useful in mounting an attack on the communicating. This information could be useful in
authentication server. mounting an attack on the authentication server.
radiusAuthClientServerPortNumber radiusAuthClientServerPortNumber This can be used to determine the
This can be used to determine the port number on which the port number on which the RADIUS authentication client is
RADIUS authentication client is sending. This information sending. This information could be useful in impersonating
could be useful in impersonating the client in order to send the client in order to send data to the authentication
data to the authentication server. server.
It is thus important to control even GET access to these objects and 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 possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment. for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network itself SNMPv1 by itself is not a secure environment. Even if the network
is secure (for example by using IPSec), there is no control as to who on itself is secure (for example by using IPSec), there is no control as
the secure network is allowed to access and GET/SET to who on the secure network is allowed to access and GET/SET
(read/change/create/delete) the objects in this MIB. (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features It is recommended that the implementers consider the security
as provided by the SNMPv3 framework. Specifically, the use of the User- features as provided by the SNMPv3 framework. Specifically, the use
based Security Model RFC 2274 [12] and the View-based Access Control of the User-based Security Model RFC 2574 [12] and the View-based
Model RFC 2275 [15] is recommended. Using these security features, Access Control Model RFC 2575 [15] is recommended. Using these
customer/users can give access to the objects only to those principals security features, customer/users can give access to the objects only
(users) that have legitimate rights to GET or SET (change/create/delete) to those principals (users) that have legitimate rights to GET or SET
them. (change/create/delete) them.
10. Acknowledgments 7. Acknowledgments
The authors acknowledge the contributions of the RADIUS Working Group in The authors acknowledge the contributions of the RADIUS Working Group
the development of this MIB. Thanks to Narendra Gidwani of Microsoft, in the development of this MIB. Thanks to Narendra Gidwani of
Allan C. Rubens of MERIT, Carl Rigney of Livingston and Peter Heitman of Microsoft, Allan C. Rubens of MERIT, Carl Rigney of Livingston and
American Internet Corporation for useful discussions of this problem Peter Heitman of American Internet Corporation for useful discussions
space. of this problem space.
11. Authors' Addresses 8. Authors' Addresses
Bernard Aboba Bernard Aboba
Microsoft Corporation Microsoft Corporation
One Microsoft Wy One Microsoft Wy
Redmond, WA 98052 Redmond, WA 98052
Phone: 425-936-6605 Phone: 425-936-6605
EMail: bernarda@microsoft.com EMail: bernarda@microsoft.com
Glen Zorn Glen Zorn
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Phone: 425-703-1559 Phone: 425-703-1559
EMail: glennz@microsoft.com EMail: glennz@microsoft.com
12. Intellectural Property Statement 9. Intellectural Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to
to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; neither does it represent that it has made any might or might not be available; neither does it represent that it
effort to identify any such rights. Information on the IETF's has made any effort to identify any such rights. Information on the
procedures with respect to rights in standards-track and standards- IETF's procedures with respect to rights in standards-track and
related documentation can be found in BCP-11. Copies of claims of standards-related documentation can be found in BCP-11. Copies of
rights made available for publication and any assurances of licenses to claims of rights made available for publication and any assurances of
be made available, or the result of an attempt made to obtain a general licenses to be made available, or the result of an attempt made to
license or permission for the use of such proprietary rights by obtain a general license or permission for the use of such
implementors or users of this specification can be obtained from the proprietary rights by implementors or users of this specification can
IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary
which may cover technology that may be required to practice this rights which may cover technology that may be required to practice
standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
13. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). 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. 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.
14. Expiration Date 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.
This memo is filed as <draft-ietf-radius-auth-clientmib-04.txt>, and The limited permissions granted above are perpetual and will not be
expires August 1, 1999. 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 78 change blocks. 
268 lines changed or deleted 236 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/