Re: [rtcweb] New Draft - WebRTC JS Object API Model

Iñaki Baz Castillo <ibc@aliax.net> Mon, 01 July 2013 16:06 UTC

Return-Path: <ibc@aliax.net>
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 A9C3421F9C88 for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 09:06:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.577
X-Spam-Level:
X-Spam-Status: No, score=-2.577 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 kxn9v-+lTiur for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 09:06:43 -0700 (PDT)
Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by ietfa.amsl.com (Postfix) with ESMTP id C330011E82A8 for <rtcweb@ietf.org>; Mon, 1 Jul 2013 09:06:17 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id ci6so2171012qab.18 for <rtcweb@ietf.org>; Mon, 01 Jul 2013 09:06:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=jP0YsSWzxJi19mcYY3vA6V1kG4kVn1pxXk2CUME8G+Q=; b=LDafrU58IBCmFwt4RD7X0X9mnOa8mjrqkKeR3ZrLosVFZyIj+OlBKcO3Uw39eIbb0K IFX4i3jszHWt/0ufYgrNUtk2DSObLl7cMp/8SeTnS1PKk4GtFVpIWyYxt3HgrViiB31v kfSWyOjFA4pdOA+lFtnyPBMewmv+kBVJDh3ni/TW2WVWEys4v9e+LPyMM4YX3l0u/ANI kdKNjvdJPhFjH5kkh0YExG8HthtffXv5WdWvvW+67pk3HNMSDmKNWTM3pxa0538bWQ4m 1yFnyT9K9oamgAEPE4dEVqwF4G1HlWqsXdswjpIObvCOLlYgwRhkJ2glAOQwyJW9HXJ6 4wpw==
X-Received: by 10.224.92.79 with SMTP id q15mr14720964qam.104.1372694772361; Mon, 01 Jul 2013 09:06:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Mon, 1 Jul 2013 09:05:52 -0700 (PDT)
In-Reply-To: <CA+9kkMC5FoxKSz7DuHxN8cEO=0PDpoAGrLshpFmnDe3gco06cw@mail.gmail.com>
References: <51CA6FEE.6030702@hookflash.com> <1447FA0C20ED5147A1AA0EF02890A64B1C3093E0@ESESSMB209.ericsson.se> <CALiegfmsahUM6w00thQSCu3CpKse2C3LKSb1LzkwodNgKTOK0g@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C309655@ESESSMB209.ericsson.se> <CALiegfnAN9SJx0nLyegFJoQscG-18Gs4umd-pe7S3y6xREpByQ@mail.gmail.com> <CA+9kkMC5FoxKSz7DuHxN8cEO=0PDpoAGrLshpFmnDe3gco06cw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 01 Jul 2013 18:05:52 +0200
Message-ID: <CALiegfnpj+nBdhn0g8A7iTdXKZdqvwyffjdLAOuM_qQkhTuKew@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmHZNL7o0V1psxFEypqPcnvw1O5Yop5eM1fdQ/s7wzByxM7/jrX8zRwf2/uBHJXCDF8y3XO
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] New Draft - WebRTC JS Object API Model
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: Mon, 01 Jul 2013 16:06:47 -0000

2013/7/1 Ted Hardie <ted.ietf@gmail.com>:
> On Mon, Jul 1, 2013 at 7:28 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:
>>
>> Stefan, the media/transport info will be sent from browser A to
>> browser B using the custom format the developer of the website chose,
>> period. I don't understand why you think that the format of the
>> media/transport info must be constant/fixed for any website using
>> WebRTC.
>
>
> Because ultimately the media is sent via transports set up by the browser.
> If the browser must understand every custom format, the system cannot scale.


Ted, the media can be *perfectly* sent in-the-wire with any custom
format the web developer builts (JSON, XML, plain SDP or whatever).
The receiver JS app parses the information (i.e. converts from JSON to
an Object), extracts the media/transport fields and pass them to the
PeerConnection via API methods.

It is really so hard? this is how WWW works (in contrast to how SIP works).

If it is possible, please take a look to
http://tools.ietf.org/html/draft-raymond-rtcweb-webrtc-js-obj-api-rationale-00.

Best regards.

--
Iñaki Baz Castillo
<ibc@aliax.net>