Re: [rtcweb] realiable data service

Tim Panton <tim@phonefromhere.com> Mon, 18 July 2011 09:28 UTC

Return-Path: <tim@phonefromhere.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 4C7C721F87BC for <rtcweb@ietfa.amsl.com>; Mon, 18 Jul 2011 02:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W0-LhgHFk2yv for <rtcweb@ietfa.amsl.com>; Mon, 18 Jul 2011 02:28:47 -0700 (PDT)
Received: from zimbra.westhawk.co.uk (zimbra.westhawk.co.uk [192.67.4.167]) by ietfa.amsl.com (Postfix) with ESMTP id 1D6DD21F8B9A for <rtcweb@ietf.org>; Mon, 18 Jul 2011 02:28:47 -0700 (PDT)
Received: from [192.168.0.14] (unknown [93.89.81.113]) by zimbra.westhawk.co.uk (Postfix) with ESMTP id 516F837A902; Mon, 18 Jul 2011 10:38:35 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <CAHp8n2md2P7_9MR-6TURVTKG6Ng-+1iq3P+Pdxu+wzQTfyz7VQ@mail.gmail.com>
Date: Mon, 18 Jul 2011 10:28:45 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <930E44D5-D72A-4F60-B28B-9DD8F3B49BAC@phonefromhere.com>
References: <4E0832FE.7010401@ericsson.com> <4E1DC07B.7000807@ericsson.com> <D1BE71E1-4F3B-474E-8A28-AA53CE6B684E@cisco.com> <CAMKM2LzpVcS9jjXjfffuXy+YQmjZXbdaSJBp+O22nLd4N2KAvg@mail.gmail.com> <CAHp8n2md2P7_9MR-6TURVTKG6Ng-+1iq3P+Pdxu+wzQTfyz7VQ@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] realiable data service
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, 18 Jul 2011 09:28:51 -0000

I understand the pushback on supporting  reliable datagrams from Cullen, Silvia, Serge and others.

I'm pushing for it simply because I've had it in our browser rt-audio component, and used it extensively.
Without the ability to transport reliable datagrams in 'near realtime' the projects 
we have done would have been far less compelling for the user. The Datagrams are often the 
key to providing a special user experience, beyond conventional telephony. If we don't provide this,
we risk producing the tools for a round of  browser based deskphone emulators. We can do better.

As an example, the demo I show in this blog would have been much harder and less responsive without
realtime data coming back up the RFC 5456 channel :

https://babyis60.wordpress.com/2009/10/24/my-astricon-googlewave-ibook-skype-demo/

So I guess I am asking: Are we aiming for  browser based deskphone emulators or a new sort of
rich media experience for browser users? 

I know what I want.

Tim.