Re: [TLS] TLS 1.3 process

"Salz, Rich" <rsalz@akamai.com> Sun, 30 March 2014 16:56 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 222201A089B for <tls@ietfa.amsl.com>; Sun, 30 Mar 2014 09:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 2QqvvIb6o0e2 for <tls@ietfa.amsl.com>; Sun, 30 Mar 2014 09:56:39 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (prod-mail-xrelay06.akamai.com [96.6.114.98]) by ietfa.amsl.com (Postfix) with ESMTP id 4A26F1A06EA for <tls@ietf.org>; Sun, 30 Mar 2014 09:56:39 -0700 (PDT)
Received: from prod-mail-xrelay06.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 2F495165590; Sun, 30 Mar 2014 16:56:36 +0000 (GMT)
Received: from prod-mail-relay08.akamai.com (unknown [172.27.22.71]) by prod-mail-xrelay06.akamai.com (Postfix) with ESMTP id 241EC165588; Sun, 30 Mar 2014 16:56:36 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub5.kendall.corp.akamai.com [172.27.105.21]) by prod-mail-relay08.akamai.com (Postfix) with ESMTP id F2ED59803D; Sun, 30 Mar 2014 16:56:35 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([172.27.107.26]) by USMA1EX-CASHUB5.kendall.corp.akamai.com ([172.27.105.21]) with mapi; Sun, 30 Mar 2014 12:56:35 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Dan Harkins <dharkins@lounge.org>, Bill Frantz <frantz@pwpconsult.com>
Date: Sun, 30 Mar 2014 12:56:34 -0400
Thread-Topic: [TLS] TLS 1.3 process
Thread-Index: Ac9MNHDXJVsFytQcSwSa3cBsJuAKxwAA8/0w
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C711FD90EE3E@USMBX1.msg.corp.akamai.com>
References: <r422Ps-1075i-3F3E24809EA445E4888C1202C5515245@Williams-MacBook-Pro.local> <8812ef304b84ab08775b790b9a2ac415.squirrel@www.trepanning.net>
In-Reply-To: <8812ef304b84ab08775b790b9a2ac415.squirrel@www.trepanning.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/9BBZncyjSI1QMLCPEhLCk07ao3I
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] TLS 1.3 process
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 30 Mar 2014 16:56:40 -0000

One use (sic) of use-cases is that they are helpful to determine what's in-scope and what's out of scope.  For example, DNS is typically over UDP and doesn't care about replay or out of order. TLS-layer compression has security issues, and arguably application-level compression can be more effective by leveraging semantics (e.g., HTTP2 headers).  Both of those cases impact encryption.

I share the concern about not being distracted, but nowhere near as strongly as Dan.  And we're certainly not all concerned about getting authentication working correctly; it depends on what the definition of correctly is, I suppose.

	/r$

--  
Principal Security Engineer
Akamai Technology
Cambridge, MA