Table of Contents
Fetching ...

Yodel: A Layer 3.5 Name-Based Multicast Network Architecture For The Future Internet

Morteza Moghaddassian, Alberto Leon-Garcia

TL;DR

Yodel tackles the challenge of providing scalable, multi-domain multicast on the existing Internet by introducing a name-based Layer 3.5 architecture that operates across domain boundaries without requiring a clean-slate rebuild. It leverages SDN for centralized control and a hierarchical conceptual model (Valleys, Namespaces, Communities) to enable divide-and-conquer management of naming, routing, and policy. A key novelty is the name-group binding principle, push-based delivery, multi-tenancy support, and Layer 3.5 interdomain forwarding, together with an Infrastructure Setup and Host Twins for resiliency. The approach promises rapid deployability and interoperability with current IP-based networks while offering flexible multicast service models, including Yodel-SSM.

Abstract

Multicasting refers to the ability of transmitting data to multiple recipients without data sources needing to provide more than one copy of the data to the network. The network takes responsibility to route and deliver a copy of each data to every intended recipient. Multicasting has the potential to improve the network efficiency and performance (e.g., throughput and latency) through transferring fewer bits in communicating the same data to multiple recipients compared with unicast transmissions, reduce the amount of networking resources needed for communication, lower the network energy footprint, and alleviate the occurrence of congestion in the network. Over the past few decades, providing multicast services has been a real challenge for ISPs, especially to support home users and multi-domain network applications, leading to the emergence of complex application-level solutions. These solutions like Content Delivery and Peer-to-Peer networks take advantage of complex caching, routing, transport, and topology management systems which put heavy strains on the underlying Internet infrastructures to offer multicasting services. In reality, the main motivation behind the design of these systems is rather sharing content than offering efficient multicast services. In this paper, we propound Yodel, a name-based multicast network architecture that can provide multi-domain multicast services for current and future Internet applications. Compared to the wider array of other name-based network architectures with clean-slate infrastructure requirements, Yodel is designed to provide multicast services over the current Internet infrastructure. Hence, Yodel puts forward several design goals that distinguish it from other name-based network architectures with inherent multicast capabilities. This paper is prepared to discuss the Yodel architecture, its design goals, and architectural functions.

Yodel: A Layer 3.5 Name-Based Multicast Network Architecture For The Future Internet

TL;DR

Yodel tackles the challenge of providing scalable, multi-domain multicast on the existing Internet by introducing a name-based Layer 3.5 architecture that operates across domain boundaries without requiring a clean-slate rebuild. It leverages SDN for centralized control and a hierarchical conceptual model (Valleys, Namespaces, Communities) to enable divide-and-conquer management of naming, routing, and policy. A key novelty is the name-group binding principle, push-based delivery, multi-tenancy support, and Layer 3.5 interdomain forwarding, together with an Infrastructure Setup and Host Twins for resiliency. The approach promises rapid deployability and interoperability with current IP-based networks while offering flexible multicast service models, including Yodel-SSM.

Abstract

Multicasting refers to the ability of transmitting data to multiple recipients without data sources needing to provide more than one copy of the data to the network. The network takes responsibility to route and deliver a copy of each data to every intended recipient. Multicasting has the potential to improve the network efficiency and performance (e.g., throughput and latency) through transferring fewer bits in communicating the same data to multiple recipients compared with unicast transmissions, reduce the amount of networking resources needed for communication, lower the network energy footprint, and alleviate the occurrence of congestion in the network. Over the past few decades, providing multicast services has been a real challenge for ISPs, especially to support home users and multi-domain network applications, leading to the emergence of complex application-level solutions. These solutions like Content Delivery and Peer-to-Peer networks take advantage of complex caching, routing, transport, and topology management systems which put heavy strains on the underlying Internet infrastructures to offer multicasting services. In reality, the main motivation behind the design of these systems is rather sharing content than offering efficient multicast services. In this paper, we propound Yodel, a name-based multicast network architecture that can provide multi-domain multicast services for current and future Internet applications. Compared to the wider array of other name-based network architectures with clean-slate infrastructure requirements, Yodel is designed to provide multicast services over the current Internet infrastructure. Hence, Yodel puts forward several design goals that distinguish it from other name-based network architectures with inherent multicast capabilities. This paper is prepared to discuss the Yodel architecture, its design goals, and architectural functions.
Paper Structure (31 sections, 7 figures)

This paper contains 31 sections, 7 figures.

Figures (7)

  • Figure 1: Yodel Design Goals and Considerations
  • Figure 2: The current Internet protocol stack, demonstrating the adaption of a new layer 3.5 for handling interdomain networking.
  • Figure 3: The Yodel management tree, featuring the Yodel conceptual model as well as the routing and forwarding management objects.
  • Figure 4: The Yodel Network Infrastructure (H=Host, EN=Edge Node, CN=Connector Node, and P/C=Data Producer/Consumer).
  • Figure 5: The Yodel YNI in its default IPv6-like presentation.
  • ...and 2 more figures