IETF Logo Mail Archive

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

Michael Thomas <mike@mtcc.com> Thu, 14 March 2013 21:43 UTC

Return-Path: <mike@mtcc.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 ABC8821F8530 for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2013 14:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level:
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 qyxCZ7QwIsTp for <homenet@ietfa.amsl.com>; Thu, 14 Mar 2013 14:43:39 -0700 (PDT)
Received: from mtcc.com (mtcc.com [IPv6:2001:5a8:4:9fe0:224:8cff:feaa:6d9b]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB6B21F8263 for <homenet@ietf.org>; Thu, 14 Mar 2013 14:43:38 -0700 (PDT)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id r2ELgclH015356 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 14 Mar 2013 14:42:39 -0700
Message-ID: <5142444E.10105@mtcc.com>
Date: Thu, 14 Mar 2013 14:42:38 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
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>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6ED79F@xmb-rcd-x14.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=677; t=1363297359; x=1364161359; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[homenet]=20Next=20steps=20for=20draft- behringer-homenet-trust-bootstrap? |Sender:=20 |To:=20=22Michael=20Behringer=20(mbehring)=22=20<mbehring@c isco.com> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=FToS22slqPdhk0u2mQPDQ1TmMrMyx3tLDntbWHjBfBk=; b=rgi/w7lfJSqvThMzgi4rGjNSPckvkgDWgy2vGnPgm06OY9Kix24BwNjkA8 bfFmXbDTT+NpK0xTeM2IyYbvIAz6Fs0Jx+fSD709JyDwF5t9hEbC6KwGNrls XlL4Lp65IEUX4GdFEDuXjOg++vRtOPbVWqTiPwZt5rB/sKOnkul/8=;
Authentication-Results: mtcc.com; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; ); dkim-asp=pass header.From=mike@mtcc.com
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "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: Thu, 14 Mar 2013 21:43:39 -0000

On 03/14/2013 10:03 AM, Michael Behringer (mbehring) wrote:
>> From: Michael Thomas [mailto:mike@mtcc.com]
> [...]
>> In today's world access control is gated at L2 via wpa or similar. Are you
>> suggesting that we have a L3 equivalent? In addition? In replacement?
> We need a solution to this problem. I think this is the first important thing to note, and so far it isn't noted (or I missed it). Which solution is open for discussion.
>
> Can we agree thus far?

Well, it seems to me that we have a solution today at L2, at
least for wireless which is the most pressing need. Am I missing
something? Or are talking about remote access into your homenet?

Mike

v2.23.0 | Report a Bug | By Email