- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Wed, 29 Oct 2014 00:32:29 +0100
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: Matthew Kaufman <matthew.kaufman@skype.net>, public-webrtc <public-webrtc@w3.org>
2014-10-28 23:18 GMT+01:00 Silvia Pfeiffer <silviapfeiffer1@gmail.com>: >> I'm not entirely thrilled about all the bugs being closed as "this is the >> IETF's problem", but this one in particular is an issue. There is currently >> NO chain of normative references, RFC or otherwise, which when used as a >> specification results in SDP that is compatible with any SDP generated or >> consumed by any WEBRTC implementation. This is a bug *with the W3C >> specification* until such time as we reach the point where the normative >> references are sufficient to create an interoperable implementation without >> reference to third party source code. > > Is this a quality of implementation issue or a api definition issue? The SDP in WebRTC is a String with ~3700 chars. There is no "API" in there. > Isn't the next version of the spec supposed to abstract away the sdp > surface? Abstracting away the SDP does not fix this issue. The browser still needs to generate and parse SDP (those String with more than 3700 chars). > In your opinion, does ORTC have the right api to resolve this > issue? Of course. -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Tuesday, 28 October 2014 23:33:17 UTC