Re: [quicwg/base-drafts] Explicitly define H3_REQUEST_FOO as stream error (#4766)
Kazu Yamamoto <notifications@github.com> Wed, 20 January 2021 06:13 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 9B6353A03EE for <quic-issues@ietfa.amsl.com>; Tue, 19 Jan 2021 22:13:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.258
X-Spam-Level:
X-Spam-Status: No, score=-2.258 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 NXVhxIwwdJ-W for <quic-issues@ietfa.amsl.com>; Tue, 19 Jan 2021 22:13:11 -0800 (PST)
Received: from smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AA723A03EC for <quic-issues@ietf.org>; Tue, 19 Jan 2021 22:13:10 -0800 (PST)
Received: from github.com (hubbernetes-node-94c13b3.va3-iad.github.net [10.48.112.30]) by smtp.github.com (Postfix) with ESMTPA id 2FBD83405B8 for <quic-issues@ietf.org>; Tue, 19 Jan 2021 22:13:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611123190; bh=ogvfHjrgvzzQdWAAQ2JWoHfG70Um4Z7GLyuNZASlz0s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=B+J6MXChBcmz07H6xTlJMdrAP9Ufa/8tSXLjCYEKHe3Vw0ZLNeoV/trKmnOCa11fG MkD9krxSccTFWPRb0MOUTC4EVjKTlaoofU8pGhzNj19ABG3OwcuL2UbG3qCqSegKip UBbZ39PffKboR/orQ45pAU5U/tK0BowXem417JDc=
Date: Tue, 19 Jan 2021 22:13:10 -0800
From: Kazu Yamamoto <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3O5JTDJDA6IDY4DYF6COVPNEVBNHHC6DXCQA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4766/763362822@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4766@github.com>
References: <quicwg/base-drafts/issues/4766@github.com>
Subject: Re: [quicwg/base-drafts] Explicitly define H3_REQUEST_FOO as stream error (#4766)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_6007c9f62c249_5f1a0429524"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazu-yamamoto
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/1p45TbuCSclTKau58VR1cUjF-10>
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, 20 Jan 2021 06:13:13 -0000
My example proposal is to replace "the server SHOULD abort its response with the error code H3_REQUEST_INCOMPLETE" with "the server SHOULD abort its response and treat as a stream error of type H3_REQUEST_INCOMPLETE" in Sec 4.1. I don't understand why this would introduce inconsistency. -- 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/4766#issuecomment-763362822
- [quicwg/base-drafts] Explicitly define H3_REQUEST… Kazu Yamamoto
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Lucas Pardue
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Lucas Pardue
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Kazu Yamamoto
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Lucas Pardue
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Kazu Yamamoto
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Kazuho Oku
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Lucas Pardue
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Mike Bishop
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Kazu Yamamoto
- Re: [quicwg/base-drafts] Explicitly define H3_REQ… Mike Bishop