IETF Logo Mail Archive

Re: [rtcweb] Review of draft-ietf-rtcweb-mdns-ice-candidates

youenn fablet <youennf@gmail.com> Fri, 28 September 2018 05:01 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 EF97E12F1AB for <rtcweb@ietfa.amsl.com>; Thu, 27 Sep 2018 22:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 vmuVy2EyXzgh for <rtcweb@ietfa.amsl.com>; Thu, 27 Sep 2018 22:01:56 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 AC467130DC3 for <rtcweb@ietf.org>; Thu, 27 Sep 2018 22:01:55 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id r191-v6so3994917lff.2 for <rtcweb@ietf.org>; Thu, 27 Sep 2018 22:01:55 -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=PpXq8AVVJbq2bDBCTUt1uzF7PYWeoh/tnufhbz10y70=; b=Im5+zwoQ3uDrTWhcSxh+Oyf7kGTqdGy6qs1m1JoeDH0TRVsArkk67dVGAE/RiWxFbX c3xNmO6kdP2K1PhULoL4LW5AP8uvJF8Gy6NbgTMwhHgMoWPSg9eoe5nS5a4YBXBsNkDg NckqaaapF5ZY9d6SyFKYNkM3wl8Ejz9j/Lu8VlSD6CfAYVf48Gb77tZmfgeLP4tGEZDH Y4ovURxSGdZKIKBwYu00KxE4LjiJoeaV1HxVjE8fp3SD1AzAh6oKkq+WCmDuTdhx/5vS +fzMGqcSc7UfmJKXqlKnkCwh529pP4GOOgdFPNnfMMIAoWpEEugfOLC1+nQL5AsI70Rm xZow==
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=PpXq8AVVJbq2bDBCTUt1uzF7PYWeoh/tnufhbz10y70=; b=XejTqXaI61DRW0GsBmnMdohFoA0kPG3oHmW6b0FpDeSRiBSGZmb7qMbdxPMDwBwcgM OP3eLxYZY8XF24aAl+O71YlOXSlFd6list3uQ+CfcmK8ljSSovOSVj6ABjb3UNO9Vts9 8sdX2U63iRhpJfTImaza4Fdz+/TERuIfetOX5gloVS7mdlhY1K8uHMS/Hb0wWdZX998q 6z0Y48LRqzO7vN4icAQin9RGBiHPAjfRrDEWDSt/qh7ntDYtN8dOYCIORW/7sL+bHoVN JGMQ4YjmHhGDDABwwaxCmQXv6koPad/rPWigBo7YxGygSvsJfEP1VTPQG1F+IEU0FWlN WYGQ==
X-Gm-Message-State: ABuFfoihOWn+3LErR3ydquSvmwABAIH4dzOaffo6UL6qCwlhqBNjHrob NUC9uocU2qmMhInZ/6/kvhcLhI4uZALMAtztp9wGQQ==
X-Google-Smtp-Source: ACcGV60kACnKZdEAudswf7Qz3M0C9Fa4DChCmJY1OgcpNKiHTGjBxIRQWxtF/nJwB+gkAFk8LXvvwHby5FyUdi/ABUQ=
X-Received: by 2002:a19:1346:: with SMTP id j67-v6mr9158512lfi.93.1538110913463; Thu, 27 Sep 2018 22:01:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAOW+2dtkNjzS0DkD37SD=POtC2Nd6Xe=upyjvVoyBnnMw7qwbQ@mail.gmail.com> <CANN+akb1S=eJNhSOT-e6R1yn_u20nuZNwDFEK7S90ksJ3wt95A@mail.gmail.com> <b890dedd-9f32-890f-3719-5c0c8ffa8345@gmail.com> <CANN+akZtT7dtcCLgLW9AQy+ZFuDHXxJFNxikPGBQCf7Duy0sug@mail.gmail.com> <CAOJ7v-0qTc-Qig_39fNhQiz=LV69MPDVC=jskeBVXoz=ANa2vw@mail.gmail.com>
In-Reply-To: <CAOJ7v-0qTc-Qig_39fNhQiz=LV69MPDVC=jskeBVXoz=ANa2vw@mail.gmail.com>
From: youenn fablet <youennf@gmail.com>
Date: Thu, 27 Sep 2018 22:01:40 -0700
Message-ID: <CANN+akZYpj4KS=HoN6T78Pu5=F56GQCPsrMexepH8pYey2iYAw@mail.gmail.com>
To: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009f495a0576e75a01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/lOMVAs71OTG7TdQu5fzGavUkM50>
Subject: Re: [rtcweb] Review of draft-ietf-rtcweb-mdns-ice-candidates
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 28 Sep 2018 05:01:59 -0000

FYI, we are tracking the feedback from this thread and last IETF meeting at
https://github.com/youennf/mdns-ice-candidates/issues.
   Y

Le jeu. 27 sept. 2018 à 16:10, Justin Uberti <juberti@google.com> a écrit :

> I suggest that we hold off on assessing what this might mean for data
> channel and related applications until we have data from browsers showing
> the actual connectivity/traffic impact of mDNS.
>
> We should have initial data on this topic from Chrome by EOY.
>
> On Mon, Sep 24, 2018 at 10:14 PM youenn fablet <youennf@gmail.com> wrote:
>
>>
>>
>>> Perhaps its feasible for those use cases where the administrator is
>>> already aware of the software but definitely not for small applications
>>> such as sharedrop.io, Threema Web whose main use case is the direct
>>> connection in same network environments and its significant benefits
>>> regarding throughput.
>>>
>>
>> I agree this is the most likely scenario where host candidates are
>> actually useful: two web browsers doing pure data channel on a
>> managed/complex network, and no coordination between the network admin
>> being and the app.
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>>
>

v2.23.0 | Report a Bug | By Email