Re: [rtcweb] IP handling: Using mDNS names for host candidates

westhawk <thp@westhawk.co.uk> Tue, 03 July 2018 15:58 UTC

Return-Path: <thp@westhawk.co.uk>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0311D130E66 for <rtcweb@ietfa.amsl.com>; Tue, 3 Jul 2018 08:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 Tjf02opyjakL for <rtcweb@ietfa.amsl.com>; Tue, 3 Jul 2018 08:58:47 -0700 (PDT)
Received: from smtp001.apm-internet.net (smtp001-out.apm-internet.net [85.119.248.222]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E195E12DD85 for <rtcweb@ietf.org>; Tue, 3 Jul 2018 08:58:45 -0700 (PDT)
Received: (qmail 81822 invoked from network); 3 Jul 2018 15:58:43 -0000
X-APM-Authkey: 255286/0(159927/0) 1872
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp001.apm-internet.net with SMTP; 3 Jul 2018 15:58:43 -0000
Received: from localhost (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id D22C918A0512; Tue, 3 Jul 2018 16:58:43 +0100 (BST)
Received: from zimbra003.verygoodemail.com ([127.0.0.1]) by localhost (zimbra003.verygoodemail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0g11gjllbJNv; Tue, 3 Jul 2018 16:58:43 +0100 (BST)
Received: from [192.67.4.84] (unknown [192.67.4.84]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 964FB18A04FB; Tue, 3 Jul 2018 16:58:43 +0100 (BST)
From: westhawk <thp@westhawk.co.uk>
Message-Id: <BA6C07F2-4C2B-482E-B54C-D88C6B5DBF9E@westhawk.co.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A4849746-E438-420A-9545-6023B76A85F4"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Date: Tue, 03 Jul 2018 16:58:35 +0100
In-Reply-To: <CANN+akYYLrmwM5ZuXYSuC0m0ueiF169JjuPZQr5Tb22nQX_QQA@mail.gmail.com>
Cc: Justin Uberti <juberti=40google.com@dmarc.ietf.org>, RTCWeb IETF <rtcweb@ietf.org>
To: youenn fablet <youennf@gmail.com>
References: <CAOJ7v-2FQ3yfyfmFY8MT17nTFUvsNyixKuXXeT-Rq7zVQKBMnA@mail.gmail.com> <092e15c3-3ae8-5b18-1195-498f9cef1488@alvestrand.no> <CAOJ7v-3e8ytXd5NQLYdPyVdiSYDy4kGxQvbEh=_D9Mm0eSLmVg@mail.gmail.com> <CAPcE_Lf5kVoMzid1+Vc=mhGuH9v7nqoSq=TYJE8W9FMfcggKJA@mail.gmail.com> <CABcZeBOSyuOP6E4dreJc_OoxMTqZg-N5J9Gkbp7ygrXQbFd-XQ@mail.gmail.com> <CAOJ7v-3vZH81m9DK9CNmEH3UKTBZT+0f1=uuQdz7ou2JXxeMsA@mail.gmail.com> <CANN+akbH54-05VceqL-rfq+ZURB85LxXFb4_B5KV_6KaLaC=+g@mail.gmail.com> <CABcZeBOCE2sxriCZs=iwe69=fcefa5O5bjD92TNe1q231oTNqw@mail.gmail.com> <CAOJ7v-0KVPC8_FMBjfkqw+wJ6kM_N+pAs04xty=co+gU65CMUw@mail.gmail.com> <9EB00E21-6D1B-4090-B7C4-4C5ADA9E2D44@westhawk.co.uk> <CANN+akYYLrmwM5ZuXYSuC0m0ueiF169JjuPZQr5Tb22nQX_QQA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/eC5i4DP0gjlTJ-On7vtBU-chUMM>
Subject: Re: [rtcweb] IP handling: Using mDNS names for host candidates
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.26
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 03 Jul 2018 15:58:51 -0000


> On 3 Jul 2018, at 16:53, youenn fablet <youennf@gmail.com> wrote:
> 
> If GUM is not used at least once for the lifetime of the page, WebKit is currently using mode 3.
> 
> There is the possibility for a user to grant persistent access to camera/microphone for an origin through Safari UI.
> In that case, the user will no longer be prompted for any page of that origin.
> Mode 2 could be used by default for these pages since user actually opted in.

In one of my workflows that would actually be quite useful. 
We scan a QR to establish an identity pairing, then subsequent connections don’t use the camera
just data and received video.

T.


> 
> Le mar. 3 juil. 2018 à 02:18, westhawk <thp@westhawk.co.uk <mailto:thp@westhawk.co.uk>> a écrit :
> Slightly off topic - but if an origin was permissioned once but does not do GUM on this particular
> page, which ruleset applies ?
> 
> 
>> On 3 Jul 2018, at 00:08, Justin Uberti <juberti=40google.com@dmarc.ietf.org <mailto:juberti=40google.com@dmarc.ietf.org>> wrote:
>> 
> 
>> That's the approach we plan to take in Chrome. There is a substantial amount of datachannel traffic, and a quick calculation suggests that most of that is non-permissioned, so we should be able to measure the effects of this change.
>> 
>> On Sat, Jun 30, 2018 at 5:44 AM Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com>> wrote:
>> I haven't thought about it too much, but I think that I would probably do is an A/B test where I randomly set clients to this strategy or the current strategy and measured success rates, time to connect, and (maybe) some sort of call quality stat. It's not going to be easy because I don't know how much non-permissioned WebRTC there is in the wild.
>> -Ekr
>> 
>> 
>> On Fri, Jun 29, 2018 at 6:06 PM, youenn fablet <youennf@gmail.com <mailto:youennf@gmail.com>> wrote:
>> A draft describing the Safari/WebKit approach is available at https://www.ietf.org/id/draft-mdns-ice-candidates-00.txt <https://www.ietf.org/id/draft-mdns-ice-candidates-00.txt>
>> 
>> Eric, can you precise the kind of information you would like to have?
>> Some testing has been done to validate the approach but I do not think this is representative of the actual state of the affair. Safari/WebKit is not gathering any related statistic.
>> 
>>    Y
>> 
>> Le ven. 29 juin 2018 à 11:10, Justin Uberti <juberti=40google.com@dmarc.ietf.org <mailto:40google.com@dmarc.ietf.org>> a écrit :
>> I believe such data will be forthcoming from the Safari team. We are also working on this.
>> 
>> On Fri, Jun 29, 2018 at 7:03 AM Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com>> wrote:
>> It seems like this is something one could A/B test and measure connection rates. Has someone done so?
>> 
>> -Ekr
>> 
> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org <mailto:rtcweb@ietf.org>
>> https://www.ietf.org/mailman/listinfo/rtcweb <https://www.ietf.org/mailman/listinfo/rtcweb>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org <mailto:rtcweb@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtcweb <https://www.ietf.org/mailman/listinfo/rtcweb>