draft-ietf-radius-auth-clientmib-01.txt   draft-ietf-radius-auth-clientmib-02.txt 
RADIUS Working Group Bernard Aboba RADIUS Working Group Bernard Aboba
INTERNET-DRAFT Microsoft INTERNET-DRAFT Microsoft
Category: Standards Track Glen Zorn Category: Standards Track Glen Zorn
<draft-ietf-radius-auth-clientmib-01.txt> Microsoft <draft-ietf-radius-auth-clientmib-02.txt> Microsoft
12 February 1998 11 November 1998
RADIUS Authentication Client MIB RADIUS Authentication Client MIB
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working docu- This document is an Internet-Draft. Internet-Drafts are working docu-
ments of the Internet Engineering Task Force (IETF), its areas, and ments of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute work- its working groups. Note that other groups may also distribute work-
ing documents as Internet-Drafts. ing documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference mate- time. It is inappropriate to use Internet-Drafts as reference mate-
rial or to cite them other than as ``work in progress.'' rial or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net Directories on ftp.ietf.org (US East Coast), nic.nordu.net
(Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
The distribution of this memo is unlimited. It is filed as <draft- The distribution of this memo is unlimited. It is filed as <draft-
ietf-radius-auth-clientmib-01.txt>, and expires August 1, 1998. ietf-radius-auth-clientmib-02.txt>, and expires May 1, 1999. Please
Please send comments to the authors. send comments to the authors.
2. Abstract 2. Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
3. Abstract
This memo defines a set of extensions which instrument RADIUS authen- This memo defines a set of extensions which instrument RADIUS authen-
tication client functions. These extensions represent a portion of the tication client functions. These extensions represent a portion of the
Management Information Base (MIB) for use with network management pro- Management Information Base (MIB) for use with network management pro-
tocols in the Internet community. Using these extensions IP-based tocols in the Internet community. Using these extensions IP-based
management stations can manage RADIUS authentication clients. management stations can manage RADIUS authentication clients.
3. Introduction 4. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In 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, Today a wide range of network devices, including routers and NASes,
act as RADIUS authentication clients in order to provide authentica- act as RADIUS authentication clients in order to provide authentica-
tion and authorization services. As a result, the effective management tion and authorization services. As a result, the effective management
of RADIUS authentication clients is of considerable importance. of RADIUS authentication clients is of considerable importance.
4. The SNMPv2 Network Management Framework 5. The SNMP Management Framework
The SNMPv2 Network Management Framework consists of four major compo-
nents. They are:
o RFC 1902 which defines the SMI, the mechanisms used for The SNMP Management Framework presently consists of five major compo-
describing and naming objects for the purpose of management. nents:
o RFC 1905 which defines the protocol used for network access to o An overall architecture, described in RFC 2271 [1].
managed objects.
o RFC 1907 defines the core set of managed objects for the o Mechanisms for describing and naming objects and events for
Internet suite of protocols. the purpose of management. The first version of this Structure
of Management Information (SMI) is called SMIv1 and described
in RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second
version, called SMIv2, is described in RFC 1902 [5], RFC 1903
[6] and RFC 1904 [7].
o RFC 1909 which defines the administrative aspects of the o Message protocols for transferring management information. The
framework. first version of the SNMP message protocol is called SNMPv1
and described in RFC 1157 [8]. A second version of the 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 2272 [11]
and RFC 2274 [12].
The Framework permits new objects to be defined for the purpose of o Protocol operations for accessing management information. The
experimentation and evaluation. first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations
and associated PDU formats is described in RFC 1905 [13].
4.1. Object Definitions o A set of fundamental applications described in RFC 2273 [14]
and the view-based access control mechanism described in RFC
2275 [15].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the subset of Abstract Syntax Notation One (ASN.1) defined using the mechanisms defined in the SMI.
defined in the SMI. In particular, each object object type is named by
an OBJECT IDENTIFIER, an administratively assigned name. The object
type together with an object instance serves to uniquely identify a
specific instantiation of the object. For human convenience, we often
use a textual string, termed the descriptor, to refer to the object
type.
5. Overview This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate trans-
lations. 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 informa-
tion is not considered to change the semantics of the MIB.
The RADIUS authentication protocol, described in [1], distinguishes 6. Overview
The RADIUS authentication protocol, described in [16], distinguishes
between the client function and the server function. In RADIUS authen- between the client function and the server function. In RADIUS authen-
tication, clients send Access-Requests, and servers reply with Access- tication, clients send Access-Requests, and servers reply with Access-
Accepts, Access-Rejects, and Access-Challenges. Typically NAS devices Accepts, Access-Rejects, and Access-Challenges. Typically NAS devices
implement the client function, and thus would be expected to implement implement the client function, and thus would be expected to implement
the RADIUS authentication client MIB, while RADIUS authentication the RADIUS authentication client MIB, while RADIUS authentication
servers implement the server function, and thus would be expected to servers implement the server function, and thus would be expected to
implement the RADIUS authentication server MIB. 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 both client and server functions. For example, a RADIUS proxy may act
as a server to one or more RADIUS authentication clients, while simul- as a server to one or more RADIUS authentication clients, while simul-
taneously acting as an authentication client to one or more authenti- taneously acting as an authentication client to one or more authenti-
cation servers. In such situations, it is expected that RADIUS enti- cation servers. In such situations, it is expected that RADIUS enti-
ties combining client and server functionality will support both the ties combining client and server functionality will support both the
client and server MIBs. client and server MIBs.
5.1. Selected objects 6.1. Selected objects
This MIB module contains two scalars as well as a single table: This MIB module contains two scalars as well as a single table:
(1) the RADIUS Authentication Server Table contains one row for each (1) the RADIUS Authentication Server Table contains one row for each
RADIUS authentication server that the client shares a secret with. RADIUS authentication server that the client shares a secret with.
Each entry in the RADIUS Authentication Server Table includes thirteen Each entry in the RADIUS Authentication Server Table includes fifteen
entries presenting a view of the activity of the RADIUS authentication columns presenting a view of the activity of the RADIUS authentication
client. client.
6. Definitions 7. Definitions
RADIUS-AUTH-CLIENT-MIB DEFINITIONS ::= BEGIN RADIUS-AUTH-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
OBJECT-IDENTITY, experimental, OBJECT-IDENTITY, experimental,
Counter32, Integer32, Gauge32, Counter32, Integer32, Gauge32,
IpAddress, TimeTicks FROM SNMPv2-SMI IpAddress, TimeTicks FROM SNMPv2-SMI
DisplayString FROM SNMPv2-TC DisplayString FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radius OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { experimental 79 }
radiusAuthentication OBJECT IDENTIFIER ::= {radius 1}
radiusAuthClientMIB MODULE-IDENTITY radiusAuthClientMIB MODULE-IDENTITY
LAST-UPDATED "9802121659Z" LAST-UPDATED "9811161659Z"
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 dule for entities implementing the client side of
the Remote Access Dialin User Service (RADIUS) authentication the Remote Access Dialin User Service (RADIUS) authentication
protocol." protocol."
::= { radiusAuthentication 2 } ::= { radiusAuthentication 2 }
radius OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { experimental 79 }
radiusAuthentication OBJECT IDENTIFIER ::= {radius 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 total number of RADIUS Access-Response packets "The total number of RADIUS Access-Response packets
received from unknown addresses since client start-up." received from unknown addresses since client start-up."
::= { radiusAuthClient 1 } ::= { radiusAuthClient 1 }
radiusAuthClientIdentifier OBJECT-TYPE radiusAuthClientIdentifier OBJECT-TYPE
skipping to change at page 4, line 55 skipping to change at page 5, line 21
radiusAuthClientRoundTripTime TimeTicks, radiusAuthClientRoundTripTime TimeTicks,
radiusAuthClientAccessRequests Counter32, radiusAuthClientAccessRequests Counter32,
radiusAuthClientAccessRetransmissions Counter32, radiusAuthClientAccessRetransmissions Counter32,
radiusAuthClientAccessAccepts Counter32, radiusAuthClientAccessAccepts Counter32,
radiusAuthClientAccessRejects Counter32, radiusAuthClientAccessRejects Counter32,
radiusAuthClientAccessChallenges Counter32, radiusAuthClientAccessChallenges Counter32,
radiusAuthClientMalformedAccessResponses Counter32, radiusAuthClientMalformedAccessResponses Counter32,
radiusAuthClientBadAuthenticators Counter32, radiusAuthClientBadAuthenticators Counter32,
radiusAuthClientPendingRequests Gauge32, radiusAuthClientPendingRequests Gauge32,
radiusAuthClientTimeouts Counter32, radiusAuthClientTimeouts Counter32,
radiusAuthClientUnknownType Counter32 radiusAuthClientUnknownTypes Counter32,
radiusAuthClientPacketsDropped Counter32
} }
radiusAuthServerIndex OBJECT-TYPE radiusAuthServerIndex OBJECT-TYPE
SYNTAX Integer32 (0..MAX) SYNTAX Integer32 (0..MAX)
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 }
skipping to change at page 5, line 43 skipping to change at page 6, line 10
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time interval between the most recent "The time interval between the most recent
Access-Reply/Access-Challenge and the Access-Request that Access-Reply/Access-Challenge and the Access-Request that
matched it from this RADIUS authentication server." matched it from this RADIUS authentication server."
::= { radiusAuthServerEntry 4 } ::= { radiusAuthServerEntry 4 }
-- Request/Response statistics -- Request/Response statistics
-- Ignoring Unknown Types, then --
-- AccessRequests + AccesssRetransmissions = AccessAccepts + -- TotalIncomingPackets = Accepts + Rejects + Challenges + UnknownTypes
-- AccessRejects + AccessChallenges + PendingRequests + Timeouts --
-- TotalIncomingPackets - MalformedResponses - BadAuthenticators -
-- 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 total number of RADIUS Access-Request packets sent "The total number of RADIUS Access-Request packets sent
to this server since client start-up. This does not to this server since client start-up. This does not
include retransmissions." include retransmissions."
::= { radiusAuthServerEntry 5 } ::= { radiusAuthServerEntry 5 }
skipping to change at page 6, line 19 skipping to change at page 6, line 46
retransmitted to this RADIUS authentication server retransmitted to this RADIUS authentication server
since client start-up." since client start-up."
::= { radiusAuthServerEntry 6 } ::= { radiusAuthServerEntry 6 }
radiusAuthClientAccessAccepts OBJECT-TYPE radiusAuthClientAccessAccepts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of RADIUS Access-Accept packets "The total number of RADIUS Access-Accept packets
received from this server since client start-up." (valid or invalid) received from this server
since client start-up."
::= { radiusAuthServerEntry 7 } ::= { radiusAuthServerEntry 7 }
radiusAuthClientAccessRejects OBJECT-TYPE radiusAuthClientAccessRejects OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of RADIUS Access-Reject packets "The total number of RADIUS Access-Reject packets
received from this server since client start-up." (valid or invalid) received from this server
since client start-up."
::= { radiusAuthServerEntry 8 } ::= { radiusAuthServerEntry 8 }
radiusAuthClientAccessChallenges OBJECT-TYPE radiusAuthClientAccessChallenges OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of RADIUS Access-Challenge packets "The total number of RADIUS Access-Challenge packets
received from this server since client start-up." (valid or invalid) received from this server since
client start-up."
::= { radiusAuthServerEntry 9 } ::= { radiusAuthServerEntry 9 }
-- "Access-Response" includes an Access-Accept, Access-Challenge -- "Access-Response" includes an Access-Accept, Access-Challenge
-- or Access-Reject -- or Access-Reject
radiusAuthClientMalformedAccessResponses OBJECT-TYPE radiusAuthClientMalformedAccessResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of malformed RADIUS Access-Response "The total number of malformed RADIUS Access-Response
packets received from this server since client packets received from this server since client
start-up. Malformed packets include packets with start-up. Malformed packets include packets with
an invalid length. Bad authenticators or an invalid length. Bad authenticators or
Signature attributes are not Signature attributes or unknown types are not
included as malformed access responses." included as malformed access responses."
::= { radiusAuthServerEntry 10 } ::= { radiusAuthServerEntry 10 }
radiusAuthClientBadAuthenticators OBJECT-TYPE radiusAuthClientBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of RADIUS Access-Response packets "The total number of RADIUS Access-Response packets
containing invalid authenticators or Signature containing invalid authenticators or Signature
skipping to change at page 7, line 22 skipping to change at page 7, line 52
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 total number of RADIUS Access-Request packets "The total 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 Access-Reply or Access-Challenge, receipt of an Acess-Accept, Access-Reject or Access-Challenge,
a timeout or retransmission." 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 total number of authentication timeouts to this server "The total number of authentication timeouts to this server
since client startup. After a timeout the client may since client startup. After a timeout the client may
retry to the same server, send to a different server, or retry to the same server, send to a different server, or
give up. A retry to the same server is counted as a give up. A retry to the same server is counted as a
retransmit as well as a timeout. A send to a different retransmit as well as a timeout. A send to a different
server is counted as a Request as well as a timeout." server is counted as a Request as well as a timeout."
::= { radiusAuthServerEntry 13 } ::= { radiusAuthServerEntry 13 }
radiusAuthClientUnknownType OBJECT-TYPE radiusAuthClientUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of RADIUS packets of unknown type which "The total number of RADIUS packets of unknown type which
were received from this server on the authentication port were received from this server on the authentication port
since client start-up." since client start-up."
::= { radiusAuthServerEntry 14 } ::= { radiusAuthServerEntry 14 }
radiusAuthClientPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of RADIUS packets of which were
received from this server on the authentication port
and dropped for some other reason since client
start-up."
::= { radiusAuthServerEntry 15 }
-- conformance information -- conformance information
radiusAuthClientMIBConformance radiusAuthClientMIBConformance
OBJECT IDENTIFIER ::= { radiusAuthClientMIB 2 } OBJECT IDENTIFIER ::= { radiusAuthClientMIB 2 }
radiusAuthClientMIBCompliances radiusAuthClientMIBCompliances
OBJECT IDENTIFIER ::= { radiusAuthClientMIBConformance 1 } OBJECT IDENTIFIER ::= { radiusAuthClientMIBConformance 1 }
radiusAuthClientMIBGroups radiusAuthClientMIBGroups
OBJECT IDENTIFIER ::= { radiusAuthClientMIBConformance 2 } OBJECT IDENTIFIER ::= { radiusAuthClientMIBConformance 2 }
-- compliance statements -- compliance statements
radiusAuthClientMIBCompliance MODULE-COMPLIANCE radiusAuthClientMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for authentication clients "The compliance statement for authentication clients
implementing the RADIUS Authentication Client MIB." implementing the RADIUS Authentication Client MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusAuthClientMIBGroup } MANDATORY-GROUPS { radiusAuthClientMIBGroup }
skipping to change at page 8, line 33 skipping to change at page 9, line 21
radiusAuthClientRoundTripTime, radiusAuthClientRoundTripTime,
radiusAuthClientAccessRequests, radiusAuthClientAccessRequests,
radiusAuthClientAccessRetransmissions, radiusAuthClientAccessRetransmissions,
radiusAuthClientAccessAccepts, radiusAuthClientAccessAccepts,
radiusAuthClientAccessRejects, radiusAuthClientAccessRejects,
radiusAuthClientAccessChallenges, radiusAuthClientAccessChallenges,
radiusAuthClientMalformedAccessResponses, radiusAuthClientMalformedAccessResponses,
radiusAuthClientBadAuthenticators, radiusAuthClientBadAuthenticators,
radiusAuthClientPendingRequests, radiusAuthClientPendingRequests,
radiusAuthClientTimeouts, radiusAuthClientTimeouts,
radiusAuthClientUnknownType radiusAuthClientUnknownTypes,
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
7. Security considerations 8. References
All MIB variables described in this document are read-only. [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Sys-
tems, Inc., BMC Software, Inc., IBM T. J. Watson Research, Jan-
uary 1998.
8. Acknowledgments [2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
Carl Rigney of Livingston and Peter Heitman of American Internet Cor- Performance Systems International, Hughes LAN Systems, March
poration for useful discussions of this problem space. 1991.
9. References [4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991.
[1] C. Rigney, A. Rubens, W. Simpson, S. Willens. "Remote Authenti- [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
cation Dial In User Service (RADIUS)." RFC 2138, Livingston, Merit, of Management Information for Version 2 of the Simple Network
Daydreamer, April, 1997. Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc.,
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[2] C. Rigney. "RADIUS Authentication." RFC 2139, Livingston, April, [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Proto-
col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems,
Inc., Dover Beach Consulting, Inc., International Network Ser-
vices, January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor-
mance Statements for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems,
Inc., Dover Beach Consulting, Inc., International Network Ser-
vices, January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Net-
work Management Protocol", RFC 1157, SNMP Research, Performance
Systems International, Performance Systems International, MIT
Laboratory for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc-
tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc.,
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Pro-
cessing and Dispatching for the Simple Network Management Proto-
col (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January
1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Proto-
col (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems,
Inc., Dover Beach Consulting, Inc., International Network Ser-
vices, January 196.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998
[16] Rigney, C., Rubens, A., Simpson W., and S. Willens, "Remote
Authentication Dial In User Service (RADIUS)", RFC 2138, April
1997. 1997.
[3] C. Rigney, W. Willats. "RADIUS Extensions." draft-ietf-radius- [17] "Information processing systems - Open Systems Interconnection -
ext-00.txt, Livingston, January, 1997. Specification of Abstract Syntax Notation One (ASN.1)", Interna-
tional Organization for Standardization, International Standard
8824, December 1987.
[4] "Information processing systems - Open Systems Interconnection - 9. Security considerations
Specification of Abstract Syntax Notation One (ASN.1)", International
Organization for Standardization, International Standard 8824, Decem-
ber 1987.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- There are no management objects defined in this MIB that have a MAX-
tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco ACCESS clause of read-write and/or read-create. So, if this MIB is
Systems, Dover Beach Consulting, Inc., International Network Services, implemented correctly, then there is no risk that an intruder can
January, 1996. alter or create any management objects of this MIB via direct SNMP SET
operations.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure There are a number of managed objects in this MIB that may contain
of Management Information for Version 2 of the Simple Network Manage- sensitive information. These are:
ment Protocol (SNMPv2)", RFC 1902, SNMP Research, Inc., Cisco Systems,
Dover Beach Consulting, Inc., International Network Services, January,
1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual radiusAuthServerAddress
Conventions for version 2 of the the Simple Network Management Proto- This can be used to determine the address of the RADIUS
col (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Dover authentication server with which the client is communicat-
Beach Consulting, Inc., International Network Services, January, 1996. ing. This information could be useful in mounting an attack
on the authentication server.
[8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor- radiusAuthClientServerPortNumber
mance Statements for version 2 of the the Simple Network Management This can be used to determine the port number on which the
Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, RADIUS authentication client is sending. This information
Dover Beach Consulting, Inc., International Network Services, January, could be useful in impersonating the client in order to send
1996. data to the authentication server.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol It is thus important to control even GET access to these objects and
Operations for Version 2 of the Simple Network Management Protocol possibly to even encrypt the values of these object when sending them
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Dover Beach over the network via SNMP. Not all versions of SNMP provide features
Consulting, Inc., International Network Services, January, 1996. for such a secure environment.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport SNMPv1 by itself is not a secure environment. Even if the network
Mappings for Version 2 of the Simple Network Management Protocol itself is secure (for example by using IPSec), there is no control as
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Dover Beach to who on the secure network is allowed to access and GET/SET
Consulting, Inc., International Network Services, January, 1996. (read/change/create/delete) the objects in this MIB.
[11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Manage- It is recommended that the implementers consider the security features
ment Information Base for Version 2 of the Simple Network Management as provided by the SNMPv3 framework. Specifically, the use of the
Protocol (SNMPv2)", RFC 1907, SNMP Research, Inc., Cisco Systems, User-based Security Model RFC 2274 [12] and the View-based Access Con-
Dover Beach Consulting, Inc., International Network Services, January, trol Model RFC 2275 [15] is recommended. Using these security fea-
1996. tures, customer/users can give access to the objects only to those
principals (users) that have legitimate rights to GET or SET
(change/create/delete) them.
[12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexis- 10. Acknowledgments
tence between Version 1 and Version 2 of the Internet-standard Network
Management Framework", RFC 1908, SNMP Research, Inc., Cisco Systems,
Dover Beach Consulting, Inc., International Network Services, January,
1996.
[13] McCloghrie, K., "An Administrative Infrastructure for SNMPv2", Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT,
RFC 1909, Cisco Systems, February, 1996. Carl Rigney of Livingston and Peter Heitman of American Internet Cor-
poration for useful discussions of this problem space.
10. Authors' Addresses 11. Authors' Addresses
Bernard Aboba Bernard Aboba
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
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. Full Copyright Statement
Copyright (C) The Internet Society (1997). 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 docu-
ment itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other Inter-
net 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 permis-
sions 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 WAR-
RANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE."
13. Expiration Date
This memo is filed as <draft-ietf-radius-auth-clientmib-02.txt>, and
expires May 1, 1999.
m o
 End of changes. 56 change blocks. 
112 lines changed or deleted 213 lines changed or added

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