draft-ietf-radext-rfc2621bis-01.txt   draft-ietf-radext-rfc2621bis-02.txt 
Network Working Group D. Nelson Network Working Group D. Nelson
Internet-Draft Enterasys Networks Internet-Draft Enterasys Networks
Obsoletes: RFC 2621 (if approved) October 18, 2005 Obsoletes: RFC 2621 (if approved) January 25, 2006
Expires: April 21, 2006 Expires: July 29, 2006
RADIUS Acct Server MIB (IPv6) RADIUS Acct Server MIB (IPv6)
draft-ietf-radext-rfc2621bis-01.txt draft-ietf-radext-rfc2621bis-02.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 April 21, 2006. This Internet-Draft will expire on July 29, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a set of extensions which instrument RADIUS
accounting server functions. These extensions represent a portion of
the Management Information Base (MIB) for use with network management
protocols in the Internet community. Using these extensions IP-based
management stations can manage RADIUS accounting servers.
This memo obsoletes RFC 2621 by deprecating the MIB table containing This memo obsoletes RFC 2621 by deprecating the MIB table containing
IPv4-only address formats and defining a new table to add support for IPv4-only address formats and defining a new table to add support for
version neutral IP address formats. The remaining MIB objects from version neutral IP address formats. The remaining MIB objects from
RFC 2621 are carried forward into this document. RFC 2621 are carried forward into this document. This memo also adds
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 . . . . . . . . . . . . . . . . . . . . . . 4
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 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 . . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . . . 22 Intellectual Property and Copyright Statements . . . . . . . . . . 24
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
packets, particularly in the context of counters of "malformed
packets". While RFC 2866 does not provide an explicit definition of
"malformed", malformed generally means that the implementation has
determined the packet does not match the format defined in RFC 2866.
Those implementations are used in deployments today, and thus set the
de-facto definition of "malformed".
2. Introduction 2. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
The objects defined within this memo relate to the Remote The objects defined within this memo relate to the Remote
Authentication Dial-In User Service (RADIUS) Accounting Server as Authentication Dial-In User Service (RADIUS) Accounting Server as
defined in RFC 2866 [RFC2866]. defined in RFC 2866 [RFC2866].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
skipping to change at page 3, line 45 skipping to change at page 4, line 7
4. Scope of Changes 4. Scope of Changes
This document obsoletes RFC 2621 [RFC2621], RADIUS Accounting Server This document obsoletes RFC 2621 [RFC2621], RADIUS Accounting Server
MIB, by deprecating the radiusAccClientTable table and adding a new MIB, by deprecating the radiusAccClientTable table and adding a new
table, radiusAccClientExtTable, containing table, radiusAccClientExtTable, containing
radiusAccClientInetAddressType and radiusAccClientInetAddress. The radiusAccClientInetAddressType and radiusAccClientInetAddress. The
purpose of these added MIB objects is to support version neutral IP purpose of these added MIB objects is to support version neutral IP
addressing formats. The existing table containing addressing formats. The existing table containing
radiusAccClientAddress is deprecated. The remaining MIB objects from radiusAccClientAddress is deprecated. The remaining MIB objects from
RFC 2621 are carried forward into this document. RFC 2621 are carried forward into this document. This memo also adds
UNITS and REFERENCE clauses to selected objects.
RFC 4001 [RFC4001], which defines the SMI Textual Conventions for RFC 4001 [RFC4001], which defines the SMI Textual Conventions for
version neutral IP addresses, contains the following recommendation. version neutral IP addresses, contains the following recommendation.
'In particular, when revising a MIB module that contains IPv4 'In particular, when revising a MIB module that contains IPv4
specific tables, it is suggested to define new tables using the specific tables, it is suggested to define new tables using the
textual conventions defined in this memo [RFC 4001] that support all textual conventions defined in this memo [RFC 4001] that support all
versions of IP. The status of the new tables SHOULD be "current", versions of IP. The status of the new tables SHOULD be "current",
whereas the status of the old IP version specific tables SHOULD be whereas the status of the old IP version specific tables SHOULD be
changed to "deprecated". The other approach, of having multiple changed to "deprecated". The other approach, of having multiple
similar tables for different IP versions, is strongly discouraged.' similar tables for different IP versions, is strongly discouraged.'
5. Structure of the MIB Module 5. Structure of the MIB Module
The RADIUS accounting protocol, described in RFC 2866 [RFC2866], The RADIUS accounting protocol, described in RFC 2866 [RFC2866],
distinguishes between the client function and the server function. distinguishes between the client function and the server function.
In RADIUS accounting, clients send Accounting-Requests, and servers In RADIUS accounting, clients send Accounting-Requests, and servers
reply with Accounting-Responses. Typically NAS devices implement the reply with Accounting-Responses. Typically Network Access Server
client function, and thus would be expected to implement the RADIUS (NAS) devices implement the client function, and thus would be
accounting client MIB, while RADIUS accounting servers implement the expected to implement the RADIUS accounting client MIB, while RADIUS
server function, and thus would be expected to implement the RADIUS accounting servers implement the server function, and thus would be
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.
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 twelve columns entry in the RADIUS Accounting Client Table includes eleven 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,
and the deprecated table is supported for backwards compatibility and the deprecated table is supported for backwards compatibility
with older management stations. This option SHOULD only be used with older management stations. This option SHOULD only be used
when the IP addresses in the new table are in IPv4 format and can when the IP addresses in the new table are in IPv4 format and can
accurately be represented in both the new table and the accurately be represented in both the new table and the
deprecated table. deprecated table.
Managed entities SHOULD NOT instantiate the deprecated table Managed entities SHOULD NOT instantiate row entries in the deprecated
containing IPv4-only address objects when the RADIUS server address table, containing IPv4-only address objects, when the RADIUS
represented in the table row is not an IPv4 address. Managed accounting client address represented in such a table row is not an
entities SHOULD NOT return inaccurate values of IP address or SNMP IPv4 address. Managed entities SHOULD NOT return inaccurate values
object access errors for IPv4-only address objects in otherwise of IP address or SNMP object access errors for IPv4-only address
populated tables. objects in otherwise populated tables. When row entries exist in
both the deprecated IPv4-only table and the new IP version neutral
table that describe the same RADIUS accounting client, the row
indexes SHOULD be the same for the corresponding rows in each table,
to facilitate correlation of these related rows by management
applications.
7. Definitions 7. Definitions
RADIUS-ACCT-SERVER-MIB DEFINITIONS ::= BEGIN RADIUS-ACCT-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Integer32, Counter32, Integer32,
IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InetAddressType, InetAddress FROM INET-ADDRESS-MIB InetAddressType, InetAddress FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
radiusAccServMIB MODULE-IDENTITY radiusAccServMIB MODULE-IDENTITY
LAST-UPDATED "200510170000Z" -- 17 Oct 2005 LAST-UPDATED "200601250000Z" -- 25 Jan 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."
REVISION "200510170000Z" -- 17 Oct 2005 REVISION "200601250000Z" -- 25 Jan 2006
DESCRIPTION "Revised version as published in RFC xxxx. DESCRIPTION "Revised version as published in RFC xxxx.
This version obsoletes that of RFC 2621 by deprecating the This version obsoletes that of RFC 2621 by deprecating the
MIB table containing IPv4-only address formats and defining MIB table containing IPv4-only address formats and defining
a new table to add support for version neutral IP address a new table to add support for version neutral IP address
formats. The remaining MIB objects from RFC 2621 are carried formats. The remaining MIB objects from RFC 2621 are carried
forward into this version." forward into this version."
REVISION "9906110000Z" -- 11 Jun 1999 REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2621" DESCRIPTION "Initial version as published in RFC 2621."
-- RFC Editor: replace xxxx with actual RFC number at the time of -- RFC Editor: replace xxxx with actual RFC number at the time of
-- publication, and remove this note. -- publication, and remove this note.
::= { radiusAccounting 1 } ::= { radiusAccounting 1 }
radiusMIB OBJECT-IDENTITY radiusMIB OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA." "The OID assigned to RADIUS MIB work by the IANA."
skipping to change at page 7, line 31 skipping to change at page 7, line 46
if the server had just been started. This value will if the server had just been started. This value will
never be returned by a read operation. When read, never be returned by a read operation. When read,
one of the following values will be returned: one of the following values will be returned:
other(1) - server in some unknown state; other(1) - server in some unknown state;
initializing(3) - server (re)initializing; initializing(3) - server (re)initializing;
running(4) - server currently running." running(4) - server currently running."
::= {radiusAccServ 4} ::= {radiusAccServ 4}
radiusAccServTotalRequests OBJECT-TYPE radiusAccServTotalRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets received on the "The number of packets received on the
accounting port." accounting port."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccServ 5 } ::= { radiusAccServ 5 }
radiusAccServTotalInvalidRequests OBJECT-TYPE radiusAccServTotalInvalidRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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
received from unknown addresses." received from unknown addresses."
REFERENCE "RFC 2866 sections 2, 4.1"
::= { radiusAccServ 6 } ::= { radiusAccServ 6 }
radiusAccServTotalDupRequests OBJECT-TYPE radiusAccServTotalDupRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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." packets received."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccServ 7 } ::= { radiusAccServ 7 }
radiusAccServTotalResponses OBJECT-TYPE radiusAccServTotalResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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." sent."
REFERENCE "RFC 2866 section 4.2"
::= { radiusAccServ 8 } ::= { radiusAccServ 8 }
radiusAccServTotalMalformedRequests OBJECT-TYPE radiusAccServTotalMalformedRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 received. Bad authenticators or unknown packets received. Bad authenticators or unknown
types are not included as malformed Access-Requests." types are not included as malformed Access-Requests."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServ 9 } ::= { radiusAccServ 9 }
radiusAccServTotalBadAuthenticators OBJECT-TYPE radiusAccServTotalBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 Signature attributes." which contained an invalid authenticator."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServ 10 } ::= { radiusAccServ 10 }
radiusAccServTotalPacketsDropped OBJECT-TYPE radiusAccServTotalPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of incoming packets silently discarded "The number of incoming packets silently discarded
for a reason other than malformed, bad authenticators, for a reason other than malformed, bad authenticators,
or unknown types." or unknown types."
REFERENCE "RFC 2866 section 3"
::= { radiusAccServ 11 } ::= { radiusAccServ 11 }
radiusAccServTotalNoRecords OBJECT-TYPE radiusAccServTotalNoRecords OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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."
::= { radiusAccServ 12 } ::= { radiusAccServ 12 }
radiusAccServTotalUnknownTypes OBJECT-TYPE radiusAccServTotalUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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." were received."
REFERENCE "RFC 2866 section 4"
::= { radiusAccServ 13 } ::= { radiusAccServ 13 }
radiusAccClientTable OBJECT-TYPE radiusAccClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccClientEntry SYNTAX SEQUENCE OF RadiusAccClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS accounting "The (conceptual) table listing the RADIUS accounting
clients with which the server shares a secret." clients with which the server shares a secret."
::= { radiusAccServ 14 } ::= { radiusAccServ 14 }
skipping to change at page 10, line 20 skipping to change at page 11, line 4
::= { radiusAccClientEntry 1 } ::= { radiusAccClientEntry 1 }
radiusAccClientAddress OBJECT-TYPE radiusAccClientAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The NAS-IP-Address of the RADIUS accounting client "The NAS-IP-Address of the RADIUS accounting client
referred to in this table entry." referred to in this table entry."
::= { radiusAccClientEntry 2 } ::= { radiusAccClientEntry 2 }
radiusAccClientID OBJECT-TYPE radiusAccClientID OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The NAS-Identifier of the RADIUS accounting client "The NAS-Identifier of the RADIUS accounting client
referred to in this table entry. This is not referred to in this table entry. This is not
necessarily the same as sysName in MIB II." necessarily the same as sysName in MIB II."
REFERENCE "RFC 2865 section 5.32"
::= { radiusAccClientEntry 3 } ::= { radiusAccClientEntry 3 }
-- Server Counters -- Server Counters
-- --
-- Requests - DupRequests - BadAuthenticators - MalformedRequests - -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - Responses = Pending -- UnknownTypes - PacketsDropped - Responses = Pending
-- --
-- Requests - DupRequests - BadAuthenticators - MalformedRequests - -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - NoRecords = entries logged -- UnknownTypes - PacketsDropped - NoRecords = entries logged
radiusAccServPacketsDropped OBJECT-TYPE radiusAccServPacketsDropped OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of incoming packets received "The number of incoming packets received
from this client and silently discarded from this client and silently discarded
for a reason other than malformed, bad for a reason other than malformed, bad
authenticators, or unknown types." authenticators, or unknown types."
REFERENCE "RFC 2866 section 3"
::= { radiusAccClientEntry 4 } ::= { radiusAccClientEntry 4 }
radiusAccServRequests OBJECT-TYPE radiusAccServRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
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."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccClientEntry 5 } ::= { radiusAccClientEntry 5 }
radiusAccServDupRequests OBJECT-TYPE radiusAccServDupRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
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."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccClientEntry 6 } ::= { radiusAccClientEntry 6 }
radiusAccServResponses OBJECT-TYPE radiusAccServResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS Accounting-Response packets "The number of RADIUS Accounting-Response packets
sent to this client." sent to this client."
REFERENCE "RFC 2866 section 4.2"
::= { radiusAccClientEntry 7 } ::= { radiusAccClientEntry 7 }
radiusAccServBadAuthenticators OBJECT-TYPE radiusAccServBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
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."
REFERENCE "RFC 2866 section 3"
::= { radiusAccClientEntry 8 } ::= { radiusAccClientEntry 8 }
radiusAccServMalformedRequests OBJECT-TYPE radiusAccServMalformedRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
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 included as malformed Accounting-Requests." are not included as malformed Accounting-Requests."
REFERENCE "RFC 2866 section 3"
::= { radiusAccClientEntry 9 } ::= { radiusAccClientEntry 9 }
radiusAccServNoRecords OBJECT-TYPE radiusAccServNoRecords OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
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."
::= { radiusAccClientEntry 10 } ::= { radiusAccClientEntry 10 }
radiusAccServUnknownTypes OBJECT-TYPE radiusAccServUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "packets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The number of RADIUS packets of unknown type which "The number of RADIUS packets of unknown type which
were received from this client." were received from this client."
REFERENCE "RFC 2866 section 4"
::= { radiusAccClientEntry 11 } ::= { radiusAccClientEntry 11 }
-- New MIB objects added in this revision -- New MIB objects added in this revision
radiusAccClientExtTable OBJECT-TYPE radiusAccClientExtTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccClientExtEntry SYNTAX SEQUENCE OF RadiusAccClientExtEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS accounting "The (conceptual) table listing the RADIUS accounting
skipping to change at page 13, line 36 skipping to change at page 14, line 35
radiusAccClientInetAddress object." radiusAccClientInetAddress object."
::= { radiusAccClientExtEntry 2 } ::= { radiusAccClientExtEntry 2 }
radiusAccClientInetAddress OBJECT-TYPE radiusAccClientInetAddress 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
client referred to in this table entry, using client referred to in this table entry, using
the IPv6 adddess format." the IPv6 address format."
::= { radiusAccClientExtEntry 3 } ::= { radiusAccClientExtEntry 3 }
radiusAccClientExtID OBJECT-TYPE radiusAccClientExtID OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The NAS-Identifier of the RADIUS accounting client "The NAS-Identifier of the RADIUS accounting client
referred to in this table entry. This is not referred to in this table entry. This is not
necessarily the same as sysName in MIB II." necessarily the same as sysName in MIB II."
REFERENCE "RFC 2865 section 5.32"
::= { radiusAccClientExtEntry 4 } ::= { radiusAccClientExtEntry 4 }
-- Server Counters -- Server Counters
-- --
-- Requests - DupRequests - BadAuthenticators - MalformedRequests - -- Requests - DupRequests - BadAuthenticators - MalformedRequests -
-- UnknownTypes - PacketsDropped - Responses = Pending -- UnknownTypes - PacketsDropped - Responses = Pending
-- --
-- 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"
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 client and silently discarded from this client and silently discarded
for a reason other than malformed, bad for a reason other than malformed, bad
authenticators, or unknown types." authenticators, or unknown types."
REFERENCE "RFC 2866 section 3"
::= { radiusAccClientExtEntry 5 } ::= { radiusAccClientExtEntry 5 }
radiusAccServExtRequests OBJECT-TYPE radiusAccServExtRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccClientExtEntry 6 } ::= { radiusAccClientExtEntry 6 }
radiusAccServExtDupRequests OBJECT-TYPE radiusAccServExtDupRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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."
REFERENCE "RFC 2866 section 4.1"
::= { radiusAccClientExtEntry 7 } ::= { radiusAccClientExtEntry 7 }
radiusAccServExtResponses OBJECT-TYPE radiusAccServExtResponses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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."
REFERENCE "RFC 2866 section 4.2"
::= { radiusAccClientExtEntry 8 } ::= { radiusAccClientExtEntry 8 }
radiusAccServExtBadAuthenticators OBJECT-TYPE radiusAccServExtBadAuthenticators OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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."
REFERENCE "RFC 2866 section 3"
::= { radiusAccClientExtEntry 9 } ::= { radiusAccClientExtEntry 9 }
radiusAccServExtMalformedRequests OBJECT-TYPE radiusAccServExtMalformedRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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 included as malformed Accounting-Requests." are not included as malformed Accounting-Requests."
REFERENCE "RFC 2866 section 3"
::= { radiusAccClientExtEntry 10 } ::= { radiusAccClientExtEntry 10 }
radiusAccServExtNoRecords OBJECT-TYPE radiusAccServExtNoRecords OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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."
::= { radiusAccClientExtEntry 11 } ::= { radiusAccClientExtEntry 11 }
radiusAccServExtUnknownTypes OBJECT-TYPE radiusAccServExtUnknownTypes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
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."
REFERENCE "RFC 2866 section 4"
::= { radiusAccClientExtEntry 12 } ::= { radiusAccClientExtEntry 12 }
-- conformance information -- conformance information
radiusAccServMIBConformance OBJECT IDENTIFIER radiusAccServMIBConformance OBJECT IDENTIFIER
::= { radiusAccServMIB 2 } ::= { radiusAccServMIB 2 }
radiusAccServMIBCompliances OBJECT IDENTIFIER radiusAccServMIBCompliances OBJECT IDENTIFIER
::= { radiusAccServMIBConformance 1 } ::= { radiusAccServMIBConformance 1 }
skipping to change at page 16, line 4 skipping to change at page 17, line 16
-- 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 }
-- compliance statements -- compliance statements
radiusAccServMIBCompliance MODULE-COMPLIANCE radiusAccServMIBCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for accounting servers "The compliance statement for accounting servers
implementing the RADIUS Accounting Server MIB." implementing the RADIUS Accounting Server MIB.
Implementation of this module is for IPv4-only
entities, or for backwards compatibility use with
entities that support both IPv4 and IPv6."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusAccServMIBGroup } MANDATORY-GROUPS { radiusAccServMIBGroup }
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)."
::= { radiusAccServMIBCompliances 1 } ::= { radiusAccServMIBCompliances 1 }
radiusAccServExtMIBCompliance MODULE-COMPLIANCE radiusAccServExtMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for accounting servers "The compliance statement for accounting
implementing the RADIUS Accounting Server MIB." servers implementing the RADIUS Accounting
Server IPv6 Extensions MIB. Implementation of
this module is for entities that support 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)."
::= { radiusAccServMIBCompliances 2 } ::= { radiusAccServMIBCompliances 2 }
-- units of conformance -- units of conformance
skipping to change at page 18, line 4 skipping to change at page 19, line 25
radiusAccServExtBadAuthenticators, radiusAccServExtBadAuthenticators,
radiusAccServExtMalformedRequests, radiusAccServExtMalformedRequests,
radiusAccServExtNoRecords, radiusAccServExtNoRecords,
radiusAccServExtUnknownTypes radiusAccServExtUnknownTypes
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects providing management of "The collection of objects providing management of
a RADIUS Accounting Server." a RADIUS Accounting Server."
::= { radiusAccServMIBGroups 2 } ::= { radiusAccServMIBGroups 2 }
END END
8. IANA Considerations 8. IANA Considerations
This document requires no new IANA assignments. This document requires no new IANA assignments.
9. Security Considerations 9. Security Considerations
There are no management objects defined in this MIB that have a MAX- There are management objects (radiusAccServConfigReset) defined in
ACCESS clause of read-write and/or read-create. So, if this MIB is this MIB that have a MAX-ACCESS clause of read-write and/or read-
implemented correctly, then there is no risk that an intruder can create. Such objects may be considered sensitive or vulnerable in
alter or create any management objects of this MIB via direct SNMP some network environments. The support for SET operations in a non-
SET operations. secure environment without proper protection can have a negative
effect on network operations. These are:
radiusAccServConfigReset This object can be used to reinitialize the
persistent state of any server. When set to reset(2), any
persistent server state (such as a process) is reinitialized as if
the server had just been started. Depending on the server
impelmentation details, this action may or may not interrupt the
processing of pending request in the server. Abuse of this object
may lead to a Denial of Service attack on the server.
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
sensitive information. These are: sensitive information. These are:
radiusAccClientIPAddress This can be used to determine the address of radiusAccClientIPAddress This can be used to determine the address of
the RADIUS accounting client with which the server is the RADIUS accounting client with which the server is
communicating. This information could be useful in mounting an communicating. This information could be useful in mounting an
attack on the accounting client. attack on the accounting client.
radiusAccClientInetAddress This can be used to determine the address radiusAccClientInetAddress This can be used to determine the address
of the RADIUS accounting client with which the server is of the RADIUS accounting client with which the server is
communicating. This information could be useful in mounting an communicating. This information could be useful in mounting an
attack on the accounting client. attack on the accounting client.
It is thus important to control even GET access to these objects and It is thus important to control even GET access to these objects and
possibly to even encrypt the values of these object when sending them possibly to even encrypt the values of these object when sending them
over the network via SNMP. Not all versions of SNMP provide features over the network via SNMP. Not all versions of SNMP provide features
for such a secure environment. for such a secure environment.
SNMP versions prior to SNMPv3 do not provide a secure environment. SNMP versions prior to SNMPv3 do not provide a secure environment.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPsec),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB. MIB.
It is recommended that the implementers consider the security It is RECOMMENDED that implementers consider the security features as
features as provided by the SNMPv3 framework. Specifically, the use provided by the SNMPv3 framework (see [RFC3410], section 8),
of the User-based Security Model [RFC2574] and the View-based Access including full support for the SNMPv3 cryptographic mechanisms (for
Control Model [RFC2575] is recommended. Using these security authentication and privacy).
features, customer/users can give access to the objects only to those
principals (users) that have legitimate rights to GET or SET (change/ Further, deployment of SNMP versions prior to SNMPv3 is NOT
create/delete) them. RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
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 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
skipping to change at page 19, line 32 skipping to change at page 21, line 21
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.
[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 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)", STD 62, Simple Network Management Protocol (SNMP)", STD 62,
RFC 3418, December 2002. 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 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.
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000.
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 and Greg Weber.
Author's Address Author's Address
skipping to change at page 22, line 41 skipping to change at page 24, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 78 change blocks. 
52 lines changed or deleted 151 lines changed or added

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