Re: [quicwg/base-drafts] Rationalise HTTP_WRONG_SETTING_DIRECTION error (#2810)

Kazuho Oku <notifications@github.com> Wed, 19 June 2019 12:22 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 2977112014F for <quic-issues@ietfa.amsl.com>; Wed, 19 Jun 2019 05:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Level:
X-Spam-Status: No, score=-6.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 xEABHvBgdADu for <quic-issues@ietfa.amsl.com>; Wed, 19 Jun 2019 05:22:28 -0700 (PDT)
Received: from out-21.smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE472120483 for <quic-issues@ietf.org>; Wed, 19 Jun 2019 05:22:28 -0700 (PDT)
Date: Wed, 19 Jun 2019 05:22:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560946947; bh=VXQ/uaN7JYm2z2ogLoL0GUj4dXSMwNC98UI+s7StRVE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JDMYbrfPcERPiIHWGk7ADONIqauhbPWtzKSL6iTD39WYNEWB5gisPTRQS/RhlhNV9 B2+sZLIIh+5VSutSO+HIGHw5jNfpPY91LijVF5dPWvVhThtrJnTRZnxmh1d24+DSIu e+kQGNaIyRuzbVdqvQMieHRLG9PqQeJy7PzyQ/OM=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK562GDJMM2TGIZZ3KF3C5NYHEVBNHHBWS4NUU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2810/503537665@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2810@github.com>
References: <quicwg/base-drafts/issues/2810@github.com>
Subject: Re: [quicwg/base-drafts] Rationalise HTTP_WRONG_SETTING_DIRECTION error (#2810)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0a2903a834c_4dae3fe6e16cd95c4588df"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/8PzCv4GIje8MfT1mA5rwhKhLQMA>
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, 19 Jun 2019 12:22:30 -0000

Thank you for opening the issues.

While I agree that we do not need an error code specific to SETTINGS going in the wrong direction, I am not sure if declassifying it as an error is the right option. Not that I have a strong opinion, but IIRC our consensus is to be more strict against misbehaving peers in HTTP/3 compared to HTTP/2.

-- 
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/2810#issuecomment-503537665