Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface

Philipp Hancke <fippo@goodadvice.pages.de> Thu, 04 July 2013 06:35 UTC

Return-Path: <fippo@goodadvice.pages.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE8BD21F96D5 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 23:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1JwQar7eEbB1 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 23:35:50 -0700 (PDT)
Received: from lo.psyced.org (lost.IN.psyced.org [188.40.42.221]) by ietfa.amsl.com (Postfix) with ESMTP id 467A821F8FAF for <rtcweb@ietf.org>; Wed, 3 Jul 2013 23:35:49 -0700 (PDT)
Received: from lo.psyced.org (localhost [127.0.0.1]) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id r646ZlxA015791 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jul 2013 08:35:47 +0200
Received: from localhost (fippo@localhost) by lo.psyced.org (8.14.3/8.14.3/Submit) with ESMTP id r646ZkPe015787; Thu, 4 Jul 2013 08:35:46 +0200
X-Authentication-Warning: lo.psyced.org: fippo owned process doing -bs
Date: Thu, 4 Jul 2013 08:35:46 +0200 (CEST)
From: Philipp Hancke <fippo@goodadvice.pages.de>
X-X-Sender: fippo@lo.psyced.org
To: Eric Rescorla <ekr@rtfm.com>
In-Reply-To: <CABcZeBMCGdY=LS0OG22aFdhwU2m_-H4_sHb15SAYBT7e2_4RLQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1307040753330.14960@lo.psyced.org>
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <CABcZeBPa4wBS8pYq=0wesMOfL6TkeC7QGAZ8pWwOcnkhkJqWfA@mail.gmail.com> <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com> <CABcZeBOTKpmFC34waqZ4kA-P8t+E6yY9gX1JFCHhsBH0+CF-Qw@mail.gmail.com> <CALiegfnDD8PAxZMfczV=cZtwx49XDT2+XiRhe5t88cT+xayz5g@mail.gmail.com> <CABcZeBMCGdY=LS0OG22aFdhwU2m_-H4_sHb15SAYBT7e2_4RLQ@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="683466026-978727032-1372919747=:14960"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jul 2013 06:35:54 -0000

On Wed, 3 Jul 2013, Eric Rescorla wrote:
> Who said anything about impossible? It's a mechanical transformation
> (see: http://xmpp.org/extensions/xep-0167.html).

That is true for simple usage and works reasonably well. See my
strophe.jingle code on github. I'd note that I want to revamp
the API such that it wraps the peerconnections SDP apis more closely.

Things like the content-add/content-remove are harder because the API 
user is required to calculate an SDP delta/diff. The appendix A.1.3 of the 
JSEP draft calls this createContentAdd, parseContentAdd, 
createContentAccept and parseContentAccept. Has anyone ever implemented 
those operations in javascript and can demonstrate running code?