IETF Logo Mail Archive

Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317)

ianswett <notifications@github.com> Mon, 23 April 2018 13:56 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 94A03126D74 for <quic-issues@ietfa.amsl.com>; Mon, 23 Apr 2018 06:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.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, 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 4ydcB1bgPG3C for <quic-issues@ietfa.amsl.com>; Mon, 23 Apr 2018 06:56:53 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCE21126CD6 for <quic-issues@ietf.org>; Mon, 23 Apr 2018 06:56:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=f/Q2hpleyzHy8DEL70oAYGUM7Co=; b=gVBEM/VndDgpcCOp ue7ctozzt5dQst3+d+QggSh9UqejYboTnq9DziJPWNOYKpFm8LfVJDcCU1suCG65 ytBbAsgj3KsJsJz9mhpACHdbI+hEXc1/2V/hE8a8F+eNAmp79Jxl0jO58moB5lgM hhxy0iWHZMJfZyAveWKM2zxlLMI=
Received: by filter0183p1las1.sendgrid.net with SMTP id filter0183p1las1-26242-5ADDE623-5 2018-04-23 13:56:51.18698414 +0000 UTC
Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [192.30.252.33]) by ismtpd0008p1iad2.sendgrid.net (SG) with ESMTP id _rNPzB0LSyKC9V0T87tzUw for <quic-issues@ietf.org>; Mon, 23 Apr 2018 13:56:51.048 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 09E9DC15D5 for <quic-issues@ietf.org>; Mon, 23 Apr 2018 06:56:51 -0700 (PDT)
Date: Mon, 23 Apr 2018 13:56:51 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf808ca40e206a3a9866400ba39604e9e2f58a03a92cf0000000116f5a82392a169ce12df98aa@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/383584368@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_5adde623747f_10812aeef4650f501264ee"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-CSA-Complaints: whitelist-complaints@eco.de
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1FzzpN/WT1xqzxKkgbFEQP/HVQ2lsYBv3Zwb pTqOD3kIFYtrDdfV0XQdM51iiztKtnAST5UnovOz6QBSMzY1myDBUn1NCNIiKe1Gwfaw+o3JFmWVmP ggYmK/2aggWlknE4moPEPcAIzFJw6+DqqIslf97EfSRhQTcSCd8JSmJNoBpQ1W5NcNdGsMjsLn9hS9 o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/9V1_Vp65gXIvCnJ8L1cjFMHGhm4>
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, 23 Apr 2018 13:56:55 -0000

Re: "On the sender side, we can continue living with just one loss recovery / congestion control device per connection. This is because in QUIC v1 a sender never sends retransmittable frames through under multiple CIDs at the same time."

PATH_CHALLENGE and PATH_RESPONSE frames generate acknowledgements, and are sent on the non-default path, so extra care has to be taken to not cause the acknowledgement of these packets to cause packets on the current default path to be acknowledged.

Once you have per-CID PN spaces, a way to ack them in a single QUIC frame or packet, and separate loss recovery contexts for each, you've pretty much created multipath.  Except for some text, I don't think there's much left?

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

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