MOQT encodes the delivery information via Object headers (Section 9.1). A relay MUST NOT modify Object properties when forwarding.
A relay MUST treat the object payload as opaque. A relay MUST NOT combine, split, or otherwise modify object payloads. A relay SHOULD prioritize sending Objects based on Section 6.
A publisher SHOULD begin sending incomplete objects when available to avoid incurring additional latency.
A relay that reads from one stream and writes to another in order can introduce head-of-line blocking. Packet loss will cause stream data to be buffered in the library, awaiting in-order delivery, which could increase latency over additional hops. To mitigate this, a relay MAY read and write stream data out of order subject to flow control limits. See section 2.2 in [QUIC].