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

Neil Stratford <neils@belltower.co.uk> Wed, 09 November 2011 13:42 UTC

Return-Path: <neils@vipadia.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 CCCB521F8B79 for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 05:42:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level:
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 qFw5WbHVNMUw for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 05:42:49 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8CC21F8B76 for <rtcweb@ietf.org>; Wed, 9 Nov 2011 05:42:49 -0800 (PST)
Received: by iaeo4 with SMTP id o4so2254496iae.31 for <rtcweb@ietf.org>; Wed, 09 Nov 2011 05:42:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.20.201 with SMTP id g9mr571882ibb.57.1320846168584; Wed, 09 Nov 2011 05:42:48 -0800 (PST)
Sender: neils@vipadia.com
Received: by 10.231.207.10 with HTTP; Wed, 9 Nov 2011 05:42:48 -0800 (PST)
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE22186AAFD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <8A61D801-D14D-408B-9875-63C37D0CC166@acmepacket.com> <CABw3bnPE=OY_h5bM7GA6wgrXiOBL8P4J0kw1jLv-GSpHAbg=Cg@mail.gmail.com> <CABcZeBNqdkh8u=gwOvKfDCQA7rXdAyQkfaM1r2Sx10787btP6A@mail.gmail.com> <B10FEFF6-0ADC-4DB1-83BB-50A11C65EC35@acmepacket.com> <CABcZeBNSXtim_VqzqAd8Z-u4zWSjaYmsVZPN=7sDYkJsgtRAHA@mail.gmail.com> <4EB7E6A5.70209@alvestrand.no> <F8003BA9-BCD8-4F02-B514-8B883FF90F91@acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01349D81@inba-mail01.sonusnet.com> <845C03B2-1975-4145-8F52-8CEC9E360AF3@edvina.net> <5454E693-5C34-4C77-BA07-2A9EE9EE4AFD@cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01349FFE@inba-mail01.sonusnet.com> <1D062974A4845E4D8A343C653804920206D3B7FD@XMB-BGL-414.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C0134A105@inba-mail01.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09804691DA2@HKGMBOXPRD22.polycom.com> <CALiegfmf59jb4asUu9LA6YY_aMtKEnM1Wy34KbuLEn3_h1xBXA@mail.gmail.com> <1D062974A4845E4D8A343C653804920206D3B9C1@XMB-BGL-414.cisco.com> <CALiegfmM1PB=VAQjfh4rW3-3C8aumHdWy9nZxD0-BWBq9Kq_tg@mail.gmail.com> <CABRok6nha3Ut5A1c1k=WUYxrn6kxDD=P2no6EFaf4=Uzdbbpwg@mail.gmail.com> <EDC0A1AE77C57744B664A310A0B23AE22186AAFD@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Wed, 9 Nov 2011 13:42:48 +0000
X-Google-Sender-Auth: qBvHkwX_DPJrCA4MAXoF8jSD-o8
Message-ID: <CABRok6mbEBuKEq5rFOsEXn=J4H3jrgpqFeTwNTcxLj_Pbm0tjg@mail.gmail.com>
From: Neil Stratford <neils@belltower.co.uk>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=0015175ce0d8ae71d504b14d769f
Cc: "rtcweb@ietf.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: Wed, 09 Nov 2011 13:42:49 -0000

On Wed, Nov 9, 2011 at 1:04 PM, DRAGE, Keith (Keith) <
keith.drage@alcatel-lucent.com> wrote:

>  If you want to be in the world of telecommunications you carry a legacy
> baggage.
>

Only at the point you want to interop with that legacy world. Skype did a
pretty good job of avoiding the legacy and changing users expectations of
telecommunications.

Your proposal to provide a gateway is just one way of dealing with the
> legacy baggage. It does however carry the downside that you need a player
> to provide such gateways in support of interworking to the legacy.****
>
> ** **
>
> Suppose I make an emergency call to a PSAP. The legacy baggage here is
> that unless someone volunteers to provide all those PSAPs worldwide with
> new kit, the majority will remain connected to the PSTN (i.e. not even
> SIP). I need a guarantee that someone out there will provide a gateway.
> Which player provides that in your business model.
>

If there is a market for interop (which there clearly is) then multiple
vendors will no doubt offer gateways. I'm just concerned that we are
talking about imposing legacy requirements on the core API, when WebRTC
seems an ideal opportunity to break away from that legacy.

Neil