IETF Logo Mail Archive

Re: [quicwg/base-drafts] Semantics of SETTINGS_MAX_HEADER_LIST_SIZE (#2516)

Kazuho Oku <notifications@github.com> Mon, 11 March 2019 22:07 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 5ABCD128664 for <quic-issues@ietfa.amsl.com>; Mon, 11 Mar 2019 15:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 Av6_omds6W4P for <quic-issues@ietfa.amsl.com>; Mon, 11 Mar 2019 15:07:01 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 985D61310C6 for <quic-issues@ietf.org>; Mon, 11 Mar 2019 15:07:01 -0700 (PDT)
Date: Mon, 11 Mar 2019 15:07:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1552342020; bh=PL/FskRdpQ72yfWXhlyGWSzLvpuApnJd97t/Q8fPRBA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Vo22vNYnLXYkWpeDZqKipVOzWvZ41qvSc75N1LvioMFzBtuO+xV9XwgZVzJe53Lxa T8VdeqSgb50Swmpt0Kjw7MZdJkDruwwCwPQem49m2s9dFXuKdOueRsmfavA9daD7lq kii0dEzwP6wUOa0cLlFWT6ovmPYKuGwAp5x/b6Lw=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8a700c37b15019f251a803642fc21cbcd4616b1a92cf00000001189e9e0492a169ce190431b1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2516/471756391@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2516@github.com>
References: <quicwg/base-drafts/issues/2516@github.com>
Subject: Re: [quicwg/base-drafts] Semantics of SETTINGS_MAX_HEADER_LIST_SIZE (#2516)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c86dc046c51b_76043fea3f8d45b422919"; 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/_CAfWbClUH8lI_-jiSpTrPy2oLI>
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, 11 Mar 2019 22:07:03 -0000

My preference goes to being strict. Quoting from 
https://github.com/quicwg/base-drafts/pull/2510#issuecomment-47171000:
> Think it from an end-user perspective. Without the restriction, we might see one user-agent telling you that the request is too large, and the other processing the same request. That'd be confusing.

I also think that what @dtikhonov points out in 
https://github.com/quicwg/base-drafts/pull/2510#issuecomment-471716253 is an argument for making this an enforcement (or drop the settings entirely). Unless we do so, implementations would be tempted to ignore the setting for "maximum interoperability," making the feature meaningless.

-- 
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/2516#issuecomment-471756391

v2.31.3 | Report a Bug | By Email | System Status