Re: [yam] AD DISCUSS about Section 8 of draft-ietf-yam-rfc4409bis-02 - Message Modifications

"John Levine" <johnl@taugh.com> Tue, 23 August 2011 07:13 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: yam@ietfa.amsl.com
Delivered-To: yam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F88421F8B18 for <yam@ietfa.amsl.com>; Tue, 23 Aug 2011 00:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.115
X-Spam-Level:
X-Spam-Status: No, score=-111.115 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ckPwu+ntHYVI for <yam@ietfa.amsl.com>; Tue, 23 Aug 2011 00:13:47 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 0166321F8AF6 for <yam@ietf.org>; Tue, 23 Aug 2011 00:13:45 -0700 (PDT)
Received: (qmail 61531 invoked from network); 23 Aug 2011 07:14:50 -0000
Received: from gal.iecc.com (64.57.183.53) by mail2.iecc.com with SMTP; 23 Aug 2011 07:14:50 -0000
Received: (qmail 27724 invoked from network); 23 Aug 2011 07:14:50 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 23 Aug 2011 07:14:50 -0000
Date: Tue, 23 Aug 2011 07:14:28 -0000
Message-ID: <20110823071428.18097.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: yam@ietf.org
In-Reply-To: <6.2.5.6.2.20110822151213.0aea6018@elandnews.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Cc: sm+ietf@elandsys.com
Subject: Re: [yam] AD DISCUSS about Section 8 of draft-ietf-yam-rfc4409bis-02 - Message Modifications
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 07:13:47 -0000

>     If an incoming message includes a DKIM [DKIM], PGP [RFC4880],
>     S/MIME [RFC5751], or other signature, sites SHOULD consider what
>     effect message modifications will have on the validity of the
>     signature, and MAY use the presence or absence of a signature as
>     a criterion when deciding what, if any, modifications to make.

I think the existing text is dandy, but I would, since I wrote it.

I suppose we could add some examples, but as others have noted, there's
a lot of different possibilities, and we don't know what they are.  The
sort of stuff I was thinking of includes:

* If there's a valid S/MIME signature, don't mess with the body.  (I
can tell you from experience that if you wrap a signed MIME body in a
multipart/related, about half of MUAs will still recognize the
signature and half won't.)

* If there's a DKIM signature, and the MSA doesn't sign, don't mess
with the message.  But if the MSA does sign, do mess and then sign the
modified message.

I'm not saying either of these are always the right thing to do, but
they're the sort of tradeoffs I had in mind.  And I'm not at all sure
that there is any way to say that that will not be misread as
normative NEVER CHANGE A DKIM SIGNED MESSAGE or the like.

R's,
John