Common RADIUS Implementation Issues and Suggested Fixes
draft-aboba-radext-fixes-03
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2008-04-16 (latest revision 2006-06-08) | ||
| Replaced by | draft-ietf-radext-fixes | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-radext-fixes | |
| 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-aboba-radext-fixes-03.txt
https://www.ietf.org/archive/id/draft-aboba-radext-fixes-03.txt
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
David Nelson (d.b.nelson@comcast.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)