The PKI SASL Mechanism
draft-hansen-sasl-pki-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tony Hansen | ||
| Last updated | 2003-02-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 document defines a user/password Simple Authentication and Security Layer(SASL) mechanism called the PKI mechanism. The PKI mechanism is intended to be used in situations where (1) passwords must be encrypted, (2) the password must be recoverable, and (3) using TLS in combination with a SASL mechanism such as PLAIN is inappropriate. NOTE: This document is a straw proposal to see what interest there is in having a SASL mechanism such as this. See the first section below for more information on why this mechanism is needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)