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

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 21 November 2013 14:17 UTC

Return-Path: <superuser@gmail.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 17AED1AE17D; Thu, 21 Nov 2013 06:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 Rleegq-07u79; Thu, 21 Nov 2013 06:17:01 -0800 (PST)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5F01AE16F; Thu, 21 Nov 2013 06:17:01 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id x12so797966wgg.28 for <multiple recipients>; Thu, 21 Nov 2013 06:16:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lS7OC0dDQrl/GkTF++biafOUeBZ6EMkn3aAtd6IEehI=; b=sG/VZ8UwZ/VIigj4S6vUE2w/RuEQ6IsF2XUahBwEYF3pqFnx1X5YcjpwEmwOe8xI3P YmzHQgQYJeDd5pxOu6OKwfVctKlx0Q/Cc4Cxkb8bFtnvIoaiEuU+rNgQ0xppP8q2mEcE 5AD/3gxOja0wxKBxf5FQmpWBG8ZtBeXpgN5sSOybFQcmVr0WWxjMN5OiWsLp8xP3lfNF khhH9XKIjitRINo0eaG7losuz8BJCwo5ag9cRyuD8Jjrf07PZPCcvm2qM2zBbWqMx6Tb Ba4WzSNtOqO16BxyjITPJ8sukzjpvsEDcf/o3ldEbl0+e0rxHH34BEsb8HQKl1iBQNcj bIqA==
MIME-Version: 1.0
X-Received: by 10.180.39.238 with SMTP id s14mr6157453wik.60.1385043413971; Thu, 21 Nov 2013 06:16:53 -0800 (PST)
Received: by 10.181.13.230 with HTTP; Thu, 21 Nov 2013 06:16:53 -0800 (PST)
In-Reply-To: <20131121121728.12108.46847.idtracker@ietfa.amsl.com>
References: <20131121121728.12108.46847.idtracker@ietfa.amsl.com>
Date: Thu, 21 Nov 2013 06:16:53 -0800
Message-ID: <CAL0qLwaR7pvNxMgCz8gvFoj+ZX_nf=zL3KDqQxrFL8XxywKnKA@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="001a11c24faab03a2704ebb08c31"
Cc: "appsawg-chairs@tools.ietf.org" <appsawg-chairs@tools.ietf.org>, "draft-ietf-appsawg-malformed-mail@tools.ietf.org" <draft-ietf-appsawg-malformed-mail@tools.ietf.org>, The IESG <iesg@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, SM <sm+ietf@elandsys.com>
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: Thu, 21 Nov 2013 14:17:03 -0000

Hi Stephen,

On Thu, Nov 21, 2013 at 4:17 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie>wrote:

>
> Thanks for a useful document. I would have loved to have
> seen text about S/MIME and PGP issues, but I guess that
> might require another equally long document all by
> itself. It might well be worth looking though to see if
> there's a reference to which you could point that has
> relevant guidance about those.
>

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.


>
> Separately, it might also be worth pointing out that
> some of the handling guidance you give if applied to
> some S/MIME or PGP messages is likely to break
> signatures or make decryption impossible.
>
>
Sure, we can look at that angle as well.  Thanks for the suggestion.

-MSK