RFC 4669: RADIUS Authentication Server MIB for IPv6
In plain English — editorial summary, not part of the RFC
This memo defines a set of extensions that instrument RADIUS authentication server 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 authentication servers. This memo obsoletes RFC 2619 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 2619 are carried forward into this document. This memo also adds UNITS and REFERENCE clauses to selected objects. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4669
- Published
- August 2006
- Authors
- D. Nelson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 25
- Also known as
- —
- Obsoletes:
- RFC 2619
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4670RADIUS Accounting Client MIB for IPv6Current
August 2006
- RFC 4668RADIUS Authentication Client MIB for IPv6Current
August 2006
- RFC 4671RADIUS Accounting Server MIB for IPv6Current
August 2006
- RFC 6065Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group MappingsCurrent
December 2010
- RFC 2618RADIUS Authentication Client MIBObsoleted
June 1999
- RFC 4672RADIUS Dynamic Authorization Client MIBCurrent
September 2006
- RFC 4673RADIUS Dynamic Authorization Server MIBCurrent
September 2006
- RFC 4765The Intrusion Detection Message Exchange Format (IDMEF)Current
March 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?