W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: [#150] Making certain settings mandatory

From: Jeff Pinner <jpinner@twitter.com>
Date: Sun, 30 Jun 2013 12:13:18 -0700
Message-ID: <CA+pLO_jS3N7b8DNbr9h6TH_g7CCJg2gisE2QEgY-3_zWyAab1g@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: Roberto Peon <grmocg@gmail.com>, Mike Belshe <mike@belshe.com>, Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Here the initial values CAN be changed by a client sending the header
during the upgrade process.

The question is if sending certain settings should be mandatory.

Are you proposing we remove all default values and require that they all be
explicitly negotiated?


On Sat, Jun 29, 2013 at 1:47 PM, Eliot Lear <lear@cisco.com> wrote:

>
> On 6/29/13 9:47 PM, Jeff Pinner wrote:
>
> So devil's advocate -- why make the mandatory during Upgrade?
>
>  If the client is upgrading to HTTP/2.0 and doesn't send them, why can't
> we just assume that the client has accepted the default values?
>
>
> Because defaults can NEVER be changed.  Sometimes it's better to not ever
> have them.
>
Received on Sunday, 30 June 2013 19:13:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:11 UTC