Guidelines for Creating Generally Useful Authentication Mechanisms (GUAM)
draft-salowey-guam-mech-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Joseph A. Salowey | ||
| Last updated | 2006-06-28 | ||
| 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
Generic Security Services API (GSS-API), the Simple Authentication and Security Layer (SASL), and the Extensible Authentication Protocol (EAP) are three authentication and frameworks used within the IETF that have similar goals. This document describes guidelines for creating authentication mechanisms that are generally usable in any of these frameworks.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)