IETF Logo Mail Archive

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

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Mon, 01 June 2015 06:01 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 64B7E1A88C7 for <rtcweb@ietfa.amsl.com>; Sun, 31 May 2015 23:01:13 -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 K3s86hSCmqEU for <rtcweb@ietfa.amsl.com>; Sun, 31 May 2015 23:01:11 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 756781A88BE for <rtcweb@ietf.org>; Sun, 31 May 2015 23:01:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1775; q=dns/txt; s=iport; t=1433138472; x=1434348072; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=QMo8BLFJCL9ACqXt6YYKxsrKZC+z+Ash4E3fvLe/2B4=; b=HCBCIsiq9U5mnFLDhsDjai1F5GWtTq1CKMIfRZ0Lpi3teafAjvvdyLAX 0TtEHbvFo5uFay6MpvlViIwZKBpv/MGczIs1DpsNTSQjm6eDCn7OWTBOg oNrjDLJN3IBDKtDQI3LtDDBRtgqni1iCn+iaeLm2RV+aN2grm1VdMKECc A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0APBQB09GtV/4MNJK1cgxBUXgbAHwqFLUoCgSVMAQEBAQEBgQuEIgEBAQQBAQE3NAsMBAIBCBEDAQIfECEGCx0IAgQBDQWIGAMSDdARDYR2AQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSLQ4JNgWFYBwaEJwEEkwqJOYFZkC6HBCNhgxdvgQRCgQEBAQE
X-IronPort-AV: E=Sophos;i="5.13,530,1427760000"; d="scan'208";a="16375139"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-8.cisco.com with ESMTP; 01 Jun 2015 06:01:11 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t5161Ad1019877 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 1 Jun 2015 06:01:10 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.78]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0195.001; Mon, 1 Jun 2015 01:01:10 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.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: AQHQnDBb22/gwedzA02iXYPQWliciA==
Date: Mon, 01 Jun 2015 06:01:09 +0000
Message-ID: <D191F31F.32336%rmohanr@cisco.com>
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>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D873AEB@ESESSMB209.ericsson.se>
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: [173.39.66.102]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6E53443F8D162643873555C838EEE5AF@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/nHFAVuuk2E4JRH_ys2R1lTB4iAU>
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 06:01:13 -0000

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.

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

v2.23.0 | Report a Bug | By Email