- From: Lucas Pardue via GitHub <sysbot+gh@w3.org>
- Date: Sun, 25 Nov 2018 14:43:06 +0000
- To: public-web-and-tv@w3.org
The IETF standard form of QUIC is not a replacement for HTTP/1.1 or HTTP/2. It is a secure, mulitplexed transport that is a substitute for TCP+TLS, or maybe be a suitable substitute for SCTP+DTLS. QUICv1 will not offer unreliable stream delivery, multipath or FEC as standard. I look forward to the continued evolution of a widely adopted transport protocol at internet-scale. As to the WebRTC proposal, there is merit in supporting alternative transport protocols that allow the flexible carriage of application layer protocols. There is merit is exposing capability like this to the web platform. However, I think the proposals of QUIC API for WebRTC need further refinement to interface and implementation. The discussions at the IETF 103 [TAPS session](https://datatracker.ietf.org/meeting/103/materials/slides-103-taps-3c-w3c-quic-api-for-webrtc-01) ([minutes](https://datatracker.ietf.org/meeting/103/materials/minutes-103-taps-00.html)) were useful for context. -- GitHub Notification of comment by LPardue Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/1#issuecomment-441445532 using your GitHub account
Received on Sunday, 25 November 2018 14:43:13 UTC