# Authors: EPFLs (JP & team, Marcel, Mathias & Daniele, Ed, Jim, Carmela & team), ETHs (Srdjan, Kenny, Dennis J.), Cas Cremers, Niels, Seda, Michael, Bart, Nigel

• # Acks: Ciro, Alain, Reuben, 

# Need for technological solution

# Technology as a solution, not a new problem. Design respect, privacy, and purpose limitation

• Decentralized vs centralized vs Asia-data-hungry
• Then came The Protocol

# Technology alone is not a solution: hurdles of integration

• Bluetooth limitations and attack surface
• Integration in OS / Phone <-- GAEN adoption
• Integration in Health system
• Many stakeholders! Legal, doctors, users

# Many lessons for the future, and 

• # More privacy engineering beyond the protocol
  • Obstacles: the phone platform is not a PC (bandwidth, battery, ...)
  • Others put constraints: GAEN protocols, new functions, external mainteinance functionality, legal
• # Adoption
  • Get stakeholders on board
  • Communication is key
  • PETS are hard to explain -- people don't believe this is not a problem (pre-conditioned judgement)
• # Bluetooth performance / risk assessment
  • Not a CS / EE paper, reality -> the goal is to be as good as the human, not perfect (GAEN frequency)
  • Constrained by GAEN's API design decisions

# The future is now -> CrowdNotifier.