RFC 5080: Common Remote Authentication Dial In User Service (RADIUS) Implementation Issues and Suggested Fixes

This document describes common issues seen in Remote Authentication Dial In User Service (RADIUS) implementations and suggests some fixes. Where applicable,…

Read RFC 5080 on the RFC Editor

Outgoing relationships (4 related RFCs)

Updates — RFC 2865: Remote Authentication Dial In User Service (RADIUS)
Updates — RFC 3579: RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)
Updates — RFC 2866: RADIUS Accounting
Updates — RFC 2869: RADIUS Extensions

Incoming relationships (12 related RFCs)

Normatively referenced by — RFC 5997: Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol
Normatively referenced by — RFC 6519: RADIUS Extensions for Dual-Stack Lite
Normatively referenced by — RFC 7360: Datagram Transport Layer Security (DTLS) as a Transport Layer for RADIUS
Normatively referenced by — RFC 5608: Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models
Normatively referenced by — RFC 6930: RADIUS Attribute for IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)
Informatively referenced by — RFC 6709: Design Considerations for Protocol Extensions
Informatively referenced by — RFC 6158: RADIUS Design Guidelines
Informatively referenced by — RFC 6613: RADIUS over TCP
Informatively referenced by — RFC 6632: An Overview of the IETF Network Management Standards
Informatively referenced by — RFC 7499: Support of Fragmentation of RADIUS Packets
Informatively referenced by — RFC 7831: Application Bridging for Federated Access Beyond Web (ABFAB) Architecture
Informatively referenced by — RFC 9765: RADIUS/1.1: Leveraging Application-Layer Protocol Negotiation (ALPN) to Remove MD5