Re: [quicwg/base-drafts] Define initial PRIORITY frame and remove exclusive dependencies (#2075)

[Mike Bishop <[e-mail]>]

For your second, there's no loop.  B depends on A, regardless of A's ancestry.  B might attach to A before or after it gets reparented, but that's fine.

For the first, though, there's defined behavior (in 7540) of creating a dependency on a descendant -- that descendant implicitly moves up to become a peer, then the dependency stated in the priority frame is created.  A client trying to leverage this behavior could produce that sequence.

Another option would be to instead say that declaring a dependency on a descendant is always an error, and you need to explicitly perform the elevation-to-peer step (on the control stream).  That would be consistent with removing exclusive dependencies, because it's eliminating another implicit mutation of the priority tree.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2075#issuecomment-444265261