3 ms·
For the interested: A working group to standardize QUIC was accepted into the Transport and Services area of the IETF at the last meeting in Berlin a couple of
by x3ro 10y ago
For the interested: A working group to standardize QUIC was accepted into the Transport and Services area of the IETF at the last meeting in Berlin a couple of weeks ago [1].
The WG charter is this one [2]:
Define a new standards track IETF transport protocol based on deployment experience with QUIC. Four focus areas:
* Core transport work: wire format, basic mechanisms
* Security: TLS 1.3 to protect QUIC header and payload
* Application semantic mapping: initial focus on HTTP/2
* Extension to multipath for migration and load sharing
[1]: http://etherpad.tools.ietf.org:9000/p/notes-ietf-96-quic?useMonospaceFont=true&showChat=false http://etherpad.tools.ietf.org:9000/p/notes-ietf-96-quic?use...
[2]: https://www.ietf.org/proceedings/96/slides/slides-96-quic-0.pdf https://www.ietf.org/proceedings/96/slides/slides-96-quic-0....
- amluto 10y ago> * Security: TLS 1.3 to protect QUIC header and payload That seems odd. QUIC's crypto is much nicer than any TLS version or draft last time I looked.