Re: [quicwg/base-drafts] QPACK: instructions and stream description is suboptimal (#2339)

[afrind <[e-mail]>]

> my currency is the header block. I've been told it can be sent in HEADERS and PUSH_PROMISE, I don't need to be told how those frames are sent (i.e. what streams).

Maybe it would simplify the document to refer to encoder stream, decoder stream and header blocks in that case?

>  I'd class the instructions as a primitive of header compression.

True, much like frames are primitives in transport and HTTP.  Both documents were reorganized as concepts first and wire-specifics following.  Perhaps instructions as a concept aren't explained early enough?  I'd prefer to keep the wire instructions after concepts.

> It still hasn't leapt out to me if the encoder and decoder stream exchange clear header blocks, or just a stream of instructions.

See 4.3 and 4.4

> The contents of the en/decoder stream are an unframed sequence of the following instructions.

-- 
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/2339#issuecomment-454876451