Re: [homenet] security work items - what do we want to do?
Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 24 January 2018 23:28 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
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 99E1612D82E for <homenet@ietfa.amsl.com>; Wed, 24 Jan 2018 15:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 wjNrw5XqLGLE for <homenet@ietfa.amsl.com>; Wed, 24 Jan 2018 15:28:49 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F82F12D82D for <homenet@ietf.org>; Wed, 24 Jan 2018 15:28:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 29C53BE4C; Wed, 24 Jan 2018 23:28:47 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pE-7Axgb1JE1; Wed, 24 Jan 2018 23:28:45 +0000 (GMT)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 99587BE49; Wed, 24 Jan 2018 23:28:45 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1516836525; bh=Ky7qLKO14YKq5QemXRYp9egGO0gme1sUcMw8xv283M8=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=ibJ5dnQM57PGv4m1eO/8P0AJDveXYkNoNRzYxwBo4PDMhayKWt/eyYsDOEkXq0+qS x5dh0etp3okQFhjtVTgnFvRtMlKU29UgAshSSiMGGh06fi5q2ZpRRayn/ZS2KuEN8z BaccZMBvRMgtCVQKNJ6GarwZFnAfbHoNZ0kYEZWc=
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Ted Lemon <mellon@fugue.com>, "homenet@ietf.org" <homenet@ietf.org>
References: <cd3042c4-e213-feb2-47ea-00f5fb6ab3ab@cs.tcd.ie> <3348.1516762103@obiwan.sandelman.ca> <00a33dc6-ad12-3a9b-cdab-086268a45882@cs.tcd.ie> <10646.1516800778@dooku.sandelman.ca> <f2102db2-87b5-eae8-b2c0-aa13ba6fc6c1@cs.tcd.ie> <9F46C0C4-8092-4504-913E-8AA8666E7D65@fugue.com> <530976ef-479d-2a1a-1cc3-64a1ca2c143e@cs.tcd.ie> <A669D7BD-D4C7-479F-BEA9-BEF0B1C7C02D@fugue.com> <361154ea-3af8-25b0-aab6-972fdba17815@cs.tcd.ie> <27690.1516821666@obiwan.sandelman.ca>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=5BB5A6EA5765D2C5863CAE275AB2FAF17B172BEA; url=
Message-ID: <7ed65e80-0246-be11-b432-de62f0de9b4c@cs.tcd.ie>
Date: Wed, 24 Jan 2018 23:28:44 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <27690.1516821666@obiwan.sandelman.ca>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="LLGI8KUP15uSi5zO7I0VvcVFm16nFok59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/B6PZ40kVFVBHU-7LsfvpOAS2yeA>
Subject: Re: [homenet] security work items - what do we want to do?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 24 Jan 2018 23:28:51 -0000
Hiya, On 24/01/18 19:21, Michael Richardson wrote: > > Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > On 24/01/18 15:36, Ted Lemon wrote: > >> Yes, enrollment is the process by which trust is established. Google > >> home has an example, but it's rickety. It's actually not too bad for > >> actual Google devices, but the third party enrollment process could > >> really benefit from some open standards (imho). > > > While I don't disagree with you, I do still wonder if we'd > > not be better off using another term for cases where maybe > > all that are involved are a couple of routers in the home, > > and where there's no external party, such as google in the > > example you give. > > If you are suggesting we should write a clear problem statement with > new-fangled and terminology devoid of historical baggage, and then argue > about that for 6-10 months... well... we could start that now :-) You are entirely correct that I'm not suggesting that:-) > Two routers exchanging some keys on a TOFU basis might qualify as (mutual) > enrollment, as the keys are stored someplace for the "second use". Sure. OTOH, using the term enrollment I think might confuse folks and perhaps the discussion as there's quite a bit of (mostly PKI;-) baggage associated with that term, for me anyway. Aside from terminology the main thing is the distinction between situations that do, or do not, involve a party external to the homenet, which makes a very big difference. Cheers, S. > > Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > Without a chair hat on, I'm not sure that some of those > > other bits of work need to be fully finished - if we know > > what kind of keying that'll be used in the final results, > > we could make some progress, but I do agree we'd need to > > the reason I said that things should be finished, is because I believe that a > 3/4 year problem statement discussion will distract the WG from actually > finishing that existing work > > -- > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- > > > -- PGP key change time for me. New-ID 7B172BEA; old-ID 805F8DA2 expires Jan 24 2018. NewWithOld sigs in keyservers. Sorry if that mucks something up;-)
- [homenet] security work items - what do we want t… Stephen Farrell
- Re: [homenet] security work items - what do we wa… Michael Richardson
- Re: [homenet] security work items - what do we wa… Stephen Farrell
- Re: [homenet] security work items - what do we wa… Michael Richardson
- Re: [homenet] security work items - what do we wa… Stephen Farrell
- Re: [homenet] security work items - what do we wa… Ted Lemon
- Re: [homenet] security work items - what do we wa… Stephen Farrell
- Re: [homenet] security work items - what do we wa… Ted Lemon
- Re: [homenet] security work items - what do we wa… Stephen Farrell
- Re: [homenet] security work items - what do we wa… Ted Lemon
- Re: [homenet] security work items - what do we wa… Juliusz Chroboczek
- Re: [homenet] security work items - what do we wa… Michael Richardson
- Re: [homenet] security work items - what do we wa… Michael Richardson
- Re: [homenet] security work items - what do we wa… Stephen Farrell
- Re: [homenet] security work items - what do we wa… Andrew Sullivan
- Re: [homenet] security work items - what do we wa… Michael Richardson
- Re: [homenet] security work items - what do we wa… Juliusz Chroboczek
- Re: [homenet] security work items - what do we wa… Stephen Farrell