14 ms·
So pushing something no one uses, and has significantly narrow uses, and still isn't deployed publicly, into the core... How is that anything but self-serving p
by MichaelGG 12y ago
So pushing something no one uses, and has significantly narrow uses, and still isn't deployed publicly, into the core... How is that anything but self-serving protocol designers? How do they get away with that?
- teach 12y agoMulticast has much more than "significantly narrow uses". When we were studying IPv6 in my network protocols course 20 years ago(!) I remember thinking how useful that would be if widely deployed.
- FeepingCreature 12y agoI'm a private customer, and I use IPv4 Multicast. My ISP uses it to distribute IPTV streams. Don't generalize from "I don't know anybody who uses" to "nobody uses".
- jewel 12y agoA good portion of the bandwidth being used on the Internet could be done over multicast if it were widely supported. For example, popular content on Hulu could be multicast. You'd download the beginning of the video over HTTP but simultaneously tune into the multicast that started the most recently. Once the two streams meet you drop the HTTP connection. If widely deployed this would reduce costs for both Hulu and ISPs, and for places where multicast doesn't work it can fall back to HTTP.
- xorcist 12y agoIt decreases network load (when implemented correctly). Broadcast floods used to be a real problem.