Re: [rtcweb] Let's define the purpose of WebRTC

Iñaki Baz Castillo <ibc@aliax.net> Mon, 07 November 2011 15:50 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 A1A9C21F8C04 for <rtcweb@ietfa.amsl.com>; Mon, 7 Nov 2011 07:50:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level:
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=0.041, 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 eTRitm530qb3 for <rtcweb@ietfa.amsl.com>; Mon, 7 Nov 2011 07:50:40 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0368021F8BF3 for <rtcweb@ietf.org>; Mon, 7 Nov 2011 07:50:39 -0800 (PST)
Received: by vcbfl11 with SMTP id fl11so4604372vcb.31 for <rtcweb@ietf.org>; Mon, 07 Nov 2011 07:50:39 -0800 (PST)
Received: by 10.220.199.2 with SMTP id eq2mr2029626vcb.103.1320681039090; Mon, 07 Nov 2011 07:50:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.107.206 with HTTP; Mon, 7 Nov 2011 07:50:18 -0800 (PST)
In-Reply-To: <CAAJUQMihjTRgpO8hjgiYz5iLbWTncdXFO8nnRE9VDRND36-b2w@mail.gmail.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <CAD5OKxt=k_Mon_GMs1w-bGMgpk12h6ZQ=FkoRVsTp4271iMSLA@mail.gmail.com> <CABcZeBNMTgwH-R_jd-AiEJ8tELTeFMNm-bAJohRg2RxD5e+kZQ@mail.gmail.com> <CAD6AjGRBmrAqB3CEWxtaXnryPA5App13S2jJPAt+7HwWZsQFzA@mail.gmail.com> <CABcZeBNtoizuRymVMxF4CdiLu1Nju63C0xkWJHjoarpxeLXjyA@mail.gmail.com> <CALiegfk=oJJ20GhKQBKA7aspHhUyQ-s+DR-qSi4XV455Nj718w@mail.gmail.com> <9C4C8AE2-4AFF-4553-9D19-556F12AC066E@phonefromhere.com> <9B907E0E-7FE7-4302-BDFA-CEEC12734B8C@edvina.net> <7BF02133-2A7E-48ED-982F-90B7868F9FB9@phonefromhere.com> <4EB74D06.8000006@jesup.org> <CAAJUQMihjTRgpO8hjgiYz5iLbWTncdXFO8nnRE9VDRND36-b2w@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Mon, 7 Nov 2011 16:50:18 +0100
Message-ID: <CALiegfmhst-2anmO1HMO1MVp=GFEjqOoG50wVKKMQic3AjxUsA@mail.gmail.com>
To: Wolfgang Beck <wolfgang.beck01@googlemail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
Subject: Re: [rtcweb] Let's define the purpose of WebRTC
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, 07 Nov 2011 15:50:42 -0000

2011/11/7 Wolfgang Beck <wolfgang.beck01@googlemail.com>om>:
>> For example, you mention forking and glare.  Well, I've given very
>> non-interop cases of where forking would be useful: contacting someone who
>> has 2 desktops, a notebook, a tablet, and a phone all logged into the
>> service, or some of the game scenarios, or a very non-standard-SIP-like mesh
>> conference using forked invites.

> Do you really need forking to achieve this? Couldn't you just return
> references to those devices back to the caller
> which can then decide how to call them? A redirect server instead of a
> forking proxy?

That's a limitation rather than a simplification, and would make lot
of scenarios just harder. Don't think just in SIP. Any future *pure*
WebRTC scenario could desire to fork a call into multiple N
destinations without making the *JavaScript* client code to deal with
N different sessions.


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