9. Conclusions
In this paper we take a look at some practical considerations in the implementation of FIB caching. We extend previous work in significant ways by looking at practical issues, such as charac- terization of cache misses, queuing issues (buffer occupancy and delay), memory bandwidth requirements and robustness against 652 cache pollution attacks. We used traces collected at links from our regional ISP to a Tier-1 ISP for our analysis. Our design uses a cacheable FIB to avoid the cache hiding problem, and we presented an algorithm to convert a regular FIB to a cacheable FIB. Our work has some limitations. First, we only look at packet traces from a single regional ISP. We therefore cannot evaluate cache performance at core routers, where traffic may be more di- verse causing hit rates to drop. While we do not have access to data from core routers to answer this question (we need a packet 661 trace and a simultaneous snapshot of the FIB at a core router), the tools and methodology we developed are applicable to a core en- vironment and we plan to repeat the study once we have an ap- propriate dataset. Are there trends that may invalidate the benefits of FIB caching? On the contrary, recent trends such as traffic concentra- tion to major social networks, search engines that reside in data- centers [14] and CDNs make caching even more likely to provide benefits. In these environments, traffic becomes more focused and likely to hit a smaller set of prefixes, resulting into a more stable working set.