RADIUS Extensions for Server Load Balancing
draft-massameno-radius-lb-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Daniel Massameno | ||
Last updated | 2020-12-27 (Latest revision 2020-06-25) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a method for a Network Access Server (NAS) to dynamically discover all available RADIUS servers. It defines a new message type within the STATUS-SERVER message, which is requested by the NAS and provided by the RADIUS server. The NAS is then able to load balance its RADIUS messages across multiple RADIUS servers based on priority and weight supplied by the initial server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)