Re:YouTube's road to HTTPS
by dublinben on Monday August 01, 2016 @02:50PM
(#12204897)
The more modern implementation of this (I'm looking at you, T-Mobile) is just to throttle all connections to content providers. They rely on the content providers' own adaptive streaming technology to deliver the appropriate 480p video when presented with a constrained connection.
[ Parent
| on HN ]
> The more modern implementation of this (I'm looking at you, T-Mobile) is just to throttle all connections to content providers.
If YouTube can't handle traffic shaping, Youtube is broken.
If your ISP applies artificial traffic shaping, your ISP is broken.
What's "artificial" shaping?
The average consumer ISP has an over subscription ratio of 70-to-1.
Unless you want to pay 70x as much for your "100mbit" connection, there are going to be times when packets get dropped.
Isn't it better to drop packets fairly among subscribers? No shaping would result in whoever is using the most dominating everyone else.
This basic principle is still neutral; you don't have to shape based on destination / content provider.
I should be able to turn it off, but I like that tmo throttles my video. I only get 2.5 gb, I don't need 1080p.
You can turn it off, but it removes the zero rating. Up to you either way.
I'm on the light package so I don't even get the zero rating.
What the ISP is doing isn't any different than what any private network could do. If YouTube can not handle that, Youtube is not playing well with standard network practices and is broken at a technical level.
Your ISP doing traffic shaping is a question of if they should, not a technical question.
In this case, that's what "broken" means. Not that there is something technically wrong, but that they are doing things that they shouldn't.
That shaping should not be broken by HTTPS. The only things that would be affected by HTTPS is carriers munging the bits.
Re:YouTube's road to HTTPS
by ianlevesque on Monday August 01, 2016 @03:20PM
(#12205132)
Not ideal but that's a lot less intrusive.