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

Matthew Kaufman <matthew@matthew.at> Thu, 04 July 2013 15:03 UTC

Return-Path: <matthew@matthew.at>
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 4E1D311E8134 for <rtcweb@ietfa.amsl.com>; Thu, 4 Jul 2013 08:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.034
X-Spam-Level:
X-Spam-Status: No, score=-0.034 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, MIME_QP_LONG_LINE=1.396]
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 5-6MH6Bb9JDN for <rtcweb@ietfa.amsl.com>; Thu, 4 Jul 2013 08:03:54 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E43711E812A for <rtcweb@ietf.org>; Thu, 4 Jul 2013 08:03:54 -0700 (PDT)
Received: from [10.10.155.233] (unknown [10.10.155.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by where.matthew.at (Postfix) with ESMTP id 4ACD8250041; Thu, 4 Jul 2013 08:03:47 -0700 (PDT)
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>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51D53C07.6040402@oracle.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <42509D1B-2807-4611-BA25-416DE0C25EB9@matthew.at>
X-Mailer: iPhone Mail (10B146)
From: Matthew Kaufman <matthew@matthew.at>
Date: Thu, 4 Jul 2013 08:03:45 -0700
To: Binod <binod.pg@oracle.com>
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 15:03:58 -0000

You will still be required to wrestle the browser's offer-answer state machine into submission to get the results you want.

Matthew Kaufman

(Sent from my iPhone)

On Jul 4, 2013, at 2:10 AM, Binod <binod.pg@oracle.com>; wrote:

> 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.
>> 
>> 
>> 
>> --
>> Iñaki Baz Castillo
>> <ibc@aliax.net>;
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb