Re: [rtcweb] A compromise for SDES

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

On 7/13/13 11:02 PM, Bernard Aboba wrote:
> Hadriel --
>
> I think you've brought up a critical point, which is very worth keeping
> in mind throughout the discussions in IETF RTCWEB.  That is that WebRTC
> is really two distinct innovations -- one, a profile of "RAI 2.0"
> functionality, defining a core set of RTP functionality developed over
> the last decade (e.g. end-to-end security, adaptive HD codecs, AVPF,
> etc.), and the other, a set of Javascript APIs for Web browsers defined
> by the W3C.IMHO,  the "RAI 2.0" aspect is likely to prove more
 > important (and long-lived) than the W3C WEBRTC API aspect.


I think that the Javascript APIs are going to be very important, but I 
fully agree that the "RAI 2.0" profile defined will be used beyond 
browsers. And I think that the more self contained (i.e. not dependent 
on other signaling during operation) we can make that RAI 2.0 profile 
the better.

So I am again arguing for pushing things like pause/resume signaling to 
RTP/RCTP, and not depend on out of band exchanges of signaling messages.