RFC 6158: RADIUS Design Guidelines
In plain English — editorial summary, not part of the RFC
This document provides guidelines for the design of attributes used by the Remote Authentication Dial In User Service (RADIUS) protocol. It is expected that these guidelines will prove useful to authors and reviewers of future RADIUS attribute specifications, within the IETF as well as other Standards Development Organizations (SDOs). This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6158
- Published
- March 2011
- Authors
- A. DeKok; G. Weber
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- sec
- Pages
- 38
- Also known as
- BCP158
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6170Internet X.509 Public Key Infrastructure -- Certificate ImageObsoleted
May 2011
- RFC 6176Prohibiting Secure Sockets Layer (SSL) Version 2.0Updated
March 2011
- RFC 6113A Generalized Framework for Kerberos Pre-AuthenticationCurrent
April 2011
- RFC 6112Anonymity Support for KerberosObsoleted
April 2011
- RFC 6111Additional Kerberos Naming ConstraintsCurrent
April 2011
- RFC 6071IP Security (IPsec) and Internet Key Exchange (IKE) Document RoadmapCurrent
February 2011
- RFC 6066Transport Layer Security (TLS) Extensions: Extension DefinitionsUpdated
January 2011
- RFC 6251Using Kerberos Version 5 over the Transport Layer Security (TLS) ProtocolCurrent
May 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?