[quicwg/base-drafts] H3 guidance on CONNECTION_CLOSE does make clear if the type is 0x1c or 0x1d (#3428)

Lucas Pardue <notifications@github.com> Wed, 05 February 2020 23:41 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 A489A1200A4 for <quic-issues@ietfa.amsl.com>; Wed, 5 Feb 2020 15:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
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: 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 yxBdH7a_GDGO for <quic-issues@ietfa.amsl.com>; Wed, 5 Feb 2020 15:41:09 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF9A12001E for <quic-issues@ietf.org>; Wed, 5 Feb 2020 15:41:09 -0800 (PST)
Received: from github-lowworker-c53a806.ac4-iad.github.net (github-lowworker-c53a806.ac4-iad.github.net [10.52.23.45]) by smtp.github.com (Postfix) with ESMTP id 95E836606B7 for <quic-issues@ietf.org>; Wed, 5 Feb 2020 15:41:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1580946068; bh=hU1Xri0dA+6PIHrTUo4VFz5pBaCJRPPUjZVWe1udfDE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=e04iNoZTFnHu9Fam9+Ikip93Zf9gqlwM1TH2I/xQdUxvOKmrGQVmS9QDnilMbEFvB jCY6VUuoAsIgGEUnXOnYlYjSXIwVn7/OfPm8AwswSLRZ0Z7SfJgUaZTv/1IB7myq3v RGtzeUdcdVOu84u34Yov36rUAaX6A+3KDIrDNahg=
Date: Wed, 05 Feb 2020 15:41:08 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6CD4YMFOEIVE3O6LV4JCCRJEVBNHHCC24CWU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3428@github.com>
Subject: [quicwg/base-drafts] H3 guidance on CONNECTION_CLOSE does make clear if the type is 0x1c or 0x1d (#3428)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e3b5294862b6_1b7c3f8ea2ecd964246783"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/-Wp0nDwufegGBJQQhPdkAkuaR3I>
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: Wed, 05 Feb 2020 23:41:11 -0000

Draft 25 section 5.3 says:

> An HTTP/3 implementation can immediately close the QUIC connection at
   any time.  This results in sending a QUIC CONNECTION_CLOSE frame to
   the peer; the error code in this frame indicates to the peer why the
   connection is being closed.

This doesn't specifically tie down H3-initiated closure to only use the application variant of CONNECTION_CLOSE (0x1d). This gets a bit strange when combined with later guidance to use H3 error codes or treat unknown error codes as `H3_NO_ERROR`

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