IETF Logo Mail Archive

Re: [rtcweb] OPS-Dir review of draft-ietf-rtcweb-stun-consent-freshness-13

Christer Holmberg <christer.holmberg@ericsson.com> Sun, 31 May 2015 13:38 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 203551A1BB8 for <rtcweb@ietfa.amsl.com>; Sun, 31 May 2015 06:38:17 -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 xkY7FpbD3vOU for <rtcweb@ietfa.amsl.com>; Sun, 31 May 2015 06:38:15 -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 3A4381A1BB1 for <rtcweb@ietf.org>; Sun, 31 May 2015 06:38:15 -0700 (PDT)
X-AuditID: c1b4fb25-f79b66d000001131-65-556b0ec5f27c
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C6.31.04401.5CE0B655; Sun, 31 May 2015 15:38:13 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.71]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0210.002; Sun, 31 May 2015 15:38:12 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bernard Aboba <bernard.aboba@gmail.com>, Harald Alvestrand <harald@alvestrand.no>
Thread-Topic: [rtcweb] OPS-Dir review of draft-ietf-rtcweb-stun-consent-freshness-13
Thread-Index: AQHQmcKuxYNeEsZ9K0CG03cvwAJmIp2TJGkAgADaPoCAAKz8gIABQITg
Date: Sun, 31 May 2015 13:38:12 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D873AEB@ESESSMB209.ericsson.se>
References: <913383AAA69FF945B8F946018B75898A478607D3@xmb-rcd-x10.cisco.com> <D18DD4A0.31980%rmohanr@cisco.com> <CE03DB3D7B45C245BCA0D243277949364CB762@MX104CL02.corp.emc.com> <556965FD.1060001@alvestrand.no> <B00F986D-664C-4DC5-AD9E-785680DAE81B@gmail.com>
In-Reply-To: <B00F986D-664C-4DC5-AD9E-785680DAE81B@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGLMWRmVeSWpSXmKPExsUyM+Jvre5RvuxQg4nXRCw27PvPbHGsr4vN Yu2/dnYHZo8rE66weuycdZfdY8mSn0wBzFFcNimpOZllqUX6dglcGXPf32AuOMJRsXfRI9YG xs9sXYycHBICJhI3bq1ggrDFJC7cWw8U5+IQEjjKKHF1xh12kISQwGJGiZ1z1bsYOTjYBCwk uv9pg4RFBMIl3rc/YwGxmQXUJe4sPgdWLiwQKtH34QAbSLmIQJjE7YNmEOVuEvdfPwIrYRFQ lbj/dwIziM0r4Ctx58xrZoi1nUwSJw7vALuNU8BW4uW/u2BFjEC3fT+1hglil7jErSfzoW4W kFiy5zwzhC0q8fLxP1YIW0li0e3PUPU6Egt2f2KDsLUlli18DbVYUOLkzCcsExjFZiEZOwtJ yywkLbOQtCxgZFnFKFqcWpyUm25krJdalJlcXJyfp5eXWrKJERhRB7f8Vt3BePmN4yFGAQ5G JR5eheysUCHWxLLiytxDjNIcLErivJ5dIaFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGBlD cv70X20/FfBRYs/LY55Rx3dvssh/l363L2OZepD0k8LIb/80zqy6ZHpLf09J6Nuf4t+4hCc9 XP09kDtM+rT+GgWW/K9HnKe6mr5ZpvDTav/C8L0bp54+ynBDSOT8ukSV0v+Pt6eePzp1y7XU a6/+TXbZL8Os9sLLISuYaQVXu7R6xL4IHlElluKMREMt5qLiRAA9yMYhiQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/QcnbVuy-2WFemlTrde4ao83hVvk>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] OPS-Dir review of draft-ietf-rtcweb-stun-consent-freshness-13
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: Sun, 31 May 2015 13:38:17 -0000

Hi,

>> I'd prefer to limit the number of documents that try to design APIs.
>> 
>> Can we do something more generic, like "Applications that use the 
>> RTWEB transport will need to be notified when transmission ceases 
>> due to expiry of consent. The design of APIs to carry these 
>> notifications  is out of scope for this document."?
>
> [BA] Agree with Harald. Loss of STUN consent on a 5-tuple is quite different from tripping 
> a circuit breaker. Let's not design the APIs in this document.

I agree on the not-designing-the-API part.

Regarding Harald's suggested text, it's fine - but I don't think it belongs in this document. Shouldn't it be in the RTCWEB overview and/or security document instead?

The consent freshness draft could then state that the mechanism/requirements how applications are made aware of consent expiration is outside the scope of the document.

Regards,

Christer





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

v2.23.0 | Report a Bug | By Email