IETF Logo Mail Archive

Re: [rtcweb] Consent Freshness: Connection liveness/heartbeats

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 14 October 2014 06:39 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6270A1A1A40 for <rtcweb@ietfa.amsl.com>; Mon, 13 Oct 2014 23:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pofqGKUVqnck for <rtcweb@ietfa.amsl.com>; Mon, 13 Oct 2014 23:39:48 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45E1C1A6FAC for <rtcweb@ietf.org>; Mon, 13 Oct 2014 23:39:47 -0700 (PDT)
X-AuditID: c1b4fb25-f791c6d00000617b-24-543cc531bf56
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 6C.87.24955.135CC345; Tue, 14 Oct 2014 08:39:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0174.001; Tue, 14 Oct 2014 08:39:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Consent Freshness: Connection liveness/heartbeats
Thread-Index: Ac/khDonWu2om5LnTYiCouL4O3PwFQC9Nuyg
Date: Tue, 14 Oct 2014 06:39:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D47B520@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D474980@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D474980@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D47B520ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvja7hUZsQg+3HpC3W/mtnd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxrXzL9kLpiVVrJ/3h7WB8X1YFyMnh4SAiUTbk7PsELaYxIV7 69m6GLk4hASOMkqcbL0B5SxhlHjy9y1LFyMHB5uAhUT3P22QBhGBWIkVm6ezgNjCAnYSl9e8 Z4SI20vcmtjABGEbSUxpv80GYrMIqEp8uH+LGcTmFfCVODz3DVivEJB9e8IDMJtTwE/i+YNj YAcxAh30/dQasDnMAuISt57MZ4I4VEBiyZ7zzBC2qMTLx/9YIWwlibWHt4OdySyQL7FhgR7E KkGJkzOfsExgFJmFZNIshKpZSKogSnQkFuz+xAZha0ssW/iaGcY+c+AxE7L4Akb2VYyixanF SbnpRsZ6qUWZycXF+Xl6eaklmxiB8XNwy2/VHYyX3zgeYhTgYFTi4V3QbBMixJpYVlyZe4hR moNFSZx34bl5wUIC6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoYEy/fYFw3o9aA7fXFlV0i7f8d SlznNbuWyET72vdZP/1g8OT971of44Xqj75Oe7v9ddHO7zc5lZZ8enPxx92lGxedtVglH7PR 7MI17vfijwsmLq1bUa61JdGlzeXaHOUP18Kjdplk1K2aU73j94XW7Gcmy4N6o9yMmzf7M2el VR5qnrLn4s0HekosxRmJhlrMRcWJAI5B0ZCAAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/L4ekZArCiOJFsDUHkEpLqxl9wMk
Subject: Re: [rtcweb] Consent Freshness: Connection liveness/heartbeats
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 14 Oct 2014 06:39:50 -0000

Hi,

I suggest that we REMOVE the liveness/heartbeats feature from the consent refresh draft. As I said earlier, I see no need for sending additional consent requests in addition to those already sent every 5th second.

Regards,

Christer

From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: 10 October 2014 15:23
To: rtcweb@ietf.org
Subject: [rtcweb] Consent Freshness: Connection liveness/heartbeats

Hi,

I have some questions on the connection liveness/heartbeat section of the draft.


Q1:
===

The text says:

        "Similarly, if packets haven't been received within a certain period,
        an application can request a consent check (heartbeat) be generated."

BUT, if an endpoint is anyway sending consent requests every 5th second, why aren't the those enough as hearbeats? As long as the endpoint receives responses, it knows the remote endpoint is alive (the text even says that an endpoint is considered alive as long as some data is received from it).

And, if the endpoint does NOT receive responses to the consent requests, consent will expire anyway.

I DO understand that an ICE lite may want to send a heartbeat request if it does not receive any data, as it doesn't send consent requests.


Q2:
===

The text says:


        "Sending consent checks (heartbeats) at a high rate could allow a

        malicious application to generate congestion, so applications MUST

        NOT be able to send heartbeats at an average rate of more than 1 per

        second."



I don't think applications should be alowed to generate heartbeats this often, and I see no need for it.


Q3:
===

The spec is unclear on what happens is a response to a heartbeat request is not received. I guess that is an application decision, but I think the spec should be clear that it does NOT have any impact on consent - the "real" consent requests are used to determine.


Regards,

Christer

v2.23.0 | Report a Bug | By Email