- From: Christer Holmberg via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Mar 2024 14:35:44 +0000
- To: public-webrtc-logs@w3.org
> Also, as Harald noted, RFC 8865 is incompatible with the specification for the WebRTC data channel, > and as a result, it is not implementable. That is not correct. It is true that there is a case where SCTP stream-id collision can occur, if: 1) the offer contains actpass; AND 2) the application uses both DCEP and RFC 8864 at the same time I am not aware of applications that would use both DCEP and RFC 8864 at the same time. WebRTC does not mandate usage of DCEP, AFAIK. So, while there is a case (unlikely to occur, in my expereince) where a collision could occur, that does not mean it is incompatible. -- GitHub Notification of comment by cdh4u Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-2004088255 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 March 2024 14:35:45 UTC