Re: [homenet] security work items - what do we want to do?

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 24 January 2018 19:21 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 BC5FE1272E1 for <homenet@ietfa.amsl.com>; Wed, 24 Jan 2018 11:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 zt8x973Z6-kS for <homenet@ietfa.amsl.com>; Wed, 24 Jan 2018 11:21:12 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B17C1271DF for <homenet@ietf.org>; Wed, 24 Jan 2018 11:21:12 -0800 (PST)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id BB1C920094; Wed, 24 Jan 2018 14:26:51 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 41C3180A6A; Wed, 24 Jan 2018 14:21:06 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: Ted Lemon <mellon@fugue.com>, "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <361154ea-3af8-25b0-aab6-972fdba17815@cs.tcd.ie>
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>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 24 Jan 2018 14:21:06 -0500
Message-ID: <27690.1516821666@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/MNg2QlR8Sk1Kwam58CHGSJ9rkjI>
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 19:21:14 -0000

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 :-)

Two routers exchanging some keys on a TOFU basis might qualify as (mutual)
enrollment, as the keys are stored someplace for the "second use".

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 =-