Common Remote Authentication Dial In User Service Implementation Issues and Suggested Fixes
RFC 5080, “Common Remote Authentication Dial In User Service Implementation Issues and Suggested Fixes”, is a Proposed Standard document published in December 2007 by D. Nelson, A. DeKok. It updates RFC 2865, RFC 2866, RFC 2869, RFC 3579. The canonical text is published by the RFC Editor.
Abstract
This document describes common issues seen in Remote Authentication Dial In User Service (RADIUS) implementations and suggests some fixes. Where applicable, ambiguities and errors in previous RADIUS specifications are clarified. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5080 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5079 Rejecting Anonymous Requests in the Session Initiation Protocol
- RFC 5081 Using OpenPGP Keys for Transport Layer Security Authentication
- RFC 5078 IAB and IESG Selection, Confirmation, and Recall Process: Revision of the Nominating and Recall Committees Timeline
- RFC 5082 The Generalized TTL Security Mechanism
- RFC 5083 Cryptographic Message Syntax Authenticated-Enveloped-Data Content Type
- RFC 5076 ENUM Validation Information Mapping for the Extensible Provisioning Protocol
- RFC 5084 Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax
- RFC 5075 IPv6 Router Advertisement Flags Option