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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 21 November 2013 17:52 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 20B9B1AE00B for <apps-discuss@ietfa.amsl.com>; Thu, 21 Nov 2013 09:52:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525] 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 BGMOi8R--DPm for <apps-discuss@ietfa.amsl.com>; Thu, 21 Nov 2013 09:52:55 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id C8CB61AD79D for <apps-discuss@ietf.org>; Thu, 21 Nov 2013 09:52:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1B9D7BE5C; Thu, 21 Nov 2013 17:52:47 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzaantznyBQM; Thu, 21 Nov 2013 17:52:43 +0000 (GMT)
Received: from [10.87.48.12] (unknown [86.42.24.123]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5F835BE6F; Thu, 21 Nov 2013 17:52:43 +0000 (GMT)
Message-ID: <528E486B.10809@cs.tcd.ie>
Date: Thu, 21 Nov 2013 17:52:43 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>, apps-discuss@ietf.org
References: <20131121171252.41040.qmail@joyce.lan>
In-Reply-To: <20131121171252.41040.qmail@joyce.lan>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 17:52:58 -0000

On 11/21/2013 05:12 PM, John Levine wrote:
>> 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.
> 
> I'm not a co-author, but other than messages signed with expired keys
> it's hard to think of anything.  In general, if you don't have the
> key, you can't verify the signature or decode the message, so there's
> nothing to fix.

Well there were cases of folks messing up when they forwarded
signed mails and so on, but maybe those were all sorted in the
end. Paul H. might even have written something up back in his
IMC days. But again, I'm not asking that stuff like that be
added unless the authors want to do it.

S

> 
>  
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
> 
>