- From: Christer Holmberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2024 17:47:57 +0000
- To: public-webrtc-logs@w3.org
> In addition to Harald's concerns, the transport mismatch between RFC 8865 and the RTT RFCs such as RFC 4103 and RFC 9071 are concerning. If RFC 8865 encapsulated RTP fields like timestamp, CSRC/SSRC and used unreliable/unordered data channel, the translation to/from RFC 4103 and 9071 would be simplified. As it is, I don't see how the RFC 8865 design can be deployed in a reliable way at large scale. In particular, the design seems like it would be particularly problematic for life critical services such as emergency calling. So, are you saying that a Web app that uses a data channel to transport T.140 should generate and send RTP-specific information (CSRC/SSRC), in case there will be data channel-to-RTP gateway somewhere in the path? Wouldn't that gateway then create such RTP information? -- GitHub Notification of comment by cdh4u Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-1934641520 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 February 2024 17:47:59 UTC