RE: WebSocket2

On 05 October 2016, Van Catha wrote: 17:29

Standardized protocol or not is irrelevant.  I was simply considering the options
and what would work.  QUIC uses different negotiation and transport frames then HTTP/2
does (also QUIC does not have HTTP/2 SETTINGS frames). I was proposing ideas at
tackling the problem to make WebSocket2 work across different transport layers.

The current QUIC-H2 mapping document (https://tools.ietf.org/html/draft-shade-quic-http2-mapping-00) discusses the use of HTTP/2 SETTINGS frames in section 3. Some settings are superseded by QUIC transport parameters but I would think that extension negotiation would work fine in QUIC. The charter explicitly calls out accommodation for H2 extension mechanisms.

Lucas




----------------------------

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.

---------------------