Re: [quicwg/base-drafts] Multiple connections on the same port (#714)

Nick Banks <notifications@github.com> Tue, 14 November 2017 16:36 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 E26B2127005 for <quic-issues@ietfa.amsl.com>; Tue, 14 Nov 2017 08:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 UOTUC7719e4e for <quic-issues@ietfa.amsl.com>; Tue, 14 Nov 2017 08:36:44 -0800 (PST)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (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 E7A671271FD for <quic-issues@ietf.org>; Tue, 14 Nov 2017 08:36:43 -0800 (PST)
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=NU3vj+O3VTsoU7ugZpEO6udFrYs=; b=TXiy6PyjtNz0pMdB 2VUzIbFd6A/kbClhpGrWqi3fCV5zV3I/O9Rv3Gjl1LRkPn/HFYsZ5HKCw64UCeSW SipH6H4LqwKPV9bwVBZgmKOjBfxwsV9KGr9yXIFqC2Ojed0ftbdXWKvYo/QZjW7U POI8pZdSAGE6KzFKOV03FmbTru8=
Received: by filter0554p1iad2.sendgrid.net with SMTP id filter0554p1iad2-31965-5A0B1B9A-1C 2017-11-14 16:36:42.46644126 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0017p1iad2.sendgrid.net (SG) with ESMTP id Xq7KR0kKQXmU_cX7AEQO_w for <quic-issues@ietf.org>; Tue, 14 Nov 2017 16:36:42.466 +0000 (UTC)
Date: Tue, 14 Nov 2017 16:36:42 +0000
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0524aaa90a689b623c22456c7bfb6c148cba357a92cf000000011622dd9a92a169ce0ed5746a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/714/344317467@github.com>
In-Reply-To: <quicwg/base-drafts/issues/714@github.com>
References: <quicwg/base-drafts/issues/714@github.com>
Subject: Re: [quicwg/base-drafts] Multiple connections on the same port (#714)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a0b1b9a5fd2d_18453fc7ee05cf3028746e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0PlG7X/entzI4zgFRghkgY8gQqNrYNbKaFB/ J4L2VvhGEyXKvVwHNDTGHTng+HPcnlaE9wvIxb1Ud10Lm03xzK7gCJEqRw5bCIPWM7eeIt+unJslPB bgLs8OR3SzrkW6xBrP/8zPiS3cEA+1bLtyqXMZfhB9C5WDenL/yP+bhrJj1OvSqOE/I5CS+1SWKnxb k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/eZ9L_K4z5zYYM30D6shHuWpg1_s>
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, 14 Nov 2017 16:36:46 -0000

Maybe we are crossing paths and misunderstanding each other. Here is the problem I am trying to solve:

1. A client has N new Connections (in the handshake state) to the same remote IP/Port on the same local IP/Port.
2. The client receives a packet (long header or short header) on that local IP/Port with a Connection ID it doesn't know about.

How can the client determine which Connection to deliver that packet to for processing?

Since the packet is encrypted with the Client Connection ID and not the Server Connection ID, it cannot decrypt the packet until it has determined what the Client Connection ID was. Therefore, it cannot rely on any encrypted information to calculate the Client Connection ID.


-- 
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/714#issuecomment-344317467