Considerations for protecting Email header with S/MIME
draft-melnikov-lamps-header-protection-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Alexey Melnikov | ||
| Last updated | 2019-04-21 (Latest revision 2018-10-18) | ||
| Replaced by | draft-ietf-lamps-header-protection-requirements | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-lamps-header-protection-requirements | |
| 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
This document describes best practices for handling of Email header protected by S/MIME. Procedures described in this document are also applicable to OpenPGP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)