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

Lucas Pardue <> Wed, 08 August 2018 14:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 47BC4130E0D for <>; Wed, 8 Aug 2018 07:21:06 -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 Jv0HeKDuZK0a for <>; Wed, 8 Aug 2018 07:21:03 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BB235130E20 for <>; Wed, 8 Aug 2018 07:21:03 -0700 (PDT)
Date: Wed, 08 Aug 2018 07:21:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1533738063; bh=5eN0Ui+9sp2i8Jh2z4Q563wRGywagglDeOIGQqHK3Fk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=E2t9Fv/We2YHxgKVTBLwmEshRj0WE2Jp5C2o3gspmIAKRTEZ5SwoB0tfvXNG/ZrhR y/D5+A8GpQ2rSmJiymel0WJJd+VJL1YnzFTK33OplspFdBimtmaf3Bh0vMM2BrS5t6 SwHlLSD2kHcJtcqJULrjLnhW4UtSi0prBqiQOI4g=
From: Lucas Pardue <>
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_5b6afc4eeaf79_40be3fca71cbe6181752cc"; 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
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: Wed, 08 Aug 2018 14:21:06 -0000

I think there is merit in making SETTINGS simple numerical values, arising from lack of compelling argument otherwise. 

Are use cases that would like more forms of expression really going to be satisfied with an unmodifiable SETTINGS value?

> Here's an example that might make sense, though I doubt that I would implement it... a setting that included a base URL so that request targets could be identified relative to that URL if desired. That might be justified on the basis that we can't compress parts of header fields (for good reasons), but that particular tweak is probably safe.

This is curious example but I'll bite. You could achieve the same by defining an extension, enabled by a new numerical SETTINGS value, that articulates the base URL in a new extension frame. 

To take this to an extreme, we could imagine a request group concept *cough* where a set of requests are linked to a particular base URL via stapling to this extension frame. The base URL can be modified through the lifetime of the QUIC connection if needs be. 

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