[Teep] Re: Éric Vyncke's No Objection on draft-ietf-teep-protocol-24: (with COMMENT)

["Eric Vyncke (evyncke)" <[e-mail]>]

Hannes,

Thank you for your messages and the revised I-Ds.

Regards

-éric

From: Hannes Tschofenig <[e-mail]>
Date: Thursday, 26 February 2026 at 21:02
To: The IESG <[e-mail]>, [e-mail] <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, Eric Vyncke (evyncke) <[e-mail]>
Subject: Re: [Teep] Éric Vyncke's No Objection on draft-ietf-teep-protocol-24: (with COMMENT)


Hi Eliot,


Eric mentioned the IoT directorate review provided by Eliot in his email below. Thanks for your review, Eliot!

In version -26 I have addressed the still remaining comments since version -25 was published.

Here is the diff:
https://author-tools.ietf.org/iddiff?url1=draft-ietf-teep-protocol-25&url2=draft-ietf-teep-protocol-26&difftype=--html


Ciao

Hannes


Am 26.02.2026 um 20:10 schrieb Hannes Tschofenig:

Hi Eric!

Thank you for the review and suggestions.

We made the following updates:

- Section 3: Clarified the language.
- Added cross-reference the transport-binding requirements section.
- Added data-item-requested registry and referenced it - Renamed Section 11 from "Transport Considerations" to "Transport Binding Requirements" and clarified that it defines requirements for companion transport bindings.
- We added IANA text for Designated Experts.
- Added "private use" registry entry. - Added aasvg statement to relevant figures. Looks better now.

Regarding the BCP14 / IESG statement comment: Thank you for the pointer.

Ciao
Hannes


Am 19.02.2026 um 15:45 schrieb Éric Vyncke via Datatracker:

Éric Vyncke 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:
----------------------------------------------------------------------


# Éric Vyncke INT AD comments for draft-ietf-teep-protocol-24
CC @evyncke

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points/nits (replies would be
appreciated even if only for my own education).

Other thanks to Eliot Lear, the IoT directorate reviewer (at my request),
please consider this int-dir review:
https://datatracker.ietf.org/doc/review-ietf-teep-protocol-23-iotdir-telechat-lear-2026-02-08/
(and I have yet to read a reply from the authors)

I hope that this review helps to improve the document,

Regards,

-éric

Note: this ballot comments follow the Markdown syntax of
https://github.com/mnot/ietf-comments/tree/main, i.e., they can be processed by
a tool to create github issues.

## COMMENTS (non-blocking)

### IoT directorate review and section 4.1.1

As noted above, Eliot did an extensive review and has provided feedback, his
points about section 4.1.1 should really be addressed.

### Section 3

Who is the "we" in `we assume them ` ? The authors ? The WG ? The IETF
community ? Please avoid ambiguities.

Possibly also in other places.

### Section 4.2

Why not a MUST in `The TAM SHOULD set an expiration time for each token` ? Also
note that guidance must be given if "SHOULD" is kept. See
https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/
(cfr the guidance/exception given for a SHOULD in section 4.3.1)

### Section 4.2

Please add text about data-item-requested being a registry defined in section
13.3 (which is good idea).

### Section 13.3

Suggest to have at least one code point for "private use" per RFC 8126

### Use of SVG graphics

To make a much nicer HTML rendering, suggest using the aasvg tool to generate
SVG graphics. It is worth a try especially if the I-D uses the Kramdown file
format ;-)



_______________________________________________
TEEP mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>