Re: [rtcweb] realiable data service

Cullen Jennings <fluffy@cisco.com> Mon, 18 July 2011 17:00 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 B609D21F8BBB for <rtcweb@ietfa.amsl.com>; Mon, 18 Jul 2011 10:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 v8YZ4XyduAGT for <rtcweb@ietfa.amsl.com>; Mon, 18 Jul 2011 10:00:17 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4858B21F8B3D for <rtcweb@ietf.org>; Mon, 18 Jul 2011 10:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=871; q=dns/txt; s=iport; t=1311008417; x=1312218017; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=2yX1Ok5go+0TVyo72JbKwFatMoHdHCpVb74qpH9IPvc=; b=WDOh/L4374cnEBqbR0M+e/gdD0WSlcZfhSo730VX/0UWfVI8i0ZQlJul PSuTDwIfAc9DZL3Vq1HZbFd85f1CYrNuY7ZQTAXQXVKgyHXPh+bn9c7Mb 65KDRyxjI4l2m2YYSNG2lndNrktHkLadE133hvB31EXt6j0q7taSww0bL E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHRmJE6Q/khL/2dsb2JhbABUp3l3iHykNJ4PhV1fBIdUixKQdQ
X-IronPort-AV: E=Sophos;i="4.67,223,1309737600"; d="scan'208";a="43064475"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 18 Jul 2011 17:00:07 +0000
Received: from sjc-vpn3-1134.cisco.com (sjc-vpn3-1134.cisco.com [10.21.68.110]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p6IH05OX019404; Mon, 18 Jul 2011 17:00:06 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: <271CD938-00F7-423D-BA6E-6407811DC80E@phonefromhere.com>
Date: Mon, 18 Jul 2011 10:00:04 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CEC8860-BF8F-44CB-8641-925F18503231@cisco.com>
References: <4E0832FE.7010401@ericsson.com> <4E1DC07B.7000807@ericsson.com> <D1BE71E1-4F3B-474E-8A28-AA53CE6B684E@cisco.com> <F43A8952-0CF3-4683-923F-DF1ED0B4344B@phonefromhere.com> <4E243B77.1000900@ericsson.com> <271CD938-00F7-423D-BA6E-6407811DC80E@phonefromhere.com>
To: Tim Panton <tim@phonefromhere.com>
X-Mailer: Apple Mail (2.1084)
Cc: "rtcweb@ietf.org" <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:00:21 -0000

On Jul 18, 2011, at 7:19 , Tim Panton wrote:

> 
> On 18 Jul 2011, at 14:56, Magnus Westerlund wrote:
> 
>> On 2011-07-15 19:29, Tim Panton wrote:
>>> I don't think it is very hard to implement, we could take RFC 5456's
>>> sequencing and retry mechanism for example. or indeed Plan9's IL .
>> 
>> I would warn about thinking this is easy. It is easy to get something
>> that works on sunny days, it is hard to build something that is secure,
>> efficient, robust and fair.
>> 
> 
> Agreed, getting all 4 in any protocol is hard, indeed I don't think I've seen it 
> done yet.

FWIW - TLS over TCP with application level reconnect on failure seem to meet all 4. Where it fails if you can't easily do it in user space. So I'd add two more. Needs to work with high degree of nat/fw traversal success and be easy to deploy.