[Teep] Ketan Talaulikar's Discuss on draft-ietf-teep-protocol-24: (with DISCUSS)

[Ketan Talaulikar via Datatracker <[e-mail]>]

Ketan Talaulikar has entered the following ballot position for
draft-ietf-teep-protocol-24: Discuss

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/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Thanks to the authors and the WG for their work on this document.

I have a few discussion points related to the IANA considerations that should
be straightforward to address.

1) I believe this document needs to instruct the IANA to create a new registry
group - perhaps "Trusted Execution Environment Provisioning (TEEP) Protocol
Parameters" registry group? All the registries mentioned in sections 13.2
through 13.7 are then to be created within this new registry group?

2) When the IANA section says "Reserved for future use", I believe those are
"unassigned" (i.e., other docs/specs may ask for their allocation to IANA)?
While when "Reserved" is used, it is an instruction for IANA to not allocate
those values? Please check since some values that are "Reserved" (see below)
might actually be "deprecated" ? Also, please indicate that the allocations
given in the tables are the initial allocations being made by this document.

4       (Reserved)      This document

3) There are registries with "Specification Required" but no guidance has been
provided for DEs as required per RFC8126. Please provide DE guidance or
alternately use IETF Review policy instead of Specification Required if
allocations are going to done only from within the IETF.

4) For the TEEP CBOR Label Registry (section 13.5), is there an upper bound?
Can someone ask IANA for allocating a very high random number?