RFC 4672 on RADIUS Dynamic Authorization Client MIB
rfc-editor@rfc-editor.org Wed, 20 September 2006 23:43 UTC
Envelope-to: radiusext-data@psg.com
Delivery-date: Wed, 20 Sep 2006 23:44:06 +0000
Date: Wed, 20 Sep 2006 16:43:26 -0700
Message-Id: <200609202343.k8KNhQaS029264@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 4672 on RADIUS Dynamic Authorization Client MIB
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, radiusext@ops.ietf.org
A new Request for Comments is now available in online RFC libraries. RFC 4672 Title: RADIUS Dynamic Authorization Client MIB Author: S. De Cnodder, N. Jonnala, M. Chiba Status: Informational Date: September 2006 Mailbox: stefaan.de_cnodder@alcatel.be, njonnala@cisco.com, mchiba@cisco.com Pages: 24 Characters: 50817 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-radext-dynauth-client-mib-06.txt URL: http://www.rfc-editor.org/rfc/rfc4672.txt 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. This memo provides information for the Internet community. This document is a product of the RADIUS EXTensions Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/radiusext/>