Skip to main content

Considerations for protecting Email header with S/MIME

Document Type Expired Internet-Draft (individual)
Author Alexey Melnikov
Last updated 2018-04-19 (Latest revision 2017-10-02)
Stream (None)
Intended RFC status (None)
Expired & archived
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 can be found at:


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.


Alexey Melnikov

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)