Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?
Wolfgang Beck <wolfgang.beck01@googlemail.com> Fri, 21 October 2011 12:25 UTC
Return-Path: <wolfgang.beck01@googlemail.com>
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 48CEF21F8C5E for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 05:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 jeaKQxa+iHvp for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 05:25:34 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id D79A421F8C5C for <rtcweb@ietf.org>; Fri, 21 Oct 2011 05:25:33 -0700 (PDT)
Received: by qyk31 with SMTP id 31so3388793qyk.10 for <rtcweb@ietf.org>; Fri, 21 Oct 2011 05:25:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=5VwsWx6fcT1bjIeY4/Oc8hshKswoIPxB9VV5/APPcnM=; b=qgnCRdPJX9vzZDCoG21HfClbQifP4dZFnm2r91puLVsefSLRESeSPxdjU4rEewHvd1 mc0RzeL5WwomvXkPUnMjB38uzlKG7BWbveH4L7mtIeE8aLIRK6n6BreVoGj45B6eXnKt WLcuGwrS4T+2vIyvAFV5qVscFWMtaE9crEwok=
MIME-Version: 1.0
Received: by 10.68.39.231 with SMTP id s7mr27716876pbk.33.1319199932985; Fri, 21 Oct 2011 05:25:32 -0700 (PDT)
Received: by 10.68.55.230 with HTTP; Fri, 21 Oct 2011 05:25:32 -0700 (PDT)
In-Reply-To: <2E239D6FCD033C4BAF15F386A979BF51159B91@sonusinmail02.sonusnet.com>
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org> <2E239D6FCD033C4BAF15F386A979BF51159B91@sonusinmail02.sonusnet.com>
Date: Fri, 21 Oct 2011 14:25:32 +0200
Message-ID: <CAAJUQMjHOJxCUGTwON9PmK-QEN0jM++RTWuRpmsHS-eszcNkXQ@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: Ravindran Parthasarathi <pravindran@sonusnet.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?
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: Fri, 21 Oct 2011 12:25:35 -0000
Comments inline On Fri, Oct 21, 2011 at 1:47 PM, Ravindran Parthasarathi <pravindran@sonusnet.com> wrote: > ... > Please note that SIP is not designed in legacy > telephony (PSTN/SS7) architecture fashion (by ITU) but designed based on > Internet model wherein UA(endpoint) is intelligent. ..but we still introduced the BYE request and stateful proxies for forking. Both functions could have been done in the UA.. > After 10 years, now we are interested in real-time communication using HTTP only. No, not at all. We're interested in UAs that are programmable on the fly -- like a web browser with javascript --, so that we don't have to specify a protocol between client and server. Jonathan Rosenberg did an enlightening presentation at one of the past plenaries. When do we need a standardized protocol? We need one if two parties on the same network layer were implemented by different vendors. This is true for RTP (at least if we stick to the P2P media dogma). Browsers of different vendors must interoperate. It might be true for SDP's functionality. If we implement it deep in the browser, it must be standardized. The problem with SDP is, that it relies on some other protocol for transport and has some very specific requirements on that protocol. If we can make sure that all parties involved in a call use the same JS client, we can get away without standardization. At the layer of call signaling messages are ultimately exchanged between two JS clients running on browsers. If we have different JS clients here, we need a standardized protocol between them. With trapezoid interconnection, we can hide this to some extent by doing protocol translations between JS client A / RTCWEB Server A and Server B / JS client B. Some information will get lost in translation. But as browsers can load JS on the fly, user A could simply point her browser to Server B and use the same client as user B. Now all components at the signaling layer are provided by a single vendor and no standardized protocol is required. There is no loss of information as there are no protocol translators. Wolfgang Beck
- Re: [rtcweb] A plea for simplicity, marketability… Bernard Aboba
- Re: [rtcweb] A plea for simplicity, marketability… Saúl Ibarra Corretgé
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Saúl Ibarra Corretgé
- [rtcweb] A plea for simplicity, marketability - a… Dan York
- Re: [rtcweb] A plea for simplicity, marketability… Harald Alvestrand
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Wolfgang Beck
- Re: [rtcweb] A plea for simplicity, marketability… Aaron Clauson
- Re: [rtcweb] A plea for simplicity, marketability… Cullen Jennings
- Re: [rtcweb] A plea for simplicity, marketability… Cullen Jennings
- Re: [rtcweb] A plea for simplicity, marketability… Bernard Aboba
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Olle E. Johansson
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] Single-origin and consent Bernard Aboba
- Re: [rtcweb] A plea for simplicity, marketability… Roman Shpount
- Re: [rtcweb] A plea for simplicity, marketability… Roman Shpount
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Olle E. Johansson
- Re: [rtcweb] A plea for simplicity, marketability… Eric Rescorla
- Re: [rtcweb] A plea for simplicity, marketability… Roman Shpount
- Re: [rtcweb] A plea for simplicity, marketability… Eric Rescorla
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Bernard Aboba
- [rtcweb] Single-origin and consent Randell Jesup
- Re: [rtcweb] Single-origin and consent Harald Alvestrand
- Re: [rtcweb] A plea for simplicity, marketability… Ravindran Parthasarathi
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Wolfgang Beck
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Randell Jesup
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Matthew Kaufman
- Re: [rtcweb] A plea for simplicity, marketability… Harald Alvestrand
- Re: [rtcweb] A plea for simplicity, marketability… Wolfgang Beck
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Wolfgang Beck
- Re: [rtcweb] A plea for simplicity, marketability… Iñaki Baz Castillo
- Re: [rtcweb] A plea for simplicity, marketability… Wolfgang Beck