Re: [rtcweb] Basic scenario 'impossible?' to achieve with the actual API

[Stefan Håkansson LK <[e-mail]>]

On 7/2/13 8:05 PM, José Luis Millán wrote:
> In order to avoid the exposed circumstance, where a user has to
> 'suppose' she is sharing her media because there is no way to certainly
> know, yes, the JS application should be able to, at least, check if a
> localMediaStream is being transmitted out of the RTCPeerConnection.

There is a proposal that addresses this:

http://lists.w3.org/Archives/Public/public-webrtc/2013Jan/att-0005/PrioAPI.pdf

(Note that the constraint part would be simplified per the recent 
agreements in the Media Capture TF)

Stefan



>
> This would be a simple task if each mediaStream, or mediaStreamTrack had
> it's own associated (even if logical because of Boundle) transport. In
> that case, such connectivity status would give the information and much
> more control over each media element.
>
>
> 2013/7/2 Jim Barnett <[e-mail]
> <mailto:[e-mail]>>
>
>     When the JS calls setRemote with the response (which rejects the
>     video), the UA will know that the video has been rejected.  Is the
>     idea that the UA will let the user know via the chrome?  Do we think
>     it is the JS applications job to notify the user of success/failure,
>     or the UA's?  I don't recall a discussion of this.
>
>     - Jim
>
>     -----Original Message-----
>     From: [e-mail] <mailto:[e-mail]>
>     [mailto:[e-mail] <mailto:[e-mail]>] On
>     Behalf Of Iñaki Baz Castillo
>     Sent: Tuesday, July 02, 2013 12:48 PM
>     To: Enrico Marocco
>     Cc: [e-mail] <mailto:[e-mail]>
>     Subject: Re: [rtcweb] Basic scenario 'impossible?' to achieve with
>     the actual API
>
>     2013/7/2 Enrico Marocco <[e-mail]
>     <mailto:[e-mail]>>:
>      > Audio-only call establishment:
>      >
>      > A --{"action":"CALL","sdp":"v=0..."}-> B B --{"action":"ACCEPT
>      > CALL","sdp":"v=0..."}-> A
>      >
>      > Rejected audio+video upgrade proposal:
>      >
>      > A --{"action":"UPGRADE","sdp":"v=0..."}-> B B --{"action":"REJECT
>      > UPGRADE"}-> A
>
>
>     SDP itself is a media negotiation protocol so SDP (and its WebRTC
>     "API") should provide a way to determine whether the remote has
>     accepted or not our new stream/track. But how? Current API lacks any
>     kind of event for the case in which the remote replies a SDP
>     rejecting our new local strem/track.
>
>     --
>     Iñaki Baz Castillo
>     <[e-mail] <mailto:[e-mail]>>
>     _______________________________________________
>     rtcweb mailing list
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/rtcweb
>     _______________________________________________
>     rtcweb mailing list
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
>
> --
> José Luis Millán