Re: [#150] Making certain settings mandatory

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.
>