Re: Proposed Proposed Statement on e-mail encryption at the IETF

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 02 June 2015 14:59 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5741ACD52 for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 07:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 TDhMiy0LQbiK for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 07:59:11 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB1CC1ACD54 for <ietf@ietf.org>; Tue, 2 Jun 2015 07:59:10 -0700 (PDT)
Received: by lbbqq2 with SMTP id qq2so106180487lbb.3 for <ietf@ietf.org>; Tue, 02 Jun 2015 07:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=hGnIq8K5+FYWCRJloRJDU+xYvc/k8SL0BkpBRSfrKbo=; b=XEDYB0nrAke846uVOmty/eFrqSdG1OoW6Cu96eueM65qS37Wixix4avPzKNuZ3fWyM CeaJelBIgUkyIoLrcOB3E4PVU4B/JzTqvQaMxe6UTNIA+HSL1BZsN+sNruzPjhKDIojD xTAjIA+vb4S/k3/Opi1CsWnU/X0GOA7WVzQ2h925Oz0EUlT3oM/PSFOZkhctFqyRHIWE TJIvan5kX3+sA/DEi2hCqKgMHFhWYFBIhPZkQzq6AJ0Ov+PitOicvApDxTllIBDdylJo V76C2UX76m5JaQKmfqJe9stNQ+C2jm/dTLJ9dEiRhH+SkZUZqEh+4hYuZxx9H+eR4574 auWA==
MIME-Version: 1.0
X-Received: by 10.112.40.9 with SMTP id t9mr27235889lbk.55.1433257149465; Tue, 02 Jun 2015 07:59:09 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.203.163 with HTTP; Tue, 2 Jun 2015 07:59:09 -0700 (PDT)
In-Reply-To: <556DB997.6030800@cs.tcd.ie>
References: <DD88F4E4-6BBA-4610-BB49-3158A26DF55B@hopcount.ca> <556DB997.6030800@cs.tcd.ie>
Date: Tue, 02 Jun 2015 10:59:09 -0400
X-Google-Sender-Auth: EWqm1vXBdDrZ7PYE2fDvXGdBfp0
Message-ID: <CAMm+LwjRgLV+26fOGKysa5JaS3_2qcHT=vB_rMjbPKyaSGagqQ@mail.gmail.com>
Subject: Re: Proposed Proposed Statement on e-mail encryption at the IETF
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="001a11336578440cdc05178a2f70"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NenCf4dbk-htV-cT0CkpN5SJISI>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2015 14:59:12 -0000

On Tue, Jun 2, 2015 at 10:11 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> Hiya,
>
> On 02/06/15 14:44, Joe Abley wrote:
>
> > Note that this is not an attempt to start a conversation about
> > whether PGP is usable, or whether S/MIME is better. I will fall off
> > my chair in surprise if it doesn't turn into one, though.
>
> We have a list for such discussion [1] if folks feel the need.
> And I know PHB has an interesting idea to try to merge the two
> in terms of message formats. I'm not sure that's feasible but
> discuss on [1] if you feel the need. And please don't have that
> discussion here unless there's a reason for it to be here and
> not there:-)
>

Actually merge the two as far as the user is aware.

Obviously, the more components are shared, the easier things become for
implementations. But adding message formats is not the hard part. I'll
probably have something for endymail next week.


The bigger issue for me is 'mailing list'. I can easily write a protocol
for an end to end secure collaborative forum as a Web Service but there is
no way that I expect to do anything useful with legacy SMTP infrastructure
as the transport.

SMTP sucks as a mailing list protocol.


What we need is a return to something that is a bit more like NNTP which
began life as an attempt to make mailing list interactions more efficient.