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

MikkelFJ <> Tue, 29 October 2019 05:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 84396120043 for <>; Mon, 28 Oct 2019 22:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BujQ1dMiGxte for <>; Mon, 28 Oct 2019 22:00:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 10F41120044 for <>; Mon, 28 Oct 2019 22:00:56 -0700 (PDT)
Date: Mon, 28 Oct 2019 22:00:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1572325255; bh=tgeLgqG4a/Yito4UpTv3Kg9ChkW+6sNBP2OMCsZJ8Cw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fiuqDX9D5QIQsgNMb7ipOw9Tz+yCJ6HX4voGKzxIo7ml0vzP/HPslmAuWFYbwdvyv x1GSPXb9OvUsA9wunQxuwaOlLfxTJvDT0YHy6LRJYOvs7YkaBnFbuBaFZuXOCzw9fX 0uIXNgCZ6koUfNGGa555B3DQOXv/+gBiATZ7vPQM=
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_5db7c78737c4e_2b793fea9e6cd9641286f1"; 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
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: Tue, 29 Oct 2019 05:00:58 -0000

I agree with @nibanks there is an age old discussion on handling errors in early connection. Simply forbidding them without understanding this would be unfortunate.

Consider errors in early handshake where the server does not wish to proceed. It doesn't like the client, it doesn't have the resources, it is about to reboot, or whatever. It can either drop the packets or wait if it cannot close immediately. It doesn't want to wait so it drops. Drops then probably results in unnecessary resets.

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