IETF Logo Mail Archive

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

ianswett <notifications@github.com> Mon, 21 October 2019 20:07 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 534551209A0 for <quic-issues@ietfa.amsl.com>; Mon, 21 Oct 2019 13:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.382
X-Spam-Level:
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: 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 YrvwyYUKcGfl for <quic-issues@ietfa.amsl.com>; Mon, 21 Oct 2019 13:07:56 -0700 (PDT)
Received: from xtrwsrhn.outbound-mail.sendgrid.net (xtrwsrhn.outbound-mail.sendgrid.net [167.89.101.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6323A1209A6 for <quic-issues@ietf.org>; Mon, 21 Oct 2019 13:07:56 -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=c2x3ZUycFT/XdtZ8NchH0bCrXA0=; b=N3a0idfJGsEiXlej TmdX17tdaMOsDuJALdEZNMyKDZp5fQztmpXKcGZQU3O+t4RCKb8tbjRocqicobjt Y5qXqOvQpPnMZMfi61rgw5DW20w/wPm9K6xDHf/AhUKMg70VT0qeiIOGYaCwhhmx VPsSQGYBQ3fyMqG9xoE6Tk3jc0U=
Received: by filter0674p1iad2.sendgrid.net with SMTP id filter0674p1iad2-17616-5DAE101B-1B 2019-10-21 20:07:55.545730014 +0000 UTC m=+419615.238549100
Received: from github-lowworker-c7d2ff2.cp1-iad.github.net (unknown [140.82.115.67]) by ismtpd0070p1iad1.sendgrid.net (SG) with ESMTP id a-aijJ1oS4Go7XP7JXh2Ag for <quic-issues@ietf.org>; Mon, 21 Oct 2019 20:07:55.432 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-c7d2ff2.cp1-iad.github.net (Postfix) with ESMTP id 4B8764C0268 for <quic-issues@ietf.org>; Mon, 21 Oct 2019 13:07:55 -0700 (PDT)
Date: Mon, 21 Oct 2019 20:07:55 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3KH77Y6QLWGR7NE7V3XNIKXEVBNHHB42N4IA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3126/544685436@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3126@github.com>
References: <quicwg/base-drafts/issues/3126@github.com>
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-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0NQTFfGfgIc9Vb/O+ctQY9uVndzo4rRZ/+kF rwoU2TAQUAg/lawFJSdITww5GzVmhF5ch/Z5xd2JN1XpgqjVeVf7il0QznyGtkfi7YvfG61n2UHZoJ F47tlWvOguJVhV1o5pUkzYVHgaloIZUimxIaodXQO6UzxnfFErAGlVRIBpJxaHo9oV0qwEeG6NUKdR E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/oMz7Y9GO0h5N0nAXtODRDYRXGIk>
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: 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:
https://github.com/quicwg/base-drafts/issues/3126#issuecomment-544685436

v2.23.0 | Report a Bug | By Email