IETF Logo Mail Archive

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

Lucas Pardue <notifications@github.com> Wed, 13 March 2019 21: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 33C6B120106 for <quic-issues@ietfa.amsl.com>; Wed, 13 Mar 2019 14:22:32 -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_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 tPNwuB33rFvI for <quic-issues@ietfa.amsl.com>; Wed, 13 Mar 2019 14:22:30 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 981F712008A for <quic-issues@ietf.org>; Wed, 13 Mar 2019 14:22:30 -0700 (PDT)
Date: Wed, 13 Mar 2019 14:22:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1552512149; bh=WLstLLNUcyAtRZJhfvG1430iqSt1fOGT4fxKAHT/Tc8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=JdMKHLhFieRltJf7LC7oarVnXiwbp4KL8hIB904+3Gmz+pjqeCARg8BPQTHMt8RHf 8LiwwCh3TJNNJxGyassZPZTCWoYoQQUwnPxMQeu/FGeNSDyaXrD0xQUeXHkXvCg8Ql fi/L8y1MwW/jzUlsIb3LhYXPcuJOSzMelVT5JGU8=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe970faec4abc61698eb249be6760b7ceb5e5f08592cf0000000118a1369592a169ce190431b1@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/472610912@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_5c897495663e3_eec3f9b4fcd45b8100599"; 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/SJNeLgbYKhnpEwrLEdWXbalnW4c>
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, 13 Mar 2019 21:22:32 -0000

An optional limit that's rarely enforced and, perhaps worse, unpredictably enforced seems like a waste of a limit. 

Implementations already have limits on the size of individual headers, which trigger semantic layer errors. Why does the sum total need to trigger a syntax type of error?

Enforcing error makes this stricter than H2, hurting interoperability between implementations that support H3 and H2 at the same time. 

Speculating, I can see this causing some strange issues in the wild, where clients Alt-Svc up to H3, encounter a sporadic error and then purge H3 endpoints from their Alt-Svc cache. 

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

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