[Teep] Re: Gunter Van de Velde's No Objection on draft-ietf-teep-protocol-24: (with COMMENT)

[Hannes Tschofenig <[e-mail]>]

Thank you, Gunter, for your review.

I agree that the term "interoperable" in the previous abstract was a bit 
too generic. We have updated the abstract to describe the protocol scope 
more explicitly: the TAM/TEEP Agent message exchanges, the supported 
lifecycle operations (install/update/delete), attestation-related 
exchanges, and the use of CBOR and COSE.

I believe that the revised abstract now reads much better.

Ciao
Hannes


Am 17.02.2026 um 14:48 schrieb Gunter Van de Velde via Datatracker:
> Gunter Van de Velde has entered the following ballot position for
> draft-ietf-teep-protocol-24: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-teep-protocol/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> # Gunter Van de Velde, RTG AD, comments for draft-ietf-teep-protocol-24
>
> # The line numbers used are rendered from IETF idnits tool:
> https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-teep-protocol-24.txt
>
> # idnits report displays few warnings
>
> # This document is not an easy read (i am not a security expert) and have only
> performed a high level review. The sections i processed were well written.
>
> # i have only one observation:
>
> 19         This document specifies a protocol that installs, updates, and
> 20         deletes Trusted Components in a device with a Trusted Execution
> 21         Environment (TEE).  This specification defines an interoperable
> 22         protocol for managing the lifecycle of Trusted Components.
>
> GV> The abstract says that it defines an interoperable protocol. Is that not
> implicit when a protocol is used by different devices? Maybe my question is
> what does 'interoperable' describe in the context of the abstract?
>
> What about the following abstract (AI generated)
>
> "
>     This document specifies the Trusted Execution Environment Provisioning
>     (TEEP) Protocol, which enables secure lifecycle management of Trusted
>     Components in devices with a Trusted Execution Environment (TEE).
>     The protocol defines message exchanges between a Trusted Application
>     Manager (TAM) and a TEEP Agent to query device state, convey
>     attestation evidence, and install, update, or delete Trusted
>     Components.  Messages are encoded in CBOR and secured using COSE.
> "
>
> Many thanks for this document,
>
> Kind Regards,
> Gunter Van de Velde
>
>
>
> _______________________________________________
> TEEP mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]