- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Nov 2023 10:23:45 +0000
- To: public-webrtc-logs@w3.org
So codecs are necessarily per m= section since directionality is not something that is negotiated in the SDP. - The other endpoint prefers to receive codec X, for which we don't have a transformer? No problem, this is just a preference, the sender can send whatever it wants, whenever it wants, and is not obligated to add a transformer until it decides to use the transformer. - The other endpoint negotiates codec X. We can't know if the app wants to use it for sending or for receiving, so we can't forbid it based on whether or not transforms exist. On the receive side, yes, the transform is needed before receiving, but this is a timing issue rather than a hard requirement for negotiation. We can decide if we want to add any "hand-holding" logic to prevent foot-gunning (I don't think we necessarily do), but nothing changes the fact that a) codec negotiation is per transceiver and in a direction-agnostic way, and b) it is perfectly valid to create the transformer at a later stage than negotiation. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1818768574 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 November 2023 10:23:46 UTC