Header Protection for S/MIME
draft-ietf-lamps-header-protection-06
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Daniel Kahn Gillmor , Bernie Hoeneisen , Alexey Melnikov | ||
Last updated | 2022-01-27 (Latest revision 2021-07-26) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
GENART Last Call review
(of
-20)
by Peter Yee
Ready w/nits
ARTART Last Call review
(of
-20)
by Bron Gondwana
Ready w/nits
SECDIR Last Call Review due 2024-03-25
Incomplete
OPSDIR Last Call Review due 2024-03-25
Incomplete
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Associated WG milestone |
|
||
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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
S/MIME version 3.1 has introduced a feasible standardized option to accomplish Header Protection. However, few implementations generate messages using this structure, and several legacy and non-legacy implementations have revealed rendering issues at the receiving side. Clearer specifications regarding message processing, particularly with respect to header sections, are needed in order to resolve these rendering issues. Some mail user agents are also sending and receiving cryptographically-protected message headers using a different structure. In order to help implementers to correctly compose and render email messages with Header Protection, this document updates S/MIME Header Protection specifications with additional guidance on MIME format, sender and receiver processing.
Authors
Daniel Kahn Gillmor
Bernie Hoeneisen
Alexey Melnikov
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)