IETF Logo Mail Archive

Re: [rtcweb] Security implications of host candidates

youenn fablet <youennf@gmail.com> Wed, 04 July 2018 21:12 UTC

Return-Path: <youennf@gmail.com>
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 423EA130DE2 for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2018 14:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kELPX61GqGIA for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2018 14:12:38 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA3CE130DC0 for <rtcweb@ietf.org>; Wed, 4 Jul 2018 14:12:37 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id l16-v6so5249301lfc.13 for <rtcweb@ietf.org>; Wed, 04 Jul 2018 14:12:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZA1GgNCRpOukiatcTesNXjn2I9sJAY4HZgLWtf7MgVE=; b=U5SoCT+L7jdkRIF+UO+gd1VW8MJtyjpZTISN79yvdeBk6p4zuV2Xefkjyb7Lc5KF5D goRIvLEy1nZufid5t/SBSkpLHv7+KYe4NBfVMDQ4q12VSMlMg1+v4LPOv32ntBuNfxPj +MDozkSMIHNWHPWisEUrn7ZXb5IEw0G512aJVFiERngeEFwR6K9gEWHnZzDZBF/JhTpV ABKaaKACIYdhK44NwOnUD1e4OgLkVkKCG+k1wjEM7mUFQILal4vaw6A0CrOxMVkp24N4 Ki7NRj2H9qxunZnzDHjImDYkHtIVbZAD9zLS43UQ4Z79AbOU2MkpsU2poJslBYWpzDps JJrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZA1GgNCRpOukiatcTesNXjn2I9sJAY4HZgLWtf7MgVE=; b=KAFdGuBWssgMUdE7r7nsmkLnq2BCZoUwQ4WAODlzzPN4Cnmc5AMElFsMMKzIHQ88JT won3ga+XJRkDHmS5oquLVFnEdRDDCoKmvxW1IERQMlIdpw8RmpGYfHNuiswrTty8VIjn 8XIB8nTxHZ4FQiei00MLxlWlnXa2rApQGaWus9uApRbzGn6qnbj4MSsKLKgFbXIAolpA opy9pWqzWv7egeNnl9zACzL+/V+ksJWqEoqnAogU5PEJH/we8iAoJezwXir5obOGCPWu Cm/m523OAy88WtdjyvN0yl+W5KsbSRJ/G6akkljglO+IeHvi+lEWG6J/yimHvyfrCkRe owiQ==
X-Gm-Message-State: APt69E1Liv6dO7zlpiMeM6baMo5rZqAGeGgAw6gOw4gI/RjdVm1zVoJy AdzNMmeYH/4RipquZ7PS60LMl/pS+m4+Pt4xjZA=
X-Google-Smtp-Source: AAOMgpepiylOhPsSiLM/JYhnR2j2/7jSa6FGhPLPiQBQijaOPEGnLFcaJbLPTp6tdVHKxoY4hklJzkHY2Af8g3jgwao=
X-Received: by 2002:a19:9646:: with SMTP id y67-v6mr2378006lfd.130.1530738755960; Wed, 04 Jul 2018 14:12:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAOJ7v-1t_BDEEHmA4eqiS9ksYOOyHUz9LFLhQxs8FhjTdswP5w@mail.gmail.com> <CANN+akZLRdZdexjU44zPCA6vdQR0hVYT17_4P8DefC0JbRL5mA@mail.gmail.com> <CAOJ7v-2JdiMJ9iWE_cL8G7xDM6iekexJL8KLEbz0jD=p7hiGZg@mail.gmail.com> <CANN+akbv2mpyhgV5vxDHKcsA8UPsSEr0bEjJK4xYxtvbkXNA7w@mail.gmail.com> <CAOJ7v-3gHMCxHU02YG3NoqvWHtXgOSWSm+y88GNDW0qc=Sqq=A@mail.gmail.com> <CAOJ7v-3moUqwgxkz1Fek4vy-XV+WpDaO-PsQZEw4ougoCHjLww@mail.gmail.com>
In-Reply-To: <CAOJ7v-3moUqwgxkz1Fek4vy-XV+WpDaO-PsQZEw4ougoCHjLww@mail.gmail.com>
From: youenn fablet <youennf@gmail.com>
Date: Wed, 04 Jul 2018 14:12:24 -0700
Message-ID: <CANN+akZ=Ebw41mA2wEX7-4u6q5WcZbFtM=VMLX4nDK39S=QGOQ@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: youenn fablet <yfablet@apple.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cb0634057032e30a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/vWo_y5kLxt2zB42MpJ9jXKAqK5c>
Subject: Re: [rtcweb] Security implications of 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: Wed, 04 Jul 2018 21:12:41 -0000

Le mar. 3 juil. 2018 à 14:40, Justin Uberti <juberti@google.com> a écrit :

> Updated fiddle (outputs to display as well as console):
> https://jsfiddle.net/juberti/x7a8ut0q/37/
>

Right, this shows the local loopback latency.


> On Tue, Jul 3, 2018 at 11:16 AM Justin Uberti <juberti@google.com> wrote:
>
>> I wasn't able to get that example to work (tried with 2 Chrome and 2
>> Safari instances, got a setRemoteDescription error both times), but I was
>> able to make a JSFiddle <https://jsfiddle.net/juberti/x7a8ut0q/25/>
>> which does something similar in a single page. At present, even host-host
>> connections were seeing a 2 ms RTT, possibly because of the clamping
>> <https://developer.mozilla.org/en-US/docs/Web/API/Performance/now> that
>> has been applied to performance.now() to deal with Spectre et al.
>>
>
I updated
https://evening-thicket-98446.herokuapp.com/src/content/peerconnection/datachannel-b2b/,
it should hopefully be more intuitive to use this time:
1. load the page in one device
2. load the link provided by the page on another device
3. click 'call' on the first page
4. a latency value should appear on the page and be continuously updated

v2.23.0 | Report a Bug | By Email