Considerations for protecting Email header with S/MIME
draft-melnikov-smime-header-signing-03
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Alexey Melnikov | ||
| Last updated | 2017-02-25 (Latest revision 2016-08-24) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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. 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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)