I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-avtcore-rtp-v3c-??
Reviewer: Lars Eggert
Review Date: 2025-10-28
IETF LC End Date: 2025-10-29
IESG Telechat date: Not scheduled for a telechat

# genart review of draft-ietf-avtcore-rtp-v3c-12

CC @larseggert

## Comments

This is in good shape, No specific concerns.

### Section 4.3.1, paragraph 3
```
      unsigned int(5) vuh_unit_type;
```
What does the parenthesized integer indicate? Am not familiar with this style of pseudocode.

### Boilerplate

This document uses the RFC2119 keywords "SHALL", "SHOULD", "MUST NOT", "SHALL
NOT", "MAY", "OPTIONAL", "MUST", and "MUST NOT", but does not contain the
recommended RFC8174 boilerplate. (It contains a variant of the RFC2119
boilerplate.)

### Inclusive language

Found terminology that should be reviewed for inclusivity; see
https://www.rfc-editor.org/part2/#inclusive_language for background and more
guidance:

 * Term `traditional`; alternatives might be `classic`, `classical`, `common`,
   `conventional`, `customary`, `fixed`, `habitual`, `historic`,
   `long-established`, `popular`, `prescribed`, `regular`, `rooted`,
   `time-honored`, `universal`, `widely used`, `widespread`

## Nits

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

### Typos

#### Section 3.1.2, paragraph 17
```
-    volumetric frame: set of 3D points specified by their cartesian
-                                                          ^
+    volumetric frame: set of 3D points specified by their Cartesian
+                                                          ^
```

### Grammar/style

#### Section 5.4.3, paragraph 8
```
the conditional DOND/DONL field. Otherwise v3c-tile-id field MUST NOT be pre
                                 ^^^^^^^^^
```
A comma may be missing after the conjunctive/linking adverb "Otherwise".

#### Section 7.2, paragraph 26
```
ion level. The attribute allows to associate V3C specific media format parame
                                ^^^^^^^^^^^^
```
Did you mean "associating"? Or maybe you should add a pronoun? In active voice,
"allow" + "to" takes an object, usually a pronoun.

#### Section 7.2, paragraph 36
```
e to understand them. It allows to associate V3C specific parameters with the
                                ^^^^^^^^^^^^
```
Did you mean "associating"? Or maybe you should add a pronoun? In active voice,
"allow" + "to" takes an object, usually a pronoun.

#### Section 9.3, paragraph 7
```
ll be registered with IANA; see Section Section 7.1. 10.2. V3C format paramet
                                ^^^^^^^^^^^^^^^
```
Possible typo: you repeated a word.

#### Section 9.4, paragraph 1
```
line. Its format is defined in Section Section 9.1. Further semantics are pro
                               ^^^^^^^^^^^^^^^
```
Possible typo: you repeated a word.

#### Section 9.4, paragraph 5
```
TP in general. This responsibility lays on anyone using RTP in an application
                                   ^^^^^^^
```
Did you mean "lies on"?

## Notes

This review is in the ["IETF Comments" Markdown format][ICMF]. You can use the
[`ietf-comments` tool][ICT] to automatically convert this review into
individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].

[ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
[ICT]: https://github.com/mnot/ietf-comments
[IRT]: https://github.com/larseggert/ietf-reviewtool