CR on correction to animation samples transport
Proposal 1: Add a NOTE in clause 6.2 clarifying that the metadata data channel (sub‑protocol "3gpp‑ar‑metadata") is text‑only and is not intended for the transport of binary data such as avatar animation samples.
Proposal 2: Add a new sentence at the end of clause 6.2 stating: "The metadata data channel shall not be used to transport ARF avatar animation samples defined in clause 8 of [10]."
Proposal 3: Replace the existing text in clause 6.3.2 with new text that defines an Avatar Animation Data Channel with sub‑protocol "3gpp-ar-animation" for binary transport of ARF avatar animation samples as specified in clause 8 of [10], separate from the metadata data channel defined in clause 6.2.
Proposal 4: Specify in clause 6.3.2 that the Avatar Animation Data Channel shall only carry avatar animation samples, with transmission order set to in‑order and transmission reliability set to reliable (with optional negotiation of partial reliability using data‑channel parameters).
Proposal 5: Specify in clause 6.3.2 that each "3gpp-ar-animation" data‑channel message shall contain exactly one ARF animation sample.
Proposal 6: Remove the existing text in clause 6.3.2 that defines avatar animation messages with type "urn:3gpp:avatar:v1:animation" and the associated message format in Table 6.3-1, as these are replaced by the binary Avatar Animation Data Channel.
Proposal 7: Retain the existing text in clause 6.3.2 regarding the stopped and resumed control messages (Tables 6.3-2 and 6.3-3), as these control messages continue to use the metadata data channel.