Change:
Trusted applications (TAs): An application component that runs in a TEE. <del> For more information about TEEs see I-D.ietf-teep-architecture.  TEEP requires the use of SUIT for delivering TAs. </del> <ins> Trust Anchor: A trust anchor, as defined in RFC6024, represents an authoritative entity via a public key and associated data.  The public key is used to verify digital signatures, and the associated data is used to constrain the types of information for which the trust anchor is authoritative." </ins> <del> The following entities are used: </del> <ins> Trust Anchor Store: A trust anchor store, as defined in RFC6024, is a set of one or more trust anchors stored in a device.  A device may have more than one trust anchor store, each of which may be used by one or more applications.  A trust anchor store must resist modification against unauthorized insertion, deletion, and modification. 2.2. The following stakeholders are used in this document: </ins> Author: The author is the entity that creates the firmware image. <del> There may be multiple authors in a system either when a device consists of multiple micro-controllers or when the the final firmware image consists of software components from multiple companies. </del> <ins> There may be multiple authors involved in producing firmware running on an IoT device. device talks about those IoT device deployment cases. Device Operator: The device operator is responsible for the day- to-day operation of a fleet of IoT devices.  Customers of IoT devices, as the owners of IoT devices - such as enterprise customers or end users, interact with their IoT devices indirectly through the device operator via web or smart phone apps. Network Operator: The network operator is responsible for the operation of a network to which IoT devices connect. Trust Provisioning Authority (TPA): The TPA distributes trust anchors and authorization policies to various stakeholders.  The TPA may also delegate rights to stakeholders.  For example, in some cases, the Original Design Manufacturer (ODM), which is a company that designs and manufactures a product, may act as a TPA and may decide to remain in full control over the firmware update process of their products. 2.3. (IoT) Device: A device refers to the entire IoT product, which consists of one or many MCUs, sensors and/or actuators.  Many IoT devices sold today contain multiple MCUs and therefore a single device may need to obtain more than one firmware image and manifest to succesfully perform an update. Status Tracker: The status tracker has a client and a server component and performs three tasks: 1) It communicates the availability of a new firmware version.  This information will flow from the server to the client. 2) It conveys information about software and hardware characteristics of the device.  The information flow is from the client to the server. 3) It can remotely trigger the firmware update process.  The information flow is from the server to the client. For example, a device operator may want to read the installed firmware version number running on the device and information about available flash memory.  Once an update has been triggered, the device operator may want to obtain information about the state of the firmware update.  If errors occurred, the device operator may want to troubleshoot problems by first obtaining diagnostic information (typically using a device management protocol). We make no assumptions about where the server-side component is deployed.  The deployment of status trackers is flexible and may be found at cloud-based servers, on-premise servers, or may be embedded in edge computing device.  A status tracker server component may even be deployed on an IoT device.  For example, if the IoT device contains multiple MCUs, then the main MCU may act as a status tracker towards the other MCUs.  Such deployment is useful when updates have to be synchronized across MCUs. </ins> Firmware Consumer: The firmware consumer is the recipient of the firmware image and the manifest.  It is responsible for parsing

Discussion:
First chunk of changes.
This is a really great set of edits. I think that it really improves the document as a whole! I have suggested a couple of minor edits.Quick partial language review