SASL in HTTP/1.1
draft-nystrom-http-sasl-12
| Document | Type |
Expired Internet-Draft
(individual in app area)
Expired & archived
|
|
|---|---|---|---|
| Authors | Magnus Nyström , Alexey Melnikov | ||
| Last updated | 2015-10-14 (Latest revision 2005-01-11) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Ted Hardie | ||
| Send notices to | <mel@isode.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo suggest the use of SASL [RFC2222] as a framework to enable the use of strong authentication mechanisms in http/1.1 [RFC2616], and defines one approach to accomplish this. Please send comments on this document to the relevant mailing lists, e.g. ietf-sasl@imc.org.
Authors
Magnus Nyström
Alexey Melnikov
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)