RFC 5997: Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol
In plain English — editorial summary, not part of the RFC
This document describes a deployed extension to the Remote Authentication Dial In User Service (RADIUS) protocol, enabling clients to query the status of a RADIUS server. This extension utilizes the Status-Server (12) Code, which was reserved for experimental use in RFC 2865. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5997
- Published
- August 2010
- Authors
- A. DeKok
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 24
- Also known as
- —
- Updates:
- RFC 2866
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5998An Extension for EAP-Only Authentication in IKEv2Current
September 2010
- RFC 5996Internet Key Exchange Protocol Version 2 (IKEv2)Obsoleted
September 2010
- RFC 5990Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS)Obsoleted
September 2010
- RFC 6012Datagram Transport Layer Security (DTLS) Transport Mapping for SyslogUpdated
October 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 6025ASN.1 TranslationCurrent
October 2010
- RFC 6027IPsec Cluster Problem StatementCurrent
October 2010
- RFC 6030Portable Symmetric Key Container (PSKC)Current
October 2010
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?