- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Jun 2017 05:32:17 +0000
- To: public-webrtc-logs@w3.org
> But I don't really follow the motivation behind allowing custom ID to be set for all cases. It makes sense to provide ID when negotiated is false, but when negotiated is true, it doesn't really make sense for applications to be exposed to this kind of low level details. I agree. So, I see three options: 1. Say "you can only specify the ID when `negotiated` is `true`". Would break existing apps (though I don't know why they'd need this functionality in the first place). 2. Once the DTLS role is determined, close the data channel with an error if the ID is invalid. Is also bound to break existing apps, though it would be following draft-ietf-rtcweb-data-protocol to the letter. 3. Change the draft-ietf-rtcweb-data-protocol requirement to only apply to IDs generated by the user agent. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1413#issuecomment-310279891 using your GitHub account
Received on Thursday, 22 June 2017 05:32:23 UTC