Re: [quicwg/base-drafts] HTTP SETTINGS: define setting content encoding (#1556)

ianswett <> Sun, 26 August 2018 12:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D386D130DE1 for <>; Sun, 26 Aug 2018 05:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Status: No, score=-8.01 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, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id IdPs0eleOZkX for <>; Sun, 26 Aug 2018 05:08:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 375211277CC for <>; Sun, 26 Aug 2018 05:08:48 -0700 (PDT)
Date: Sun, 26 Aug 2018 05:08:46 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1535285326; bh=tfuZOvhijyGQZFXClFxOV8kS+vhnQgUyVJNKdDY2c1g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qBEiLu1t7S35cSLDbJxRSmZfr/GcES9pB5YTnHlZx5PNYuq5ziuOcxkhkaW4jRtp7 fDeHiIvVld6ZLESrDcsFxhmBItXZAmbZeBy3gnczKvx7OF4lTInspXxOPMQMLqz1Ky vrMsTbPcyOacqOsT7yyxxbMrQ7Qqrk3sCzZJb03k=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1556/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP SETTINGS: define setting content encoding (#1556)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b82984e8abf8_287f3fc116cbe61833401f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.27
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 26 Aug 2018 12:08:50 -0000

I agree with Lucas, I'd prefer simple numerical values given that's all we're using in v1.

One could negotiate an extension later to enable other values once/if we have a clear idea of what those are, but I tend to think it'll never be necessary.

Besides complexity, I'm a bit worried implementations will naively parse the settings into a map in memory and then use them.  Given the value is virtually unbounded in length, this could go quite badly.  Admittedly, that would be a poor design, but it's not even possible if every setting value is a number.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: