- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2023 10:36:14 +0000
- To: public-webrtc-logs@w3.org
Sounds like we have agreement on what to do, and Chrome [has a fix](https://webrtc-review.googlesource.com/c/src/+/297860). Question remains: any clarification needed on the spec side? JSEP: > Lastly, if a data channel has been created, an "m=" section MUST be generated for data. The <media> field MUST be set to "application", and the <proto> field MUST be set to "UDP/DTLS/SCTP" [[RFC8841](https://www.rfc-editor.org/rfc/rfc8829.html#RFC8841)]. The <fmt> value MUST be set to "webrtc-datachannel" as specified in [[RFC8841](https://www.rfc-editor.org/rfc/rfc8829.html#RFC8841)], [Section 4.2.2](https://www.rfc-editor.org/rfc/rfc8841#section-4.2.2). "has been created" includes any past created ones, even if closed. So close this issue? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2839#issuecomment-1471700038 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 March 2023 10:36:16 UTC