IETF Logo Mail Archive

Re: [quicwg/base-drafts] Add Advice and Rules for CONN_CLOSE in Initial and Handshake (#1786)

martinduke <notifications@github.com> Fri, 21 September 2018 20:46 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 C1863130E21 for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 13:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.009
X-Spam-Level:
X-Spam-Status: No, score=-3.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 YUNM--4gDzjg for <quic-issues@ietfa.amsl.com>; Fri, 21 Sep 2018 13:46:27 -0700 (PDT)
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 B591212785F for <quic-issues@ietf.org>; Fri, 21 Sep 2018 13:46:26 -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=aXpY/Sfh0omM0ukoMdj0NEBh2s4=; b=LcnKfHZq26P2cFP1 QN1DJgaS5XHsgdwd1a000eTis/Ii9UMrBhwNWZnHWM+By8Pa1N0uYr3+43BNYEeP FtupPmRjxkKKD8WBmInUrqlFe2KKIb8pVninXKLvyKwelyunkywCw3u/5ua7i8nG E8YP2nbxS/Jkw1R4NmJ0Ubjb+Uw=
Received: by filter0156p1iad2.sendgrid.net with SMTP id filter0156p1iad2-3070-5BA558A0-25 2018-09-21 20:46:24.888129796 +0000 UTC m=+1290579.590296265
Received: from github-lowworker-e711880.cp1-iad.github.net (unknown [192.30.252.45]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id nnylht7VRIazNR-uX3j48Q for <quic-issues@ietf.org>; Fri, 21 Sep 2018 20:46:24.757 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-e711880.cp1-iad.github.net (Postfix) with ESMTP id B5918440789 for <quic-issues@ietf.org>; Fri, 21 Sep 2018 13:46:24 -0700 (PDT)
Date: Fri, 21 Sep 2018 20:46:25 +0000
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2044fd5a75d947194313c531b779e8f86193468b92cf0000000117bd1aa092a169ce159f31b4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1786/423665660@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1786@github.com>
References: <quicwg/base-drafts/issues/1786@github.com>
Subject: Re: [quicwg/base-drafts] Add Advice and Rules for CONN_CLOSE in Initial and Handshake (#1786)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba558a0ae3b0_70503f7e536d45b413853d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2gSR2RixdQKDSYGUcT+VK24wjt+boQEeBQkb WYib5bTHYJqUajMtKHGwTPArFG5VZdLrGhBNBFfEyhQzmLxGi8zRoM001fAm68wOsS1l+Y/7FZjkJ3 82Nj3q8fmJFdhQmwLhM5HSJ1rrNOHsubFkGjCi4ThjL2PoXiqsiGTB7WS7n0oTnJq2fdFWDKi8mxQH c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/pMDD9u_4PRic4qQrXZMD3ucP_i4>
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: Fri, 21 Sep 2018 20:46:29 -0000

I don't think that works with #2. Though my rule doesn't work either. If the server needs to send one right after its first flight, it knows only that the peer processes INITIAL. The client will have HS packets from the server, so it will drop with Initial. The server might actually send 1-RTT, and this would work as well under the current rule if nothing is lost.

None of these solutions are obviously best, which is why there should be some guidance. I have to think about it some more, and would appreciate that others do so.

-- 
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/1786#issuecomment-423665660

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