Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317)
Martin Thomson <notifications@github.com> Mon, 30 April 2018 23:56 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 ADFBF12D7EC for <quic-issues@ietfa.amsl.com>; Mon, 30 Apr 2018 16:56:34 -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_IMAGE_ONLY_32=0.001, 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 E5L0f9BSI7k8 for <quic-issues@ietfa.amsl.com>; Mon, 30 Apr 2018 16:56:32 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCA5D127333 for <quic-issues@ietf.org>; Mon, 30 Apr 2018 16:56:32 -0700 (PDT)
Date: Mon, 30 Apr 2018 16:56:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1525132591; bh=WLKDXRBaQ4O5o/ApbUZPsYmdJSDnOAUPRfj1xnMTZ+o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0bT7VpAtfnmNAesl+50ymALbfctUbXYT1Qf9p7TYJt52/YeIuRH2eGzyvNBHHGD0I 2An+qrVddBuSdidwM+I4wzkG+7hvRFbqNeCyVacFu0uTfEg3eFeKG6VV4mbL00eu9P vG28mu+Xp5Z1bL+8fCbTA7N7BKvk8Cz+StO4Eq4I=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfc7cb0dba09e219aecc0d50ce3209b9e98e413e492cf0000000116ff6f2f92a169ce12df98aa@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1317/385562880@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1317@github.com>
References: <quicwg/base-drafts/issues/1317@github.com>
Subject: Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ae7ad2fc85be_55392aba11c36f54505bd"; 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/caMvwdJBAqD-GgxePyvQO4aHaz8>
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: Mon, 30 Apr 2018 23:56:35 -0000
I've been casually considering whether to couple changing connection ID to key update. That would mean that we can't remove the sequence number from NEW_CONNECTION_ID, but it would remove the KEY_PHASE bit and accomplish the same ends as this proposes, without having to grapple with separate packet number spaces. The only problem this introduces is that with multipath you get much less coherent sequences of packet numbers as each path has different latency and loss characteristics, which might lead to ACK frames encoding less efficiently. -- 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/1317#issuecomment-385562880
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- [quicwg/base-drafts] per-CID PN space? (#1317) Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space? (#1317) MikkelFJ
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space to avoi… ianswett
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Antoine Delignat-Lavaud
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Antoine Delignat-Lavaud
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space to avoi… janaiyengar
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Christian Huitema
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Martin Thomson
- Re: [quicwg/base-drafts] per-CID PN space to avoi… ianswett
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Martin Thomson
- Re: [quicwg/base-drafts] per-CID PN space to avoi… MikkelFJ
- Re: [quicwg/base-drafts] per-CID PN space to avoi… Kazuho Oku
- Re: [quicwg/base-drafts] per-CID PN space to avoi… janaiyengar