Named Data Networking for Content Delivery Network Workflows
Rama Krishna Thelagathoti, Spyridon Mastorakis, Anant Shah and, Harkeerat Bedi, Susmit Shannigrahi

TL;DR
This paper evaluates Named Data Networking's potential benefits for CDN workflows, comparing its performance to HTTP in various network conditions and highlighting its advantages in packet loss resilience and lower latency.
Contribution
It provides an empirical comparison of NDN and HTTP for CDN workflows, demonstrating NDN's advantages in packet loss scenarios and latency reduction.
Findings
NDN performs better under packet loss conditions.
TTFB is lower in NDN (~50ms) compared to HTTP (~100ms).
NDN supports transparent failover in CDN scenarios.
Abstract
In this work we investigate Named Data Networking's (NDN's) architectural properties and features, such as content caching and intelligent packet forwarding, in the context of a Content Delivery Network (CDN) workflows. More specifically, we evaluate NDN's properties for PoP (Point of Presence) to PoP and PoP to device connectivity. We use the Apache Traffic Server (ATS) platform to create an HTTP, CDN-like caching hierarchy in order to compare NDN with HTTP-based content delivery. Overall, our work demonstrates that properties inherent to NDN can benefit content providers and users alike. Our experimental results demonstrate that HTTP is faster under stable conditions due to a mature software stack. However, NDN performs better in the presence of packet loss, even for a loss rate as low as 0.1%, due to packet-level caching in the network and fast retransmissions from close upstreams…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
