IETF Logo Mail Archive

Re: [quicwg/base-drafts] Preventing KEY_PHASE bit from being used as a tool to correlate CIDs (#1322)

Martin Thomson <notifications@github.com> Fri, 04 May 2018 03:00 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 967AB12AAB6 for <quic-issues@ietfa.amsl.com>; Thu, 3 May 2018 20:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level:
X-Spam-Status: No, score=-6.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 vL_CCvSDardq for <quic-issues@ietfa.amsl.com>; Thu, 3 May 2018 20:00:47 -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 0D37A129C6E for <quic-issues@ietf.org>; Thu, 3 May 2018 20:00:47 -0700 (PDT)
Date: Thu, 03 May 2018 20:00:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1525402846; bh=0iTiLujWvvNUeCY4sZVKxiGccI37doXsZIA2SiOZRuE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=pCQrJy7LtEP6m2WEb04SrLtffOVP51fKsA4u8mZ3lRXeZPJa8Mm/xp7TursTQ57ut nyxv+HJC7hGA7e0qK0x6zFldkr1+xVblS/Ia4RiWjjNZe7C4R823Q7xmJQU7ZtBbPO ioeiwofXnsg0h9AoI57Fk3TEAO06D2FcSjnPl328=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb9e3e2d0e25189111bc1638bb200ca8fd7ed1c8692cf0000000117038ede92a169ce12e69628@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/386494973@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_5aebccde7114d_32fe2aebd5d82f5c22581f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/l3ClzfTwFsVu1De0Uteea4ix9gw>
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: Fri, 04 May 2018 03:00:50 -0000

Yes, I have considered that option.  I still prefer coupling connection ID change to key migration.  It has the benefit of consolidating mechanisms for migration and key update, which means that the mechanism is more likely to see use.

-- 
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-386494973

v2.29.0 | Report a Bug | By Email | System Status