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

[Martin Thomson <[e-mail]>]

On 2 July 2013 09:13, Enrico Marocco <[e-mail]> wrote:
> On 7/2/13 6:04 PM, José Luis Millán wrote:
>> Hi,
>>
>> Please, let me know how this normal use case could be solved with the
>> current API.
>
> Just off the top of my head:
>
> 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
>
> Alice rolls back and removes local video display.

This is fine for the case that has been proposed, but it doesn't work
as well if A and B are initiating a session.  In that case, you would
need two rounds of negotiation to get the functionality you describe.

There are two separate problems here:

1. How do I reject a proposed stream?

2. How do I learn that my proposed stream was rejected?

I'm sure that there are controls for this already...  Maybe.  You
could, as Enrico suggests, add streams one-by-one using multiple
offer/answer rounds - then you would be able to isolate what was
rejected. That doesn't really scale.

Note: These questions are only relevant with offer/answer.  Choosing
not to do offer/answer means that the application is in control, so
the question is moot.