Design Guidelines for RADIUS Attributes
draft-weber-radius-attr-guidelines-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Greg Weber | ||
| Last updated | 2006-06-27 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
This memo explores various issues related to the data model used by the Remote Authentication Dial In User Service (RADIUS) protocol. Recommendations are made to facilitate internal alignment and uniformity. Attribute design guidelines are provided both as an aid to IETF development work, and to facilitate independent work by other Standards Development Organizations (SDOs).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)