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

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Mon, 22 September 2014 04:33 UTC

Return-Path: <rmohanr@cisco.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 127C11A1A1C for <rtcweb@ietfa.amsl.com>; Sun, 21 Sep 2014 21:33:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.437
X-Spam-Level:
X-Spam-Status: No, score=-11.437 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 NGLGul7A-Rye for <rtcweb@ietfa.amsl.com>; Sun, 21 Sep 2014 21:33:43 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51A1C1A1A18 for <rtcweb@ietf.org>; Sun, 21 Sep 2014 21:33:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3056; q=dns/txt; s=iport; t=1411360423; x=1412570023; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ZFlY+LBLYWixxeL1yV5/0poynkSzpKwk3i04RrazIoQ=; b=eEeZBuW8oK7p7qI/zIENNTLdxGPZd87uYQAM+J9xF831cc0TlCYgrKkL +bPRiFOIZz+fjStbGk+BX5zX1ryLtUmPR1UdlMaoVaMuuSj0lzfTAdrKQ vYT5OAFlVj97mqwwYhNUWG7ulfeV6yvujCGOtqksvybGmgrmCrNl2nT+8 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAA+mH1StJV2d/2dsb2JhbABggw6BLoJ9zm0BGWsWAXmEAwEBAQQ0VQIBBgIRAwECBSgCAjAdCAIEARKIPpEynEEGlVcBF4EmjmeCcoFZAQSRV4s/lVKDYWyBSIECAQEB
X-IronPort-AV: E=Sophos;i="5.04,570,1406592000"; d="scan'208";a="79971637"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-6.cisco.com with ESMTP; 22 Sep 2014 04:33:42 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s8M4Xg2l018070 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 22 Sep 2014 04:33:42 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.227]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0195.001; Sun, 21 Sep 2014 23:33:42 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Consent Freshness: Some suggestions for editorial clarifications
Thread-Index: AQHP1h2Dt0wZcvY3bE2GylGVu4RX/JwNQcqA
Date: Mon, 22 Sep 2014 04:33:42 +0000
Message-ID: <D045A44E.136B2%rmohanr@cisco.com>
References: <7594FB04B1934943A5C02806D1A2204B1D44E72A@ESESSMB209.ericsson.se> <D045A2A3.1369F%rmohanr@cisco.com>
In-Reply-To: <D045A2A3.1369F%rmohanr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [173.39.65.37]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <F50A34AA1D85844A9C9E81F4276435D9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/l0jiEGpOvnZLsiPx5QMLqoy82yM
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: Mon, 22 Sep 2014 04:33:45 -0000

Hi Christer,

Please see inline

>
>
>From:  Christer Holmberg <christer.holmberg@ericsson.com>
>Date:  Wednesday, 17 September 2014 1:11 pm
>To:  "rtcweb@ietf.org" <rtcweb@ietf.org>
>Subject:  [rtcweb] Consent Freshness: Some suggestions for
>editorial	clarifications
>
>
>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.

This depends on the underlying transport used. If its UDP as you said its
unreliable. For other transports it is not the case. So I don’t see a need
to add any text in this 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².

Will update this in the next revision.

> 
> 
>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. I think it would be useful to
>explicitly indicate that, and also say that responses that are received
>after that time must be
> discarded.

Ok. Will mention that any responses received after 30 secs will be
discarded.

Regards,
Ram

> 
>Thanks!
> 
>Regards,
> 
>Christer
> 
> 
>