Re: [rtcweb] Interoperability - what have we learned?

[Ron <[e-mail]>]

On Sat, Dec 21, 2013 at 06:25:08PM -0500, Bernard Aboba wrote:
> On Dec 21, 2013, at 6:17 PM, "Ron" <[e-mail]> wrote:
> > 
> > It ...  didn't?  SIP has so many ways to be completely non-interoperable
> > that as a global standard it's been completely stillborn.  Codecs are
> > the least of the many interoperability problems that ruined it by design.
> 
> [BA] Indeed. And let me suggest that we are in great danger of repeating this
> in RTCWEB, which today is not sufficiently specified to enable widespread
> interop - but could be if we were to spend our efforts more wisely.

That's only a danger if we handwave away the Difficult problems with
"let the market decide" platitudes.

I haven't seen other questions of interoperability going unanswered
just because this one is still not resolved yet.  And however many
drafts may still be waiting on something for completion, I haven't
seen huge floods of people reporting having those problems either.

I suspect most people here have mastered chewing gum and walking at
the same time;  so if this is the current bulk of the list discussion
I can only imagine that either people aren't running into many interop
problems in other areas -- or they aren't actually working on their own
independent implementations until they are sure this can be resolved
satisfactorily and that work won't be a total waste of their time.

The two major browser vendors at least seem to be actively collaborating
on resolving any interop problems they have identified and making good
progress with that.  I assume what they learn will make its way into
being properly specified if it isn't already.

What issues do you see that you haven't already been engaging with here?

  Ron