Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface

[Peter Thatcher <[e-mail]>]

On Tue, Jul 9, 2013 at 4:26 AM, Stefan Håkansson LK <
[e-mail]> wrote:

> On 2013-07-09 12:18, Iñaki Baz Castillo wrote:
> > 2013/7/9 Stefan Håkansson LK <[e-mail]>:
> >> I want to be very clear and careful on what I say. So I am repeating:
> >>
> >> * My comment that I think Eric is right in that there is consensus on
> >> providing APIs that allow most use-cases to be met without SDP mangling
> >> is meant only in that context: SDP O/A is kept (and PeerConnection more
> >> or less as is and so on).
> >
> > Hi Stefan,
> >
> > You insist that "there is consensus on keeping SDP O/A but providing a
> > better API".
>
> I must be expressing myself quite badly, because the message seems not
> to get through.
>
> * I think we have consensus on adding API that allows most use-cases to
> be met without SDP mangling (given that SDP O/A is kept naturally)
>
> * We discussed last year an alternative API that did not use SDP at all
> (and did not use PeerConnection). The decision at that time was to
> continue developing the API based on PeerConnection and SDP O/A.
>
> Have not stated anything more than that.
>

Thank you for clarifying, Stefan.  It's often very difficult for those of
us who weren't there to understand what was consensus, and what wasn't, and
what was decided and what was decided and what wasn't.  It seems that if
you ask 10 people, you get 10 different answers.


In other words, it's hard to see much consensus on what we have consensus
on.


So thank you for your clarifications.  It's probably not a very fun job for
you :).   Along with that, I have two more questions for you:


1.  You said we have consensus on adding API that allows most use-cases to
be met without SDP mangling.  Since that point in time has there been in
any progress in adding such APIs?  Can you give me a rough feel for how
much time has passed, how many proposals have been made, how many have been
accepted, and how many have been implemented?  I think it's great that
we'll do this "someday", but I'd like to get a feel for how far away
"someday" is.  Thanks in advance.

2.  You said we have consensus against an alternative API.  Was that
consensus against any additions to the API that would allow JS to bypass
SDP, or was that a consensus against just that particular alternative API?
 I'd like to get a feel for how many people voted for "no; let's not go
down that specific road" vs. "no; we cannot go on any road but this one".
I think there's a big difference between the two.  Thanks again in advance.


By the way, Ted asked us to move discussions about the API to
public-webrtc, so should we do that now?



> Stefan
>
> > Given current discussions IMHO it is clear there is not
> > such a consensus (not at all). Or may be you are just talking about
> > two years ago in some IETF meeting (if so I'm sorry).
> >
> > Please review the results in
> >
> https://docs.google.com/a/aliax.net/spreadsheet/ccc?key=0AuaKXw3SkHMSdHlZdV9RN0xSWFhybVl4anJLRkVPV0E#gid=1
> >
> >    Bad for advanced stuff: 94%
> >    OK for 1.0: 40%
> >
> > IMHO such a result indicates all but "let's keep SDP O/A and improve a
> > bit the API" (I mean now, in July 2013).
> >
> >
> > Best regards.
> >
> >
> >
> > --
> > Iñaki Baz Castillo
> > <[e-mail]>
> >
>
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
>