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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 01 July 2013 14:28 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 17F8621F9ED9 for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 07:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level:
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.150, 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 4086uHVxg2qx for <rtcweb@ietfa.amsl.com>; Mon, 1 Jul 2013 07:28:37 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6610B11E80E7 for <rtcweb@ietf.org>; Mon, 1 Jul 2013 07:28:37 -0700 (PDT)
Received: by mail-qa0-f49.google.com with SMTP id hu16so2075330qab.8 for <rtcweb@ietf.org>; Mon, 01 Jul 2013 07:28:35 -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=lAfKtoD61d8crE5w8vnEguDZDClUxkPKz6SVnWxVOBw=; b=OSpgvN/2SpyIxFFrLD9W1bFSJsDF5wMDVLNBiSH6s4OJS8O84s9Aq5O9lHjDzGInub QQ1oUFAjpXxu+xRhLBbxU/86v9oMcXeYoKG/rLlQDcnD632bdh56O+rusMSbeICHLy0n +tWavbIQCZ9VxbVl4hd0obS0IS80IfO4kbzkDHJV0/ATdQBU433mCQOYmZ6iAHmt8Y4p OKHOCz9ZsfLCQ+KKLGAzsRTmB8mZCg7jijwzZ/BlGtHQJAuKboH2SVWoGBmoGq86k7x5 77G9v2xWrrzM5MKrccqRUb+oKBfJhTetajzgckfhoZ4uBhQnM/qs7Uma0xWT0a8/dEGp H8ew==
X-Received: by 10.224.92.79 with SMTP id q15mr14109842qam.104.1372688915797; Mon, 01 Jul 2013 07:28:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Mon, 1 Jul 2013 07:28:15 -0700 (PDT)
In-Reply-To: <1447FA0C20ED5147A1AA0EF02890A64B1C309655@ESESSMB209.ericsson.se>
References: <51CA6FEE.6030702@hookflash.com> <1447FA0C20ED5147A1AA0EF02890A64B1C3093E0@ESESSMB209.ericsson.se> <CALiegfmsahUM6w00thQSCu3CpKse2C3LKSb1LzkwodNgKTOK0g@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C309655@ESESSMB209.ericsson.se>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 1 Jul 2013 16:28:15 +0200
Message-ID: <CALiegfnAN9SJx0nLyegFJoQscG-18Gs4umd-pe7S3y6xREpByQ@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: ALoCoQmkwupGBfK7pt0QDhZFp/zdvu77a3H1r3uZVoAqoyCF/Q1k29Izewsj8Ux1yrJqadOKbAzt
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 14:28:44 -0000

2013/7/1 Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>om>:
>> The draft explains (in section 5) why it is not needed to mandate how
>> media info must be sent in the wire. Instead, let the developer to
>> retrieve the media/transport information from the API and send it in
>> the wire in the way it wants.
>
> I still think my point is valid. If the app i browser A retrieves this
> media/transport info using the API, and sends it to the peer app in
> another browser B, it must still mean the same for both browsers.
>
> True, we're struggling with this part for SDP. But removing it and only
> have API calls does not get us away from defining exactly what those
> calls mean.


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. It makes no sense IMHO. That is up to the website developer.


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