draft-ietf-radius-auth-servmib-01.txt   draft-ietf-radius-auth-servmib-02.txt 
RADIUS Working Group Glen Zorn RADIUS Working Group Glen Zorn
INTERNET-DRAFT Microsoft INTERNET-DRAFT Microsoft
Category: Standards Track Bernard Aboba Category: Standards Track Bernard Aboba
<draft-ietf-radius-auth-servmib-01.txt> Microsoft <draft-ietf-radius-auth-servmib-02.txt> Microsoft
12 February 1998 11 November 1998
RADIUS Authentication Server MIB RADIUS Authentication Server 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-servmib-01.txt>, and expires August 1, 1998. Please ietf-radius-auth-servmib-02.txt>, and expires May 1, 1999. 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 server functions. These extensions represent a portion of the tication server 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 servers. management stations can manage RADIUS authentication servers.
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 servers. authentication servers.
RADIUS authentication servers are today widely deployed by dialup RADIUS authentication servers are today widely deployed by dialup
Internet Service Providers, in order to provide authentication ser- Internet Service Providers, in order to provide authentication ser-
vices. As a result, the effective management of RADIUS authentication vices. As a result, the effective management of RADIUS authentication
servers is of considerable importance. servers 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 defined the Management Information Base or MIB. Objects in the MIB are
using the subset of Abstract Syntax Notation One (ASN.1) defined in defined using the mechanisms defined in the SMI.
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 spe-
cific 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 five scalars as well as a single table: This MIB module contains fourteen scalars as well as a single table:
(1) the RADIUS Authentication Client Table contains one row for each (1) the RADIUS Authentication Client Table contains one row for each
RADIUS authentication client that the server shares a secret with. RADIUS authentication client that the server shares a secret with.
Each entry in the RADIUS Authentication Client Table includes twelve Each entry in the RADIUS Authentication Client Table includes twelve
entries presenting a view of the activity of the RADIUS authentication columns presenting a view of the activity of the RADIUS authentication
server. server.
6. Definitions 7. Definitions
RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
OBJECT-IDENTITY, experimental, OBJECT-IDENTITY, experimental,
Counter32, Gauge32, Integer32, Counter32, Gauge32, Integer32,
IpAddress FROM SNMPv2-SMI IpAddress FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DisplayString FROM SNMPv2-TC TEXTUAL-CONVENTION, 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}
radiusAuthServMIB MODULE-IDENTITY radiusAuthServMIB MODULE-IDENTITY
LAST-UPDATED "9802121659Z" LAST-UPDATED "9811161659Z"
ORGANIZATION "IETF RADIUS Working Group." ORGANIZATION "IETF RADIUS Working Group."
CONTACT-INFO CONTACT-INFO
" Glen Zorn " Glen Zorn
Microsoft Microsoft
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
US US
Phone: +1 425 703 1559 Phone: +1 425 703 1559
EMail: glennz@microsoft.com" EMail: glennz@microsoft.com"
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the server "The MIB module for entities impleenting the server
side of the Remote Access Dialin User Service (RADIUS) side of the Remote Access Dialin User Service (RADIUS)
authentication protocol." authentication protocol."
::= { radiusAuthentication 1 } ::= { radiusAuthentication 1 }
radius OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { experimental 79 }
radiusAuthentication OBJECT IDENTIFIER ::= {radius 1}
radiusAuthServMIBObjects OBJECT IDENTIFIER ::= { radiusAuthServMIB 1 } radiusAuthServMIBObjects OBJECT IDENTIFIER ::= { radiusAuthServMIB 1 }
radiusAuthServ OBJECT IDENTIFIER ::= { radiusAuthServMIBObjects 1 } radiusAuthServ OBJECT IDENTIFIER ::= { radiusAuthServMIBObjects 1 }
-- Textual conventions -- Textual conventions
RadiusTime ::= TEXTUAL-CONVENTION RadiusTime ::= TEXTUAL-CONVENTION
DISPLAY-HINT "4d" DISPLAY-HINT "4d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"RadiusTime values are 32-bit unsigned integers which "RadiusTime values are 32-bit unsigned integers which
measure time in seconds." measure time in seconds."
SYNTAX Gauge32 SYNTAX Gauge32
skipping to change at page 5, line 21 skipping to change at page 5, line 41
running(4) - server currently running." running(4) - server currently running."
::= {radiusAuthServ 4} ::= {radiusAuthServ 4}
-- New Stats proposed by Dale E. Reed Jr (daler@iea-software.com) -- New Stats proposed by Dale E. Reed Jr (daler@iea-software.com)
radiusAuthServTotalAccessRequests OBJECT-TYPE radiusAuthServTotalAccessRequests 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 "The total number of packets received on the
received since server start-up." authentication port since server start-up."
::= { radiusAuthServ 5} ::= { radiusAuthServ 5}
radiusAuthServTotalInvalidRequests OBJECT-TYPE radiusAuthServTotalInvalidRequests 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 "The total number of RADIUS Access-Request packets
received from unknown addresses since server start-up." received from unknown addresses since server start-up."
::= { radiusAuthServ 6 } ::= { radiusAuthServ 6 }
skipping to change at page 6, line 23 skipping to change at page 6, line 43
sent since server start-up." sent since server start-up."
::= { radiusAuthServ 10 } ::= { radiusAuthServ 10 }
radiusAuthServTotalMalformedAccessRequests OBJECT-TYPE radiusAuthServTotalMalformedAccessRequests 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-Request "The total number of malformed RADIUS Access-Request
packets received since server start-up. Bad authenticators packets received since server start-up. Bad authenticators
are not included as malformed Access-Requests." and unknown types are not included as
malformed Access-Requests."
::= { radiusAuthServ 11 } ::= { radiusAuthServ 11 }
radiusAuthServTotalBadAuthenticators OBJECT-TYPE radiusAuthServTotalBadAuthenticators 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 Authentication-Request packets "The total number of RADIUS Authentication-Request packets
which contained invalid Signature attributes received which contained invalid Signature attributes received
since server start-up." since server start-up."
::= { radiusAuthServ 12 } ::= { radiusAuthServ 12 }
radiusAuthServTotalPacketsDropped OBJECT-TYPE radiusAuthServTotalPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of packets dropped with no reply sent." "The total number of incoming packets
silently discarded for some reason other
than malformed, bad authenticators or
unknown types."
::= { radiusAuthServ 13 } ::= { radiusAuthServ 13 }
radiusAuthServTotalUnknownType OBJECT-TYPE radiusAuthServTotalUnknownTypes 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 since server start-up." were received since server start-up."
::= { radiusAuthServ 14 } ::= { radiusAuthServ 14 }
-- End of new -- End of new
skipping to change at page 7, line 33 skipping to change at page 7, line 57
radiusAuthClientAddress IpAddress, radiusAuthClientAddress IpAddress,
radiusAuthClientID DisplayString, radiusAuthClientID DisplayString,
radiusAuthServAccessRequests Counter32, radiusAuthServAccessRequests Counter32,
radiusAuthServDupAccessRequests Counter32, radiusAuthServDupAccessRequests Counter32,
radiusAuthServAccessAccepts Counter32, radiusAuthServAccessAccepts Counter32,
radiusAuthServAccessRejects Counter32, radiusAuthServAccessRejects Counter32,
radiusAuthServAccessChallenges Counter32, radiusAuthServAccessChallenges Counter32,
radiusAuthServMalformedAccessRequests Counter32, radiusAuthServMalformedAccessRequests Counter32,
radiusAuthServBadAuthenticators Counter32, radiusAuthServBadAuthenticators Counter32,
radiusAuthServPacketsDropped Counter32, radiusAuthServPacketsDropped Counter32,
radiusAuthServUnknownType Counter32 radiusAuthServUnknownTypes Counter32
} }
radiusAuthClientIndex OBJECT-TYPE radiusAuthClientIndex 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 client with which this server authentication client with which this server
communicates." communicates."
skipping to change at page 8, line 12 skipping to change at page 8, line 36
SYNTAX DisplayString SYNTAX DisplayString
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
referred to in this table entry. This is not necessarily referred to in this table entry. This is not necessarily
the same as sysName in MIB II." the same as sysName in MIB II."
::= { radiusAuthClientEntry 3 } ::= { radiusAuthClientEntry 3 }
-- Server Counters -- Server Counters
--
-- Responses = AccessAccepts + AccessRejects + AccessChallenges
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - Responses = Pending
--
-- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped = entries logged
radiusAuthServAccessRequests OBJECT-TYPE radiusAuthServAccessRequests 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 "The total number of packets received on the authentication
received from this client since server start-up." port from this client since server start-up."
::= { radiusAuthClientEntry 4 } ::= { radiusAuthClientEntry 4 }
radiusAuthServDupAccessRequests OBJECT-TYPE radiusAuthServDupAccessRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of duplicate RADIUS Access-Request "The total number of duplicate RADIUS Access-Request
packets received from this client since server start-up." packets received from this client since server start-up."
::= { radiusAuthClientEntry 5 } ::= { radiusAuthClientEntry 5 }
skipping to change at page 9, line 4 skipping to change at page 9, line 35
::= { radiusAuthClientEntry 7 } ::= { radiusAuthClientEntry 7 }
radiusAuthServAccessChallenges OBJECT-TYPE radiusAuthServAccessChallenges 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
sent to this client since server start-up." sent to this client since server start-up."
::= { radiusAuthClientEntry 8 } ::= { radiusAuthClientEntry 8 }
radiusAuthServMalformedAccessRequests OBJECT-TYPE radiusAuthServMalformedAccessRequests 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-Request "The total number of malformed RADIUS Access-Request
packets received from this client since server start-up. packets received from this client since server start-up.
Bad authenticators are not included as Bad authenticators and unknown types are not included as
malformed Access-Requests." malformed Access-Requests."
::= { radiusAuthClientEntry 9 } ::= { radiusAuthClientEntry 9 }
radiusAuthServBadAuthenticators OBJECT-TYPE radiusAuthServBadAuthenticators 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 Authentication-Request packets "The total number of RADIUS Authentication-Request packets
which contained invalid Signature attributes received which contained invalid Signature attributes received
from this client since server start-up." from this client since server start-up."
::= { radiusAuthClientEntry 10 } ::= { radiusAuthClientEntry 10 }
radiusAuthServPacketsDropped OBJECT-TYPE radiusAuthServPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of packets dropped from this client, "The total number of incoming packets from this
with no reply sent." client silently discarded for some reason other
than malformed, bad authenticators or
unknown types."
::= { radiusAuthClientEntry 11 } ::= { radiusAuthClientEntry 11 }
radiusAuthServUnknownType OBJECT-TYPE radiusAuthServUnknownTypes 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 client since authentication server were received from this client since authentication server
start-up." start-up."
::= { radiusAuthClientEntry 12 } ::= { radiusAuthClientEntry 12 }
-- conformance information -- conformance information
skipping to change at page 10, line 29 skipping to change at page 11, line 10
radiusAuthServConfigReset, radiusAuthServConfigReset,
radiusAuthServTotalAccessRequests, radiusAuthServTotalAccessRequests,
radiusAuthServTotalInvalidRequests, radiusAuthServTotalInvalidRequests,
radiusAuthServTotalDupAccessRequests, radiusAuthServTotalDupAccessRequests,
radiusAuthServTotalAccessAccepts, radiusAuthServTotalAccessAccepts,
radiusAuthServTotalAccessRejects, radiusAuthServTotalAccessRejects,
radiusAuthServTotalAccessChallenges, radiusAuthServTotalAccessChallenges,
radiusAuthServTotalMalformedAccessRequests, radiusAuthServTotalMalformedAccessRequests,
radiusAuthServTotalBadAuthenticators, radiusAuthServTotalBadAuthenticators,
radiusAuthServTotalPacketsDropped, radiusAuthServTotalPacketsDropped,
radiusAuthServTotalUnknownType, radiusAuthServTotalUnknownTypes,
radiusAuthClientAddress, radiusAuthClientAddress,
radiusAuthClientID, radiusAuthClientID,
radiusAuthServAccessRequests, radiusAuthServAccessRequests,
radiusAuthServDupAccessRequests, radiusAuthServDupAccessRequests,
radiusAuthServAccessAccepts, radiusAuthServAccessAccepts,
radiusAuthServAccessRejects, radiusAuthServAccessRejects,
radiusAuthServAccessChallenges, radiusAuthServAccessChallenges,
radiusAuthServMalformedAccessRequests, radiusAuthServMalformedAccessRequests,
radiusAuthServBadAuthenticators, radiusAuthServBadAuthenticators,
radiusAuthServPacketsDropped, radiusAuthServPacketsDropped,
radiusAuthServUnknownType radiusAuthServUnknownTypes
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects providing management of "The collection of objects providing management of
a RADIUS Authentication Server." a RADIUS Authentication Server."
::= { radiusAuthServMIBGroups 1 } ::= { radiusAuthServMIBGroups 1 }
END END
7. Security considerations 8. References
All MIB variables described in this document are read-only, with the [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
exception of radiusAuthServConfigReset. 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 a number of management objects defined in this MIB that have
tion to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco a MAX-ACCESS clause of read-write and/or read-create. Such objects
Systems, Dover Beach Consulting, Inc., International Network Services, may be considered sensitive or vulnerable in some network environ-
January, 1996. ments. The support for SET operations in a non-secure environment
without proper protection can have a negative effect on network opera-
tions.
[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 radiusAuthClientAddress
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 client with which the server is communicat-
Beach Consulting, Inc., International Network Services, January, 1996. ing. This information could be useful in impersonating the
client.
[8] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Confor- radiusAuthClientID
mance Statements for version 2 of the the Simple Network Management This can be used to determine the client ID of the authenti-
Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, cation client with which the server is communicating. This
Dover Beach Consulting, Inc., International Network Services, January, information could be useful in impersonating the client.
1996.
[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, nc., Cisco Systems, Dover User-based Security Model RFC 2274 [12] and the View-based Access Con-
Beach Consulting, Inc., International Network Services, January, 1996. trol Model RFC 2275 [15] is recommended. Using these security fea-
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
Glen Zorn Bernard Aboba
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Phone: 425-703-1559 Phone: 425-936-6605
EMail: glennz@microsoft.com EMail: bernarda@microsoft.com
Bernard Aboba Glen Zorn
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Phone: 425-936-6605 Phone: 425-703-1559
EMail: bernarda@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-servermib-02.txt>, and
expires May 1, 1999.
 End of changes. 60 change blocks. 
118 lines changed or deleted 210 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/