Generally Useful Authentication Mechanisms (GUAM)
draft-salowey-guam-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Joseph A. Salowey | ||
| Last updated | 2005-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
Generic Security Services API (GSS-API), the Simple Authentication and Security Layer (SASL), the Extensible Authentication Protocol (EAP) and Transport Layer Security (TLS) are examples of four different security frameworks within the IETF. Each of these frameworks have evolved separately towards a common goal of authentication and establishing a cryptographic context. They support different types of security mechanisms and have historically evolved to integrate with different security infrastructures. This document discusses their similarities and differences and how these security mechanisms might start to converge into a more uniform approach involving generally useful authentication mechanisms that can be used in any of these frameworks with a variety of different security infrastructures.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)