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