Re: [quicwg/base-drafts] HTTP/3 with strict priorities (#2700)

[Lucas Pardue <[e-mail]>]

LPardue commented on this pull request.

This seems like a strong alternative candidate for modifying prioritisation without massive deviation from the H2 spec

>      {{prioritized-element-types}}). When sent on a request stream, this MUST be
-    set to `11`.  When sent on the control stream, this MUST NOT be set to `11`.
+    set to `0`.
+
+  D (Dependent On Placeholder):
+  : A one-bit field indicating whether a element depends upon a placeholder

```suggestion
  : A one-bit field indicating whether an element depends upon a placeholder
```

>  {: #element-dependency-types title="Element Dependency Types"}
 
 Note that unlike in {{!RFC7540}}, the root of the tree cannot be referenced
-using a Stream ID of 0, as in QUIC stream 0 carries a valid HTTP request.  The
-root of the tree cannot be reprioritized.
+using 0, so the root of the tree cannot be reprioritized.
 
 The PRIORITY frame can express relationships which might not be permitted based
 on the stream on which it is sent or its position in the stream. These
 situations MUST be treated as a connection error of type HTTP_MALFORMED_FRAME.
 The following situations are examples of invalid PRIORITY frames:
 
 - A PRIORITY frame sent on a request stream with the Prioritized Element Type

Since the list is one bullet point long with this change, you could probably roll this back into prose

-- 
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/2700#pullrequestreview-237785560