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

"Joe Abley" <jabley@hopcount.ca> Tue, 02 June 2015 18:28 UTC

Return-Path: <jabley@hopcount.ca>
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 E854E1B34B0 for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 11:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 zTonK9l-aSU6 for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 11:28:41 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (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 92F1F1B34AE for <ietf@ietf.org>; Tue, 2 Jun 2015 11:28:41 -0700 (PDT)
Received: by wgbgq6 with SMTP id gq6so147460474wgb.3 for <ietf@ietf.org>; Tue, 02 Jun 2015 11:28:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-type; bh=czsG5wyWGINZ/gwWVmJAecw0CYABLCIbRPCaDMUKbXQ=; b=UyR9EW4ov2YsuAf3Uf2wH7bf9/GgOBXQoI/FWta2WGEkKqRxwrHPkpTUEzw/1nt2zp RG5L5tnaQYUXXJYQXV1mBNUoERgFzFWd/gdb3pTo8Nse+bpUaeVCdapEcSoyRkCT9/X6 Ly9wvYPB7PvZTdyDkJwfS8WVMFTsc8uZTluow=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-type; bh=czsG5wyWGINZ/gwWVmJAecw0CYABLCIbRPCaDMUKbXQ=; b=Rif+RUPnnByVde7CqpQXFoUoaMVwB4OZkMAH3nUnQikfYvbjLQkivWX3axfWjtgj4S V0ug46uKnh5FwAbaJNxv9MBLV3injcSOSzHB2Wlpu8cfeuObjQ2Fu0Ii2yg41ncTO+hs yz8ydRQtkSlzzKqC35tPk7mtZ3YCD+xsFfiMT+NesnUbsoVdfiz51jyFWRHGp7qk4sI5 jlrRpL4emb9k5V5fITivC3Ue2hC4J94z1sGLRjk3biem/zXn19P6KnMr1xhbxKNgsB2i VR3eAf6hXibzrSSFhe7di5EdDuWacrWrMKyiT7paeA4msV2TrgfqfHx0ubpQt/GCGh/b aWzQ==
X-Gm-Message-State: ALoCoQkzjNcSDfIlpIueyXOcvZ9k8XcGp5/FoRKEeRIzR3zwapj62/kLm8q6Qz8U1OlD1zh4JKEG
X-Received: by 10.180.82.6 with SMTP id e6mr33968654wiy.84.1433269720023; Tue, 02 Jun 2015 11:28:40 -0700 (PDT)
Received: from [10.0.4.42] ([193.95.80.178]) by mx.google.com with ESMTPSA id z9sm22857675wiv.9.2015.06.02.11.28.09 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 02 Jun 2015 11:28:39 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
To: Nico Williams <nico@cryptonector.com>
Subject: Re: Proposed Proposed Statement on e-mail encryption at the IETF
Date: Tue, 02 Jun 2015 18:59:30 +0100
Message-ID: <3B90AA8C-693A-424B-8724-508FD85AAF3F@hopcount.ca>
In-Reply-To: <20150602174825.GM17122@localhost>
References: <DD88F4E4-6BBA-4610-BB49-3158A26DF55B@hopcount.ca> <2DA10E34-02DA-4245-9031-8C0F2749461D@vpnc.org> <20150602174825.GM17122@localhost>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.1r5084)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8CaPBtzpO_4wUPvDmvjhSNBoOPo>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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 18:28:43 -0000

On 2 Jun 2015, at 18:48, Nico Williams wrote:

> On Tue, Jun 02, 2015 at 10:15:54AM -0700, Paul Hoffman wrote:
>> On Jun 2, 2015, at 6:44 AM, Joe Abley <jabley@hopcount.ca> wrote:
>>> If the argument that we should use HTTPS everywhere (which I do not
>>> disagree with) is reasonable, it feels like an argument about
>>> sending encrypted e-mail whenever possible ought to be similarly
>>> reasonable. Given that so much of the work of the IETF happens over
>>> e-mail, a focus on HTTP seems a bit weird.
>
> There's no point to encrypting (to subscribers) posts to *public*
> mailing lists!

Yes, I know. Hence "wherever possible". If you have an expectation that 
the contents of e-mail conversations are public (e.g. in archives) then 
that's not possible. So that's not what I am talking about.

> There's also no point to doing anything more than DKIM as far as the
> mailing list processor goes.

Sure.

> Users should be (and are) able to sign their posts if they like, but I
> don't think there's much point to requiring them to.

All agreed.

Perhaps you didn't read my original e-mail, and are just responding to 
quoted fragments of it; I was talking about all the e-mail that doesn't 
involve public lists. The example I gave was based on an imagined desire 
of someone to say something to the IAB as a closed group, not on a 
public list, and desiring some privacy in their communications. There 
are surely other examples.


Joe