Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Observing traffic prioritization in Comcast’s network

ber.gd

Post reply on HN
Print view View original

21–29 of 29 posts

Re: Observing traffic prioritization in Comcast’s network

#21

Post by ars »

bdb wrote: post #20
ars wrote: post #18

Earlier quoted context omitted.

Did you know that when you watch pay per view on your TV using comcast it runs on the exact same lines as your internet? So are you saying comcast can not provide pay per view? They can not prioritize the internet part of their service "network traffic", but as you yourself proved this service doesn't use your internet bandwidth, even if it uses TCP/IP. It runs using its own section of the cable line. It doesn't matt…

Most of your cable service's video is actually delivered over IP, but it is on dedicated RF spectrum, even though it's on the same physical wire. If Comcast wants to deliver video to my STB over separate channels, I don't care what protocol they decide to use. However, if they're delivering video to a generalized computing device in my home, over my home Ethernet network, over the same downstream channels as Internet…

It's only prioritized up till the cable modem, not after so that part doesn't matter (i.e. other providers have equal access to your home network).

And up till the cable modem it is basically using a different channel: They are increasing your allowed bandwidth to make up for the usage. To me that's indistinguishable from a dedicated RF channel.

Re: Observing traffic prioritization in Comcast’s network

#22

Post by bdb »

ars wrote: post #21
bdb wrote: post #20

Earlier quoted context omitted.

Most of your cable service's video is actually delivered over IP, but it is on dedicated RF spectrum, even though it's on the same physical wire. If Comcast wants to deliver video to my STB over separate channels, I don't care what protocol they decide to use. However, if they're delivering video to a generalized computing device in my home, over my home Ethernet network, over the same downstream channels as Internet…

It's only prioritized up till the cable modem, not after so that part doesn't matter (i.e. other providers have equal access to your home network). And up till the cable modem it is basically using a different channel: They are increasing your allowed bandwidth to make up for the usage. To me that's indistinguishable from a dedicated RF channel.

On your last point, we'll have to agree to disagree. Good night! Thanks for the spirited discussion.

Re: Observing traffic prioritization in Comcast’s network

#23

Post by wtvanhest »

ars wrote: post #19
bdb wrote: post #4

Earlier quoted context omitted.

hey Zac. I'm the author of the post. That, or something like it, is Comcast's argument. Which makes no sense. This is a video streaming service, it's prioritized, and it's delivered just like other video streaming services are. Hopefully the data reflects this.

> This is a video streaming service, it's prioritized, and it's delivered just like other video streaming services are. So is pay per view. Rephrase your argument in such a way that pay per view is allowed and this isn't. You can't, because your argument is incorrect. Pay per view is allowed, and so is this.

Maybe you got down voted due to tone, but I thought your comment was really valid.

I hope they legislate a more pure neutrality, but I can see how what you are saying allows them to continue this.

Re: Observing traffic prioritization in Comcast’s network

#25

Post by cllunsford »

WireSpeed wrote: post #24

So, hypothetically speaking, modifying traffic as it flows through a linux firewall in order to change the DSCP field to the values used by Comcast would be useful in avoiding the caps on traffic levels.

This article only looked at downstream traffic, so all the bandwidth management is done before you can touch the packets. On the upstream, Comcast is certainly re-marking (overwriting) the QoS values based on their own priorities.

Re: Observing traffic prioritization in Comcast’s network

#26

Post by Retric »

ars wrote: post #21
bdb wrote: post #20

Earlier quoted context omitted.

Most of your cable service's video is actually delivered over IP, but it is on dedicated RF spectrum, even though it's on the same physical wire. If Comcast wants to deliver video to my STB over separate channels, I don't care what protocol they decide to use. However, if they're delivering video to a generalized computing device in my home, over my home Ethernet network, over the same downstream channels as Internet…

It's only prioritized up till the cable modem, not after so that part doesn't matter (i.e. other providers have equal access to your home network). And up till the cable modem it is basically using a different channel: They are increasing your allowed bandwidth to make up for the usage. To me that's indistinguishable from a dedicated RF channel.

By prioritizing network traffic and running this over their same routers someone down the street using their XBox reduces my bandwidth without being part of any cap's, that's a real problem.

Re: Observing traffic prioritization in Comcast’s network

#27

Post by dodava »

ars wrote: post #19
bdb wrote: post #4

Earlier quoted context omitted.

hey Zac. I'm the author of the post. That, or something like it, is Comcast's argument. Which makes no sense. This is a video streaming service, it's prioritized, and it's delivered just like other video streaming services are. Hopefully the data reflects this.

> This is a video streaming service, it's prioritized, and it's delivered just like other video streaming services are. So is pay per view. Rephrase your argument in such a way that pay per view is allowed and this isn't. You can't, because your argument is incorrect. Pay per view is allowed, and so is this.

You can access Xfinity Streampix through the Xbox app. Streampix is an additional service which cost $4.99 per month and allows access to a library of tv shows and movies which can be viewed by customers on their PCs, Xbox360 and Apple mobile platforms. When Comcast gets around to adding streaming capabilities to their Android app presumably it will available their also.

Unlike Ondemand or pay per view pricing is not based on a per viewing or a predefined rental period. All content decisions are made by Comcast versus Ondemand where the content providers control what content is available and when it is available. For example HBO makes different content available via ondemand each month and the decision regarding which content is available is made by HBO and not Comcast.

It is like and intended to compete with Netflix and other Internet streaming services. It operates differently from traditional pay per view and content streaming services. It also is not like a traditional premium tv channel for which a monthly fee is paid. It is exactly this type of service the agreement was designed to prevent favorable treatment of versus the same type of service provided by someone besides Comcast.

Re: Observing traffic prioritization in Comcast’s network

#28

Post by Cyndre »

The important part to this article isn't that they are doing this. Its that they are back tracking on their own statements of why the caps were needed in the first place.

If you remember when they were arguing for the caps the main reason was the cost to deliver to the last mile. This clearly shows that is not the case as they have given all of their customers additional bandwidth above and beyond their stated plans.

Kind of makes the reason for caps in the first place null and void.

Re: Observing traffic prioritization in Comcast’s network

#29

Post by WireSpeed »

cllunsford wrote: post #25
WireSpeed wrote: post #24

So, hypothetically speaking, modifying traffic as it flows through a linux firewall in order to change the DSCP field to the values used by Comcast would be useful in avoiding the caps on traffic levels.

This article only looked at downstream traffic, so all the bandwidth management is done before you can touch the packets. On the upstream, Comcast is certainly re-marking (overwriting) the QoS values based on their own priorities.

Ohh netflix!! Think we have the solution for your problems....

Didn't mention what side of the traffic you do this on :)

Post reply on HN