Re: [homenet] Next steps for draft-behringer-homenet-trust-bootstrap?

Russ White <russw@riw.us> Wed, 20 March 2013 12:47 UTC

Return-Path: <russw@riw.us>
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 2C42F21F8F78 for <homenet@ietfa.amsl.com>; Wed, 20 Mar 2013 05:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EiZqoRGCwLBZ for <homenet@ietfa.amsl.com>; Wed, 20 Mar 2013 05:47:35 -0700 (PDT)
Received: from da31.namelessnet.net (da31.namelessnet.net [74.124.205.66]) by ietfa.amsl.com (Postfix) with ESMTP id AB5B721F8C9E for <homenet@ietf.org>; Wed, 20 Mar 2013 05:47:35 -0700 (PDT)
Received: from cpe-098-122-147-095.nc.res.rr.com ([98.122.147.95] helo=[192.168.100.75]) by da31.namelessnet.net with esmtpa (Exim 4.80) (envelope-from <russw@riw.us>) id 1UIIQZ-0004aj-6y for homenet@ietf.org; Wed, 20 Mar 2013 05:47:35 -0700
Message-ID: <5149AFEC.2020009@riw.us>
Date: Wed, 20 Mar 2013 08:47:40 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: homenet@ietf.org
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6ED6C6@xmb-rcd-x14.cisco.com> <5141F140.2070508@mtcc.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6ED79F@xmb-rcd-x14.cisco.com> <5142444E.10105@mtcc.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6EE46B@xmb-rcd-x14.cisco.com> <5142D736.1090008@gmail.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6EE603@xmb-rcd-x14.cisco.com> <51430A9A.7070005@gmail.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6EE696@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6EE696@xmb-rcd-x14.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Antivirus-Scanner: Seems clean. You should still use an Antivirus Scanner
Subject: Re: [homenet] Next steps for draft-behringer-homenet-trust-bootstrap?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 20 Mar 2013 12:47:36 -0000

>>> Before we dive into the solution space, Brian, do you agree that the
>> framework draft should include this requirement?
>>
>> Yes, but I think that simplicity of deployment and management is part of the
>> requirement.
> 
> Absolutely agree!

+1

One thing to think about --what if we just assumed some sort of layer 2
overlay used _only_ for control traffic among all the devices on the
network --or a layer 3 multicast group that was "location specific," in
some way?

A lot of the problems we seem to have here revolve around coordinating
what device is doing what, what services are available, where the edges
are, etc. Maybe if we could figure out a single control channel for all
devices on the network, whether it's by tagging on to the routing
protocol, or by setting up a well known local multicast group, or by
setting up a layer 2 "control channel," or even an "out of band
bluetooth control channel," or whatever, we could make progress using
the existence of a such a control channel as an underlying assumption?

Russ