draft-ietf-radext-rfc2621bis-00.txt   draft-ietf-radext-rfc2621bis-01.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Internet-Draft Enterasys Networks
Updates: RFC 2621 (if approved) August 30, 2005 Obsoletes: RFC 2621 (if approved) October 18, 2005
Expires: March 3, 2006 Expires: April 21, 2006
RADIUS Acct Server MIB (IPv6) RADIUS Acct Server MIB (IPv6)
draft-ietf-radext-rfc2621bis-00.txt draft-ietf-radext-rfc2621bis-01.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 March 3, 2006. This Internet-Draft will expire on April 21, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo updates 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. version neutral IP address formats. The remaining MIB objects from
RFC 2621 are carried forward into this document.
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 9. Security Considerations . . . . . . . . . . . . . . . . . . . 18
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
10.1. Normative References . . . . . . . . . . . . . . . . . . 19 10.1. Normative References . . . . . . . . . . . . . . . . . . 19
10.2. Informative References . . . . . . . . . . . . . . . . . 20 10.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 20 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 21 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 21
Intellectual Property and Copyright Statements . . . . . . . . . . 22 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].
skipping to change at page 3, line 38 skipping to change at page 3, line 38
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
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
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 updates 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. radiusAccClientAddress is deprecated. The remaining MIB objects from
RFC 2621 are carried forward into this document.
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 [RFC 4001] that support all textual conventions defined in this memo [RFC 4001] 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 structure of the MIB Module defined in this memo corresponds to The RADIUS accounting protocol, described in RFC 2866 [RFC2866],
the structure of the MIB Module defined in RADIUS Accounting Server distinguishes between the client function and the server function.
MIB, RFC 2621 [RFC2621]. This MIB module contains thirteen scalars In RADIUS accounting, clients send Accounting-Requests, and servers
as well as a single table, the RADIUS Accounting Client Table, which reply with Accounting-Responses. Typically NAS devices implement the
contains one row for each RADIUS accounting client with which the client function, and thus would be expected to implement the RADIUS
server shares a secret. accounting client MIB, while RADIUS accounting servers implement the
server function, and thus would be expected to implement the RADIUS
accounting server MIB.
Each entry in the RADIUS Accounting Client Table includes twelve However, it is possible for a RADIUS accounting entity to perform
columns presenting a view of the activity of the RADIUS accounting both client and server functions. For example, a RADIUS proxy may
server. act as a server to one or more RADIUS accounting clients, while
simultaneously acting as an accounting client to one or more
accounting servers. In such situations, it is expected that RADIUS
entities combining client and server functionality will support both
the client and server MIBs.
This MIB module contains thirteen scalars as well as a single table,
the RADIUS Accounting Client Table, which contains one row for each
RADIUS accounting client with which the server shares a secret. Each
entry in the RADIUS Accounting Client Table includes twelve columns
presenting a view of the activity of the RADIUS accounting server.
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
skipping to change at page 4, line 47 skipping to change at page 5, line 14
Managed entities SHOULD NOT instantiate the deprecated table Managed entities SHOULD NOT instantiate the deprecated table
containing IPv4-only address objects when the RADIUS server address containing IPv4-only address objects when the RADIUS server address
represented in the table row is not an IPv4 address. Managed represented in the table row is not an IPv4 address. Managed
entities SHOULD NOT return inaccurate values of IP address or SNMP entities SHOULD NOT return inaccurate values of IP address or SNMP
object access errors for IPv4-only address objects in otherwise object access errors for IPv4-only address objects in otherwise
populated tables. populated tables.
7. Definitions 7. Definitions
4. Definitions
RADIUS-ACCT-SERVER-MIB DEFINITIONS ::= BEGIN RADIUS-ACCT-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 "200508300000Z" -- 30 Aug 2005 LAST-UPDATED "200510170000Z" -- 17 Oct 2005
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." Service (RADIUS) accounting protocol."
REVISION "200510170000Z" -- 17 Oct 2005
DESCRIPTION "Revised version as published in RFC xxxx.
This version obsoletes that of RFC 2621 by deprecating the
MIB table containing IPv4-only address formats and defining
a new table to add support for version neutral IP address
formats. The remaining MIB objects from RFC 2621 are carried
forward into this version."
REVISION "9906110000Z" -- 11 Jun 1999 REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2621" DESCRIPTION "Initial version as published in RFC 2621"
REVISION "200508300000Z" -- 30 Aug 2005
DESCRIPTION "Revised version as published in RFC xxxx."
-- 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 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 }
radiusAccServExtMIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS Extensions MIB
work by the IANA."
::= { mib-2 TBA }
-- RFC Editor: replace TBA with IANA assigned OID value, and
-- remove this note.
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2} radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
radiusAccServMIBObjects OBJECT IDENTIFIER radiusAccServMIBObjects OBJECT IDENTIFIER
::= { radiusAccServMIB 1 } ::= { radiusAccServMIB 1 }
radiusAccServExtMIBObjects OBJECT IDENTIFIER
::= { radiusAccServExtMIB 1 }
radiusAccServ OBJECT IDENTIFIER radiusAccServ OBJECT IDENTIFIER
::= { radiusAccServMIBObjects 1 } ::= { radiusAccServMIBObjects 1 }
radiusAccServExt OBJECT IDENTIFIER
::= { radiusAccServExtMIBObjects 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}
skipping to change at page 12, line 20 skipping to change at page 12, line 21
radiusAccServUnknownTypes OBJECT-TYPE radiusAccServUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 client." were received from this client."
::= { radiusAccClientEntry 11 } ::= { radiusAccClientEntry 11 }
-- Extended MIB Objects -- 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
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS accounting "The (conceptual) table listing the RADIUS accounting
clients with which the server shares a secret." clients with which the server shares a secret."
::= { radiusAccServExt 1 } ::= { radiusAccServ 15 }
radiusAccClientExtEntry OBJECT-TYPE radiusAccClientExtEntry OBJECT-TYPE
SYNTAX RadiusAccClientExtEntry SYNTAX RadiusAccClientExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) representing a RADIUS "An entry (conceptual row) representing a RADIUS
accounting client with which the server shares a accounting client with which the server shares a
secret." secret."
INDEX { radiusAccClientExtIndex } INDEX { radiusAccClientExtIndex }
skipping to change at page 16, line 4 skipping to change at page 16, line 4
-- conformance information -- conformance information
radiusAccServMIBConformance OBJECT IDENTIFIER radiusAccServMIBConformance OBJECT IDENTIFIER
::= { radiusAccServMIB 2 } ::= { radiusAccServMIB 2 }
radiusAccServMIBCompliances OBJECT IDENTIFIER radiusAccServMIBCompliances OBJECT IDENTIFIER
::= { radiusAccServMIBConformance 1 } ::= { radiusAccServMIBConformance 1 }
radiusAccServMIBGroups OBJECT IDENTIFIER radiusAccServMIBGroups OBJECT IDENTIFIER
::= { radiusAccServMIBConformance 2 } ::= { radiusAccServMIBConformance 2 }
radiusAccServExtMIBConformance OBJECT IDENTIFIER
::= { radiusAccServExtMIB 2 }
radiusAccServExtMIBCompliances OBJECT IDENTIFIER
::= { radiusAccServExtMIBConformance 1 }
radiusAccServExtMIBGroups OBJECT IDENTIFIER
::= { radiusAccServExtMIBConformance 2 }
-- compliance statements -- compliance statements
radiusAccServMIBCompliance MODULE-COMPLIANCE radiusAccServMIBCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for accounting servers "The compliance statement for accounting servers
implementing the RADIUS Accounting Server MIB." implementing the RADIUS Accounting Server MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusAccServMIBGroup } MANDATORY-GROUPS { radiusAccServMIBGroup }
skipping to change at page 16, line 41 skipping to change at page 16, line 32
DESCRIPTION DESCRIPTION
"The compliance statement for accounting servers "The compliance statement for accounting servers
implementing the RADIUS Accounting Server MIB." implementing the RADIUS Accounting Server MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusAccServExtMIBGroup } MANDATORY-GROUPS { radiusAccServExtMIBGroup }
OBJECT radiusAccServConfigReset OBJECT radiusAccServConfigReset
WRITE-SYNTAX INTEGER { reset(2) } WRITE-SYNTAX INTEGER { reset(2) }
DESCRIPTION "The only SETable value is 'reset' (2)." DESCRIPTION "The only SETable value is 'reset' (2)."
::= { radiusAccServExtMIBCompliances 1 } ::= { radiusAccServMIBCompliances 2 }
-- units of conformance -- units of conformance
radiusAccServMIBGroup OBJECT-GROUP radiusAccServMIBGroup OBJECT-GROUP
OBJECTS {radiusAccServIdent, OBJECTS {radiusAccServIdent,
radiusAccServUpTime, radiusAccServUpTime,
radiusAccServResetTime, radiusAccServResetTime,
radiusAccServConfigReset, radiusAccServConfigReset,
radiusAccServTotalRequests, radiusAccServTotalRequests,
radiusAccServTotalInvalidRequests, radiusAccServTotalInvalidRequests,
skipping to change at page 18, line 12 skipping to change at page 17, line 50
radiusAccServExtResponses, radiusAccServExtResponses,
radiusAccServExtBadAuthenticators, radiusAccServExtBadAuthenticators,
radiusAccServExtMalformedRequests, radiusAccServExtMalformedRequests,
radiusAccServExtNoRecords, radiusAccServExtNoRecords,
radiusAccServExtUnknownTypes radiusAccServExtUnknownTypes
} }
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."
::= { radiusAccServExtMIBGroups 1 } ::= { radiusAccServMIBGroups 2 }
END END
8. IANA Considerations 8. IANA Considerations
This document requires IANA assignment of a number in the MIB-2 OID This document requires no new IANA assignments.
number space.
9. Security Considerations 9. Security Considerations
There are no management objects defined in this MIB that have a MAX- There are no management objects defined in this MIB that have a MAX-
ACCESS clause of read-write and/or read-create. So, if this MIB is ACCESS clause of read-write and/or read-create. So, if this MIB is
implemented correctly, then there is no risk that an intruder can implemented correctly, then there is no risk that an intruder can
alter or create any management objects of this MIB via direct SNMP alter or create any management objects of this MIB via direct SNMP
SET operations. SET operations.
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
 End of changes. 24 change blocks. 
54 lines changed or deleted 46 lines changed or added

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