From SRM to NDN: Lessons on Data-Centric Communication from Three Decades of Networking
TL;DR
The SRM experience suggests a broader architectural lesson: scalable multiparty communication benefits from aligning network delivery mechanisms with the data-centric semantics of applications—a principle that becomes increasingly important as collaborative systems, content platforms, and large-scale multiparty applications proliferate.
Abstract
The 1995 SIGCOMM paper "A Reliable Multicast Framework for Light-weight Sessions and Application-Level Framing" (SRM) introduced a receiver-driven, data-centric approach to reliable multiparty communication, in which receivers recover losses by explicitly requesting missing data. Three decades later, we revisit SRM as a case study in data-centric networking design. Although SRM achieved scalability in controlled environments, experience with IP multicast exposed persistent inefficiencies rooted in an architectural mismatch: applications identify and request data, while the network layer forwards packets by address and is oblivious to data identity. We argue that this mismatch, rather than particular protocol mechanisms, prevents recovery from being localized to where data is needed and available. Using Named Data Networking (NDN) as a contrasting design point, we show how making data identifiers visible to the network enables localized retrieval and recovery. The SRM experience suggests a broader architectural lesson: scalable multiparty communication benefits from aligning network delivery mechanisms with the data-centric semantics of applications—a principle that becomes increasingly important as collaborative systems, content platforms, and large-scale multiparty applications proliferate.