- From: Gunnar Hellström via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Jan 2024 17:26:35 +0000
- To: public-webrtc-logs@w3.org
I would like to see the API support conveying the dcsa attribute contents. Then it would be easier to fully implement RFC 8865 with its full intentions. There seems also to be a conflict to handle the stream ID, if you want to use the API to create the data channel but add the dcsa negotiation beside the API.Then dcsa has the stream id as a parameter to set, but the API usually controls setting the stream ID when you request the data channel creation. But, how about both updating section 14 and trying to create advice in the normative part of the document for how to support RFC 8865 through the API and something defined extra. Yes I would also expect emergency communication to start looking at supporting WebRTC. -- GitHub Notification of comment by gunnarhm Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2931#issuecomment-1919571049 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 January 2024 17:26:37 UTC