Problem Statement and Requirements for Header Protection
draft-ietf-lamps-header-protection-requirements-01
| Document | Type | Expired Internet-Draft (lamps WG) | |
|---|---|---|---|
| Last updated | 2020-05-01 (latest revision 2019-10-29) | ||
| Replaces | draft-melnikov-lamps-header-protection | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | 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-lamps-header-protection-requirements-01.txt
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
(alexey.melnikov@isode.com)
Bernie Hoeneisen
(bernie@ietf.hoeneisen.ch)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)