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

Eliot Lear <lear@cisco.com> Mon, 13 February 2017 13:29 UTC

Return-Path: <lear@cisco.com>
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 E93F2129576 for <saag@ietfa.amsl.com>; Mon, 13 Feb 2017 05:29:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 9Nb0I8gIEc28 for <saag@ietfa.amsl.com>; Mon, 13 Feb 2017 05:29:27 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 500FB129657 for <saag@ietf.org>; Mon, 13 Feb 2017 05:29:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6724; q=dns/txt; s=iport; t=1486992563; x=1488202163; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=o/kiaOklIUtfHf5MRjQkhPwUA8NXKY53Ut6kOjliXBE=; b=C7WtthJpe6/VnffmyBXKCJzgyIIcXKV85OQX2iBzWSHm/wjjSSPgjARS VbxyDrKLHGJfZ+vTJTmpk/m8d/2p8v8At05Stot3vYycum8l/9hXEu8YM z15L/CpY8BLfv6tdM80uSfrT9DmlZmvmzOzt2zw0G+p0kTP4I2xhqb0qJ A=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DmCACFs6FY/xbLJq1eGQEBAQEBAQEBAQEBBwEBAQEBhDMDJ1+DWYp6kHofkAqFLIIMHwEKgkKDNgKDJRYBAgEBAQEBAQFiKIRqAQEEAQEhSxsLBBQqAgInMAYBDAYCAQGJZg6uDoIlK4sXAQEBAQEBAQEBAQEBAQEBAQEBAQEBDgoFiFEIgmKHWoJfBZtyg3OCB3WLJYF7iESGRogsimkmCSiBACAUCBUVPYZEPzUBiiwBAQE
X-IronPort-AV: E=Sophos;i="5.35,156,1484006400"; d="asc'?scan'208,217";a="652451379"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2017 13:29:21 +0000
Received: from [10.61.213.107] ([10.61.213.107]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v1DDTKKl020816; Mon, 13 Feb 2017 13:29:21 GMT
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, saag <saag@ietf.org>
References: <16c236b7-dd80-1e27-8de9-16f05558d38e@gmx.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <dbc93119-3128-64e0-b6b0-1a0e87e95f90@cisco.com>
Date: Mon, 13 Feb 2017 14:29:20 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <16c236b7-dd80-1e27-8de9-16f05558d38e@gmx.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="kllqoAeNUrcKresAsLQlScEJBo7gPFHsq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/CP73XkA1FiSyqNGwFMAbRgUMdSM>
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: Mon, 13 Feb 2017 13:29:30 -0000

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