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

Viktor Dukhovni <ietf-dane@dukhovni.org> Mon, 23 March 2015 17:14 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 EB0AF1ACE55 for <tls@ietfa.amsl.com>; Mon, 23 Mar 2015 10:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 RUN5y4oOhOch for <tls@ietfa.amsl.com>; Mon, 23 Mar 2015 10:14:41 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1C2B1ACE4F for <tls@ietf.org>; Mon, 23 Mar 2015 10:14:40 -0700 (PDT)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id D72E8283011; Mon, 23 Mar 2015 17:14:39 +0000 (UTC)
Date: Mon, 23 Mar 2015 17:14:39 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: tls@ietf.org
Message-ID: <20150323171439.GL9387@mournblade.imrryr.org>
References: <CABkgnnWXtpuSKH-eEou9O7qncUSeuiv=4kw_GE6Um8VW3dcohQ@mail.gmail.com> <20150323083308.GL21267@localhost> <20150323144052.GF9387@mournblade.imrryr.org> <55102E3A.70300@zinks.de> <20150323152831.GG9387@mournblade.imrryr.org> <55103A6E.4060409@zinks.de> <20150323162200.GI9387@mournblade.imrryr.org> <20150323165201.GA15202@LK-Perkele-VII> <20150323165936.GK9387@mournblade.imrryr.org> <20150323170733.GA18328@LK-Perkele-VII>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150323170733.GA18328@LK-Perkele-VII>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/XAGe-KwTMskoJeTlqFj7ilQzmcY>
Subject: Re: [TLS] 0-RTT and Anti-Replay
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tls@ietf.org
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 17:14:42 -0000

On Mon, Mar 23, 2015 at 07:07:33PM +0200, Ilari Liusvaara wrote:

> > A connection on which the initial data was lost is broken.  Signalling
> > such loss is simplest by dropping the connection.
> 
> No, it isn't. The client will need to handle 0-RTT being lost
> anyway.

Naturally before disconnecting, the server stack should send an
appropriate alert.  But since clients should only be configured
for 0-RTT with application protocols where the server is required
to support 0-RTT, there's no point in falling back.

I don't see 0-RTT as an "opportunistic" feature.  I see it as
support for latency-sensitive idempotent applications in which it
is always used.  Eliminating fallback to 1-RTT avoids much complexity.

-- 
	Viktor.