Re: [quicwg/base-drafts] Initials carrying different first ClientHello are considered as belonging to different connections (#2076)

Christian Huitema <notifications@github.com> Thu, 06 December 2018 03:29 UTC

Return-Path: <noreply@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 5437D130FA6 for <quic-issues@ietfa.amsl.com>; Wed, 5 Dec 2018 19:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 0a5EU1hfip3o for <quic-issues@ietfa.amsl.com>; Wed, 5 Dec 2018 19:29:10 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66404130EB4 for <quic-issues@ietf.org>; Wed, 5 Dec 2018 19:29:10 -0800 (PST)
Date: Wed, 05 Dec 2018 19:29:07 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544066947; bh=0J+1vPTLCNAEDxJxO131ca/Ks62OFK4EucaExBJ0Zz8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=i1f9uy+HR7WHchDYbsAjfSQLrVsvBjfNONT1qqHIlNavMkB0biB0mJl8nTwabhanB LtQgRYurFoJm/fzcEKLSFGHNuC6Ljb5/fwciqQ8Rkpa6i0GW4TmbiZ9vjGh25z8qIz 6DtctqG+WfSfRCVSUyeN7Q8eMimUZHpQPLyAw++0=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfda9b7eb1b5c0a8be69ead0b099eb9be51cae4e792cf000000011820598392a169ce1701edfc@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2076/c444736092@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2076@github.com>
References: <quicwg/base-drafts/pull/2076@github.com>
Subject: Re: [quicwg/base-drafts] Initials carrying different first ClientHello are considered as belonging to different connections (#2076)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c08978354a36_5ac63feecaad45b42842b5"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/A3TAvHmcVF-ekO1v_4ni1IyTIV8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Dec 2018 03:29:12 -0000

In the mailing discussion, I mentioned that "_I understand how to create a separate connection context on the server for each different incoming server hello... but I am concerned that this solution breaks if the client needs to send multiple different Initial messages, such as a new Client Hello in response to an HRR, or an ACK._" @kazuho replied that HRR would be very rare in practice and thus not a worry, and that "_Regarding ACKs, you need to potentially ignore or postpone applying them. The same goes for CONNECTION_CLOSE._" But this PR does not say any of that. If we want it considered, then it needs to explain how the processing of ACK and CONNECTION_CLOSE frames is modified for Initial packets. It also need to explain how HRR are handled. That cannot be just a handwave.

-- 
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/pull/2076#issuecomment-444736092