Re: [rtcweb] realiable data service

Tim Panton <tim@phonefromhere.com> Mon, 18 July 2011 17:36 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 3758D21F8AD9 for <rtcweb@ietfa.amsl.com>; Mon, 18 Jul 2011 10:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 l7Q+im01NZNC for <rtcweb@ietfa.amsl.com>; Mon, 18 Jul 2011 10:36:01 -0700 (PDT)
Received: from zimbra.westhawk.co.uk (zimbra.westhawk.co.uk [192.67.4.167]) by ietfa.amsl.com (Postfix) with ESMTP id 7C24A21F8A30 for <rtcweb@ietf.org>; Mon, 18 Jul 2011 10:36:00 -0700 (PDT)
Received: from [192.168.0.14] (unknown [93.89.81.113]) by zimbra.westhawk.co.uk (Postfix) with ESMTP id DE8B637A902; Mon, 18 Jul 2011 18:45:43 +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: <49CD37FC-7951-45A0-84C4-A443F8B151F3@cisco.com>
Date: Mon, 18 Jul 2011 18:35:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <32BE1B60-DB34-4744-B17C-CEC92F2E74AE@phonefromhere.com>
References: <4E0832FE.7010401@ericsson.com> <4E1DC07B.7000807@ericsson.com> <D1BE71E1-4F3B-474E-8A28-AA53CE6B684E@cisco.com> <CA+9kkMCJiE+bfEqZzOBo46aXVH-H2sehHh6UJv3tVdJKGjaokQ@mail.gmail.com> <49CD37FC-7951-45A0-84C4-A443F8B151F3@cisco.com>
To: Cullen Jennings <fluffy@cisco.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 17:36:02 -0000

On 18 Jul 2011, at 18:12, Cullen Jennings wrote:

>> 
>> 
>> To put this another way, a reliable protocol associated with a real time stream has some pretty obvious uses (gaming has also already been mentioned).
> 
> I'm pushing back on it is obvious that there are use cases for this. That there is simultaneous need for the semantics of "you must deliver this data no matter how long it takes" and "this data need to get there in less than X time or it is useless" is not obvious to me. 

To my mind,  _sequence_ is vital. 

The protocol should promise to deliver these datagrams to the application layer in the order that they were
sent. If that requires an occasional round-trip delay to cope with packet loss (perhaps with a flag to say it was late),
that's acceptable (but sub-optimal), out-of-order datagrams aren't.  

In the vast majority of cases we can expect it to deliver the datagram in close sync with the associated media.

Tim.