- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Sun, 23 Aug 2020 15:02:21 +0000
- To: public-webrtc-logs@w3.org
@sean-der @mhoro I think you've found something that needs more examination. The question is what information the RTP packetizer needs in order to packetize the encrypted payload, and where that information comes from. One set of information is needed to fill out the RTP header and RTP header extensions such as the Generic Descriptor or its successor (the Dependency Descriptor). Another set of information relates to the packetization of the RTP payload. Some of the info needed by the generic RTP packetizer depends on characteristics of the frame which are included in the metadata (such as the timestamp). But other info is specific to each RTP packet (like the marker bit). In general, the Dependency Descriptor is supposed to be able to work with all codecs, and should contain all the info that an SFU needs to make a forwarding/drop decision. If we assume that the payload is completely encrypted, I think this implies that all of the information required to generate the DD needs to be present in the metadata. It does not seem right to. me that the generic. RTP packetizer should require some info in the payload. to be unencrypted, since the point of the DD is that it contains all the info needed for forwarding (and perhaps RTP. packetization). -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/37#issuecomment-678784800 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 23 August 2020 15:02:23 UTC