As defined in its charter, the mission of the Web Real-Time Communications Working Group, created in May 2011, and renewed in July 2015 is to define client-side APIs to enable Real-Time Communications in Web browsers.
The current roadmap of the group is delayed compared to the proposed schedule in the charter. The updated schedule (where agreed) is detailed below.
|Specification||Internal draft||TR Working draft||Stable draft (Last Call)||Implementors feedback (CR)||Standard (Rec)||Test Suite||Notes|
|WebRTC 1.0: Real-time Communication Between Browsers||Repository, Issues, Editors draft
||28 Feb 2016||N/A (Process 2014)||Q2 2016?||Repository, Test suite|
|Media Capture and Streams (getUserMedia)||Repository, Issues, Editors draft
||12 Feb 2015||14 Apr 2015||19 May 2016||Repository, Test suite||Part of Media Capture Task Force — Last Call comments tracker|
|MediaStream Recording||Repository, Editors draft
||8 Sep 2015||N/A (Process 2014)||Part of Media Capture Task Force|
|MediaStream Image Capture||Repository, Issues, Editors draft
||27 Jan 2015||N/A (Process 2014)||Part of Media Capture Task Force|
|Media Capture Depth Stream Extensions||Repository, Issues, Editors draft
||26 Feb 2016||N/A (Process 2014)||Part of Media Capture Task Force|
|Media Capture from DOM Elements||Repository, Issues, Editors draft
||19 Feb 2015||N/A (Process 2014)||Part of Media Capture Task Force|
|Audio output devices API||Repository, issues, Editors draft
||Feb 10 2015||N/A (Process 2014)||Part of Media Capture Task Force|
|Identifiers for WebRTC's Statistics API||Repository, Editors draft
||6 Feb 2015||N/A (Process 2014)|
|Screen Capture||Repository, issues, Editors draft
||10 Feb 2015||N/A (Process 2014)||Part of Media Capture Task Force|
MediaStream Capture Scenarios
(as part of the Media Capture Task Force)
This non-normative document will end as a Working Group Note.
Documents and Logistics
The Web Real-Time Communications Working Group's wiki documents ongoing works, draft documents and other working materials and logistics information.
See the list of current participants.
We track open bugs on our specs using Github’ issue tracker in the relevant repositories.
Some documents of interest to participants in the Working Group:
- Latest draft of Web Real-Time Communication Use-cases and Requirements (WebRTC/RTCWEB joint document)
- Real-Time Communication in WEB-browsers IETF group
- Report and papers from the RTC Web Workshop held in October 2010.
The group meets on an ad-hoc basis week on the phone. Please check the mailing-list for logistics information.
Minutes: June 28 2016 Virtual Interim,, May 27 2016 Virtual Interim, Feb 25 2016 Virtual Interim, Jan 14 2016 Virtual Interim, Oct 29 2015 F2F, Oct 30 2015 F2F, Sep 10 2015 F2F, Sep 9 2015 F2F, April 28 2015 teleconf (group rechartering), Oct 30-31st 2014 F2F (TPAC), May 21 2014 F2F, May 20 2014 F2F, Apr 28 2014, Dec 19 2013, Nov 12 2013 F2F, Nov 11 2013 F2F, Sep 3 2013, June 5 2013 (Promises), Feb 7 2013 F2F, Jan 10 2013, Dec 13 2012, Oct 30 2012 F2F, Oct 29 2012 F2F, Sep 17 2012, Aug 28 2012, June 11 2012 F2F, April 10 teleconf (draft), March 13 2012 teleconf, Feb 1 2012 F2F, 15 Dec 2011 teleconf, Nov 1 2011 F2F, Oct 31 2011 F2F, Oct 5 2011 teleconf, Aug 31 2011 teleconf, July 23 2011 F2F, July 12 2011 teleconf, May 19 2011 teleconf
The calls of the Media Capture task force are logged on the task force home page.
Past F2F in Sapporo, Japan / TPAC 2015 (Oct 29-30 2015)
Past F2F in Seattle/Redmond, WA, USA (Sep 9-10 2015)
Past F2F in Shenzhen, China and Seattle, USA (Nov 11-12 2013)
Past F2F in Bedford, MA, USA (Feb 7 2013)
The group held its sixth F2F meeting on February 7 in Bedford, MA, USA, combined with a F2F meeting of the Media Capture Task Force and an interim meeting of the IETF RTCWeb and MMusic Working Groups: agenda, minutes.
Past F2F in Lyon, France (October 29-30 2012)
Past F2F in Stockholm, Sweden (June 11 2012)
Past F2F in Mountain View, USA (Feb 1st 2012)
Past F2F in Santa Clara, USA (Oct/Nov 2011)
This group operates under the W3C Patent Policy — see its Patent Policy status for more details.