IETF Logo Mail Archive

[TLS] tickets or sesssions or both (oh my)

"Salz, Rich" <rsalz@akamai.com> Tue, 02 September 2014 17:05 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 53B551A0706 for <tls@ietfa.amsl.com>; Tue, 2 Sep 2014 10:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level:
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.668] 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 Es50glhh8mAe for <tls@ietfa.amsl.com>; Tue, 2 Sep 2014 10:05:14 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [72.246.2.115]) by ietfa.amsl.com (Postfix) with ESMTP id 39E1B1A0700 for <tls@ietf.org>; Tue, 2 Sep 2014 10:05:13 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id A32C2474C7 for <tls@ietf.org>; Tue, 2 Sep 2014 17:05:10 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (prod-mail-relay07.akamai.com [172.17.121.112]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id 960E4474BA for <tls@ietf.org>; Tue, 2 Sep 2014 17:05:10 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub6.kendall.corp.akamai.com [172.27.105.22]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id 8E38A80040 for <tls@ietf.org>; Tue, 2 Sep 2014 17:05:10 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([169.254.1.218]) by USMA1EX-CASHUB6.kendall.corp.akamai.com ([172.27.105.22]) with mapi; Tue, 2 Sep 2014 13:05:10 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "TLS@ietf.org (tls@ietf.org)" <tls@ietf.org>
Date: Tue, 02 Sep 2014 13:05:09 -0400
Thread-Topic: tickets or sesssions or both (oh my)
Thread-Index: Ac/Gz8oQp3LCuGinQ4CDT7fKauIhyw==
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C71D1204BE08@USMBX1.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2A0EFB9C05D0164E98F19BB0AF3708C71D1204BE08USMBX1msgcorp_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/PVNs4vcfrxYPMCa45rf9LVR5gy4
Subject: [TLS] tickets or sesssions or both (oh my)
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: Tue, 02 Sep 2014 17:05:19 -0000

Right now we have sessions (server-side, possible scalability issues) and tickets (client-side, hard to make work well with PFS).

A poll for this community: is one likely to be more strategic, or are both likely to be important in the near term  (say within two years after TLS 1.3 is done).

--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: rsalz@jabber.me<mailto:rsalz@jabber.me> Twitter: RichSalz

v2.23.0 | Report a Bug | By Email