W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2017

Re: [webrtc-pc] Should even/odd id validation be enforced in createDataChannel when negotiated is true?

From: jesup via GitHub <sysbot+gh@w3.org>
Date: Thu, 22 Jun 2017 14:49:25 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-310403292-1498142964-sysbot+gh@w3.org>
> 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).
Specifying the ID with negotiated = false should be ignored.  If you want, we could complain or reject it.  I suspect the only people doing it are doing it by accident (specify everything!) and aren't depending on it (since it does nothing currently).

> 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.
I wonder how many people are using negotiated=true (and actually have a reason to do so)

> Change the draft-ietf-rtcweb-data-protocol requirement to only apply to IDs generated by the user agent.
There was a lot of discussion about this in the IETF meetings... (maybe in webrtc ones).  Someone should pull the minutes and check.  Honestly it was long enough ago and argued over enough (lots of opinions) that I honestly can't remember how we ended up here and what the expected way of dealing with opening-before-connection was.

GitHub Notification of comment by jesup
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1413#issuecomment-310403292 using your GitHub account
Received on Thursday, 22 June 2017 14:49:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC