1. ICN, IoT and the Fog Enabling computation at the edge Marcel Enguehard
April 13th, 2017
RIOT INRIA

2. Information Centric Networking
User application
Each retrievable content is named
Name-based routing
Pull based model w/ symmetric routing
Every node is a cache
Interest: /roomA/temperature
Content: 20°C
Sensor board

3. Vanilla ICN Forwarding
Forward to “faces”
2 modules: Forwarding Interest Base (FIB) and Pending Interest Table (PIT)
Interest  LPM in FIB
Content  Symmetric routing through PIT
Faces = {application, neighbours, usw}

4. Why ICN for IoT ICN-IoT leverages the salient features of ICN:
Name-based Communication model
Seamless mobility support, scalability, and efficient content and service delivery
Simplicity of the stack
Lower memory/energy footprint [Baccelli, ICN’14]
Security
Content-based, No (D)TLS connection

5. Low latency applications In-network processing Local storage
The Fog layer
Low latency applications
In-network processing
Local storage
Geography-aware applications

6. Example use-case https://opendata.paris.fr
{ "id": 6177, "name": "Terre plein - Kiosque",
"type": "turnstile", "metrics": [
{ "id": "direction_1",
"name": "Vers le Nord" }, {
"id": "direction_2",
"name": "Vers le Sud" } ],
"classes": [ "all" ],
"location": { "latitude": ,
"longitude":

7. Mobility and low-latency in the cloud
App
App
Fog
Access

8. Challenges with migration
Network protocol
Service availability
Security:
Access control on compute node (for app and from cloud)
Access control on application
Access control on node

9. Connection-less model Object-based security Name-based model
Why ICN for the Fog?
Connection-less model
Easy load-balancing, location-independent
Object-based security
Mobility of the device
Application migration
Name-based model
Embedded caching
Named-Function Networking

10. Connection-less model – location independence
App
App

11. Connection less-model – Load-balancing
App
App
PER PACKET
Handover

12. Object-based security
App
App

13. Name-based model
App
App
/app

14. Network emulation with vICN
vICN: large-scale emulation platform
Open source in Linux Foundation fd.io project
Integrated with full ICN suite
Industry need: full vertical, low-cost testing, IPR, control

15. vICN

16. vICN topology declaration
“resources”: { {
"type": "Physical",
"name": "server",
"hostname":  "localhost" },
"type": "LxcContainer",
"image": "ubuntu1604-cicnsuite-rc2",
"name": "core1",
"node": "server »
"type": "MetisForwarder",
"node": "core1" }
...
... {
“type”: “Link”,
“src_node”: “core1”,
“dst_node”: “core2” },
"type": "LxcContainer",
"image": "ubuntu1604-cicnsuite-rc2",
"name": "prod1",
"node": "server »
"type": "MetisForwarder",
"node": "prod1" }

17. vICN – Example

18. vICN – RIOT integration
RIOT with ccn-lite
Link emulator
Gateway
Control interface

19. vICN –RIOT integration – what’s missing
Device emulation: RIOT as Linux process in Linux Container
Link model: model from ns3
Gateway: face on socket-based forwarder
Security?
L2 encryption
ICN signature