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

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Mon, 01 July 2013 17:05 UTC

Return-Path: <stefan.lk.hakansson@ericsson.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 3B01311E81A8 for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 10:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.874
X-Spam-Level:
X-Spam-Status: No, score=-5.874 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 XKL4l8RRDpeG for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 10:05:25 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id A95BE11E81F7 for <rtcweb@ietf.org>; Mon, 1 Jul 2013 10:05:24 -0700 (PDT)
X-AuditID: c1b4fb25-b7f826d000001766-41-51d1b6cffe28
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 79.91.05990.FC6B1D15; Mon, 1 Jul 2013 19:05:19 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.6]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.02.0328.009; Mon, 1 Jul 2013 19:05:19 +0200
From: =?iso-8859-1?Q?Stefan_H=E5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Thread-Topic: [rtcweb] New Draft - WebRTC JS Object API Model
Thread-Index: AQHOcibV+w71mSCXSkiQxLiPakqfXQ==
Date: Mon, 1 Jul 2013 17:05:18 +0000
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1C309759@ESESSMB209.ericsson.se>
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> <CALiegfnpj+nBdhn0g8A7iTdXKZdqvwyffjdLAOuM_qQkhTuKew@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBLMWRmVeSWpSXmKPExsUyM+Jvre75bRcDDZo3SlhM32djsfZfO7tF 41w7B2aPcw3v2T12zrrL7rFkyU+mAOYoLpuU1JzMstQifbsErozTPzvYC+7zVWz8H9bA2MTT xcjJISFgIjG96wkThC0mceHeerYuRi4OIYHDjBKrbv9jhXAWMkqsvX4HrIpNIFBi674FbCC2 iIClxI25N5lBbGYBD4lpt5aygtjCAjYSfR8+A9VzANXYSmxrY4Uo15OY83klO4jNIqACZB8F G8Mr4CsxZ2kX1K4LzBJv/78Fm8kIdNH3U2uYIOaLS9x6Mh/qUgGJJXvOM0PYohIvH/9jhbAV JXaebYe6R0/ixtQpbBC2tsSyha+ZIZYJSpyc+YRlAqPoLCRjZyFpmYWkZRaSlgWMLKsY2XMT M3PSy402MQJj4+CW36o7GO+cEznEKM3BoiTOu1nvTKCQQHpiSWp2ampBalF8UWlOavEhRiYO TqkGxj37qyqf1TYxyf7f/+3QuesaK0MZ9zy/O+3/Phlrm+fKGtuYHcLk/SbvVrQOivT4Hxa0 s3gSW1v3Q5e6yOXt0YuzGzIuab2pufeL6xDbSzmP7c1uYkm95qkGasZy+04x85/6Ht2xeaWT 9y+phucnolfmbLm7/aVDoS1H6JTKd4ks/VImZVnsSizFGYmGWsxFxYkAb7pujFsCAAA=
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 17:05:30 -0000

On 2013-07-01 18:06, Iñaki Baz Castillo wrote:
> 2013/7/1 Ted Hardie <ted.ietf@gmail.com>om>:
>> 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).

I had the impression that we had consensus for using (S)RTP for the media.

> 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.

My point is that when the app passes the fields to the PeerConnection, 
it must be specified exactly what those fields mean (so that the RTP 
send by one browser can be used by another browser receiving it). And 
that requirement is the same regardless of if we use SDP generated and 
consumed by the browser to describe it or something else.

>
> 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>
>