< draft-ietf-radext-rfc2620bis-03.txt   draft-ietf-radext-rfc2620bis-04.txt >
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Internet-Draft Enterasys Networks
Obsoletes: RFC 2620 (if approved) May 12, 2006 Obsoletes: RFC 2620 (if approved) June 26, 2006
Expires: November 13, 2006 Expires: December 28, 2006
RADIUS Acct Client MIB (IPv6) RADIUS Accounting Client MIB for IPv6
draft-ietf-radext-rfc2620bis-03.txt draft-ietf-radext-rfc2620bis-04.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 November 13, 2006. This Internet-Draft will expire on December 28, 2006.
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, which instrument RADIUS
accounting client functions. These extensions represent a portion of accounting client 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 IP-based
management stations can manage RADIUS accounting clients. 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. This memo also adds RFC 2620 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. 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 . . . . . . . . . . . . . . . . . . . . . . 5
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative References . . . . . . . . . . . . . . . . . . 20 10.1. Normative References . . . . . . . . . . . . . . . . . . 20
10.2. Informative References . . . . . . . . . . . . . . . . . 21 10.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 21 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 21
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22
Intellectual Property and Copyright Statements . . . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . . . 23
skipping to change at page 4, line 38 skipping to change at page 4, line 38
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 client and server MIBs. The client MIB is defined in this
document, and the server MIB is defined in [2621bis].
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 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 fifteen 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
skipping to change at page 5, line 28 skipping to change at page 5, line 33
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 server, the row table that describe the same RADIUS accounting server, 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-ACCT-CLIENT-MIB DEFINITIONS ::= BEGIN RADIUS-ACC-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;
skipping to change at page 21, line 5 skipping to change at page 21, line 8
[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.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
10.2. Informative References 10.2. Informative References
[2621bis] Nelson, D., "RADIUS Accounting Server MIB for IPv6",
draft-ietf-radext-rfc2621bis-04.txt (work in progress),
June 2006.
[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.
[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.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
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, 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
 End of changes. 10 change blocks. 
13 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/