Re: [TLS] 0-RTT and Anti-Replay

"Salz, Rich" <rsalz@akamai.com> Mon, 23 March 2015 15:06 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 8B93D1A901C for <tls@ietfa.amsl.com>; Mon, 23 Mar 2015 08:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 qg-zCbxXjnwb for <tls@ietfa.amsl.com>; Mon, 23 Mar 2015 08:06:26 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (prod-mail-xrelay02.akamai.com [72.246.2.14]) by ietfa.amsl.com (Postfix) with ESMTP id 262A21A8FD6 for <tls@ietf.org>; Mon, 23 Mar 2015 08:06:26 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (localhost [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 6FE2528878 for <tls@ietf.org>; Mon, 23 Mar 2015 15:06:25 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (prod-mail-relay07.akamai.com [172.17.121.112]) by prod-mail-xrelay02.akamai.com (Postfix) with ESMTP id 59B0228867 for <tls@ietf.org>; Mon, 23 Mar 2015 15:06:25 +0000 (GMT)
Received: from email.msg.corp.akamai.com (usma1ex-cas3.msg.corp.akamai.com [172.27.123.32]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id 55C538004A for <tls@ietf.org>; Mon, 23 Mar 2015 15:06:25 +0000 (GMT)
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com (172.27.123.102) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.913.22; Mon, 23 Mar 2015 11:06:06 -0400
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com ([172.27.123.102]) by usma1ex-dag1mb2.msg.corp.akamai.com ([172.27.123.102]) with mapi id 15.00.0913.011; Mon, 23 Mar 2015 11:06:06 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "Sniffen, Brian" <bsniffen@akamai.com>
Thread-Topic: [TLS] 0-RTT and Anti-Replay
Thread-Index: AQHQZOoxUeEZJ8kfGkGiuqONqc5YFZ0qXeyAgAACMICAAA1ugP//vYog
Date: Mon, 23 Mar 2015 15:06:06 +0000
Message-ID: <f23afade22374f538a3a472711928313@usma1ex-dag1mb2.msg.corp.akamai.com>
References: <CABcZeBP9LaGhDVETsJeecnAtSPUj=Kv37rb_2esDi3YaGk9b4w@mail.gmail.com> <55101D8B.7050909@zinks.de> <CABkgnnXm3LMsy7sN--Q35ZxVUXj=hQG0+JJarSF6U=ayZ1NZ4A@mail.gmail.com> <m2bnjjlpwa.fsf@usma1mc-0csx92.kendall.corp.akamai.com>
In-Reply-To: <m2bnjjlpwa.fsf@usma1mc-0csx92.kendall.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.113.103]
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/0FNRLBu-WrwadceaqkXFi8psH2M>
Cc: "TLS@ietf.org \(tls@ietf.org\)" <tls@ietf.org>
Subject: Re: [TLS] 0-RTT and Anti-Replay
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: Mon, 23 Mar 2015 15:06:30 -0000

> APIs offering a socket model and attempting to provide a secure socket layer
> shouldn't use the 0RTT path at all, then?

TLS_SOCKOPT_STOP_ME_IF_YOUVE_HEARD_THIS_BEFORE ?

Call me cynical, but search engines are going to force adoption of this.

--  
Senior Architect, Akamai Technologies
IM: rsalz@jabber.me Twitter: RichSalz