Tussles for Edge Network Caching ITU Workshop on "Future Trust and Knowledge Infrastructure", Phase 1 Geneva, Switzerland, 24 April 2015 Tussles for Edge Network Caching Patrick Poullie Jr. Researcher Communication Systems Group University of Zurich, poullie@ifi.uzh.ch

Contents Investigated scenario Tussle Analysis Applied Tussle Analysis Stakeholders and tussles for investigated scenario Evolution of one tussle Conclusions Slide 2 of 10

Investigated Scenario Traditional data delivery Internet Social Networks Edge ISP Home routers User controlled uNaDa home router with custom software and storage Energy efficiency Social content: more complex in terms of caching compared to pure multi-media platform content Goal: traffic reduction and QoS increase End-users Slide 3 of 10

Investigated Scenario Envisioned approach Internet Social Networks Edge ISP Nano data centers End-users Slide 3 of 10

Tussle Analysis Y.3013: Socio-economic Assessment of Future Networks by Tussle Analysis Complementation of future network design and standardization by a socio-economic assessment Analysis goal is to find satisfying outcome for all stakeholders Developed in SG13 – WP3 – Question 16 Environmental and socio-economic sustainability in future networks and early realization of future networks Slide 4 of 10

Tussle Analysis’ Three Steps Step 1: Identify all affected stakeholders Step 2: Identify stakeholders’ interests and conflicts between these and means available to them tussle tussle tussle Step 3: Identify means stakeholders will take according to their interests and resulting interactions 1. All stakeholders of this functionality derive a payoff that is considered fair (and have no means to increase their payoff), wherefore they will not take means to change the outcome (i.e., step 3.c does not need to be applied) and thus the tussle will not evolve further, and; 2. No stakeholder of another technology, who was receiving a fair payoff before, gets an unfair payoff after this tussle equilibrium has been reached (i.e., step 3.c does not need to be applied). No Stakeholder can or wants to change the outcome Tussle cannot be avoided by technology changes Slide 5 of 10

Scenario Stakeholders and Interests Malicious users / data miners Internet Service Providers Reduce network load Sell in-network caching Access to social content Internet ISP Cloud Service Provider (CSP) Reduce NW load particularly at peering points High QoS Privacy energy and bandwidth utilization Content control Data mining Ad placement End- users Slide 6 of 10

Scenario Tussles Content control End-user privacy uNaDa deployment CSPs not want third parties to mine their data End-user privacy End-users not want third parties to access their private info uNaDa deployment End-users require compensation for hosting uNaDa Change in peering traffic uNaDas may serve users in other access networks Increases traffic for ISPs with uNaDas! Distribution of illegal content Slide 7 of 10

Tussle Evolution (1) uNaDas get deployed and store content unencrypted High traffic savings for CSPs and ISPs Low content control for CSPs End-users protest due to privacy loss and demand Thus, uNaDas only store content accessible to owner Comprehensible privacy concept (RFC 7234 not applicable) Decreases caching efficiency CSPs distribute encrypted content to uNaDas and handle keys centralized Regain content control User privacy ensured High caching efficiency Slide 8 of 10

Tussle Evolution (2) Content Control Tussle: End-user Privacy Tussle: uNaDs store encrypted content, keys are provided by servers Content is served by traditional data centers CSP CSPs have sole control over content More control but less caching efficiency Content Control Tussle: All content cached unencrypted 3. Parties can access content without permission Malicious users / data miners End-users feel their privacy is protected End-users End-user Privacy Tussle: uNaDas cache only content that is accessible to its owner End-users feel their privacy is not protected Malicious users / data miners Regulator intervenes Slide 9 of 10

Conclusions CSP need to support uNaDas Otherwise content cannot be cached Access providers need to support uNaDas Else end-users can not be compensated for installing them Open tussle: unwanted peering Promising approach Caching content encrypted and handling keys centralized One set of keys for each user and privacy level Because of TA we know this now Slide 10 of 10

Acknowledgements