draft-ietf-radext-rfc2619bis-04.txt   rfc4669.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Request for Comments: 4669 Enterasys Networks
Obsoletes: RFC 2619 (if approved) June 26, 2006 Obsoletes: 2619 August 2006
Expires: December 28, 2006 Category: Standards Track
RADIUS Authentication Server MIB for IPv6 RADIUS Authentication Server MIB for IPv6
draft-ietf-radext-rfc2619bis-04.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any Status of This Memo
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 28, 2006. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a set of extensions, which instrument RADIUS This memo defines a set of extensions that instrument RADIUS
authentication server functions. These extensions represent a authentication server functions. These extensions represent a
portion of the Management Information Base (MIB) for use with network portion of the Management Information Base (MIB) for use with network
management protocols in the Internet community. Using these management protocols in the Internet community. Using these
extensions IP-based management stations can manage RADIUS extensions, IP-based management stations can manage RADIUS
authentication servers. authentication servers.
This memo obsoletes RFC 2619 by deprecating the MIB table containing This memo obsoletes RFC 2619 by deprecating the MIB table containing
IPv4-only address formats and defining a new table to add support for IPv4-only address formats and defining a new table to add support for
version neutral IP address formats. The remaining MIB objects from version-neutral IP address formats. The remaining MIB objects from
RFC 2619 are carried forward into this document. This memo also adds RFC 2619 are carried forward into this document. This memo also adds
UNITS and Reference clauses to selected objects. UNITS and REFERENCE clauses to selected objects.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology .....................................................3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework ......................3
4. Scope of Changes . . . . . . . . . . . . . . . . . . . . . . . 3 4. Scope of Changes ................................................3
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module .....................................4
6. Deprecated Objects . . . . . . . . . . . . . . . . . . . . . . 5 6. Deprecated Objects ..............................................5
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Definitions .....................................................5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 8. Security Considerations ........................................21
9. Security Considerations . . . . . . . . . . . . . . . . . . . 22 9. References .....................................................23
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 9.1. Normative References ......................................23
10.1. Normative References . . . . . . . . . . . . . . . . . . 23 9.2. Informative References ....................................23
10.2. Informative References . . . . . . . . . . . . . . . . . 23 Appendix A. Acknowledgements ......................................24
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 24
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 26
1. Terminology 1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
The objects defined within this memo relate to the Remote
Authentication Dial-In User Service (RADIUS) Authentication Server as
defined in RFC 2865 [RFC2865].
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
This document uses terminology from RFC 2865 [RFC2865]. This document uses terminology from RFC 2865 [RFC2865].
This document uses the word "malformed" with respect to RADIUS This document uses the word "malformed" with respect to RADIUS
packets, particularly in the context of counters of "malformed packets, particularly in the context of counters of "malformed
packets". While RFC 2865 does not provide an explicit definition of packets". While RFC 2865 does not provide an explicit definition of
"malformed", malformed generally means that the implementation has "malformed", malformed generally means that the implementation has
determined the packet does not match the format defined in RFC 2865. determined the packet does not match the format defined in RFC 2865.
Some implementations may determine that packets are malformed when Some implementations may determine that packets are malformed when
the Vendor Specific Attribute (VSA) format does not follow the RFC the Vendor Specific Attribute (VSA) format does not follow the RFC
2865 recommendations for VSAs. Those implementations are used in 2865 recommendations for VSAs. Those implementations are used in
deployments today, and thus set the de-facto definition of deployments today, and thus set the de facto definition of
"malformed". "malformed".
2. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
The objects defined within this memo relate to the Remote
Authentication Dial-In User Service (RADIUS) Authentication Server as
defined in RFC 2865 [RFC2865].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
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. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
skipping to change at page 4, line 7 skipping to change at page 4, line 4
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. Scope of Changes 4. Scope of Changes
This document obsoletes RFC 2619 [RFC2619], RADIUS Authentication This document obsoletes RFC 2619 [RFC2619], RADIUS Authentication
Server MIB, by deprecating the radiusAuthClientTable table and adding Server MIB, by deprecating the radiusAuthClientTable table and adding
a new table, radiusAuthClientExtTable, containing a new table, radiusAuthClientExtTable, containing
radiusAuthClientInetAddressType and radiusAuthClientInetAddress. The radiusAuthClientInetAddressType and radiusAuthClientInetAddress. The
purpose of these added MIB objects is to support version neutral IP purpose of these added MIB objects is to support version-neutral IP
addressing formats. The existing table containing addressing formats. The existing table containing
radiusAuthClientAddress is deprecated. The remaining MIB objects radiusAuthClientAddress is deprecated. The remaining MIB objects
from RFC 2619 are carried forward into this document. This memo also from RFC 2619 are carried forward into this document. This memo also
adds UNITS and REFERENCE clauses to selected objects. adds UNITS and REFERENCE clauses to selected objects.
RFC 4001 [RFC4001], which defines the SMI Textual Conventions for RFC 4001 [RFC4001], which defines the SMI Textual Conventions for
version neutral IP addresses, contains the following recommendation. version-neutral IP addresses, contains the following recommendation.
'In particular, when revising a MIB module that contains IPv4 'In particular, when revising a MIB module that contains IPv4
specific tables, it is suggested to define new tables using the specific tables, it is suggested to define new tables using the
textual conventions defined in this memo [RFC4001] that support all textual conventions defined in this memo [RFC4001] that support all
versions of IP. The status of the new tables SHOULD be "current", versions of IP. The status of the new tables SHOULD be "current",
whereas the status of the old IP version specific tables SHOULD be whereas the status of the old IP version specific tables SHOULD be
changed to "deprecated". The other approach, of having multiple changed to "deprecated". The other approach, of having multiple
similar tables for different IP versions, is strongly discouraged.' similar tables for different IP versions, is strongly discouraged.'
5. Structure of the MIB Module 5. Structure of the MIB Module
The RADIUS authentication protocol, described in RFC 2865 [RFC2865], The RADIUS authentication protocol, described in RFC 2865 [RFC2865],
distinguishes between the client function and the server function. distinguishes between the client function and the server function.
In RADIUS authentication, clients send Access-Requests, and servers In RADIUS authentication, clients send Access-Requests, and servers
reply with Access-Accepts, Access-Rejects, and Access-Challenges. reply with Access-Accepts, Access-Rejects, and Access-Challenges.
Typically NAS devices implement the client function, and thus would Typically, NAS devices implement the client function, and thus would
be expected to implement the RADIUS authentication client MIB, while be expected to implement the RADIUS authentication client MIB, while
RADIUS authentication servers implement the server function, and thus RADIUS authentication servers implement the server function, and thus
would be expected to implement the RADIUS authentication server MIB. would 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 both client and server functions. For example, a RADIUS proxy may
act as a server to one or more RADIUS authentication clients, while act 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 authentication servers. In such situations, it is expected that
RADIUS entities combining client and server functionality will RADIUS entities combining client and server functionality will
support both the client and server MIBs. The server MIB is defined support both the client and server MIBs. The server MIB is defined
in this document, and the client MIB is defined in [2618bis]. in this document, and the client MIB is defined in [RFC4668].
RFC Editor: Replace the above I-D reference with the assigned RFC
number at the time of publication and delete this note.
This MIB module contains fourteen scalars as well as a single table, This MIB module contains fourteen scalars as well as a single table,
the RADIUS Authentication Client Table, which contains one row for the RADIUS Authentication Client Table, which contains one row for
each RADIUS authentication client with which the server shares a each RADIUS authentication client with which the server shares a
secret. Each entry in the RADIUS Authentication Client Table secret. Each entry in the RADIUS Authentication Client Table
includes thirteen columns presenting a view of the activity of the includes thirteen columns presenting a view of the activity of the
RADIUS authentication server. RADIUS authentication server.
This MIB imports from [RFC2578], [RFC2580], [RFC3411], and [RFC4001].
6. Deprecated Objects 6. Deprecated Objects
The deprecated table in this MIB is carried forward from RFC 2619 The deprecated table in this MIB is carried forward from RFC 2619
[RFC2619]. There are two conditions under which it MAY be desirable [RFC2619]. There are two conditions under which it MAY be desirable
for managed entities to continue to support the deprecated table: for managed entities to continue to support the deprecated table:
1. The managed entity only supports IPv4 address formats. 1. The managed entity only supports IPv4 address formats.
2. The managed entity supports both IPv4 and IPv6 address formats, 2. The managed entity supports both IPv4 and IPv6 address formats,
and the deprecated table is supported for backwards compatibility and the deprecated table is supported for backwards compatibility
with older management stations. This option SHOULD only be used with older management stations. This option SHOULD only be used
when the IP addresses in the new table are in IPv4 format and can when the IP addresses in the new table are in IPv4 format and can
accurately be represented in both the new table and the accurately be represented in both the new table and the
deprecated table. deprecated table.
Managed entities SHOULD NOT instantiate row entries in the deprecated Managed entities SHOULD NOT instantiate row entries in the deprecated
table, containing IPv4-only address objects, when the RADIUS client table, containing IPv4-only address objects, when the RADIUS client
address represented in such a table row is not an IPv4 address. address represented in such a table row is not an IPv4 address.
skipping to change at page 5, line 27 skipping to change at page 5, line 26
when the IP addresses in the new table are in IPv4 format and can when the IP addresses in the new table are in IPv4 format and can
accurately be represented in both the new table and the accurately be represented in both the new table and the
deprecated table. deprecated table.
Managed entities SHOULD NOT instantiate row entries in the deprecated Managed entities SHOULD NOT instantiate row entries in the deprecated
table, containing IPv4-only address objects, when the RADIUS client table, containing IPv4-only address objects, when the RADIUS client
address represented in such a table row is not an IPv4 address. address represented in such a table row is not an IPv4 address.
Managed entities SHOULD NOT return inaccurate values of IP address or Managed entities SHOULD NOT return inaccurate values of IP address or
SNMP object access errors for IPv4-only address objects in otherwise SNMP object access errors for IPv4-only address objects in otherwise
populated tables. When row entries exist in both the deprecated populated tables. When row entries exist in both the deprecated
IPv4-only table and the new IP version neutral table that describe IPv4-only table and the new IP-version-neutral table that describe
the same RADIUS client, the row indexes SHOULD be the same for the the same RADIUS client, the row indexes SHOULD be the same for the
corresponding rows in each table, to facilitate correlation of these corresponding rows in each table, to facilitate correlation of these
related rows by management applications. related rows by management applications.
7. Definitions 7. Definitions
RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN RADIUS-AUTH-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32, Counter32, Integer32,
IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress FROM INET-ADDRESS-MIB InetAddressType, InetAddress FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radiusAuthServMIB MODULE-IDENTITY radiusAuthServMIB MODULE-IDENTITY
LAST-UPDATED "200608210000Z" -- 21 August 2006
ORGANIZATION "IETF RADIUS Extensions Working Group." ORGANIZATION "IETF RADIUS Extensions 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 server "The MIB module for entities implementing the server
side of the Remote Authentication Dial-In User side of the Remote Authentication Dial-In User
Service (RADIUS) authentication protocol. Copyright Service (RADIUS) authentication protocol. Copyright
(C) The Internet Society (2006). This version of this (C) The Internet Society (2006). This version of this
MIB module is part of RFC xxxx; see the RFC itself for MIB module is part of RFC 4669; see the RFC itself for
full legal notices." full legal notices."
REVISION "200608210000Z" -- 21 August 2006
-- RFC Editor: replace xxxx with actual RFC number at the time of
-- publication, and remove this note.
DESCRIPTION DESCRIPTION
"Revised version as published in RFC xxxx. This "Revised version as published in RFC 4669. This
version obsoletes that of RFC 2619 by deprecating the version obsoletes that of RFC 2619 by deprecating the
MIB table containing IPv4-only address formats and MIB table containing IPv4-only address formats and
defining a new table to add support for version neutral defining a new table to add support for version-neutral
IP address formats. The remaining MIB objects from RFC IP address formats. The remaining MIB objects from RFC
2619 are carried forward into this version." 2619 are carried forward into this version."
-- RFC Editor: replace xxxx with actual RFC number at the time of
-- publication, and remove this note.
DESCRIPTION "Initial version as published in RFC 2619." DESCRIPTION "Initial version as published in RFC 2619."
::= { radiusAuthentication 1 } ::= { radiusAuthentication 1 }
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 67 } ::= { mib-2 67 }
radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1} radiusAuthentication OBJECT IDENTIFIER ::= {radiusMIB 1}
skipping to change at page 7, line 10 skipping to change at page 6, line 44
radiusAuthServ OBJECT IDENTIFIER radiusAuthServ OBJECT IDENTIFIER
::= { radiusAuthServMIBObjects 1 } ::= { radiusAuthServMIBObjects 1 }
radiusAuthServIdent OBJECT-TYPE radiusAuthServIdent OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The implementation identification string for the "The implementation identification string for the
RADIUS authentication server software in use on the RADIUS authentication server software in use on the
system, for example; `FNS-2.1'" system, for example, 'FNS-2.1'."
::= {radiusAuthServ 1} ::= {radiusAuthServ 1}
radiusAuthServUpTime OBJECT-TYPE radiusAuthServUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the server has a persistent state (e.g., a "If the server has a persistent state (e.g., a
process), this value will be the time elapsed (in process), this value will be the time elapsed (in
hundredths of a second) since the server process hundredths of a second) since the server process
was started. For software without persistent state, was started. For software without persistent state,
this value will be zero." this value will be zero."
::= {radiusAuthServ 2} ::= {radiusAuthServ 2}
radiusAuthServResetTime OBJECT-TYPE radiusAuthServResetTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the server has a persistent state (e.g., a process) "If the server has a persistent state (e.g., a process)
and supports a `reset' operation (e.g., can be told to and supports a 'reset' operation (e.g., can be told to
re-read configuration files), this value will be the re-read configuration files), this value will be the
time elapsed (in hundredths of a second) since the time elapsed (in hundredths of a second) since the
server was `reset.' For software that does not server was 'reset.' For software that does not
have persistence or does not support a `reset' have persistence or does not support a 'reset'
operation, this value will be zero." operation, this value will be zero."
::= {radiusAuthServ 3} ::= {radiusAuthServ 3}
radiusAuthServConfigReset OBJECT-TYPE radiusAuthServConfigReset OBJECT-TYPE
SYNTAX INTEGER { other(1), SYNTAX INTEGER { other(1),
reset(2), reset(2),
initializing(3), initializing(3),
running(4)} running(4)}
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 9, line 44 skipping to change at page 9, line 32
REFERENCE "RFC 2865 section 4.1" REFERENCE "RFC 2865 section 4.1"
::= { radiusAuthServ 11 } ::= { radiusAuthServ 11 }
radiusAuthServTotalBadAuthenticators OBJECT-TYPE radiusAuthServTotalBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Authentication-Request packets "The number of RADIUS Authentication-Request packets
which contained invalid Message Authenticator that contained invalid Message Authenticator
attributes received." attributes received."
REFERENCE "RFC 2865 section 3" REFERENCE "RFC 2865 section 3"
::= { radiusAuthServ 12 } ::= { radiusAuthServ 12 }
radiusAuthServTotalPacketsDropped OBJECT-TYPE radiusAuthServTotalPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 10, line 20 skipping to change at page 10, line 8
unknown types." unknown types."
REFERENCE "RFC 2865 section 3" REFERENCE "RFC 2865 section 3"
::= { radiusAuthServ 13 } ::= { radiusAuthServ 13 }
radiusAuthServTotalUnknownTypes OBJECT-TYPE radiusAuthServTotalUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS packets of unknown type which "The number of RADIUS packets of unknown type that
were received." were received."
REFERENCE "RFC 2865 section 4" REFERENCE "RFC 2865 section 4"
::= { radiusAuthServ 14 } ::= { radiusAuthServ 14 }
radiusAuthClientTable OBJECT-TYPE radiusAuthClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAuthClientEntry SYNTAX SEQUENCE OF RadiusAuthClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS "The (conceptual) table listing the RADIUS
skipping to change at page 13, line 35 skipping to change at page 13, line 24
REFERENCE "RFC 2865 section 3" REFERENCE "RFC 2865 section 3"
::= { radiusAuthClientEntry 9 } ::= { radiusAuthClientEntry 9 }
radiusAuthServBadAuthenticators OBJECT-TYPE radiusAuthServBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS Authentication-Request packets "The number of RADIUS Authentication-Request packets
which contained invalid Message Authenticator that contained invalid Message Authenticator
attributes received from this client." attributes received from this client."
REFERENCE "RFC 2865 section 3" REFERENCE "RFC 2865 section 3"
::= { radiusAuthClientEntry 10 } ::= { radiusAuthClientEntry 10 }
radiusAuthServPacketsDropped OBJECT-TYPE radiusAuthServPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
skipping to change at page 14, line 4 skipping to change at page 13, line 41
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of incoming packets from this "The number of incoming packets from this
client silently discarded for some reason other client silently discarded for some reason other
than malformed, bad authenticators or than malformed, bad authenticators or
unknown types." unknown types."
REFERENCE "RFC 2865 section 3" REFERENCE "RFC 2865 section 3"
::= { radiusAuthClientEntry 11 } ::= { radiusAuthClientEntry 11 }
radiusAuthServUnknownTypes OBJECT-TYPE radiusAuthServUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS packets of unknown type which "The number of RADIUS packets of unknown type that
were received from this client." were received from this client."
REFERENCE "RFC 2865 section 4" REFERENCE "RFC 2865 section 4"
::= { radiusAuthClientEntry 12 } ::= { radiusAuthClientEntry 12 }
-- New MIB objects added in this revision -- New MIB objects added in this revision
radiusAuthClientExtTable OBJECT-TYPE radiusAuthClientExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAuthClientExtEntry SYNTAX SEQUENCE OF RadiusAuthClientExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS "The (conceptual) table listing the RADIUS
authentication clients with which the server shares authentication clients with which the server shares
a secret." a secret."
skipping to change at page 15, line 33 skipping to change at page 15, line 22
radiusAuthClientInetAddress object." radiusAuthClientInetAddress object."
::= { radiusAuthClientExtEntry 2 } ::= { radiusAuthClientExtEntry 2 }
radiusAuthClientInetAddress OBJECT-TYPE radiusAuthClientInetAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the RADIUS authentication "The IP address of the RADIUS authentication
client referred to in this table entry, using client referred to in this table entry, using
the version neutral IP address format." the version-neutral IP address format."
::= { radiusAuthClientExtEntry 3 } ::= { radiusAuthClientExtEntry 3 }
radiusAuthClientExtID OBJECT-TYPE radiusAuthClientExtID 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
referred to in this table entry. This is not referred to in this table entry. This is not
necessarily the same as sysName in MIB II." necessarily the same as sysName in MIB II."
skipping to change at page 18, line 10 skipping to change at page 17, line 46
REFERENCE "RFC 2865 sections 3, 4.1" REFERENCE "RFC 2865 sections 3, 4.1"
::= { radiusAuthClientExtEntry 10 } ::= { radiusAuthClientExtEntry 10 }
radiusAuthServExtBadAuthenticators OBJECT-TYPE radiusAuthServExtBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Authentication-Request packets "The number of RADIUS Authentication-Request packets
which contained invalid Message Authenticator that contained invalid Message Authenticator
attributes received from this client. This counter attributes received from this client. This counter
may experience a discontinuity when the RADIUS Server may experience a discontinuity when the RADIUS Server
module within the managed entity is reinitialized, as module within the managed entity is reinitialized, as
indicated by the current value of indicated by the current value of
radiusAuthServCounterDiscontinuity." radiusAuthServCounterDiscontinuity."
REFERENCE "RFC 2865 section 3" REFERENCE "RFC 2865 section 3"
::= { radiusAuthClientExtEntry 11 } ::= { radiusAuthClientExtEntry 11 }
radiusAuthServExtPacketsDropped OBJECT-TYPE radiusAuthServExtPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 18, line 41 skipping to change at page 18, line 29
radiusAuthServCounterDiscontinuity." radiusAuthServCounterDiscontinuity."
REFERENCE "RFC 2865 section 3" REFERENCE "RFC 2865 section 3"
::= { radiusAuthClientExtEntry 12 } ::= { radiusAuthClientExtEntry 12 }
radiusAuthServExtUnknownTypes OBJECT-TYPE radiusAuthServExtUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets" UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS packets of unknown type which "The number of RADIUS packets of unknown type that
were received from this client. This counter may were received from this client. This counter may
experience a discontinuity when the RADIUS Server experience a discontinuity when the RADIUS Server
module within the managed entity is reinitialized, as module within the managed entity is reinitialized, as
indicated by the current value of indicated by the current value of
radiusAuthServCounterDiscontinuity." radiusAuthServCounterDiscontinuity."
REFERENCE "RFC 2865 section 4" REFERENCE "RFC 2865 section 4"
::= { radiusAuthClientExtEntry 13 } ::= { radiusAuthClientExtEntry 13 }
radiusAuthServCounterDiscontinuity OBJECT-TYPE radiusAuthServCounterDiscontinuity OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
skipping to change at page 22, line 4 skipping to change at page 21, line 38
radiusAuthServExtBadAuthenticators, radiusAuthServExtBadAuthenticators,
radiusAuthServExtPacketsDropped, radiusAuthServExtPacketsDropped,
radiusAuthServExtUnknownTypes, radiusAuthServExtUnknownTypes,
radiusAuthServCounterDiscontinuity radiusAuthServCounterDiscontinuity
} }
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 2 } ::= { radiusAuthServMIBGroups 2 }
END
8. IANA Considerations
This document requires no new IANA assignments. END
9. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are: network operations. These are:
radiusAuthServConfigReset This object can be used to reinitialize the radiusAuthServConfigReset
persistent state of any server. When set to reset(2), any This object can be used to reinitialize the persistent state of
persistent server state (such as a process) is reinitialized as if any server. When set to reset(2), any persistent server state
the server had just been started. Depending on the server (such as a process) is reinitialized as if the server had just
impelmentation details, this action may ot may not interrupt the been started. Depending on the server implementation details,
processing of pending request in the server. Abuse of this object this action may or may not interrupt the processing of pending
may lead to a Denial of Service attack on the server. request in the server. Abuse of this object may lead to a Denial
of Service attack on the server.
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:
radiusAuthClientIPAddress This can be used to determine the address radiusAuthClientIPAddress
of the RADIUS authentication client with which the server is This can be used to determine the address of the RADIUS
communicating. This information could be useful in mounting an authentication client with which the server is communicating.
attack on the authentication client. This information could be useful in mounting an attack on the
radiusAuthClientInetAddress This can be used to determine the address authentication client.
of the RADIUS authentication client with which the server is
communicating. This information could be useful in mounting an radiusAuthClientInetAddress
attack on the authentication client. This can be used to determine the address of the RADIUS
authentication client with which the server is communicating.
This information could be useful in mounting an attack on the
authentication client.
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.
SNMP versions prior to SNMPv3 do not provide a secure environment. SNMP versions prior to SNMPv3 do not provide a secure environment.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
skipping to change at page 23, line 16 skipping to change at page 22, line 51
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them rights to indeed GET or SET (change/create/delete) them.
10. References 9. References
10.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000. RFC 2865, June 2000.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
10.2. Informative References 9.2. Informative References
[2618bis] Nelson, D., "RADIUS Authentication Client MIB for IPv6",
draft-ietf-radext-rfc2618bis-04.txt (work in progress),
June 2006.
[RFC2619] Zorn, G. and B. Aboba, "RADIUS Authentication Server MIB", [RFC2619] Zorn, G. and B. Aboba, "RADIUS Authentication Server MIB",
RFC 2619, June 1999. RFC 2619, June 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
Appendix A. Acknowledgments [RFC4668] Nelson, D., "RADIUS Authentication Client MIB for IPv6",
RFC 4668, August 2006.
Appendix A. Acknowledgements
The authors of the original MIB are Bernard Aboba and Glen Zorn. The authors of the original MIB are Bernard Aboba and Glen Zorn.
Many thanks to all reviewers, especially to David Harrington, Dan Many thanks to all reviewers, especially to David Harrington, Dan
Romascanu, C.M. Heard, Bruno Pape, Greg Weber and Bert Wijnen. Romascanu, C.M. Heard, Bruno Pape, Greg Weber, and Bert Wijnen.
Author's Address Author's Address
David B. Nelson David B. Nelson
Enterasys Networks Enterasys Networks
50 Minuteman Road 50 Minuteman Road
Andover, MA 01810 Andover, MA 01810
USA USA
Email: dnelson@enterasys.com EMail: dnelson@enterasys.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property
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 Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 26, line 29 skipping to change at page 25, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
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 copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 54 change blocks. 
137 lines changed or deleted 114 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/