Re: [Iot-directorate] IETF107 prep call agenda thoughts
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 10 March 2020 14:26 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: iot-directorate@ietfa.amsl.com
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB77F3A13C5 for <iot-directorate@ietfa.amsl.com>; Tue, 10 Mar 2020 07:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] 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 oSnyRCgRvnTN for <iot-directorate@ietfa.amsl.com>; Tue, 10 Mar 2020 07:26:24 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32B703A13CE for <iot-directorate@ietf.org>; Tue, 10 Mar 2020 07:26:23 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B42EF3818F; Tue, 10 Mar 2020 10:25:08 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 84C25825; Tue, 10 Mar 2020 10:26:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: =?us-ascii?Q?=3D=3Futf-8=3FB=3FQXJpIEtlcs OkbmVu=3F=3D?= <ari.keranen@ericsson.com>, IETF IoT Directorate <iot-directorate@ietf.org>
In-Reply-To: <27955.1583800689@localhost>
References: <18010.1583534730@localhost> <1242AF17-F61B-488F-A77B-2F9E8C2AFB6F@ericsson.com> <27955.1583800689@localhost>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.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: Tue, 10 Mar 2020 10:26:20 -0400
Message-ID: <7428.1583850380@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/cUTAXughredVYv6wiJuJ8S0Um0Q>
Subject: Re: [Iot-directorate] IETF107 prep call agenda thoughts
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for the IoT Directorate Members <iot-directorate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-directorate/>
List-Post: <mailto:iot-directorate@ietf.org>
List-Help: <mailto:iot-directorate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2020 14:26:27 -0000
Ari, please confirm the IoT DIR meeting is starting in 30 minutes. {Given North American DST change, I am not 100% certain I got the right thing} IoTSF paragraph: The UK IoT Security Foundation held a 1-day conference, the IoT Security Conference just after IETF106. There were a lot of interesting things presented. In particular, an under-appreciated aspect of IoT security relates to partner abuse. While devices can be used for spying, but a deeper problem is that people often "outsource" their device setup to another person, and it is difficult to be sure that the device has been "rekeyed" when that relationship ends. There were presentations on BRSKI, SUIT, remote attestation (including an interesting use of a shared ledger). IoTSF held their quarterly plenary meeting February 13, outlining some structural changes to how IoTSF organizes work. Supply Chain Security has become a very important process. IoTSF has a building security WG, which has created four stakeholder groups: Facilities, Manufacturers, Owners and Integrators. IoTSF has a residential/security document which specifies an architecture, but the document is not moving forward at this point. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Iot-directorate] Webex meeting invitation: IoT D… Ari Keränen
- [Iot-directorate] IETF107 prep call agenda though… Michael Richardson
- Re: [Iot-directorate] IETF107 prep call agenda th… Ari Keränen
- Re: [Iot-directorate] IETF107 prep call agenda th… Michael Richardson
- Re: [Iot-directorate] [E] Re: IETF107 prep call a… Chakrabarti, Samita
- Re: [Iot-directorate] [E] Re: IETF107 prep call a… Ines Robles
- Re: [Iot-directorate] [E] Re: IETF107 prep call a… Chakrabarti, Samita
- Re: [Iot-directorate] [E] Re: IETF107 prep call a… Nancy Cam-Winget (ncamwing)
- Re: [Iot-directorate] IETF107 prep call agenda th… Ari Keränen
- Re: [Iot-directorate] IETF107 prep call agenda th… Michael Richardson
- Re: [Iot-directorate] IETF107 prep call agenda th… Stephen Farrell
- Re: [Iot-directorate] IETF107 prep call agenda th… Ari Keränen
- Re: [Iot-directorate] IETF107 prep call agenda th… Michael Richardson
- Re: [Iot-directorate] IETF107 prep call agenda th… Ari Keränen
- Re: [Iot-directorate] IETF107 prep call agenda th… Ari Keränen
- Re: [Iot-directorate] IETF107 prep call agenda th… Michael Richardson