Re: Call for adoption - WEBRTC-QUIC

Ted Hardie said:

"Building an API without those pieces being done is both risky and potentially destructive of working relationship of the IETF and W3C in this space."

[BA]  Thank you Ted for your extraordinary confidence in the efficiency of the W3C WEBRTC WG.  Given how long it has taken to get WebRTC-PC to Candidate Recommendation (6 years?), there are many who doubt the WEBRTC WG's ability to complete work in a timely manner.  Looking at the IETF QUIC WG Charter, the current estimate is that the QUIC Transport document will be completed by July 2019.  So the idea that the WEBRTC WG could guide WEBRTC-QUIC to completion (or even some level of stability) prior to that date (or even within a year or two of it) represents such extraordinary confidence in the WG that even sceptics lie stunned into silence.  To the doubters - no comments on "the triumph of hope over experience", please.

Of course, one could have made the same argument with respect to starting work on the WebRTC-PC API, since it depended on completion of work items within the IETF RTCWEB and other WGs, whose completion dates were uncertain. No doubt, had we waited until all RTCWEB WG work items were completed to begin work on the WebRTC API, the eventual result would have been different (and perhaps better).  Though there is the (minor) issue of what developers would have done in the interim.

Received on Wednesday, 28 November 2018 22:00:57 UTC