- From: Rick Waldron via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 May 2017 16:56:41 +0000
- To: public-webrtc-logs@w3.org
@taylor-b I need a little more clarification, I appreciate your patience. Can you explain how the values of these properties are populated? (from https://w3c.github.io/webrtc-pc/#rtcicecandidate-interface) - [ ] `foundation` - [ ] `priority` - [ ] `ip` - [ ] `protocol` - [ ] `port` - [ ] `type` - [ ] `tcpType` - [ ] `relatedAddress` - [ ] `relatedPort` @foolip > 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](https://tools.ietf.org/html/rfc5245#section-15.1) of [[ICE]](https://tools.ietf.org/html/rfc5245). If no corresponding value is present, the value must be `null`." -- GitHub Notification of comment by rwaldron Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1211#issuecomment-302470331 using your GitHub account
Received on Thursday, 18 May 2017 16:56:52 UTC