Re: [quicwg/base-drafts] TIMEOUT CONNECTION_CLOSE error (#3126)

ianswett <> Mon, 21 October 2019 20:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 534551209A0 for <>; Mon, 21 Oct 2019 13:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.382
X-Spam-Status: No, score=-1.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_NONE=-0.0001, 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 YrvwyYUKcGfl for <>; Mon, 21 Oct 2019 13:07:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6323A1209A6 for <>; Mon, 21 Oct 2019 13:07:56 -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=c2x3ZUycFT/XdtZ8NchH0bCrXA0=; b=N3a0idfJGsEiXlej TmdX17tdaMOsDuJALdEZNMyKDZp5fQztmpXKcGZQU3O+t4RCKb8tbjRocqicobjt Y5qXqOvQpPnMZMfi61rgw5DW20w/wPm9K6xDHf/AhUKMg70VT0qeiIOGYaCwhhmx VPsSQGYBQ3fyMqG9xoE6Tk3jc0U=
Received: by with SMTP id filter0674p1iad2-17616-5DAE101B-1B 2019-10-21 20:07:55.545730014 +0000 UTC m=+419615.238549100
Received: from (unknown []) by (SG) with ESMTP id a-aijJ1oS4Go7XP7JXh2Ag for <>; Mon, 21 Oct 2019 20:07:55.432 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 4B8764C0268 for <>; Mon, 21 Oct 2019 13:07:55 -0700 (PDT)
Date: Mon, 21 Oct 2019 20:07:55 +0000
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3126/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] TIMEOUT CONNECTION_CLOSE error (#3126)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dae101b4a43a_2ae23f95a60cd96c321257"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0NQTFfGfgIc9Vb/O+ctQY9uVndzo4rRZ/+kF rwoU2TAQUAg/lawFJSdITww5GzVmhF5ch/Z5xd2JN1XpgqjVeVf7il0QznyGtkfi7YvfG61n2UHZoJ F47tlWvOguJVhV1o5pUkzYVHgaloIZUimxIaodXQO6UzxnfFErAGlVRIBpJxaHo9oV0qwEeG6NUKdR E=
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: Mon, 21 Oct 2019 20:08:03 -0000

I think the transport doc currently suggests using NO_ERROR.  There are no other suggested uses of NO_ERROR, so this seems like it is functionally equivalent to a TIMEOUT error code?

> After receiving a CONNECTION_CLOSE frame, endpoints enter the draining state. An endpoint that receives a CONNECTION_CLOSE frame MAY send a single packet containing a CONNECTION_CLOSE frame before entering the draining state, using a CONNECTION_CLOSE frame and a NO_ERROR code if appropriate. An endpoint MUST NOT send further packets, which could result in a constant exchange of CONNECTION_CLOSE frames until the closing period on either peer ended.

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