Re: [Teep] [saag] BOFs about IoT firmware update and TEE configuration
Eliot Lear <lear@cisco.com> Wed, 22 February 2017 08:33 UTC
Return-Path: <lear@cisco.com>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B6F12968C; Wed, 22 Feb 2017 00:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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_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, 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 MsDzJzgzS8ZD; Wed, 22 Feb 2017 00:33:18 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16EB91294C0; Wed, 22 Feb 2017 00:33:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6259; q=dns/txt; s=iport; t=1487752398; x=1488961998; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=z0zgPGN+l8lyuUIKJtQKocrsa5RSJ6zTIduiMyjFfG4=; b=D9x5VJovmpfe61aT5bk8S9++dl5kqe/kKs+kiMnTdE+WZMXkuHOwfKks YSTGpJBgT8xR/JtoE6PfjLYEqVnfh2hcDCtCnnn0vFddmh5o3oqUhsfsE 9/HpQ09PcxlHGu77Zq+hni0jB08n+UViUoq65x5gVl+CgLc/SEvJxRKb9 g=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D4AQAfTK1Y/xbLJq1eGQEBAQEBAQEBAQEBBwEBAQEBhDIDJ1+DW4oIcpBolTSCDR8NgkCDNgKDMxgBAgEBAQEBAQFiKIRxAQECAgEBIUgDBwQQCxgqAgInMAYNBgIBAReHbQOBag6ueIImi0cBAQEBAQEBAQEBAQEBAQEBAQERCgWIUYFhgQmHWoJfBYkZgVeRG4N3ggh1iy2Be4hJhkuINYZUhBwfOIEAIRQIFxU+hko/NQGKOQEBAQ
X-IronPort-AV: E=Sophos;i="5.35,193,1484006400"; d="asc'?scan'208";a="692437999"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Feb 2017 08:33:15 +0000
Received: from [10.61.198.238] ([10.61.198.238]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1M8XFl2030938; Wed, 22 Feb 2017 08:33:15 GMT
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <16c236b7-dd80-1e27-8de9-16f05558d38e@gmx.net> <dbc93119-3128-64e0-b6b0-1a0e87e95f90@cisco.com> <1da45f12-7999-6a9e-3649-2ffea4d50511@gmx.net> <fe6c2aaf-dc0a-bfc2-59c2-a077ddc4e43b@cisco.com> <6916bccf-9273-5d2f-af44-ef38d1394223@gmx.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <42690b82-8d20-a524-cf0a-ed665fa1610f@cisco.com>
Date: Wed, 22 Feb 2017 09:33:14 +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: <6916bccf-9273-5d2f-af44-ef38d1394223@gmx.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="6vLu85G6JLGLgaTmTlHiG6sfFAtMw1F2T"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/a8l8Wvpi2KgzWFbrn7LcN7rZ-Gw>
X-Mailman-Approved-At: Wed, 22 Feb 2017 00:38:45 -0800
Cc: teep@ietf.org, saag <saag@ietf.org>
Subject: Re: [Teep] [saag] BOFs about IoT firmware update and TEE configuration
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 08:33:20 -0000
Great start, thanks! Will contact you offline to further discuss. Eliot On 2/22/17 9:15 AM, Hannes Tschofenig wrote: > Hi Eliot, > > > (I put the TEEP mailing list on CC since they may be interested in this > conversation as well.) > > The use case for TEEP is a bit different. > > The idea is to configure software running on a trusted execution > environment. While the currently proposed solution assumes a PKI and the > use of asymmetric key cryptography it does not use 802.1AR certificates. > There is no notion of a local network since it does not matter. The > document also does not talk about how the messages are conveyed but HTTP > is more likely for the smart phone/tablet use cases. > > > I created a slide deck for presentation at the T2TRG meeting at the > Berlin IETF but unfortunately there was no time. Nevertheless, here is > the slide deck: > https://github.com/t2trg/2016-ietf96/blob/master/slides/70_OTrP-IETF93.pdf > > Does this provide enough information about the intention? > > Ciao > Hannes > > On 02/20/2017 03:58 PM, Eliot Lear wrote: >> Hi Hannes, >> >> First, Max, Michael, Michael, and Kent are far more the experts than I >> am on this, but here is a brief summary: >> >> The purpose of draft-ietf-anima-bootstrap-keyinfra is to provide a >> trusted introduction between devices and the network such that you start >> in the following state: >> >> Device has a manufacturer certificate (802.1AR iDevID) and a >> manufacturer trust root, and the local network can in some way >> authenticate the manufacturer, and perhaps visa versa. The end state is >> that the device has a local (802.1 LDevID) and a local trust anchor. To >> accomplish this, a flow is defined to get to the point where the device >> will register with a local registrar using EST (either EST or EST/CoAP). >> >> Now perhaps you could explain a little about the TEE draft you're doing? >> >> If there's some overlap perhaps there's a chance to consolidate the work. >> >> Eliot >> >> >> >> On 2/18/17 5:17 PM, Hannes Tschofenig wrote: >>> 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 >>
- Re: [Teep] [saag] BOFs about IoT firmware update … Hannes Tschofenig
- Re: [Teep] [saag] BOFs about IoT firmware update … Eliot Lear