Re: [radext] BoF request for IETF 115

[[e-mail]]

Something I'd find useful is a RADIUS equivalent of traceroute.

This would allow a RADIUS client to probe the path towards a named realm
across none, one or more proxies.

I think this might be useful because
* the RADIUS protocol offers limited diagnostic information across proxies
(e.g., realm availability)
* troubleshooting RADIUS issues in federated environments often requires
coordinating with multiple parties to establish what they are seeing
* there are multiple RADIUS transports, each with their own failure modes; a
path could incorporate two or more of these
* there are multiple discovery methods, such as RFC7585, that have their own
failure modes; a path could incorporate two or more of these

I imagine it would operate similarly to Status-Server, but traverse proxies
and provide reporting on the availability of the next hop, the transport(s),
realm discovery method(s), failure reasons, etc.

Even if the work of radext is wildly successful, we will be operating in a
hybrid environment with RFC2865 for many years. I think this could be a
useful tool to help the adoption and operation of new protocols.

Josh