- From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
- Date: Thu, 31 Mar 2016 18:25:09 +0200
- To: public-ortc@w3.org
- Message-ID: <56FD4F65.4070806@gmail.com>
I think that those topics are the weakest topics in ORTC, and we should leave them resolved asap to avoid "backward compatibility issues" that would prevent us to have a much more efficient/user friendly api. I believe that a face 2 face meeting is much more effective for solving this, but I understand that we are quite far away to do it, so I am ok with the virtual meetings. Best regards Sergio On 31/03/2016 4:01, Bernard Aboba wrote: > > [BA] There are open issues relating to the object model for > RTX/RED/FEC that have the potential to affect both the ORTC API as > well as WebRTC 1.0: > > Issue 444 (RTX APT): https://github.com/openpeer/ortc/issues/444 > <https://github.com/openpeer/ortc/issues/444> > > Issue 440 (Split RTCRtpEncodingParameters): > https://github.com/openpeer/ortc/issues/440 > <https://github.com/openpeer/ortc/issues/440> > > Issue 528 (RTX/RED/FEC handling): > https://github.com/w3c/webrtc-pc/issues/548 > <https://github.com/w3c/webrtc-pc/issues/548> > > My preference would be to have a discussion of these issues well > before TPAC (or even the July IETF meeting in Berlin). > > This could be accomplished via an online meeting (an ORTC CG meeting > and/or a WebRTC WG virtual interim) > > Peter said: > > “Would it make sense to do so near TPAC, since that's nearby? Or even > > around the July IETF, which is in Berlin? I love Spain (I used to live > > there), and would enjoy going there, but for me (and I'm guessing others), > > doing on long trip with two spots nearby is easier than two long trips (or > > N vs N+1, as the case may be). > > ” >
Received on Thursday, 31 March 2016 16:25:40 UTC