W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2018

Re: status of webrtc-quic

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Wed, 29 Aug 2018 22:52:12 +0000
To: Peter Saint-Andre <stpeter@mozilla.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <DM5PR00MB0327DB576C7F2AB5E64FED4EEC090@DM5PR00MB0327.namprd00.prod.outlook.com>
The QUIC API for WebRTC[4] was originally developed by the ORTC CG as part of the ORTC specification [5].

Peter Thatcher presented it to the WebRTC WG at last year's TPAC meeting in SFO [1].  So as to make it easier for the WEBRTC WG to evaluate, the QUIC-related sections of the ORTC specification were broken out into a separate specification using respec boilerplate which referred to the WEBRTC WG, rather than the ORTC CG.

Feedback on WebRTC-QUIC and WebRTC-ICE was subsequently solicited from the WEBRTC WG on the mailing list [2], at the January 11, 2018 Virtual Interim meeting [3] and also at the F2F meeting in Stockholm.

As you noted, at the Stockholm WEBRTC WG meeting, there was no consensus to adopt WebRTC-QUIC.  The minutes do show interest in further work relating to ICE.

So it appears to me that WebRTC-QUIC is currently a work item of the ORTC CG and probably should have its boilerplate modified to indicate that status.  WebRTC-ICE also has WebRTC WG boilerplate, but it is not related to work in the ORTC CG.

[1] Presentation: https://www.w3.org/2011/04/webrtc/wiki/images/8/8a/WebRTCWG-2017-TPAC.pdf  (starting at slide 82)
Minutes: http://www.w3.org/2017/11/06-webrtc-minutes.html#item24

[2] http://lists.w3.org/Archives/Public/public-webrtc/2018Jan/0037.html [3] https://www.w3.org/2018/01/11-webrtc-minutes#item05 [4] https://w3c.github.io/webrtc-quic/ [5] http://draft.ortc.org/

From: Peter Saint-Andre <stpeter@mozilla.com>
Sent: Wednesday, August 29, 2018 2:18 PM
To: public-webrtc@w3.org
Subject: status of webrtc-quic

The QUIC API for WebRTC [0] asserts it is an Editor's Draft, which is a
spec status [1] reserved for official working group documents. However,
as far as I can see, this work item is not listed in the WG charter [2],
a call for adoption has not yet been issued on this mailing list, and
the summary of decisions from the Stockholm interim [3] indicates that
we did not have consensus to adopt.

Shouldn't this spec be "unofficial" at this point?

And should we have a web platform test in place [4] for something that's


[0] https://w3c.github.io/webrtc-quic/
QUIC API for WebRTC - W3C on GitHub<https://w3c.github.io/webrtc-quic/>
This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received from another browser or device implementing the QUIC protocol.

[1] https://github.com/w3c/respec/wiki/specStatus

[2] https://www.w3.org/2018/07/webrtc-charter.html

[3] https://lists.w3.org/Archives/Public/public-webrtc/2018Jun/0191.html

Received on Wednesday, 29 August 2018 22:52:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:43 UTC