[RTW] New draft on WebRTC API draft-jennings-rtcweb-api

[François AUDET]

Hi Cullen,

Can you elaborate on the reasons why you believe that the Adv/Prop model would be more appropriate than offer/answer specifically for the RTCWEB use case?

I understand the problems and limitations with offer/answer in general of course, but I'm assuming that there is something specific to this use case that makes Adv/Prop especially appropriate? In other words, I imagine it's not just because "adv/prov is better than offer/answer in general", right?

Also, while draft-peterson-sipcore-advprop talks mainly about using subscriptions for the Adv phase, I would think that a dynamic pre-negotiation would very often be more appropriate (with OPTIONS or something similar), because many use cases for RTCWEB would not have the luxury of following a presence subscription model (i.e., the target for the call would not necessarily be followed for presence all the time, or even be known by the initiator of the call).

On Mar 10, 2011, at 12:20 , Cullen Jennings wrote:

> 
> I wrote up the start of a draft on requirements and a sketch of an API proposal. It is at
> 
> http://tools.ietf.org/html/draft-jennings-rtcweb-api-00
> 
> I view this as very early but starts to list some of the issues and an evolving sketch of how the API might look. 
> 
> Cullen
> 
> _______________________________________________
> RTC-Web mailing list
> RTC-Web at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/rtc-web