Status-Realm and Loop Prevention for the Remote Dial-In User Service (RADIUS)
draft-ietf-radext-status-realm-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Margaret Cullen , Alan DeKok , Mark J Donnelly , Josh Howlett | ||
| Last updated | 2024-09-05 (Latest revision 2024-03-04) | ||
| Replaces | draft-cullen-radextra-status-realm | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 extension to the Remote Authentication Dial- In User Service (RADIUS) protocol to allow participants in a multi- hop RADIUS proxy fabric to check the status of a remote RADIUS authentication realm, gain visibility into the path that a RADIUS request will take across the RADIUS proxy fabric, and mitigate or prevent RADIUS proxy loops.
Authors
Margaret Cullen
Alan DeKok
Mark J Donnelly
Josh Howlett
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)