RFC 3576: Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5176.
Current version: RFC 5176 — Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)
In plain English — editorial summary, not part of the RFC
This document describes a currently deployed extension to the Remote Authentication Dial In User Service (RADIUS) protocol, allowing dynamic changes to a user session, as implemented by network access server products. This includes support for disconnecting users and changing authorizations applicable to a user session. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3576
- Published
- July 2003
- Authors
- M. Chiba; G. Dommety; M. Eklund; D. Mitton; B. Aboba
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 30
- Also known as
- —
- Obsoleted by:
- RFC 5176
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4072Diameter Extensible Authentication Protocol (EAP) ApplicationUpdated
August 2005
- RFC 2867RADIUS Accounting Modifications for Tunnel Protocol SupportCurrent
June 2000
- RFC 2865Remote Authentication Dial In User Service (RADIUS)Updated
June 2000
- RFC 3575IANA Considerations for RADIUS (Remote Authentication Dial In User Service)Updated
July 2003
- RFC 3579RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)Updated
September 2003
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
- RFC 4005Diameter Network Access Server ApplicationObsoleted
August 2005
- RFC 2882Network Access Servers Requirements: Extended RADIUS PracticesCurrent
July 2000
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?