Telechat Review of draft-ietf-teep-architecture-18
review-ietf-teep-architecture-18-iotdir-telechat-robles-2022-09-04-00

Request Review of draft-ietf-teep-architecture
Requested revision No specific revision (document currently at 19)
Type Telechat Review
Team Internet of Things Directorate (iotdir)
Deadline 2022-09-04
Requested 2022-08-26
Requested by Éric Vyncke
Authors Mingliang Pei , Hannes Tschofenig , Dave Thaler , Dave Wheeler
I-D last updated 2022-09-04
Completed reviews Secdir Last Call review of -16 by Benjamin M. Schwartz (diff)
Artart Last Call review of -16 by Russ Housley (diff)
Genart Last Call review of -16 by Paul Kyzivat (diff)
Intdir Telechat review of -18 by Bob Halley (diff)
Iotdir Telechat review of -18 by Ines Robles (diff)
Comments 
While I do not expect issues from the Internet or IoT points of view, I would appreciate a review by the int and iot directorates.

Thank you in advance

-éric
Assignment Reviewer Ines Robles
State Completed
Request Telechat review on draft-ietf-teep-architecture by Internet of Things Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/iot-directorate/4l5qrIbeWJMCBGCtsVPsZbKQQpQ
Reviewed revision 18 (document currently at 19)
Result Ready
Completed 2022-09-04
review-ietf-teep-architecture-18-iotdir-telechat-robles-2022-09-04-00
IoT Review of draft-ietf-teep-architecture

Summary:

This document depicts a Trusted Execution Environment (TEE) architecture
stating that any code within that environment cannot be tampered with, and that
any data used by such code cannot be read or tampered with by any code outside
that environment; describing a protocol for managing the lifecycle of trusted
applications running inside such a TEE.

Major Issues: Not found

Minor Issues: Not found

Nits/Questions/Comments:

* Pag 9 - Figure 1: The arrows in the diagram are unidirectional, Are there
cases where it could be bidirectional: e.g. the communication of the Agent with
the Broker?

* Having an IoT scenario, in your opinion which type of Classes of Constrained
Devices (Class 0, Class 1, etc. [RFC7228]) can participate in the TEE as a
"Device" in Figure 1.

* Page 27: "...In some use cases it may be sufficient to identify only the
class of the device..." what do you mean with class of device? Perphaps would
be nice to add between brakets some examples.

Thanks for this document,

Ines.