draft-ietf-radext-rfc2620bis-00.txt   draft-ietf-radext-rfc2620bis-01.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Internet-Draft Enterasys Networks
Updates: RFC 2620 (if approved) August 30, 2005 Obsoletes: RFC 2620 (if approved) October 18, 2005
Expires: March 3, 2006 Expires: April 21, 2006
RADIUS Acct Client MIB (IPv6) RADIUS Acct Client MIB (IPv6)
draft-ietf-radext-rfc2620bis-00.txt draft-ietf-radext-rfc2620bis-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 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. version neutral IP address formats. The remaining MIB objects from
RFC 2620 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 . . . . . . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.1. Normative References . . . . . . . . . . . . . . . . . . 17 10.1. Normative References . . . . . . . . . . . . . . . . . . 17
10.2. Informative References . . . . . . . . . . . . . . . . . 18 10.2. Informative References . . . . . . . . . . . . . . . . . 18
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 18 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 20 Intellectual Property and Copyright Statements . . . . . . . . . . 20
1. Terminology 1. Terminology
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 2620 [RFC2620], RADIUS Authentication This document obsoletes RFC 2620 [RFC2620], RADIUS Authentication
Client MIB, by deprecating the radiusAuthServerTable table and adding Client MIB, by deprecating the radiusAuthServerTable table and adding
a new table, radiusAuthServerExtTable, containing a new table, radiusAuthServerExtTable, containing
radiusAuthServerInetAddressType, radiusAuthServerInetAddress, and radiusAuthServerInetAddressType, radiusAuthServerInetAddress, and
radiusAuthClientServerInetPortNumber. The purpose of these added MIB radiusAuthClientServerInetPortNumber. The purpose of these added MIB
objects is to support version neutral IP addressing formats. The objects is to support version neutral IP addressing formats. The
existing table containing radiusAuthServerAddress and existing table containing radiusAuthServerAddress and
radiusAuthClientServerPortNumber is deprecated. radiusAuthClientServerPortNumber is deprecated. The remaining MIB
objects from RFC 2620 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
IPv6 addresses, contains the following recommendation. IPv6 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 Authentication distinguishes between the client function and the server function.
Client MIB, RFC 2620 [RFC2620]. This MIB module contains two scalars In RADIUS accounting, clients send Accounting-Requests, and servers
as well as a single table, the RADIUS Accounting Server Table, which reply with Accounting-Responses. Typically NAS devices implement the
contains one row for each RADIUS server with which the client shares client function, and thus would be expected to implement the RADIUS
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 Server Table includes fifteen However, it is possible for a RADIUS accounting entity to perform
columns presenting a view of the activity of the RADIUS client. both client and server functions. For example, a RADIUS proxy may
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 two scalars as well as a single table, the
RADIUS Accounting Server Table, which contains one row for each
RADIUS server with which the client shares a secret. Each entry in
the RADIUS Accounting Server Table includes fifteen columns
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
skipping to change at page 5, line 14 skipping to change at page 5, line 26
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 "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 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
DESCRIPTION "Revised version as published in RFC xxxx.
This version obsoletes that of RFC 2620 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 2620 are carried
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"
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 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."
::= { mib-2 67 } ::= { mib-2 67 }
radiusAccClientExtMIB 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}
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
skipping to change at page 10, line 21 skipping to change at page 10, line 28
radiusAccClientPacketsDropped OBJECT-TYPE radiusAccClientPacketsDropped 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 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 }
-- Extended MIB Objects -- New MIB objects added in this revision
radiusAccClientExtMIBObjects OBJECT IDENTIFIER
::= { radiusAccClientExtMIB 1 }
radiusAccClientExt OBJECT IDENTIFIER
::= { radiusAccClientExtMIBObjects 1 }
radiusAccServerExtTable OBJECT-TYPE radiusAccServerExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccServerExtEntry SYNTAX SEQUENCE OF RadiusAccServerExtEntry
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
servers with which the client shares a secret." servers with which the client shares a secret."
::= { radiusAccClientExt 1 } ::= { radiusAccClient 4 }
radiusAccServerExtEntry OBJECT-TYPE radiusAccServerExtEntry OBJECT-TYPE
SYNTAX RadiusAccServerExtEntry SYNTAX RadiusAccServerExtEntry
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 server with which the client shares a accounting server with which the client shares a
secret." secret."
INDEX { radiusAccServerExtIndex } INDEX { radiusAccServerExtIndex }
skipping to change at page 11, line 46 skipping to change at page 11, line 46
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 IPv6 adddess format." the version neutral IP adddess 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."
::= { radiusAccServerExtEntry 4 } ::= { radiusAccServerExtEntry 4 }
skipping to change at page 14, line 43 skipping to change at page 14, line 43
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 }
radiusAccClientExtMIBConformance OBJECT IDENTIFIER
::= { radiusAccClientExtMIB 2 }
radiusAccClientExtMIBCompliances OBJECT IDENTIFIER
::= { radiusAccClientExtMIBConformance 1 }
radiusAccClientExtMIBGroups OBJECT IDENTIFIER
::= { radiusAccClientExtMIBConformance 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."
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 clients
implementing the RADIUS Accounting Client MIB." implementing the RADIUS Accounting Client MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusAccClientExtMIBGroup } MANDATORY-GROUPS { radiusAccClientExtMIBGroup }
::= { radiusAccClientExtMIBCompliances 1 } ::= { radiusAccClientMIBCompliances 2 }
-- units of conformance -- units of conformance
radiusAccClientMIBGroup OBJECT-GROUP radiusAccClientMIBGroup OBJECT-GROUP
OBJECTS { radiusAccClientIdentifier, OBJECTS { radiusAccClientIdentifier,
radiusAccClientInvalidServerAddresses, radiusAccClientInvalidServerAddresses,
radiusAccServerAddress, radiusAccServerAddress,
radiusAccClientServerPortNumber, radiusAccClientServerPortNumber,
radiusAccClientRoundTripTime, radiusAccClientRoundTripTime,
radiusAccClientRequests, radiusAccClientRequests,
skipping to change at page 16, line 4 skipping to change at page 15, line 43
radiusAccClientPendingRequests, radiusAccClientPendingRequests,
radiusAccClientTimeouts, radiusAccClientTimeouts,
radiusAccClientUnknownTypes, radiusAccClientUnknownTypes,
radiusAccClientPacketsDropped radiusAccClientPacketsDropped
} }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The basic collection of objects providing management of "The basic collection of objects providing management of
RADIUS Accounting Clients." RADIUS Accounting Clients."
::= { radiusAccClientMIBGroups 1 } ::= { radiusAccClientMIBGroups 1 }
radiusAccClientExtMIBGroup OBJECT-GROUP radiusAccClientExtMIBGroup OBJECT-GROUP
OBJECTS { radiusAccClientIdentifier, OBJECTS { radiusAccClientIdentifier,
radiusAccClientInvalidServerAddresses, radiusAccClientInvalidServerAddresses,
radiusAccServerInetAddressType, radiusAccServerInetAddressType,
radiusAccServerInetAddress, radiusAccServerInetAddress,
radiusAccClientExtServerInetPortNumber, radiusAccClientServerInetPortNumber,
radiusAccClientExtRoundTripTime, radiusAccClientExtRoundTripTime,
radiusAccClientExtRequests, radiusAccClientExtRequests,
radiusAccClientExtRetransmissions, radiusAccClientExtRetransmissions,
radiusAccClientExtResponses, radiusAccClientExtResponses,
radiusAccClientExtMalformedResponses, radiusAccClientExtMalformedResponses,
radiusAccClientExtBadAuthenticators, radiusAccClientExtBadAuthenticators,
radiusAccClientExtPendingRequests, radiusAccClientExtPendingRequests,
radiusAccClientExtTimeouts, radiusAccClientExtTimeouts,
radiusAccClientExtUnknownTypes, radiusAccClientExtUnknownTypes,
radiusAccClientExtPacketsDropped radiusAccClientExtPacketsDropped
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The basic collection of objects providing management of "The basic collection of objects providing management of
RADIUS Accounting Clients." RADIUS Accounting Clients."
::= { radiusAccClientExtMIBGroups 1 } ::= { radiusAccClientMIBGroups 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. 23 change blocks. 
51 lines changed or deleted 48 lines changed or added

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