draft-ietf-radext-dynauth-server-mib-06.txt   rfc4673.txt 
Network Working Group S. De Cnodder Network Working Group S. De Cnodder
Internet-Draft Alcatel Request for Comments: 4673 Alcatel
Expires: December 17, 2006 N. Jonnala Category: Informational N. Jonnala
M. Chiba M. Chiba
Cisco Systems, Inc. Cisco Systems, Inc.
June 15, 2006 September 2006
Dynamic Authorization Server MIB
draft-ietf-radext-dynauth-server-mib-06.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at RADIUS Dynamic Authorization Server MIB
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on December 17, 2006. This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). 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 Remote Authentication Dial In User In particular, it describes the Remote Authentication Dial-In User
Service (RADIUS) [RFC2865] Dynamic Authorization Server (DAS) Service (RADIUS) (RFC 2865) Dynamic Authorization Server (DAS)
functions that support the dynamic authorization extensions as 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 ....................................................2
1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Notation ......................................2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology ................................................2
2. The Internet-Standard Management Framework . . . . . . . . . . 4 2. The Internet-Standard Management Framework ......................2
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Overview ........................................................3
4. RADIUS Dynamic Authorization Server MIB Definitions . . . . . 7 4. RADIUS Dynamic Authorization Server MIB Definitions .............5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 22 5. Security Considerations ........................................20
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 23 6. IANA Considerations ............................................21
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24 7. Acknowledgements ...............................................21
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8. References .....................................................21
8.1. Normative References . . . . . . . . . . . . . . . . . . . 25 8.1. Normative References ......................................21
8.2. Informative References . . . . . . . . . . . . . . . . . . 25 8.2. Informative References ....................................22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27
Intellectual Property and Copyright Statements . . . . . . . . . . 28
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 [RFC2618bis] and [RFC2620bis], accounting clients as described in [RFC4668] and [RFC4670],
respectively. respectively.
-- RFC Ed.: references [DYNCLNT], [RFC2618bis], [RFC2619bis], 1.1. Requirements Notation
-- [RFC2620bis], and [RFC2621bis] should be replaced by
-- references to the corresponding RFC.
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)
The component that resides on the NAS which processes the Disconnect The component that resides on the NAS that processes the Disconnect
and Change-of-Authorization (CoA) Request packets [RFC3576] sent by and Change-of-Authorization (CoA) Request packets [RFC3576] sent by
the Dynamic Authorization Client. the Dynamic Authorization Client.
Dynamic Authorization Client (DAC) Dynamic Authorization Client (DAC)
The component which sends Disconnect and CoA-Request packets to the The component that sends Disconnect and CoA-Request packets to the
Dynamic Authorization Server. While often residing on the RADIUS Dynamic Authorization Server. Although this component often resides
server, it is also possible for this component to be located on a on the RADIUS server, it is also possible for it to be located on a
separate host, such as a Rating Engine. 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.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
[RFC3410]. [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base, or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC2578 [RFC2578], STD 58, RFC2579 [RFC2579] and STD 58, RFC2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Overview 3. Overview
"Dynamic Authorization Extensions to RADIUS" [RFC3576] defines the "Dynamic Authorization Extensions to RADIUS" [RFC3576] defines the
operation of Disconnect-Request, Disconnect-ACK, Disconnect-NAK, CoA- operation of Disconnect-Request, Disconnect-ACK, Disconnect-NAK,
Request, CoA-ACK and CoA-NAK packets. Typically NAS devices CoA-Request, CoA-ACK, and CoA-NAK packets. Typically, NAS devices
implement the DAS function, and thus would be expected to implement implement the DAS function, and thus would be expected to implement
the RADIUS Dynamic Authorization Server MIB, while DACs implement the the RADIUS Dynamic Authorization Server MIB, whereas DACs implement
client function, and thus would be expected to implement the RADIUS the client function and thus would be expected to implement the
Dynamic Authorization Client MIB. RADIUS Dynamic Authorization Client MIB.
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:
[RFC2618bis] describes the MIB for a RADIUS Auth Client MIB. [RFC4668] describes the MIB for a RADIUS Auth Client MIB.
[RFC2619bis] describes the MIB for a RADIUS Auth Server MIB. [RFC4669] describes the MIB for a RADIUS Auth Server MIB.
[RFC2620bis] describes the MIB for a RADIUS Acct Client MIB. [RFC4670] describes the MIB for a RADIUS Acct Client MIB.
[RFC2621bis] describes the MIB for a RADIUS Acct Server MIB. [RFC4671] describes the MIB for a RADIUS Acct Server MIB.
[DYNCLNT] describes the MIB for a RADIUS Dynamic Authorization [RFC4672] describes the MIB for a RADIUS Dynamic Auth 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, any one MIB can be implemented Authorization Server. However, any one MIB can be implemented
without implementing any of the other MIBs, i.e. the MIBs have no without implementing any of the other MIBs; i.e., the MIBs have no
dependencies on each other. A typical case would be for a device to dependencies on each other. A typical case would be for a device to
implement the MIBs RADIUS authentication server, RADIUS accounting implement the MIBs RADIUS authentication server, RADIUS accounting
server and RADIUS Dynamic Authorization Client. A RADIUS proxy might server, and RADIUS Dynamic Authorization Client. A RADIUS proxy
implement any, all or a subset of the MIBs listed above and the MIB might implement any, all, or a subset of the MIBs listed above and
as defined in this document. the MIB as defined in this document.
+---------------+ +---------------+ +---------------+ +---------------+
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, and 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.
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, Counter32, Integer32, mib-2,
TimeTicks FROM SNMPv2-SMI -- [RFC2578] TimeTicks 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 "200608290000Z" -- 29 August 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 5, line 50
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 to Remote side of the Dynamic Authorization Extensions to the
Authentication Dial In User Service (RADIUS) protocol. Remote Authentication Dial-In User Service (RADIUS)
protocol. Copyright (C) The Internet Society (2006).
Copyright (C) The Internet Society (2006). Initial Initial version as published in RFC 4673; for full
version as published in RFC yyyy; legal notices see the RFC itself."
for full legal notices see the RFC itself."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note REVISION "200608290000Z" -- 29 August 2006
DESCRIPTION "Initial version as published in RFC yyyy." DESCRIPTION "Initial version as published in RFC 4673."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note ::= { mib-2 146 }
::= { mib-2 xxx }
-- The value xxx to be assigned by IANA.
radiusDynAuthServerMIBObjects OBJECT IDENTIFIER ::= radiusDynAuthServerMIBObjects OBJECT IDENTIFIER ::=
{ radiusDynAuthServerMIB 1 } { radiusDynAuthServerMIB 1 }
radiusDynAuthServerScalars OBJECT IDENTIFIER ::= radiusDynAuthServerScalars 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-Request packets received from "The number of Disconnect-Request packets received from
unknown addresses. This counter may experience a unknown addresses. This counter may experience a
discontinuity when the DAS module (re)starts as discontinuity when the DAS module (re)starts, as
indicated by the value of indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
::= { radiusDynAuthServerScalars 1 } ::= { radiusDynAuthServerScalars 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-Request packets received from unknown "The number of CoA-Request packets received from unknown
addresses. This counter may experience a discontinuity addresses. This counter may experience a discontinuity
when the DAS module (re)starts as indicated by the value when the DAS module (re)starts, as indicated by the
of radiusDynAuthServerCounterDiscontinuity." value of radiusDynAuthServerCounterDiscontinuity."
::= { radiusDynAuthServerScalars 2 } ::= { radiusDynAuthServerScalars 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. This is not necessarily the same as sysName in Server. This is not necessarily the same as sysName in
MIB II." MIB II."
skipping to change at page 10, line 19 skipping to change at page 8, line 15
} }
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
"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."
skipping to change at page 11, line 24 skipping to change at page 9, line 20
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 that include "The number of RADIUS Disconnect-Requests that include
a Service-Type attribute with value 'Authorize Only' a Service-Type attribute with value 'Authorize Only'
received from this Dynamic Authorization Client. This received from this Dynamic Authorization Client. This
counter may experience a discontinuity when the DAS counter may experience a discontinuity when the DAS
module (re)starts as indicated by the value of module (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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
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. This counter may experience a discontinuity Client. This counter may experience a discontinuity
when the DAS module (re)starts as indicated by the when the DAS module (re)starts, as indicated by the
value of radiusDynAuthServerCounterDiscontinuity." value of radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 6 } ::= { 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 sent to "The number of RADIUS Disconnect-ACK packets sent to
this Dynamic Authorization Client. This counter may this Dynamic Authorization Client. This counter may
experience a discontinuity when the DAS module experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 7 } ::= { 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. This sent to this Dynamic Authorization Client. This
includes the RADIUS Disconnect-NAK packets sent includes the RADIUS Disconnect-NAK packets sent
with a Service-Type attribute with value 'Authorize with a Service-Type attribute with value 'Authorize
Only' and the RADIUS Disconnect-NAK packets sent Only' and the RADIUS Disconnect-NAK packets sent
because no session context was found. This counter because no session context was found. This counter
may experience a discontinuity when the DAS module may experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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 that "The number of RADIUS Disconnect-NAK packets that
include a Service-Type attribute with value include a Service-Type attribute with value
'Authorize Only' sent to this Dynamic Authorization 'Authorize Only' sent to this Dynamic Authorization
Client. This counter may experience a discontinuity Client. This counter may experience a discontinuity
when the DAS module (re)starts as indicated by the when the DAS module (re)starts, as indicated by the
value of radiusDynAuthServerCounterDiscontinuity." value of radiusDynAuthServerCounterDiscontinuity."
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
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
because no session context was found. This counter may because no session context was found. This counter may
experience a discontinuity when the DAS module experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)." "RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthClientEntry 10 } ::= { 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 can remove multiple user sessions. In cases where
that this Dynamic Authorization Server has no this Dynamic Authorization Server has no
knowledge of the number of user sessions that knowledge of the number of user sessions that
are affected by a single request, for each such are affected by a single request, each such
Disconnect-Request, it will count as a single Disconnect-Request will count as a single
affected user session only. This counter may experience affected user session only. This counter may experience
a discontinuity when the DAS module (re)starts as a discontinuity when the DAS module (re)starts, as
indicated by the value of indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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. This counter included as malformed Disconnect-Requests. This counter
may experience a discontinuity when the DAS module may experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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 12 } ::= { 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 that contained an invalid Authenticator field
received from this Dynamic Authorization Client. This received from this Dynamic Authorization Client. This
counter may experience a discontinuity when the DAS counter may experience a discontinuity when the DAS
module (re)starts as indicated by the value of module (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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 13 } ::= { 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. This counter may experience a discontinuity types. This counter may experience a discontinuity
when the DAS module (re)starts as indicated by the when the DAS module (re)starts, as indicated by the
value of radiusDynAuthServerCounterDiscontinuity." value of radiusDynAuthServerCounterDiscontinuity."
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 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 also 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'. This counter may with value 'Authorize Only'. This counter may
experience a discontinuity when the DAS module experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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 that include a "The number of RADIUS CoA-requests that include a
Service-Type attribute with value 'Authorize Only' Service-Type attribute with value 'Authorize Only'
received from this Dynamic Authorization Client. This received from this Dynamic Authorization Client. This
counter may experience a discontinuity when the DAS counter may experience a discontinuity when the DAS
module (re)starts as indicated by the value of module (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of duplicate RADIUS CoA-Request packets "The number of duplicate RADIUS CoA-Request packets
received from this Dynamic Authorization Client. This received from this Dynamic Authorization Client. This
counter may experience a discontinuity when the DAS counter may experience a discontinuity when the DAS
module (re)starts as indicated by the value of module (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 17 } ::= { 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 sent to this "The number of RADIUS CoA-ACK packets sent to this
Dynamic Authorization Client. This counter may Dynamic Authorization Client. This counter may
experience a discontinuity when the DAS module experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 18 } ::= { 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 sent to "The number of RADIUS CoA-NAK packets sent to
this Dynamic Authorization Client. This includes this Dynamic Authorization Client. This includes
the RADIUS CoA-NAK packets sent with a Service-Type the RADIUS CoA-NAK packets sent with a Service-Type
attribute with value 'Authorize Only' and the RADIUS attribute with value 'Authorize Only' and the RADIUS
CoA-NAK packets sent because no session context was CoA-NAK packets sent because no session context was
found. This counter may experience a discontinuity found. This counter may experience a discontinuity
when the DAS module (re)starts as indicated by the when the DAS module (re)starts, as indicated by the
value of radiusDynAuthServerCounterDiscontinuity." value of radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"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 that include a "The number of RADIUS CoA-NAK packets that include a
Service-Type attribute with value 'Authorize Only' Service-Type attribute with value 'Authorize Only'
sent to this Dynamic Authorization Client. This counter sent to this Dynamic Authorization Client. This counter
may experience a discontinuity when the DAS module may experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of RADIUS CoA-NAK packets sent to this "The number of RADIUS CoA-NAK packets sent to this
Dynamic Authorization Client because no session context Dynamic Authorization Client because no session context
was found. This counter may experience a discontinuity was found. This counter may experience a discontinuity
when the DAS module (re)starts as indicated by the when the DAS module (re)starts, as indicated by the
value of radiusDynAuthServerCounterDiscontinuity." value of radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization "RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)." Messages (CoA)."
::= { radiusDynAuthClientEntry 21 } ::= { 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 cases where
this Dynamic Authorization Server has no knowledge of this Dynamic Authorization Server has no knowledge of
the number of user sessions that are affected by a the number of user sessions that are affected by a
single request, for each such CoA-Request, it will single request, each such CoA-Request will
count as a single affected user session only. This count as a single affected user session only. This
counter may experience a discontinuity when the DAS counter may experience a discontinuity when the DAS
module (re)starts as indicated by the value of module (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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
DESCRIPTION DESCRIPTION
"The number of malformed RADIUS CoA-Request packets "The number of malformed RADIUS CoA-Request packets
received from this Dynamic Authorization Client. Bad received from this Dynamic Authorization Client. Bad
authenticators and unknown types are not included as authenticators and unknown types are not included as
malformed CoA-Requests. This counter may experience a malformed CoA-Requests. This counter may experience a
discontinuity when the DAS module (re)starts as discontinuity when the DAS module (re)starts, as
indicated by the value of indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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 23 } ::= { 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 that
contained invalid Authenticator field received contained an invalid Authenticator field received
from this Dynamic Authorization Client. This counter from this Dynamic Authorization Client. This counter
may experience a discontinuity when the DAS module may experience a discontinuity when the DAS module
(re)starts as indicated by the value of (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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 24 } ::= { 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. This malformed, bad authenticators, or unknown types. This
counter may experience a discontinuity when the DAS counter may experience a discontinuity when the DAS
module (re)starts as indicated by the value of module (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
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 25 } ::= { 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 which "The number of incoming packets of unknown types that
were received on the Dynamic Authorization port. This were received on the Dynamic Authorization port. This
counter may experience a discontinuity when the DAS counter may experience a discontinuity when the DAS
module (re)starts as indicated by the value of module (re)starts, as indicated by the value of
radiusDynAuthServerCounterDiscontinuity." radiusDynAuthServerCounterDiscontinuity."
REFERENCE REFERENCE
"RFC 3576, Section 2.3, Packet Format." "RFC 3576, Section 2.3, Packet Format."
::= { radiusDynAuthClientEntry 26 } ::= { radiusDynAuthClientEntry 26 }
radiusDynAuthServerCounterDiscontinuity OBJECT-TYPE radiusDynAuthServerCounterDiscontinuity OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
UNITS "hundredths of a second" UNITS "hundredths of a second"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 20, line 20 skipping to change at page 18, line 16
globally unique IPv6 addresses." globally unique IPv6 addresses."
GROUP radiusDynAuthServerAuthOnlyGroup GROUP radiusDynAuthServerAuthOnlyGroup
DESCRIPTION DESCRIPTION
"Only required for Dynamic Authorization Clients that "Only required for Dynamic Authorization Clients that
are supporting Service-Type attributes with value are supporting Service-Type attributes with value
'Authorize-Only'." 'Authorize-Only'."
GROUP radiusDynAuthServerNoSessGroup GROUP radiusDynAuthServerNoSessGroup
DESCRIPTION DESCRIPTION
"This group is not required in case the Dynamic "This group is not required if the Dynamic
Authorization Server can not easily determine whether Authorization Server can not easily determine whether
a session exists or not (e.g., in case of a RADIUS a session exists (e.g., in case of a RADIUS
proxy)." 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,
skipping to change at page 21, line 33 skipping to change at page 19, line 29
value 'Authorize 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."
::= { radiusDynAuthServerMIBGroups 3 } ::= { radiusDynAuthServerMIBGroups 3 }
END END
5. 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
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
radiusDynAuthClientAddress and radiusDynAuthClientAddressType radiusDynAuthClientAddress and radiusDynAuthClientAddressType
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
DAS is communicating. This information could be useful in mounting the DAS is communicating. This information could be useful in
an attack on the DAC. mounting 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.
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 23, line 5 skipping to change at page 21, 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.
6. IANA considerations 6. IANA Considerations
IANA is requested to assign an OID xxx under mib-2. The IANA has assigned OID number 146 under mib-2.
7. Acknowledgements 7. Acknowledgements
The authors would also like to acknowledge the following people for The authors would like to acknowledge the following people for their
their comments on this document: Bernard Aboba, Alan DeKok, David comments on this document: Bernard Aboba, Alan DeKok, David Nelson,
Nelson, Anjaneyulu Pata, Dan Romascanu, Juergen Schoenwaelder, Greg Anjaneyulu Pata, Dan Romascanu, Juergen Schoenwaelder, Greg Weber,
Weber, Bert Wijnen and Glen Zorn. 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", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Structure of Management "Structure of Management Information Version 2 (SMIv2)",
Information Version 2 (SMIv2)", STD 58, RFC 2578, STD 58, RFC 2578, April 1999.
April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Textual Conventions for "Textual Conventions for SMIv2", STD 58, RFC 2579, April
SMIv2", STD 58, RFC 2579, April 1999. 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Rose, M., and S. Waldbusser, "Conformance Statements for "Conformance Statements for SMIv2", STD 58, RFC 2580,
SMIv2", STD 58, RFC 2580, April 1999. April 1999.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. 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.
[RFC4001] Daniele, M. and et al., "Textual Conventions for Internet [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Network Addresses", RFC 4001, February 2005. Schoenwaelder, "Textual Conventions for Internet 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 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
Authorization Client MIB", "Remote Authentication Dial In User Service (RADIUS)", RFC
draft-ietf-radext-dynauth-client-mib-05.txt, work in 2865, June 2000.
progress, December 2005.
[RFC2618bis] [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Nelson, D., "RADIUS Auth Client MIB (IPv6)", "Introduction and Applicability Statements for Internet-
draft-ietf-radext-rfc2618bis-01.txt work in progress, Standard Management Framework", RFC 3410, December 2002.
October 2005.
[RFC2619bis] [RFC4668] Nelson, D., "RADIUS Authentication Client MIB for IPv6",
Nelson, D., "RADIUS Auth Server MIB (IPv6)", RFC 4668, August 2006.
draft-ietf-radext-rfc2619bis-01.txt work in progress,
October 2005.
[RFC2620bis] [RFC4669] Nelson, D., "RADIUS Authentication Server MIB for IPv6",
Nelson, D., "RADIUS Acct Client MIB (IPv6)", RFC 4669, August 2006.
draft-ietf-radext-rfc2620bis-01.txt work in progress,
October 2005.
[RFC2621bis] [RFC4670] Nelson, D., "RADIUS Accounting Client MIB for IPv6", RFC
Nelson, D., "RADIUS Acct Server MIB (IPv6)", 4670, August 2006.
draft-ietf-radext-rfc2621bis-01.txt work in progress,
October 2005.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC4671] Nelson, D., "RADIUS Accounting Server MIB for IPv6", RFC
"Remote Authentication Dial In User Service (RADIUS)", 4671, August 2006.
RFC 2865, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC4672] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic
"Introduction and Applicability Statements for Internet- Authorization Client MIB", RFC 4672, September 2006.
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
Phone: +32 3 240 85 15 Phone: +32 3 240 85 15
Email: stefaan.de_cnodder@alcatel.be EMail: stefaan.de_cnodder@alcatel.be
Nagi Reddy Jonnala Nagi Reddy Jonnala
Cisco Systems, Inc. Cisco Systems, Inc.
Divyasree Chambers, B Wing, O'Shaugnessy Road Divyasree Chambers, B Wing, O'Shaugnessy Road
Bangalore-560027, India Bangalore-560027, India
Phone: +91 94487 60828 Phone: +91 94487 60828
Email: njonnala@cisco.com EMail: njonnala@cisco.com
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
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 28, line 29 skipping to change at page 24, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 90 change blocks. 
197 lines changed or deleted 160 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/