draft-ietf-radext-dynauth-server-mib-01.txt   draft-ietf-radext-dynauth-server-mib-02.txt 
Network Working Group S. De Cnodder Network Working Group S. De Cnodder
Internet-Draft Alcatel Internet-Draft Alcatel
Expires: January 8, 2006 N. Jonnala Expires: April 22, 2006 N. Jonnala
M. Chiba M. Chiba
Cisco Systems, Inc. Cisco Systems, Inc.
July 7, 2005 October 19, 2005
Dynamic Authorization Server MIB Dynamic Authorization Server MIB
draft-ietf-radext-dynauth-server-mib-01.txt draft-ietf-radext-dynauth-server-mib-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 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 January 8, 2006. This Internet-Draft will expire on April 22, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
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 RADIUS Dynamic Authorization Server
(DAS) functions that support the dynamic authorization extensions as (DAS) functions that support the dynamic authorization extensions as
defined in RFC 3576. defined in RFC 3576.
Table of Contents Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . 5 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 6 2. The Internet-Standard Management Framework . . . . . . . . . . 4
5. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. RADIUS Dynamic Authorization Server MIB Definitions . . . . 9 4. RADIUS Dynamic Authorization Server MIB Definitions . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . 19 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. IANA considerations . . . . . . . . . . . . . . . . . . . . 21 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.1 Normative References . . . . . . . . . . . . . . . . . . 23 8.1. Normative References . . . . . . . . . . . . . . . . . . . 24
10.2 Informative References . . . . . . . . . . . . . . . . . 23 8.2. Informative References . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26
Intellectual Property and Copyright Statements . . . . . . . 25 Intellectual Property and Copyright Statements . . . . . . . . . . 27
1. Requirements notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
2. 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.
It complements the managed objects used for managing RADIUS This RADIUS Dynamic Authorization Server (DAS) MIB complements the
authentication and accounting clients as described in [RFC2618] and managed objects used for managing RADIUS authentication and
[RFC2620], respectively. accounting clients as described in [RFC2618] and [RFC2620],
respectively. The corresponding version neutral IP address MIBs
3. The Internet-Standard Management Framework [RFC2618bis] and [RFC2620bis] will obsolete (if approved) [RFC2618]
and [RFC2620].
For a detailed overview of the documents that describe the current 1.1. Requirements notation
Internet-Standard Management Framework, please refer to section 7 of
[RFC3410].
Managed objects are accessed via a virtual information store, termed The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
the Management Information Base or MIB. MIB objects are generally "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
accessed through the Simple Network Management Protocol (SNMP). document are to be interpreted as described in [RFC2119].
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC2578 [RFC2578], STD 58, RFC2579 [RFC2579] and STD 58, RFC2580
[RFC2580].
4. Terminology 1.2. Terminology
Dynamic Authorization Server (DAS) Dynamic Authorization Server (DAS)
The component that resides on the NAS which processes the Disconnect The component that resides on the NAS which processes the Disconnect
and CoA requests sent by the Dynamic Authorization Client as and Change-of-Authorization (CoA) Request packets [RFC3576] sent by
described in [RFC3576]. the Dynamic Authorization Client.
Dynamic Authorization Client (DAC) Dynamic Authorization Client (DAC)
The component which sends the Disconnect and CoA requests to the The component which sends Disconnect and CoA-Request packets to the
Dynamic Authorization Server as described in [RFC3576]. This is Dynamic Authorization Server. While often residing on the RADIUS
typically a RADIUS Server, but is not limited to it and may, for server, it is also possible for this component to be located on a
example, be a Rating Engine used for Prepaid Billing. separate host, such as a Rating Engine.
Dynamic Authorization Server Port Dynamic Authorization Server Port
The UDP port on which the Dynamic Authorization server listens for The UDP port on which the Dynamic Authorization Server listens for
the Disconnect and CoA requests sent by the Dynamic Authorization the Disconnect and CoA requests sent by the Dynamic Authorization
Client. Client.
5. Overview 2. The Internet-Standard Management Framework
The RADIUS dynamic authorization extensions defined in [RFC3576], For a detailed overview of the documents that describe the current
distinguish between the client function and the server function. In Internet-Standard Management Framework, please refer to section 7 of
RADIUS dynamic authorization, clients send Disconnect-Requests and [RFC3410].
CoA-Requests, and servers reply with Disconnect-Acks, CoA-Acks, and
CoA-NAKs. Typically NAS devices implement the DAS function, and thus
would be expected to implement the RADIUS dynamic authorization
server MIB, while DACs implement the client function, and thus would
be expected to implement the RADIUS dynamic authorization client MIB.
However, it is possible for a RADIUS dynamic authorization entity to Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC2578 [RFC2578], STD 58, RFC2579 [RFC2579] and STD 58, RFC2580
[RFC2580].
3. Overview
"Dynamic Authorization Extensions to RADIUS" [RFC3576] defines the
operation of Disconnect-Request, Disconnect-ACK, Disconnect-NAK, CoA-
Request, CoA-ACK and CoA-NAK packets. Typically NAS devices
implement the DAS function, and thus would be expected to implement
the RADIUS Dynamic Authorization Server MIB, while DACs implement the
client function, and thus would be expected to implement the RADIUS
Dynamic Authorization Client MIB.
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. [RFC2618] describes the MIB for a RADIUS Authentication Client.
[RFC2619] describes the MIB for a RADIUS authentication server. [RFC2619] describes the MIB for a RADIUS Authentication Server.
[RFC2620] describes the MIB for a RADIUS accounting client. [RFC2620] describes the MIB for a RADIUS Accounting Client.
[RFC2621] describes the MIB for a RADIUS accounting server. [RFC2621] describes the MIB for a RADIUS Accounting Server.
[DYNCLNT] describes the MIB for a RADIUS dynamic authorization The above MIBs support IPv4-only address format. The following MIBs
client. support version neutral IP address formats and (if approved) obsolete
the respective MIBs mentioned above.
A NAS typically implements the MIBs for a RADIUS authentication [RFC2618bis] describes the MIB for a RADIUS Auth Client MIB (IPv6).
client, a RADIUS accounting client, and a RADIUS dynamic
authorization server. However, there is not strict relationship [RFC2619bis] describes the MIB for a RADIUS Auth Server MIB (IPv6).
[RFC2620bis] describes the MIB for a RADIUS Acct Client MIB (IPv6).
[RFC2621bis] describes the MIB for a RADIUS Acct Server MIB (IPv6).
[DYNCLNT] describes the MIB for a RADIUS Dynamic Authorization
Client.
A NAS typically implements the MIBs for a RADIUS Authentication
Client, a RADIUS accounting client, and a RADIUS Dynamic
Authorization Server. However, there is not strict relationship
between these three MIBs, i.e. one MIB can be implemented without between these three MIBs, i.e. one MIB can be implemented without
implementing the other MIBs. Similarly, for the other 3 MIBs implementing the other MIBs. Similarly, for the other 3 MIBs
mentioned above, a typical case would be where the MIBs for a RADIUS mentioned above, a typical case would be where the MIBs for a RADIUS
authentication server, a RADIUS accounting server, and a RADIUS authentication server, a RADIUS accounting server, and a RADIUS
dynamic authorization client are implemented by the same device. Dynamic Authorization Client are implemented by the same device.
However, also for these 3 MIBs, they can be implemented independent However, also for these 3 MIBs, they can be implemented independent
from each other. A RADIUS proxy might implement any of these 6 MIBs, from each other. A RADIUS proxy might implement any of these 6 MIBs,
but can also implement any subset of these 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. Two scalar objects 1. Three scalar objects.
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.
6. 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 Counter32, Integer32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
InetAddressType, InetAddress FROM INET-ADDRESS-MIB InetAddressType,
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; InetAddress FROM INET-ADDRESS-MIB -- [RFC4001]
MODULE-COMPLIANCE,
OBJECT-GROUP FROM SNMPv2-CONF; -- [RFC2580]
radiusDynAuthServerMIB MODULE-IDENTITY radiusDynAuthServerMIB MODULE-IDENTITY
LAST-UPDATED "200507020000Z" -- 2 July 2005 LAST-UPDATED "200510160000Z" -- 16 October 2005
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 10, line 8 skipping to change at page 8, line 10
side of the Dynamic Authorization extensions Remote side of the Dynamic Authorization extensions Remote
Access Dialin User Service (RADIUS) protocol. Access Dialin User Service (RADIUS) protocol.
Copyright (C) The Internet Society (2005). This initial Copyright (C) The Internet Society (2005). This initial
version of this MIB module was published in RFC yyyy; version of this MIB module was 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 "200507020000Z" -- 2 July 2005 REVISION "200510160000Z" -- 16 October 2005
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
::= { radiusDynamicAuthorization 1 } ::= { mib-2 xxx }
radiusDynamicAuthorization OBJECT IDENTIFIER ::= { 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
skipping to change at page 10, line 45 skipping to change at page 8, line 45
DESCRIPTION DESCRIPTION
"The number of CoA messages received from unknown "The number of CoA messages 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."
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 }
radiusDynAuthClientEntry OBJECT-TYPE radiusDynAuthClientEntry OBJECT-TYPE
SYNTAX RadiusDynAuthClientEntry SYNTAX RadiusDynAuthClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) representing one Dynamic "An entry (conceptual row) representing one Dynamic
Authorization Client with which the server shares a Authorization Client with which the server shares a
secret." secret."
INDEX { radiusDynAuthClientIndex } INDEX { radiusDynAuthClientIndex }
::= { radiusDynAuthClientTable 1 } ::= { radiusDynAuthClientTable 1 }
RadiusDynAuthClientEntry ::= SEQUENCE { RadiusDynAuthClientEntry ::= SEQUENCE {
radiusDynAuthClientIndex Integer32, radiusDynAuthClientIndex Integer32,
radiusDynAuthClientAddressType InetAddressType, radiusDynAuthClientAddressType InetAddressType,
radiusDynAuthClientAddress InetAddress, radiusDynAuthClientAddress InetAddress,
radiusDynAuthServDisconRequests Counter32, radiusDynAuthServDisconRequests Counter32,
radiusDynAuthServDisconAuthOnlyRequests Counter32,
radiusDynAuthServDupDisconRequests Counter32, radiusDynAuthServDupDisconRequests Counter32,
radiusDynAuthServDisconAcks Counter32, radiusDynAuthServDisconAcks Counter32,
radiusDynAuthServDisconNaks Counter32, radiusDynAuthServDisconNaks Counter32,
radiusDynAuthServDisconNakAuthOnlyRequests Counter32,
radiusDynAuthServDisconNakSessNoContext Counter32,
radiusDynAuthServDisconUserSessRemoved Counter32, radiusDynAuthServDisconUserSessRemoved Counter32,
radiusDynAuthServMalformedDisconRequests Counter32, radiusDynAuthServMalformedDisconRequests Counter32,
radiusDynAuthServDisconBadAuthenticators Counter32, radiusDynAuthServDisconBadAuthenticators Counter32,
radiusDynAuthServDisconPacketsDropped Counter32, radiusDynAuthServDisconPacketsDropped Counter32,
radiusDynAuthServCoARequests Counter32, radiusDynAuthServCoARequests Counter32,
radiusDynAuthServCoAAuthOnlyRequests Counter32,
radiusDynAuthServDupCoARequests Counter32, radiusDynAuthServDupCoARequests Counter32,
radiusDynAuthServCoAAcks Counter32, radiusDynAuthServCoAAcks Counter32,
radiusDynAuthServCoANaks Counter32, radiusDynAuthServCoANaks Counter32,
radiusDynAuthServCoANakAuthOnlyRequests Counter32,
radiusDynAuthServCoANakSessNoContext Counter32,
radiusDynAuthServCoAUserSessChanged Counter32, radiusDynAuthServCoAUserSessChanged Counter32,
radiusDynAuthServMalformedCoARequests Counter32, radiusDynAuthServMalformedCoARequests Counter32,
radiusDynAuthServCoABadAuthenticators Counter32, radiusDynAuthServCoABadAuthenticators Counter32,
radiusDynAuthServCoAPacketsDropped Counter32, radiusDynAuthServCoAPacketsDropped Counter32,
radiusDynAuthServUnknownTypes Counter32 radiusDynAuthServUnknownTypes Counter32
} }
radiusDynAuthClientIndex OBJECT-TYPE radiusDynAuthClientIndex 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 dynamic "A number uniquely identifying each RADIUS Dynamic
authorization client with which this Dynamic Authorization Client with which this Dynamic
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
skipping to change at page 12, line 37 skipping to change at page 10, line 41
Authorization Client referred to in this table entry." Authorization Client referred to in this table entry."
::= { 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." from this Dynamic Authorization Client. This includes
the RADIUS Disconnect-Requests that have a
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
SYNTAX Counter32
UNITS "requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-Requests including a
Service-Type attribute with value 'Autorize Only'
received from this Dynamic Authorization Client."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { 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
DESCRIPTION DESCRIPTION
"The number of duplicate RADIUS Disconnect-Request "The number of duplicate RADIUS Disconnect-Request
packets received from this Dynamic Authorization packets received from this Dynamic Authorization
Client." Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 5 } ::= { radiusDynAuthClientEntry 6 }
radiusDynAuthServDisconAcks OBJECT-TYPE radiusDynAuthServDisconAcks 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-ACK packets "The number of RADIUS Disconnect-ACK packets
sent to this Dynamic Authorization Client" sent to this Dynamic Authorization Client"
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 6 } ::= { radiusDynAuthClientEntry 7 }
radiusDynAuthServDisconNaks OBJECT-TYPE radiusDynAuthServDisconNaks 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
sent to this Dynamic Authorization Client." sent to this Dynamic Authorization Client. This
includes the RADIUS Disconnect-NAK packets sent
with a Service-Type attribute with value 'Authorize
Only' and the RADIUS Disconnect-NAK packets sent
because no session context was found."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 7 } ::= { radiusDynAuthClientEntry 8 }
radiusDynAuthServDisconNakAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-NAK packets
including a Service-Type attribute with value
'Autorize Only' sent to this Dynamic Authorization
Client."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 9 }
radiusDynAuthServDisconNakSessNoContext OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-NAK packets
sent to this Dynamic Authorization Client
because no session context was found."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 10 }
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 this
Dynamic Autorization Server has no knowledge of Dynamic Authorization Server has no knowledge of
the number of user sessions that are affected, then the number of user sessions that are affected, then
it counts a single user session for each such it counts a single user session for each such
Disconnect-Request." Disconnect-Request."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 8 } ::= { 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."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM), and "RFC 3576, Section 2.1, Disconnect Messages (DM), and
Section 2.3, Packet Format." Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 9 } ::= { radiusDynAuthClientEntry 12 }
radiusDynAuthServDisconBadAuthenticators OBJECT-TYPE radiusDynAuthServDisconBadAuthenticators 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-Request packets "The number of RADIUS Disconnect-Request packets
which contained invalid Authenticator field which contained invalid Authenticator field
received from this Dynamic Authorization Client." received from this Dynamic Authorization Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM), and "RFC 3576, Section 2.1, Disconnect Messages (DM), and
Section 2.3, Packet Format." Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 10 } ::= { radiusDynAuthClientEntry 13 }
radiusDynAuthServDisconPacketsDropped OBJECT-TYPE radiusDynAuthServDisconPacketsDropped 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 incoming Disconnect-Requests "The number of incoming Disconnect-Requests
from this Dynamic Authorization Client silently from this Dynamic Authorization Client silently
discarded by the server application for some reason discarded by the server application for some reason
other than malformed, bad authenticators or unknown other than malformed, bad authenticators or unknown
types." types."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM), and "RFC 3576, Section 2.1, Disconnect Messages (DM), and
Section 2.3, Packet Format." Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 11 } ::= { 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 CoA requests received from this "The number of RADIUS CoA-requests received from this
Dynamic Authorization Client." Dynamic Authorization Client. This includes
the CoA requests that have a Service-Type attribute
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 12 } ::= { radiusDynAuthClientEntry 15 }
radiusDynAuthServCoAAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32
UNITS "requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-requests including a
Service-Type attribute with value 'Autorize Only'
received from this Dynamic Authorization Client."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthClientEntry 16 }
radiusDynAuthServDupCoARequests OBJECT-TYPE radiusDynAuthServDupCoARequests 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 duplicate RADIUS CoA-Request "The number of duplicate RADIUS CoA-Request
packets received from this Dynamic Authorization packets received from this Dynamic Authorization
client." Client."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 13 } ::= { radiusDynAuthClientEntry 17 }
radiusDynAuthServCoAAcks OBJECT-TYPE radiusDynAuthServCoAAcks 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-ACK packets "The number of RADIUS CoA-ACK packets
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 14 } ::= { radiusDynAuthClientEntry 18 }
radiusDynAuthServCoANaks OBJECT-TYPE radiusDynAuthServCoANaks 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 "The number of RADIUS CoA-NAK packets sent to
this Dynamic Authorization Client. This includes
the RADIUS CoA-NAK packets sent with a Service-Type
attribute with value 'Authorize Only' and the RADIUS
CoA-NAK packets sent because no session context was
found."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthClientEntry 19 }
radiusDynAuthServCoANakAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-NAK packets including a
Service-Type attribute with value 'Autorize 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 15 } ::= { radiusDynAuthClientEntry 20 }
radiusDynAuthServCoANakSessNoContext OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-NAK packets
sent to this Dynamic Authorization Client
because no session context was found."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthClientEntry 21 }
radiusDynAuthServCoAUserSessChanged OBJECT-TYPE radiusDynAuthServCoAUserSessChanged 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 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 Autorization 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, then
it counts a single user session for each such it counts a single user session for each such
CoA-Request." CoA-Request."
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 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
DESCRIPTION DESCRIPTION
"The number of malformed RADIUS CoA-Request "The number of malformed RADIUS CoA-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 CoA-Requests." included as malformed CoA-Requests."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA), and Section 2.3, Packet Format." Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 17 } ::= { radiusDynAuthClientEntry 23 }
radiusDynAuthServCoABadAuthenticators OBJECT-TYPE radiusDynAuthServCoABadAuthenticators 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-Request packets which "The number of RADIUS CoA-Request packets which
contained invalid Authenticator field received contained invalid Authenticator field received
from this Dynamic Authorization client." 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), and Section 2.3, Packet Format." Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 18 } ::= { radiusDynAuthClientEntry 24 }
radiusDynAuthServCoAPacketsDropped OBJECT-TYPE radiusDynAuthServCoAPacketsDropped 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 incoming CoA packets from this "The number of incoming CoA packets from this
Dynamic Authorization Client silently discarded Dynamic Authorization Client silently discarded
by the server application for some reason other than by the server application for some reason other than
malformed, bad authenticators or unknown types." malformed, bad authenticators or unknown types."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA), and Section 2.3, Packet Format." Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 19 } ::= { radiusDynAuthClientEntry 25 }
radiusDynAuthServUnknownTypes OBJECT-TYPE radiusDynAuthServUnknownTypes 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 incoming packets of unknown types "The number of incoming packets of unknown types
which were received on the Dynamic Authorization port." which were received on the Dynamic Authorization port."
REFERENCE REFERENCE
"RFC 3576, Section 2.3, Packet Format." "RFC 3576, Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 20 } ::= { radiusDynAuthClientEntry 26 }
-- conformance information -- conformance information
radiusDynAuthServerMIBConformance radiusDynAuthServerMIBConformance
OBJECT IDENTIFIER ::= { radiusDynAuthServerMIB 2 } OBJECT IDENTIFIER ::= { radiusDynAuthServerMIB 2 }
radiusDynAuthServerMIBCompliances radiusDynAuthServerMIBCompliances
OBJECT IDENTIFIER ::= { radiusDynAuthServerMIBConformance 1 } OBJECT IDENTIFIER ::= { radiusDynAuthServerMIBConformance 1 }
radiusDynAuthServerMIBGroups radiusDynAuthServerMIBGroups
OBJECT IDENTIFIER ::= { radiusDynAuthServerMIBConformance 2 } OBJECT IDENTIFIER ::= { radiusDynAuthServerMIBConformance 2 }
-- compliance statements -- compliance statements
radiusAuthServerMIBCompliance MODULE-COMPLIANCE radiusAuthServerMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for entities implementing "The compliance statement for entities implementing
the RADIUS Dynamic Authorization Server." the RADIUS Dynamic Authorization Server."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { radiusDynAuthServerMIBGroup } MANDATORY-GROUPS { radiusDynAuthServerMIBGroup }
GROUP radiusDynAuthServerAuthOnlyGroup
DESCRIPTION
"Only required for Dynamic Authorization Clients that
are supporting Service-Type attributes with value
'Authorize-Only'."
GROUP radiusDynAuthServerNoSessGroup
DESCRIPTION
"This group is not required in case the Dynamic
Authorization Server can not easily determine whether
a session exists or not (e.g., in case of a RADIUS
proxy)."
::= { radiusDynAuthServerMIBCompliances 1 } ::= { radiusDynAuthServerMIBCompliances 1 }
-- units of conformance -- units of conformance
radiusDynAuthServerMIBGroup OBJECT-GROUP radiusDynAuthServerMIBGroup OBJECT-GROUP
OBJECTS { radiusDynAuthServerDisconInvalidClientAddresses, OBJECTS { radiusDynAuthServerDisconInvalidClientAddresses,
radiusDynAuthServerCoAInvalidClientAddresses, radiusDynAuthServerCoAInvalidClientAddresses,
radiusDynAuthServerIdentifier, radiusDynAuthServerIdentifier,
radiusDynAuthClientAddressType, radiusDynAuthClientAddressType,
radiusDynAuthClientAddress, radiusDynAuthClientAddress,
radiusDynAuthServDisconRequests, radiusDynAuthServDisconRequests,
radiusDynAuthServDupDisconRequests, radiusDynAuthServDupDisconRequests,
radiusDynAuthServDisconAcks, radiusDynAuthServDisconAcks,
radiusDynAuthServDisconNaks, radiusDynAuthServDisconNaks,
skipping to change at page 18, line 34 skipping to change at page 19, line 6
radiusDynAuthServCoABadAuthenticators, radiusDynAuthServCoABadAuthenticators,
radiusDynAuthServCoAPacketsDropped, radiusDynAuthServCoAPacketsDropped,
radiusDynAuthServUnknownTypes radiusDynAuthServUnknownTypes
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects providing management of "The collection of objects providing management of
a RADIUS Dynamic Authorization Server." a RADIUS Dynamic Authorization Server."
::= { radiusDynAuthServerMIBGroups 1 } ::= { radiusDynAuthServerMIBGroups 1 }
radiusDynAuthServerAuthOnlyGroup OBJECT-GROUP
OBJECTS { radiusDynAuthServDisconAuthOnlyRequests,
radiusDynAuthServDisconNakAuthOnlyRequests,
radiusDynAuthServCoAAuthOnlyRequests,
radiusDynAuthServCoANakAuthOnlyRequests
}
STATUS current
DESCRIPTION
"The collection of objects supporting the RADIUS
messages including Service-Type attribute with
value 'Autorize Only'."
::= { radiusDynAuthServerMIBGroups 2 }
radiusDynAuthServerNoSessGroup OBJECT-GROUP
OBJECTS { radiusDynAuthServDisconNakSessNoContext,
radiusDynAuthServCoANakSessNoContext
}
STATUS current
DESCRIPTION
"The collection of objects supporting the RADIUS
messages that are referring to non existing sessions."
::= { radiusDynAuthServerMIBGroups 3 }
END END
7. Security Considerations 5. Security Considerations
There are no management objects defined in this MIB module that have There are no management objects defined in this MIB module that have
a MAX-ACCESS clause of read-write and/or read-create. So, if this a MAX-ACCESS clause of read-write and/or read-create. So, if this
MIB module is implemented correctly, then there is no risk that an MIB module is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations module via direct SNMP SET operations
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
skipping to change at page 19, line 38 skipping to change at page 21, line 8
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 The other readable objects are not really considered as being
sensitive or vulnerable. These objects are: sensitive or vulnerable. These objects are:
radiusDynAuthServerDisconInvalidClientAddresses, radiusDynAuthServerDisconInvalidClientAddresses,
radiusDynAuthServerCoAInvalidClientAddresses, radiusDynAuthServerCoAInvalidClientAddresses,
radiusDynAuthServDisconRequests, radiusDynAuthServDisconRequests,
radiusDynAuthServDisconAuthOnlyRequests,
radiusDynAuthServDupDisconRequests, radiusDynAuthServDupDisconRequests,
radiusDynAuthServDisconAcks, radiusDynAuthServDisconAcks,
radiusDynAuthServDisconNaks, radiusDynAuthServDisconNaks,
radiusDynAuthServDisconNakAuthOnlyRequests,
radiusDynAuthServDisconNakSessNoContext,
radiusDynAuthServDisconUserSessRemoved, radiusDynAuthServDisconUserSessRemoved,
radiusDynAuthServMalformedDisconRequests, radiusDynAuthServMalformedDisconRequests,
radiusDynAuthServDisconBadAuthenticators, radiusDynAuthServDisconBadAuthenticators,
radiusDynAuthServDisconPacketsDropped, radiusDynAuthServDisconPacketsDropped,
radiusDynAuthServCoARequests, radiusDynAuthServCoARequests,
radiusDynAuthServCoAAuthOnlyRequests,
radiusDynAuthServDupCoARequests, radiusDynAuthServDupCoARequests,
radiusDynAuthServCoAAcks, radiusDynAuthServCoAAcks,
radiusDynAuthServCoANaks, radiusDynAuthServCoANaks,
radiusDynAuthServCoANakAuthOnlyRequests,
radiusDynAuthServCoANakSessNoContext,
radiusDynAuthServCoAUserSessChanged, radiusDynAuthServCoAUserSessChanged,
radiusDynAuthServMalformedCoARequests, radiusDynAuthServMalformedCoARequests,
radiusDynAuthServCoABadAuthenticators, radiusDynAuthServCoABadAuthenticators,
radiusDynAuthServCoAPacketsDropped, and radiusDynAuthServCoAPacketsDropped, and
radiusDynAuthServUnknownTypes. 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
skipping to change at page 21, line 5 skipping to change at page 22, line 5
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
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
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.
8. 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.
9. Acknowledgements 7. Acknowledgements
This document reuses some of the work done in earlier RADIUS MIB This document reuses some of the work done in earlier RADIUS MIB
specifications [RFC2618] and [RFC2620]. 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, and their comments to this document: Anjaneyulu Pata, Dan Romascanu, Bert
Bert Wijnen. Wijnen, Bernard Aboba, David Nelson, Greg Weber and Glen Zorn.
10. References
10.1 Normative References 8. References
[DYNCLNT] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic 8.1. Normative References
Authorization Client MIB",
draft-decnodder-radext-dynauth-client-mib-01.txt, work in
progress, June 2004.
[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
Information Version 2 (SMIv2)", STD 58, RFC 2578, Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999. April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[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.
[RFC3576] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. [RFC3576] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
Aboba, "Dynamic Authorization Extensions to Remote Aboba, "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", RFC 3576, Authentication Dial In User Service (RADIUS)", RFC 3576,
July 2003. July 2003.
10.2 Informative References [RFC4001] Daniele, M. and et al., "Textual Conventions for Internet
Network Addresses", RFC 4001, February 2005.
8.2. Informative References
[DYNCLNT] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic
Authorization Client MIB",
draft-decnodder-radext-dynauth-client-mib-02.txt, work in
progress, September 2005.
[RFC2618] Aboba, B. and G. Zorn, "RADIUS Authentication Client MIB", [RFC2618] Aboba, B. and G. Zorn, "RADIUS Authentication Client MIB",
RFC 2618, June 1999. RFC 2618, June 1999.
[RFC2618bis]
Nelson, D., "RADIUS Auth Client MIB (IPv6)",
draft-ietf-radext-rfc2618bis-00.txt work in progress,
August 2005.
[RFC2619] Zorn, G. and B. Aboba, "RADIUS Authentication Server MIB", [RFC2619] Zorn, G. and B. Aboba, "RADIUS Authentication Server MIB",
RFC 2619, June 1999. RFC 2619, June 1999.
[RFC2619bis]
Nelson, D., "RADIUS Auth Server MIB (IPv6)",
draft-ietf-radext-rfc2619bis-00.txt work in progress,
August 2005.
[RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB", [RFC2620] Aboba, B. and G. Zorn, "RADIUS Accounting Client MIB",
RFC 2620, June 1999. RFC 2620, June 1999.
[RFC2620bis]
Nelson, D., "RADIUS Acct Client MIB (IPv6)",
draft-ietf-radext-rfc2620bis-00.txt work in progress,
August 2005.
[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.
[RFC2621bis]
Nelson, D., "RADIUS Acct Server MIB (IPv6)",
draft-ietf-radext-rfc2621bis-00.txt work in progress,
August 2005.
[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
 End of changes. 85 change blocks. 
130 lines changed or deleted 316 lines changed or added

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