Re: [webrtc-encoded-transform] Should we expose packetization level API to RTCRtpScriptTransform? (#131)

I like the idea of a prefix, which could also be used to address the [A/V/data sync issue](https://github.com/w3c/webrtc-nv-use-cases/issues/74).  You might want to make clear that  the browser is expected to take care of RTP header/extension formatting (e.g. things like setting the Marker bit).   The size of header extensions can vary with each packet, so that the available payload size needs to be provided for each packet. 

-- 
GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/131#issuecomment-1030400898 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 4 February 2022 22:29:00 UTC