Hi,

I have been selected as the Operational Directorate (opsdir) reviewer for this Internet-Draft. 

The Operational Directorate reviews all operational and management-related Internet-Drafts to ensure alignment with operational best practices and that adequate operational considerations are covered.

A complete set of _"Guidelines for Considering Operations and Management in IETF Specifications"_ can be found at https://datatracker.ietf.org/doc/draft-opsarea-rfc5706bis/.

While these comments are primarily for the Operations and Management Area Directors (Ops ADs), the authors should consider them alongside other feedback received.


- Document: [draft-ietf-teep-protocol

- Reviewer: Luigi Iannone

- Review Date: 06 November 2025

- Intended Status: Standards Track 

 
---

## Summary 

- Has Issues: I have some minor concerns about this document that I think should be resolved before publication.
 

## General Operational Comments Alignment with RFC 5706bis 

This document specifies a protocol that installs, updates, and deletes Trusted Components in a device with a Trusted Execution Environment (TEE).

The specifications are quite clear and well done, and cover fault management, namely the case of invalid messages.
However, there is no operational and configuration considerations at all.

## Major Issues 

The key point is that it would be good if the authors add operational considerations as for https://datatracker.ietf.org/doc/draft-opsarea-rfc5706bis/

If operational considerations are covered by other documents (e.g. RFC9397), direct reference to the considerations that apply to this document should be added. 
 
## Minor Issues

I gather that configuration is more part of the TEEP framework, but a more explicit statement of where the usage of this protocol is configured would be welcome.

---

Luigi Iannone