Re: [webrtc-pc] RTCIceCandidate: how is extensibility handled?

@taylor-b I need a little more clarification, I appreciate your patience. Can you explain how the values of these properties are populated? (from

- [ ] `foundation`
- [ ] `priority`
- [ ] `ip`
- [ ] `protocol`
- [ ] `port`
- [ ] `type`
- [ ] `tcpType`
- [ ] `relatedAddress`
- [ ] `relatedPort`


> And if the effort to specify it is too high then i think it should be left to javascript.

I think it could be as simple as adding the following sentence (or something similar) to each property definition: 

"The value of [this property foo] must be the corresponding value derived from parsing the candidate-attribute string as described by [15.1]( of [[ICE]]( If no corresponding value is present, the value must be `null`."

GitHub Notification of comment by rwaldron
Please view or discuss this issue at using your GitHub account

Received on Thursday, 18 May 2017 16:56:52 UTC