IETF Logo Mail Archive

Re: [TLS] PR#449

Ilari Liusvaara <ilariliusvaara@welho.com> Fri, 13 May 2016 13:02 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 93C4512D501 for <tls@ietfa.amsl.com>; Fri, 13 May 2016 06:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.919
X-Spam-Level:
X-Spam-Status: No, score=0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L4=2.299, RP_MATCHES_RCVD=-0.996, SUBJ_ALL_CAPS=1.506] autolearn=no 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 x4zvy--n5GKc for <tls@ietfa.amsl.com>; Fri, 13 May 2016 06:02:35 -0700 (PDT)
Received: from welho-filter3.welho.com (welho-filter3.welho.com [83.102.41.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4510A12D1E7 for <tls@ietf.org>; Fri, 13 May 2016 06:02:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by welho-filter3.welho.com (Postfix) with ESMTP id 383119267; Fri, 13 May 2016 16:02:33 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp3.welho.com ([IPv6:::ffff:83.102.41.86]) by localhost (welho-filter3.welho.com [::ffff:83.102.41.25]) (amavisd-new, port 10024) with ESMTP id 2jRnnIMaInIB; Fri, 13 May 2016 16:02:32 +0300 (EEST)
Received: from LK-Perkele-V2 (87-100-155-121.bb.dnainternet.fi [87.100.155.121]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by welho-smtp3.welho.com (Postfix) with ESMTPSA id B33812310; Fri, 13 May 2016 16:02:32 +0300 (EEST)
Date: Fri, 13 May 2016 16:02:30 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: Eric Rescorla <ekr@rtfm.com>
Message-ID: <20160513130230.GA22096@LK-Perkele-V2.elisa-laajakaista.fi>
References: <CABcZeBM0-tofOi3TnVBOuhkhWjyqwtf-vVwJ7GB8vD4=jYqOcA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <CABcZeBM0-tofOi3TnVBOuhkhWjyqwtf-vVwJ7GB8vD4=jYqOcA@mail.gmail.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Sender: ilariliusvaara@welho.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/Me8uhJDN-lu6VYqw2E1qFhYFD8Q>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] PR#449
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 13 May 2016 13:02:37 -0000

On Wed, May 11, 2016 at 01:36:13PM +0200, Eric Rescorla wrote:
> https://github.com/tlswg/tls13-spec/pull/449
> 
> In Buenos Aires, we agreed to add EncryptedExtensions from the client
> in 0-RTT to carry the ticket age/elapsed_time. I have written this up in
> the PR above. Comments welcome.

How do clock rate errors affect the mechanism? It occurs to me that
if clock isn't NTP-synced, clock rate can be quite a bit off, not
just the time being off.

On my main desktop, I estimate that if the clock wasn't NTP-synced,
it would drift about 140ms per day (and I have seen a LOT worse
clocks).


-Ilari

v2.23.0 | Report a Bug | By Email