Re: [Teep] Charter Text
"zhoup@bjleisen.com" <zhoup@bjleisen.com> Fri, 22 September 2017 02:11 UTC
Return-Path: <zhoup@bjleisen.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 F0F8613301B; Thu, 21 Sep 2017 19:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 WYPMVqrZ9EsS; Thu, 21 Sep 2017 19:11:08 -0700 (PDT)
Received: from m50210.mail.qiye.163.com (m50210.mail.qiye.163.com [123.125.50.210]) by ietfa.amsl.com (Postfix) with ESMTP id BC98D132941; Thu, 21 Sep 2017 19:11:06 -0700 (PDT)
Received: from zp-bjleisen (unknown [219.239.243.130]) by smtp6 (Coremail) with SMTP id RNOowEApGEMnccRZIKB9Aw--.1S2; Fri, 22 Sep 2017 10:10:51 +0800 (CST)
Date: Fri, 22 Sep 2017 10:10:57 +0800
From: "zhoup@bjleisen.com" <zhoup@bjleisen.com>
To: Dapeng Liu <maxpassion@gmail.com>, Lubna Dajani <lubnadajani@gmail.com>, "ppeterka@verimatrix.com" <ppeterka@verimatrix.com>, teep-bounces <teep-bounces@ietf.org>, teep <teep@ietf.org>, Mingliang Pei <Mingliang_Pei@symantec.com>, "Marc.Canel" <Marc.Canel@arm.com>, Richard Parris <richard.parris@intercede.com>, Rob Coombs <rob.coombs@arm.com>, "qingyang.meng" <qingyang.meng@beanpodtech.com>, Brian Witten <brian_witten@symantec.com>, "henry.j.lee@samsung.com" <henry.j.lee@samsung.com>, Nick Cook <Nick.Cook@intercede.com>, "Mike.M.Parsel@sprint.com" <Mike.M.Parsel@sprint.com>, Hannes Tschofenig <hannes.tschofenig@arm.com>, "zhijian.zhang" <zhijian.zhang@beanpodtech.com>, 魏茂军 <maojun.wei@watchdata.com>, Dominique Bolignano <dominique.bolignano@provenrun.com>, "heekwan.lee@samsung.com" <heekwan.lee@samsung.com>, Mike Hendrick <mike.hendrick@seqlabs.com>, XiaYubin <xiayubin@trustkernel.com>, "sangjin.park@hansol.com" <sangjin.park@hansol.com>, "Paczkowski, Lyle W [CTO]" <lyle.w.paczkowski@sprint.com>, Pengcheng Zou <zoupc@thundersoft.com>, "fmw@whty.com.cn" <fmw@whty.com.cn>, "philip.attfield" <philip.attfield@seqlabs.com>, "Andrew.Atyeo" <Andrew.Atyeo@intercede.com>, paromix <paromix@sola-cia.com>, ppeterkaa <ppeterkaa@verimatrix.com>, "max.ldp@alibaba-inc.com" <max.ldp@alibaba-inc.com>
References: <6EFD27BC-CE56-4112-AD20-C787520BEE87@cisco.com>, <DM5PR20MB1228DEC9757FCBDCA4254052AAA70@DM5PR20MB1228.namprd20.prod.outlook.com>, <d6015c71-04de-3323-bb08-5ac66a5c21d0@mixmax.com>, <35502548-8d02-4af2-b409-d8be73dd6a6d.max.ldp@alibaba-inc.com>, <CAKcc6AdZV7HsUvTiKnSP7dXf9Q4PMfBmNyWnwMLnGF6re3aKAQ@mail.gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 5, 140[cn]
Mime-Version: 1.0
Message-ID: <201709221010555677461@bjleisen.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart282306807136_=----"
X-CM-TRANSID: RNOowEApGEMnccRZIKB9Aw--.1S2
X-Coremail-Antispam: 1Uf129KBjvJXoW3XF4DCr1kJF4fGFW5CryrCrg_yoWfGrW7pF WfKrsxAF4DJF1xGw1DAa1xu3WS9FWrGFW7JFn5G348Aas8CryxKr13t34FvF9rGr93JFWY v3yj9rn8ZaykZaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x0pi1xRgUUUUU=
X-Originating-IP: [219.239.243.130]
X-CM-SenderInfo: p2kr31w6emzvhlvh0hhfrp/1tbiaBBbjVlZtCEMawAAsc
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/O3-2KO3SnHSH5Y_G_tzmSR87jqI>
X-Mailman-Approved-At: Thu, 21 Sep 2017 19:58:31 -0700
Subject: Re: [Teep] Charter Text
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 22 Sep 2017 02:11:12 -0000
hi, Beijing Laser Tech. support it.thanks. 周鹏 CEO 北京雷森科技发展有限公司 Beijing Laser Technology Development CO.,LTD 地址:西直门北大街甲43号金运大厦7层 邮编100044 手机:18910750012/15601105750/13911779990 网址:www.bjleisen.com From: Dapeng Liu Date: 2017-09-13 00:49 To: Lubna Dajani; ppeterka; teep-bounces; teep; Mingliang Pei; Marc Canel; richard.parris@intercede.com; Rob Coombs; qingyang.meng; brian_witten; henry.j.lee@samsung.com; Nick Cook; Mike.M.Parsel@sprint.com; Hannes Tschofenig; zhijian.zhang; zhoup; maojun.wei; dominique.bolignano; heekwan.lee@samsung.com; mike.hendrick@seqlabs.com; xiayubin; sangjin.park; lyle.w.paczkowski; Pengcheng Zou; fmw; philip.attfield; Andrew.Atyeo; paromix; ppeterkaa; 成 鹏 Subject: re: [Teep] Charter Text Hello Nancy, Thanks! Actually, there are lots of companies/experts are very interested in the proposed TEEP work. But they may not familiar with IETF process, I hope they would getting more active in the list after the long summer vacation:) Note: I have copied to all the experts that are interested in TEEP based on offline discussions. To all the experts copied in this mail: Please subscribe to TEEP email list first if you want to reply. Here is how to subscribe: https://www.ietf.org/mailman/listinfo/teep Thanks, Max ------------------------------------------------------------------ From:Nancy Cam-Winget (ncamwing) <ncamwing@cisco.com> Send Time:2017年9月12日(星期二) 23:50 To:Lubna Dajani <lubnadajani@gmail.com>; Petr Peterka <ppeterka@verimatrix.com> Cc:teep@ietf.org <teep@ietf.org> Subject:Re: [Teep] Charter Text Thank you Lubna and Petr! Would still like to hear from others and also solicit feedback on the proposed charter text. Warm regards, Nancy From: Lubna Dajani <lubnadajani@gmail.com> Date: Tuesday, September 12, 2017 at 4:40 AM To: Petr Peterka <ppeterka@verimatrix.com> Cc: "ncamwing@cisco.com" <ncamwing@cisco.com>, "teep@ietf.org" <teep@ietf.org> Subject: Re: [Teep] Charter Text please allow me to echo Petr's responses. 1. Yes 2. Yes 3. Yes 4. Yes I am personally very excited to see this WG form and I look forward to actively contributing to the evolution of this protocol as I have since the ideation stages of this protocol … Thank you Nancy, Petr and everyone here… Lubna __________________________________________________ Lubna Dajani I Allternet Ltd. @lubnadajani @futuristasORG + 1 201 982 0934 Confidentiality Notice: The information contained in this email and any attachments is intended only for the recipient[s] listed above and may be privileged and confidential. Any dissemination, copying, or use of or reliance upon such information by or to anyone other than the recipient[s] listed above is prohibited. If you have received this message in error, please notify the sender immediately at the email address above and destroy any and all copies of this message. Sent with Mixmax On Thu, Jul 20, 2017 2:48 AM, Petr Peterka ppeterka@verimatrix.com wrote: Hi Nancy I think we had a very productive meeting yesterday. Here are my answers to your questions: 1) Do you understand what TEEP is trying to achieve? ANSWER: Yes, I do. I’d like to add that the charter may re-emphasize that the proposed WG is not going to define the TEE or the TAM service themselves but just the protocol between them. 2) Is this work that should be done in general? ANSWER: Yes, it should since there are going to be more and more trusted execution environments (lower case) especially with the proliferation of IoT devices which will need more security than what they have today. 3) Is this work that should be done in the IETF, or does it belong to somewhere else? ANSWER: Since we are trying to define a protocol that is independent of the different TEE implementations, I believe that IETF is the right home for it. 4) Should we form a WG with given charter to work on this? ANSWER: Yes, that is my recommendation. Thanks Petr From: TEEP [mailto:teep-bounces@ietf.org] On Behalf Of Nancy Cam-Winget (ncamwing) Sent: Thursday, July 20, 2017 11:13 AM To: teep@ietf.org Subject: Re: [Teep] Charter Text All, Please provide feedback on the results of yesterday’s side meeting. In particular, we’d like to get feedback on whether this the right scope and if we have captured it appropriately. If it is not, also please comment and if possible, provide suggestions for improvement. We would like to continue discussion over email and get consensus around the 2nd week of September so that we can have a path forward. In particular we would like to get answers for: 1) Do you understand what TEEP is trying to achieve? 2) Is this work that should be done in general? 3) Is this work that should be done in the IETF, or does it belong to somewhere else? 4) Should we form a WG with given charter to work on this? Warm regards, Nancy & Tero (TEEP BoF Chairs) From: TEEP <teep-bounces@ietf.org> on behalf of Hannes Tschofenig <Hannes.Tschofenig@arm.com> Date: Wednesday, July 19, 2017 at 5:56 AM To: "teep@ietf.org" <teep@ietf.org> Subject: [Teep] Charter Text Here is the charter text we came up in the side-meeting today. ------ TEEP -- A Protocol for Dynamic Trusted Execution Environment Enablement Charter The Trusted Execution Environment (TEE) is a secure area of a processor. The TEE provides security features, such as isolated execution, integrity of Trusted Applications along with confidentiality of their assets. In general terms, the TEE offers an execution space that provides a higher level of security than a "rich" operating system and more functionality than a secure element. For example, implementations of the TEE concept have been developed by ARM, and Intel using the TrustZone and the SGX technology, respectively. To programmatically install, update, and delete applications running in the TEE, this protocol runs between a service running within the TEE, a relay application or service access point on the device's network stack and a server-side infrastructure that interacts with and optionally maintains the applications. Some tasks are security sensitive and the server side requires information about the device characteristics in form of attestation and the device-side may require information about the server. Privacy considerations have to be taken into account with authentication features and attestation. This working group aims to develop an application layer protocol providing TEEs with the following functionality, * lifecycle management of trusted applications, and * security domain management. A security domain allows a service provider's applications to be isolated so that one security domain cannot be influenced by another, unless it exposes an API to allow it. The solution approach must take a wide range of TEE and relevant technologies into account and will focus on the use of public key cryptography. The group will produce the following deliverables. First, an architecture document describing the involved entities, their relationships, assumptions, the keying framework and relevant use cases. Second, a solution document that describes the above-described functionality. The choice of encoding format(s) will be decided in the working group. The group may document several attestation technologies considering the different hardware capabilities, performance, privacy and operational properties. The group will maintain a close relationship with the GlobalPlatform, Trusted Computing Group, and other relevant standards to ensure proper use of existing TEE-relevant application layer interfaces. Milestones Dec 2017 Submit "TEEP Architecture" document as WG item. Feb 2018 Submit "TEEP Protocol" document as WG item. July 2018 Submit "TEEP Architecture" to the IESG for publication as an Informational RFC. Feb 2019 Submit "TEEP Protocol" to the IESG for publication as a Proposed Standard. Additional calendar items: Nov 2017 IETF #100 Hackathon to work on TEEP protocol prototype implementations. Mar 2018 1st interoperability event (at IETF #101). Jul 2018 2nd interoperability event (at IETF #102). IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
- [Teep] Charter Text Hannes Tschofenig
- Re: [Teep] Charter Text Nancy Cam-Winget (ncamwing)
- Re: [Teep] Charter Text Petr Peterka
- Re: [Teep] Charter Text Kaarthik Sivakumar
- Re: [Teep] [EXT] Re: Charter Text Mingliang Pei
- Re: [Teep] [EXT] Re: Charter Text Kaarthik Sivakumar
- Re: [Teep] Charter Text Lubna Dajani
- Re: [Teep] Charter Text Nancy Cam-Winget (ncamwing)
- Re: [Teep] Charter Text 刘大鹏(鹏成)
- Re: [Teep] Charter Text Dapeng Liu
- Re: [Teep] Charter Text Nancy Cam-Winget (ncamwing)
- Re: [Teep] Charter Text Dapeng Liu
- Re: [Teep] Charter Text Mingliang Pei
- Re: [Teep] Charter Text Paczkowski, Lyle W [CTO]
- Re: [Teep] Charter Text zhoup@bjleisen.com
- Re: [Teep] [EXT] RE: Charter Text Mingliang Pei
- Re: [Teep] Charter Text Nancy Cam-Winget (ncamwing)
- Re: [Teep] Charter Text Jeremy O'Donoghue
- Re: [Teep] Charter Text Wheeler, David M
- Re: [Teep] Charter Text Jeremy O'Donoghue
- Re: [Teep] Charter Text Nancy Cam-Winget (ncamwing)
- Re: [Teep] [EXT] Re: Charter Text Brian Witten
- Re: [Teep] [EXT] Re: Charter Text Dave Thaler
- Re: [Teep] [EXT] Re: Charter Text 刘大鹏(鹏成)
- Re: [Teep] [EXT] Re: Charter Text Dave Thaler
- Re: [Teep] [EXT] Re: Charter Text 刘大鹏(鹏成)
- Re: [Teep] [EXT] Re: Charter Text Dave Thaler
- Re: [Teep] Charter Text Dave Thaler
- Re: [Teep] Charter Text Robert Broberg
- Re: [Teep] Charter Text Jeremy O'Donoghue
- Re: [Teep] Charter Text Hank Chavers