Re: [TLS] The case for a single stream of data
Ilari Liusvaara <ilariliusvaara@welho.com> Sat, 06 May 2017 09:58 UTC
Return-Path: <ilariliusvaara@welho.com>
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 8781D12751F for <tls@ietfa.amsl.com>; Sat, 6 May 2017 02:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level:
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 nUqueLzeIOfb for <tls@ietfa.amsl.com>; Sat, 6 May 2017 02:58:38 -0700 (PDT)
Received: from welho-filter2.welho.com (welho-filter2.welho.com [83.102.41.24]) by ietfa.amsl.com (Postfix) with ESMTP id 90A14126C23 for <tls@ietf.org>; Sat, 6 May 2017 02:58:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by welho-filter2.welho.com (Postfix) with ESMTP id B962C213DA; Sat, 6 May 2017 12:58:35 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp2.welho.com ([IPv6:::ffff:83.102.41.85]) by localhost (welho-filter2.welho.com [::ffff:83.102.41.24]) (amavisd-new, port 10024) with ESMTP id vt5vdaP7rrmX; Sat, 6 May 2017 12:58:35 +0300 (EEST)
Received: from LK-Perkele-V2 (87-92-51-204.bb.dnainternet.fi [87.92.51.204]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by welho-smtp2.welho.com (Postfix) with ESMTPSA id 7AF0821C; Sat, 6 May 2017 12:58:35 +0300 (EEST)
Date: Sat, 06 May 2017 12:58:35 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: Colm MacCárthaigh <colm@allcosts.net>
Cc: "tls@ietf.org" <tls@ietf.org>
Message-ID: <20170506095834.GA4355@LK-Perkele-V2.elisa-laajakaista.fi>
References: <CAAF6GDfm=voTt_=JrdGtiaYby1JG8ySU2s6myjjpHKeGvi0bMg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAAF6GDfm=voTt_=JrdGtiaYby1JG8ySU2s6myjjpHKeGvi0bMg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/qFwUCBY-uaBEUroy0lWsk1Beggk>
Subject: Re: [TLS] The case for a single stream of data
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: Sat, 06 May 2017 09:58:40 -0000
On Fri, May 05, 2017 at 09:28:07AM -0700, Colm MacCárthaigh wrote: > I wanted to start a separate thread on this, just to make some small > aspects of replay mitigating clear, because I'd like to make a case for TLS > providing a single-stream, which is what people seem to be doing anyway. <Snip a long mail> Couple points: - AFAIK, the 10 second or so figure in existing spec is a slop margin, which means the replay window would be 20 seconds, not 10. - The size of the window depends on clock error margin and transport delay margin. At 1s/day clock error margin, you need 14 second window just from clock error. - It is not just low-power devices with really bad clocks. I have seen 20s per day(!) clock drift on high-power device that doesn't sleep. - So basically, the size of window is tradeoff with number of devices. - That automatic wait on 0-RTT failure seems just the kind of feature that gets disabled. Furthermore, 10 second idle on connection is going to trigger quite a bit of connection timeouts. - There seems to be no consideration how this interacts with 0-RTT exporters (probably applications that accept 0-RTT will then use 0-RTT exporters for the entiere connection, and those exporters have seriously weaker properties). -Ilari
- [TLS] The case for a single stream of data Colm MacCárthaigh
- Re: [TLS] The case for a single stream of data Ilari Liusvaara
- Re: [TLS] The case for a single stream of data Salz, Rich
- Re: [TLS] The case for a single stream of data Kyle Rose
- Re: [TLS] The case for a single stream of data Ilari Liusvaara
- Re: [TLS] The case for a single stream of data Kyle Rose
- Re: [TLS] The case for a single stream of data Eric Rescorla
- Re: [TLS] The case for a single stream of data Benjamin Kaduk
- Re: [TLS] The case for a single stream of data Ilari Liusvaara
- Re: [TLS] The case for a single stream of data Benjamin Kaduk
- Re: [TLS] The case for a single stream of data Salz, Rich
- Re: [TLS] The case for a single stream of data Viktor Dukhovni
- Re: [TLS] The case for a single stream of data Colm MacCárthaigh
- Re: [TLS] The case for a single stream of data Salz, Rich
- Re: [TLS] The case for a single stream of data Salz, Rich
- Re: [TLS] The case for a single stream of data Andrei Popov
- Re: [TLS] The case for a single stream of data Roland Zink
- Re: [TLS] The case for a single stream of data Colm MacCárthaigh
- Re: [TLS] The case for a single stream of data Ilari Liusvaara
- Re: [TLS] The case for a single stream of data Colm MacCárthaigh
- Re: [TLS] The case for a single stream of data Benjamin Kaduk
- Re: [TLS] The case for a single stream of data Colm MacCárthaigh
- Re: [TLS] The case for a single stream of data Ilari Liusvaara
- Re: [TLS] The case for a single stream of data Ilari Liusvaara