Routing Server apps register their name prefixes with the local router Routers announce name prefixes into the routing system Conventional routing protocol can be used to compute the paths to each name prefixes New routing protocols are also possible 21
21 Routing Server apps register their name prefixes with the local router. Routers announce name prefixes into the routing system. Conventional routing protocol can be used to compute the paths to each name prefixes. New routing protocols are also possible
Caching w Universal caching by routers helps in several different scenarios multicast asynchronous retrieva Congestion control Mobility support How much memory/ disk does it take? Routers already use memory for buffering, but not caching since no way to identify the content With named data, change mru to Lru replacement policy Possible add-on services by ISPs: selling extra cache for specific contents 22
22 Caching Universal caching by routers helps in several different scenarios multicast asynchronous retrieval Congestion control Mobility support How much memory/disk does it take? Routers already use memory for buffering, but not caching since no way to identify the content. With named data, change MRU to LRU replacement policy. Possible add-on services by ISPs: selling extra cache for specific contents
Transport no need for flow control k Interest does that In-network congestion control By controlling the number of pending interests to control the data rate Quicker local recovery due to cache Retx doesnt have to start all over again from the producer No transport protocol in the traditional sense The apps need naming convention, name discovery, and maybe end-to-end reliability 23
23 Transport No need for flow control Interest does that. In-network congestion control By controlling the number of pending interests to control the data rate. Quicker local recovery due to cache. Retx doesn’t have to start all over again from the producer. No transport protocol in the traditional sense. The apps need naming convention, name discovery, and maybe end-to-end reliability
Robust Packet Delivery The ultimate goal of routing and forwarding is to deliver packets The ideal is what Paul Baran called" perfect switching": be able to deliver packets in the presence of faults as long as the destination is still reachable w We study: k Evaluate ndn vs IP Explore some design choices in NDN forwarding strategIes without considering the benefits and impact of caching (next step NDN Retreat May 2011 24
Robust Packet Delivery The ultimate goal of routing and forwarding is to deliver packets. The ideal is what Paul Baran called “perfect switching”: be able to deliver packets in the presence of faults as long as the destination is still reachable. We study: Evaluate NDN vs. IP Explore some design choices in NDN forwarding strategies. without considering the benefits and impact of caching (next step) May 2011 NDN Retreat 24
Data Delivery in IP Routing plane computes the best paths data plane(packet forwarding simply follows the paths Achieving perfect switching requires perfect routing - reality is far from it, e.g Prefix hijack(routing is fooled) Link failure (routing convergence is slow Congestion(routing is not aware of the problem NDN Retreat May 2011
Data Delivery in IP Routing plane computes the best paths data plane (packet forwarding) simply follows the paths. Achieving perfect switching requires perfect routing – reality is far from it, e.g., Prefix hijack (routing is fooled) Link failure (routing convergence is slow) Congestion (routing is not aware of the problem) May 2011 NDN Retreat 25