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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 24 January 2018 08:23 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 78C8512D965 for <homenet@ietfa.amsl.com>; Wed, 24 Jan 2018 00:23:14 -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 wYw8VCRwM09E for <homenet@ietfa.amsl.com>; Wed, 24 Jan 2018 00:23:12 -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 63CA712D847 for <homenet@ietf.org>; Wed, 24 Jan 2018 00:23:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1A925BE38; Wed, 24 Jan 2018 08:23:10 +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 AS632U0ucxnb; Wed, 24 Jan 2018 08:23:08 +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 3E2D8BE2E; Wed, 24 Jan 2018 08:23:08 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1516782188; bh=G1WflpIKCuF7+N2TOoctrCP2ao9KRufKrBLTw6+KgI4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=W9NvLJEoOCNUyPTyuGGwv4TBZ6MLNxdP97qxBqGAG7DBrMZAPBSvgAhwDj2nUoWri vHt0vairAbxVGGJDr4UV2C5DsCUK6sm9qTiQ1yehRYWULJKuhaGHSzxG1JqAhqUk0T CuiSF+Y4yaLRsySzwMHATZLzcaRGyjXj3dup6o64=
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "homenet@ietf.org" <homenet@ietf.org>
References: <cd3042c4-e213-feb2-47ea-00f5fb6ab3ab@cs.tcd.ie> <3348.1516762103@obiwan.sandelman.ca>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=5BB5A6EA5765D2C5863CAE275AB2FAF17B172BEA; url=
Message-ID: <00a33dc6-ad12-3a9b-cdab-086268a45882@cs.tcd.ie>
Date: Wed, 24 Jan 2018 08:23:07 +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: <3348.1516762103@obiwan.sandelman.ca>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="1DmF3Gz4IzfBSAW1OV8i4wdJKXfbLdSgp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/cqT9oz0mJ2ccL-CA3vwYzw0ZrJA>
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 08:23:14 -0000

Hiya,

On 24/01/18 02:48, Michael Richardson wrote:
> 
> Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>     > - Does this sound roughly right or off the wall?
> 
> It sounds right.
> I think that bootstrap of security should become an recharter item in the
> future.  Some kind of BCP on interactions with MUD, SUIT, etc. IN THE
> FUTURE. NOT NOW.

Can you say more? Eg. what would be needed before you think
it'd be sensible for homenet to start work in this space?

> 
>     > 2. We have this milestone in our charter:
> 
>     > "Nov 2018 - Submission of the perimeter security draft
>     > to the IESG as Informational RFC"
> 
> Yes.  Are the authors still engaged?

I'm not aware that we have authors;-( I guess someone could have
volunteered in the past before I was helping out as chair (if so,
please do let us know).

Cheers,
S.

> I think I've missed the last three homenet WG sessions due to conflicts.
> I find that the ML is too frequently ratholed when it isn't silent.
> 
>     > - Does the homenet wg need to profile use of those
>     > security mechanisms, for example to document a way to
>     > establish initial keying material that we'd like to see
>     > implemented when those protocols are used in home networks?
> 
>     > - If so, (and without yet getting into discussions about ToFU
>     > etc) do we have people who are interested in working on
>     > that?
> 
> Yes, but not yet.
> 
> --
> 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;-)