Data Types in the Remote Authentication Dial-In User Service Protocol (RADIUS)
draft-dekok-radext-datatypes-06

Document Type Replaced Internet-Draft (candidate for radext WG)
Last updated 2016-03-04 (latest revision 2015-04-01)
Replaced by draft-ietf-radext-datatypes
Stream IETF
Intended RFC status Informational
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-radext-datatypes
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dekok-radext-datatypes-06.txt

Abstract

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 RFC 2865. We provide an IANA registry for the data types, and update the RADIUS Attribute Type 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.

Authors

Alan DeKok (aland@freeradius.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)