Status of WebRTC standards work, latest changes and where we are in the process of standardization.

1. WebRTC Standards &
Implementation Q&A
Amir
Zmora
TheNewDialTone
Dan
Burnett
StandardsPlay

2. Watch video recording of this session
http://ccst.io/e/webrtcstandards15

3. Session sponsored by
WebRTC.ventures
is
a
custom
design
and
development
shop
dedicated
to
building
WebRTC based
applications
for
web
and
mobile.
We
have
built
end-­‐to-­‐end
broadcast
solutions
for
events
and
entertainment
clients,
telehealth solutions
for
multiple
clients,
live
support
tools,
as
well
as
communication
tools
for
a
variety
of
other
applications. WebRTC.ventures is
a
recognized
development
partner
of
TokBox and
has
also
built
native
WebRTC solutions

4. We use CrowdCast….It’s WebRTC

5. WebRTCStandards.info
Sponsored by

6. About Us
• Amir Zmora • Dan Burnett

7. Save The Date: May 15th
Register Now: http://ccst.io/e/webrtcstandards16
Next Session

8. Standards Update

9. The next goal for the WebRTC Specification:
Candidate Recommendation
• This matters because
• It is traditionally the point at which potential implementers who have been waiting for stability
can finally feel safe to start – not because nothing will change, but because there is finally an
effort not to change things beyond this point
… and ...
• for the WebRTC group, this was the milestone we required before we would allow the working
group to begin working on the next version of WebRTC
• in order to ensure that we did not distract from finishing WebRTC 1.0

10. What is the Candidate Recommendation stage?
• Stages: Working Draft -­> Candidate Recommendation -­> Proposed Recommendation -­>
Recommendation
• Requirements for
• Entry into Candidate Recommendation:
• The document is believed to be technically complete
• Exit from Candidate Recommendation to Proposed Recommendation
• The document has has wide review
• No substantive changes, other than those marked as at risk, have occurred since entry
• The document has been sufficiently implemented (as evidenced by reports of implementations of a
designated test suite)

11. Much recent progress towards "technically
complete"
• Half of all WebRTC spec
Issues and PRs created in
last 13 months
• Yet number outstanding has
been reduced by 47
• Now stand at 25 total issues
and PRs
(as of April 21, 2017)
0
10
20
30
40
50
60
70
80
4-­‐16 5 6 7 8 9 10 11 12 1-­‐17 2 3 4
Issues
&
PRs
Month
W3C
WebRTC
Spec
-­‐ Monthly
change
in
issues
and
PRs
Opened
Closed

12. How?
• Monthly "virtual interims"
• List available at https://www.w3.org/2011/04/webrtc/wiki/Main_Page
• Diligence by chairs and editors in pushing issues forward
• Enormous work by many
• Particularly Bernard Aboba (Microsoft) and Taylor Brandstetter (Google)
• More than 100 commits in past 3 months by Bernard alone

13. Recent important changes
• PR 1119: make legacy methods optional to implement
• Notable features marked as at risk of removal: Identity (PR 1114), PRANSWER (PR 1110)
• Finally, an error object!
• PR 1003: setLocalDescription() now requires unchanged O/A string (from
createOffer()/createAnswer())
• PR 1030: getStats() now operates on senders and receivers rather than
MediaStreamTracks
• And many, many, many edge case definitions (largely completely new functionality, so no
change to existing code)

14. So now what?
• Target: (first) Candidate Recommendation of WebRTC specification by early May
• After which the group will focus on
• wide review of both documents (Media Capture and Streams and WebRTC)
• development of test suites for both documents
• We expect to need second CR documents for both specifications
• Goals will be
• Truly technically complete (no substantive changes needed after this point)
• Provided with test suites
• Seeking sufficient implementation
• 2 implementations of each required feature, 1 of each optional feature

15. And when will we be done????
• (Sigh)
• Factors to consider
• The simpler Media Capture and Streams specification had its first CR May 19, 2016 (almost a
year ago!) and we are still not ready for the second CR
• The group will be distracted with starting the next version of WebRTC because everyone wants
to work on the shiny new toy rather than do the hard work of finishing up the old toy
• So, when will we be done?
• Unless a Proposed Recommendation is declared by fiat at W3C, violating all of its process, at
the earliest the spec will likely really be technically complete a year from now (May 2018) and
done with the process a year after that (May 2019).

16. ?

17. Save The Date: May 15th
Register Now: http://ccst.io/e/webrtcstandards16
Next Session

18. Session sponsored by

19. WebRTC Standards &
Implementation Q&A
Amir
Zmora
TheNewDialTone
Dan
Burnett
StandardsPlay