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

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 01 June 2015 09:16 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 572181A90CF for <rtcweb@ietfa.amsl.com>; Mon, 1 Jun 2015 02:16:44 -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 6oSpAuEf61MC for <rtcweb@ietfa.amsl.com>; Mon, 1 Jun 2015 02:16:42 -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 599031A90C0 for <rtcweb@ietf.org>; Mon, 1 Jun 2015 02:16:41 -0700 (PDT)
X-AuditID: c1b4fb25-f79b66d000001131-cf-556c22f7feca
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.125]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C3.D1.04401.7F22C655; Mon, 1 Jun 2015 11:16:39 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.71]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0210.002; Mon, 1 Jun 2015 11:16:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, 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: AQHQmcKuxYNeEsZ9K0CG03cvwAJmIp2TJGkAgADaPoCAAKz8gIABQITggAEfgoCAADWpgIAAIiEA
Date: Mon, 01 Jun 2015 09:16:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D874C4F@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> <7594FB04B1934943A5C02806D1A2204B1D873AEB@ESESSMB209.ericsson.se> <D191F31F.32336%rmohanr@cisco.com> <913383AAA69FF945B8F946018B75898A478627AA@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A478627AA@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZGfG3Vve7Uk6owby3EhYb9v1ntjjW18Vm sbxrB6PF2n/t7BYndm9jdGD1uDLhCqvHlN8bWT12zrrL7rFkyU+mAJYoLpuU1JzMstQifbsE roy3b5pYCl5KVfQdPMDewPhFtIuRk0NCwERi5p+VbBC2mMSFe+uBbC4OIYGjjBIvD69mhHAW MUpc3dfL2sXIwcEmYCHR/U8bJC4isItRYuvkyYwg3cwC6hJ3Fp9jB7GFBUIl+j4cYAOpFxEI k7h90AwkLCIQJTG39SgTiM0ioCKx58dHsFZeAV+JVxv2Qu3ayixx8MVCsAQnUGLz57VgNiPQ dd9PrWGC2CUucevJfCaIqwUkluw5zwxhi0q8fPyPFcJWlGh/2gB1m57EjalT2CBsbYllC18z QywWlDg58wnLBEaxWUjGzkLSMgtJyywkLQsYWVYxihanFiflphsZ66UWZSYXF+fn6eWllmxi BMbcwS2/VXcwXn7jeIhRgINRiYd3wZ7sUCHWxLLiytxDjNIcLErivJ5dIaFCAumJJanZqakF qUXxRaU5qcWHGJk4OKUaGBvPayom5Zbe/sv5s8ieTyJwve7q3jtVAqdkeafnK+1+wPbW/fiT w0xPK1hfOLg8143zkbjo4X24O7p+TfEe++kHxYPO9ySfvF0hUPln3/bN1qZ2ZSc/vIyVL3rp EWyetHjS/M9mflveWVy8YrY2/sXSW4xhv/adT5z2I6oyY+/6d3yHtTaa+CmxFGckGmoxFxUn AgAZsfAFmgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/tYQ-j-CMBkLElowfvAAbnyvi5y8>
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: Mon, 01 Jun 2015 09:16:44 -0000

Hi,

Why do we need to talk about W3C specifications at all? Couldn't we simply remove section 8?

The out-of-the-scope text I suggested earlier could be put e.g. in the Introduction, or in an Applicability section.

Regards,

Christer

-----Original Message-----
From: Tirumaleswar Reddy (tireddy) [mailto:tireddy@cisco.com] 
Sent: 1. kesäkuuta 2015 12:13
To: Ram Mohan R (rmohanr); Christer Holmberg; Bernard Aboba; Harald Alvestrand
Cc: rtcweb@ietf.org
Subject: RE: [rtcweb] OPS-Dir review of draft-ietf-rtcweb-stun-consent-freshness-13

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Ram Mohan R
> (rmohanr)
> Sent: Monday, June 01, 2015 11:31 AM
> To: Christer Holmberg; Bernard Aboba; Harald Alvestrand
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] OPS-Dir review of 
> draft-ietf-rtcweb-stun-consent-
> freshness-13
> 
> WFM. I am fine with keeping APIs out of scope for consent document. It 
> will be better to have all APIs in one document and have reference to 
> that where ever applicable.

NEW:

8.  API Recommendations

   The W3C specification [W3C-WEBRTC] 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.
   The mechanism of how applications are made aware of consent
   expiration is outside the scope of the document.

-Tiru

> 
> Regards,
> Ram
> 
> -----Original Message-----
> From: Christer Holmberg <christer.holmberg@ericsson.com>
> Date: Sunday, 31 May 2015 7:08 pm
> To: Bernard Aboba <bernard.aboba@gmail.com>, Harald Alvestrand 
> <harald@alvestrand.no>
> Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
> Subject: Re: [rtcweb] OPS-Dir review of
> draft-ietf-rtcweb-stun-consent-freshness-13
> 
> >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
> >
> >_______________________________________________
> >rtcweb mailing list
> >rtcweb@ietf.org
> >https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb