Re: [homenet] About Ted's naming architecture presentation and document

james woodyatt <jhw@google.com> Thu, 01 December 2016 20:55 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 BA49F129CB9 for <homenet@ietfa.amsl.com>; Thu, 1 Dec 2016 12:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.896
X-Spam-Level:
X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.896, 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 v_5o-rLU_UYf for <homenet@ietfa.amsl.com>; Thu, 1 Dec 2016 12:55:04 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (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 BFD75129E59 for <homenet@ietf.org>; Thu, 1 Dec 2016 12:45:53 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id 3so98750661pgd.0 for <homenet@ietf.org>; Thu, 01 Dec 2016 12:45:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:message-id:mime-version:subject:date:references:to:in-reply-to; bh=MDwtagofkeaBnpq13a+tBAWwOoo21tz7AhAOSq8vbhc=; b=CVX2w1/gFmaIz3rKoqw8xs2nn9wzhN8/kdsOgXMNMD0w8pPJSELyFbAOV8H0aDEpm/ VvW9RkFUW3UkXRaKgjOLrkK6StLxiuTN3xLlJ8fOchypJHMFUhF39MC5ige56Pc81QBn AoQnFaH/kdi1+KnxvLhk3Lnbt1J2ItF6nN0bIdpsbDgeFHSVYEgPtQHzInp4uj6baxDz 9qIVRk/gsb8m+rOSWpciHLNyj8iprupRNGlPMAgOwe+m+zp+kVt57CgNB7qhO3xWoqMG Q/gCZZR4n9dBPzI8vTGUpOzUbIYdBJHHWhNel4iEu3B6pdE9sRqh1mlx/CiVhP6DwnpY 3KTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :references:to:in-reply-to; bh=MDwtagofkeaBnpq13a+tBAWwOoo21tz7AhAOSq8vbhc=; b=mJ4RL6ffYrua5aqkBhFMdyemG2yxfncS5BYUW8sbtPBTPLME/r7qyjr7168+4aYmi0 jJW/d61VI6FZdln0uknWRSBjv8mJhLMWaYbZzunWlwKK41vE1RXF7WkMwSIMS1E3P7Tf GZwYPeguk8LqNqJxq5jYHtBXYhLlDry2HXn4L+c2GUfGY1oeFZebR2z1KRQ3bCn+CUPL AeBVHQo9C/p8TR8/784KrLiUUU5LaBZ3y3fGd7Fn1n+I+RPgpk22Y6yI71VNO6Wa0W9N 3lKkEtOKRY4H8yo7K5BQw9gabbuRbzqBebrb76+X8/VbOEQFzKi87iet1AS+qm08XNmC c+cw==
X-Gm-Message-State: AKaTC02MpZE7Bib7AQujp1ifqDdbEJ6RlQQqx8FBJaA1o8aLB3rKC/n/xuczInzSAUAPdg8f
X-Received: by 10.84.137.1 with SMTP id 1mr86958192plm.8.1480625152897; Thu, 01 Dec 2016 12:45:52 -0800 (PST)
Received: from ?IPv6:2620::10e7:10:284c:3380:856b:3696? ([2620:0:10e7:10:284c:3380:856b:3696]) by smtp.gmail.com with ESMTPSA id 64sm2252571pfu.17.2016.12.01.12.45.52 for <homenet@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 01 Dec 2016 12:45:52 -0800 (PST)
From: james woodyatt <jhw@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D577E24A-8965-45D9-BB2D-D57A5D915B3A"
Message-Id: <2D8D2C2C-44D4-49CD-B7CB-F5CC011D3E4D@google.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Date: Thu, 01 Dec 2016 12:45:51 -0800
References: <871syc54d1.wl-jch@pps.univ-paris-diderot.fr> <CAPt1N1=eXRBh6UqGGqUSK9cH_jY5MvPcE4MFZUPe2Z48LF7bkA@mail.gmail.com> <87lgwj504t.wl-jch@irif.fr> <CAPt1N1kDCMDBEpt7QYhHtPYjaMJAzw8G81=2y2f=y0ZProeCPA@mail.gmail.com> <13675.1479346312@dooku.sandelman.ca> <3B35AF68-4792-4B2A-8277-A7B49206581F@google.com> <58404736.2010301@globis.net>
To: HOMENET <homenet@ietf.org>
In-Reply-To: <58404736.2010301@globis.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/0FDePbEi0L5s5gS-wUsXOd3jnyQ>
Subject: Re: [homenet] About Ted's naming architecture presentation and document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Dec 2016 20:55:07 -0000

On Dec 1, 2016, at 07:52, Ray Hunter (v6ops) <v6ops@globis.net> wrote:
> james woodyatt wrote:
>> 
>> If anybody is currently shipping, or has announced plans to ship, any kind of home automation device that does this, please speak up on the mailing list. I’d like to calibrate my perhaps mistaken apprehension that nobody would seriously consider doing this. Everyone I know in this field plans to do this by providing a single public rendezvous point with high availability servers that communicate in turn to home automation controllers acting as private clients.
> 
> RFC3724.
> 
> >  End user choice and empowerment, integrity of service, support for trust, and "good network citizen behavior" are all properties that have developed as a consequence of the end-to-end principle. 

Funny. I would have cherry-picked *this* quote from that RFC:

>> These conflicts [between service providers, end users, etc.] will inevitably be reflected in the Internet architecture going forward.  Some of these conflicts are impossible to resolve on a technical level, and would not even be desirable, because they involve social and legal choices that the IETF is not empowered to make […]

> Rendezvous points are themselves an attack vector/ anti-privacy snooping vector/ commercial lock-in/ convenience, depending on your point of view.

Indeed. “Depending on your point of view.” Hence, the quote I picked above as a counterpoint.

> So please let's empower the end user to either "opt in" or "opt out”.

>  <https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
Already done and done. End users are free to “opt out” by not using the products and services that require the use of rendezvous points to facilitate end-to-end communication between home networks and roaming mobile handsets. Alternatively, they may build and run their own bespoke gear that works differently according to whatever optional security method they are managing themselves at the border of their home network. The default we are recommending in the HNCP draft is to turn on the simple security firewall, and therefore require the rendezvous point. Can you blame industry for expecting that most end users will never feel moved to opt out of this convention?


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>