RFC 6929: Remote Authentication Dial In User Service (RADIUS) Protocol Extensions
In plain English — editorial summary, not part of the RFC
The Remote Authentication Dial-In User Service (RADIUS) protocol is nearing exhaustion of its current 8-bit Attribute Type space. In addition, experience shows a growing need for complex grouping, along with attributes that can carry more than 253 octets of data. This document defines changes to RADIUS that address all of the above problems.
Document record
- Document ID
- RFC6929
- Published
- April 2013
- Authors
- A. DeKok; A. Lior
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 68
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6911RADIUS Attributes for IPv6 Access NetworksCurrent
April 2013
- RFC 6960X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPUpdated
June 2013
- RFC 6961The Transport Layer Security (TLS) Multiple Certificate Status Request ExtensionObsoleted
June 2013
- RFC 6880An Information Model for Kerberos Version 5Current
March 2013
- RFC 6876A Posture Transport Protocol over TLS (PT-TLS)Current
February 2013
- RFC 6989Additional Diffie-Hellman Tests for the Internet Key Exchange Protocol Version 2 (IKEv2)Current
July 2013
- RFC 7009OAuth 2.0 Token RevocationCurrent
August 2013
- RFC 6844DNS Certification Authority Authorization (CAA) Resource RecordObsoleted
January 2013
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?