Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)

Iñaki Baz Castillo <ibc@aliax.net> Sat, 20 July 2013 14:04 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 B3C6621F9655 for <rtcweb@ietfa.amsl.com>; Sat, 20 Jul 2013 07:04:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.623
X-Spam-Level:
X-Spam-Status: No, score=-2.623 tagged_above=-999 required=5 tests=[AWL=0.054, 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 et+evFYosV0B for <rtcweb@ietfa.amsl.com>; Sat, 20 Jul 2013 07:04:19 -0700 (PDT)
Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by ietfa.amsl.com (Postfix) with ESMTP id EDA3021F9C2D for <rtcweb@ietf.org>; Sat, 20 Jul 2013 07:04:16 -0700 (PDT)
Received: by mail-qe0-f44.google.com with SMTP id 5so2958223qeb.31 for <rtcweb@ietf.org>; Sat, 20 Jul 2013 07:04:16 -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=YL0L+RmRwPnZkRxgEyMmBuj7dfH1gRX4CUkfFCnsHb0=; b=JGQpz4x5fZg3Z6OaoFQkIw0DNloDUBK8aTGogcXwwb3GUPuJsaH+p/GtQHGOU36c9d uvdBOVvXlpdmoKUw7AE2cEnbVyhsxHXPIL/Qqv6sdp1n8ptskEXFjU4jZvJck5KFugq6 0mOuIqw4Du1aMhErrHlkSbF0THYzfbeoi3F0kH64fEhrwW3BvlHzFjfKefK85mf0VO2T NaiPLybWNGA+yeAAbUBnCp1fVFKq2wZkrIFB90pBl3/G12tMuvxdE1dPi5B2Pt3gIJrc 5WBwXh+ejeQErwUaAQePLAjjrs0y/ZRuwd+lPpFpiYVqf2nggpfrO+7r+R9Njsy9B4y8 Jp3g==
X-Received: by 10.49.84.164 with SMTP id a4mr22954896qez.4.1374329056375; Sat, 20 Jul 2013 07:04:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.72.132 with HTTP; Sat, 20 Jul 2013 07:03:56 -0700 (PDT)
In-Reply-To: <644AB0EE-8889-4940-BA88-33EA653D44DC@iii.ca>
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> <1447FA0C20ED5147A1AA0EF02890A64B1C30BC0F@ESESSMB209.ericsson.se> <CAD5OKxtKLMf_d=8GSMrqfNhDHPe9MFP2ZTKzZHFn9CyMr-gSVQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30C833@ESESSMB209.ericsson.se> <CAD5OKxvGfkgRp6tXwbOu_kVteHiBBqsyR5ixH18FMKjCNGO8VQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30CD1E@ESESSMB209.ericsson.se> <BLU401-EAS386F88B3FE140492B39B59693610@phx.gbl> <AE1A6B5FD507DC4FB3C5166F3A05A484213E41E7@TK5EX14MBXC265.redmond.corp.microsoft.com> <C50FDAD5-492C-4A83-AD6D-464242FB4A05@iii.ca> <CALiegfneUj=kzDjR_E1=S-bqAajaPUE3f_A2g8oGriFyPhamPA@mail.gmail.com> <51E96B5B.2050302@nostrum.com> <CABkgnnXa-eTzRHcLMnHam4c+1D9kkvRwi9=V-9P43+p+pKE_sw@mail.gmail.com> <644AB0EE-8889-4940-BA88-33EA653D44DC@iii.ca>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Sat, 20 Jul 2013 16:03:56 +0200
Message-ID: <CALiegf=BPjQqd5cdagvm3ZsBYizxOmA8HfRF=n8pV5YkQzPU9Q@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmKyu1YYbOPyhlnWomltdBMV/4aWVVjyRpRun+TPX612RZj88UMZHpjlaLu5ncgNHqrVmFi
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>, "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] On babies and bathwater (was Re: 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: Sat, 20 Jul 2013 14:04:24 -0000

2013/7/20 Cullen Jennings <fluffy@iii.ca>;:
> It's not true when a browser from one vendor running an application from a scone vendor needs to talk to video conferencing system from a third vendor.

In the WWW, the servide provider provides both the server side (in
this case the Web and the video conference server) and the client side
(the JS). Your concern is good for a SIP phone but not for a browser
nor for a JS custom application controlled and designed by the
provider.


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