Hacker News Reader

Comment by juiceandjuice | Hacker News Reader

Cool, maybe they can deploy it at comcast and deliver content via the same magical content pipe comcast uses for their xfinity service.

View on HN

I think Comcast would be pretty opposed to let a competing product into their not-for-sale DC space. The real benefit here is that it saves ISPs on peering charges. Comcast, AFAIK, does a lot of their own peering and has financial motivations to NOT let Netflix into their DCs (onDemand.)

We will see how this plays into the me neutrality battle...

Comcast does not operate their own video delivery infrastructure. They contract that out to Akamai. Furthermore, Comcast will happily sell non-transit, A.K.A. paid peering, to all who come. They don't (and never have) sell colocation (DC space). Presumably, Netflix is just going to buy access to the Comcast network, same as every other CDN has done.

http://www.comcast.com/dedicatedinternet/

Most of the large CDN's already deliver straight into Comcast's network. Last I heard Netflix was already paying Level3 to do this. Xfinity doesn't have a magic pipe, all the content and deliver is internal to the Comcast network so its its own "CDN".

It was a joke, the hint was the use of the word magic.

More info on Comcast's DiffServ magic: http://ber.gd/post/23025893856/comcast-traffic-prioritizatio...

Which Comcast says isn't happening.

http://blog.comcast.com/2012/05/the-facts-about-xfinity-tv-a...

I don't really want to rehash that whole discussion, but Comcast admits they're using DiffServ tagging. People are just debating whether it's a form of "prioritization" or not.

Reply on news.ycombinator.com