[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 4668 on RADIUS Authentication Client MIB for IPv6
A new Request for Comments is now available in online RFC libraries.
Title: RADIUS Authentication Client MIB for
Author: D. Nelson
Status: Standards Track
Date: August 2006
I-D Tag: draft-ietf-radext-rfc2618bis-04.txt
This memo defines a set of extensions that instrument RADIUS
authentication 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
This memo obsoletes RFC 2618 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 2618 are carried forward into this document. The memo also adds
UNITS and REFERENCE clauses to selected objects. [STANDARDS TRACK]
This document is a product of the RADIUS EXTensions
Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.Please refer to the current edition of the
Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol. Distribution of this memo is
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:
Subject: getting 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
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 firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.