W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2012

Summary of desired spec updates (Was: summary of some ongoing discussions)

From: Justin Uberti <juberti@google.com>
Date: Mon, 16 Jul 2012 14:45:43 -0400
Message-ID: <CAOJ7v-2htpW-vA=g92au_ZBjfQgA-wf4p+NWQ6MX0moH+CX4Fg@mail.gmail.com>
To: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
I've tried to summarize all of these changes and the discussions of the
 past few weeks into a concrete proposal for an updated API. This proposal
is attached, and is also available at
https://docs.google.com/document/d/1nfA1ElWed5PPR4nqenEkxNMMLRfzAsh1yMLe8yRcns8/edit#
.

Summary below.

----------------

*The following changes have been made based on the consensus summarized in
http://lists.w3.org/Archives/Public/public-webrtc/2012Jun/0267.html, namely:

   - Addition of RTC prefix to WebRTC-specific types to avoid namespace
   collisions
   - Addition of async callbacks to indicate result of
   SetLocalDescription/SetRemoteDescription APIs
   - New state names and explicit state diagram set for PeerState/IceState


In addition, the following changes were made based on discussions from the
interim meeting and list feedback:

   - Definition added for RTCIceServer and RTCIceServers
   - Type field moved to SessionDescription object (and removed from
   setLocalDesc/setRemoteDesc)
   - Unnecessary callbacks (onconnecting, onopened) removed
   - createProvisionalAnswer and restartIce parameters removed (now done
   via constraints)
   - Addition of "int mediaIndex" parameter to RTCIceCandidate, to provide
   a simpler matching of IceCandidate to m-line index


Other notes:

   - RTCSessionDescription and RTCIceCandidate remain as objects, not
   dictionaries; since this is the way things currently are, we opted not to
   change it.
   - MediaConstraints are used everywhere, instead of settings
   dictionaries, as it was made fairly clear that we would end up needing the
   same sort of constraints behavior from settings dictionaries. We do need to
   indicate in the documentation which constraints are valid for which API
   calls.

*


Received on Monday, 16 July 2012 18:46:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:28 UTC