FACILITATING ICN DEPLOYMENT WITH AN EXTENDED OPENFLOW PROTOCOL - PowerPoint PPT Presentation

FACILITATING ICN DEPLOYMENT WITH AN EXTENDED OPENFLOW PROTOCOL Piotr Zuraniewski, Niels van Adrichem, Wieger Ijntema, Daan Ravesteijn (TNO) Borgert van der Kluit, Ray van Brandenburg (former TNO)

CONNECTING ICN „ISLANDS” One of deployment problems with ICN: „islands” separated by traditional network Manual tunnels set-up to enable communication: tedious, error-prone etc. a) Available in cache? ICN b) Pending in PIT? c) If not, then forward Non-ICN network ICN Data interest … … ICN Data source

SDN ENHANCED ICN FORWARDING Update forwarding entries ICN repository “app” Perform any action to forward via legacy network (e.g., rewrite What’s the nearest IP, push MPLS,...) SDN controller ICN node containing the data object of interest? Non-ICN network ICN Demo: with SDN gateways Non-ICN network = IPv4 SDN Controller = Ryu + OpenFlow 1.3 SDN SDN switch = CPDQ softswitch ICN SDN modified to handle eBPF programs to match on ICN names ICN ICN node = nfd 0.4.1 ICN app = Ryu app gathering ICN Data a)Forwarding entry available ? routing information source Then just forward  b)If not, then ask controller