SLIDE 1
RICE: Remote Method Invocation in ICN
Michał Król, Karim Habak, David Oran, Dirk Kutscher, Ioannis Psaras
2
It’s NOT about
- RPC, CORBA, Java RMI
- Tightly-coupled system from (not so)
RICE: Remote Method Invocation in ICN Micha Krl, Karim Habak, David - - PowerPoint PPT Presentation
RICE: Remote Method Invocation in ICN Micha Krl, Karim Habak, David - - PowerPoint PPT Presentation
RICE: Remote Method Invocation in ICN Micha Krl, Karim Habak, David Oran, Dirk Kutscher, Ioannis Psaras Its NOT about RPC, CORBA, Java RMI Tightly-coupled system from (not so) long time ago 2 Static data retrieval Give me data
SLIDE 2
SLIDE 3
SLIDE 4
4 Give me data
Static data retrieval
SLIDE 5
5 Compute this for me c
In-network computation
SLIDE 6
6
In-network computation
- Multiple use-cases
– edge/fog computing, IoT, VR/AR
- Multiple existing frameworks: NFN,
NFaaS, CCNxServe, SCN, NextServe
- Migrate functions where they’re
needed the most
- Populate FIB tables with routes to
services
SLIDE 7
7 No need for a DNS/SDN server
Anycast
SLIDE 8
8
Load control
SLIDE 9
9 c c
Result caching
SLIDE 10
10
Issues
SLIDE 11
11
Client Authorization
SLIDE 12
12
Large Parameter Passing
SLIDE 13
13
Accommodating non-trivial computations
PIT expires
SLIDE 14
14
Accommodating non-trivial computations
SLIDE 15
15
RICE Design
SLIDE 16
16
Design Goals
- Consumer authentication and authorization
- Large parameter passing
- Accommodating non-trivial computations
- Allow result caching
- Adhere to ICN principles
– Pull model – Avoid revealing permanent client identifers – Support client mobility
- Make minimal changes to ICN protocols and
forwarder behaviour
SLIDE 17
SLIDE 18
Naming
SLIDE 19
19
4-way Handshake
- Enable 2-way communication between
producers and consumers
- Shared Secret Derivation
- Client Authentication
- Large Input Parameters Submission
SLIDE 20
4-way Handshake
SLIDE 21
21
Dynamic Content Retrieval
SLIDE 22
22
Network and Application Timescale
- PIT entries use timeouts
- When requesting static content
Interest Satisfaction Time equals RTT
- Generating dynamic content adds a
delay that is unknown to the network
- PIT entries can expiry before
returning the results
SLIDE 23
Network Timescale Application Timescale
- Fast recovery
- No assumption on
execution time
- Huge overhead
- Challenging
bandwidth allocation
- Low overhead
- Regular Bandwidth
allocation
- Slow Recovery
- Requires a lot of
knowledge
We want to decouple application timescale from network timescale
SLIDE 24
Thunks
SLIDE 25
Network Timescale
SLIDE 26
Application Timescale
SLIDE 27
Acknowledgements
SLIDE 28
29
Results
SLIDE 29
30
Handshake
SLIDE 30
31
Thunks
SLIDE 31
32
Thunks
SLIDE 32
33
Referentially opaque function
SLIDE 33
34
Referentially transparent function
SLIDE 34
Thunks
SLIDE 35
36
Prototype
SLIDE 36
37
Limitations
- Thunks require accurate computation
time estimation
– Overestimation increases the delay – Underestimation increases overhead
- Referentially transparent functions
can be cached under diferent names
– Can be solved by using forwarding hints
SLIDE 37
38
Conclusion and Future Work
- Client authentication, large parameter
passing, accommodating non-trivial computation using a 4-way handshake + thunks
- Generic API for function invocation
- RICE can be a basis for many NFN-
inspired systems.
- Prototype and demo
SLIDE 38
39
In the future
- Integration with routing hints and NACKs
- Implement highly-scalable server
- Developing higher-layer abstractions on
top of RICE.
– pushing data (for custodial transfer, re-publishing,
storing)
– support for more pervasive in-network computing – rethinking and re-engineering existing
applications, especially web
SLIDE 39
40