[rfc-dist] RFC 4670 on RADIUS Accounting Client MIB for IPv6
rfc-editor at rfc-editor.org
Mon Aug 28 11:24:07 PDT 2006
A new Request for Comments is now available in online RFC libraries.
Title: RADIUS Accounting Client MIB for
Author: D. Nelson
Date: August 2006
Mailbox: dnelson at enterasys.com
I-D Tag: draft-ietf-radext-rfc2620bis-04.txt
This memo defines a set of extensions that instrument RADIUS
accounting client functions. These extensions represent a portion of
the Management Information Base (MIB) for use with network management
protocols in the Internet community. Using these extensions, IP-based management stations can manage RADIUS accounting clients.
This memo obsoletes RFC 2620 by deprecating the MIB table containing
IPv4-only address formats and defining a new table to add support for
version-neutral IP address formats. The remaining MIB objects from
RFC 2620 are carried forward into this document. This memo also adds
UNITS and REFERENCE clauses to selected objects. 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist