draft-ietf-radext-dynauth-server-mib-02.txt   draft-ietf-radext-dynauth-server-mib-03.txt 
Network Working Group S. De Cnodder Network Working Group S. De Cnodder
Internet-Draft Alcatel Internet-Draft Alcatel
Expires: April 22, 2006 N. Jonnala Expires: July 7, 2006 N. Jonnala
M. Chiba M. Chiba
Cisco Systems, Inc. Cisco Systems, Inc.
October 19, 2005 January 3, 2006
Dynamic Authorization Server MIB Dynamic Authorization Server MIB
draft-ietf-radext-dynauth-server-mib-02.txt draft-ietf-radext-dynauth-server-mib-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 36 skipping to change at page 1, line 36
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 22, 2006. This Internet-Draft will expire on July 7, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
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.
In particular, it describes the RADIUS Dynamic Authorization Server In particular, it describes the Remote Authentication Dial In User
(DAS) functions that support the dynamic authorization extensions as Service (RADIUS) [RFC2865] Dynamic Authorization Server (DAS)
functions that support the dynamic authorization extensions as
defined in RFC 3576. defined in RFC 3576.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 4 2. The Internet-Standard Management Framework . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. RADIUS Dynamic Authorization Server MIB Definitions . . . . . 7 4. RADIUS Dynamic Authorization Server MIB Definitions . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 22 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 21
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.1. Normative References . . . . . . . . . . . . . . . . . . . 24 8.1. Normative References . . . . . . . . . . . . . . . . . . . 23
8.2. Informative References . . . . . . . . . . . . . . . . . . 24 8.2. Informative References . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . . . 27 Intellectual Property and Copyright Statements . . . . . . . . . . 26
1. Introduction 1. 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.
It is becoming increasingly important to support Dynamic It is becoming increasingly important to support Dynamic
Authorization extensions on the network access server (NAS) devices Authorization extensions on the network access server (NAS) devices
to handle the Disconnect and Change-of-Authorization (CoA) messages to handle the Disconnect and Change-of-Authorization (CoA) messages
as described in [RFC3576] . As a result, the effective management of as described in [RFC3576] . As a result, the effective management of
RADIUS Dynamic Authorization entities is of considerable importance. RADIUS Dynamic Authorization entities is of considerable importance.
This RADIUS Dynamic Authorization Server (DAS) MIB complements the This RADIUS Dynamic Authorization Server (DAS) MIB complements the
managed objects used for managing RADIUS authentication and managed objects used for managing RADIUS authentication and
accounting clients as described in [RFC2618] and [RFC2620], accounting clients as described in [RFC2618bis] and [RFC2620bis],
respectively. The corresponding version neutral IP address MIBs respectively.
[RFC2618bis] and [RFC2620bis] will obsolete (if approved) [RFC2618]
and [RFC2620]. -- RFC Ed.: references [DYNSERV], [RFC2618bis], [RFC2619bis],
-- [RFC2620bis], and [RFC2621bis] should be replaced by
-- references to the corresponding RFC.
1.1. Requirements notation 1.1. Requirements notation
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
1.2. Terminology 1.2. Terminology
Dynamic Authorization Server (DAS) Dynamic Authorization Server (DAS)
skipping to change at page 5, line 25 skipping to change at page 5, line 25
However, it is possible for a RADIUS Dynamic Authorization entity to However, it is possible for a RADIUS Dynamic Authorization entity to
perform both client and server functions. For example, a RADIUS perform both client and server functions. For example, a RADIUS
proxy may act as a DAS to one or more DACs, while simultaneously proxy may act as a DAS to one or more DACs, while simultaneously
acting as a DAC to one or more DASs. In such situations, it is acting as a DAC to one or more DASs. In such situations, it is
expected that RADIUS entities combining client and server expected that RADIUS entities combining client and server
functionality will support both the client and server MIBs. functionality will support both the client and server MIBs.
This memo describes the MIB for Dynamic Authorization Servers and This memo describes the MIB for Dynamic Authorization Servers and
relates to the following documents as follows: relates to the following documents as follows:
[RFC2618] describes the MIB for a RADIUS Authentication Client. [RFC2618bis] describes the MIB for a RADIUS Auth Client MIB.
[RFC2619] describes the MIB for a RADIUS Authentication Server.
[RFC2620] describes the MIB for a RADIUS Accounting Client.
[RFC2621] describes the MIB for a RADIUS Accounting Server.
The above MIBs support IPv4-only address format. The following MIBs
support version neutral IP address formats and (if approved) obsolete
the respective MIBs mentioned above.
[RFC2618bis] describes the MIB for a RADIUS Auth Client MIB (IPv6).
[RFC2619bis] describes the MIB for a RADIUS Auth Server MIB (IPv6). [RFC2619bis] describes the MIB for a RADIUS Auth Server MIB.
[RFC2620bis] describes the MIB for a RADIUS Acct Client MIB (IPv6). [RFC2620bis] describes the MIB for a RADIUS Acct Client MIB.
[RFC2621bis] describes the MIB for a RADIUS Acct Server MIB (IPv6). [RFC2621bis] describes the MIB for a RADIUS Acct Server MIB.
[DYNCLNT] describes the MIB for a RADIUS Dynamic Authorization [DYNCLNT] describes the MIB for a RADIUS Dynamic Authorization
Client. Client.
A NAS typically implements the MIBs for a RADIUS Authentication A NAS typically implements the MIBs for a RADIUS Authentication
Client, a RADIUS accounting client, and a RADIUS Dynamic Client, a RADIUS accounting client, and a RADIUS Dynamic
Authorization Server. However, there is not strict relationship Authorization Server. However, any one MIB can be implemented
between these three MIBs, i.e. one MIB can be implemented without without implementing any of the other MIBs, i.e. the MIBs have no
implementing the other MIBs. Similarly, for the other 3 MIBs dependencies on each other. A typical case would be for a device to
mentioned above, a typical case would be where the MIBs for a RADIUS implement the MIBs RADIUS authentication server, RADIUS accounting
authentication server, a RADIUS accounting server, and a RADIUS server and RADIUS Dynamic Authorization Client. A RADIUS proxy might
Dynamic Authorization Client are implemented by the same device. implement any, all or a subset of the MIBs listed above and the MIB
However, also for these 3 MIBs, they can be implemented independent as defined in this document.
from each other. A RADIUS proxy might implement any of these 6 MIBs,
but can also implement any subset of these MIBs.
+---------------+ +---------------+ +---------------+ +---------------+
User 1----| | Disconnect-Request | | User 1----| | Disconnect-Request | |
| Dynamic | CoA-Request | Dynamic | | Dynamic | CoA-Request | Dynamic |
User 2----| Authorization |<---------------------| Authorization | User 2----| Authorization |<---------------------| Authorization |
| Server |--------------------->| Client | | Server |--------------------->| Client |
User 3----| (DAS) | Disconnect-Ack | (DAC) | User 3----| (DAS) | Disconnect-Ack | (DAC) |
| | Disconnect-NAK | | | | Disconnect-NAK | |
+---------------+ CoA-Ack/CoA-NAK +---------------+ +---------------+ CoA-Ack/CoA-NAK +---------------+
Figure 1: Mapping of clients and servers. Figure 1: Mapping of clients and servers.
This MIB module for the Dynamic Authorization Server contains the This MIB module for the Dynamic Authorization Server contains the
following: following:
1. Three scalar objects. 1. Three scalar objects, and
2. One Dynamic Authorization Client Table. This table contains one 2. One Dynamic Authorization Client Table. This table contains one
row for each DAC with which the DAS shares a secret. row for each DAC with which the DAS shares a secret.
4. RADIUS Dynamic Authorization Server MIB Definitions 4. RADIUS Dynamic Authorization Server MIB Definitions
RADIUS-DYNAUTH-SERVER-MIB DEFINITIONS ::= BEGIN RADIUS-DYNAUTH-SERVER-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Counter32, Integer32, mib-2 FROM SNMPv2-SMI -- [RFC2578] Counter32, Integer32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
InetAddressType, InetAddressType,
InetAddress FROM INET-ADDRESS-MIB -- [RFC4001] InetAddress FROM INET-ADDRESS-MIB -- [RFC4001]
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF; -- [RFC2580] OBJECT-GROUP FROM SNMPv2-CONF; -- [RFC2580]
radiusDynAuthServerMIB MODULE-IDENTITY radiusDynAuthServerMIB MODULE-IDENTITY
LAST-UPDATED "200510160000Z" -- 16 October 2005 LAST-UPDATED "200601030000Z" -- 3 January 2006
ORGANIZATION "IETF RADEXT Working Group" ORGANIZATION "IETF RADEXT Working Group"
CONTACT-INFO CONTACT-INFO
" Stefaan De Cnodder " Stefaan De Cnodder
Alcatel Alcatel
Francis Wellesplein 1 Francis Wellesplein 1
B-2018 Antwerp B-2018 Antwerp
Belgium Belgium
Phone: +32 3 240 85 15 Phone: +32 3 240 85 15
EMail: stefaan.de_cnodder@alcatel.be EMail: stefaan.de_cnodder@alcatel.be
skipping to change at page 7, line 49 skipping to change at page 7, line 49
Murtaza Chiba Murtaza Chiba
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Dr. 170 West Tasman Dr.
San Jose CA, 95134 San Jose CA, 95134
Phone: +1 408 525 7198 Phone: +1 408 525 7198
EMail: mchiba@cisco.com " EMail: mchiba@cisco.com "
DESCRIPTION DESCRIPTION
"The MIB module for entities implementing the server "The MIB module for entities implementing the server
side of the Dynamic Authorization extensions Remote side of the Dynamic Authorization Extensions to Remote
Access Dialin User Service (RADIUS) protocol. Authentication Dial In User Service (RADIUS) protocol.
Copyright (C) The Internet Society (2005). This initial Copyright (C) The Internet Society (2005). Initial
version of this MIB module was published in RFC yyyy; version as published in RFC yyyy;
for full legal notices see the RFC itself. Supplementary for full legal notices see the RFC itself. Supplementary
information may be available on information may be available on
http://www.ietf.org/copyrights/ianamib.html." http://www.ietf.org/copyrights/ianamib.html."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200510160000Z" -- 16 October 2005 REVISION "200601030000Z" -- 3 January 2006
DESCRIPTION "Initial version as published in RFC yyyy." DESCRIPTION "Initial version as published in RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 xxx } ::= { mib-2 xxx }
-- The value xxx to be assigned by IANA. -- The value xxx to be assigned by IANA.
radiusDynAuthServerMIBObjects OBJECT IDENTIFIER ::= radiusDynAuthServerMIBObjects OBJECT IDENTIFIER ::=
{ radiusDynAuthServerMIB 1 } { radiusDynAuthServerMIB 1 }
radiusDynAuthServer OBJECT IDENTIFIER ::= radiusDynAuthServer OBJECT IDENTIFIER ::=
{ radiusDynAuthServerMIBObjects 1 } { radiusDynAuthServerMIBObjects 1 }
radiusDynAuthServerDisconInvalidClientAddresses OBJECT-TYPE radiusDynAuthServerDisconInvalidClientAddresses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Disconnect messages received from unknown "The number of Disconnect-Request packets received from
addresses." unknown addresses."
::= { radiusDynAuthServer 1 } ::= { radiusDynAuthServer 1 }
radiusDynAuthServerCoAInvalidClientAddresses OBJECT-TYPE radiusDynAuthServerCoAInvalidClientAddresses OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of CoA messages received from unknown "The number of CoA-Request packets received from unknown
addresses." addresses."
::= { radiusDynAuthServer 2 } ::= { radiusDynAuthServer 2 }
radiusDynAuthServerIdentifier OBJECT-TYPE radiusDynAuthServerIdentifier 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 Dynamic Authorization "The NAS-Identifier of the RADIUS Dynamic Authorization
Server." Server. This is not necessarily the same as sysName in
MIB II."
REFERENCE REFERENCE
"RFC 2865, Section 5.32, NAS-Identifier." "RFC 2865, Section 5.32, NAS-Identifier."
::= { radiusDynAuthServer 3 } ::= { radiusDynAuthServer 3 }
radiusDynAuthClientTable OBJECT-TYPE radiusDynAuthClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusDynAuthClientEntry SYNTAX SEQUENCE OF RadiusDynAuthClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the RADIUS Dynamic "The (conceptual) table listing the RADIUS Dynamic
Authorization Clients with which the server shares a Authorization Clients with which the server shares a
secret." secret."
::= { radiusDynAuthServer 4 } ::= { radiusDynAuthServer 4 }
skipping to change at page 10, line 21 skipping to change at page 10, line 23
Authorization Server communicates. This number is Authorization Server communicates. This number is
allocated by the agent implementing this MIB module, allocated by the agent implementing this MIB module,
and is unique in this context." and is unique in this context."
::= { radiusDynAuthClientEntry 1 } ::= { radiusDynAuthClientEntry 1 }
radiusDynAuthClientAddressType OBJECT-TYPE radiusDynAuthClientAddressType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of IP-Address of the RADIUS Dynamic "The type of IP address of the RADIUS Dynamic
Authorization Client referred to in this table entry." Authorization Client referred to in this table entry."
::= { radiusDynAuthClientEntry 2 } ::= { radiusDynAuthClientEntry 2 }
radiusDynAuthClientAddress OBJECT-TYPE radiusDynAuthClientAddress OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP-Address value of the RADIUS Dynamic "The IP address value of the RADIUS Dynamic
Authorization Client referred to in this table entry." Authorization Client referred to in this table entry,
using the version neutral IP address format."
::= { radiusDynAuthClientEntry 3 } ::= { radiusDynAuthClientEntry 3 }
radiusDynAuthServDisconRequests OBJECT-TYPE radiusDynAuthServDisconRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Disconnect-Requests received "The number of RADIUS Disconnect-Requests received
from this Dynamic Authorization Client. This includes from this Dynamic Authorization Client. This also
the RADIUS Disconnect-Requests that have a includes the RADIUS Disconnect-Requests that have a
Service-Type attribute with value 'Authorize Only'." Service-Type attribute with value 'Authorize Only'."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 4 } ::= { radiusDynAuthClientEntry 4 }
radiusDynAuthServDisconAuthOnlyRequests OBJECT-TYPE radiusDynAuthServDisconAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Disconnect-Requests including a "The number of RADIUS Disconnect-Requests that include
Service-Type attribute with value 'Autorize Only' a Service-Type attribute with value 'Authorize Only'
received from this Dynamic Authorization Client." received from this Dynamic Authorization Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 5 } ::= { radiusDynAuthClientEntry 5 }
radiusDynAuthServDupDisconRequests OBJECT-TYPE radiusDynAuthServDupDisconRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 12, line 12 skipping to change at page 12, line 16
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 8 } ::= { radiusDynAuthClientEntry 8 }
radiusDynAuthServDisconNakAuthOnlyRequests OBJECT-TYPE radiusDynAuthServDisconNakAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "replies" UNITS "replies"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS Disconnect-NAK packets "The number of RADIUS Disconnect-NAK packets that
including a Service-Type attribute with value include a Service-Type attribute with value
'Autorize Only' sent to this Dynamic Authorization 'Authorize Only' sent to this Dynamic Authorization
Client." Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 9 } ::= { radiusDynAuthClientEntry 9 }
radiusDynAuthServDisconNakSessNoContext OBJECT-TYPE radiusDynAuthServDisconNakSessNoContext OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "replies" UNITS "replies"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 12, line 43 skipping to change at page 12, line 47
radiusDynAuthServDisconUserSessRemoved OBJECT-TYPE radiusDynAuthServDisconUserSessRemoved OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of user sessions removed for the "The number of user sessions removed for the
Disconnect-Requests received from this Disconnect-Requests received from this
Dynamic Authorization Client. Depending on site Dynamic Authorization Client. Depending on site
specific policies, a single Disconnect request specific policies, a single Disconnect request
can remove multiple user sessions. In the case this can remove multiple user sessions. In the case
Dynamic Authorization Server has no knowledge of that this Dynamic Authorization Server has no
the number of user sessions that are affected, then knowledge of the number of user sessions that
it counts a single user session for each such are affected by a single request, for each such
Disconnect-Request." Disconnect-Request, it will count as a single
affected user session only."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 11 } ::= { radiusDynAuthClientEntry 11 }
radiusDynAuthServMalformedDisconRequests OBJECT-TYPE radiusDynAuthServMalformedDisconRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of malformed RADIUS Disconnect-Request "The number of malformed RADIUS Disconnect-Request
packets received from this Dynamic Authorization packets received from this Dynamic Authorization
Client. Bad authenticators and unknown types are not Client. Bad authenticators and unknown types are not
included as malformed Disconnect-Requests." included as malformed Disconnect-Requests."
skipping to change at page 14, line 8 skipping to change at page 14, line 13
Section 2.3, Packet Format." Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 14 } ::= { radiusDynAuthClientEntry 14 }
radiusDynAuthServCoARequests OBJECT-TYPE radiusDynAuthServCoARequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS CoA-requests received from this "The number of RADIUS CoA-requests received from this
Dynamic Authorization Client. This includes Dynamic Authorization Client. This also includes
the CoA requests that have a Service-Type attribute the CoA requests that have a Service-Type attribute
with value 'Authorize Only'." with value 'Authorize Only'."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 15 } ::= { radiusDynAuthClientEntry 15 }
radiusDynAuthServCoAAuthOnlyRequests OBJECT-TYPE radiusDynAuthServCoAAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS CoA-requests including a "The number of RADIUS CoA-requests that include a
Service-Type attribute with value 'Autorize Only' Service-Type attribute with value 'Authorize Only'
received from this Dynamic Authorization Client." received from this Dynamic Authorization Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 16 } ::= { radiusDynAuthClientEntry 16 }
radiusDynAuthServDupCoARequests OBJECT-TYPE radiusDynAuthServDupCoARequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 15, line 33 skipping to change at page 15, line 38
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 19 } ::= { radiusDynAuthClientEntry 19 }
radiusDynAuthServCoANakAuthOnlyRequests OBJECT-TYPE radiusDynAuthServCoANakAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "replies" UNITS "replies"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS CoA-NAK packets including a "The number of RADIUS CoA-NAK packets that include a
Service-Type attribute with value 'Autorize Only' Service-Type attribute with value 'Authorize Only'
sent to this Dynamic Authorization Client." sent to this Dynamic Authorization Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 20 } ::= { radiusDynAuthClientEntry 20 }
radiusDynAuthServCoANakSessNoContext OBJECT-TYPE radiusDynAuthServCoANakSessNoContext OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "replies" UNITS "replies"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 16, line 19 skipping to change at page 16, line 24
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of user sessions authorization "The number of user sessions authorization
changed for the CoA-Requests received from this changed for the CoA-Requests received from this
Dynamic Authorization Client. Depending on site Dynamic Authorization Client. Depending on site
specific policies, a single CoA request can change specific policies, a single CoA request can change
multiple user sessions' authorization. In the case multiple user sessions' authorization. In the case
this Dynamic Authorization Server has no knowledge of this Dynamic Authorization Server has no knowledge of
the number of user sessions that are affected, then the number of user sessions that are affected by a
it counts a single user session for each such single request, for each such CoA-Request, it will
CoA-Request." count as a single affected user session only."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 22 } ::= { radiusDynAuthClientEntry 22 }
radiusDynAuthServMalformedCoARequests OBJECT-TYPE radiusDynAuthServMalformedCoARequests OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "requests" UNITS "requests"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 19, line 16 skipping to change at page 19, line 21
radiusDynAuthServerAuthOnlyGroup OBJECT-GROUP radiusDynAuthServerAuthOnlyGroup OBJECT-GROUP
OBJECTS { radiusDynAuthServDisconAuthOnlyRequests, OBJECTS { radiusDynAuthServDisconAuthOnlyRequests,
radiusDynAuthServDisconNakAuthOnlyRequests, radiusDynAuthServDisconNakAuthOnlyRequests,
radiusDynAuthServCoAAuthOnlyRequests, radiusDynAuthServCoAAuthOnlyRequests,
radiusDynAuthServCoANakAuthOnlyRequests radiusDynAuthServCoANakAuthOnlyRequests
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects supporting the RADIUS "The collection of objects supporting the RADIUS
messages including Service-Type attribute with messages including Service-Type attribute with
value 'Autorize Only'." value 'Authorize Only'."
::= { radiusDynAuthServerMIBGroups 2 } ::= { radiusDynAuthServerMIBGroups 2 }
radiusDynAuthServerNoSessGroup OBJECT-GROUP radiusDynAuthServerNoSessGroup OBJECT-GROUP
OBJECTS { radiusDynAuthServDisconNakSessNoContext, OBJECTS { radiusDynAuthServDisconNakSessNoContext,
radiusDynAuthServCoANakSessNoContext radiusDynAuthServCoANakSessNoContext
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects supporting the RADIUS "The collection of objects supporting the RADIUS
messages that are referring to non existing sessions." messages that are referring to non existing sessions."
skipping to change at page 20, line 32 skipping to change at page 20, line 32
These can be used to determine the address of the DAC with which the These can be used to determine the address of the DAC with which the
DAS is communicating. This information could be useful in mounting DAS is communicating. This information could be useful in mounting
an attack on the DAC. an attack on the DAC.
radiusDynAuthServerIdentifier radiusDynAuthServerIdentifier
This can be used to determine the Identifier of the DAS. This This can be used to determine the Identifier of the DAS. This
information could be useful in impersonating the DAS. information could be useful in impersonating the DAS.
The other readable objects are not really considered as being
sensitive or vulnerable. These objects are:
radiusDynAuthServerDisconInvalidClientAddresses,
radiusDynAuthServerCoAInvalidClientAddresses,
radiusDynAuthServDisconRequests,
radiusDynAuthServDisconAuthOnlyRequests,
radiusDynAuthServDupDisconRequests,
radiusDynAuthServDisconAcks,
radiusDynAuthServDisconNaks,
radiusDynAuthServDisconNakAuthOnlyRequests,
radiusDynAuthServDisconNakSessNoContext,
radiusDynAuthServDisconUserSessRemoved,
radiusDynAuthServMalformedDisconRequests,
radiusDynAuthServDisconBadAuthenticators,
radiusDynAuthServDisconPacketsDropped,
radiusDynAuthServCoARequests,
radiusDynAuthServCoAAuthOnlyRequests,
radiusDynAuthServDupCoARequests,
radiusDynAuthServCoAAcks,
radiusDynAuthServCoANaks,
radiusDynAuthServCoANakAuthOnlyRequests,
radiusDynAuthServCoANakSessNoContext,
radiusDynAuthServCoAUserSessChanged,
radiusDynAuthServMalformedCoARequests,
radiusDynAuthServCoABadAuthenticators,
radiusDynAuthServCoAPacketsDropped, and
radiusDynAuthServUnknownTypes.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
skipping to change at page 23, line 7 skipping to change at page 22, line 7
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
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.
6. IANA considerations 6. IANA considerations
IANA is requested to assign an OID xxx under mib-2. IANA is requested to assign an OID xxx under mib-2.
7. Acknowledgements 7. Acknowledgements
This document reuses some of the work done in earlier RADIUS MIB
specifications [RFC2618] and [RFC2620].
The authors would also like to acknowledge the following people for The authors would also like to acknowledge the following people for
their comments to this document: Anjaneyulu Pata, Dan Romascanu, Bert their comments on this document: Bernard Aboba, Alan DeKok, David
Wijnen, Bernard Aboba, David Nelson, Greg Weber and Glen Zorn. Nelson, Anjaneyulu Pata, Dan Romascanu, Greg Weber, Bert Wijnen, and
Glen Zorn.
8. References 8. References
8.1. Normative References 8.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", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
skipping to change at page 24, line 42 skipping to change at page 23, line 42
Authentication Dial In User Service (RADIUS)", RFC 3576, Authentication Dial In User Service (RADIUS)", RFC 3576,
July 2003. July 2003.
[RFC4001] Daniele, M. and et al., "Textual Conventions for Internet [RFC4001] Daniele, M. and et al., "Textual Conventions for Internet
Network Addresses", RFC 4001, February 2005. Network Addresses", RFC 4001, February 2005.
8.2. Informative References 8.2. Informative References
[DYNCLNT] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic [DYNCLNT] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic
Authorization Client MIB", Authorization Client MIB",
draft-decnodder-radext-dynauth-client-mib-02.txt, work in draft-ietf-radext-dynauth-client-mib-03.txt, work in
progress, September 2005. progress, December 2005.
[RFC2618] Aboba, B. and G. Zorn, "RADIUS Authentication Client MIB",
RFC 2618, June 1999.
[RFC2618bis] [RFC2618bis]
Nelson, D., "RADIUS Auth Client MIB (IPv6)", Nelson, D., "RADIUS Auth Client MIB (IPv6)",
draft-ietf-radext-rfc2618bis-00.txt work in progress, draft-ietf-radext-rfc2618bis-01.txt work in progress,
August 2005. October 2005.
[RFC2619] Zorn, G. and B. Aboba, "RADIUS Authentication Server MIB",
RFC 2619, June 1999.
[RFC2619bis] [RFC2619bis]
Nelson, D., "RADIUS Auth Server MIB (IPv6)", Nelson, D., "RADIUS Auth Server MIB (IPv6)",
draft-ietf-radext-rfc2619bis-00.txt work in progress, draft-ietf-radext-rfc2619bis-01.txt work in progress,
August 2005. October 2005.
[RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB",
RFC 2620, June 1999.
[RFC2620bis] [RFC2620bis]
Nelson, D., "RADIUS Acct Client MIB (IPv6)", Nelson, D., "RADIUS Acct Client MIB (IPv6)",
draft-ietf-radext-rfc2620bis-00.txt work in progress, draft-ietf-radext-rfc2620bis-01.txt work in progress,
August 2005. October 2005.
[RFC2621] Zorn, G. and B. Aboba, "RADIUS Accounting Server MIB",
RFC 2621, June 1999.
[RFC2621bis] [RFC2621bis]
Nelson, D., "RADIUS Acct Server MIB (IPv6)", Nelson, D., "RADIUS Acct Server MIB (IPv6)",
draft-ietf-radext-rfc2621bis-00.txt work in progress, draft-ietf-radext-rfc2621bis-01.txt work in progress,
August 2005. October 2005.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, 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.
Authors' Addresses Authors' Addresses
Stefaan De Cnodder Stefaan De Cnodder
Alcatel Alcatel
Francis Wellesplein 1 Francis Wellesplein 1
B-2018 Antwerp B-2018 Antwerp
Belgium Belgium
skipping to change at page 27, line 41 skipping to change at page 26, 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. 46 change blocks. 
139 lines changed or deleted 91 lines changed or added

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