draft-ietf-radext-rfc2621bis-02.txt   draft-ietf-radext-rfc2621bis-03.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Internet-Draft Enterasys Networks
Obsoletes: RFC 2621 (if approved) January 25, 2006 Obsoletes: RFC 2621 (if approved) May 12, 2006
Expires: July 29, 2006 Expires: November 13, 2006
RADIUS Acct Server MIB (IPv6) RADIUS Acct Server MIB (IPv6)
draft-ietf-radext-rfc2621bis-02.txt draft-ietf-radext-rfc2621bis-03.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 July 29, 2006. This Internet-Draft will expire on November 13, 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 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
skipping to change at page 2, line 17 skipping to change at page 2, line 17
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Scope of Changes . . . . . . . . . . . . . . . . . . . . . . . 3 4. Scope of Changes . . . . . . . . . . . . . . . . . . . . . . . 3
5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4
6. Deprecated Objects . . . . . . . . . . . . . . . . . . . . . . 4 6. Deprecated Objects . . . . . . . . . . . . . . . . . . . . . . 4
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
9. Security Considerations . . . . . . . . . . . . . . . . . . . 19 9. Security Considerations . . . . . . . . . . . . . . . . . . . 21
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10.1. Normative References . . . . . . . . . . . . . . . . . . 20 10.1. Normative References . . . . . . . . . . . . . . . . . . 22
10.2. Informative References . . . . . . . . . . . . . . . . . 21 10.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 21 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 23
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 23 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . . . . . 24 Intellectual Property and Copyright Statements . . . . . . . . . . 25
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
This document uses terminology from RFC 2866 [RFC2866]. This document uses terminology from RFC 2866 [RFC2866].
This document uses the word "malformed" with respect to RADIUS This document uses the word "malformed" with respect to RADIUS
skipping to change at page 4, line 43 skipping to change at page 4, line 43
both client and server functions. For example, a RADIUS proxy may both client and server functions. For example, a RADIUS proxy may
act as a server to one or more RADIUS accounting clients, while act as a server to one or more RADIUS accounting clients, while
simultaneously acting as an accounting client to one or more simultaneously acting as an accounting client to one or more
accounting servers. In such situations, it is expected that RADIUS accounting servers. In such situations, it is expected that RADIUS
entities combining client and server functionality will support both entities combining client and server functionality will support both
the client and server MIBs. the client and server MIBs.
This MIB module contains 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 eleven 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.
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,
skipping to change at page 5, line 39 skipping to change at page 5, line 39
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 "200601250000Z" -- 25 Jan 2006 LAST-UPDATED "200605100000Z" -- 10 May 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." Service (RADIUS) accounting protocol. Copyright (C)
REVISION "200601250000Z" -- 25 Jan 2006 The Internet Society (2006). This version of this
DESCRIPTION "Revised version as published in RFC xxxx. MIB module is part of RFC xxxx; see the RFC itself
This version obsoletes that of RFC 2621 by deprecating the forfull legal notices."
MIB table containing IPv4-only address formats and defining
a new table to add support for version neutral IP address -- RFC Editor: replace xxxx with actual RFC number at the time of
formats. The remaining MIB objects from RFC 2621 are carried -- publication, and remove this note.
forward into this version."
REVISION "9906110000Z" -- 11 Jun 1999 REVISION "200605100000Z" -- 10 May 2006
DESCRIPTION "Initial version as published in RFC 2621." 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."
-- 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.
REVISION "199906110000Z" -- 11 Jun 1999
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 14, line 7 skipping to change at page 14, line 16
radiusAccClientInetAddressType InetAddressType, radiusAccClientInetAddressType InetAddressType,
radiusAccClientInetAddress InetAddress, radiusAccClientInetAddress InetAddress,
radiusAccClientExtID SnmpAdminString, radiusAccClientExtID SnmpAdminString,
radiusAccServExtPacketsDropped Counter32, radiusAccServExtPacketsDropped Counter32,
radiusAccServExtRequests Counter32, radiusAccServExtRequests Counter32,
radiusAccServExtDupRequests Counter32, radiusAccServExtDupRequests Counter32,
radiusAccServExtResponses Counter32, radiusAccServExtResponses Counter32,
radiusAccServExtBadAuthenticators Counter32, radiusAccServExtBadAuthenticators Counter32,
radiusAccServExtMalformedRequests Counter32, radiusAccServExtMalformedRequests Counter32,
radiusAccServExtNoRecords Counter32, radiusAccServExtNoRecords Counter32,
radiusAccServExtUnknownTypes Counter32 radiusAccServExtUnknownTypes Counter32,
radiusAccServerCounterDiscontinuity TimeTicks
} }
radiusAccClientExtIndex OBJECT-TYPE radiusAccClientExtIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A number uniquely identifying each RADIUS accounting "A number uniquely identifying each RADIUS accounting
client with which this server communicates." client with which this server communicates."
::= { radiusAccClientExtEntry 1 } ::= { radiusAccClientExtEntry 1 }
skipping to change at page 15, line 15 skipping to change at page 15, line 25
-- --
-- Requests - DupRequests - BadAuthenticators - MalformedRequests - -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - NoRecords = entries logged -- UnknownTypes - PacketsDropped - NoRecords = entries logged
radiusAccServExtPacketsDropped OBJECT-TYPE radiusAccServExtPacketsDropped 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 received "The number of incoming packets received from this
from this client and silently discarded client and silently discarded for a reason other
for a reason other than malformed, bad than malformed, bad authenticators, or unknown types.
authenticators, or unknown types." This counter may experience a discontinuity when the
RADIUS Accounting Server module within the managed
entity is reinitialized, as indicated by the current
value of radiusAccServerCounterDiscontinuity."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccClientExtEntry 5 } ::= { radiusAccClientExtEntry 5 }
radiusAccServExtRequests OBJECT-TYPE radiusAccServExtRequests 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 packets received from this "The number of packets received from this
client on the accounting port." client on the accounting port. This counter
may experience a discontinuity when the
RADIUS Accounting Server module within the
managed entity is reinitialized, as indicated by
the current value of
radiusAccServerCounterDiscontinuity."
REFERENCE "RFC 2866 section 4.1" REFERENCE "RFC 2866 section 4.1"
::= { radiusAccClientExtEntry 6 } ::= { radiusAccClientExtEntry 6 }
radiusAccServExtDupRequests OBJECT-TYPE radiusAccServExtDupRequests 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 duplicate RADIUS Accounting-Request "The number of duplicate RADIUS Accounting-Request
packets received from this client." packets received from this client. This counter
may experience a discontinuity when the RADIUS
Accounting Server module within the managed
entity is reinitialized, as indicated by the
current value of
radiusAccServerCounterDiscontinuity."
REFERENCE "RFC 2866 section 4.1" REFERENCE "RFC 2866 section 4.1"
::= { radiusAccClientExtEntry 7 } ::= { radiusAccClientExtEntry 7 }
radiusAccServExtResponses OBJECT-TYPE radiusAccServExtResponses 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-Response packets "The number of RADIUS Accounting-Response packets
sent to this client." sent to this client. This counter may experience
a discontinuity when the RADIUS Accounting Server
module within the managed entity is reinitialized,
as indicated by the current value of
radiusAccServerCounterDiscontinuity."
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 which contained invalid authenticators received
from this client." from this client. This counter may experience a
discontinuity when the RADIUS Accounting Server
module within the managed entity is reinitialized,
as indicated by the current value of
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 which were received from this client.
Bad authenticators and unknown types Bad authenticators and unknown types are not
are not included as malformed Accounting-Requests." included as malformed Accounting-Requests. This
counter may experience a discontinuity when the
RADIUS Accounting Server module within the managed
entity is reinitialized, as indicated by the current
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 which were received and responded to but not
recorded." recorded. This counter may experience a
discontinuity when the RADIUS Accounting Server
module within the managed entity is reinitialized,
as indicated by the current value of
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 which
were received from this client." were received from this client. This counter may
experience a discontinuity when the RADIUS Accounting
Server module within the managed entity is
reinitialized, as indicated by the current value of
radiusAccServerCounterDiscontinuity."
REFERENCE "RFC 2866 section 4" REFERENCE "RFC 2866 section 4"
::= { radiusAccClientExtEntry 12 } ::= { radiusAccClientExtEntry 12 }
radiusAccServerCounterDiscontinuity OBJECT-TYPE
SYNTAX TimeTicks
UNITS "centiseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of centiseconds since the last
discontinuity in the RADIUS Accounting Server
counters. A discontinuity may be the result of
a reinitialization of the RADIUS Accounting Server
module within the managed entity."
::= { radiusAccClientExtEntry 13 }
-- 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 }
skipping to change at page 18, line 6 skipping to change at page 19, line 13
Server IPv6 Extensions MIB. Implementation of Server IPv6 Extensions MIB. Implementation of
this module is for entities that support IPv6, this module is for entities that support IPv6,
or support IPv4 and IPv6." or support IPv4 and IPv6."
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)."
OBJECT radiusAccClientInetAddressType
SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION
"An implementation is only required to support
IPv4 and globally unique IPv6 addresses."
OBJECT radiusAccClientInetAddress
SYNTAX InetAddress ( SIZE (4|16) )
DESCRIPTION
"An implementation is only required to support
IPv4 and globally unique IPv6 addresses."
::= { radiusAccServMIBCompliances 2 } ::= { 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,
skipping to change at page 19, line 18 skipping to change at page 20, line 37
radiusAccClientInetAddressType, radiusAccClientInetAddressType,
radiusAccClientInetAddress, radiusAccClientInetAddress,
radiusAccClientExtID, radiusAccClientExtID,
radiusAccServExtPacketsDropped, radiusAccServExtPacketsDropped,
radiusAccServExtRequests, radiusAccServExtRequests,
radiusAccServExtDupRequests, radiusAccServExtDupRequests,
radiusAccServExtResponses, radiusAccServExtResponses,
radiusAccServExtBadAuthenticators, radiusAccServExtBadAuthenticators,
radiusAccServExtMalformedRequests, radiusAccServExtMalformedRequests,
radiusAccServExtNoRecords, radiusAccServExtNoRecords,
radiusAccServExtUnknownTypes radiusAccServExtUnknownTypes,
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. IANA Considerations
skipping to change at page 20, line 48 skipping to change at page 22, line 21
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 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[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.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002.
[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
[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,
"Introduction and Applicability Statements for Internet-
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 and Greg Weber. 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
 End of changes. 25 change blocks. 
65 lines changed or deleted 117 lines changed or added

This html diff was produced by rfcdiff 1.31. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/