Re: [Teep] Charter Text

[" 刘大鹏(鹏成) " <[e-mail]>]

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) <[e-mail]>Send Time:2017年9月12日(星期二) 23:50To:Lubna Dajani <[e-mail]>; Petr Peterka <[e-mail]>Cc:[e-mail] <[e-mail]>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 <[e-mail]>
Date: Tuesday, September 12, 2017 at 4:40 AM
To: Petr Peterka <[e-mail]>
Cc: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: Re: [Teep] Charter Text please allow me to echo Petr's responses. 1. Yes2. Yes3. Yes4. 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
[e-mail] wrote:Hi NancyI 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:[e-mail]]
On Behalf Of Nancy Cam-Winget (ncamwing)
Sent: Thursday, July 20, 2017 11:13 AM
To: [e-mail]
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 <[e-mail]> on behalf of Hannes Tschofenig <[e-mail]>
Date: Wednesday, July 19, 2017 at 5:56 AM
To: "[e-mail]" <[e-mail]>
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.