Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 2865,RFC 3162,RFC 4072,RFC 6158,RFC 6572,RFC 7268

Author:

A. DeKok

Stream:

IETF

Source:

radext (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8044

Discuss this RFC: Send questions or comments to the mailing listradext@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8044

Abstract

RADIUS specifications have used data types for two decades withoutdefining them as managed entities. During this time, RADIUSimplementations have named the data types and have used them inattribute definitions. This document updates the specifications tobetter follow established practice. We do this by naming the datatypes defined in RFC 6158, which have been used since at least thepublication of RFC 2865. We provide an IANA registry for the datatypes and update the "RADIUS Attribute Types" registry to include aData Type field for each attribute. Finally, we recommend thatauthors of RADIUS specifications use these types in preference toexisting practice. This document updates RFCs 2865, 3162, 4072,6158, 6572, and 7268.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.