Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 03 July 2014 06:29 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5C281B278D for <homenet@ietfa.amsl.com>; Wed, 2 Jul 2014 23:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level:
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 r4ueD9ok8Adp for <homenet@ietfa.amsl.com>; Wed, 2 Jul 2014 23:29:00 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE05E1A0AE1 for <homenet@ietf.org>; Wed, 2 Jul 2014 23:28:59 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D16A0A1; Thu, 3 Jul 2014 08:28:56 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1404368936; bh=hDDSFVbU4e5nTFtc/ilCAwYrY4ZOBGmzOSWiOO3ba4Q=; h=Date:From:To:Subject:In-Reply-To:References:From; b=PfqncdYoDElCGt1IF/Ts4Pfqv5wNCNGlAMJDXNtzvf43AnFlRey7TQZn95ihBk1co 51hvmGBcTbwTqRFrAUwCkLGLGH2Mw5jIy12F0ogYzTibXt795oQhqNhihANf/9GKkc Hz2BhXf5BDoRF8bFOP/PKkWsHGxyReQTRZX4P1dc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id C90FB9F for <homenet@ietf.org>; Thu, 3 Jul 2014 08:28:56 +0200 (CEST)
Date: Thu, 3 Jul 2014 08:28:56 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <7F29FBCE-1308-425A-85ED-3B10DC554C66@gmail.com>
Message-ID: <alpine.DEB.2.02.1407030822070.19077@uplift.swm.pp.se>
References: <CADZyTkk6rUuFJ5Wds2hioBBQa9-kXDJxyg_gBGQ1R6u5CHF2Ww@mail.gmail.com> <87fvij5wdw.wl.jch@pps.univ-paris-diderot.fr> <7F29FBCE-1308-425A-85ED-3B10DC554C66@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/uIwgLNDlyx2AL3nRhus5kNfzIfY
Subject: Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 03 Jul 2014 06:29:02 -0000

On Wed, 2 Jul 2014, Douglas Otis wrote:

> In essence, especially because ULA address use was ignored by the mDNS 
> proxy scheme, anything reported by mDNS that is routable is to be 
> published into DNS as a means to establish a routable unicast 
> alternative to that of mDNS.  One major downside is this will end up 
> including devices never intended to have direct access from the 
> Internet, where things like an All-in-One printer or baby monitor may 
> find themselves.  Use of a ULA addressing space offers a locally 
> routable alternative without exposing these devices to the Internet. 
> Unfortunately, many in the homenet wg consider this to be a problem to 
> be resolved by the device rather than the homenet protocol.

Personally my thinking has been that the service discovery mechanisms and 
how wide the service discovery information is propagated (and wherefrom 
and who has access to the services themselves), would be up to policy in 
the homenet CPEs.

I have always envisioned a "control panel" for the home, where (new) 
devices pops up, and the user has to set up roles or equivalent for these 
devices, and the roles control how these devices and their services should 
be handled.

I would like to see a lot of this complexity done at the CPE (or a 
"homenet controller") and not in the individual device. The "controller" 
would own the policy settings that the user interacts with using for 
instance a smartphone app and/or a web page.

I have been meaning to write down use-cases and examples of my thoughts 
but I have not done this yet, but I should in the near future.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se