W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: [rtcweb] Proposed message to send to the IETF rtcweb and W3C WebRTC working groups.

From: Philipp Hancke <fippo@goodadvice.pages.de>
Date: Mon, 22 Jul 2013 19:00:11 +0200
Message-ID: <51ED651B.3000401@goodadvice.pages.de>
To: rtcweb@ietf.org, public-webrtc@w3.org, XMPP Jingle <jingle@xmpp.org>
(removed stox)

Am 22.07.2013 17:14, schrieb IƱaki Baz Castillo:
> Great. First thing you should complain about is the fact that current
> WebRTC specification makes unfeasible for a browser to use SDP-XML as
> defined by XEP-0167.

I said this before, but since you insist on repeating your argument i'll 
repeat mine: I have running code doing exactly that.

It's hard work and there are some points where this is PITA, I have 
discovered numerous bugs in chrome (and the jingle spec) along the way, 
but it's certainly not unfeasible.


So far, this mapping works using the elements already defined in XEPs 
0167, 0293, 0294 and 0320 even. 
http://tools.ietf.org/html/draft-ietf-rtcweb-jsep-03#section-4.1 has a 
quite concrete list of features of what functionality the mapping 
between SDP and the xmlish SD has to define.

I'd note that I consider jingle a better way to talk about the session 
description because it has a very clear separation between codec 
negotation and transport which has led to concepts like trickle-ice. 
Also, it defined actions like content-add which seem to have influenced 
unified plan.


I have yet to see the current API fail completly and have been using it 
in ways that were certainly not imagined, e.g. early transport warmup 
using PRANSWER (and I still owe feedback on that to the JSEP authors; 
ironically, the solution is more SDP in the API).
Received on Monday, 22 July 2013 17:00:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:35 UTC