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

MikkelFJ <notifications@github.com> Tue, 14 November 2017 16:07 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 3CFAF127876 for <quic-issues@ietfa.amsl.com>; Tue, 14 Nov 2017 08:07:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level:
X-Spam-Status: No, score=-2.019 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, RCVD_IN_MSPIKE_H4=-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 yUMg7QIwLeDd for <quic-issues@ietfa.amsl.com>; Tue, 14 Nov 2017 08:07:25 -0800 (PST)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (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 1A86B1275F4 for <quic-issues@ietf.org>; Tue, 14 Nov 2017 08:07:24 -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=w09YWchuXKsXXQesUrE7CynNdMo=; b=oVmgc/1zt0iLTffi S8B/q5XAtH9JQ/VGBZJp8HaAoGX19iuD1+ZM4Xz7TZqTmoyOQsroWMu1Xie0hhDE RQFC0YS874h/aL/nvsOES4Xv17C4HGqmPL/SzirL8urEODQTKi1QzM3tieshmbDQ Q23vSntNNm0gGD0/5zjNMy+jdVw=
Received: by filter0344p1las1.sendgrid.net with SMTP id filter0344p1las1-28503-5A0B14BB-11 2017-11-14 16:07:23.266851782 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id Wbjb76yRRdWP76HXykA8_w for <quic-issues@ietf.org>; Tue, 14 Nov 2017 16:07:23.103 +0000 (UTC)
Date: Tue, 14 Nov 2017 16:07:23 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5bd683a91650a94ca61df7a0796e53dc613347db92cf000000011622d6ba92a169ce0ed5746a@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/344307767@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_5a0b14bad9827_51cf3f8349a5cf3816687f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2Gt6e1Y2k3AWBbPjympJ6U5X+oGdkdTExB+z 7/HousufEHsyy7/rNyMd8nX/xZI2XOrw1lGfvewy3+poPtvv4jiRYrs5oTuuzVIRiryrPcDazQlMZm 9cs+fQ47y5v9iJaq1JyUvRwC4S07waICKtenw6ptkpyOnG5fiO6HKsPEiGO/3RftwG3UFuBx94AGN/ A=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/j_sOkKTC-K06dHhK4H_waf9PSrU>
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:07:27 -0000

@nibanks Right.

Another concern is AEAD encryption based on the connection ID. If the client ID is encrypted, the client cannot use the ID to map the new server. However, if the server continues to reply with client connection ID and carries the new server ID in the packet, or perhaps in some TLS parameter as suggestion by @ianswett, then the client can easily make the link between the connections and connection ID based client to server routing would still work since the client changes ID. Still not sure about the 0-RTT impact.

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