Last Call: <draft-ietf-lamps-header-protection-20.txt> (Header Protection for Cryptographically Protected E-mail) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 04 March 2024 16:37 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-lamps-header-protection-20.txt> (Header Protection for Cryptographically Protected E-mail) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-lamps-header-protection@ietf.org, housley@vigilsec.com, lamps-chairs@ietf.org, rdd@cert.org, spasm@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <170957023196.14016.17680168906943528470@ietfa.amsl.com>
Date: Mon, 04 Mar 2024 08:37:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/FWub2Z_3bR8vSg4LyXGwdpC56zs>

The IESG has received a request from the Limited Additional Mechanisms for
PKIX and SMIME WG (lamps) to consider the following document: - 'Header
Protection for Cryptographically Protected E-mail'
  <draft-ietf-lamps-header-protection-20.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-03-25. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   S/MIME version 3.1 introduced a mechanism to provide end-to-end
   cryptographic protection of e-mail message headers.  However, few
   implementations generate messages using this mechanism, and several
   legacy implementations have revealed rendering or security issues
   when handling such a message.

   This document updates the S/MIME specification ([RFC8551]) to offer a
   different mechanism that provides the same cryptographic protections
   but with fewer downsides when handled by legacy clients.  The Header
   Protection schemes described here are also applicable to messages
   with PGP/MIME cryptographic protections.  Furthermore, this document
   offers more explicit guidance for clients when generating or handling
   e-mail messages with cryptographic protection of message headers.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lamps-header-protection/



No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    draft-ietf-lamps-e2e-mail-guidance: Guidance on End-to-End E-mail Security (None - Internet Engineering Task Force (IETF))
    draft-ietf-lamps-header-protection-requirements: Problem Statement and Requirements for Header Protection (None - Internet Engineering Task Force (IETF))

Last Call: <draft-ietf-lamps-header-protection-20… The IESG