IETF Logo Mail Archive

Re: [saag] BOFs about IoT firmware update and TEE configuration

Hannes Tschofenig <hannes.tschofenig@gmx.net> Sat, 18 February 2017 16:17 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 684641294AD for <saag@ietfa.amsl.com>; Sat, 18 Feb 2017 08:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 7psZCZSFWdOr for <saag@ietfa.amsl.com>; Sat, 18 Feb 2017 08:17:20 -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 9A8381294A1 for <saag@ietf.org>; Sat, 18 Feb 2017 08:17:19 -0800 (PST)
Received: from [192.168.91.175] ([195.149.223.239]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M4Gyx-1cOPl31d91-00rtCT; Sat, 18 Feb 2017 17:17:14 +0100
To: Eliot Lear <lear@cisco.com>, saag <saag@ietf.org>
References: <16c236b7-dd80-1e27-8de9-16f05558d38e@gmx.net> <dbc93119-3128-64e0-b6b0-1a0e87e95f90@cisco.com>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <1da45f12-7999-6a9e-3649-2ffea4d50511@gmx.net>
Date: Sat, 18 Feb 2017 17:17:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <dbc93119-3128-64e0-b6b0-1a0e87e95f90@cisco.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="3rGUct50h63CBaJ7r2lItJ806xAQPxJ6p"
X-Provags-ID: V03:K0:RuooEaQghX8wc/5SkFnFYXZLwEFuLgYDlQ/+9QPuRdT6T/ahcJ3 3yj3VbhFaUdXItSyl2YHDEsqKZseHi9d1dj11LEZXIKbGqhzjNU6cELIhqMudbiv0TSrZ0D ESzHNFtkJ0+uxoNm1Swgjr5v7lXy7qVw8tDEg80K7AL/TA5aWH/IxOiZmMtZvlAXhc3mv2o jtECxmcLc7X/Lq4tE3Pww==
X-UI-Out-Filterresults: notjunk:1;V01:K0:39deIRF2L8I=:qshQDiYRY2e3ll+2h4ckF3 S7GwCit/IRwuwnAb65fJmG6hoDfLpvY2wTOJ4cVBEw7JCIO//e6wV1/1smQCP0kBJnHzVPLTh XIxW85KhMEhiHVvafB8UzPs4ZwctB7F25iMneP1GEgZQhp7lfkS0lkOpeZNUL0H8NIZKO6VAr /TP1KilRKjzqyySlX0avFhJKlueQi7TQrQvNCjJx7YsX/kA0MPukSBszSWFsr9VdReED9oCYW iuT1wjGKT77kYSV/w/+KJdiobYZLaFUqzjI/H8oZa5QaXBRD4OsaWtc3RiRu0MwNrDDELxODf nhejOYRJW4HT9P7xSRJj9++/64ItcwrVIA3FVqbZHUeNvDhG5Glc7Geg3z8M8JVVvN46+GeA7 45jm1p+qZgOJR80beGTbrXwVkBtrmUMtQFUFfYq+CxVZjTAc9YYZRcrapAmRqVPyEhd+r8y9r vDHdduW/OothHra9LCI/omnFre/LAPhPTi61gmPB2bQhX1nnEHGsaE2XDz/8GKWSdK2Rd5WXr I//+QZr/2q2klgCeGsp8ZxVHkoYlitMi6TI1Pw9oao3Z9w/AUdaXnofxAh4gHn+ZRxENLPabO Q0p4ymIW0CYXzjk9tIKwqT3SygUw1zO6xwCKV6mXXqKFERuHXNF0cogpClpxaFFwUSXtifwks TeJwsZt+OK5ERP3pk/b7hcn24L+FxRl9jUlZKTk71B6B3dBJdEq9nQV9o7GSHQeG5t48h5Zqm kZ1/5jquxxcVzrLSsf6K7KFNxWqwhqTak96DeWCTItIJHBCC3pTCzakVz4E=
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/hPQNJYX2GVGkfhBFB_tFnMjxcs0>
Subject: Re: [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: Sat, 18 Feb 2017 16:17:21 -0000

Hi Eliot,

I actually don't know since I never understood the ANIMA work all that
well due to its fuzzy scope. I suspect that you can answer the question
better than I do.

Ciao
Hannes

On 02/13/2017 02:29 PM, Eliot Lear wrote:
> Hannes,
> 
> Can you say a few words about how TEE compares to
> draft-ietf-anima-bootstrap-keyinfra (et al) which has been in
> development in a WG for quite some time?
> 
> Eliot
> 
> 
> On 2/13/17 12:51 PM, Hannes Tschofenig wrote:
>> 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
>>
>>
>>
>>
>> _______________________________________________
>> saag mailing list
>> saag@ietf.org
>> https://www.ietf.org/mailman/listinfo/saag
>

v2.23.0 | Report a Bug | By Email