IETF Logo Mail Archive

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

ianswett <notifications@github.com> Sun, 26 August 2018 12:08 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 D386D130DE1 for <quic-issues@ietfa.amsl.com>; Sun, 26 Aug 2018 05:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
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: 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 IdPs0eleOZkX for <quic-issues@ietfa.amsl.com>; Sun, 26 Aug 2018 05:08:48 -0700 (PDT)
Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 375211277CC for <quic-issues@ietf.org>; 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; d=github.com; 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 <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf3a32fab862195a456ef5a23ba5179a8147894b892cf00000001179a5a4e92a169ce14546a14@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1556/416034401@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1556@github.com>
References: <quicwg/base-drafts/issues/1556@github.com>
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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/tjpXxxRmJOBEa8JDPfTn_Ik4dE8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: 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:
https://github.com/quicwg/base-drafts/issues/1556#issuecomment-416034401

v2.23.0 | Report a Bug | By Email