Subscribes to source-specific multicast IP channels and receives the UDP payloads for that traffic in web applications. This allows web developers to use network and server resources much more efficiently wherever multiple receivers are located inside networks that forward and replicate multicast traffic, whenever transmitting popular data (anything where the same content has to be delivered to many different end users).

Motivation

Currently, Web application developers have no API for receiving multicast traffic from the network. All traffic for web applications thus requires a one-to-one connection with a remote device. Multicast IP provides a one-to-many data stream, and enables packet replication by the network, enabling efficient use of broadcast-capable physical media and reducing load on congested shared paths. Enabling Web applications to receive multicast would solve the receiver distribution problem that contributes to the current under-utilization of multicast on the internet. This effort is coupled with a standardization effort in the MBONED working group at IETF and ongoing trials with multiple network operators to deploy a standardized approach for ISPs to ingest externally sourced multicast UDP traffic.

Status in Chromium

Blink>Network


No active development

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signal
  • No signals

Owners

Intent to Prototype url

Intent to Prototype thread

Comments

NB: We had a previous Intent-to-Prototype email here: https://groups.google.com/a/chromium.org/g/blink-dev/c/JVKSTHFiDzo That's part of the same project.

Last updated on 2021-02-24