Re: [rtcweb] We are moving beyond the assumptions on which O/A is based

Emil Ivov <emcho@jitsi.org> Sun, 12 May 2013 09:59 UTC

Return-Path: <emil@sip-communicator.org>
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 225A921F8E49 for <rtcweb@ietfa.amsl.com>; Sun, 12 May 2013 02:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level:
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599]
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 FZFZlbS+Sdjr for <rtcweb@ietfa.amsl.com>; Sun, 12 May 2013 02:59:02 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 52E7521F8DD5 for <rtcweb@ietf.org>; Sun, 12 May 2013 02:59:02 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id x12so5224173wgg.21 for <rtcweb@ietf.org>; Sun, 12 May 2013 02:59:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=spcMJ6czq/XoXifWLUW5x+p5FQBDUA2UL4JPZKzreFw=; b=OUWXH6PQWBGPGZEWtj0ln7X2cHQhmopB/PkMA8oE5Y4sXZ/r05FKx034YF60E/zF73 j+tB2jue6+He/Foo4Tq5cBsyldkg3Mi20bLmcodDOR6XO7RFnwTusZvn+SPs+6wCyHXB apSDD95qMya2NyWr7/IZGXl0J4EMXnAnoAMZqktysoIEADCYT5fHvww2wOv2BoPoitzT CdWT4B11LSX2ek2k5NNc3l2k2DxQ5wCw0XmZUBEz8Av4dazbvOG/Dzy4HeGxsEF9CXm1 D+M0pE9W3Es8Qs/Codf4C9qMXisTakRPeoQQMKz9kCx+x7wp9YpsKzuWDKTZKVbraCKv 5VTw==
X-Received: by 10.194.62.233 with SMTP id b9mr33564926wjs.37.1368352741344; Sun, 12 May 2013 02:59:01 -0700 (PDT)
Received: from camionet.local ([83.228.76.175]) by mx.google.com with ESMTPSA id x13sm9156601wib.3.2013.05.12.02.58.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 May 2013 02:59:00 -0700 (PDT)
Message-ID: <518F67E1.3040205@jitsi.org>
Date: Sun, 12 May 2013 12:58:57 +0300
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <20130503054601.4639.64651.idtracker@ietfa.amsl.com> <CALe60zAi_Lx3QFCbBQ5aPNkgorJAff0E79jkpbQX1Qt3wf2bzg@mail.gmail.com> <CAOJ7v-1Wk6u7XiYrNVmoqr5Jisu2WRvZpte7hQTOiP8YHUc6hg@mail.gmail.com> <518A1268.8090107@ericsson.com> <01AB1BF5-7ABF-4DD3-A831-3A6C96EA680C@iii.ca> <1447FA0C20ED5147A1AA0EF02890A64B1C2C818F@ESESSMB209.ericsson.se> <518E7700.1080906@alum.mit.edu>
In-Reply-To: <518E7700.1080906@alum.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnDLsP9dapFAPSGPOCbLCJBdyEafNb7LaxutylShLBvirDDyXlxGCVNZpzO7g1pKRyp/Vhn
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] We are moving beyond the assumptions on which O/A is based
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: Sun, 12 May 2013 09:59:03 -0000

On 11.05.13, 19:51, Paul Kyzivat wrote:
> I don't have a specific action to recommend here. This just seems like a 
> somewhat fundamental shift that out to be recognized. It probably isn't 
> just RTCWEB and CLUE, it is really related to more complex communication 
> scenarios. ISTM that CLUE is addressing this by building a layer on top 
> of O/A, while RTCWEB is *battling* with O/A.

That's a nice way to put it. Interestingly the CLUE approach to take
this out of O/A seems to be more in line with the RTCWEB paradigm than
both Plan A or Plan B.

The decision not to implement an official signalling RTCWEB protocol was
taken very early in this working group and there was very strong
consensus on the fact that imposing a specific signalling protocol would
be incompatible with the web in general.

Still, it seems to me that we are now trying to compensate for the  lack
of such a signalling protocol by piggybacking on top of O/A and SDP with
things such as the possibility to turn off individual SSRCs.

Why do we need these things? Aren't they better handled by the API?

Emil

-- 
https://jitsi.org