Re: [lamps] I-D Action: draft-ietf-lamps-header-protection-10.txt

Russ Housley <housley@vigilsec.com> Wed, 21 December 2022 17:43 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E563C14F72F for <spasm@ietfa.amsl.com>; Wed, 21 Dec 2022 09:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3NyH-goYsmtW for <spasm@ietfa.amsl.com>; Wed, 21 Dec 2022 09:43:10 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1CD6C14F731 for <spasm@ietf.org>; Wed, 21 Dec 2022 09:43:10 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 41586140E51 for <spasm@ietf.org>; Wed, 21 Dec 2022 12:43:09 -0500 (EST)
Received: from a860b60074bd.fios-router.home (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 2DB9F140CF9 for <spasm@ietf.org>; Wed, 21 Dec 2022 12:43:09 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Wed, 21 Dec 2022 12:43:08 -0500
References: <167158132346.30562.10162999394367899551@ietfa.amsl.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <167158132346.30562.10162999394367899551@ietfa.amsl.com>
Message-Id: <2DD12DD2-F92B-4C22-B8C2-B6728D16502A@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.21)
X-Scanned-By: mailmunge 3.10 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/TNNxTHWBY_kd9ukzCoUrgQH4PlM>
Subject: Re: [lamps] I-D Action: draft-ietf-lamps-header-protection-10.txt
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2022 17:43:14 -0000

Thanks for posting the update.  I have two minor suggestions.

Section 2.3.2: s/header field name name/header field name/

Section 2.5.8.1 says:

   When crafting the headers for a reply message, the composing MUA can
   make use of the reference message's HP-Removed and HP-Obscured
   headers (from within the cryptographic envelope) to ensure that
   headers derived from the reference message do not leak in the reply.

I suggest a small rewording:

   When crafting the headers for a reply message, the composing MUA can
   make use of the HP-Removed and HP-Obscured headers from within
   the cryptographic envelope of the reference message to ensure that
   headers derived from the reference message do not leak in the reply.

Russ

> On Dec 20, 2022, at 7:08 PM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Limited Additional Mechanisms for PKIX and SMIME WG of the IETF.
> 
>        Title           : Header Protection for S/MIME
>        Authors         : Daniel Kahn Gillmor
>                          Bernie Hoeneisen
>                          Alexey Melnikov
>  Filename        : draft-ietf-lamps-header-protection-10.txt
>  Pages           : 178
>  Date            : 2022-12-20
> 
> 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 to offer a different
>   mechanism that provides the same cryptographic protections but with
>   fewer downsides when handled by legacy clients.  Furthermore, it
>   offers more explicit guidance for clients when generating or handling
>   e-mail messages with cryptographic protection of message headers.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-header-protection/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-lamps-header-protection-10
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lamps-header-protection-10
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm