Re: [rtcweb] STUN for keep-alive

Michael Tüxen <Michael.Tuexen@lurchi.franken.de> Thu, 22 September 2011 19:34 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 D09B51F0C63 for <rtcweb@ietfa.amsl.com>; Thu, 22 Sep 2011 12:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.045
X-Spam-Level:
X-Spam-Status: No, score=-2.045 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 SgtNuhy-PO6p for <rtcweb@ietfa.amsl.com>; Thu, 22 Sep 2011 12:34:57 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 219CA1F0C3C for <rtcweb@ietf.org>; Thu, 22 Sep 2011 12:34:56 -0700 (PDT)
Received: from [192.168.1.195] (p5481AD2B.dip.t-dialin.net [84.129.173.43]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 142B31C0C0BD6; Thu, 22 Sep 2011 21:37:27 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5F7F4274-1AF6-4162-A177-51E1CDD0BCCD@cisco.com>
Date: Thu, 22 Sep 2011 21:37:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BC49EB9-A690-4ED2-B0E5-76BC0730A4C5@lurchi.franken.de>
References: <7F2072F1E0DE894DA4B517B93C6A05852233EDB21D@ESESSCMS0356.eemea.ericsson.se> <5F7F4274-1AF6-4162-A177-51E1CDD0BCCD@cisco.com>
To: Cullen Jennings <fluffy@cisco.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:34:57 -0000

On Sep 22, 2011, at 9:29 PM, Cullen Jennings wrote:

> 
> 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).
... if you run DTLS/UDP, DTLS provides a HB mechanism:
http://tools.ietf.org/html/draft-ietf-tls-dtls-heartbeat-02
Best regards
Michael
>> 
>> Regards,
>> 
>> Christer
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>