RFC 8559: Dynamic Authorization Proxying in the Remote Authentication Dial-In User Service (RADIUS) Protocol
In plain English — editorial summary, not part of the RFC
RFC 5176 defines Change-of-Authorization (CoA) and Disconnect Message (DM) behavior for RADIUS. RFC 5176 also suggests that proxying these messages is possible, but it does not provide guidance as to how that is done. This specification updates RFC 5176 to correct that omission for scenarios where networks use realm-based proxying as defined in RFC 7542. This specification also updates RFC 5580 to allow the Operator-Name attribute in CoA-Request and Disconnect-Request packets.
Document record
- Document ID
- RFC8559
- Published
- April 2019
- Authors
- A. DeKok; J. Korhonen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7833A RADIUS Attribute, Binding, Profiles, Name Identifier Format, and Confirmation Methods for the Security Assertion Markup Language (SAML)Current
May 2016
- RFC 7832Application Bridging for Federated Access Beyond Web (ABFAB) Use CasesCurrent
May 2016
- RFC 7831Application Bridging for Federated Access Beyond Web (ABFAB) ArchitectureCurrent
May 2016
- RFC 7585Dynamic Peer Discovery for RADIUS/TLS and RADIUS/DTLS Based on the Network Access Identifier (NAI)Current
October 2015
- RFC 7499Support of Fragmentation of RADIUS PacketsCurrent
April 2015
- RFC 9765RADIUS/1.1: Leveraging Application-Layer Protocol Negotiation (ALPN) to Remove MD5Current
April 2025
- RFC 6911RADIUS Attributes for IPv6 Access NetworksCurrent
April 2013
- RFC 6614Transport Layer Security (TLS) Encryption for RADIUSUpdated
May 2012
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?