IETF Logo Mail Archive

Re: [rtcweb] RFC 6520 vs. draft-ietf-rtcweb-stun-consent-freshness-00

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 27 November 2013 08:02 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 5D0111ADEA6 for <rtcweb@ietfa.amsl.com>; Wed, 27 Nov 2013 00:02:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 qE7Uj87MyD39 for <rtcweb@ietfa.amsl.com>; Wed, 27 Nov 2013 00:02:32 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 80B231A1F3D for <rtcweb@ietf.org>; Wed, 27 Nov 2013 00:02:31 -0800 (PST)
X-AuditID: c1b4fb32-b7f388e0000057e0-e6-5295a716e0db
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.125]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id EF.C7.22496.617A5925; Wed, 27 Nov 2013 09:02:30 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.73]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0328.009; Wed, 27 Nov 2013 09:02:29 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [rtcweb] RFC 6520 vs. draft-ietf-rtcweb-stun-consent-freshness-00
Thread-Index: AQHO6tMo2ZLY49xAXES3ooOpoMHDbpo4sR6g///zrwCAABNW8A==
Date: Wed, 27 Nov 2013 08:02:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1C55D48D@ESESSMB209.ericsson.se>
References: <CEAB0083.6FBE3%rmohanr@cisco.com> <5285E318.3090006@ericsson.com> <BLU169-W10885AF717BCBB60830502093E60@phx.gbl> <CABkgnnVpikDFwzfc=6CnHDOb6rmoe5-54AdYPyrbRvU34Epfig@mail.gmail.com> <BLU169-W11416B2C0D42888C078A7F493E60@phx.gbl> <913383AAA69FF945B8F946018B75898A2426E369@xmb-rcd-x10.cisco.com> <CABkgnnU5RqbF-PPtihGU+rtuqemN9f7N7nXLB05_OpF7EmhxjQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C55D40B@ESESSMB209.ericsson.se> <913383AAA69FF945B8F946018B75898A2426EF4D@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A2426EF4D@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.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyM+Jvra7Y8qlBBm/naVqsePKIxeLamX+M Fmv/tbNbnNi9jdGBxWPK742sHjtn3WX3WLLkJ5PHl8uf2QJYorhsUlJzMstSi/TtErgyNj0+ z17wmLnix+t5LA2Mv5m6GDk4JARMJC7+1upi5AQyxSQu3FvPBmILCZxglJg5WbmLkQvIXswo sW3eFxaQejYBC4nuf9ogNSICyRIv/31iB6lhFljAKHF69UoWkISwQIBE78J3LBBFgRKtDxey Q9hOEk3XpzOC2CwCqhKH2vrAbF4BX4mdf1awQizrYpHY+LEBLMEJlJjwdAcriM0IdN33U2uY QGxmAXGJW0/mM0FcLSCxZM95ZghbVOLl43+sELaixNXpy6HqdSQW7P7EBmFrSyxb+JoZYrGg xMmZT1gmMIrNQjJ2FpKWWUhaZiFpWcDIsopRsji1uDg33chALzc9t0QvtSgzubg4P0+vOHUT IzDeDm75bbSD8eQe+0OM0hwsSuK811lrgoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwVovF au7JYN8Ux7I5+9Gqvx6KDvLia4ytxLy+V8WK2552UedbqTJ/p8Y8YduwH69bsjYsNj3Xs7sp cIngxSU/he88uhvp9PJ75I2FWr0hiQVLb/j5sXSunxMqPWOhufvvH8FVWddvnP7hVBPX+13M YSGXpnvvsu4TWw9aPXXiPinTG6/x/l+JEktxRqKhFnNRcSIAhGVyx4UCAAA=
Cc: "draft-ietf-rtcweb-stun-consent-freshness@tools.ietf.org" <draft-ietf-rtcweb-stun-consent-freshness@tools.ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] RFC 6520 vs. draft-ietf-rtcweb-stun-consent-freshness-00
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, 27 Nov 2013 08:02:33 -0000

Hi,

>>> [1] and [2] can be solved by mandating WebRTC endpoints to support consent.
>> 
>> I thought we were going to do that anyway - no matter what consent 
>> mechanism we use.
>
> If DTLS based consent mechanism is picked then both peers must support DTLS heartbeat and willing to exchange DTLS heartbeat request/response.

How is that different from using ICE for consent? That also require support from both peers, doesn't it?

Regards,

Christer

v2.23.0 | Report a Bug | By Email