Re: [apps-discuss] Stephen Farrell's Yes on draft-ietf-appsawg-malformed-mail-10: (with COMMENT)

Ned Freed <ned.freed@mrochek.com> Fri, 22 November 2013 15:50 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E665F1AE358; Fri, 22 Nov 2013 07:50:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtpytKlIhemi; Fri, 22 Nov 2013 07:50:54 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id D9C3C1AE19B; Fri, 22 Nov 2013 07:50:52 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P12VSUPJO00010VI@mauve.mrochek.com>; Fri, 22 Nov 2013 07:45:43 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="iso-8859-1"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P0USA6030W00004G@mauve.mrochek.com>; Fri, 22 Nov 2013 07:45:37 -0800 (PST)
Message-id: <01P12VSSBO5Y00004G@mauve.mrochek.com>
Date: Fri, 22 Nov 2013 07:41:43 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 21 Nov 2013 08:58:38 -0800" <20131121165838.GC78520@C02KN7GSDTY3.corp.proofpoint.com>
References: <20131121121728.12108.46847.idtracker@ietfa.amsl.com> <CAL0qLwaR7pvNxMgCz8gvFoj+ZX_nf=zL3KDqQxrFL8XxywKnKA@mail.gmail.com> <20131121165838.GC78520@C02KN7GSDTY3.corp.proofpoint.com>
To: Gregory Shapiro <gshapiro@proofpoint.com>
Cc: "draft-ietf-appsawg-malformed-mail@tools.ietf.org" <draft-ietf-appsawg-malformed-mail@tools.ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, SM <sm+ietf@elandsys.com>, "appsawg-chairs@tools.ietf.org" <appsawg-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [apps-discuss] Stephen Farrell's Yes on draft-ietf-appsawg-malformed-mail-10: (with COMMENT)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Nov 2013 15:50:55 -0000

> >    I don't think I've ever seen an ambiguity in an email message that
> >    included S/MIME or PGP, so I don't have much to offer here.  My
> >    co-authors might, so I'll let them chime in if so.  I'll do a quick
> >    look around to see what I can find.

> Like Murray, I haven't observed any S/MIME or PGP mangling (which doesn't
> mean it doesn't happen, just that it hasn't been caught).

We mostly deal with S/MIME, and I can't recall a case where an S/MIME
message (either signed or encrypted) got mangled. Certificate problems sure,
but that's a different sort of thing.

Signed PGP messages get "mangled" all the time, but that's because a lot of PGP
still uses the text/plain approach rather than multipart/signed. I regard this
as a case of PGP acting stupidly and getting exactly what it deserves.

				Ned