Main Page
Web Real-Time Communications Working Group
This is the Wiki of the W3C Real-Time Communications Working Group. The wiki is the main point of entry for participants of the group as well as for people interesting in the day-to-day life of the group. It is used to collect drafts, ideas and logistics information. Higher-level information about the Web Real-Time Communications Working Group is available on the main home page of the group.
See also the wiki of the Media Capture Task Force.
Meetings
- January 21 2025 Virtual interim (online)
- December 10 2024 Virtual interim (online)
- November 19 2024 Virtual interim (online)
- October 15 2024 Virtual interim (online)
- September 26 2024 MEDIA/WEBRTC WG Joint TPAC Meeting (Hybrid)
- September 25 2024 RtpTransport Breakout Session (Hybrid)
- September 24b 2024 WEBRTC WG/SCCG Joint TPAC Meeting (Hybrid)
- September 24 2024 WEBRTC WG TPAC Meeting (Hybrid)
- August 27 2024 Virtual interim (online)
- June 18 2024 Virtual Interim (online)
- May 21 2024 Virtual Interim (online)
- April 23 2024 Virtual Interim (online)
- March 26 2024 Virtual interim (online)
- February 20 2024 Virtual interim (online)
- January 16 2024 Virtual interim (online)
- December 12 2023 Virtual interim (online)
- December 05 2023 Virtual interim (online)
- November 21 2023 Virtual interim (online)
- October 17 2023 Virtual interim (online)
- September 15 2023 Hybrid (online + TPAC in-person)
- September 14 2023 Hybrid (online + TPAC in-person)
- September 12 2023 Hybrid (online + TPAC in-person)
- July 18 2023 Virtual interim (online)
- June 27 2023 Virtual interim (online)
- May 16 2023 Virtual interim (online)
- April 18 2023 Virtual Interim (online)
- March 21 2023 Virtual Interim (online)
- February 21 2023 Virtual Interim (online)
- January 17 2023 Virtual Interim (online)
- December 7 2022 Virtual Interim (online)
- November 15 2022 Virtual Interim (online)
- October 18 2022 Virtual Interim (online)
- September 2022 TPAC 2022 (Hybrid)
- July 19 2022 Virtual Interim (online)
- June 23 2022 Virtual Interim (online)
- May 17 2022 Virtual interim (online)
- April 26 2022 Virtual interim (online)
- March 15 2022 Virtual interim (online)
- February 15 2022 Virtual interim (online)
- January 18 2022 Virtual interim (online)
- December 14 2021 Virtual interim (online)
- November 24 2021 Virtual interim (online)
- TPAC 2021 Virtual meetings (online)
- October 14 2021 Virtual interim (online)
- September 20 2021 Virtual interim (online)
- July 22 2021 Virtual interim (online)
- June 22 2021 Virtual interim (online)
- May 25 2021 Virtual interim (online)
- April 27 2021 Virtual interim (online)
- March 25 2021 Virtual interim (online)
- February 22 2021 Virtual interim (online)
- January 19 2021 Virtual interim (online)
- December 14 2020 Virtual interim (online)
- December 02 2020 Virtual interim (online)
- TPAC 2020 Virtual meetings (online)
- September 15 2020 Virtual interim (online)
- July 8 2020 Virtual interim (online)
- June 4 2020 Virtual interim (online)
- April 28 2020 Virtual interim (online)
- March 30 2020 Virtual interim (online)
- February 27 2020 Virtual interim (online)
- January 14 2020 Virtual interim (online)
- November 26 2019 Virtual interim (online)
- September 19-20 2019 in Fukuoka, Japan (W3C TPAC 2019)
- July 2 2019 Virtual interim (online)
- June 11 2019 Virtual interim (online)
- April 11 2019 Virtual interim (online)
- March 13 2019 Virtual interim (online)
- Jan 22 2019 Virtual interim (online)
- October 22-23 2018 in Lyon, France (W3C TPAC 2018)
- Sept 25 2018 Virtual interim (online)
* August 29 2018 Virtual Interim (online) CANCELLED
- June 19-20 2018 F2F meeting in Stockholm, Sweden
- May 22 2018 Virtual Interim (online)
- April 26 2018 WebRTC 1.0 testing call (online)
- April 12 2018 Virtual Interim (online)
- February 21 2018 Virtual Interim (online)
- January 11 2018 Virtual Interim (online)
- Public session on WebRTC testing November 6 (online)
- November 6 - 7 2017 in San Francisco, California, USA (W3C TPAC 2017)
- October 12 2017 Virtual Interim (online)
- September 13 2017 Virtual Interim (online)
- June 28 2017 Virtual Interim (online)
- June 7 2017 Virtual Interim (online)
- May 2 2017 Virtual Interim (online)
- April 4 2017 Virtual Interim (online)
- March 1 2017 Virtual Interim (online)
- January 25 2017 Virtual Interim (online)
- December 12 2016 Virtual Interim (online)
- November 9 2016 Virtual Interim (online)
- September 22 - 23 2016 in Lisbon, Portugal (W3C TPAC 2016)
- August 23 2016 Virtual Interim (online)
- June 28 2016 Virtual Interim (online)
- May 27 2016 Virtual Interim (online)
- February 25 2016 Virtual Interim (online)
- January 14 2016 Virtual Interim (online)
- October 29 - 30 2015 in Sapporo, Japan (W3C TPAC 2015)
- September 9 - 10 2015 in Redmond, WA, USA
- Apr 28 2015 teleconf (group rechartering)
- October 30 - 31 2014 in Santa Clara, California, USA (W3C TPAC 2014)
- May 19 - May 21 2014 in Washington DC, USA
- Apr 28 2014
- Dec 19 2013
- November 11 - November 12 2013 in Shenzen, China (W3C TPAC 2013)
- Sep 3 2013
- June 5 2013 (Promises)
- February 6 - February 7 2013 in Boston, USA
- Jan 10 2013
- Dec 13 2012
- October 29 - October 30 2012 in Lyon, France (W3C TPAC 2012)
- Sep 17 2012
- Aug 28 2012
- June 11 2012 in Stockholm, Sweden
- Apr 10 teleconf
- Mar 13 2012 teleconf
- February 1 2012 Feb 1st, Mountain View, CA
- 15 Dec 2011 teleconf
- October 31 - November 1 2011 in Santa Clara, California, USA (W3C TPAC 2011)
- Oct 5 2011 teleconf
- Aug 31 2011 teleconf
- July 23 2011 in Quebec City, Canada
- Jul 12 2011 teleconf,
- May 19 2011 teleconf
Background materials can sometimes be found on the Teleconferences page.
Resolutions
Any resolution taken in a face-to-face meeting or teleconference is to be considered provisional until 10 working days after the publication of the resolution in draft minutes sent to the working groups mailing list. If no objections are raised on the mailing list within that time, the resolution will be considered to have consensus as a resolution of the Working Group.
On-going work
API document
Use cases and requirements
The Editor's draft of Use cases and requirements currently merely refers to the equivalent IETF document. In the IETF document use cases and requirements are listed. New use cases that have been proposed but not yet decided are also listed (with links).
There are however some items that should be discussed more within the context of current use cases and requirements (mostly taken from this mail):
- QoS. Unclear to a large extent at this time. Skip for first version?
- The use case (4.2.5) of using SIP between service providers must be sorted out to know what "SIP" really means and furthermore if all webrtc functionality would be available or if there are certain things you can't do. Also F24 should probably be updated, along with a new API requirement (text proposed from the mail "Web API MUST NOT prevent two webapps that happen to choose to peer with SIP from peering."). Also, the current A18 is vague and it can be discussed how much this is an API question
- What of more "advanced" audio media processing should remain in webrtc, and what should be moved to the Audio WG? Will have implications on F13 and F15 and A14.
- A more advanced IVR use case, or at least more detailed should perhaps replace the text in 4.3.2
- Codec requirements.....
- Section 7.2 (Security): should these requirements be moved into the F-req part?
- More work needed on data channels (unreliable, reliable, file-transfer) in terms of actual use and of requirements.
Stats interface and stats values
Discussion on what is missing to build "real" services
Migration to Github for spec repositories
The WG has agreed that we would rather have the specs on github in repositories hosted under the W3C account than on other version control systems or sites. The page below tracks decisions and work on this.
NV Documents
List of future NV Documents (for tracking): NV Documents
Useful Resources
Mailing-lists
- Archives of the public-webrtc@w3.org mailing-list are publicly available. This mailing-list should be used for all technical discussions within the group.
- Archives of the member-webrtc@w3.org mailing-list are available to W3C Members only. Use of this second list should be restricted to administrative purposes (e.g. sending regrets or F2F logistics)
Tracker
- Tracker is used to track actions within the group. We're only using the ACTION section.
- Buganizer is available for tracking issues and bugs.
The Tracker usage guidelines (Work In Progress) gives details on how and when to use these tools.
IRC
The group uses IRC to take minutes and exchange info during calls and face-to-face meetings:
- IRC channel: #webrtc on irc.w3.org
- You may use the W3C Web client, specifying a username and channel #webrtc
- You may find more info on IRC usage at W3C