IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 15 March 2013 11:48 UTC

Return-Path: <brian.e.carpenter@gmail.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 9979621F9159 for <homenet@ietfa.amsl.com>; Fri, 15 Mar 2013 04:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.263
X-Spam-Level:
X-Spam-Status: No, score=-100.263 tagged_above=-999 required=5 tests=[AWL=1.428, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 mptmHnwqcIML for <homenet@ietfa.amsl.com>; Fri, 15 Mar 2013 04:48:33 -0700 (PDT)
Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by ietfa.amsl.com (Postfix) with ESMTP id 29D8521F915B for <homenet@ietf.org>; Fri, 15 Mar 2013 04:48:32 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id 16so2983812wgi.27 for <homenet@ietf.org>; Fri, 15 Mar 2013 04:48:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=cXTQ1sK0JIXKQZor68Lmi0SHwnCRm7hbqjVVD7Tlpw0=; b=Mjsrl0Ny6u4pSe45bhldJQe6VytYh1xfouWkdylv9rBso437G1AhgiT/5SCdp4Kdpi lf0zXDYDjw52d/CiEN3wN5RwAm2ZzkoObl56aHhHFlAGqXGtqpY4XQg+99/n1Go7IWrq 49AlF/TW6a+JgSlo1yNKrY7DY4jHMlNQmvLj9zBCZ+3B2dsQQ5omqXWw955AlHmn8bds t+vMz/afLlg6PBAAfsLMAs6xNxTIXVtncq+8wsQryxnQpNKiiTFrY+nWjXMauCKKYHJO a8cTc+JvC0jRKg95sL5s40Q3TJbfnQDC2r1H1o/zoS8bpMsNBJCaXT6l+ahXFhmECVE5 q8hg==
X-Received: by 10.180.8.4 with SMTP id n4mr2332688wia.13.1363348111238; Fri, 15 Mar 2013 04:48:31 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-188-133.as13285.net. [2.101.188.133]) by mx.google.com with ESMTPS id dm9sm2343652wib.3.2013.03.15.04.48.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Mar 2013 04:48:30 -0700 (PDT)
Message-ID: <51430A9A.7070005@gmail.com>
Date: Fri, 15 Mar 2013 11:48:42 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>
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>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6EE603@xmb-rcd-x14.cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Michael Thomas <mike@mtcc.com>, "homenet@ietf.org Group" <homenet@ietf.org>
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: Fri, 15 Mar 2013 11:48:33 -0000

On 15/03/2013 11:12, Michael Behringer (mbehring) wrote:
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> [...]
>>> But I think the need goes beyond wireless. If I have visitors, I may not like
>> it if they plug in a device into the Ethernet socket in the guest room, and the
>> device has full access to everything. I think we need a simple way to
>> accept/deny a new device onto the network, independent of the media
>> type.
>>
>> And preferably a method that doesn't involve asking your visitor for her
>> MAC address, or giving her a password that you don't want to leak.
>>
>> On the other hand, a Bluetooth-like method that involves opening access
>> for a few minutes while you automatically register the MAC address might
>> be good enough for home use (but unacceptable for professional use).
>>
>> What is unlikely to work in the real world is a complex cryptographically
>> sound mechanism, even though it might be fun to design and debug.
>>
>>     Brian
> 
> 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.

   Brian

v2.23.0 | Report a Bug | By Email