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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 01 July 2013 17:10 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 541BF11E8208 for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 10:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[AWL=0.075, 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 q3Dv+goT+81u for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 10:10:31 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB6911E8252 for <rtcweb@ietf.org>; Mon, 1 Jul 2013 10:10:31 -0700 (PDT)
Received: by mail-qa0-f51.google.com with SMTP id f11so2081785qae.17 for <rtcweb@ietf.org>; Mon, 01 Jul 2013 10:10:30 -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=wqOG7TlZSJQmBr7S5hRAYId7E55A/gh/I5ofL9ztADg=; b=oQgLqehh1AbNuEIWmwp9H0wiiIE2+vgDhiKpf54ibGrmyeyWRZIi9vETWgfv0MiZjb K1d1vOimRmBDQJxNPhLB6mXURrHayqH+vZ5L4XI01QYa2aSjoVeiWL8kGpg2+X4HPjS6 We9g6GidlTBKl7Yi2m6PSF3364xjra0B3VsDpJcv1QxVbZwiqb3aV7w9SizJak3aAk1C QZbdFWNIrRGPY/UefEV7t5oi3RhodAHInK+VYXdzsmusorfNtSHWu/HOuV6wh6qzdWIU pJfuoUlE1xRp+F2mR9Zps5Mhb/VhTN3KALwdsTyQYFA3eUHE4HE3CCt+l0iJiaSI6D37 Ksiw==
X-Received: by 10.49.117.195 with SMTP id kg3mr32966364qeb.68.1372698630741; Mon, 01 Jul 2013 10:10:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Mon, 1 Jul 2013 10:10:10 -0700 (PDT)
In-Reply-To: <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> <1447FA0C20ED5147A1AA0EF02890A64B1C309759@ESESSMB209.ericsson.se>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 1 Jul 2013 19:10:10 +0200
Message-ID: <CALiegfkqtuqZwJB9RHwsmbwTabc4-ug3dEi_SbzdYkeYu6ZWcA@mail.gmail.com>
To: =?UTF-8?Q?Stefan_H=C3=A5kansson_LK?= <stefan.lk.hakansson@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmFucEBZPxdr+o7q6x6vDoGqWWOITnFo3UQq3DgbAtHqem8XqdO8tcc0XmexrNFo7VZ3dIp
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:10:37 -0000

2013/7/1 Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>om>:


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

I meant "SDP". Of course the browser sends RTP. What I mean is that we
DO NOT need to play with a SDP blob to transmit media/transport info
between browsers and between JS and WebRTC API.


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

Sure. The point is that we don't need (and don't want) SDP since it
becomes a barrier for innovation. All the details in the draft:

  http://tools.ietf.org/html/draft-raymond-rtcweb-webrtc-js-obj-api-rationale-00.


Best regards.



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