Subject: [quicwg/base-drafts] Extension poster-child (#1482)

From: Mike Bishop <[email-masked]>
Date: Tue, 26 Jun 2018 15:53:43 -0700

Lars had suggested a while back that BLOCKED and friends are unnecessary to the core protocol.  These frames are NOT REQUIRED, but since you’re allowed to send them, every implementation must be able to receive and skip them even if they’re ignored.  In HTTP/2, we decided to remove BLOCKED from the main spec and let that be reintroduced as an extension if anyone wanted.  (It turned out no one did.)

As part of the review on the new Extension mechanism, Ian had suggested that we should consider actually publishing an extension to demonstrate how the extension mechanism would work.  It has also proved useful in HTTP/2 to have some extensions we can point authors to and say “do it like that.”

Now that the extension mechanism is landing/landed, does the working group want to consider pulling BLOCKED and kin out to a separate document and letting it be our recommended demo extension?

-- 
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/issues/1482