Re: [quicwg/base-drafts] Handling of connection ID in handshake creates corner cases (#843)
Christian Huitema <notifications@github.com> Mon, 09 October 2017 18:03 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 E45ED134755 for <quic-issues@ietfa.amsl.com>; Mon, 9 Oct 2017 11:03:20 -0700 (PDT)
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_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 sERd4o1aB4MK for <quic-issues@ietfa.amsl.com>; Mon, 9 Oct 2017 11:03:19 -0700 (PDT)
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 70F3D133071 for <quic-issues@ietf.org>; Mon, 9 Oct 2017 11:03:19 -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=kF+pQpK7isEUkKXM5/aR+Hde3Ds=; b=b/F3YwFwYBmfOYOB 3fM02XqJ+YHwCzMSjtjNf//kGNKFhlax1AC4NMT/l9xC9w+oL9WwF0XQoJV64tkc 90z1nLfEWlpHqNgR4H+RCQiB86m5yslv0Y3WWgyIUBnglEh0HZrQU1/UG3sP9q1y 98aK0XTycAc2Ao3qO/bN2EtgLz8=
Received: by filter0176p1iad2.sendgrid.net with SMTP id filter0176p1iad2-24973-59DBB9E6-15 2017-10-09 18:03:18.261631101 +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 ismtpd0004p1iad2.sendgrid.net (SG) with ESMTP id J-q47MGBQ4qssqm66neKiQ for <quic-issues@ietf.org>; Mon, 09 Oct 2017 18:03:18.324 +0000 (UTC)
Date: Mon, 09 Oct 2017 18:03:18 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4fd20f25c54834fbbd891ab64f4d4e6491ebd78392cf0000000115f37be692a169ce0fbbdfd8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/843/335238314@github.com>
In-Reply-To: <quicwg/base-drafts/issues/843@github.com>
References: <quicwg/base-drafts/issues/843@github.com>
Subject: Re: [quicwg/base-drafts] Handling of connection ID in handshake creates corner cases (#843)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59dbb9e62f410_ae63fc3dccf2f3030334"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak22seJVRa0Pc48CN8bju4TajKnuo7E9gNoKV7 1zxKD9Xu0Vcon7Cz6UR9ndvx2//KXLTTr1p+rpdj3z0i3IGNlShQ4zgpzCE0x6flcBQi+2hmb23ROP kBpoH52fcVivbvb/UAgcI2yRQx2DcQqN/VEzKAT5SqXKCpqb7JTRz4/uRWjWToSY1NKXBwg+gR9Uyr M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/jLxuFDUD1yGieRQZatok87IVUC4>
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, 09 Oct 2017 18:03:21 -0000
@RyanAtGoogle no, encrypting with the connection ID will not be sufficient. According to the spec, the Client Initial carries the client-chosen initial connection ID, but the Server Clear text carries the server chosen connection ID, which the client is supposed to adopt and then use for all consecutive packets. So the client will read the connection ID from the message header, and use it to decrypt the message. It will work, whether using connection ID #1 or #2. -- 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/843#issuecomment-335238314
- [quicwg/base-drafts] Handling of connection ID in… Christian Huitema
- Re: [quicwg/base-drafts] Handling of connection I… Ryan Hamilton
- Re: [quicwg/base-drafts] Handling of connection I… Christian Huitema
- Re: [quicwg/base-drafts] Handling of connection I… Christian Huitema
- Re: [quicwg/base-drafts] Handling of connection I… Ryan Hamilton
- Re: [quicwg/base-drafts] Handling of connection I… Christian Huitema
- Re: [quicwg/base-drafts] Handling of connection I… ekr
- Re: [quicwg/base-drafts] Handling of connection I… Ryan Hamilton
- Re: [quicwg/base-drafts] Handling of connection I… Christian Huitema
- Re: [quicwg/base-drafts] Handling of connection I… Christian Huitema