Re: [quicwg/base-drafts] Preventing KEY_PHASE bit from being used as a tool to correlate CIDs (#1322)
Kazuho Oku <notifications@github.com> Tue, 01 May 2018 08:12 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3541126BF7 for <quic-issues@ietfa.amsl.com>; Tue, 1 May 2018 01:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 Dfcf_rdrvM-5 for <quic-issues@ietfa.amsl.com>; Tue, 1 May 2018 01:12:37 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AF33126BF0 for <quic-issues@ietf.org>; Tue, 1 May 2018 01:12:37 -0700 (PDT)
Date: Tue, 01 May 2018 01:12:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1525162356; bh=i8knmkMaHaCQy4o9Z2e3ZjNvDzd99AnyUVUVzvI4je0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YTd8Hxhkz1NF2OpGn9wxlDgFenMBJNx4Ftw/1qFEdg7QqcMfwuk6z7oXHYOlBs25S Rxb7hGqi1BGfVHNA7yu6ZabbBFs9DfbXjXdw2Wq74ZOLywsPnmrhC6HLwgjzUNVmB7 FPA5e/Wjv6GyprxHWomX/vmFaG52Fzmkx5TUE2P8=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab1e37cb4c982453d44668083f9b8a05730f33fb8892cf0000000116ffe37492a169ce12e69628@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1322/385622096@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1322@github.com>
References: <quicwg/base-drafts/issues/1322@github.com>
Subject: Re: [quicwg/base-drafts] Preventing KEY_PHASE bit from being used as a tool to correlate CIDs (#1322)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ae821742aad5_45063ff4fab6af8812734b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/zXnIKxhGmX3nf9hPeOP1YezQsq4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 08:12:39 -0000
@martinthomson > One thing I've been concerned about with key update is that no one will implement it. NSS only very recently grew that capability in TLS 1.3; it's a small feature, but one that took ages to implement because there wasn't much incentive to build it. We still don't have the DTLS variant because it messes with our timers in ways that are hard to reason about. > > I agree that simultaneous migration would be a mistake. Better to drive rollovers based on packet counts as @kazuho suggests. Though I think that we can probably ignore the 2<sup>62</sup> limit and throw connections away if they ever get to that point. FWIW, picotls doesn't yet have key updates (and I wonder if I would ever implement it). Considering that, I am perfectly fine with dropping key update entirely from QUIC v1, leaving it as an issue to be solved by an extension or v2 issue. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/1322#issuecomment-385622096
- [quicwg/base-drafts] Preventing KEY_PHASE bit fro… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Christian Huitema
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… MikkelFJ
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… MikkelFJ
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… MikkelFJ
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Christian Huitema
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… MikkelFJ
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Marten Seemann
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… janaiyengar
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Marten Seemann
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Marten Seemann
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… MikkelFJ
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… MikkelFJ
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… MikkelFJ
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Kazuho Oku
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Brian Trammell
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson
- Re: [quicwg/base-drafts] Preventing KEY_PHASE bit… Martin Thomson