RADIUS Security Roadmap
draft-moskowitz-radius-sec-roadmap-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robert Moskowitz | ||
| Last updated | 2005-02-16 | ||
| 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
RADIUS has become the defacto protocol between network edge devices (e,g, dial NAS or Wireless AP) and a backend Authentication Server. In this environment the backend Server is often called a (RADIUS Server). RADIUS is gaining very broad penetration, even into homes, because of its use with wireless authentication. Because of the amount of deployed infrastructure already in place, we believe that RADIUS will not be supplanted by another authentication service in the foreseeable future. Because the widespread deployment in wireless has different infrastructure requirements than what is required for dialup, RADIUS requirements, especially trust between Edge devices and RADIUS Servers needs to be addressed. This document sets the requirements for RADIUS security and then sets forth technologies that will satisfy those requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)