draft-ietf-radext-rfc2621bis-04.txt   rfc4671.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Request for Comments: 4671 Enterasys Networks
Obsoletes: RFC 2621 (if approved) June 26, 2006 Obsoletes: 2621 August 2006
Expires: December 28, 2006 Category: Informational
RADIUS Accounting Server MIB for IPv6 RADIUS Accounting Server MIB for IPv6
draft-ietf-radext-rfc2621bis-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 memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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
accounting server functions. These extensions represent a portion of accounting server functions. These extensions represent a portion of
the Management Information Base (MIB) for use with network management the Management Information Base (MIB) for use with network management
protocols in the Internet community. Using these extensions IP-based protocols in the Internet community. Using these extensions,
management stations can manage RADIUS accounting servers. IP-based management stations can manage RADIUS accounting servers.
This memo obsoletes RFC 2621 by deprecating the MIB table containing This memo obsoletes RFC 2621 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 2621 are carried forward into this document. This memo also adds RFC 2621 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 . . . . . . . . . . . . . . . . . . . . . 21 8. Security Considerations ........................................20
9. Security Considerations . . . . . . . . . . . . . . . . . . . 21 9. References .....................................................22
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22 9.1. Normative References ......................................22
10.1. Normative References . . . . . . . . . . . . . . . . . . 22 9.2. Informative References ....................................22
10.2. Informative References . . . . . . . . . . . . . . . . . 22 Appendix A. Acknowledgements ......................................23
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 23
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . . . . . 25
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) Accounting Server as
defined in RFC 2866 [RFC2866].
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 2866 [RFC2866]. This document uses terminology from RFC 2865 [RFC2865] and RFC 2866
[RFC2866].
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 2866 does not provide an explicit definition of packets". While RFC 2866 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 2866. determined the packet does not match the format defined in RFC 2866.
Those implementations are used in deployments today, and thus set the Those implementations are used in deployments today, and thus set the
de-facto definition of "malformed". de facto definition of "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) Accounting Server as
defined in RFC 2866 [RFC2866].
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).
skipping to change at page 4, line 4 skipping to change at page 3, line 51
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 2621 [RFC2621], RADIUS Accounting Server This document obsoletes RFC 2621 [RFC2621], RADIUS Accounting Server
MIB, by deprecating the radiusAccClientTable table and adding a new MIB, by deprecating the radiusAccClientTable table and adding a new
table, radiusAccClientExtTable, containing table, radiusAccClientExtTable, containing
radiusAccClientInetAddressType and radiusAccClientInetAddress. The radiusAccClientInetAddressType and radiusAccClientInetAddress. 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
radiusAccClientAddress is deprecated. The remaining MIB objects from radiusAccClientAddress is deprecated. The remaining MIB objects from
RFC 2621 are carried forward into this document. This memo also adds RFC 2621 are carried forward into this document. This memo also adds
UNITS and REFERENCE clauses to selected objects. 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 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 Network Access Server reply with Accounting-Responses. Typically, Network Access Server
(NAS) devices implement the client function, and thus would be (NAS) devices implement the client function, and thus would be
expected to implement the RADIUS accounting client MIB, while RADIUS expected to implement the RADIUS accounting client MIB, while RADIUS
accounting servers implement the server function, and thus would be accounting servers implement the server function, and thus would be
expected to implement the RADIUS 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 server MIB is defined in this the client and server MIBs. The server MIB is defined in this
document, and the client MIB is defined in [2620bis]. document, and the client MIB is defined in [RFC4670].
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 thirteen scalars as well as a single table, This MIB module contains thirteen scalars as well as a single table,
the RADIUS Accounting Client Table, which contains one row for each the RADIUS Accounting Client Table, which contains one row for each
RADIUS accounting client with which the server shares a secret. Each RADIUS accounting client with which the server shares a secret. Each
entry in the RADIUS Accounting Client Table includes twelve columns entry in the RADIUS Accounting Client Table includes twelve columns
presenting a view of the activity of the RADIUS accounting server. presenting a view of the activity of the RADIUS accounting 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 2621 The deprecated table in this MIB is carried forward from RFC 2621
[RFC2621]. There are two conditions under which it MAY be desirable [RFC2621]. 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 table, containing IPv4-only address objects, when the RADIUS
accounting client address represented in such a table row is not an accounting client address represented in such a table row is not an
skipping to change at page 5, line 25 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 table, containing IPv4-only address objects, when the RADIUS
accounting client address represented in such a table row is not an accounting client address represented in such a table row is not an
IPv4 address. Managed entities SHOULD NOT return inaccurate values IPv4 address. Managed entities SHOULD NOT return inaccurate values
of IP address or SNMP object access errors for IPv4-only address of IP address or SNMP object access errors for IPv4-only address
objects in otherwise populated tables. When row entries exist in objects in otherwise populated tables. When row entries exist in
both the deprecated IPv4-only table and the new IP version neutral both the deprecated IPv4-only table and the new IP-version-neutral
table that describe the same RADIUS accounting client, the row table that describe the same RADIUS accounting client, the row
indexes SHOULD be the same for the corresponding rows in each table, indexes SHOULD be the same for the corresponding rows in each table,
to facilitate correlation of these related rows by management to facilitate correlation of these related rows by management
applications. applications.
7. Definitions 7. Definitions
RADIUS-ACC-SERVER-MIB DEFINITIONS ::= BEGIN RADIUS-ACC-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;
radiusAccServMIB MODULE-IDENTITY radiusAccServMIB 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) accounting protocol. Copyright (C) Service (RADIUS) accounting protocol. Copyright (C)
The Internet Society (2006). This version of this The Internet Society (2006). This version of this
MIB module is part of RFC xxxx; see the RFC itself MIB module is part of RFC 4671; see the RFC itself
forfull legal notices." forfull 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 4671. This
version obsoletes that of RFC 2621 by deprecating version obsoletes that of RFC 2621 by deprecating
the MIB table containing IPv4-only address formats the MIB table containing IPv4-only address formats
and defining a new table to add support for version and defining a new table to add support for version-
neutral IP address formats. The remaining MIB objects neutral IP address formats. The remaining MIB objects
from RFC 2621 are carried forward into this version." from RFC 2621 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 2621." DESCRIPTION "Initial version as published in RFC 2621."
::= { radiusAccounting 1 } ::= { radiusAccounting 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 }
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2} radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
skipping to change at page 7, line 8 skipping to change at page 6, line 45
radiusAccServ OBJECT IDENTIFIER radiusAccServ OBJECT IDENTIFIER
::= { radiusAccServMIBObjects 1 } ::= { radiusAccServMIBObjects 1 }
radiusAccServIdent OBJECT-TYPE radiusAccServIdent 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 accounting server software in use on the RADIUS accounting server software in use on the
system, for example; `FNS-2.1'" system, for example, 'FNS-2.1'."
::= {radiusAccServ 1} ::= {radiusAccServ 1}
radiusAccServUpTime OBJECT-TYPE radiusAccServUpTime 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 was hundredths of a second) since the server process was
started. For software without persistent state, this started. For software without persistent state, this
value will be zero." value will be zero."
::= {radiusAccServ 2} ::= {radiusAccServ 2}
radiusAccServResetTime OBJECT-TYPE radiusAccServResetTime 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."
::= {radiusAccServ 3} ::= {radiusAccServ 3}
radiusAccServConfigReset OBJECT-TYPE radiusAccServConfigReset 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 23 skipping to change at page 9, line 13
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccServ 9 } ::= { radiusAccServ 9 }
radiusAccServTotalBadAuthenticators OBJECT-TYPE radiusAccServTotalBadAuthenticators 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 Accounting-Request packets "The number of RADIUS Accounting-Request packets
which contained an invalid authenticator." that contained an invalid authenticator."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccServ 10 } ::= { radiusAccServ 10 }
radiusAccServTotalPacketsDropped OBJECT-TYPE radiusAccServTotalPacketsDropped 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 incoming packets silently discarded "The number of incoming packets silently discarded
skipping to change at page 9, line 46 skipping to change at page 9, line 36
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccServ 11 } ::= { radiusAccServ 11 }
radiusAccServTotalNoRecords OBJECT-TYPE radiusAccServTotalNoRecords 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 Accounting-Request packets "The number of RADIUS Accounting-Request packets
which were received and responded to but not that were received and responded to but not
recorded." recorded."
::= { radiusAccServ 12 } ::= { radiusAccServ 12 }
radiusAccServTotalUnknownTypes OBJECT-TYPE radiusAccServTotalUnknownTypes 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 2866 section 4" REFERENCE "RFC 2866 section 4"
::= { radiusAccServ 13 } ::= { radiusAccServ 13 }
radiusAccClientTable OBJECT-TYPE radiusAccClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccClientEntry SYNTAX SEQUENCE OF RadiusAccClientEntry
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
skipping to change at page 12, line 41 skipping to change at page 12, line 31
REFERENCE "RFC 2866 section 4.2" REFERENCE "RFC 2866 section 4.2"
::= { radiusAccClientEntry 7 } ::= { radiusAccClientEntry 7 }
radiusAccServBadAuthenticators OBJECT-TYPE radiusAccServBadAuthenticators 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 Accounting-Request packets "The number of RADIUS Accounting-Request packets
which contained invalid authenticators received that contained invalid authenticators received
from this client." from this client."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccClientEntry 8 } ::= { radiusAccClientEntry 8 }
radiusAccServMalformedRequests OBJECT-TYPE radiusAccServMalformedRequests 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 malformed RADIUS Accounting-Request "The number of malformed RADIUS Accounting-Request
packets which were received from this client. packets that were received from this client.
Bad authenticators and unknown types Bad authenticators and unknown types
are not included as malformed Accounting-Requests." are not included as malformed Accounting-Requests."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccClientEntry 9 } ::= { radiusAccClientEntry 9 }
radiusAccServNoRecords OBJECT-TYPE radiusAccServNoRecords 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 Accounting-Request packets "The number of RADIUS Accounting-Request packets
which were received and responded to but not that were received and responded to but not
recorded." recorded."
::= { radiusAccClientEntry 10 } ::= { radiusAccClientEntry 10 }
radiusAccServUnknownTypes OBJECT-TYPE radiusAccServUnknownTypes 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 2866 section 4" REFERENCE "RFC 2866 section 4"
::= { radiusAccClientEntry 11 } ::= { radiusAccClientEntry 11 }
-- New MIB objects added in this revision -- New MIB objects added in this revision
radiusAccClientExtTable OBJECT-TYPE radiusAccClientExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccClientExtEntry SYNTAX SEQUENCE OF RadiusAccClientExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 16, line 45 skipping to change at page 16, line 34
REFERENCE "RFC 2866 section 4.2" REFERENCE "RFC 2866 section 4.2"
::= { radiusAccClientExtEntry 8 } ::= { radiusAccClientExtEntry 8 }
radiusAccServExtBadAuthenticators OBJECT-TYPE radiusAccServExtBadAuthenticators 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 Accounting-Request packets "The number of RADIUS Accounting-Request packets
which contained invalid authenticators received that contained invalid authenticators received
from this client. This counter may experience a from this client. This counter may experience a
discontinuity when the RADIUS Accounting Server discontinuity when the RADIUS Accounting Server
module within the managed entity is reinitialized, module within the managed entity is reinitialized,
as indicated by the current value of as indicated by the current value of
radiusAccServerCounterDiscontinuity." radiusAccServerCounterDiscontinuity."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccClientExtEntry 9 } ::= { radiusAccClientExtEntry 9 }
radiusAccServExtMalformedRequests OBJECT-TYPE radiusAccServExtMalformedRequests 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 malformed RADIUS Accounting-Request "The number of malformed RADIUS Accounting-Request
packets which were received from this client. packets that were received from this client.
Bad authenticators and unknown types are not Bad authenticators and unknown types are not
included as malformed Accounting-Requests. This included as malformed Accounting-Requests. This
counter may experience a discontinuity when the counter may experience a discontinuity when the
RADIUS Accounting Server module within the managed RADIUS Accounting Server module within the managed
entity is reinitialized, as indicated by the current entity is reinitialized, as indicated by the current
value of radiusAccServerCounterDiscontinuity." value of radiusAccServerCounterDiscontinuity."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccClientExtEntry 10 } ::= { radiusAccClientExtEntry 10 }
radiusAccServExtNoRecords OBJECT-TYPE radiusAccServExtNoRecords 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 Accounting-Request packets "The number of RADIUS Accounting-Request packets
which were received and responded to but not that were received and responded to but not
recorded. This counter may experience a recorded. This counter may experience a
discontinuity when the RADIUS Accounting Server discontinuity when the RADIUS Accounting Server
module within the managed entity is reinitialized, module within the managed entity is reinitialized,
as indicated by the current value of as indicated by the current value of
radiusAccServerCounterDiscontinuity." radiusAccServerCounterDiscontinuity."
::= { radiusAccClientExtEntry 11 } ::= { radiusAccClientExtEntry 11 }
radiusAccServExtUnknownTypes OBJECT-TYPE radiusAccServExtUnknownTypes 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 Accounting experience a discontinuity when the RADIUS Accounting
Server module within the managed entity is Server module within the managed entity is
reinitialized, as indicated by the current value of reinitialized, as indicated by the current value of
radiusAccServerCounterDiscontinuity." radiusAccServerCounterDiscontinuity."
REFERENCE "RFC 2866 section 4" REFERENCE "RFC 2866 section 4"
::= { radiusAccClientExtEntry 12 } ::= { radiusAccClientExtEntry 12 }
radiusAccServerCounterDiscontinuity OBJECT-TYPE radiusAccServerCounterDiscontinuity OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
UNITS "centiseconds" UNITS "centiseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of centiseconds since the last "The number of centiseconds since the last
discontinuity in the RADIUS Accounting Server discontinuity in the RADIUS Accounting Server
counters. A discontinuity may be the result of counters. A discontinuity may be the result of
a reinitialization of the RADIUS Accounting Server a reinitialization of the RADIUS Accounting Server
skipping to change at page 21, line 5 skipping to change at page 20, line 41
radiusAccServerCounterDiscontinuity radiusAccServerCounterDiscontinuity
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects providing management of "The collection of objects providing management of
a RADIUS Accounting Server." a RADIUS Accounting Server."
::= { radiusAccServMIBGroups 2 } ::= { radiusAccServMIBGroups 2 }
END END
8. IANA Considerations 8. Security Considerations
This document requires no new IANA assignments.
9. Security Considerations
There are management objects (radiusAccServConfigReset) defined in There are management objects (radiusAccServConfigReset) defined in
this MIB that have a MAX-ACCESS clause of read-write and/or read- this MIB that have a MAX-ACCESS clause of read-write and/or read-
create. Such objects may be considered sensitive or vulnerable in create. Such objects may be considered sensitive or vulnerable in
some network environments. The support for SET operations in a non- some network environments. The support for SET operations in a non-
secure environment without proper protection can have a negative secure environment without proper protection can have a negative
effect on network operations. These are: effect on network operations. These are:
radiusAccServConfigReset This object can be used to reinitialize the radiusAccServConfigReset
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 or 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:
radiusAccClientIPAddress This can be used to determine the address of radiusAccClientIPAddress
the RADIUS accounting client with which the server is This can be used to determine the address of the RADIUS accounting
communicating. This information could be useful in mounting an client with which the server is communicating. This information
attack on the accounting client. could be useful in mounting an attack on the accounting client.
radiusAccClientInetAddress This can be used to determine the address
of the RADIUS accounting client with which the server is radiusAccClientInetAddress
communicating. This information could be useful in mounting an This can be used to determine the address of the RADIUS accounting
attack on the accounting client. client with which the server is communicating. This information
could be useful in mounting an attack on the accounting 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 22, line 14 skipping to change at page 22, line 5
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.
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, 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
[2620bis] Nelson, D., "RADIUS Accounting Client MIB for IPv6",
draft-ietf-radext-rfc2620bis-04.txt (work in progress),
June 2006.
[RFC2621] Zorn, G. and B. Aboba, "RADIUS Accounting Server MIB", [RFC2621] Zorn, G. and B. Aboba, "RADIUS Accounting Server MIB",
RFC 2621, June 1999. RFC 2621, June 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.
[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 [RFC4670] Nelson, D., "RADIUS Accounting Client MIB for IPv6", RFC
4670, 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 Dave Harrington, Dan Many thanks to all reviewers, especially to Dave 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 25, line 29 skipping to change at page 24, 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. 53 change blocks. 
140 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/