From a legal standpoint that makes sense, but from a technical standpoint I just tunnel whatever I want over $SECURE_PROTOCOL and at that point all they've done is specified data latency/speed tiers.
Unless they're specifically looking at discriminating based on protocol, I don't see why they just don't talk about realtime vs. streaming vs. download data priority tiers, which seems a lot simpler from an implementation standpoint, and a lot easier to stomach from a net neutrality standpoint. Maybe that's all they're talking about. But the way it's phrased it sounds very dependent on protocol, which I would say is very non-neutral, because it's only possible to implement if you have a whitelist of protocols, and it's pretty much impossible for the established players to fairly arbitrate which protocols are which. What is streaming video over http? https? What if I've got a VOIP app running over https? Web-based email? Pigeonholing a protocol into a data priority tier just doesn't make sense.
Unless you're deliberately trying to lock out innovative protocols.
Unless they're specifically looking at discriminating based on protocol, I don't see why they just don't talk about realtime vs. streaming vs. download data priority tiers, which seems a lot simpler from an implementation standpoint, and a lot easier to stomach from a net neutrality standpoint. Maybe that's all they're talking about. But the way it's phrased it sounds very dependent on protocol, which I would say is very non-neutral, because it's only possible to implement if you have a whitelist of protocols, and it's pretty much impossible for the established players to fairly arbitrate which protocols are which. What is streaming video over http? https? What if I've got a VOIP app running over https? Web-based email? Pigeonholing a protocol into a data priority tier just doesn't make sense.
Unless you're deliberately trying to lock out innovative protocols.