Re: [quicwg/base-drafts] Application close should be disallowed in Initial or Handshake (#3158)

MikkelFJ <> Wed, 30 October 2019 07:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ED4BB120846 for <>; Wed, 30 Oct 2019 00:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Status: No, score=-1.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id FyDQOiIbTjSA for <>; Wed, 30 Oct 2019 00:10:42 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D8671120839 for <>; Wed, 30 Oct 2019 00:10:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; 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=cdxKBpaZXjgrZM8G2j3tGNn1pAo=; b=OE+OssO8MpMoKmXm xAPpg8ZFd+a7OLR6Y2YUmYTezFyqqniJQ2PKafU/8m345kIH30RwW0gPXZRvtEpg 1Nhkl6yynQtg8cHfPggrAvlOZdIRXfvsBtllwPWD6mRarQKAYq+hkolPPlTM+VpV V5djON/n+gz4ncIR8t/usqLQfFk=
Received: by with SMTP id filter1417p1las1-12565-5DB93770-7 2019-10-30 07:10:40.228131188 +0000 UTC m=+393410.056533554
Received: from (unknown []) by (SG) with ESMTP id UGbT4-qgTU2_Zpzyo_JuEQ for <>; Wed, 30 Oct 2019 07:10:40.100 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 08CE2C0DF3 for <>; Wed, 30 Oct 2019 00:10:40 -0700 (PDT)
Date: Wed, 30 Oct 2019 07:10:40 +0000
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3158/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Application close should be disallowed in Initial or Handshake (#3158)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db93770749d_45773f8d660cd96432373e"; 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-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1+O8iK+TH3vuPw7rLipIWQuTurg4aqWj8ZB3 3mC4aXvraQR2Olo/Ojw/mrxsb7UdHJn6PNk7224aoOqyVVINPFibu6jliKwMnnqX6/DUhOwPvpWXy5 dKzy8bXINcL0iIARlBWW6s23/vlPE9rThPYw89duAi5lOM0GNnHE9fRkkg==
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 30 Oct 2019 07:10:43 -0000

Maybe we need to add an API recommendation (not requirement) that says that "an application could be allowed to close a connection during handshake using a transport connection close frame". This is similar to my earlier suggestion that an application could be allowed to reject incoming connections because the server is busy or whatever - this suggestion was not accepted as a requirement because it isn't necessary, but it is still a good thing to support. The question is then, how is the connection taken down - i.e. silently or with a transport close?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: