IETF Logo Mail Archive

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

james woodyatt <jhw@google.com> Thu, 26 October 2017 18:32 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 3302213F5EA for <homenet@ietfa.amsl.com>; Thu, 26 Oct 2017 11:32:48 -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 XpMlkV-mb-yS for <homenet@ietfa.amsl.com>; Thu, 26 Oct 2017 11:32:46 -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 A647A13F448 for <homenet@ietf.org>; Thu, 26 Oct 2017 11:32:46 -0700 (PDT)
Received: by mail-io0-x244.google.com with SMTP id j17so7465256iod.5 for <homenet@ietf.org>; Thu, 26 Oct 2017 11:32:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=eWImjdqgzYU1UDK8YJEm8Rn1A0KguT2Q64eW1zRCY+M=; b=gymE7TyGT9VUQS8t1QE7gk3ATGwnSFhc1wjjP060lsMEm3qLsLrU6MbqkBIS4Rry/H aDjfHSi/0R0Abl9VCI1mN2Ukz7YD+Rn4TfNFTjXJUfQM4vW5C6FxNl82wxTd1E5aJDOE ckzdOr9nlcUiRGA3QccA903wpDSaL8yUsA+nCpxKZ4Eof6Y2B9G+JNDYheY9mWyKlsN5 RbiyVkhT5xyeTXE5ObvIKoxzRZdkvnTBI6k2qKLtiAERN0+uUG1VpdHYL6yaHFRdDPDN kSKCpCS0/0PgoWV0sUcoWRUkBqZzzbYDt47vsQ9VPQpanwk9aehVwhIqQLPkl5FwffP8 xaGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eWImjdqgzYU1UDK8YJEm8Rn1A0KguT2Q64eW1zRCY+M=; b=L71USS2tcgdMYYFnXq285nT0E6igPkZVaBSLKVKkDS+T2e+1MC8niFnPhJYLDquOU3 GceUfkCw618A7ugb3ad4/C95E4o2onGrw5nwXGb2vfRsAflKvekUWwlVxCgQif4kisis qTYOqKpAOagLrhnYsxrnL1pgf2Xs5CXw/KoD4WKC4g63pEWJSCRImBJeklXyN0Jp1BrL g/4IFlY2iR45ZDimQyAbtplPnddHf5DqZchttH6IA3ml2lHpgchsghh9meo0Atb9fcqg NYyqWyNyxf4l8UVgVGDv57UkiP1mEDUCe5TDNhQ2rTzl1TPGnBZkrRoh7dO2B6tiHk3B 2gCw==
X-Gm-Message-State: AMCzsaWg97xj+Fnjrq6Kocr5vnjfevPUroxuOsSybYXN09oMY8sqFiAh Zk85FP3m1VJ+uVmELiV9ZsRfIfkoHaQ=
X-Google-Smtp-Source: ABhQp+Tfft/b721f29gnEYDcrfrrpWJM+l5RjE9+pzy3IWZVXPofxyjVJmSczb8MmRetKGSabhtRhQ==
X-Received: by 10.36.44.76 with SMTP id i73mr3963502iti.41.1509042765605; Thu, 26 Oct 2017 11:32:45 -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 t3sm2558304ioa.3.2017.10.26.11.32.44 for <homenet@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Oct 2017 11:32:45 -0700 (PDT)
To: 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>
From: james woodyatt <jhw@google.com>
Message-ID: <63640f24-f178-2fe7-7c1f-e2680496b733@google.com>
Date: Thu, 26 Oct 2017 11:32:44 -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: <7iwp3i3pev.wl-jch@irif.fr>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/mQfngw3AfYc4u8mwKK5fEjn_5so>
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 18:32:48 -0000

On 10/26/2017 08:22 AM, Juliusz Chroboczek wrote:
 >On 10/24/2017 07:00 AM, Gert Doering wrote:
 >>
>> I find the model of "there is a CPE, and behind that CPE, I connect
>> another router to get homenet functionality" a bit unsatisfactory.
> 
> I think there are two possible deployment models.
> 
> 1. The « My Friendly ISP » model [...]
> 2. The « My Home, my Castle » model [...]

I agree.

> Note that the « My Home, my Castle » model is more general, since it can
> implement the « My Friendly ISP » model by co-locating the EHR and the
> CPE.  I don't think the opposite is true -- once you've leaked HNCP data
> to the ISP, there's no way to unleak it.

Moreover, I don't believe there are any ISPs that are interested in the 
"My Friendly ISP" model at this time. And I would further contend that 
the word "friendly" is doing some rather Orwellian political work in 
that construction.

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.


--james

v2.23.0 | Report a Bug | By Email