Re: [rtcweb] STUN for keep-alive

Cullen Jennings <fluffy@cisco.com> Thu, 22 September 2011 19:26 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 9EAC011E809D for <rtcweb@ietfa.amsl.com>; Thu, 22 Sep 2011 12:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.103
X-Spam-Level:
X-Spam-Status: No, score=-103.103 tagged_above=-999 required=5 tests=[AWL=-0.504, 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 WuuzJ2s-Fln1 for <rtcweb@ietfa.amsl.com>; Thu, 22 Sep 2011 12:26:59 -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 0D2A811E809A for <rtcweb@ietf.org>; Thu, 22 Sep 2011 12:26:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1580; q=dns/txt; s=iport; t=1316719771; x=1317929371; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=INf/q4PbOINKAbXAcw2uaNtU/PDKbTjcXeQ5YZzzqeA=; b=b33hr39cKi6uP2mv+OkDtVFsHLusD9C3y0eqVxjcesVVYV2gqVrAhxKc 3loHMIYz1ahfuPjCIPZS0n4Rl9SV0rCLz2Uu2xTWvU4EZu/YfKJ4FN4Bc gQ4MykCCpUTAcsYqPcFM8HVpie7WtPyKz6HWK+KTHhkFdaBIKEPpj5kUK M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAGKLe06rRDoG/2dsb2JhbABCqAJ4gVMBAQEBAgEBAQEPASc0CxALRicwBhMih1YGlxcBniyGHWAEh3GLX4UfjC8
X-IronPort-AV: E=Sophos;i="4.68,424,1312156800"; d="scan'208";a="3730070"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 22 Sep 2011 19:29:31 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p8MJTUwf013610; Thu, 22 Sep 2011 19:29:30 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: <7F2072F1E0DE894DA4B517B93C6A05852233EDB21D@ESESSCMS0356.eemea.ericsson.se>
Date: Thu, 22 Sep 2011 13:29:30 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F7F4274-1AF6-4162-A177-51E1CDD0BCCD@cisco.com>
References: <7F2072F1E0DE894DA4B517B93C6A05852233EDB21D@ESESSCMS0356.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1084)
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] STUN for keep-alive
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: Thu, 22 Sep 2011 19:26:59 -0000

In the past, we had too many ways of doing keep alive and it resulted in poor interoperability when two sides choose different ways - I'd rather avoid that sort of problem

On Sep 14, 2011, at 3:48 AM, Christer Holmberg wrote:

> 
> Hi,
> 
> Assuming we would use ICE for media authorization, it has been indicated that, for legacy interoperability, a gateway would be required in many cases (as the legacy entities might not support ICE).
> 
> ICE "bundles" functions together, meaning that if you use STUN for media authorization purpose (which is a part of the connectivity check purpose), you will also use STUN for keep-alive purpose (for UDP based media).
> 
> My question is: would we be able to relax the requirement to use STUN for keep-alive? Because, eventhough the keep-alives messages aren't authenticated, and do not trigger responses, a gateway would still have to process them, and since a gateway typically would serve a large number of browser clients, that could have quite big performance impact (the number of STUN keep-alives sent per session of course depend on how much other media traffic there is, but still).
> 
> So, for RTP based media, one could use RTP, and for UDP based data channels "dummy" UDP packets (unless there is a protocol on top of UDP which provides a keep-alive mechanism itself).
> 
> Regards,
> 
> Christer
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb