Web Security Framework: Problem Statement and Requirements
draft-hodges-websec-framework-reqs-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-01-17 (latest revision 2012-07-16) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-hodges-websec-framework-reqs-02.txt
Abstract
Web-based malware and attacks are proliferating rapidly on the Internet. New web security mechanisms are also rapidly growing in number, although in an incoherent fashion. This document provides a brief overview of the present situation and the various seemingly piece-wise approaches being taken to mitigate the threats. It then provides an overview of requirements as presently being expressed by the community in various online and face-to-face discussions.
Authors
Jeff Hodges (Jeff.Hodges@PayPal.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)