draft-ietf-radext-rfc2620bis-02.txt   draft-ietf-radext-rfc2620bis-03.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Internet-Draft Enterasys Networks
Obsoletes: RFC 2620 (if approved) January 25, 2006 Obsoletes: RFC 2620 (if approved) May 12, 2006
Expires: July 29, 2006 Expires: November 13, 2006
RADIUS Acct Client MIB (IPv6) RADIUS Acct Client MIB (IPv6)
draft-ietf-radext-rfc2620bis-02.txt draft-ietf-radext-rfc2620bis-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 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
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 . . . . . . . . . . . . . . . . . . . . . 17 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 17 9. Security Considerations . . . . . . . . . . . . . . . . . . . 19
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative References . . . . . . . . . . . . . . . . . . 19 10.1. Normative References . . . . . . . . . . . . . . . . . . 20
10.2. Informative References . . . . . . . . . . . . . . . . . 19 10.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 20 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 21
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 21 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22
Intellectual Property and Copyright Statements . . . . . . . . . . 22 Intellectual Property and Copyright Statements . . . . . . . . . . 23
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 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 fourteen 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
[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,
skipping to change at page 5, line 40 skipping to change at page 5, line 40
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 "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 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.Copyright (C) The
REVISION "200601250000Z" -- 25 Jan 2006 Internet Society (2006). This version of this MIB
DESCRIPTION "Revised version as published in RFC xxxx. module is part of RFC xxxx; see the RFC itself for
This version obsoletes that of RFC 2620 by deprecating the full legal notices."
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
DESCRIPTION "Initial version as published in RFC 2620."
-- 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 "200605100000Z" -- 10 May 2006
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."
-- RFC Editor: replace xxxx with actual RFC number at the time of
-- publication, and remove this note.
REVISION "199906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2620."
::= { 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 }
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2} radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
skipping to change at page 12, line 4 skipping to change at page 12, line 15
radiusAccClientServerInetPortNumber InetPortNumber, radiusAccClientServerInetPortNumber InetPortNumber,
radiusAccClientExtRoundTripTime TimeTicks, radiusAccClientExtRoundTripTime TimeTicks,
radiusAccClientExtRequests Counter32, radiusAccClientExtRequests Counter32,
radiusAccClientExtRetransmissions Counter32, radiusAccClientExtRetransmissions Counter32,
radiusAccClientExtResponses Counter32, radiusAccClientExtResponses Counter32,
radiusAccClientExtMalformedResponses Counter32, radiusAccClientExtMalformedResponses Counter32,
radiusAccClientExtBadAuthenticators Counter32, radiusAccClientExtBadAuthenticators Counter32,
radiusAccClientExtPendingRequests Gauge32, radiusAccClientExtPendingRequests Gauge32,
radiusAccClientExtTimeouts Counter32, radiusAccClientExtTimeouts Counter32,
radiusAccClientExtUnknownTypes Counter32, radiusAccClientExtUnknownTypes Counter32,
radiusAccClientExtPacketsDropped Counter32 radiusAccClientExtPacketsDropped Counter32,
radiusAccClientCounterDiscontinuity TimeTicks
} }
radiusAccServerExtIndex OBJECT-TYPE radiusAccServerExtIndex 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 "A number uniquely identifying each RADIUS
Accounting server with which this client Accounting server with which this client
communicates." communicates."
skipping to change at page 12, line 37 skipping to change at page 12, line 49
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 version neutral IP address format." the version neutral IP address format."
::= { radiusAccServerExtEntry 3 } ::= { radiusAccServerExtEntry 3 }
radiusAccClientServerInetPortNumber OBJECT-TYPE radiusAccClientServerInetPortNumber OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber ( 1..65535 )
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. The value zero (0) is
invalid."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 4 } ::= { radiusAccServerExtEntry 4 }
radiusAccClientExtRoundTripTime OBJECT-TYPE radiusAccClientExtRoundTripTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time interval between the most recent "The time interval between the most recent
Accounting-Response and the Accounting-Request that Accounting-Response and the Accounting-Request that
skipping to change at page 13, line 26 skipping to change at page 13, line 38
-- Responses - MalformedResponses - BadAuthenticators - -- Responses - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received -- UnknownTypes - PacketsDropped = Successfully received
radiusAccClientExtRequests OBJECT-TYPE radiusAccClientExtRequests 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
sent. This does not include retransmissions." sent. This does not include retransmissions.
This counter may experience a discontinuity when the
RADIUS Accounting Client module within the managed
entity is reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 4.1" REFERENCE "RFC 2866 section 4.1"
::= { radiusAccServerExtEntry 6 } ::= { radiusAccServerExtEntry 6 }
radiusAccClientExtRetransmissions OBJECT-TYPE radiusAccClientExtRetransmissions 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
retransmitted to this RADIUS accounting server. retransmitted to this RADIUS accounting server.
Retransmissions include retries where the Retransmissions include retries where the
Identifier and Acct-Delay have been updated, as Identifier and Acct-Delay have been updated, as
well as those in which they remain the same." well as those in which they remain the same.
This counter may experience a discontinuity when the
RADIUS Accounting Client module within the managed
entity is reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 2" REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 7 } ::= { radiusAccServerExtEntry 7 }
radiusAccClientExtResponses OBJECT-TYPE radiusAccClientExtResponses 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 received on the "The number of RADIUS packets received on the
accounting port from this server." accounting port from this server. This counter
may experience a discontinuity when the RADIUS
Accounting Client module within the managed entity is
reinitialized, as indicated by the current value of
radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 4.2" REFERENCE "RFC 2866 section 4.2"
::= { radiusAccServerExtEntry 8 } ::= { radiusAccServerExtEntry 8 }
radiusAccClientExtMalformedResponses OBJECT-TYPE radiusAccClientExtMalformedResponses 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-Response "The number of malformed RADIUS Accounting-Response
packets received from this server. Malformed packets packets received from this server. Malformed packets
include packets with an invalid length. Bad include packets with an invalid length. Bad
authenticators and unknown types are not included as authenticators and unknown types are not included as
malformed accounting responses." malformed accounting responses. This counter may
experience a discontinuity when the RADIUS Accounting
Client module within the managed entity is
reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 9 } ::= { radiusAccServerExtEntry 9 }
radiusAccClientExtBadAuthenticators OBJECT-TYPE radiusAccClientExtBadAuthenticators 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 "The number of RADIUS Accounting-Response
packets which contained invalid authenticators packets which contained invalid authenticators
received from this server." received from this server. This counter may
experience a discontinuity when the RADIUS
Accounting Client module within the managed
entity is reinitialized, as indicated by the
current value of
radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 3" REFERENCE "RFC 2866 section 3"
::= { radiusAccServerExtEntry 10 } ::= { radiusAccServerExtEntry 10 }
radiusAccClientExtPendingRequests OBJECT-TYPE radiusAccClientExtPendingRequests OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
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
sent to this server that have not yet timed out or sent to this server that have not yet timed out or
received a response. This variable is incremented received a response. This variable is incremented
when an Accounting-Request is sent and decremented when an Accounting-Request is sent and decremented
due to receipt of an Accounting-Response, a timeout due to receipt of an Accounting-Response, a timeout
or a retransmission." or a retransmission. This counter may experience a
discontinuity when the RADIUS Accounting Client module
within the managed entity is reinitialized, as
indicated by the current value of
radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 2" REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 11 } ::= { radiusAccServerExtEntry 11 }
radiusAccClientExtTimeouts OBJECT-TYPE radiusAccClientExtTimeouts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "timeouts" UNITS "timeouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of accounting timeouts to this server. "The number of accounting timeouts to this server.
After a timeout the client may retry to the same After a timeout the client may retry to the same
server, send to a different server, or give up. server, send to a different server, or give up.
A retry to the same server is counted as a A retry to the same server is counted as a
retransmit as well as a timeout. A send to a different retransmit as well as a timeout. A send to a different
server is counted as an Accounting-Request as well as server is counted as an Accounting-Request as well as
a timeout." a timeout. This counter may experience a discontinuity
when the RADIUS Accounting Client module within the
managed entity is reinitialized, as indicated by the
current value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 2" REFERENCE "RFC 2866 section 2"
::= { radiusAccServerExtEntry 12 } ::= { radiusAccServerExtEntry 12 }
radiusAccClientExtUnknownTypes OBJECT-TYPE radiusAccClientExtUnknownTypes 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 server on the accounting port." were received from this server on the accounting port.
This counter may experience a discontinuity when the
RADIUS Accounting Client module within the managed
entity is reinitialized, as indicated by the current
value of radiusAccClientCounterDiscontinuity."
REFERENCE "RFC 2866 section 4" REFERENCE "RFC 2866 section 4"
::= { radiusAccServerExtEntry 13 } ::= { radiusAccServerExtEntry 13 }
radiusAccClientExtPacketsDropped OBJECT-TYPE radiusAccClientExtPacketsDropped 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 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. This counter may experience a
discontinuity when the RADIUS Accounting Client module
within the managed entity is reinitialized, as indicated
by the current value of
radiusAccClientCounterDiscontinuity."
::= { radiusAccServerExtEntry 14 } ::= { radiusAccServerExtEntry 14 }
radiusAccClientCounterDiscontinuity 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 Client
counters. A discontinuity may be the result of a
reinitialization of the RADIUS Accounting Client
module within the managed entity."
::= { radiusAccServerExtEntry 15 }
-- conformance information -- conformance information
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 }
skipping to change at page 16, line 28 skipping to change at page 17, line 41
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for accounting "The compliance statement for accounting
clients implementing the RADIUS Accounting clients implementing the RADIUS Accounting
Client IPv6 Extensions MIB. Implementation of Client 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 { radiusAccClientExtMIBGroup } MANDATORY-GROUPS { radiusAccClientExtMIBGroup }
OBJECT radiusAccServerInetAddressType
SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION
"An implementation is only required to support
IPv4 and globally unique IPv6 addresses."
OBJECT radiusAccServerInetAddress
SYNTAX InetAddress ( SIZE (4|16) )
DESCRIPTION
"An implementation is only required to support
IPv4 and globally unique IPv6 addresses."
::= { radiusAccClientMIBCompliances 2 } ::= { 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,
skipping to change at page 17, line 23 skipping to change at page 18, line 49
radiusAccClientServerInetPortNumber, radiusAccClientServerInetPortNumber,
radiusAccClientExtRoundTripTime, radiusAccClientExtRoundTripTime,
radiusAccClientExtRequests, radiusAccClientExtRequests,
radiusAccClientExtRetransmissions, radiusAccClientExtRetransmissions,
radiusAccClientExtResponses, radiusAccClientExtResponses,
radiusAccClientExtMalformedResponses, radiusAccClientExtMalformedResponses,
radiusAccClientExtBadAuthenticators, radiusAccClientExtBadAuthenticators,
radiusAccClientExtPendingRequests, radiusAccClientExtPendingRequests,
radiusAccClientExtTimeouts, radiusAccClientExtTimeouts,
radiusAccClientExtUnknownTypes, radiusAccClientExtUnknownTypes,
radiusAccClientExtPacketsDropped radiusAccClientExtPacketsDropped,
radiusAccClientCounterDiscontinuity
} }
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."
::= { radiusAccClientMIBGroups 2 } ::= { radiusAccClientMIBGroups 2 }
END END
8. IANA Considerations 8. IANA Considerations
skipping to change at page 19, line 10 skipping to change at page 20, line 36
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.
10.2. Informative References
[RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB",
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.
[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. [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
[RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB",
RFC 2620, June 1999.
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. 29 change blocks. 
61 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/