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

Robin Raymond <robin@hookflash.com> Thu, 04 July 2013 11:33 UTC

Return-Path: <robin@hookflash.com>
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 3C3AA21F9EB3 for <rtcweb@ietfa.amsl.com>; Thu, 4 Jul 2013 04:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[AWL=-0.289, BAYES_00=-2.599, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 7AOEraLyF1yE for <rtcweb@ietfa.amsl.com>; Thu, 4 Jul 2013 04:32:55 -0700 (PDT)
Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1DF7A21F9E79 for <rtcweb@ietf.org>; Thu, 4 Jul 2013 04:32:55 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id s9so3020576iec.27 for <rtcweb@ietf.org>; Thu, 04 Jul 2013 04:32:54 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=lhjjkgnHPe0iGZp7bJ9gg1eN4G3ehCGWm2xDEvnSZtU=; b=jrxlLFxCaIPuTeO1Sh5IfBluFqVKPx9pd7ht+wHcY5910crFyXixd/RjyZQKdAIhKp oUhSjVwWhLsg55D6R8Px68UQGEUCx5lKiKtpl2riZ7TqERGklxs73PPDvl9AKz+mb940 ioD/gCnYeUWgknFeCp5TrZs8C72nL9Ziqfgi+L+6BqNC2BwGw5E19nsB6hvd2wPjGyoi xWnYS2ik536fn86k4xbCMYOso0lkCEhxittoCXb/cQhgoVKLAruE7pwpBzcJkcJBVKIt p8xQCb6dHSy9vr0AfebirPJAPKs77AHqjbepfn7GPYeDUiBYSRfrAHpMoiO2hBLbD+jt 9onQ==
X-Received: by 10.50.3.42 with SMTP id 10mr26633244igz.39.1372937573998; Thu, 04 Jul 2013 04:32:53 -0700 (PDT)
Received: from Robins-MacBook-Pro.local (CPE602ad08742f7-CM602ad08742f4.cpe.net.cable.rogers.com. [99.224.116.224]) by mx.google.com with ESMTPSA id vc13sm1546103igb.1.2013.07.04.04.32.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Jul 2013 04:32:53 -0700 (PDT)
Message-ID: <51D55D62.7090608@hookflash.com>
Date: Thu, 04 Jul 2013 07:32:50 -0400
From: Robin Raymond <robin@hookflash.com>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Binod <binod.pg@oracle.com>
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> <CALiegfk9nqabnnF8tA5Qwg4_XUKB80sMpA59vm_2v3p4k3VOUg@mail.gmail.com> <CABcZeBN-pEN9jK36aN0kkMX9M82tpJr3B6+TQa4ihJgAJW6vKQ@mail.gmail.com> <CABcZeBMxF6UbeXbLLVBiTEhR0mAWL-HgDn7Ra=eiuQ1kUsrFCg@mail.gmail.com> <CALiegfk4QjOTeG2qQqdENg2QpkYUPbVV7VO9-1bhBv6Pd6tANg@mail.gmail.com> <51D53C07.6040402@oracle.com>
In-Reply-To: <51D53C07.6040402@oracle.com>
Content-Type: multipart/alternative; boundary="------------030309080505080209080703"
X-Gm-Message-State: ALoCoQlR7YnpsIjDjdc6MmGqMAQR9v9YTf8pixMxHONLsb+GxohXwE9W13SiI4aZ8aPoazIbNwGD
Cc: 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 11:33:00 -0000

+1 on object model with a "toSDP / fromSDP"  (FYI - an object model 
draft is looming shortly)

I think it's best to put "toSDP / fromSDP" outside the browser binary as 
a common github JS library because I know a lot of SIP folks love custom 
SDP extensions and being able to fork/tweak the SDP without petitioning 
the browser vendors for an "update" is important.

-Robin

> Binod <mailto:binod.pg@oracle.com>
> 4 July, 2013 5:10 AM
> On Thursday 04 July 2013 01:51 PM, Iñaki Baz Castillo wrote:
>> 2013/7/4 Eric Rescorla <ekr@rtfm.com>;:
>>> Looking back at your posts from back then, I see you did in fact 
>>> suggest
>>> a set of API modifications that would have included an abstract session
>>> description. That would in fact have made Jingle somewhat (though not
>>> really that much) easier. So my last sentence here is unfair. My 
>>> apologies.
>> Initially I though that SessionDescription was a powerful JS Object
>> with all the fields and attributes to construct a SDP, so a developer
>> could extract those media/transport fields and create a SDP via JS. At
>> the same time, the SessionDescription object would include helper
>> methods (defined by the WebRTC API) to build a plain SDP (i.e. toSDP)
>> and some others like XML-SDP (i.e. toXMLSDP).
> I like that approach. Have an API to specify all/most of what is
> in the SDP and then use a toSDP to generate actual SDP string to be sent
> across the wire.
>
> Other side should be able to reconstruct the browser side
> object(s) using the received SDP string.
>
> thanks,
> Binod.