All things related to multicast

[Alan Crosswell <>]

We were 2.3G inbound and about 2G outbound on our commodity links. We  
were flat-topped at 200M (contracted rate) in and out on our NYSERNet  
I2 connection. Researchers (if any) were hosed by octoshape.

We ran a local MPEG-2 Vbrick multicast of C-SPAN for a handful of  
congregation areas.
/a

On Jan 23, 2009, at 5:18 PM, Bill Owens 
<>
 wrote:

> On Fri, Jan 23, 2009 at 04:09:53PM -0600, Julian Y. Koh wrote:
> > Now, we had definite pains on some of our external traffic due to the
> > Octoshape P2P streaming that CNN was employing, but luckily we  
> > already had
> > our multicast traffic bypassing the equipment that was hurting.   
> > Otherwise
> > life would have been not so good for us.  As it was, the pain that  
> > people
> > were experiencing with the unicast streams (and I'm including the  
> > Octoshape
> > streams there as well) is going to serve as a good leverage for  
> > publicizing
> > the multicast-based services.
>
> It would have been bitterly ironic if the all-but-unannounced P2P  
> pseudo-multicast traffic had interfered with the one high-grade  
> multicast feed that was available to us.
>
> We saw unicast traffic peaks at almost 1.2 Gbps on our egress  
> connections, with several campuses maxing out their connections, all  
> attributable to Octoshape (since NYSERNet doesn't provide transit to  
> any commercial streaming sources). I'm glad that the network was  
> used, but I do wish that they could come up with something a bit  
> smarter.
>
> Bill.