Security Requirements for HTTP
draft-ietf-httpbis-security-properties-05
| Document | Type | Expired Internet-Draft (httpbis WG) | |
|---|---|---|---|
| Last updated | 2010-03-10 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Dead WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-httpbis-security-properties-05.txt
Abstract
Recent IESG practice dictates that IETF protocols must specify mandatory-to-implement (MTI) security mechanisms, so that all conformant implementations share a common baseline. This document examines all widely deployed HTTP security technologies, and analyzes the trade-offs of each.
Authors
Jeff Hodges
(Jeff.Hodges@PayPal.com)
Barry Leiba
(barryleiba@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)