Re: ENABLE ⇒ PROVIDE | Re: SETTINGS_PRIORITY_SCHEME | Re: Setting to disable HTTP/2 Priorities

[Lucas Pardue <[e-mail]>]

On Wed, 31 Jul 2019, 19:01 Kari Hurtta, <[e-mail]>
wrote:

>
> Yes,
>
>
> SETTINGS_ENABLE_* typically changes how HTTP/2 connection is
> prosessed or allows some usages which otherwise produce
> protocol error (example: SETTINGS_ENABLE_CONNECT_PROTOCOL).
>
> Therefore these these typically allows only 0 ⇒ 1 transitions.
> Feature which is enabled, is not allowed to be turned off because
> it may effect handling of frames which are already sent by
> other peer.
>
> Therefore I think that
>
>     SETTINGS_PROVIDE_HTTP2_PRIORITIES
>
> is better name than
>
>     SETTINGS_ENABLE_HTTP2_PRIORITIES
>
>
> In other words this does not chahneg parsing of HTTP/2
> frames. Even when this is set to 0, sending priorities
> does not cause protocol error.
>
> In SETTINGS_PROVIDE_HTTP2_PRIORITIES server asks
> client to provide (or not provide) http/2 tree
> priorities.
>

Thanks. Along that line of thinking, maybe its simpler just to represent
this as an opt out flag? E.g. SETTINGS_RFC7540_PRIORITY_OPT_OUT which can
only ever be a value of 1. By default H2 endpoints have opted in and they
have a freedom to opt out. However, once they do so there are no take
backs.

Lucas

P.s.the cynic in me would call this SETTINGS_PREXIT. An endpoint that
invokes RFCticle 9050,  needs to select a new deal or crash out to WT(FIF)O
priorities.



>
> ( Another possible name is
>
>   SETTINGS_PROVIDE_TREE_PRIORITIES
>
> )
>
> / Kari Hurtta
>
>