Re: [homenet] support for HNCP in IPv6 CE routers

james woodyatt <jhw@google.com> Fri, 27 October 2017 21:03 UTC

Return-Path: <jhw@google.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 C629E13F5D1 for <homenet@ietfa.amsl.com>; Fri, 27 Oct 2017 14:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 2nFxaGSV-tbR for <homenet@ietfa.amsl.com>; Fri, 27 Oct 2017 14:03:35 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 E920F13871A for <homenet@ietf.org>; Fri, 27 Oct 2017 14:03:34 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id 134so15397405ioo.0 for <homenet@ietf.org>; Fri, 27 Oct 2017 14:03:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=BLlG/9I/DsPykjmKGRNZCKyMdfJoAdtH53fjzI5LyuE=; b=gwnEYdKfCYkT4m59BdlzbSoc+KG/Oc09HPINb2uc9K30ev3YYhDZQgqBZDSt7pj4kp JbOec33nKPdjJBbRPXyJK0xZN3t/8HThiIA6krsU4htrQxJ6Qhg9K8G0TvI57y/3lGdE A16Hv0CP6KUXtGq4gkDn+retd/B4N4B0v4W2rLqt028UKTKA0sI6aGadwLIgA5tds4Uj 9Rh+IQWuffpzfGnXwQ2qEEFs7eHJTSg/+juBrRCDlVn3Sx96KnQC8239A9EsR+I6Ehwm 7lV8SwXZqDYJIg+Vk3GH4ew+ZyQ9Spo2n+LNNVfIF7bLvu2tvQXsErmyU4kjJyo9vz3G Biiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=BLlG/9I/DsPykjmKGRNZCKyMdfJoAdtH53fjzI5LyuE=; b=EbpX+nWMR8ieUrB+ceLxpZ8KcQirWR+kXrLY0Mj0rfCY2PQqGI1H1FyAsOePyNDYKJ ZjCk6BFflI8Dxor8HeYnLfhMyMYjMfxyjr691bp7sVF5971MOkWxV47kQga2AeIK5Y1c nyNpl9263ayVUIt8vbi0XE/0ViUuIOx7VH6mXoklO5l7AOYOn9N3mK1rGch42RQn2plB g1AsXeMMt1VgghgaVIKO6EgVK/Q832MdijEwr/7kj9+uK3v43tEqleib1+ljCcklZ7vc FCdYScIF2NGyjfqp+xbhaejyoYQXZhUJmHa5qEfSd6Xcwq2OMOfL+VwZLh8jDFvoDK/n M/vw==
X-Gm-Message-State: AMCzsaUpJHrwh3FqFJ0Ma8aKosgrrOOpAbNsFCF5DwFU4BR6CT2LiNRL CrODoUKyw+fSZ2QKNks0f4e7d58JfXo=
X-Google-Smtp-Source: ABhQp+ShRHs2mgoN1/pDnaUaniC0Y/PerxKnaHv8UAjd7qQvYUXpN4QpGI2lpw/JJjdF5eehU5jF3w==
X-Received: by 10.36.80.14 with SMTP id m14mr2414069itb.148.1509138213774; Fri, 27 Oct 2017 14:03:33 -0700 (PDT)
Received: from ?IPv6:2620:0:10e7:7:c048:bfa9:aa30:da1d? ([2620:0:10e7:7:c048:bfa9:aa30:da1d]) by smtp.gmail.com with ESMTPSA id t69sm1374443itt.37.2017.10.27.14.03.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Oct 2017 14:03:33 -0700 (PDT)
To: Juliusz Chroboczek <jch@irif.fr>
Cc: homenet@ietf.org
References: <80D10C70-9411-48EE-8189-87E9401D7F22@consulintel.es> <FFB4541F-0BDB-4D5F-B6BB-647EFD0FE27E@google.com> <20171024140034.GS45648@Space.Net> <7iwp3i3pev.wl-jch@irif.fr> <63640f24-f178-2fe7-7c1f-e2680496b733@google.com> <20171026183952.GI45648@Space.Net> <9cfd149e-fb08-22ed-3fa9-9a1786a2a95d@google.com> <8737652ao1.wl-jch@irif.fr>
From: james woodyatt <jhw@google.com>
Message-ID: <f04db4ae-28cc-8189-03d5-c05042667d30@google.com>
Date: Fri, 27 Oct 2017 14:00:35 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <8737652ao1.wl-jch@irif.fr>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/cr_akI34fVRJkcCnwDxc2LVmZtc>
Subject: Re: [homenet] support for HNCP in IPv6 CE routers
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 27 Oct 2017 21:03:37 -0000

On 10/27/2017 02:38 AM, Juliusz Chroboczek wrote:
>> The protocols we are developing here in HOMENET are for the tiny minority
>> of people who prefer to build their own home networks instead of just
>> plumbing their ISP directly up to every device in their home.
> 
> I think you're underestimating normal people, James.

Bear with me please.

> I do not remember the last time I've been in a flat that didn't have:
> 
>    - an ISP-provided CPE;
>    - a network-connected media playback device (either a Windows machine or
>      a gaming console connected to a large);
>    - a WiFi network with a password that's shared with the guests.

It's worth noting that in the vast majority of cases like you describe, 
the CE router provided by the ISP is only serviceable by the provider, 
or if it *is* serviceable by the subscriber, the serviceability is 
ridiculously tortuous and very limited.

 From the perspective of most "normal" subscribers, that Wi-Fi network 
with the password they share with guests is a service provided by their 
ISP, and it's *not* something they build themselves. I've lost count of 
the number of homes I've visited where the Wi-Fi network and its 
password were configured by the installer technician who pulled the 
cable, and never reconfigured after that.

People who like to build and operate their own home Wi-Fi network seem 
to be a very weird and obscure minority, even in the more utopian parts 
of Europa and not just the barbaric deserts of North America and elsewhere.

 > At least over here, there definitely is a market for non-trivial home 
networks

Indeed, and I think there is definitely a case for IETF establishing 
standards for how to use Internet protocols in them, as HOMENET is 
doing. What I don't think is helpful is gating our development of those 
standards on the predicate that ISPs should have anything to do with it. 
That way lies near certain complete failure.


--james