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

Rui Paulo <notifications@github.com> Mon, 21 October 2019 19:51 UTC

Return-Path: <noreply@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 001D51208FB for <quic-issues@ietfa.amsl.com>; Mon, 21 Oct 2019 12:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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_20=1.546, 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: 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 Ejpi-6OKDJDq for <quic-issues@ietfa.amsl.com>; Mon, 21 Oct 2019 12:51:29 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BBAA1208F8 for <quic-issues@ietf.org>; Mon, 21 Oct 2019 12:51:29 -0700 (PDT)
Date: Mon, 21 Oct 2019 12:51:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571687488; bh=kDihmSW1AlCPkb3NOoy1SzfzUOAHyHOOUqnkLZRHGqE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=nmARRN36bneGcwJCBRqb6KB7vLKb7/a8C2EuVU/mmfA1yQRBn319TogcGhVOZYx7E pzUc9EQXcWG+KZoWBxRp3/ugTAvaod67NGVEcyeF5lm2zIc78UpCGXSBm6LDBln3g4 heGLfZIqozkBSvAJTW3ziCzOF9j/AlbDqAmulQL4=
From: Rui Paulo <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5URYNRLUSQ3RXBC7V3XNGNBEVBNHHB42N4IA@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@github.com>
Subject: [quicwg/base-drafts] TIMEOUT CONNECTION_CLOSE error (#3126)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dae0c406e2c5_5be53fac39acd9681439a6"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: rpaulo
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/CSHUe9cFixXHc2AW4uECSvqmZ10>
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 19:51:31 -0000

Perhaps we should have a TIMEOUT error code?  Connection timeouts are extremely common.  It would help implementations detect timeout conditions without having to parse the connection_close error string.  One could argue that a timeout isn't an error, but we already have SERVER_BUSY.

-- 
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