The main theme of exploration would be "How would X need to change to support the requirements of functions and serverless computing?"
Some of the broad set of questions to consider include, but are not limited to:
The aim is to understand how the serverless paradigm may force us to rethink existing approaches to designing, implementing and deploying applications and infrastructure. Here is a rough categorization of the above topics into sessions:
Hardware (2 sessions)
(potential topics: switching; interconnects; AQM; disaggregation; optics; what abstractions should the network provide? role of programmable network hardware)
Protocols (2 sessions)
(potential topics: routing control plane; transport, flow and congestion control, socket API, addressing and naming)
Security and availability (2 session)
(potential topics: isolation, access controls, NFs, fault tolerance, function warm up vs. impact on availability, role of the network in above aspects)
Business models (1 session)
(potential topics: “killer apps”, different models of serverless akin to PaaS, IaaS, etc in the Cloud world), design challenges that arise)
Systems (1 session)
(potential topics: granularity of computation; compute control plane (scheduler scheduling and executing DAGs of functions); how to ensure low latency and high throughput task execution; storage; operating systems support; packaging, … )
Monitoring and tracing (1 session)
(potential topics: cross layer; causal tracing; abstractions for gathering statistics)
Programming and formal methods (1 session)
(new programming models; what is the role of verification and formal methods -- does the simplicity of functions make these problems simpler? are network verification etc. impacted by serverless?)