IETF Logo Mail Archive

Re: [quicwg/base-drafts] Asymmetry in the handling of SETTINGS frame (#1846)

afrind <notifications@github.com> Tue, 09 October 2018 16:04 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 A3FFC131352 for <quic-issues@ietfa.amsl.com>; Tue, 9 Oct 2018 09:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, URIBL_BLOCKED=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 An-l3ooOaKrg for <quic-issues@ietfa.amsl.com>; Tue, 9 Oct 2018 09:04:12 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2808131342 for <quic-issues@ietf.org>; Tue, 9 Oct 2018 09:04:11 -0700 (PDT)
Date: Tue, 09 Oct 2018 09:04:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1539101050; bh=Sem13GNl5akidXTNybmO/F/VdVz7w8GH8AbGKzCFEiw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=r5iFGYob7cvCrAjoaKNFBgZe1Vttdyad8S4pb3Ft8Ry3dsZ5+H9tvkYb5n8rmPHGw unAWoexl6zStECuTPIK164Q0i0Y1bs7hVwO3OcUtAXplmp9OMjMOFMkJ7CCFCxuDBz s+QnNLJD2JJDpy5TDmhN328smAUVK7r0/qxnQeag=
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf41468065bee0efc242b30eb49248d621ba1fd1592cf0000000117d4937a92a169ce15f10683@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1846/428251470@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1846@github.com>
References: <quicwg/base-drafts/issues/1846@github.com>
Subject: Re: [quicwg/base-drafts] Asymmetry in the handling of SETTINGS frame (#1846)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bbcd17ade476_5dc53fa2406d45bc178821"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
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/fVRw_bwMp9Rcn6OSw8yRdJxuW84>
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: Tue, 09 Oct 2018 16:04:14 -0000

I'm generally ok with this concept.

SETTINGS_MAX_HEADER_LIST_SIZE is also in the settings, with a default value of unlimited (side note, this meaning of this setting is not described anywhere in the HQ spec).  If we allow sending header blocks before receiving SETTINGS, is the peer required to accept arbitrarily long header lists?  Or we should reintroduce a lower default?

-- 
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/1846#issuecomment-428251470

v2.23.0 | Report a Bug | By Email