[saag] BOFs about IoT firmware update and TEE configuration

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 13 February 2017 11:51 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 135BE1295FC for <saag@ietfa.amsl.com>; Mon, 13 Feb 2017 03:51:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 vTHvNcVzP8ix for <saag@ietfa.amsl.com>; Mon, 13 Feb 2017 03:51:47 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0662B129509 for <saag@ietf.org>; Mon, 13 Feb 2017 03:51:46 -0800 (PST)
Received: from [192.168.91.173] ([195.149.223.239]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LeuUB-1c35Xs3LZ9-00qf36 for <saag@ietf.org>; Mon, 13 Feb 2017 12:51:43 +0100
To: saag <saag@ietf.org>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <16c236b7-dd80-1e27-8de9-16f05558d38e@gmx.net>
Date: Mon, 13 Feb 2017 12:51:42 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="ub4Vwe5a8oA4qKHxoQ7HNwGvXpbFWcIPc"
X-Provags-ID: V03:K0:O/EgKz9hbcr62ebx/LMJ4lMydEDgUKgA5W2URS2MwOwzltZHwjo 9+kW0MeX3qC8x8lJyLEyZv+DqtHLSdWxi1qjL1KeWXWetV2Y/l94l11ldbbfvFJrFl+rsLT KcFhOMzUg94Q1X3MFtyWyt+3nhIkGfuCN7umaOosV13LZEed17ge1CcByttsvcm6ob5IUdi kF+FA+xPjdvx1QhtDOK5Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:KU6ffav+l7c=:P7WEohMb+Usvj8mudONI/m uz6WEPZj7C+ej9Zp8fgWYxVEcpkpuLsPq8IOXyDWLX5LeUxtl4AjT08+jjtE0XFaDKT/COfFJ 0lL8vnLgvfMwk9i+UhgKqLkfuTGWjmKTY66kIDOr6XHhuXnaDzbpMhg3eodSBLcW55BiQnXGZ e+bjrXt97JHRHfJYo0l7SW/O9na5P5+mpJmfIRqwnyGYxBrddGc9QbGSElDq7/UVv02bAtWr2 waUuCqb91VtCMpWhM8GkuzOE+n9oqWshxzYaimNas2DqFeTwS5AAfuLY1iVTbpSr/OvBViqi5 5Fg2tTR9d0R3L+u8q+Azi1FnCtBxhBgKcclkxW0vzkTWGAHQ1wQkoSnaEwOjrTSRRzpnK/9va 7FbmpadIG10FleqY0iGO8V4fqsRn6wiLVmhSEb/8MZ0u1Jl9WSc3v7GNV5zShM3HJ1cJ63spC iVRtnTxoOQx04SdCyjVe/WnPq/QITuYhVXHgm6IL0KiBr5TSvPNUCpivSsFgkr3R9RQ+e2n7y IAbCgj3h+4mB0FWahaMgtNi6RlCBDafooG4aXyzOSJhUSRk67mJ+A3kuVirBQhJ3DbVfNlZ3R 8OmoOl56RLNw9wFssk/zYRd1qLlM3P56v1DQTP9u0pwwMPt6KRLpM25SzmunsKBXx7jrcxqF2 jBtcHPf26TvhJlXy4+sxdtR0AVjG06Rh9S1+J3b9ha19D50d4tAtr+pjmb0B55UBpIJjPf3d7 yw28Idbtq97Fo2IdkB0/UfTGb805Qun7J9p7y1iXukejeQuQHId4ZTrdI8U=
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/j8mtSFp_MqeMUkOW84Y5sQDBlew>
Subject: [saag] BOFs about IoT firmware update and TEE configuration
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 11:51:49 -0000

Hi all,

we have proposed two security-relevant BOFs for the upcoming meeting.
They are listed on the BOF Wiki page at
https://trac.tools.ietf.org/bof/trac/wiki but I still wanted to briefly
introduce them to you

** “Firmware Update Description (FUD)”

Last year we had a workshop organized by the IAB on firmware updates for
IoT devices (see https://www.iab.org/activities/workshops/iotsu/) where
we talked about various challenges and gaps.

As a follow-up to the workshop we would like to initiate some
standardization activity in this area.

The mailing list can be found at
https://www.ietf.org/mailman/listinfo/fud


** “A Protocol for Dynamic Trusted Execution Environment Enablement (TEEP)”

This BOF is about an application layer security protocol that allows to
configure security credentials and software running on a Trusted
Execution Environment (TEE). Today, TEEs are, for example, found home
routers, set-top boxes, smart phones, tablets, wearables, etc.
Unfortunately, there have been mostly proprietary protocols used in this
environment.

With this BOF we are making an attempt to standardize such a protocol. A
strawman proposal of such a protocol has been published with
https://tools.ietf.org/html/draft-pei-opentrustprotocol-03.

The mailing list can be found at:
https://www.ietf.org/mailman/listinfo/teep




Ciao
Hannes