Data Types in the Remote Authentication Dial-In User Service Protocol (RADIUS)
draft-dekok-radext-datatypes-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Alan DeKok | ||
| Last updated | 2013-08-16 (Latest revision 2013-02-12) | ||
| Replaced by | draft-ietf-radext-datatypes, RFC 8044 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RADIUS specifications have used data types for two decades, without rigorously defining them as managed entities. During this time, RADIUS implementations have named the data types, and have used them to as managed entities in attribute definitions. This document updates the specifications to match established prctice. We do this by naming data types defined in [RFC6158], which have been used since at least [RFC2865]. 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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)