Network Working Group S. De Cnodder
Request for Comments: 4672 Alcatel
Category: Informational N. Jonnala
M. Chiba
Cisco Systems, Inc.
September 2006
RADIUS Dynamic Authorization Client MIB
Status of This Memo
このメモのステータス
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 (C) The Internet Society (2006).
著作権（C）インターネット協会（2006）。
Abstract
抽象
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes the Remote Authentication Dial-In User Service (RADIUS) (RFC2865) Dynamic Authorization Client (DAC) functions that support the dynamic authorization extensions as defined in RFC 3576.
このメモは、インターネットコミュニティでのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。特に、それは、リモート認証ダイヤルインユーザーサービス（RADIUS）RFC 3576で定義されているダイナミックな承認拡張をサポート（RFC2865）のダイナミックな承認クライアント（DAC）の機能について説明します。
Table of Contents
目次
1. Introduction ....................................................2
1.1. Requirements Notation ......................................2
1.2. Terminology ................................................2
2. The Internet-Standard Management Framework ......................3
3. Overview ........................................................3
4. RADIUS Dynamic Authorization Client MIB Definitions .............3
5. Security Considerations ........................................19
6. IANA Considerations ............................................20
7. Acknowledgements ...............................................20
8. References .....................................................21
8.1. Normative References ......................................21
8.2. Informative References ....................................21
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes the Remote Authentication Dial-In User Service (RADIUS) [RFC2865] Dynamic Authorization Client (DAC) functions that support the dynamic authorization extensions as defined in RFC 3576.
このメモは、インターネットコミュニティでのネットワーク管理プロトコルで使用するための管理情報ベース（MIB）の一部を定義します。特に、リモート認証ダイヤルインユーザーサービス（RADIUS）[RFC2865]動的認可クライアントRFC 3576で定義されるように動的認可の拡張をサポートする（DAC）の機能を説明しています。
It is becoming increasingly important to support Dynamic Authorization extensions on the network access server (NAS) devices to handle the Disconnect and Change-of-Authorization (CoA) messages, as described in [RFC3576]. As a result, the effective management of RADIUS Dynamic Authorization entities is of considerable importance. This RADIUS Dynamic Authorization Client MIB complements the managed objects used for managing RADIUS authentication and accounting servers, as described in [RFC4669] and [RFC4671], respectively.
[RFC3576]で説明したように接続解除および変更の承認（COA）メッセージを処理するためのネットワーク・アクセス・サーバ（NAS）デバイス上のダイナミックな承認拡張をサポートすることがますます重要になってきています。その結果、RADIUSダイナミックな承認エンティティの効果的な管理はかなり重要です。このRADIUSダイナミックな承認クライアントMIBは、それぞれ、[RFC4669]で説明したように、RADIUS認証およびアカウンティングサーバを管理するために使用され、管理対象オブジェクトを補完し、[RFC4671]。
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].
この文書のキーワード "MUST"、 "MUST NOT"、 "REQUIRED"、、、、 "べきではない" "べきである" "ないもの" "ものとし"、 "推奨"、 "MAY"、および "OPTIONAL" はあります[RFC2119]に記載されているように解釈されます。
Dynamic Authorization Server (DAS)
ダイナミックな承認サーバー（DAS）
The component that resides on the NAS that processes the Disconnect and Change-of-Authorization (CoA) Request packets [RFC3576] sent by the Dynamic Authorization Client.
動的認可クライアントから送信された切断および変更の承認（COA）要求パケット[RFC3576]を処理するNAS上に存在するコンポーネント。
Dynamic Authorization Client (DAC)
ダイナミックな承認クライアント（DAC）
The component that sends Disconnect and CoA-Request packets to the Dynamic Authorization Server. Although this component often resides on the RADIUS server, it is also possible for this component to be located on a separate host, such as a Rating Engine.
ダイナミックな承認サーバーへの接続解除とCoA-Requestパケットを送信するコンポーネント。このコンポーネントは、しばしば、RADIUSサーバ上に存在するが、この成分は、このような評価エンジンとして、別のホスト上に位置するため、それも可能です。
Dynamic Authorization Server Port
ダイナミックな承認サーバポート
The UDP port on which the Dynamic Authorization Server listens for the Disconnect and CoA requests sent by the Dynamic Authorization Client.
ダイナミックな承認Serverはダイナミックな承認クライアントによって送信された切断とCoAの要求を待機するUDPポート。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of [RFC3410].
現在のインターネット標準の管理フレームワークを記述したドキュメントの詳細な概要については、[RFC3410]のセクション7を参照してください。
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, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580 [RFC2580].
管理対象オブジェクトが仮想情報店を介してアクセスされ、管理情報ベースまたはMIBと呼ばれます。 MIBオブジェクトは、一般的に簡易ネットワーク管理プロトコル（SNMP）を介してアクセスされます。 MIBのオブジェクトは、管理情報（SMI）の構造で定義されたメカニズムを使用して定義されています。このメモは、STD 58、RFC 2578 [RFC2578]、STD 58、RFC 2579 [RFC2579]に記載されているのSMIv2、およびSTD 58、RFC 2580 [RFC2580]に準拠しているMIBモジュールを指定します。
"Dynamic Authorization Extensions to RADIUS" [RFC3576] defines the operation of Disconnect-Request, Disconnect-ACK, Disconnect-NAK, CoA-Request, CoA-ACK, and CoA-NAK packets. [RFC4673] defines the Dynamic Authorization Server MIB and the relationship with other MIB modules. This MIB module for the Dynamic Authorization Client contains the following:
"動的認可RADIUSへの拡張" [RFC3576]は切断リクエスト、切断-ACK、切断-NAK、CoAのリクエスト、アシルCoA-ACK、及びアシルCoA-NAKパケットの動作を規定します。 [RFC4673]は、動的認可サーバMIBおよび他のMIBモジュールとの関係を定義します。ダイナミックな承認クライアントのためのこのMIBモジュールには、次のものが含まれています。
2. One Dynamic Authorization Server table. This table contains one row for each DAS with which the DAC shares a secret.
2.一つのダイナミックな承認Serverテーブル。この表は、DACが秘密を共有する各DASのための1つの行が含ま。
RADIUS-DYNAUTH-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32, Integer32, mib-2, TimeTicks FROM SNMPv2-SMI -- [RFC2578] SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB -- [RFC4001] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; -- [RFC2580]
輸入MODULE-IDENTITY、OBJECT-TYPE、Counter32の、Gauge32、Integer32の、MIB-2のSNMPv2-SMIからの時間刻み - [RFC2578] SNMP-FRAMEWORK-MIBかられるSnmpAdminString - [RFC3411]のInetAddressType、InetAddressの、InetPortNumber INET-ADDRESS FROM -MIB - [RFC4001] MODULE-COMPLIANCE、オブジェクト・グループのSNMPv2-CONF FROM。 - [RFC2580]
radiusDynAuthClientMIB MODULE-IDENTITY LAST-UPDATED "200608290000Z" -- 29 August 2006 ORGANIZATION "IETF RADEXT Working Group" CONTACT-INFO " Stefaan De Cnodder
radiusDynAuthClientMIBのMODULE-IDENTITY LAST-UPDATED "200608290000Z" - 2006年8月29日ORGANIZATION "IETF RADEXTワーキンググループ" CONTACT-INFO "StefaanデCnodder
Alcatel
Francis Wellesplein 1
B-2018 Antwerp
Belgium
Phone: +32 3 240 85 15 EMail: stefaan.de_cnodder@alcatel.be
電話：+32 3 240 85 15 Eメール：stefaan.de_cnodder@alcatel.be
Nagi Reddy Jonnala Cisco Systems, Inc. Divyasree Chambers, B Wing, O'Shaugnessy Road, Bangalore-560027, India.
ナギレディJonnalaシスコシステムズ、株式会社Divyasreeチェンバース、B棟、O'Shaugnessyロード、バンガロール - 560027、インド。
Phone: +91 94487 60828 EMail: njonnala@cisco.com
電話：+91 94487 60828 Eメール：njonnala@cisco.com
Murtaza Chiba Cisco Systems, Inc. 170 West Tasman Dr. San Jose CA, 95134
Murtaza千葉シスコシステムズ、株式会社170西タスマン博士サンノゼCA、95134
Phone: +1 408 525 7198 EMail: mchiba@cisco.com " DESCRIPTION "The MIB module for entities implementing the client side of the Dynamic Authorization Extensions to the Remote Authentication Dial-In User Service (RADIUS) protocol. Copyright (C) The Internet Society (2006). Initial version as published in RFC 4672; for full legal notices see the RFC itself."
電話：+1 408 525 7198 Eメール：mchiba@cisco.com「DESCRIPTION」リモート認証ダイヤルインユーザーサービス（RADIUS）プロトコルにダイナミックな承認拡張機能のクライアント側を実装するエンティティのためのMIBモジュール。著作権（C）インターネット協会（2006）。 RFC 4672で公開された最初のバージョン。完全な適法な通知についてはRFC自体を参照してください。」
REVISION "200609290000Z" -- 29 August 2006
DESCRIPTION "Initial version as published in RFC 4672"
::= { mib-2 145 }
radiusDynAuthClientMIBObjects OBJECT IDENTIFIER ::=
{ radiusDynAuthClientMIB 1 }
radiusDynAuthClientScalars OBJECT IDENTIFIER ::=
{ radiusDynAuthClientMIBObjects 1 }
radiusDynAuthClientDisconInvalidServerAddresses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of Disconnect-Ack and Disconnect-NAK packets
radiusDynAuthClientDisconInvalidServerAddressesのOBJECT-TYPE SYNTAXカウンタACCESS read-only説明「切断-ACKおよび切断-NAKパケットの数
received from unknown addresses. This counter may
experience a discontinuity when the DAC module
(re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
::= { radiusDynAuthClientScalars 1 }
radiusDynAuthClientCoAInvalidServerAddresses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of CoA-Ack and CoA-NAK packets received from
unknown addresses. Disconnect-NAK packets received
from unknown addresses. This counter may experience a
discontinuity when the DAC module (re)starts, as
indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
::= { radiusDynAuthClientScalars 2 }
radiusDynAuthServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusDynAuthServerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the RADIUS Dynamic
Authorization Servers with which the client shares a
secret."
::= { radiusDynAuthClientMIBObjects 2 }
radiusDynAuthServerEntry OBJECT-TYPE
SYNTAX RadiusDynAuthServerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) representing one Dynamic
Authorization Server with which the client shares a
secret."
INDEX { radiusDynAuthServerIndex }
::= { radiusDynAuthServerTable 1 }
RadiusDynAuthServerEntry ::= SEQUENCE {
radiusDynAuthServerIndex Integer32,
radiusDynAuthServerAddressType InetAddressType,
radiusDynAuthServerAddress InetAddress,
radiusDynAuthServerClientPortNumber InetPortNumber,
radiusDynAuthServerID SnmpAdminString,
radiusDynAuthClientRoundTripTime TimeTicks,
radiusDynAuthClientDisconRequests Counter32, radiusDynAuthClientDisconAuthOnlyRequests Counter32,
radiusDynAuthClientDisconRetransmissions Counter32,
radiusDynAuthClientDisconAcks Counter32,
radiusDynAuthClientDisconNaks Counter32,
radiusDynAuthClientDisconNakAuthOnlyRequest Counter32,
radiusDynAuthClientDisconNakSessNoContext Counter32,
radiusDynAuthClientMalformedDisconResponses Counter32,
radiusDynAuthClientDisconBadAuthenticators Counter32,
radiusDynAuthClientDisconPendingRequests Gauge32,
radiusDynAuthClientDisconTimeouts Counter32,
radiusDynAuthClientDisconPacketsDropped Counter32,
radiusDynAuthClientCoARequests Counter32,
radiusDynAuthClientCoAAuthOnlyRequest Counter32,
radiusDynAuthClientCoARetransmissions Counter32,
radiusDynAuthClientCoAAcks Counter32,
radiusDynAuthClientCoANaks Counter32,
radiusDynAuthClientCoANakAuthOnlyRequest Counter32,
radiusDynAuthClientCoANakSessNoContext Counter32,
radiusDynAuthClientMalformedCoAResponses Counter32,
radiusDynAuthClientCoABadAuthenticators Counter32,
radiusDynAuthClientCoAPendingRequests Gauge32,
radiusDynAuthClientCoATimeouts Counter32,
radiusDynAuthClientCoAPacketsDropped Counter32,
radiusDynAuthClientUnknownTypes Counter32,
radiusDynAuthClientCounterDiscontinuity TimeTicks
}
radiusDynAuthServerIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A number uniquely identifying each RADIUS Dynamic
Authorization Server with which this Dynamic
Authorization Client communicates. This number is
allocated by the agent implementing this MIB module
and is unique in this context."
::= { radiusDynAuthServerEntry 1 }
radiusDynAuthServerAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of IP address of the RADIUS Dynamic
Authorization Server referred to in this table entry."
::= { radiusDynAuthServerEntry 2 }
radiusDynAuthServerAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address value of the RADIUS Dynamic
Authorization Server referred to in this table entry
using the version neutral IP address format. The type
of this address is determined by the value of the
radiusDynAuthServerAddressType object."
::= { radiusDynAuthServerEntry 3 }
radiusDynAuthServerClientPortNumber OBJECT-TYPE
SYNTAX InetPortNumber (1..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UDP destination port that the RADIUS Dynamic
Authorization Client is using to send requests to this
server. The value zero is invalid."
::= { radiusDynAuthServerEntry 4 }
radiusDynAuthServerID OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-Identifier of the RADIUS Dynamic Authorization
Server referred to in this table entry. This is not
necessarily the same as sysName in MIB II."
REFERENCE
"RFC 2865, Section 5.32, NAS-Identifier."
::= { radiusDynAuthServerEntry 5 }
radiusDynAuthClientRoundTripTime OBJECT-TYPE
SYNTAX TimeTicks
UNITS "hundredths of a second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time interval (in hundredths of a second) between
the most recent Disconnect or CoA request and the
receipt of the corresponding Disconnect or CoA reply.
A value of zero is returned if no reply has been
received yet from this server."
::= { radiusDynAuthServerEntry 6 }
radiusDynAuthClientDisconRequests OBJECT-TYPE
SYNTAX Counter32
UNITS "requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-Requests sent
to this Dynamic Authorization Server. This also
includes the RADIUS Disconnect-Requests that have a
Service-Type attribute with value 'Authorize Only'.
Disconnect-NAK packets received from unknown addresses.
This counter may experience a discontinuity when the
DAC module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 7 }
radiusDynAuthClientDisconAuthOnlyRequests OBJECT-TYPE
SYNTAX Counter32
UNITS "requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-Requests that include a
Service-Type attribute with value 'Authorize Only'
sent to this Dynamic Authorization Server.
Disconnect-NAK packets received from unknown addresses.
This counter may experience a discontinuity when the
DAC module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 8 }
radiusDynAuthClientDisconRetransmissions OBJECT-TYPE SYNTAX Counter32 UNITS "retransmissions" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS Disconnect-request packets retransmitted to this RADIUS Dynamic Authorization Server. Disconnect-NAK packets received from unknown addresses. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity." REFERENCE
radiusDynAuthClientDisconRetransmissions OBJECT-TYPE SYNTAX Counter32ユニットを「再送信」MAX-ACCESS read-onlyステータス現在の説明「このRADIUSダイナミックな承認サーバに再送信RADIUS外し要求パケットの数。外し-NAKパケットが未知のアドレスから受信した。このカウンタは経験すること不連続DACモジュールが（再）radiusDynAuthClientCounterDiscontinuityの値によって示されるように、起動時に。」参照
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 9 }
radiusDynAuthClientDisconAcks OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-ACK packets
received from this Dynamic Authorization Server. This
counter may experience a discontinuity when the DAC
module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 10 }
radiusDynAuthClientDisconNaks OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-NAK packets
received from this Dynamic Authorization Server.
This includes the RADIUS Disconnect-NAK packets
received with a Service-Type attribute with value
'Authorize Only' and the RADIUS Disconnect-NAK
packets received if no session context was found. This
counter may experience a discontinuity when the DAC
module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 11 }
radiusDynAuthClientDisconNakAuthOnlyRequest OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-NAK packets
that include a Service-Type attribute with value
'Authorize Only' received from this Dynamic
Authorization Server. This counter may experience a
discontinuity when the DAC module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 12 }
radiusDynAuthClientDisconNakSessNoContext OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-NAK packets
received from this Dynamic Authorization Server
because no session context was found; i.e., it
includes an Error-Cause attribute with value 503
('Session Context Not Found'). This counter may
experience a discontinuity when the DAC module
(re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 13 }
radiusDynAuthClientMalformedDisconResponses OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of malformed RADIUS Disconnect-Ack and
Disconnect-NAK packets received from this Dynamic
Authorization Server. Bad authenticators and unknown
types are not included as malformed Disconnect-Ack and
Disconnect-NAK packets. This counter may experience a
discontinuity when the DAC module (re)starts, as
indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM), and
Section 2.3, Packet Format."
::= { radiusDynAuthServerEntry 14 }
radiusDynAuthClientDisconBadAuthenticators OBJECT-TYPE SYNTAX Counter32 UNITS "replies" MAX-ACCESS read-only STATUS current
radiusDynAuthClientDisconBadAuthenticators OBJECT-TYPE SYNTAX Counter32ユニットはMAX-ACCESS read-onlyステータス電流を "返信"
DESCRIPTION
"The number of RADIUS Disconnect-Ack and Disconnect-NAK
packets that contained invalid Authenticator field
received from this Dynamic Authorization Server. This
counter may experience a discontinuity when the DAC
module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM), and
Section 2.3, Packet Format."
::= { radiusDynAuthServerEntry 15 }
radiusDynAuthClientDisconPendingRequests OBJECT-TYPE
SYNTAX Gauge32
UNITS "requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Disconnect-request packets
destined for this server that have not yet timed out
or received a response. This variable is incremented
when an Disconnect-Request is sent and decremented
due to receipt of a Disconnect-Ack, a Disconnect-NAK,
a timeout, or a retransmission."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 16 }
radiusDynAuthClientDisconTimeouts OBJECT-TYPE
SYNTAX Counter32
UNITS "timeouts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Disconnect request timeouts to this
server. After a timeout, the client may retry to the
same server or give up. A retry to the same server is
counted as a retransmit and as a timeout. A send
to a different server is counted as a
Disconnect-Request and as a timeout. This counter
may experience a discontinuity when the DAC module
(re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM)."
::= { radiusDynAuthServerEntry 17 }
radiusDynAuthClientDisconPacketsDropped OBJECT-TYPE
radiusDynAuthClientDisconPacketsDropped OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming Disconnect-Ack and
Disconnect-NAK packets from this Dynamic Authorization
Server silently discarded by the client application for
some reason other than malformed, bad authenticators,
or unknown types. This counter may experience a
discontinuity when the DAC module (re)starts, as
indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.1, Disconnect Messages (DM), and
Section 2.3, Packet Format."
::= { radiusDynAuthServerEntry 18 }
radiusDynAuthClientCoARequests OBJECT-TYPE
SYNTAX Counter32
UNITS "requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-Requests sent to this
Dynamic Authorization Server. This also includes
CoA requests that have a Service-Type attribute
with value 'Authorize Only'. This counter may
experience a discontinuity when the DAC module
(re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 19 }
radiusDynAuthClientCoAAuthOnlyRequest OBJECT-TYPE SYNTAX Counter32 UNITS "requests" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of RADIUS CoA-requests that include a Service-Type attribute with value 'Authorize Only' sent to this Dynamic Authorization Client. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity."
radiusDynAuthClientCoAAuthOnlyRequest OBJECT-TYPE構文Counter32 UNITS「要求」MAX-ACCESS read-onlyステータス現在の説明「値でservice-type属性を含めるRADIUS CoAを、要求の数が 『オーサライズ時のみ』は、このダイナミックな承認クライアントに送信される。このカウンタかもしれませんradiusDynAuthClientCounterDiscontinuityの値によって示されるDACモジュール（RE）は、起動時に不連続が発生します。」
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 20 }
radiusDynAuthClientCoARetransmissions OBJECT-TYPE
SYNTAX Counter32
UNITS "retransmissions"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-request packets
retransmitted to this RADIUS Dynamic Authorization
Server. This counter may experience a discontinuity
when the DAC module (re)starts, as indicated by the
value of radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 21 }
radiusDynAuthClientCoAAcks OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-ACK packets received from
this Dynamic Authorization Server. This counter may
experience a discontinuity when the DAC module
(re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 22 }
radiusDynAuthClientCoANaks OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-NAK packets received from
this Dynamic Authorization Server. This includes the
RADIUS CoA-NAK packets received with a Service-Type
attribute with value 'Authorize Only' and the RADIUS
CoA-NAK packets received because no session context was found. This counter may experience a discontinuity
when the DAC module (re)starts, as indicated by the
value of radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 23 }
radiusDynAuthClientCoANakAuthOnlyRequest OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-NAK packets that include a
Service-Type attribute with value 'Authorize Only'
received from this Dynamic Authorization Server. This
counter may experience a discontinuity when the DAC
module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 24 }
radiusDynAuthClientCoANakSessNoContext OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-NAK packets received from
this Dynamic Authorization Server because no session
context was found; i.e., it includes an Error-Cause
attribute with value 503 ('Session Context Not Found').
This counter may experience a discontinuity when the
DAC module (re)starts as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 25 }
radiusDynAuthClientMalformedCoAResponses OBJECT-TYPE SYNTAX Counter32 UNITS "replies" MAX-ACCESS read-only STATUS current
radiusDynAuthClientMalformedCoAResponses OBJECT-TYPE SYNTAX Counter32ユニットはMAX-ACCESS read-onlyステータス電流を "返信"
DESCRIPTION
"The number of malformed RADIUS CoA-Ack and CoA-NAK
packets received from this Dynamic Authorization
Server. Bad authenticators and unknown types are
not included as malformed CoA-Ack and CoA-NAK packets.
This counter may experience a discontinuity when the
DAC module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthServerEntry 26 }
radiusDynAuthClientCoABadAuthenticators OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-Ack and CoA-NAK packets
that contained invalid Authenticator field
received from this Dynamic Authorization Server.
This counter may experience a discontinuity when the
DAC module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthServerEntry 27 }
radiusDynAuthClientCoAPendingRequests OBJECT-TYPE
SYNTAX Gauge32
UNITS "requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS CoA-request packets destined for
this server that have not yet timed out or received a
response. This variable is incremented when an
CoA-Request is sent and decremented due to receipt of
a CoA-Ack, a CoA-NAK, or a timeout, or a
retransmission."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 28 }
radiusDynAuthClientCoATimeouts OBJECT-TYPE
radiusDynAuthClientCoATimeoutsのOBJECT-TYPE
SYNTAX Counter32
UNITS "timeouts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of CoA request timeouts to this server.
After a timeout, the client may retry to the same
server or give up. A retry to the same server is
counted as a retransmit and as a timeout. A send to
a different server is counted as a CoA-Request and
as a timeout. This counter may experience a
discontinuity when the DAC module (re)starts, as
indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA)."
::= { radiusDynAuthServerEntry 29 }
radiusDynAuthClientCoAPacketsDropped OBJECT-TYPE
SYNTAX Counter32
UNITS "replies"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming CoA-Ack and CoA-NAK from this
Dynamic Authorization Server silently discarded by the
client application for some reason other than
malformed, bad authenticators, or unknown types. This
counter may experience a discontinuity when the DAC
module (re)starts, as indicated by the value of
radiusDynAuthClientCounterDiscontinuity."
REFERENCE
"RFC 3576, Section 2.2, Change-of-Authorization
Messages (CoA), and Section 2.3, Packet Format."
::= { radiusDynAuthServerEntry 30 }
radiusDynAuthClientUnknownTypes OBJECT-TYPE SYNTAX Counter32 UNITS "replies" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of incoming packets of unknown types that were received on the Dynamic Authorization port. This counter may experience a discontinuity when the DAC module (re)starts, as indicated by the value of radiusDynAuthClientCounterDiscontinuity."
radiusDynAuthClientUnknownTypes OBJECT-TYPE SYNTAXカウンタユニットはMAX-ACCESS read-only説明「動的認可ポートで受信された未知のタイプの受信パケットの数を「返信」場合DACモジュール。このカウンタは不連続性が発生する可能性があり（再） radiusDynAuthClientCounterDiscontinuityの値で示されるように、開始します。」
REFERENCE
"RFC 3576, Section 2.3, Packet Format."
::= { radiusDynAuthServerEntry 31 }
radiusDynAuthClientCounterDiscontinuity OBJECT-TYPE
SYNTAX TimeTicks
UNITS "hundredths of a second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time (in hundredths of a second) since the
last counter discontinuity. A discontinuity may
be the result of a reinitialization of the DAC
module within the managed entity."
::= { radiusDynAuthServerEntry 32 }
-- conformance information
- 適合情報
radiusDynAuthClientMIBConformance
OBJECT IDENTIFIER ::= { radiusDynAuthClientMIB 2 }
radiusDynAuthClientMIBCompliances
OBJECT IDENTIFIER ::= { radiusDynAuthClientMIBConformance 1 }
radiusDynAuthClientMIBGroups
OBJECT IDENTIFIER ::= { radiusDynAuthClientMIBConformance 2 }
-- compliance statements
radiusDynAuthClientMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities implementing the RADIUS Dynamic Authorization Client. Implementation of this module is for entities that support IPv4 and/or IPv6." MODULE -- this module MANDATORY-GROUPS { radiusDynAuthClientMIBGroup }
radiusDynAuthClientMIBCompliance MODULE-COMPLIANCEステータス現在の説明「RADIUSのダイナミックな承認クライアントを実装するエンティティのための準拠宣言。このモジュールの実装は、IPv4および/またはIPv6をサポートするエンティティのためです。」 MODULE - このモジュールMANDATORY-GROUPS {radiusDynAuthClientMIBGroup}
OBJECT radiusDynAuthServerAddressType
SYNTAX InetAddressType { ipv4(1), ipv6(2) }
DESCRIPTION
"An implementation is only required to support IPv4 and
globally unique IPv6 addresses."
OBJECT radiusDynAuthServerAddress SYNTAX InetAddress (SIZE(4|16)) DESCRIPTION "An implementation is only required to support IPv4 and globally unique IPv6 addresses."
OBJECT radiusDynAuthServerAddress構文InetAddress（SIZE（4 | 16））DESCRIPTION "実装がただIPv4およびグローバルに一意のIPv6アドレスをサポートするために必要とされます。"
GROUP radiusDynAuthClientAuthOnlyGroup DESCRIPTION "Only required for Dynamic Authorization Clients that are supporting Service-Type attributes with value 'Authorize-Only'."
GROUP radiusDynAuthClientAuthOnlyGroup説明「サービス・タイプをサポートしているだけのダイナミックな承認クライアントのために必要では 『認可のみ』の値を持つ属性。」
GROUP radiusDynAuthClientNoSessGroup DESCRIPTION "This group is not required if the Dynamic Authorization Server cannot easily determine whether a session exists (e.g., in case of a RADIUS proxy)."
GROUP radiusDynAuthClientNoSessGroup説明は、「動的認可サーバを容易セッション（例えば、RADIUSプロキシの場合）が存在するかどうかを判断できない場合、このグループは必要ありません。」
::= { radiusDynAuthClientMIBCompliances 1 }
-- units of conformance
- 適合の単位
radiusDynAuthClientMIBGroup OBJECT-GROUP OBJECTS { radiusDynAuthClientDisconInvalidServerAddresses, radiusDynAuthClientCoAInvalidServerAddresses, radiusDynAuthServerAddressType, radiusDynAuthServerAddress, radiusDynAuthServerClientPortNumber, radiusDynAuthServerID, radiusDynAuthClientRoundTripTime, radiusDynAuthClientDisconRequests, radiusDynAuthClientDisconRetransmissions, radiusDynAuthClientDisconAcks, radiusDynAuthClientDisconNaks, radiusDynAuthClientMalformedDisconResponses, radiusDynAuthClientDisconBadAuthenticators, radiusDynAuthClientDisconPendingRequests, radiusDynAuthClientDisconTimeouts, radiusDynAuthClientDisconPacketsDropped, radiusDynAuthClientCoARequests, radiusDynAuthClientCoARetransmissions, radiusDynAuthClientCoAAcks, radiusDynAuthClientCoANaks, radiusDynAuthClientMalformedCoAResponses, radiusDynAuthClientCoABadAuthenticators, radiusDynAuthClientCoAPendingRequests, radiusDynAuthClientCoATimeouts, radiusDynAuthClientCoAPacketsDropped, radiusDynAuthClientUnknownTypes, radiusDynAuthClientCounterDiscontinuity } STATUS current
radiusDynAuthClientMIBGroupオブジェクト・グループオブジェクト{radiusDynAuthClientDisconInvalidServerAddresses、radiusDynAuthClientCoAInvalidServerAddresses、radiusDynAuthServerAddressType、radiusDynAuthServerAddress、radiusDynAuthServerClientPortNumber、radiusDynAuthServerID、radiusDynAuthClientRoundTripTime、radiusDynAuthClientDisconRequests、radiusDynAuthClientDisconRetransmissions、radiusDynAuthClientDisconAcks、radiusDynAuthClientDisconNaks、radiusDynAuthClientMalformedDisconResponses、radiusDynAuthClientDisconBadAuthenticators、radiusDynAuthClientDisconPendingRequests、radiusDynAuthClientDisconTimeouts、radiusDynAuthClientDisconPacketsDropped、radiusDynAuthClientCoARequests、radiusDynAuthClientCoARetransmissions、radiusDynAuthClientCoAAcks、radiusDynAuthClientCoANaks、radiusDynAuthClientMalformedCoAResponses、radiusDynAuthClientCoABadAuthenticators、 radiusDynAuthClientCoAPendingRequests、radiusDynAuthClientCoATimeouts、radiusDynAuthClientCoAPacketsDropped、radiusDynAuthClientUnknownTypes、RA diusDynAuthClientCounterDiscontinuity} STATUSの現在
DESCRIPTION
"The collection of objects providing management of
a RADIUS Dynamic Authorization Client."
::= { radiusDynAuthClientMIBGroups 1 }
radiusDynAuthClientAuthOnlyGroup OBJECT-GROUP
OBJECTS { radiusDynAuthClientDisconAuthOnlyRequests,
radiusDynAuthClientDisconNakAuthOnlyRequest,
radiusDynAuthClientCoAAuthOnlyRequest,
radiusDynAuthClientCoANakAuthOnlyRequest
}
STATUS current
DESCRIPTION
"The collection of objects supporting the RADIUS
messages including Service-Type attribute with
value 'Authorize Only'."
::= { radiusDynAuthClientMIBGroups 2 }
radiusDynAuthClientNoSessGroup OBJECT-GROUP
OBJECTS { radiusDynAuthClientDisconNakSessNoContext,
radiusDynAuthClientCoANakSessNoContext
}
STATUS current
DESCRIPTION
"The collection of objects supporting the RADIUS
messages that are referring to non-existing sessions."
::= { radiusDynAuthClientMIBGroups 3 }
END
終わり
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 MIB module is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB module via direct SNMP SET operations.
読み書きおよび/またはリード作成のMAX-ACCESS節を持っているこのMIBモジュールで定義された管理オブジェクトがありません。このMIBモジュールが正しく実装されているのであれば、その後、侵入者が変更またはダイレクトSNMP SET操作を経て、このMIBモジュールのいずれかの管理オブジェクトを作成することができる危険性はありません。
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 vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: radiusDynAuthServerAddress and radiusDynAuthServerAddressType
このMIBモジュールで読み取り可能なオブジェクトの一部（すなわち、アクセス可能ではない以外MAX-ACCESS持つオブジェクト）は、いくつかのネットワーク環境に敏感又は脆弱と考えることができます。 GETおよび/またはこれらのオブジェクトへのアクセスを通知し、おそらくSNMPを通してネットワークの上にそれらを送信する場合でも、これらのオブジェクトの値を暗号化するためにも、制御することが重要です。 radiusDynAuthServerAddressとradiusDynAuthServerAddressType：これらは、テーブルと、オブジェクトとそれらの感度/脆弱性です
These can be used to determine the address of the DAS with which the DAC is communicating. This information could be useful in mounting an attack on the DAS.
これらは、DACが通信しているDASのアドレスを決定するために用いることができます。この情報は、DASへの攻撃を装着する際に有用である可能性があります。
radiusDynAuthServerID
radiusDynAuthServerID
This can be used to determine the Identifier of the DAS. This information could be useful in impersonating the DAS.
これは、DASの識別子を決定するために用いることができます。この情報は、DASを偽装するのに有用である可能性があります。
radiusDynAuthServerClientPortNumber
radiusDynAuthServerClientPortNumber
This can be used to determine the destination port number to which the DAC is sending. This information could be useful in mounting an attack on the DAS.
これは、DACが送信される宛先ポート番号を決定するために用いることができます。この情報は、DASへの攻撃を装着する際に有用である可能性があります。
SNMP versions prior to SNMPv3 did not include adequate security. 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 allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3の前のSNMPバージョンは十分なセキュリティを含んでいませんでした。ネットワーク自体が（IPsecを使って、例えば）安全であっても、その後も、安全なネットワーク上で/ SETにアクセスし、GETだれに許容されているかのように何の制御（読み取り/変更/作成/削除）この内のオブジェクトが存在しませんMIBモジュール。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
実装がSNMPv3フレームワークで提供するようにセキュリティ機能を考えることが推奨される（認証とプライバシーのために）SNMPv3の暗号化メカニズムの完全なサポートを含む、（[RFC3410]セクション8を参照）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
さらに、SNMPv3の前のSNMPバージョンの展開はお勧めしません。代わりに、SNMPv3を展開すると、暗号化セキュリティを有効にすることをお勧めします。このMIBモジュールのインスタンスへのアクセスを与えるSNMP実体が適切にのみプリンシパル（ユーザ）にオブジェクトへのアクセスを提供するように設定されていることを確認するために、顧客/オペレータ責任実際にGETまたはSET（変化への正当な権利を有することです/）/削除、それらを作成します。
The IANA has assigned OID number 145 under mib-2.
IANAは、MIB-2の下でOID番号145を割り当てています。
The authors would also like to acknowledge the following people for their comments on this document: Bernard Aboba, Alan DeKok, David Nelson, Anjaneyulu Pata, Dan Romascanu, Juergen Schoenwaelder, Greg Weber, Bert Wijnen, and Glen Zorn.
バーナードAboba、アランDeKok、デビッド・ネルソン、Anjaneyuluパタ、ダンRomascanu、ユルゲンSchoenwaelder、グレッグ・ウェーバー、バートWijnen、およびグレンツォルン：著者らはまた、このドキュメントの彼らのコメントについては、以下の人々に感謝します。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]ブラドナーの、S.、 "要件レベルを示すためにRFCsにおける使用のためのキーワード"、BCP 14、RFC 2119、1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578] McCloghrie、K.、パーキンス、D.、およびJ. Schoenwaelder、STD 58、RFC 2578、1999年4月 "管理情報バージョン2（SMIv2）の構造"。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579] McCloghrie、K.、パーキンス、D.、およびJ. Schoenwaelder、 "SMIv2のためのテキストの表記法"、STD 58、RFC 2579、1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580] McCloghrie、K.、パーキンス、D.、およびJ. Schoenwaelder、 "SMIv2のための適合性宣言"、STD 58、RFC 2580、1999年4月。
[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.
[RFC3411]ハリントン、D.、Presuhn、R.、およびB. Wijnenの、 "簡易ネットワーク管理プロトコル（SNMP）管理フレームワークを記述するためのアーキテクチャ"、STD 62、RFC 3411、2002年12月。
[RFC3576] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. Aboba, "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)", RFC 3576, July 2003.
、RFC 3576、2003年7月[RFC3576]千葉、M.、Dommety、G.、エクランド、M.、ミトン、D.、およびB. Aboba、 "ユーザーサービス（RADIUS）でリモート認証ダイヤルへのダイナミックな承認拡張機能"。
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.
[RFC4001]ダニエル、M.、ハーバーマン、B.、Routhier、S.、およびJ. Schoenwaelder、 "インターネットネットワークアドレスのためのテキストの表記法"、RFC 4001、2005年2月。
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865, June 2000.
[RFC2865] Rigney、C.、ウィレンス、S.、ルーベン、A.、およびW.シンプソン、RFC 2865、2000年6月 "ユーザーサービス（RADIUS）でリモート認証ダイヤル"。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]ケース、J.、マンディ、R.、パーテイン、D.、およびB.スチュワート、 "インターネット標準の管理フレームワークのための序論と適用性声明"、RFC 3410、2002年12月。
[RFC4669] Nelson, D., "RADIUS Authentication Server MIB for IPv6", RFC 4669, August 2006.
[RFC4669]ネルソン、D.、 "IPv6のためのRADIUS認証サーバのMIB"、RFC 4669、2006年8月。
[RFC4671] Nelson, D., "RADIUS Accounting Server MIB for IPv6", RFC 4671, August 2006.
[RFC4671]ネルソン、D.、 "IPv6のためのRADIUSアカウンティングサーバーMIB"、RFC 4671、2006年8月。
[RFC4673] De Cnodder, S., Jonnala, N., and M. Chiba, "RADIUS Dynamic Authorization Server MIB", RFC 4673, September 2006.
[RFC4673]デCnodder、S.、Jonnala、N.、およびM.千葉、 "RADIUSのダイナミックな承認サーバMIB"、RFC 4673、2006年9月。
Authors' Addresses
著者のアドレス
Stefaan De Cnodder Alcatel Francis Wellesplein 1 B-2018 Antwerp Belgium
StefaanデCnodderアルカテル・フランシス・ウェルズプレイン1 B-2018アントワープ、ベルギー
Phone: +32 3 240 85 15 EMail: stefaan.de_cnodder@alcatel.be
電話：+32 3 240 85 15 Eメール：stefaan.de_cnodder@alcatel.be
Nagi Reddy Jonnala Cisco Systems, Inc. Divyasree Chambers, B Wing, O'Shaugnessy Road Bangalore-560027, India
ナギレディJonnalaシスコシステムズ、株式会社Divyasreeチェンバース、B棟、O'Shaugnessyロードバンガロール - 560027、インド
Phone: +91 94487 60828 EMail: njonnala@cisco.com
電話：+91 94487 60828 Eメール：njonnala@cisco.com
Murtaza Chiba Cisco Systems, Inc. 170 West Tasman Dr. San Jose CA, 95134
Murtaza千葉シスコシステムズ、株式会社170西タスマン博士サンノゼCA、95134
Phone: +1 408 525 7198 EMail: mchiba@cisco.com
電話：+1 408 525 7198 Eメール：mchiba@cisco.com
Full Copyright Statement
完全な著作権声明
Copyright (C) The Internet Society (2006).
著作権（C）インターネット協会（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.
この文書では、BCP 78に含まれる権利と許可と制限の適用を受けており、その中の記載を除いて、作者は彼らのすべての権利を保有します。
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.
この文書とここに含まれている情報は、基礎とCONTRIBUTOR「そのまま」、ORGANIZATION HE / SHEが表すまたはインターネットソサエティおよびインターネット・エンジニアリング・タスク・フォース放棄すべての保証、明示または、（もしあれば）後援ISに設けられています。黙示、情報の利用は、特定の目的に対する権利または商品性または適合性の黙示の保証を侵害しない任意の保証含むがこれらに限定されません。
Intellectual Property
知的財産
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in 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 made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETFは、本書またはそのような権限下で、ライセンスがたりないかもしれない程度に記載された技術の実装や使用に関係すると主張される可能性があります任意の知的財産権やその他の権利の有効性または範囲に関していかなる位置を取りません利用可能です。またそれは、それがどのような権利を確認する独自の取り組みを行ったことを示すものでもありません。 RFC文書の権利に関する手続きの情報は、BCP 78およびBCP 79に記載されています。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
IPRの開示のコピーが利用できるようにIETF事務局とライセンスの保証に行われた、または本仕様の実装者または利用者がそのような所有権の使用のための一般的なライセンスまたは許可を取得するために作られた試みの結果を得ることができますhttp://www.ietf.org/iprのIETFのオンラインIPRリポジトリから。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETFは、その注意にこの標準を実装するために必要とされる技術をカバーすることができる任意の著作権、特許または特許出願、またはその他の所有権を持ってすべての利害関係者を招待します。 ietf-ipr@ietf.orgのIETFに情報を記述してください。
Acknowledgement
謝辞
Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).
RFCエディタ機能のための資金は、IETF管理サポート活動（IASA）によって提供されます。