8 ms·
Ooh I remember mbone! At the time I was a kid and didn't have an internet connection at home, but I remember Wired talking about it back when they covered tech
by nailer 7y ago
Ooh I remember mbone! At the time I was a kid and didn't have an internet connection at home, but I remember Wired talking about it back when they covered tech in detail.
Does anyone on HN know what happened to it?
- Hikikomori 7y agoScalability issues, no interest from commercial ISPs (I suspect). It was the precursor to modern multicast routing protocols (PIM), but its still a challenge to run large multicast networks today. Unicast (with CDN's) just won because it so much simpler. Multicast today is mostly used by ISPs for their own IPTV services.
- mvidal01 7y agoAnd in large corporate networks.
- iso1631 7y agoIndeed, we run multicast over 4 continents. One problem with multicast is the lack of real understanding by network engineers, because it's so rare (certainly anything that involves PIM), few people really get it, fewer tools are available to work out what's going on. In the broadcast industry, multicast at a local level is very important though - with SDI being replaced by things like 2022-6 and 2110. I believe that's mainly at the IGMP/layer 2 level though, and there aren't many 2110 implementations over routers.
- mhandley 7y agoI spent a decade working on multicast, helped write some of the second generation multicast conferencing tools, and co-authored a number of the standards. Generally, the issue was that multicast requires per group or per-source state in routers, and router memory was a scarce resource. This made it hard to scale globally. It also made forwarding problems hard to diagnose, taking up operators' time. These costs, plus an unclear connection between who benefitted from multicast and who paid for it made it difficult for core ISPs to justify. And that meant that commericial content or application providers needed to implement a plan B in case multicast wasn't available, and if that worked well enough, they didn't bother with also doing multicast. Still, RTP and SIP came directly out of the MBone, and they bootstrapped the whole Internet multimedia phenomena we're all enjoying today while working from home.
- q3k 7y agoI wouldn't exactly say I 'enjoy' using SIP.
- mhandley 7y agoSorry about that! It did rather morph from our nice simple initial design into a monster once it met the real world.
- organsnyder 7y agoAs everything is wont to do.
- jimmySixDOF 7y agoWell it sure beat using H.323
- zajio1am 7y agoWhile it has some wrinkles, i must say that i have generally much better experience with SIP tools than with a current wave of WebRTC tools.
- wolrah 7y agoWhy not? Personally I enjoy SIP itself greatly, it works well and is basically human readable, to the point that I can explain it to non-technical people. My main problems over 15 years of working with SIP have been with "helpful" boxes in the middle tampering with my SIP messaging. NAT used to cause a bunch of problems, but these days I have workarounds for most cases that work great until the aforementioned middleboxes start "helping". Give me a NAT-free network where the packet that reaches the far end is the same one I sent and my SIP systems will be quite happy.
- the8472 7y agoThe downside is that CDNs are far less democratic than hypothetical end-to-end multicast support. Imagine being able to stream to thousands of users from a single machine with a single 100Mbit NIC.