Considerations for protecting Email header with S/MIME
draft-melnikov-smime-header-signing-05
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2018-04-19 (latest revision 2017-10-02) | ||
| 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) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-melnikov-smime-header-signing-05.txt
https://www.ietf.org/archive/id/draft-melnikov-smime-header-signing-05.txt
Abstract
This document describes best practices for handling of Email header protected by S/MIME. It also adds a new Content-Type parameter to help distinguish an S/MIME protected forwarded message from an S/MIME construct protecting message header.
Authors
Alexey Melnikov (alexey.melnikov@isode.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)