Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]

Cullen Jennings <fluffy@cisco.com> Tue, 04 October 2011 22:53 UTC

Return-Path: <fluffy@cisco.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 C14A921F8D43 for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 15:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.027
X-Spam-Level:
X-Spam-Status: No, score=-103.027 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Ifcaoe1DTZiF for <rtcweb@ietfa.amsl.com>; Tue, 4 Oct 2011 15:53:13 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 0654F21F8CBB for <rtcweb@ietf.org>; Tue, 4 Oct 2011 15:53:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1259; q=dns/txt; s=iport; t=1317768979; x=1318978579; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=y3E5DStYe1HUPoNQ8CUSSYVm6//+1auHZXdtsQ53w8A=; b=AkFmgKS1iL1Z3RPGpf1nDFDdy4TU7HfGXaXFEuqCLMb8mgG0WLkMV5oa SwRWS6PUhy7Oxgz8IpLf0n6/qc4ODbvXMGCgmfdIyXd3o6oyPJkA8EVh/ qBhkjTQQ3mnc5ANKgj0JTYJnEHVRFLntcmmI2aSQxy2EVy0QIe9OzNEmI 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAMmNi06rRDoJ/2dsb2JhbABCpleBNIEFgVMBAQEBAxIBJz8QCzsLVwY1oToBnWyGQmEEh3iLboUnjDo
X-IronPort-AV: E=Sophos;i="4.68,487,1312156800"; d="scan'208";a="5947442"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 04 Oct 2011 22:56:19 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p94MuI8o010149; Tue, 4 Oct 2011 22:56:18 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <BLU152-W476B3866CE31803056E3C93FB0@phx.gbl>
Date: Tue, 4 Oct 2011 16:56:18 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE47482D-C51A-4872-8868-9AF8D0E6CAB2@cisco.com>
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com>, <2E239D6FCD033C4BAF15F386A979BF510F0C0A@sonusinmail02.sonusnet.com>, <05CAC192-E462-421F-B1E5-B78DC8F60306@ag-projects.com>, <2E239D6FCD033C4BAF15F386A979BF510F0C93@sonusinmail02.sonusnet.com>, <16880306-5B3A-4EFD-ADE4-1201138D9182@acmepacket.com>, <2E239D6FCD033C4BAF15F386A979BF510F137B@sonusinmail02.sonusnet.com>, <226C9800-9791-465A-B519-40935E2D135F@phonefromhere.com>, <4E8B1B86.2080805@jesup.org> <BLU152-W476B3866CE31803056E3C93FB0@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]
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: Tue, 04 Oct 2011 22:53:13 -0000

On Oct 4, 2011, at 12:19 PM, Bernard Aboba wrote:

> [BA]  I think this is the main point.   If we finish RTCWEB 1.0 expeditiously, this will in all likelihood
> spawn a number of browser-independent signaling libraries, as well as developing a wealth of experience
> with the limitations of RFCWEB 1.0, to inform future efforts. 
> 
> The alternative is to "load up the camel" until it collapses under the weight of (largely irrelevant) use
> cases.  Since the realtime web has been around for over a decade, we have a pretty good idea of what
> native realtime capabilities would be used for -- and PSTN connectivity has never been high on the list.

So uh, you are right we have a lot of experience with real time communications on the internet. Things that come to mind over the last ten years include Microsoft Voice.NET, Vonage, Dialpad, Telio, CBeyond, Skype, Yahoo Messenger, Fring, Google Voice, Webex. That's not a systematic sample but just some random things that came to my mind. Oddly, they all seem to connect with the PSTN. What are the things you are thinking of that decided that PSTN connectivity was not high on the list? Perhaps we can look at which ones ended up being successful.