- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Feb 2024 08:41:34 +0000
- To: public-webrtc-logs@w3.org
A proposal for an API change needs to go to webrtc-extensions, not to webrtc-pc. We don't add unimplemented feature proposals to webrtc-pc. The simpler way to support the content of dcsa (characters per second, language for sending and receiving) is to define a message to be sent on the T.140 datachannel that conveys the content - 8864 says that the rules for dcsa are defined by the subprotocol anyway, so there's no possible subprotocol-independent implelentation of RFC 8864. Keeping the negotiation of cps, hlang-send and hlang-receive inside the datachannel will allow the implementation of an RFC 8865bis that specs this to be done on top of currently implemented WebRTC implementations, without any need for an API change or updating of platforms. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-1920782124 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 February 2024 08:41:37 UTC