Subject: [Teep] TEEP Architecture Draft Updated

From: Hannes Tschofenig <[email-masked]>
Date: Tue, 12 Mar 2019 08:47:57 +0000

Hi all,

In time for the deadline we submitted an updated version of the TEEP architecture document. It was a snapshot of what we had on the TEEP WG Github repo (see https://github.com/ietf-teep/architecture). Last year we collected a list of open issues and, as you can see, there are still a number of issues open, see https://github.com/ietf-teep/architecture/issues. We plan to discuss some of them at the f2f meeting Prague.

Since the last IETF meeting in Bangkok we have tried to address some of the issues and from the diff you can see that we have addressed some of them:
https://tools.ietf.org/rfcdiff?url2=draft-ietf-teep-architecture-02.txt

Here is a short list of what has been changed in the document:

  *   Terminology: We added the device user, and the device owner term. We clarified trust anchor and device administrator.
  *   Shorted the list of assumptions
  *   Added text about multiple TEEs and multiple TAMs
  *   Added text about the client app / trusted app interaction
  *   Updated text about trust anchors
  *   Improved the example flow
  *   Added text about attestation
and made lots of other editorial improvements here and there.

Take a look at the document and let us know what you think. We also welcome your thoughts about the open issues.

Ciao
Hannes
(on behalf of the authors)
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.