Common RADIUS Implementation Issues and Suggested Fixes
draft-aboba-radext-fixes-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David B. Nelson | ||
| Last updated | 2008-04-16 (Latest revision 2006-06-08) | ||
| Replaced by | RFC 5080 | ||
| 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-fixes | |
| 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
This document describes common issues seen in RADIUS implementations and suggests some fixes. Where applicable, ambiguities and errors in previous RADIUS specifications are clarified.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)