- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Sat, 17 Sep 2016 00:11:44 +0000
- To: public-webrtc@w3.org
taylor-b has just created a new issue for https://github.com/w3c/webrtc-pc: == Specify when a data channel's ID is assigned, and what the `id` attribute returns when no ID is assigned. == This is an issue I noticed when working on a solution for issue #746. The [WebRTC data channel establishment spec](https://tools.ietf.org/html/draft-ietf-rtcweb-data-protocol-08#section-6) requires that DTLS clients choose odd stream IDs, and DTLS servers choose even IDs. However, the DTLS role may not be known at the time of creating a data channel. So, until the role is determined, what does the `id` attribute return? It's worth noting that both Chrome and Firefox currently return an ID of 65535, which is guaranteed to be out of range (the maximum usable ID is 65534). But it seems more "correct" to make the attribute nullable. And then, when should a user script expect the ID to be populated? When the stable signaling state is reached with an SCTP media description negotiated? That would seem reasonable to me. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/795 using your GitHub account
Received on Saturday, 17 September 2016 00:12:48 UTC