- From: Gunnar Hellström via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Oct 2024 20:08:52 +0000
- To: public-webrtc-logs@w3.org
[Answers on W3C comments on RFC 8865.docx](https://github.com/user-attachments/files/17235303/Answers.on.W3C.comments.on.RFC.8865.docx) I have answered comments about RFC 8865 in the attached document and tried to compose a kind of implementors guide, explaining how RFC 8865 can be used without problems. The implementors guide may need adjustments. Some of the comments above propose that the unreliable channel should have been used instead of the reliable, because then gateways to the RTP carried RFC 4103 + RFC9071 would be easier. I think that is not a favourable way to go, to require development of protocols for delivery in order and loss detection and correction just because of historical reasons for the case that a gateway may be needed in the path. Gatewaying is possible with the gateway considerations in RFC8865. It is better to use the modern features in WebRTC make life easier for the developer. Looking forward to resolve this and get hints on the formulations in the implementors guide part in the attached document. -- GitHub Notification of comment by gunnarhm Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-2389584766 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 October 2024 20:08:53 UTC