Code change:
frame.  Providing prioritization information is optional, so default values are used if no explicit indicator is provided (pri-default). <del> Explicit prioritization information can be provided for a stream to either allocate the stream to a priority group (pri-group), or to create a dependency on another stream (pri-depend). </del> 5.3.1. <del> All streams are assigned a priority group.  Each priority group is allocated a 31-bit identifier and an integer weight between 1 to 256 (inclusive). Specifying a priority group and weight for a stream causes the stream to be assigned to the identified priority group and for the weight for the group to be changed to the new value. Resources are divided proportionally between priority groups based on their weight.  For example, a priority group with weight 4 ideally receives one third of the resources allocated to a stream with weight 12. 5.3.2. </del> Each stream can be given an explicit dependency on another stream. Including a dependency expresses a preference to allocate resources <del> to the identified stream rather than to the dependent stream. A stream that is dependent on another stream becomes part of the priority group of the stream it depends on.  It belongs to the same dependency tree as the stream it depends on. </del> <ins> to the identified stream rather than to the dependent stream.  Each dependency is allocated an integer weight between 1 to 256 (inclusive). </ins> <del> A stream that is assigned directly to a priority group is not dependent on any other stream.  It is the root of a dependency tree inside its priority group. </del> <ins> The connection is the root of the dependency tree.  A stream that is not dependent on any other stream is given a stream dependency of 0x0 to signify the connection. </ins> When assigning a dependency on another stream, by default, the stream is added as a new dependency of the stream it depends on.  For

Related discussion:
text: NAME I would add an explicit hint to implementers that having more than 8 bits of internal precision is a good thing. NAME I think we should leave open the possibility to insert a new stream between the connexion and all its children, even if it's probably a large re-prioritization.
I think large re-prioritization is not a problem. If proxy gets such requests and it aggregates several frontend connections to single backend connection, inserting under stream 0x0 with exclusive flag set seems to be impossible in backend.
If it aggregates to a different backend connection it is not impossible to proxy. Consider streams A and B depend on stream 0x0 and are proxied to some backend connection as streams X and Y. If we get a new streams, C, that exclusively depends on 0x0, we can proxy it as stream Z by dropping the exclusive dependency and then re-prioritizing streams X and Y to depend on stream Z.
Yes, it works like that. But if we just don't allow 0x0 with exclusive dependency, we can do all priority stuff via proxy without doing any extra handling except for stream ID mappings.
Yep, true -- I don't have much of a preference -- if clients feel like it is not an important use case than I am perfectly happy to disallow it.
Is it possible to move this discussion to the mailing list? If you need comments from a client, I'm happy to take a look later. On Tue Apr 15 2014 at 9:39:56 AM, Jeff Pinner EMAIL wrote: