Problem Statement and Requirements for Header Protection
draft-ietf-lamps-header-protection-requirements-01
| Document | Type |
Expired Internet-Draft
(lamps WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexey Melnikov , Bernie Hoeneisen | ||
| Last updated | 2020-05-01 (Latest revision 2019-10-29) | ||
| Replaces | draft-melnikov-lamps-header-protection | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
Privacy and security issues with email header protection in S/MIME have been identified for some time. However, the desire to fix these issues has only recently been expressed in the IETF LAMPS Working Group. The existing S/MIME specification is likely to be updated regarding header protection. This document describes the problem statement, generic use cases, and requirements of header protection.
Authors
Alexey Melnikov
Bernie Hoeneisen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)