Securing Header Fields with S/MIME
draft-cailleux-secure-headers-02
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 7508.
Expired & archived
|
|
|---|---|---|---|
| Authors | Laurent Cailleux , Chris Bonatti | ||
| Last updated | 2013-07-14 (Latest revision 2013-01-10) | ||
| RFC stream | (None) | ||
| Formats | |||
| IETF conflict review | conflict-review-cailleux-secure-headers, conflict-review-cailleux-secure-headers, conflict-review-cailleux-secure-headers, conflict-review-cailleux-secure-headers, conflict-review-cailleux-secure-headers, conflict-review-cailleux-secure-headers | ||
| 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 how the S/MIME protocol can be extended in order to secure message header fields. This technology provides security services such as data integrity, non-repudiation and confidentiality. This extension is referred to as 'Secure Headers'.
Authors
Laurent Cailleux
Chris Bonatti
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)