Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol
draft-dekok-radius-status-server-02

Document Type Expired Internet-Draft (individual)
Last updated 2008-03-20
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dekok-radius-status-server-02.txt

Abstract

RFC 2865 defines a Status-Server code for use in RADIUS, but labels it as "Experimental" without further discussion. This document describes a practical use for the Status-Server packet code, which is to let clients query the status of a RADIUS server. These queries, and responses (if any) enable the client to make more informed decisions. The result is a more stable, and more robust RADIUS architecture.

Authors

Alan DeKok (aland@deployingradius.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)