AAA Referral
draft-beadles-aaa-referral-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark A. Beadles | ||
| Last updated | 1999-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 mechanism whereby, in response to a AAA request, a AAA server may refer a client to another server, which will then directly handle requests from that client. This is in contrast to a proxy mechanism, where one AAA server acts as an intermediary, communicating with another AAA server on behalf of the AAA client. An implementation of this mechanism for Dial Access AAA is presented using the RADIUS protocol.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)