Re: [homenet] support for HNCP in IPv6 CE routers
james woodyatt <jhw@google.com> Thu, 26 October 2017 22:53 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 145A913A1F4 for <homenet@ietfa.amsl.com>; Thu, 26 Oct 2017 15:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_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=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 g8fEDDJZNUUv for <homenet@ietfa.amsl.com>; Thu, 26 Oct 2017 15:53:35 -0700 (PDT)
Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 84A67139F44 for <homenet@ietf.org>; Thu, 26 Oct 2017 15:53:35 -0700 (PDT)
Received: by mail-io0-x244.google.com with SMTP id j17so8852242iod.5 for <homenet@ietf.org>; Thu, 26 Oct 2017 15:53:35 -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=xdIDtCJLoV9Vi19nQUxgQjG8JUNep4g0Z+vCK6LJdUM=; b=CMY7Za/ibYBKyDJ3vw6+AcPi7yYb8PlGY+aDiAauJBfmns/24S1IaGbpyEvHQXdvDg ote6oB78Mb7PD4/cpWgz3k86ziRjmffn/CL/pybLWqWwteLdSpylYiYVXxuetTzDrLU2 2b371EgkBncJ6usENV83fEtSd68Ajk2brGezhvCZxsAdQ6kamUMamRGmAjC+L89KOs+j 0PjE0likZTCU12n3u46+QBKBo1TcZ/OF1tl1WB9WHtBzZGKuxmFTyWtr3c6akzsop6cd WMlbgD6iLGukPR92HyR+97I2pbbSfTbfciDOYwBTWY+OYqgtfELAy9Gx4rzbhE8NU03h vBHQ==
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=xdIDtCJLoV9Vi19nQUxgQjG8JUNep4g0Z+vCK6LJdUM=; b=Ip/ad21AY74JHk5CoersFbse494e25ZJ5/yhm/jHwZtnHnNB79+C2lWYneIlEciIDu QMpBH77eFvGgpFVl8bYJzQ6m0kM3XXJZTbvDE4/4h5HjOL5jQxt+7wFpbYQvYtPn4zWr QlxBzglftdIsz/gFQ2Xxv3hmNRkmmE0EXGUlvTUFxesl5GK0vXKirSq8m6HLS+h0POUD /j8kjbOm8F6vKrDye/c2WW+XrkpY80EDmRPI0lgWeSOY5YKcIe3/4Pm6l6Nf5PbmJrU4 ecVAvY3XxjuuycJPbjxd9XBUrwKrPk/KXHmMUBZj1E2+Q5PbLxAp1aBF0YC363hGbFt8 CARQ==
X-Gm-Message-State: AMCzsaVTMthkxlT+vks5qGIFK8BGlv5XdUxO/KI6GfUK3nphcVjoofLs wVfwreIYy2m2jbRG28DWC8zFbkDWR4Q=
X-Google-Smtp-Source: ABhQp+Rx3hdbInRs/CiLgCFzcDFhetaDALs8DNZRh85tDElcE4FZBEunlluj4er5pk6jPhlEaLSZAA==
X-Received: by 10.36.185.94 with SMTP id k30mr772678iti.2.1509058414413; Thu, 26 Oct 2017 15:53:34 -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 j193sm203673ita.9.2017.10.26.15.53.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Oct 2017 15:53:33 -0700 (PDT)
To: Gert Doering <gert@space.net>
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>
From: james woodyatt <jhw@google.com>
Message-ID: <9cfd149e-fb08-22ed-3fa9-9a1786a2a95d@google.com>
Date: Thu, 26 Oct 2017 15:53:32 -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: <20171026183952.GI45648@Space.Net>
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/4E6yjeHowKuF5zINvMJVDlleIhg>
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: Thu, 26 Oct 2017 22:53:37 -0000
On 10/26/2017 11:39 AM, Gert Doering wrote: > On Thu, Oct 26, 2017 at 11:32:44AM -0700, james woodyatt wrote: >> Accordingly, I strongly recommend that HOMENET dispense with the "My >> Friendly ISP" model with extreme prejudice, and adopt what I shall call >> the "HOMENET Castle Doctrine" as a matter of working group policy. > > I claim that this is a sure way to kill homenet from being ever deployed. I would counter that relying on ISPs to adopt a HOMENET standard is certain to fail. They have already demonstrated that they will block any revision to RFC 7084 that calls for adopting even HNCP, much less the rest of the HOMENET protocol stack. If you want to kill HOMENET, then make it a predicate that ISPs have to adopt it. That will ensure it goes nowhere at all. > "Normal" People just don't buy a second router for their ISP link if they > already have one, or a 3rd and 4th one if they happen to have two ISP > links. > > So, what do we think a future home network for normal people is going to > look like? I think "normal" people don't even want to buy the 1st router for their ISP link. What they want to do is have the ISP link go straight to their internet-connected device. Like a smart phone does. When you buy a new device, you buy a new ISP link for it. 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. To facilitate that model, the HOMENET Castle Doctrine, I think we'll make its audience-- as well as ISPs-- happier, if we code our standards to the greatest common denominator of ISP linkage, then facilitate building HOMENET as a platform into which ISPs have zero visibility. --james
- [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Timothy Winters
- Re: [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers Gert Doering
- Re: [homenet] support for HNCP in IPv6 CE routers STARK, BARBARA H
- Re: [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers Michael Richardson
- Re: [homenet] support for HNCP in IPv6 CE routers JORDI PALET MARTINEZ
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Michael Richardson
- Re: [homenet] support for HNCP in IPv6 CE routers Juliusz Chroboczek
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Gert Doering
- Re: [homenet] support for HNCP in IPv6 CE routers David Oran
- Re: [homenet] support for HNCP in IPv6 CE routers Ted Lemon
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Michael Richardson
- Re: [homenet] support for HNCP in IPv6 CE routers Gert Doering
- Re: [homenet] support for HNCP in IPv6 CE routers Juliusz Chroboczek
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt
- Re: [homenet] support for HNCP in IPv6 CE routers Juliusz Chroboczek
- Re: [homenet] support for HNCP in IPv6 CE routers james woodyatt