RE: DRAFT: more details for HTTPtre

Hi Mike,

The connection coalescing case is interesting as it's not currently described in HTTP/QUIC. Presumably by oversight or time constraint rather than intent. (We've got a ticket open tracking that one.)

Changing track, I've just seen your SNI I-D
https://tools.ietf.org/html/draft-bishop-httpbis-sni-altsvc-00

References to Frames don't state a specific mapping (HTTP/2 or HTTP/QUIC). Reading between the lines this seems intentional, which got me thinking that also Frames could be described as a new HTTP semantic for binary-capable wire formats.

Lucas
________________________________________
From: Mike Bishop [mbishop@evequefou.be]
Sent: 28 November 2017 18:32
To: Lucas Pardue; ilariliusvaara@welho.com
Cc: Mark Nottingham; HTTP Working Group; Patrick McManus
Subject: RE: DRAFT: more details for HTTPtre

I agree that HPACK is largely decouplable from HTTP/2, or HTTP.  The core of the protocol is a general-purpose compression algorithm for streaming key-value dictionaries, rather than straight text.  The pieces that bind it to H2 are incidental, and perhaps we could have structured it differently.

Coalescing isn't a new semantic -- each HTTP mapping defines how parallelism and connection reuse should work in that mapping.  HTTP/2 simply happens to define it more expansively than HTTP/1.1.






-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------

Received on Thursday, 30 November 2017 10:13:24 UTC