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

Actions on open issues (Re: Sorting possible technical issues into categories)

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 25 Sep 2012 16:16:59 +0200
Message-ID: <5061BCDB.9060507@alvestrand.no>
To: public-webrtc@w3.org
I've added some items to the action tracker:
https://www.w3.org/2011/04/webrtc/track/

On 09/17/2012 12:35 PM, Stefan Hakansson LK wrote:
>
> *Being addressed*
> -----------------
> - *Learn what ICE candidates are in use*: this is part of the proposed 
> stats report
Existing ACTION-12 and ACTION-54
>
> - *Pausing and muting of streams*: there is already enable/disable on 
> tracks available [3], and there has recently been a proposal to move 
> this functionality to the consumer (e.g. PeerConnection) [2].
New ACTION-57
>
> - *Expose additional ICE state:*, *Remove offer/answer*, *Description 
> of state/behavior is currently incomplete*, *Document how the 
> different state machines interact*: The discussion of states for 
> PeerConnection, including SDP exchanges, is ongoing
Existing ACTION-51
>
> - *Are MediaStreams mutable objects?*: According to [3] they are (but 
> there is a recent proposal that a MediaStream being received from a 
> peer shall not be mutable [4])
New ACTION-58
>
> *Needs to be addressed*
> ----------------------
> - *Rollback of offers*
New ACTION-55
>
> - *Provide congestion feedback API for flows*, *Bandwidth allocation*, 
> *Bandwidth estimation feedback* (there is a bug filed related to this 
> [5]; [4] proposed an API surface that might suitable; BW allocation is 
> perhaps mostly and IETF matter)
New ACTION-56

I have not allocated specific actions for the following:
>
> *Needs further discussion*
> --------------------------
> - *DTMF onTone event*: unclear if there is consensus for supporting 
> this feature, is currently not covered by use-case document [6])
>
> - *Set Security Description*: need the discussion in IETF to finalize 
> first
>
> - *Learning of network change events*: need to discuss the role of app 
> and the role of the UA
> - *Priority allocation*: need further discussion
>
> - *API for discovering capabilities* (this has to some extent been 
> discussed in the Media Capture TF)
>
> *Needs to be more clearly described*
> ------------------------------------
> - *Control connection establishment based on certificate*
>
> - *Split SDP between PeerConnection and MediaStream*
>
> - *Serialization of duplicated tracks*
>
> - *Programmatic description of described streams*
>
> [1] http://lists.w3.org/Archives/Public/public-webrtc/2012Aug/0194.html
> [2] 
> http://lists.w3.org/Archives/Public/public-media-capture/2012Aug/0029.html
>
> [3] http://dev.w3.org/2011/webrtc/editor/getusermedia.html
>
> [4] http://lists.w3.org/Archives/Public/public-webrtc/2012Sep/0025.html
>
> [5] https://www.w3.org/Bugs/Public/show_bug.cgi?id=15861
> [6] 
> http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/
> [7] http://lists.w3.org/Archives/Public/public-webrtc/2012Sep/0098.html
>
Received on Tuesday, 25 September 2012 14:19:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 25 September 2012 14:19:51 GMT