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

"MH Michael Hammer (5304)" <MHammer@ag.com> Tue, 02 June 2015 13:55 UTC

Return-Path: <MHammer@ag.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 B66361A9131 for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 06:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 r-MXnUO3yULN for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 06:55:32 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.4]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEE681A90F8 for <ietf@ietf.org>; Tue, 2 Jun 2015 06:55:31 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES532.agna.amgreetings.com ([::1]) with mapi id 14.03.0210.002; Tue, 2 Jun 2015 09:55:30 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Joe Abley <jabley@hopcount.ca>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: RE: Proposed Proposed Statement on e-mail encryption at the IETF
Thread-Topic: Proposed Proposed Statement on e-mail encryption at the IETF
Thread-Index: AQHQnTpbC94/wtuqjUCzyqkvIF6T2Z2ZPMOg
Date: Tue, 02 Jun 2015 13:55:30 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B05260596B7@USCLES544.agna.amgreetings.com>
References: <DD88F4E4-6BBA-4610-BB49-3158A26DF55B@hopcount.ca>
In-Reply-To: <DD88F4E4-6BBA-4610-BB49-3158A26DF55B@hopcount.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.144.15.228]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CBh1eKHJXTWgESV_ejnIFZUE3oE>
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 13:55:33 -0000


> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Joe Abley
> Sent: Tuesday, June 02, 2015 9:45 AM
> To: IETF Discussion Mailing List
> Subject: Proposed Proposed Statement on e-mail encryption at the IETF
> 
> Hi all,
> 
> All this "HTTPS everywhere" mail collided for me this morning with a similar
> avalanche of press about Facebook's freshly-announced use of PGP:
> 
> https://www.facebook.com/notes/protecting-the-graph/securing-email-
> communications-from-facebook/1611941762379302
> 
> Mail to public mailing lists can already be signed (like this one is). It'd be nice if
> mailman didn't MITM the signed content, so that the signature can be
> validated. (Perhaps it will; I will find out after I hit send.) There's lots of other
> mail from individuals to closed groups like the IAB and the IESG and from IETF
> robots to individuals that *could* be encrypted, or at least signed. There is
> work here that *could* be done.
> 
> 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.
> 
> 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.
> 
> 
> Joe

Are the IETF mail servers configured to use opportunistic TLS? I haven't checked. To me this would be a good first step down the mail encryption path.

Mike