Original text:
stream A, this results in a dependency order of A followed by D followed by B and C. <del> Streams are ordered into several dependency trees within their priority group.  Each dependency tree within a priority group SHOULD be allocated the same amount of resources. Inside a dependency tree, a dependent stream SHOULD only be allocated resources if the streams that it depends on are either closed, or it is not possible to make progress on them. </del>  <del> Streams with the same dependencies SHOULD be allocated the same amount of resources.  Thus, if streams B and C depend on stream A, and if no progress can be made on A, streams B and C are given an equal share of resources. </del>  A stream MUST NOT depend on itself.  An endpoint MAY either treat this as a StreamErrorHandler of type , or assign pri-default to the stream. <del> 5.3.3. </del>  Stream priorities are changed using the <del> frame.  Setting a priority group and weight causes a stream to become part of the identified group, and not dependent on any other stream. Setting a dependency causes a stream to become dependent on the identified stream, which can cause the reprioritized stream to move to a new priority group. All streams that are dependent on a reprioritized stream move with it.  Setting a dependency with the exclusive flag for a reprioritized stream moves all the dependencies of the stream it depends on to become dependencies of the reprioritized stream. </del>  <del> 5.3.4. </del>  When a stream is closed, its dependencies can be moved to become dependent on the stream the closed stream depends on, if any, or to <del> become new dependency tree roots otherwise. </del>  It is possible for a stream to become closed while prioritization information that creates a dependency on that stream is in transit.

Reviewer comments:
The priority groups are abandoned in favor of a single weighted dependency tree. The root node of the tree is the connection, assigned the stream identifier 0x0. By default, streams are assigned a stream dependency of 0x0 with a weight of 16.
Just read through it, I think it looks good. I'd like to understand how weight of the stream is calculated and changed. Here is my understanding: The effective weight of each stream is determined by traversing tree node, taking into account of distribution of weight of parent stream among siblings. This effective weight is temporal on the tree and initial weight is unchanged for a stream, so when reprioritizing that stream, its weight is initial one. For example, suppose we have the following dependency tree: X<--(w)--Y means that Y depends on X with weight w (and w is initial weight). Calculated effective weight is like this: If parent stream is closed, then its initial weight is distributed to among the child streams and this updates initial weight of child stream. So, after A was closed, the initial weight of streams becomes like this:
NAME thanks for this. I'll have to read through this more carefully before I comment. NAME that seems right. Note that this means that a server might want to maintain more precision on it's weight values than the 8 bits we mandate in the protocol. That said, if there are deep dependency trees and you are killing off nodes that are high up, at some point you will need to round off, so I think that how much precision is allocated is largely a discretionary thing.
Looks good. , Martin Thomson EMAIL:
It seems that we can make a stream to depend on stream 0x0 exclusively, which makes all existing connections its descendant. This is not possible in the current draft version. I wonder this can be directly proxy-able since stream 0x0 is imaginable stream.
Yea, the idea is that '0' is a reserved stream ID, and so it is safe to use it as a flag for saying that (effectively) any stream with '0' as a parent has no parent. , Tatsuhiro Tsujikawa wrote:
Well, then we should explicitly say that receiver must treat exclusive bit as 0 if stream ID field is 0.
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:

Revised text:
stream A, this results in a dependency order of A followed by D followed by B and C.  <ins> Inside the dependency tree, a dependent stream SHOULD only be allocated resources if the streams that it depends on are either closed, or it is not possible to make progress on them. </ins>  <ins> Streams with the same dependencies SHOULD be allocated resources proportionally based on their weight.  Thus, if stream B depends on stream A with weight 4, and C depends on stream A with weight 12, and if no progress can be made on A, stream B ideally receives one third of the resources allocated to stream C. </ins> A stream MUST NOT depend on itself.  An endpoint MAY either treat this as a StreamErrorHandler of type , or assign pri-default to the stream.  <ins> 5.3.2. </ins> Stream priorities are changed using the  <ins> frame.  Setting a dependency causes a stream to become dependent on the identified stream.  All streams that are dependent on a reprioritized stream move with it.  Setting a dependency with the exclusive flag for a reprioritized stream moves all the dependencies of the stream it depends on to become dependencies of the reprioritized stream. </ins>  <ins> 5.3.3. </ins> When a stream is closed, its dependencies can be moved to become dependent on the stream the closed stream depends on, if any, or to  <ins> become dependent on the connection otherwise.  The weights of new dependencies SHOULD be assigned by distributing the weight of the dependency of the closed stream proportionally based on the weights of its dependencies. </ins> It is possible for a stream to become closed while prioritization information that creates a dependency on that stream is in transit.