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 Workin Group is available on the main home page of the group.
Meetings
- October 31 - November 1 2011 in Santa Clara, California, USA
- July 23 2011 in Quebec City, Canada
On-going work
API proposal
Editor's draft at: http://dev.w3.org/2011/webrtc/editor/webrtc.html
Use cases and requirements
There is an Editor's draft document at http://dev.w3.org/2011/webrtc/editor/webrtc_reqs.html. However, that document merely refers to the IETF document http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/. 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: http://www.ietf.org/mail-archive/web/rtcweb/current/msg01177.html):
- QoS. Unclear to a large extent at this time
- The use cases 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
- Codec requirements.....
- Section 7.2: should these requirements be moved into the F-req part?
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 issues and actions within the group.
IRC
The group uses IRC to take minutes and exchange info during calls and face-to-face meetings:
- IRC info: #webrtc on irc.w3.org, port 6665
- You may use the W3C Web client, specifying a username and channel #webrtc
- You may find more info on IRC usage at W3C
Other Useful W3C Resources
- World Wide Web Consortium Process Document 14 October 2005
- Art of Consensus Guide (W3C member confidential)
- Notes on IRC at W3C
- The Zakim IRC Teleconference Agent
- Quick Start Guide to taking minutes