Reviewer: Ines Robles Review result: Ready 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. -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
