Status report on the work of establishing a W3C activity to do the API work. If your company is a W3C member, you should make sure your AC representative knows you're aware of and engaged in this. Cullen and I are bashing out a corresponding IETF charter proposal. Harald ---------- Forwarded message ---------- From: Ian Jacobs <ij@w3.org> To: W3C Members <w3c-ac-forum@w3.org> Date: Thu, 16 Dec 2010 12:52:00 -0600 Subject: Work started on Web Real-Time Communications Working Group (Advance Notice) Dear Advisory Committee Representative, This is an advance notice that the Team has started work on a charter for a Working Group to produce specifications that enable Real Time Communications in Web browsers. While Web browsers have gained good capabilities to play audio and video files, they currently don't make possible to establish a direct communication link between clients. Based on discussions at an informal workshop in October, a number of W3C Members have expressed interest in specifying the technologies needed to enable this: the protocol considerations would be taken to the IETF, and the proposed W3C Working Group would work on the client-side technologies, such as the ones needed to facilitate synchronization of streams, or echo cancellation. A draft charter is available (this is not a formal review, just an early draft): http://www.w3.org/2010/12/webrtc-charter We welcome your general expressions of interest and support on <w3c-ac-forum@w3.org>. You may also send comments directly to Dominique Hazaël-Massieux <dom@w3.org>. This announcement follows section 6.2.2 of the Process Document: http://www.w3.org/2005/10/Process-20051014/groups#WGCharterDevelopment For Tim Berners-Lee, Director, Philipp Hoschka, Ubiquitous Web Domain Lead, and Dominique Hazaël-Massieux, Mobile Web Initiative Activity Lead, Ian Jacobs, Head of W3C Communications -- Ian Jacobs (ij@w3.org) http://www.w3.org/People/Jacobs/ Tel: +1 718 260 9447 --