Re: [homenet] number of devices in homenet
Daniel Migault <daniel.migault@ericsson.com> Wed, 12 June 2019 02:49 UTC
Return-Path: <mglt.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C33D31200B4 for <homenet@ietfa.amsl.com>; Tue, 11 Jun 2019 19:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 Vr8pUdHi9A9U for <homenet@ietfa.amsl.com>; Tue, 11 Jun 2019 19:49:10 -0700 (PDT)
Received: from mail-qt1-f170.google.com (mail-qt1-f170.google.com [209.85.160.170]) (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 97E46120089 for <homenet@ietf.org>; Tue, 11 Jun 2019 19:49:10 -0700 (PDT)
Received: by mail-qt1-f170.google.com with SMTP id 33so8927056qtr.8 for <homenet@ietf.org>; Tue, 11 Jun 2019 19:49:10 -0700 (PDT)
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=YNSCmheDgu/+9/yUFqR+81z0gWbfQL4UfByHCRPfrtU=; b=TsO4vm39qflV8rzReglsFDVlCuGgIlkHu83X1o3ddi0ZIl2lmmvtk/MeQsJ1EZ1Z+f KGWntgl3WzExj9z6cibY0dPQABrp5mE3Hj0WmNHALEoiAK6umHDlWJ0ZS1SBaS8c7LSp 7dHySdFWTZJWZiz+9G8rlq4H5Udc92WD50FJQHuEJRX8Fh73O9qIlVRn0tTK+4gKuTKy 5MjX9OxW+GeDFf4sDjN80L+sygjh9EV9grrpKJzc2ihupNAyaUKZ4tR9amN5NciWgJKW oUy1YgXEgDwU1/wnZbQ/MllnbSx90smTvM2dUn8cmEr9dyngP/3FCN6m1+9qqUbvuXLc EUTQ==
X-Gm-Message-State: APjAAAUh3vgbmdDs4P7FyDsUbhvFli+IQIDLzWqyzrmXL/+F3Zrcnx/5 +QV+1rZJmql7MCS5leCehRvXEDHr/3BbIDlSQhInAYVJ
X-Google-Smtp-Source: APXvYqw8b5JO/Zc9M8oSmfm4yUDqRakZB0GixT+ALQUM53ptnsIHQPahc/lwVV1MG67eXOGVgsVbDs4Ndk6udcVDp+k=
X-Received: by 2002:ac8:3613:: with SMTP id m19mr66513313qtb.193.1560307749586; Tue, 11 Jun 2019 19:49:09 -0700 (PDT)
MIME-Version: 1.0
References: <CADZyTkkgd8f49V+yoZvPZXx3b-_YRzpgUY1-obroq9QMLnFWNw@mail.gmail.com> <878su8fj24.wl-jch@irif.fr> <2348.1560261275@localhost> <87ftofwqut.wl-jch@irif.fr>
In-Reply-To: <87ftofwqut.wl-jch@irif.fr>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Tue, 11 Jun 2019 22:48:58 -0400
Message-ID: <CADZyTk=Zaj9NJgKjt_Nd0DqJDObkSz6dRrOO0t_zRsem9=c4TQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet <homenet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000278ae1058b17758b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/AaenRPpWU6kxrbVKRpToHGSH64U>
Subject: Re: [homenet] number of devices in homenet
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2019 02:49:13 -0000
Hi Juliusz, I believe the answer is similar to [1]. Regarding the number of devices we expect, it seems hard to have exact prediction, however, if we do not make it possible this number will likely remain zero. We need to make it easier to have more devices. Currently services mostly send private data to the cloud, and data is accessed through a service hosted on that cloud. While service provider have their own interest in doing so, it is also quite hard for individual to set a service in the homenet and be able to access that service. It is easy to export the video of your video camera on a public cloud, it is much difficult to be able to access the vdeo camera from outside. This is something we need to change. Video camera, all sorts of sensors, light controls... there is no special need these data goes outside your homenet. I believe the number of devices can become quite large. I also believe that 2 would be sufficient to justify not configuring things more than once. Yours Daniel [1] https://mailarchive.ietf.org/arch/msg/homenet/NCbU4XHh0tk8HAowH5rcGEB3fOo On Tue, Jun 11, 2019 at 9:11 PM Juliusz Chroboczek <jch@irif.fr> wrote: > Dear Michael, > > >> Please see my unanswered e-mail of 21 November 2018. > > >> > https://mailarchive.ietf.org/arch/msg/homenet/vz1kdCJISN6UPNZpj9ZD4e8EdwQ > > Thank you for your detailed reply. I'm glad we're finally having > a discussion about my objections to Daniel's proposal. > > > We strongly believe that the HNA needs to know the list of names in > > order to be able to answer for those names when there is unstable (or > > no) Internet connectivity. > > > Otherwise, applications and people have to know two different names for > the > > service. (A public one for when away, and the .local one) > > That's a good point. While I happen to believe that it's reasonable to > have a service known as "boombox.local" from home, and > "boombox.jch.example.org" from the Internet, this might be inconvenient > for e.g. smartphone users. > > > o the credentials for the dynamic DNS server need to be securely > > transferred to the hosts that wish to use it. This is not a > > problem for a technical user to do with one or two hosts, but it > > does not scale to multiple hosts and becomes a problem for non- > > technical users. > > I think that's our main disagreement. > > For some reason, you guys seem to be assuming that the average user will > want to publish hundreds of names in the global DNS. > > However, none of the end-user services that I know use incoming > connections require a name in the global DNS to function (WebRTC, Skype, > online games, BitTorrent, remote desktops, BTSync/Resilio, syncthing). > Thus, my assumption is that the typical user will want to publish exactly > 0 public names, and that only the extreme geek will publish up to 3 or 4 > (music server, NAS, game server, web server with family photographs). > > Richard, Daniel -- please be so kind as to explain why you think my > assumption is wrong. How many names do you envision wanting to publish in > the public DNS, and for what purpose? > > -- Juliusz > > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet >
- [homenet] securing zone transfer Daniel Migault
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] securing zone transfer Ray Bellis
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] securing zone transfer Ted Lemon
- Re: [homenet] securing zone transfer Ray Hunter (v6ops)
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] securing zone transfer Ted Lemon
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] securing zone transfer Mark Andrews
- Re: [homenet] securing zone transfer Juliusz Chroboczek
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] [EXT] securing zone transfer Jacques Latour
- Re: [homenet] [EXT] securing zone transfer Ted Lemon
- Re: [homenet] [EXT] securing zone transfer Michael Richardson
- Re: [homenet] securing zone transfer Juliusz Chroboczek
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] [EXT] securing zone transfer Ted Lemon
- Re: [homenet] securing zone transfer Juliusz Chroboczek
- Re: [homenet] [EXT] securing zone transfer Daniel Migault
- Re: [homenet] number of devices in homenet Daniel Migault
- Re: [homenet] [EXT] securing zone transfer Ray Hunter (v6ops)
- Re: [homenet] securing zone transfer Ray Hunter (v6ops)
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] securing zone transfer Ted Lemon
- Re: [homenet] webauthn for routers (was: securing… MIchael Thomas
- Re: [homenet] webauthn for routers (was: securing… Michael Richardson
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Michael Richardson
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] securing zone transfer Juliusz Chroboczek
- Re: [homenet] securing zone transfer Juliusz Chroboczek
- Re: [homenet] securing zone transfer Michael Richardson
- Re: [homenet] securing zone transfer Ray Hunter (v6ops)
- Re: [homenet] webauthn for routers Michael Richardson
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] securing zone transfer Juliusz Chroboczek
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] webauthn for routers Ted Lemon
- Re: [homenet] webauthn for routers Michael Thomas
- Re: [homenet] [EXT] securing zone transfer Ray Hunter (v6ops)