Routing Data's relationship to headers about http2-spec HOT 5 CLOSED

Alexey will provide proposed text. This will probably include moving S6.2 (HTTP Header Fields and HTTP/2.0 Headers) out of security considerations to the relevant section (S4.2).

from http2-spec.

Made the change change proposed above. If the WG wants a fixed order of ":"-header fields, this should be another change.

from http2-spec.

This request seems to be based on the "stream" compression of the headers, it is unclear how this might fit in with the new header compression scheme. I'd like to see that land before we place requirements on header ordering.

from http2-spec.

Discussed in Hamburg; need more data - input from intermediary / proxy vendors as to how desirable this is; the relative expense of reading / transmitting compressed vs. uncompressed Host header; whether more headers than Host are necessary.

Requiring that certain headers be available in certain ways from the compressor seems to increase complexity considerably, and likely isn't a good road, as it's a tradeoff of space (on the wire, in buffers, etc.), but not necessarily an assurance of saving time.

from http2-spec.

Revisited in Seattle; adding ordering the current compression scheme would increase complexity for marginal benefit. It is currently implementable.

from http2-spec.