Skip to main content

Status-Realm and Loop Prevention for the Remote Dial-In User Service (RADIUS)
draft-cullen-radextra-status-realm-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Margaret Cullen , Alan DeKok , Mark J Donnelly , Josh Howlett
Last updated 2023-04-27 (Latest revision 2022-10-24)
Replaced by draft-ietf-radext-status-realm
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Associated None milestone
May 2024
multi-hop status / traceroute, extend 8-bit ID space
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 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.)