Subject: [Coin] COIN session - comments during Piccolo talk

From: <[email-masked]>
Date: Mon, 23 Nov 2020 11:32:48 +0000

Hi,
Thanks for the jabber comments, during my talk about the Piccolo project. Just following up on them:-

<Stewart Bryant> What arethe privicy considerations on this stuff
Stewart - think you're referring to the vision processing use case. With Sensing Feeling's current product, all the vision processing is done on the camera - only the result is sent to their cloud server. For instance, the count of people, ie de-personalised information - no video is stored or transmitted. So the privacy properties are good I think (especially compared to an alternative approach of shipping /storing video and 'solving' the privacy issue by putting up a notice to warn people).
In general I think in-network computing (/edge computing) can have nice privacy properties. If the analytics function is shipped to the edge, then we can avoid transmitting all data to the central server where the human (data subject) has limited control over it (which I find particularly worrying for health-related data). It would be good if the data subject had some policy control over the edge (/in-network compute /temporary cache - for instance what types of functions could be run). Ideally the analytics function would be able to work on encrypted data, but that seems a way off.

<Kireeti Kompella> phil, in the in-reality scenario, does the edge compute terminate the flow/session (as an alternative to the cloud")?
Kireeti - my guess is that it does terminate the flow (but the project only just started, so design not worked out). I hope the project doesn't build a kludged middlebox.

<Lars Eggert> i'd have gone with Melchizedek for the project name, but it's a bit unwieldly
Quite hard to spell! When we thought of the name, I didn't know Piccolo had anything to do with champagne - just that it was a small flute. It's quite elegant that you can pour the champers out of your piccolo bottle into your flute glass.

Cheers!

Phil