Re: [rtcweb] Consent Freshness: Some suggestions for editorial clarifications

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 25 September 2014 08:32 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 3906F1A0299 for <rtcweb@ietfa.amsl.com>; Thu, 25 Sep 2014 01:32:27 -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 xcX8-Gsd19XR for <rtcweb@ietfa.amsl.com>; Thu, 25 Sep 2014 01:32:25 -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 4FF541A0031 for <rtcweb@ietf.org>; Thu, 25 Sep 2014 01:32:24 -0700 (PDT)
X-AuditID: c1b4fb25-f791c6d00000617b-9e-5423d315038c
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id D3.DB.24955.513D3245; Thu, 25 Sep 2014 10:32:22 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0174.001; Thu, 25 Sep 2014 10:32:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Thread-Topic: [rtcweb] Consent Freshness: Some suggestions for editorial clarifications
Thread-Index: AQHP2JlcIxJbv+HLeEKRM6mVcFFd6ZwRhFJw
Date: Thu, 25 Sep 2014 08:32:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D45A186@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D44E72A@ESESSMB209.ericsson.se> <CAKz0y8xB6VaJtcABPhyP2FMr13_ZGZNFzafaUs590ym2T5OPyA@mail.gmail.com>
In-Reply-To: <CAKz0y8xB6VaJtcABPhyP2FMr13_ZGZNFzafaUs590ym2T5OPyA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D45A186ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42KZGfG3RlfssnKIwcK7zBZ/NvtZrP3Xzu7A 5LFz1l12jyVLfjIFMEVx2aSk5mSWpRbp2yVwZdxsecRa0DSHseLk+emsDYxvpjN2MXJySAiY SGza+JgVwhaTuHBvPVsXIxeHkMBRRonvp54yQzhLGCU+frnL1MXIwcEmYCHR/U8bpEFEwFhi S8svsGZmAXWJO4vPsYPYwgIREmcmLmCHqImUmLl8MzNIq4iAkcTU46wgJouAqsSxZzogFbwC vhLP3kyC2jSFUeLo5dNsIAlOgUCJaRvOsoDYjEC3fT+1hglilbjErSfzmSBuFpBYsuc8M4Qt KvHy8T+oX5QkVmy/xAiyi1kgX2LKZRmIXYISJ2c+YZnAKDoLyaRZCFWzkFRBhDUl1u/Sh6hW lJjS/ZAdwtaQaJ0zlx1ZfAEj+ypG0eLU4qTcdCNjvdSizOTi4vw8vbzUkk2MwEg7uOW36g7G y28cDzEKcDAq8fAqlCuHCLEmlhVX5h5ilOZgURLnXXhuXrCQQHpiSWp2ampBalF8UWlOavEh RiYOTqkGRsd4hb+mOh8506eJLV/RJp5zfv5W8aMXekXk/8lPnbbh/vZE/VrZZQqr+n+9PV56 vsJ1gXLmYpO9Sb7mUQzSL6rM93cX5eQseenTc38Ny96LkjUh5Z9WtWWlFnjLyJWd/1y08fNC 49oNn/XNlA4JlE4WFZBe8rt/Kxu7pKBCr7hy/9+32bJ1SizFGYmGWsxFxYkAeB9uX5UCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/yLAfp56wX50HbvnSegX4EPA9y54
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Consent Freshness: Some suggestions for editorial clarifications
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: Thu, 25 Sep 2014 08:32:27 -0000

Hi,
Based on feedback I receive from implementers, there are a couple of clarifications I think would be useful in the consent freshness draft.



Q1:
-----

As STUN binding requests for consent are sent unreliably, and are not re-transmitted, I think it would be useful to have some explicit text saying that individual requests (and/or their associated responses) may get lost in the network, and that a sender must be prepared that a response to such requestmay never arrive.

It may be obvious to us, but maybe not as clear to the first-time reader of the draft.




Q2:
-----

Section 4.1 says:

“That is, if a valid STUN binding response corresponding to one of the STUN requests sent in the last 30 seconds
                has not been received from the remote peer's Transport Address, the endpoint MUST cease transmission on that 5-tuple.”

First, I suggest the following clarification:

s/”to one of the STUN requests sent in the last 30 seconds”/”to one of the STUN requests (not necessarily the last one) sent in the last 30 seconds”.


Second, there is no explicit text on for how long the client keeps the STUN transaction alive, i.e. for how long it waits for the response.

I assume that, after 30 seconds, the client does not need to maintain state and wait for the response anymore.

​My understanding is that the sender doesn't need remember the request for 30 sec, instead it needs to remember it only for RTT duration. If a matching response is received within that duration you have a 'hit'. If there is no 'hit' over the last 30 sec, consent expires.

I agree this isn't clear in the current version.

How do you calculate the RTT? Based on previous transactions? What if, for whatever reason, the roundtrip for a STUN binding request/response takes longer that previously? You would discard the response.

I think it is much more clear the specify a time. 30 seconds is a good value, because if it takes longer the response is “unvalid” anyway.

Regards,

Christer




I think it would be useful to explicitly indicate that, and also say that responses that are received after that time must be discarded.

Thanks!

Regards,

Christer



_______________________________________________
rtcweb mailing list
rtcweb@ietf.org<mailto:rtcweb@ietf.org>
https://www.ietf.org/mailman/listinfo/rtcweb