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:12 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 C42B111E8103 for <rtcweb@ietfa.amsl.com>; Sat, 20 Jul 2013 07:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level:
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=0.053, 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 w0Slu2FIUS21 for <rtcweb@ietfa.amsl.com>; Sat, 20 Jul 2013 07:12:24 -0700 (PDT)
Received: from mail-qc0-f181.google.com (mail-qc0-f181.google.com [209.85.216.181]) by ietfa.amsl.com (Postfix) with ESMTP id 8E00311E810E for <rtcweb@ietf.org>; Sat, 20 Jul 2013 07:12:24 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id u12so2831341qcx.12 for <rtcweb@ietf.org>; Sat, 20 Jul 2013 07:12:24 -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=KFRU790ni1rlxq7XSRdfjCSghSseip6PTGYGHCf2s20=; b=O/8zL2B6wKBXjUOw6JojBmLAUr5SIXoYn4CVw7cxL1FVB/Rf8iTfRnxvh/Edd6VbWk TvAblnYmo4J1NIhp2hWSgKp6+85ZtZ4oHXGL+whDOyWtdnFO/zTZmginjsz46zj9XxO7 xr8Iw3bwluvjhJg8iTwBe/aWkTD452mEVx2i69876IxNbUHfi7/9m8HOuyX5o0KyQ0Fn QYg5cTxMxtKsaOmPKqSWG1V83I+e9j+PznnIhmNTwNJ2xh7En0cYOv9Jw0GRbCIjTKrM MfrlDmFFPmsemzU542GmO/R64rNsyFXb1qFp0wJBeOSWeollm2zHFu0X+Ny89/gWPFy9 qBrg==
X-Received: by 10.229.171.2 with SMTP id f2mr5278933qcz.24.1374329543992; Sat, 20 Jul 2013 07:12:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.72.132 with HTTP; Sat, 20 Jul 2013 07:12:03 -0700 (PDT)
In-Reply-To: <CALiegf=BPjQqd5cdagvm3ZsBYizxOmA8HfRF=n8pV5YkQzPU9Q@mail.gmail.com>
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> <CALiegf=BPjQqd5cdagvm3ZsBYizxOmA8HfRF=n8pV5YkQzPU9Q@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Sat, 20 Jul 2013 16:12:03 +0200
Message-ID: <CALiegfkLic4WMA9PDqPTDvGH7tDyO5mdpxwoaVct9rZmGrb1Ww@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: ALoCoQmVvnPSUfEXkNyN9L3m0yeutONhMqmgn+6z0y9FgZruI+verm+XrduSAL54QItyYsYaw5m7
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:12:29 -0000

2013/7/20 Iñaki Baz Castillo <ibc@aliax.net>;:
> 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.

Cullen, could you please give your opinion about what I've said above?
I also would like to know what happens if the video conference server
uses Jingle or any future RTC protocol (which uses RTP but no SDP for
media sig).

Thanks a lot.


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