- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2017 10:17:36 +0000
- To: public-webrtc-logs@w3.org
The two modes specified by RTCIceTransportPolicy are the modes that can be chosen by the Javascript application. They limit what candidates are shown to signalling - based on the premise that the local Javascript can be trusted, but the signalling intermediaries and the remote party can't be. The four modes described in draft-ietf-rtcweb-ip-handling are the modes that can be chosen by the browser, based on local configuration. They limit what candidates are shown to the Javascript - based on the premise that the Javascript can't be trusted. It would be a security problem if the application could pass a parameter to loosen the browser's IP candidate policy, so the only values that can be reasonably passed are the ones that make the policy tighter. Which particular values did you want to add? -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1644#issuecomment-339283869 using your GitHub account
Received on Wednesday, 25 October 2017 10:17:38 UTC