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

The information below is for an old version of the document
Document Type Expired Internet-Draft (radext WG)
Author Alan DeKok 
Last updated 2016-05-05 (latest revision 2015-11-02)
Replaces draft-dekok-radext-datatypes
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Additional Resources
- Mailing list discussion
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Stefan Winter
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Stefan Winter" <stefan.winter@restena.lu>

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-ietf-radext-datatypes-02.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.)