• Moderated by Ami and Lorenzo
  • Lorenzo presented ideas based on his slides

Feedback from the participants:

  • jQuery-like WebRTC might or might not be of general interest
  • the question of using a url-like is reasonable and there are demos

that are build around that idea; having an simple url will simplify a throw away a lot of the flexibility

  • writing a WebRTC application focusing only on streaming, make it

very simple to an implementor by referring to a simple URL scheme

Pain-points for WebRTC from the participants:

  • Once a peer connection is rolled back, it is very difficult to

recover from that

  • The spec has more than any other spec on the web (due to its

multi-layer structure)

  • The surface provided by the WebRTC is very good
  • Multi-party, multi-stream gets a bit crazy
  • Compatibility between different versions of Chrome is a problem
  • Chrome implementation is not fully compatible with the SDP

(it's unfortunate, nobody actual enjoys the SDP that is in WebRTC) (maybe most of the people would have done it differently now?)

  • API interface such that SDP wraps into proper objects and allows

the developers to not know anything about SDP

  • There are a lot of very good SDP library -- SDP-transform

https://npmjs.org/package/sdp-transform ?

  • It's a very good to go away from SDP, but because of JavaScript?

objects it's not necessarily that you get what you want

  • Work to get gstreamer working with this without going

through a browser

  • There is someone implementing in WebKit? GTK

WebRTC and text tracks?

  • Captions in a video conference would be nice
  • Having someone on the other side typing captions and transmitting,

can be done today easily

  • Not really getting a lot of attention?

WebRTC states about other browsers:

  • Firefox is working on it
  • WebKit? community does work around this area too (not Apple contributors,

the nix port which uses gstreamer and they're working on the WK infrastructure too)

  • IE there seem to be indications (?)

Did the whole Cisco-thing help with the codec-related fight?

  • It adds information and it forces certain questions to be asked, helpfull

to move things forward and toward a resolution

  • It isn't a game changer, none of the actors have turned 180.

Anything interested that come out of TPAC related to WebRTC:

  • conversation around tracks: is this the best we can do for an API?