Crypto-Agility Requirements for Remote Dial-In User Service (RADIUS)
draft-nelson-radext-crypto-agility-requirements-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David B. Nelson | ||
| Last updated | 2012-10-30 (Latest revision 2008-03-12) | ||
| Replaced by | RFC 6421 | ||
| 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-crypto-agility-requirements | |
| 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 describes the requirements for a Crypto-Agility solution for Remote Authentication Dial-In User Service (RADIUS).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)