JVET-AM0321 AHG9: On SEI message types indicated by an SPO SEI message [Y.-K. Wang (Bytedance), M. M. Hannuksela (Nokia), Y. He (Qualcomm)] [late]
Chaired by S. Deshpande on 28 June 2025 during 9:00-9:20
The bullet items 2 and 3 in JVET-AM0121 subclause 5.1 are assertedly describing use cases of SEI message types in different SPO entries being the same. In that case, it is asserted that there is no reason to only allow SEI message types in different SPO entries being the same when PON is involved, but rather, it should be allowed even when PON is not involved.
This contribution proposes an alternative set of text changes that address the same issues as JVET-AM0121 item 5 and JVET-AM0079 item 3. The concrete changes are included in the attachment to this contribution, with changes marked relative to JVET-AL2006-v4-ncm.
In the specification text markup the key technical change proposed is:
The SEI message types indicated in different entries of an SPO SEI message are typcially different from each other but some of them may also be the same.
There are also a number of editorial changes proposed.
Decision: Adopt
NNPF SEI extensions (1)
Contributions in this area were discussed during 0900–1000 on Friday 27 June 2025 (chaired by J. Boyce).
JVET-AM0321 AHG9: On SEI message types indicated by an SPO SEI message
AI usage restrictions (AUR)