- From: Zhu, Jianjun <jianjun.zhu@intel.com>
- Date: Thu, 21 Jun 2018 15:27:21 +0000
- To: Iñaki Baz Castillo <ibc@aliax.net>
- CC: Peter Thatcher <pthatcher@google.com>, "misi@niif.hu" <misi@niif.hu>, WebRTC WG <public-webrtc@w3.org>
Privacy and security are definitely important. I'm not saying that encryption should be removed. I'm just wondering if there is any use case requires an API to disable encryption for insecure origins. But non-https is going to be history, maybe there is no reason to add features for insure sites.
Best Regards,
Jianjun
On 2018/6/21, 6:17 PM, "Iñaki Baz Castillo" <ibc@aliax.net> wrote:
On Tue, 19 Jun 2018 at 09:29, Zhu, Jianjun <jianjun.zhu@intel.com> wrote:
>>
>> How does disabling encryption help other than saving some minimal CPU? You can still do broadcasting and DRM even if there is hop-by-hop encryption.
>
> Besides minimizing latency and battery usage, I think it also helps to reduce the binary size of a WebRTC endpoint running on IoT devices or mobile phones.
It also reduces the privacy of the communication. No. Encryption is
required, even more in IoT devices.
--
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Thursday, 21 June 2018 15:27:52 UTC