draft-ietf-radext-rfc2620bis-01.txt   draft-ietf-radext-rfc2620bis-02.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Internet-Draft Enterasys Networks
Obsoletes: RFC 2620 (if approved) October 18, 2005 Obsoletes: RFC 2620 (if approved) January 25, 2006
Expires: April 21, 2006 Expires: July 29, 2006
RADIUS Acct Client MIB (IPv6) RADIUS Acct Client MIB (IPv6)
draft-ietf-radext-rfc2620bis-01.txt draft-ietf-radext-rfc2620bis-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 21, 2006. This Internet-Draft will expire on July 29, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a set of extensions which instrument RADIUS
accounting client functions. These extensions represent a portion of
the Management Information Base (MIB) for use with network management
protocols in the Internet community. Using these extensions IP-based
management stations can manage RADIUS accounting clients.
This memo obsoletes RFC 2620 by deprecating the MIB table containing This memo obsoletes RFC 2620 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 2620 are carried forward into this document. RFC 2620 are carried forward into this document. This memo also adds
UNITS and REFERENCE clauses to selected objects.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . 4 6. Deprecated Objects . . . . . . . . . . . . . . . . . . . . . . 4
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
10.1. Normative References . . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . 19
10.2. Informative References . . . . . . . . . . . . . . . . . 18 10.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 18 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 21
Intellectual Property and Copyright Statements . . . . . . . . . . 20 Intellectual Property and Copyright Statements . . . . . . . . . . 22
1. Terminology 1. 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 2866 [RFC2866]. This document uses terminology from RFC 2866 [RFC2866].
This document uses the word "malformed" with respect to RADIUS
packets, particularly in the context of counters of "malformed
packets". While RFC 2866 does not provide an explicit definition of
"malformed", malformed generally means that the implementation has
determined the packet does not match the format defined in RFC 2866.
Those implementations are used in deployments today, and thus set the
de-facto definition of "malformed".
2. Introduction 2. 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.
The objects defined within this memo relate to the Remote The objects defined within this memo relate to the Remote
Authentication Dial-In User Service (RADIUS) Accounting Client as Authentication Dial-In User Service (RADIUS) Accounting Client as
defined in RFC 2866 [RFC2866]. defined in RFC 2866 [RFC2866].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
skipping to change at page 4, line 18 skipping to change at page 4, line 26
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 accounting protocol, described in RFC 2866 [RFC2866], The RADIUS accounting protocol, described in RFC 2866 [RFC2866],
distinguishes between the client function and the server function. distinguishes between the client function and the server function.
In RADIUS accounting, clients send Accounting-Requests, and servers In RADIUS accounting, clients send Accounting-Requests, and servers
reply with Accounting-Responses. Typically NAS devices implement the reply with Accounting-Responses. Typically Network Access Server
client function, and thus would be expected to implement the RADIUS (NAS) devices implement the client function, and thus would be
accounting client MIB, while RADIUS accounting servers implement the expected to implement the RADIUS accounting client MIB, while RADIUS
server function, and thus would be expected to implement the RADIUS accounting servers implement the server function, and thus would be
accounting server MIB. expected to implement the RADIUS accounting server MIB.
However, it is possible for a RADIUS accounting entity to perform However, it is possible for a RADIUS accounting 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 accounting clients, while act as a server to one or more RADIUS accounting clients, while
simultaneously acting as an accounting client to one or more simultaneously acting as an accounting client to one or more
accounting servers. In such situations, it is expected that RADIUS accounting servers. In such situations, it is expected that RADIUS
entities combining client and server functionality will support both entities combining client and server functionality will support both
the client and server MIBs. the client and server MIBs.
This MIB module contains two scalars as well as a single table, the This MIB module contains two scalars as well as a single table, the
RADIUS Accounting Server Table, which contains one row for each RADIUS Accounting Server Table, which contains one row for each
RADIUS server with which the client shares a secret. Each entry in RADIUS server with which the client shares a secret. Each entry in
the RADIUS Accounting Server Table includes fifteen columns the RADIUS Accounting Server Table includes fourteen columns
presenting a view of the activity of the RADIUS client. presenting a view of the activity of the RADIUS client.
6. Deprecated Objects 6. Deprecated Objects
The deprecated table in this MIB is carried forward from RFC 2620 The deprecated table in this MIB is carried forward from RFC 2620
[RFC2620]. There are two conditions under which it MAY be desirable [RFC2620]. 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 the deprecated table Managed entities SHOULD NOT instantiate row entries in the deprecated
containing IPv4-only address objects when the RADIUS server address table, containing IPv4-only address objects, when the RADIUS
represented in the table row is not an IPv4 address. Managed accounting server address represented in such a table row is not an
entities SHOULD NOT return inaccurate values of IP address or SNMP IPv4 address. Managed entities SHOULD NOT return inaccurate values
object access errors for IPv4-only address objects in otherwise of IP address or SNMP object access errors for IPv4-only address
populated tables. objects in otherwise populated tables. When row entries exist in
both the deprecated IPv4-only table and the new IP version neutral
table that describe the same RADIUS accounting server, the row
indexes SHOULD be the same for the corresponding rows in each table,
to facilitate correlation of these related rows by management
applications.
7. Definitions 7. Definitions
RADIUS-ACCT-CLIENT-MIB DEFINITIONS ::= BEGIN RADIUS-ACCT-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32, Gauge32, Counter32, Integer32, Gauge32,
IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress, InetAddressType, InetAddress,
InetPortNumber FROM INET-ADDRESS-MIB InetPortNumber FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radiusAccClientMIB MODULE-IDENTITY radiusAccClientMIB MODULE-IDENTITY
LAST-UPDATED "200510170000Z" -- 17 Oct 2005 LAST-UPDATED "200601250000Z" -- 25 Jan 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 client "The MIB module for entities implementing the client
side of the Remote Authentication Dial-In User Service side of the Remote Authentication Dial-In User Service
(RADIUS) accounting protocol." (RADIUS) accounting protocol."
REVISION "200510170000Z" -- 17 Oct 2005 REVISION "200601250000Z" -- 25 Jan 2006
DESCRIPTION "Revised version as published in RFC xxxx. DESCRIPTION "Revised version as published in RFC xxxx.
This version obsoletes that of RFC 2620 by deprecating the This version obsoletes that of RFC 2620 by deprecating the
MIB table containing IPv4-only address formats and defining a MIB table containing IPv4-only address formats and defining a
new table to add support for version neutral IP address new table to add support for version neutral IP address
formats. The remaining MIB objects from RFC 2620 are carried formats. The remaining MIB objects from RFC 2620 are carried
forward into this version." forward into this version."
REVISION "9906110000Z" -- 11 Jun 1999 REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2620" DESCRIPTION "Initial version as published in RFC 2620."
-- RFC Editor: replace xxxx with actual RFC number at the time of -- RFC Editor: replace xxxx with actual RFC number at the time of
-- publication, and remove this note. -- publication, and remove this note.
::= { radiusAccounting 2 } ::= { radiusAccounting 2 }
radiusMIB OBJECT-IDENTITY radiusMIB OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA." "The OID assigned to RADIUS MIB work by the IANA."
skipping to change at page 6, line 24 skipping to change at page 6, line 39
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2} radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
radiusAccClientMIBObjects OBJECT IDENTIFIER radiusAccClientMIBObjects OBJECT IDENTIFIER
::= { radiusAccClientMIB 1 } ::= { radiusAccClientMIB 1 }
radiusAccClient OBJECT IDENTIFIER radiusAccClient OBJECT IDENTIFIER
::= { radiusAccClientMIBObjects 1 } ::= { radiusAccClientMIBObjects 1 }
radiusAccClientInvalidServerAddresses OBJECT-TYPE radiusAccClientInvalidServerAddresses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Response packets "The number of RADIUS Accounting-Response packets
received from unknown addresses." received from unknown addresses."
::= { radiusAccClient 1 } ::= { radiusAccClient 1 }
radiusAccClientIdentifier OBJECT-TYPE radiusAccClientIdentifier 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 accounting client. "The NAS-Identifier of the RADIUS accounting client.
This is not necessarily the same as sysName in MIB This is not necessarily the same as sysName in MIB
II." II."
REFERENCE "RFC 2865 section 5.32"
::= { radiusAccClient 2 } ::= { radiusAccClient 2 }
radiusAccServerTable OBJECT-TYPE radiusAccServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccServerEntry SYNTAX SEQUENCE OF RadiusAccServerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS accounting "The (conceptual) table listing the RADIUS accounting
servers with which the client shares a secret." servers with which the client shares a secret."
::= { radiusAccClient 3 } ::= { radiusAccClient 3 }
skipping to change at page 8, line 7 skipping to change at page 8, line 24
referred to in this table entry." referred to in this table entry."
::= { radiusAccServerEntry 2 } ::= { radiusAccServerEntry 2 }
radiusAccClientServerPortNumber OBJECT-TYPE radiusAccClientServerPortNumber OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The UDP port the client is using to send requests to "The UDP port the client is using to send requests to
this server." this server."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerEntry 3 } ::= { radiusAccServerEntry 3 }
radiusAccClientRoundTripTime OBJECT-TYPE radiusAccClientRoundTripTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The time interval between the most recent "The time interval between the most recent
Accounting-Response and the Accounting-Request that Accounting-Response and the Accounting-Request that
matched it from this RADIUS accounting server." matched it from this RADIUS accounting server."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 4 } ::= { radiusAccServerEntry 4 }
-- Request/Response statistics -- Request/Response statistics
-- --
-- Requests = Responses + PendingRequests + ClientTimeouts -- Requests = Responses + PendingRequests + ClientTimeouts
-- --
-- Responses - MalformedResponses - BadAuthenticators - -- Responses - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received -- UnknownTypes - PacketsDropped = Successfully received
radiusAccClientRequests OBJECT-TYPE radiusAccClientRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Request packets "The number of RADIUS Accounting-Request packets
sent. This does not include retransmissions." sent. This does not include retransmissions."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccServerEntry 5 } ::= { radiusAccServerEntry 5 }
radiusAccClientRetransmissions OBJECT-TYPE radiusAccClientRetransmissions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Request packets "The number of RADIUS Accounting-Request packets
retransmitted to this RADIUS accounting server. retransmitted to this RADIUS accounting server.
Retransmissions include retries where the Retransmissions include retries where the
Identifier and Acct-Delay have been updated, as Identifier and Acct-Delay have been updated, as
well as those in which they remain the same." well as those in which they remain the same."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 6 } ::= { radiusAccServerEntry 6 }
radiusAccClientResponses OBJECT-TYPE radiusAccClientResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS packets received on the "The number of RADIUS packets received on the
accounting port from this server." accounting port from this server."
REFERENCE "RFC 2866 section 4.2"
::= { radiusAccServerEntry 7 } ::= { radiusAccServerEntry 7 }
radiusAccClientMalformedResponses OBJECT-TYPE radiusAccClientMalformedResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of malformed RADIUS Accounting-Response "The number of malformed RADIUS Accounting-Response
packets received from this server. Malformed packets packets received from this server. Malformed packets
include packets with an invalid length. Bad include packets with an invalid length. Bad
authenticators and unknown types are not included as authenticators and unknown types are not included as
malformed accounting responses." malformed accounting responses."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerEntry 8 } ::= { radiusAccServerEntry 8 }
radiusAccClientBadAuthenticators OBJECT-TYPE radiusAccClientBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Response "The number of RADIUS Accounting-Response
packets which contained invalid authenticators packets which contained invalid authenticators
received from this server." received from this server."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerEntry 9 } ::= { radiusAccServerEntry 9 }
radiusAccClientPendingRequests OBJECT-TYPE radiusAccClientPendingRequests OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Request packets "The number of RADIUS Accounting-Request packets
sent to this server that have not yet timed out or sent to this server that have not yet timed out or
received a response. This variable is incremented received a response. This variable is incremented
when an Accounting-Request is sent and decremented when an Accounting-Request is sent and decremented
due to receipt of an Accounting-Response, a timeout due to receipt of an Accounting-Response, a timeout
or a retransmission." or a retransmission."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 10 } ::= { radiusAccServerEntry 10 }
radiusAccClientTimeouts OBJECT-TYPE radiusAccClientTimeouts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "timeouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of accounting timeouts to this server. "The number of accounting timeouts to this server.
After a timeout the client may retry to the same After a timeout the client may retry to the same
server, send to a different server, or give up. server, send to a different server, or give up.
A retry to the same server is counted as a 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 an Accounting-Request as well as server is counted as an Accounting-Request as well as
a timeout." a timeout."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerEntry 11 } ::= { radiusAccServerEntry 11 }
radiusAccClientUnknownTypes OBJECT-TYPE radiusAccClientUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 which
were received from this server on the accounting port." were received from this server on the accounting port."
REFERENCE "RFC 2866 section 4"
::= { radiusAccServerEntry 12 } ::= { radiusAccServerEntry 12 }
radiusAccClientPacketsDropped OBJECT-TYPE radiusAccClientPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS packets which were received from "The number of RADIUS packets which were received from
this server on the accounting port and dropped for some this server on the accounting port and dropped for some
other reason." other reason."
::= { radiusAccServerEntry 13 } ::= { radiusAccServerEntry 13 }
-- New MIB objects added in this revision -- New MIB objects added in this revision
skipping to change at page 11, line 46 skipping to change at page 12, line 33
radiusAccServerInetAddress object." radiusAccServerInetAddress object."
::= { radiusAccServerExtEntry 2 } ::= { radiusAccServerExtEntry 2 }
radiusAccServerInetAddress OBJECT-TYPE radiusAccServerInetAddress 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 accounting "The IP address of the RADIUS accounting
server referred to in this table entry, using server referred to in this table entry, using
the version neutral IP adddess format." the version neutral IP address format."
::= { radiusAccServerExtEntry 3 } ::= { radiusAccServerExtEntry 3 }
radiusAccClientServerInetPortNumber OBJECT-TYPE radiusAccClientServerInetPortNumber OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The UDP port the client is using to send requests "The UDP port the client is using to send requests
to this accounting server." to this accounting server."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 4 } ::= { radiusAccServerExtEntry 4 }
radiusAccClientExtRoundTripTime OBJECT-TYPE radiusAccClientExtRoundTripTime OBJECT-TYPE
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
Accounting-Response and the Accounting-Request that Accounting-Response and the Accounting-Request that
matched it from this RADIUS accounting server." matched it from this RADIUS accounting server."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 5 } ::= { radiusAccServerExtEntry 5 }
-- Request/Response statistics -- Request/Response statistics
-- --
-- Requests = Responses + PendingRequests + ClientTimeouts -- Requests = Responses + PendingRequests + ClientTimeouts
-- --
-- Responses - MalformedResponses - BadAuthenticators - -- Responses - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received -- UnknownTypes - PacketsDropped = Successfully received
radiusAccClientExtRequests OBJECT-TYPE radiusAccClientExtRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Request packets "The number of RADIUS Accounting-Request packets
sent. This does not include retransmissions." sent. This does not include retransmissions."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccServerExtEntry 6 } ::= { radiusAccServerExtEntry 6 }
radiusAccClientExtRetransmissions OBJECT-TYPE radiusAccClientExtRetransmissions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Request packets "The number of RADIUS Accounting-Request packets
retransmitted to this RADIUS accounting server. retransmitted to this RADIUS accounting server.
Retransmissions include retries where the Retransmissions include retries where the
Identifier and Acct-Delay have been updated, as Identifier and Acct-Delay have been updated, as
well as those in which they remain the same." well as those in which they remain the same."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 7 } ::= { radiusAccServerExtEntry 7 }
radiusAccClientExtResponses OBJECT-TYPE radiusAccClientExtResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS packets received on the "The number of RADIUS packets received on the
accounting port from this server." accounting port from this server."
REFERENCE "RFC 2866 section 4.2"
::= { radiusAccServerExtEntry 8 } ::= { radiusAccServerExtEntry 8 }
radiusAccClientExtMalformedResponses OBJECT-TYPE radiusAccClientExtMalformedResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of malformed RADIUS Accounting-Response "The number of malformed RADIUS Accounting-Response
packets received from this server. Malformed packets packets received from this server. Malformed packets
include packets with an invalid length. Bad include packets with an invalid length. Bad
authenticators and unknown types are not included as authenticators and unknown types are not included as
malformed accounting responses." malformed accounting responses."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 9 } ::= { radiusAccServerExtEntry 9 }
radiusAccClientExtBadAuthenticators OBJECT-TYPE radiusAccClientExtBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Response "The number of RADIUS Accounting-Response
packets which contained invalid authenticators packets which contained invalid authenticators
received from this server." received from this server."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 10 } ::= { radiusAccServerExtEntry 10 }
radiusAccClientExtPendingRequests OBJECT-TYPE radiusAccClientExtPendingRequests OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Request packets "The number of RADIUS Accounting-Request packets
sent to this server that have not yet timed out or sent to this server that have not yet timed out or
received a response. This variable is incremented received a response. This variable is incremented
when an Accounting-Request is sent and decremented when an Accounting-Request is sent and decremented
due to receipt of an Accounting-Response, a timeout due to receipt of an Accounting-Response, a timeout
or a retransmission." or a retransmission."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 11 } ::= { radiusAccServerExtEntry 11 }
radiusAccClientExtTimeouts OBJECT-TYPE radiusAccClientExtTimeouts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "timeouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of accounting timeouts to this server. "The number of accounting timeouts to this server.
After a timeout the client may retry to the same After a timeout the client may retry to the same
server, send to a different server, or give up. server, send to a different server, or give up.
A retry to the same server is counted as a 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 an Accounting-Request as well as server is counted as an Accounting-Request as well as
a timeout." a timeout."
REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 12 } ::= { radiusAccServerExtEntry 12 }
radiusAccClientExtUnknownTypes OBJECT-TYPE radiusAccClientExtUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 which
were received from this server on the accounting port." were received from this server on the accounting port."
REFERENCE "RFC 2866 section 4"
::= { radiusAccServerExtEntry 13 } ::= { radiusAccServerExtEntry 13 }
radiusAccClientExtPacketsDropped OBJECT-TYPE radiusAccClientExtPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS packets which were received from "The number of RADIUS packets which were received from
this server on the accounting port and dropped for some this server on the accounting port and dropped for some
other reason." other reason."
::= { radiusAccServerExtEntry 14 } ::= { radiusAccServerExtEntry 14 }
-- conformance information -- conformance information
skipping to change at page 14, line 44 skipping to change at page 16, line 4
radiusAccClientMIBConformance OBJECT IDENTIFIER radiusAccClientMIBConformance OBJECT IDENTIFIER
::= { radiusAccClientMIB 2 } ::= { radiusAccClientMIB 2 }
radiusAccClientMIBCompliances OBJECT IDENTIFIER radiusAccClientMIBCompliances OBJECT IDENTIFIER
::= { radiusAccClientMIBConformance 1 } ::= { radiusAccClientMIBConformance 1 }
radiusAccClientMIBGroups OBJECT IDENTIFIER radiusAccClientMIBGroups OBJECT IDENTIFIER
::= { radiusAccClientMIBConformance 2 } ::= { radiusAccClientMIBConformance 2 }
-- units of conformance -- units of conformance
radiusAccClientMIBCompliance MODULE-COMPLIANCE radiusAccClientMIBCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for accounting clients "The compliance statement for accounting clients
implementing the RADIUS Accounting Client MIB." implementing the RADIUS Accounting Client MIB.
Implementation of this module is for IPv4-only
entities, or for backwards compatibility use with
entities that support both IPv4 and IPv6."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusAccClientMIBGroup } MANDATORY-GROUPS { radiusAccClientMIBGroup }
::= { radiusAccClientMIBCompliances 1 } ::= { radiusAccClientMIBCompliances 1 }
radiusAccClientExtMIBCompliance MODULE-COMPLIANCE radiusAccClientExtMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for accounting clients "The compliance statement for accounting
implementing the RADIUS Accounting Client MIB." clients implementing the RADIUS Accounting
Client IPv6 Extensions MIB. Implementation of
this module is for entities that support IPv6,
or support IPv4 and IPv6."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusAccClientExtMIBGroup } MANDATORY-GROUPS { radiusAccClientExtMIBGroup }
::= { radiusAccClientMIBCompliances 2 } ::= { radiusAccClientMIBCompliances 2 }
-- units of conformance -- units of conformance
radiusAccClientMIBGroup OBJECT-GROUP radiusAccClientMIBGroup OBJECT-GROUP
OBJECTS { radiusAccClientIdentifier, OBJECTS { radiusAccClientIdentifier,
radiusAccClientInvalidServerAddresses, radiusAccClientInvalidServerAddresses,
skipping to change at page 17, line 21 skipping to change at page 18, line 31
the port number on which the RADIUS accounting client is sending. the port number on which the RADIUS accounting client is sending.
This information could be useful in impersonating the client in This information could be useful in impersonating the client in
order to send data to the accounting server. order to send data to the accounting server.
It is thus important to control even GET access to these objects and It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment. for such a secure environment.
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
MIB. MIB.
It is recommended that the implementers consider the security It is RECOMMENDED that implementers consider the security features as
features as provided by the SNMPv3 framework. Specifically, the use provided by the SNMPv3 framework (see [RFC3410], section 8),
of the User-based Security Model [RFC2574] and the View-based Access including full support for the SNMPv3 cryptographic mechanisms (for
Control Model [RFC2575] is recommended. Using these security authentication and privacy).
features, customer/users can give access to the objects only to those
principals (users) that have legitimate rights to GET or SET (change/ Further, deployment of SNMP versions prior to SNMPv3 is NOT
create/delete) them. RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
10. References 10. References
10.1. Normative References 10.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.
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
skipping to change at page 18, line 14 skipping to change at page 19, line 30
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.
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.
[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.
[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.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. RFC 3418, 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 10.2. Informative References
[RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB", [RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB",
RFC 2620, June 1999. RFC 2620, June 1999.
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.
Appendix A. Acknowledgments Appendix A. Acknowledgments
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 Dave Harrington, Dan Many thanks to all reviewers, especially to Dave Harrington, Dan
Romascanu, C.M. Heard, Bruno Pape and Greg Weber. Romascanu, C.M. Heard, Bruno Pape and Greg Weber.
Author's Address Author's Address
David B. Nelson David B. Nelson
skipping to change at page 20, line 41 skipping to change at page 22, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 65 change blocks. 
46 lines changed or deleted 120 lines changed or added

This html diff was produced by rfcdiff 1.28, available from http://www.levkowetz.com/ietf/tools/rfcdiff/