IETF Logo Mail Archive

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

MikkelFJ <notifications@github.com> Tue, 14 November 2017 16:29 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 9E4A6128CD5 for <quic-issues@ietfa.amsl.com>; Tue, 14 Nov 2017 08:29:07 -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_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 23pRavwd3YRz for <quic-issues@ietfa.amsl.com>; Tue, 14 Nov 2017 08:29:06 -0800 (PST)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (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 053FC128BC8 for <quic-issues@ietf.org>; Tue, 14 Nov 2017 08:29:05 -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=iSOzIEJy4B2q8nAhrYa7lHnUM48=; b=Jjbb7w6f7p7qoRR9 hZ+NPy2VH1lRbHtQt1dDQrbe4JZS1aTY2anvsdepzBX+2R7zUA/CgFRHc7rd5yD6 7TMWVyXcQrhhjPKpkmRLW3GfH9JZOZBzp4n5kkfvuK8/mMiEXl7ytmty80B0h76z igrC/aNd8iXZXinvT1FnTwgbr90=
Received: by filter0227p1las1.sendgrid.net with SMTP id filter0227p1las1-10515-5A0B19CF-1F 2017-11-14 16:29:03.633639693 +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 ismtpd0007p1iad1.sendgrid.net (SG) with ESMTP id lkA-5B7YQo2p_hO7phVfAQ for <quic-issues@ietf.org>; Tue, 14 Nov 2017 16:29:03.469 +0000 (UTC)
Date: Tue, 14 Nov 2017 16:29:03 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab13dde96601c1ae2ff0d7a3ca2dd75490626a224892cf000000011622dbcf92a169ce0ed5746a@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/344314905@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_5a0b19cf57f64_e953fef48192f2c34912"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1UuRehvLSEw8ihxzi71deHf4tdjW9ms2iRnh Zb0iCJH+Txd+kI1lWy8wUGmdaEsDpr//dFlVIweUmWh6CghwceAqNn43DuAf+EbfrAHLIWGMEGV1Vu jEjRdqbS4g9z5hhuQ4lwLIpJ19wS2mlrh2lbjAF39JstVBU4MwH37IU5H9eCUup1Ko38Z/Cm1TtJLb Y=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/BYgbt6mF6vXupYHOfdjDP2032sQ>
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:29:08 -0000

@nibanks clear text packets are encrypted and tagged with the connection ID (cleat text AEAD). Thus you need the connection ID to decrypt and verify. But it was a brain fart because regardless of which connection ID is being used to derive a key for cleartext AEAD, the connection ID is avaiable in the packet as clear text at a fixed location.

With TLS, it could work if the server uses the client connection ID in responses and stores the new connection ID in TLS, whereas the opposite would not work. Or did I miss something?

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

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