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

[Enrico Marocco <[e-mail]>]

On 7/2/13 8:05 PM, Martin Thomson wrote:
> 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.

Come on, Martin, what Enrico suggested was one of a probably unlimited
number of possible approaches for one very specific supposedly
unaddressable use case. It was put together and sent within 9' since the
initial email hit the list -- don't build your case on it!

FWIW I agree that, in more complex scenarios where streams are
frequently added and/or removed, requiring a single O/A for each
operation is going to be a problem. My preference -- a reasonable
tradeoff at this point in time -- would be to limit SDP O/A to
negotiation of ICE params, crypto material and payload types, and do
stream manipulation in an app-specific way. The latter is no-plan, that
incidentally carries my name on it. The former looks pretty much like
plan A.

Enrico