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
- RFC5176
- Published
- January 2008
- Authors
- M. Chiba; G. Dommety; M. Eklund; D. Mitton; B. Aboba
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 34
- Also known as
- —
- Obsoletes:
- RFC 3576
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5178Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name TypeCurrent
May 2008
- RFC 5179Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS MechanismCurrent
May 2008
- RFC 5169Handover Key Management and Re-Authentication Problem StatementCurrent
March 2008
- RFC 5197On the Applicability of Various Multimedia Internet KEYing (MIKEY) Modes and ExtensionsCurrent
June 2008
- RFC 5209Network Endpoint Assessment (NEA): Overview and RequirementsCurrent
June 2008
- RFC 5216The EAP-TLS Authentication ProtocolUpdated
March 2008
- RFC 5126CMS Advanced Electronic Signatures (CAdES)Current
March 2008
- RFC 5246The Transport Layer Security (TLS) Protocol Version 1.2Obsoleted
August 2008
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?