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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 06 May 2015 06:53 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 37E031A7D80 for <rtcweb@ietfa.amsl.com>; Tue, 5 May 2015 23:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7Ivk8Yjihrrj for <rtcweb@ietfa.amsl.com>; Tue, 5 May 2015 23:53:34 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FEF71A7028 for <rtcweb@ietf.org>; Tue, 5 May 2015 23:53:33 -0700 (PDT)
X-AuditID: c1b4fb30-f798d6d0000009ec-c2-5549ba6b8dc3
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 34.D2.02540.B6AB9455; Wed, 6 May 2015 08:53:31 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.61]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0210.002; Wed, 6 May 2015 08:53:30 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alissa Cooper <alissa@cooperw.in>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [rtcweb] AD evaluation: draft-ietf-rtcweb-stun-consent-freshness-11
Thread-Index: AQHQg6ZCX3ABhhDJOU+APBu3+BbmbJ1nNjYAgABrhwCABulYUA==
Date: Wed, 06 May 2015 06:53:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D7EA1AE@ESESSMB209.ericsson.se>
References: <3B27E16C-2AD7-427B-864C-741F38575B97@cooperw.in> <CABkgnnU=NeP7MzqxE1Mg+ZN8EZf=3FtayyLP1Q-z=6vaPUtAuA@mail.gmail.com> <3BE7E012-A474-4CEA-889A-B611EEFC4AEC@cooperw.in>
In-Reply-To: <3BE7E012-A474-4CEA-889A-B611EEFC4AEC@cooperw.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyM+JvjW72Ls9Qg08vNC2mn/nLaHHtzD9G i7X/2tkdmD2+PHnJ5LFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZTT132ctaOWt2PNhAWsD 40muLkZODgkBE4mGxzNYIGwxiQv31rN1MXJxCAkcZZQ4tH47E4SziFHi4/N7QFUcHGwCFhLd /7RBGkQEgiSu9M9nArGZBdQl7iw+xw5SIgwUX32GF6IkWGLzjlcsELaTxKpTqxlBbBYBFYk9 E7aB2bwCvhLzf++H2ruDUWLzos9gCU4BO4nTH/+wgdiMQMd9P7UGape4xK0nEHslBAQkluw5 zwxhi0q8fPyPFcJWlLg6fTlUvY7Egt2f2CBsbYllC18zQywWlDg58wnLBEaxWUjGzkLSMgtJ yywkLQsYWVYxihanFiflphsZ6aUWZSYXF+fn6eWllmxiBMbUwS2/DXYwvnzueIhRgINRiYd3 QalnqBBrYllxZe4hRmkOFiVxXjvjQyFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGEOb3zvd nHG07d/5GUevrC7cnjWphOn63olBqtvrc27Hy0bz6y8MS7zmsq20rnbqnxN8pzbsD1DvUS5/ /F6XhV1nZTrn/j2+rjH5CikpgS82PS/Ki9Gs/s/4vuZ9ovRMw+dmP5eJ3ys7v4z34szI+Fcc 1lcEGsxfbQvqrFl8aLXPzNKdMyNCWpVYijMSDbWYi4oTARhC9oOKAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/tJV2bw1KgAJsZPLNmLluH5J6ol4>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Wed, 06 May 2015 06:53:36 -0000

Hi,

I don't think you need to continue doing consent because of NAT issues, if you are sending normal STUN keep-alives.

Regards,

Christer

-----Original Message-----
From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Alissa Cooper
Sent: 2. toukokuuta 2015 2:20
To: Martin Thomson
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] AD evaluation: draft-ietf-rtcweb-stun-consent-freshness-11


On May 1, 2015, at 9:54 AM, Martin Thomson <martin.thomson@gmail.com> wrote:

> On 30 April 2015 at 17:32, Alissa Cooper <alissa@cooperw.in> wrote:
>> "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?
> 
> Can you tell that this is my text?
> 
> Yep, the unspoken implication is that if you stop maintaining consent, 
> a flow is highly likely to break.  I'm OK with making that explicit.
> 
> ... .  Absent better information about the network, an endpoint SHOULD 
> maintain consent if there is any possibility that a flow might be 
> needed again.

WFM

> 
> (Thanks for the suggestion on Sec7.  I wasn't happy with it before.)

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