- From: Gunnar Hellström via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Feb 2024 21:43:07 +0000
- To: public-webrtc-logs@w3.org
Yes, right, this issue is about updating section 14. I provided a proposal above in https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-1921766198 I would hope that it was fair to state that the work in mmusic is completed and RFC 8865 exsits. Did you see my earlier response to why I do not think it would be a good idea to repeat the RTP based solution of RFC 4103 + RFC9071 in WebRTC? It is also available above in https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-1924763575 We need a much less complex solution than RFC4103 + RFC9071 in WebRTC. I am convinced that it is RFC 8865, but it would be even easier if the attributes we use, which are approved in IETF as common attributes for WebRTC channels, would be supported in the API. I think we should start a new issue about how to ease RTT implementation in WebRTC, and just agree on the updated wording of Section 14 here. -- GitHub Notification of comment by gunnarhm Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-1934979877 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 21:43:09 UTC