IETF Logo Mail Archive

Re: [TLS] datacenter TLS decryption as a three-party protocol

Derrell Piper <ddp@electric-loft.org> Wed, 19 July 2017 16:36 UTC

Return-Path: <ddp@electric-loft.org>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82AE012F3CB for <tls@ietfa.amsl.com>; Wed, 19 Jul 2017 09:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=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 2PRjmL5u0Oby for <tls@ietfa.amsl.com>; Wed, 19 Jul 2017 09:36:45 -0700 (PDT)
Received: from Mail.Yoyodyne.COM (mail.yoyodyne.com [209.118.176.138]) by ietfa.amsl.com (Postfix) with SMTP id BBB28127077 for <tls@ietf.org>; Wed, 19 Jul 2017 09:36:45 -0700 (PDT)
Received: from [IPv6:2001:67c:370:128:bc7d:c18e:bcce:7d9f] ([2001:67c:370:128:bc7d:c18e:bcce:7d9f]) by Mail.Yoyodyne.COM via Internet for <tls@ietf.org>; Wed, 19 Jul 2017 09:36:45 PDT
From: Derrell Piper <ddp@electric-loft.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_51B0CCF4-5AAA-4D51-8465-A985DFC73DEB"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 19 Jul 2017 18:36:40 +0200
References: <81de2a21-610e-c2b3-d3ff-2fc598170369@akamai.com> <CAPt1N1mwYyTJVP1AyW0Zu3WBS6SCePAuR97-NQByTQh5Sg6eTA@mail.gmail.com> <CAJU8_nVfKi7iAFxTvVgYVd8G3V-mqMxMXE-03QoXxLSzMcmoHg@mail.gmail.com> <76bb50c5-a699-4c91-7993-618acb365baf@zinks.de> <B2046C73-F081-48F3-BF9F-53C955A4CD28@ll.mit.edu> <09CF3C56-E9C7-4F02-8D1F-B5766CC9430C@gmail.com>
To: "tls@ietf.org" <tls@ietf.org>
In-Reply-To: <09CF3C56-E9C7-4F02-8D1F-B5766CC9430C@gmail.com>
Message-Id: <0479B834-8E93-4590-B091-AD45CDDC812C@electric-loft.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Ty-p1Jg06RguslRQk1HjtKCcXEQ>
Subject: Re: [TLS] datacenter TLS decryption as a three-party protocol
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 16:36:51 -0000

> On Jul 19, 2017, at 6:02 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:
> 
> At the very least, a standards-track multi-party protocol like that can be something that standards like PCI, HIPAA and others can latch on to and say “Do TLS 1.3 without backdoors unless you really need to and in that case use *this*”.
> 
> That is better guidance than “Do TLS 1.3 without backdoors, unless you really need to and in that case do whatever works for you”

Yes, that’s what I would like to see after today’s meeting too.

v2.23.0 | Report a Bug | By Email