IETF Logo Mail Archive

Re: [rtcweb] WG Last Call for draft-ietf-rtcweb-stun-consent-freshness

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 29 August 2014 07:20 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 777C91A0672 for <rtcweb@ietfa.amsl.com>; Fri, 29 Aug 2014 00:20:51 -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 qehHeHKUWCua for <rtcweb@ietfa.amsl.com>; Fri, 29 Aug 2014 00:20:50 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B39A91A0677 for <rtcweb@ietf.org>; Fri, 29 Aug 2014 00:20:49 -0700 (PDT)
X-AuditID: c1b4fb2d-f793d6d000005356-31-540029cfc51f
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id EC.60.21334.FC920045; Fri, 29 Aug 2014 09:20:48 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.136]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0174.001; Fri, 29 Aug 2014 09:20:47 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Thread-Topic: [rtcweb] WG Last Call for draft-ietf-rtcweb-stun-consent-freshness
Thread-Index: AQHPwIhKn1GSXc7NQ0qIq+/SSCMFtZvheJWAgAAB7QCAABscAIABAUuAgAA/XoCAADZ6AIAEJH4Q
Date: Fri, 29 Aug 2014 07:20:46 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D431848@ESESSMB209.ericsson.se>
References: <CA+9kkMCZT1XW4LLaJ4Nq2DbrxD59cYnjLo5JXn9fjEb8pyamaQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D41CDC3@ESESSMB209.ericsson.se> <CAKz0y8zycsyr9m4BA=-8xOaWkU+Sog5Mbz7K-oN3woqi++mVzg@mail.gmail.com> <53F451CF.10705@alvestrand.no> <001b01cfbc94$fccd5310$f667f930$@co.in> <CAKz0y8zNM3rc3XC6JqrK+d4hXiT5TomhNM+W2twg0+-83-pFow@mail.gmail.com> <CABkgnnUnfB5bskH4zWRfBMdHbSoqftV5Fo_GEXoLt9XCH9Tt_w@mail.gmail.com> <CAD5OKxsT9Vdm0=tjk9WsLAH4ekbAizgyjm--168TrOf8UAYGZw@mail.gmail.com> <CABkgnnXUpibu8kWYmbJJJT2J3RNGXFV8LbceLijgG0U-pGY2xQ@mail.gmail.com> <CAKz0y8z_oBf2efavfOLgzqE1R8sZstefZ1tvwwJLkhRskXZERQ@mail.gmail.com> <CAD5OKxsSqA=cki_fSaqAPP0GXCv_kHr6571C+K9ze4ceHCGYdQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D427B68@ESESSMB209.ericsson.se> <D01D6B42.104F8%rmohanr@cisco.com> <009001cfbe4f$6b92f280$42b8d780$@co.in> <CAKz0y8y3=0_-jwWiviR_Uj6tSq75NEq92Ocergc_NvFk2h_72Q@mail.gmail.com> <CAD5OKxugaPq=cLppPUqT8CUADV-E2zDMcz6m3sUgKOnK-TdQfQ@mail.gmail.com> <CABkgnnU6kv+=jQuxj4Ci-zYW9mHEfJ=6jqqrdqDTopPN06-kgw@mail.gmail.com> <CAD5OKxu=9X2um+EebZzp3isY-R_-NqyOgH+bWj55+_Q8qXfrqg@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17828E52F5F0@US70UWXCHMBA02.zam.alcatel-lucent.com> <CABkgnnUNk=QMFtGH3ZvD0V3B6OwSjcsOmaQU5+gcQ5wg9yo7aA@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17828E532F45@US70UWXCHMBA02.zam.alcatel-lucent.com> <CAKz0y8wS93GbA-HrW9mMr=RsrTFVXTsV1=F14enNwYJ2Grfbnw@mail.gmail.com> <CABkgnnVGe_CPHrh7VL_H0STs7x3COW1w54xu=hsZSD=j-vHqCA@mail.gmail.com>
In-Reply-To: <CABkgnnVGe_CPHrh7VL_H0STs7x3COW1w54xu=hsZSD=j-vHqCA@mail.gmail.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+NgFnrHLMWRmVeSWpSXmKPExsUyM+Jvje4FTYYQgyMvWC2unfnHaPFns5/F 2n/t7A7MHjtn3WX3WLLkJ1MAUxSXTUpqTmZZapG+XQJXRmvDE+aCK+wVvw7YNTDOZuti5OSQ EDCROH3vDyOELSZx4d56oDgXh5DAUUaJ7taZUM4SRomrjWuAHA4ONgELie5/2iANIgIJEjdu TWEHsZkF1CXuLD4HZgsLBEos/vmLFaImSGJa50xmkFYRgSiJthWxICaLgKrElA0FICavgK/E so4YiEXfuCU+nDrAAtLJCTRl/ucdYBMZgU77fmoNE8QmcYlbT+YzQZwsILFkz3lmCFtU4uXj f6wQtqLE1enLoep1JBbs/sQGYWtLLFv4GqyeV0BQ4uTMJywTGMVmIRk7C0nLLCQts5C0LGBk WcUoWpxaXJybbmSsl1qUmVxcnJ+nl5dasokRGEEHt/zW3cG4+rXjIUYBDkYlHt4F9/4HC7Em lhVX5h5ilOZgURLnXXRuXrCQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGxnXLy0/MV00X1OMz cj0+TfLlulj3ksgLObN/fmm0vXB2j4Z5dkW/xIv/Qv4KZYqrqkSTal+cl+TxaN1dKJzlv1R3 y9zHSVqGTyqnS9+63cR8ptjLvoJ58lnLXfOd2cteLtx4uN/zwvl7n244Hjlzq3yGbXvXos0/ 1cPUOgTUzX0q802cPz7IV2Ipzkg01GIuKk4EADPu2/6BAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/DVdRfpqnqRUk7HCBpIhL-apwooQ
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] WG Last Call for draft-ietf-rtcweb-stun-consent-freshness
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: Fri, 29 Aug 2014 07:20:51 -0000

Hi,

>> Consent freshness is applicable to any WebRTC entity supporting full 
>> ICE. A WebRTC browser/device as defined in the transport and overview 
>> drafts support full ICE, so perform consent freshness. The 
>> requirements for other WebRTC entities, including WebRTC gateway, is 
>> yet to be fully specified, and the document that specifies them would 
>> also specify whether they support full ICE or not (and hence whether they perform consent freshness or not).
>
> Actually, that's probably the best approach: note that this applies - and can be useful for - any ICE implementation.  And leave 
> it at that for this document.  The transports or security docs might make some statements about mandating this mechanism.

As long as the WebRTC entity supporting full ICE does not assume that the remote WebRTC entity (e.g. a WebRTC gateway) also supports full ICE (read: won't perform consent freshness).

Regards,

Christer

v2.23.0 | Report a Bug | By Email