IETF Logo Mail Archive

Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-stun-consent-freshness-11

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Fri, 01 May 2015 09:16 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 A6F4C1B3025 for <rtcweb@ietfa.amsl.com>; Fri, 1 May 2015 02:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 SoLCJPKaHi8q for <rtcweb@ietfa.amsl.com>; Fri, 1 May 2015 02:16:45 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF93D1B3020 for <rtcweb@ietf.org>; Fri, 1 May 2015 02:16:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2244; q=dns/txt; s=iport; t=1430471804; x=1431681404; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=LtMQkIWNTbimwmQ7jJziut5iDUjCMqk7+duBSu9fHDA=; b=b/3GEUPRTm20e8pG8O7cABlItA/GMpn+4xfmoDlN74xtR5tZgIiru28V v9gz87zr/XlArDdzybrSTPOMuS4zuszR9u4mTl9SGqoqLBvtcmSEa5cNR zOOpGiEVxn2ketbwlXI25Ho2St2nUpW0kam5oV70EgJyLa7MAcnEfRDsM w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BSBAC0Q0NV/5JdJa1cgwxTXAXFYQmBSgqFNk4CgVk4FAEBAQEBAQGBCoQgAQEBBAEBAUQnFwQCAQgRAwECLycLHQgCBAESiCsNuHGOLgEBAQEBAQEDAQEBAQEBAQEBGYs4hQwGhCcFizuEEIIkhAqGQIEjPYMOjT+DUCODdG+BAgc7gQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,350,1427760000"; d="scan'208";a="146242846"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-4.cisco.com with ESMTP; 01 May 2015 09:15:35 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t419FZQS028016 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 May 2015 09:15:35 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.199]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0195.001; Fri, 1 May 2015 04:15:34 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Alissa Cooper <alissa@cooperw.in>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] AD evaluation: draft-ietf-rtcweb-stun-consent-freshness-11
Thread-Index: AQHQg+9gZtq5gzqSOE6Em1OL5/PJLg==
Date: Fri, 01 May 2015 09:15:34 +0000
Message-ID: <D16941CD.2D406%rmohanr@cisco.com>
References: <3B27E16C-2AD7-427B-864C-741F38575B97@cooperw.in>
In-Reply-To: <3B27E16C-2AD7-427B-864C-741F38575B97@cooperw.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.65.60.92]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DF6084A4FE9E78478C81313DB42AAED2@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/H06t9ZOvExt_BoyVx9M_1mdwV9w>
Subject: Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-stun-consent-freshness-11
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: Fri, 01 May 2015 09:16:46 -0000

Hi Alissa,

Thanks for your review. Please see inline for my responses.

-----Original Message-----
From: Alissa Cooper <alissa@cooperw.in>
Date: Friday, 1 May 2015 6:02 am
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: [rtcweb] AD evaluation:
draft-ietf-rtcweb-stun-consent-freshness-11

>I have reviewed draft-ietf-rtcweb-stun-consent-freshness-11 in
>preparation for IETF LC. The document is in good shape and I will request
>the last call shortly. I have a couple of questions I¹d like to discuss
>while the last call is ongoing, though. I¹m not entirely caught up on
>mailing list traffic so apologies if these questions/comments have
>already been discussed.
>
>Section 4.1:
>"An endpoint that is not sending any application data does not need to
>   maintain consent.  However, failure to send could cause any NAT or
>   firewall mappings for the flow to expire.  Furthermore, having one
>   peer unable to send is detrimental to many protocols."
>
>It sounds like the unstated implication here is that if you are such an
>endpoint, you should keep doing consent checks anyway to maintain
>consent. Should that be stated explicitly, or am I misunderstanding?

This is for endpoints that does not send any application data. In such
cases there may be endpoints that may not send consent. We discussed about
mandating sending consent always but there was objections to that in WG
and this statement was introduced to give flexibility so that endpoints
that does not intend to send any data on a 5-tuple may choose not to
maintain consent and can use ICE keepalives
http://tools.ietf.org/html/rfc5245#section-10.



>
>Section 7:
>The normative MAY here seems odd. It seems like this section could be
>replaced with:
>
>"The W3C specification [cite] may provide an API hook that generates an
>event when consent has expired for a given 5-tuple, meaning that
>transmission of data has ceased.  This could indicate what application
>data is affected, such as media or data channels.²

I am fine with changing this.

Regards,
Ram


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

v2.23.0 | Report a Bug | By Email