<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">There you go. SSM would be a great solution. Who the hell supports it, though?<DIV><BR class="khtml-block-placeholder"></DIV><DIV>We still get back to the issue of large scale market acceptance. High take rate will be limited to the more popular channels, which are run by large media conglomerates, who are reluctant to let streams out of a closed network.</DIV><DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Gian Anthony Constantine</DIV><DIV>Senior Network Design Engineer</DIV><DIV>Earthlink, Inc.</DIV><DIV>Office: 404-748-6207</DIV><DIV>Cell: 404-808-4651</DIV><DIV>Internal Ext: x22007</DIV><DIV><A href="mailto:constantinegi@corp.earthlink.net">constantinegi@corp.earthlink.net</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR class="Apple-interchange-newline"></SPAN></SPAN> </DIV><BR><DIV><DIV>On Jan 10, 2007, at 12:08 AM, Sean Donelan wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">On Tue, 9 Jan 2007, <A href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</A> wrote:</DIV> <BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Multicast streaming may be a big win when you're only streaming the top</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">5 or 10 networks (for some value of 5 or 10).<SPAN class="Apple-converted-space">� </SPAN>What's the performance</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">characteristics if you have 300K customers, and at any given time, 10%</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">are watching something from the "long tail" - what's the difference between</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">handling 30K unicast streams, and 30K multicast streams that each have only</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">one or at most 2-3 viewers?</DIV> </BLOCKQUOTE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">1/2, 1/3, etc the bandwidth for each additional viewer of the same stream?</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The worst case for a multicast stream is the same as the unicast stream, but the unicast stream is always the worst case.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Multicast doesn't have to be real-time. If you collect interested subscribers over a longer time period, e.g. scheduled downloads over the next hour, day, week, month, you can aggregate more multicast receivers through the same stream.<SPAN class="Apple-converted-space">� </SPAN>TiVo collects its content using a broadcast</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">schedule.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">A "long tail" distribution includes not only the tail, but also the head.<SPAN class="Apple-converted-space">� </SPAN>30K unicast streams may be the same as 30K multicast streams, but</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">30K multicast streams is a lot better than 300,000 unicast streams.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Although the long tail steams may have 1, 2, 3 receivers of a stream, the Parato curve also has 1, 2, 3 streams with 50K, 25K, 12K receivers.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">With Source-Specific Multicast addressing there isn't a shortage of multicast addresses for the typical broadcast usage.<SPAN class="Apple-converted-space">� </SPAN>At least not until</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">we also run out of IPv4 unicast addresses.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">There is rarely only one way to solve a problem.<SPAN class="Apple-converted-space">� </SPAN>There will be multiple</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">ways to distribute data, video, voice, etc.</DIV> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>