Main Page

From Web Real-Time Communications Working Group Wiki
Revision as of 14:38, 22 September 2011 by Fd (talk | contribs) (→‎Meetings)

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

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

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:

Other Useful W3C Resources