Skip to main content

IETF Last Call Review of draft-ietf-teep-protocol-21
review-ietf-teep-protocol-21-artart-lc-hollenbeck-2025-10-07-00

Request Review of draft-ietf-teep-protocol
Requested revision No specific revision (document currently at 23)
Type IETF Last Call Review
Team ART Area Review Team (artart)
Deadline 2025-10-20
Requested 2025-10-06
Authors Hannes Tschofenig , Mingliang Pei , Dave Wheeler , Dave Thaler , Akira Tsukamoto
I-D last updated 2026-02-01 (Latest revision 2026-02-01)
Completed reviews Artart IETF Last Call review of -21 by Scott Hollenbeck (diff)
Tsvart IETF Last Call review of -21 by Yoshifumi Nishida (diff)
Genart IETF Last Call review of -21 by Paul Kyzivat (diff)
Secdir IETF Last Call review of -21 by Sean Turner (diff)
Opsdir Telechat review of -21 by Luigi Iannone (diff)
Secdir Telechat review of -23 by Sean Turner
Iotdir Telechat review of -23 by Eliot Lear
Assignment Reviewer Scott Hollenbeck
State Completed
Request IETF Last Call review on draft-ietf-teep-protocol by ART Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/art/rvfn1rt3V-jvX_boo8_SLT-5txw
Reviewed revision 21 (document currently at 23)
Result Ready w/issues
Completed 2025-10-07
review-ietf-teep-protocol-21-artart-lc-hollenbeck-2025-10-07-00
I've been asked to review the subject draft as a member of the ARTART review
team. The draft is well written and very thorough in its description of the
Trusted Execution Environment Provisioning (TEEP) protocol.

I found only one issue that needs attention. In Sections 4.4 and 4.6, there's a
description of the err-msg (error message) parameter:

"The err-msg parameter is human-readable diagnostic text that MUST be encoded
using UTF-8 [RFC3629] using Net-Unicode form [RFC5198] with max 128 bytes."

This is helpful, but there's no indication of the human language that should be
used to interpret the diagnostic text. I recommend inclusion of an additional
parameter, perhaps "err-lang", that can be used to identify the language of the
error message. The value of this parameter must be a language tag as specified
in RFC 5646.