Remote Authentication Dial In User Service (RADIUS) Protocol Extensions
draft-dekok-radext-radius-extensions-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alan DeKok , Avi Lior | ||
| Last updated | 2012-10-30 (Latest revision 2011-02-08) | ||
| Replaced by | draft-ietf-radext-radius-extensions | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-radext-radius-extensions | |
| 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
The Remote Authentication Dial In User Service (RADIUS) protocol is nearing exhaustion of its current 8-bit attribute type space. In addition, experience shows a growing need for complex grouping, along with attributes which can carry more than 253 octets of data. This document defines changes to RADIUS which address all of the above problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)