RFC 8044: Data Types in RADIUS
In plain English — editorial summary, not part of the RFC
RADIUS specifications have used data types for two decades without defining them as managed entities. During this time, RADIUS implementations have named the data types and have used them in attribute definitions. This document updates the specifications to better follow established practice. We do this by naming the data types defined in RFC 6158, which have been used since at least the publication of RFC 2865. We provide an IANA registry for the data types and update the "RADIUS Attribute Types" registry to include a Data Type field for each attribute. Finally, we recommend that authors of RADIUS specifications use these types in preference to existing practice. This document updates RFCs 2865, 3162, 4072, 6158, 6572, and 7268.
Document record
- Document ID
- RFC8044
- Published
- January 2017
- Authors
- A. DeKok
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 35
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent
January 2017
- RFC 8037CFRG Elliptic Curve Diffie-Hellman (ECDH) and Signatures in JSON Object Signing and Encryption (JOSE)Updated
January 2017
- RFC 8053HTTP Authentication Extensions for Interactive ClientsCurrent
January 2017
- RFC 8031Curve25519 and Curve448 for the Internet Key Exchange Protocol Version 2 (IKEv2) Key AgreementCurrent
December 2016
- RFC 8062Anonymity Support for KerberosCurrent
February 2017
- RFC 8019Protecting Internet Key Exchange Protocol Version 2 (IKEv2) Implementations from Distributed Denial-of-Service AttacksCurrent
November 2016
- RFC 8070Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) Freshness ExtensionCurrent
February 2017
- RFC 8009AES Encryption with HMAC-SHA2 for Kerberos 5Current
October 2016
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?