I stopped reading after your analogy to a highway. In a highway, slow users affect everyone and cause congestion.
In a data pipeline, that is not the case.
Most real world analogies for the internet are contrived and do more harm than good. We need to understand this technology is unlike anything we have had before, and its closest cousin is communications. And we have already qualified our communications pipelines as neutral infrastructure.
Please give your position on this matter more thought, without the harmful highway analogy.
You misunderstand my point or you misunderstand QoS.
The capacity of a data pipeline can be significantly increased by QoS. Not its absolute, theoretical maximum, but its ability to achieve high throughput amid disparate traffic types. Ultimately it's all buffers and queues.
> And we have already qualified our communications pipelines as neutral infrastructure
Right, but POTS has a latency requirement. If you keep reading my comment, my point is simply that without making a claim for what the QoS rules should be, advocates of net neutrality are just handwaving and spreading FUD.
You don't understand how latency works at all. If latency to a location is bad, fix it -- that's what you are being paid for.
As for bandwidth allocation, that is an entirely other issue that has nothing to do with latency or congestion. You pay for the bandwidth tier you can afford, as an end-user. And business pay proportionate to the amount of bandwidth they require. This need tends to scale directly with customer load, so this arrangement is sustainable and scalable. ISPs can also profitably scale as they get more premium-tier users.
The issue is that business would now have to pay premiums in order to offer premium services. This further enhances existing monopolies and prohibits fair competition. It also reinforces the idea of, "We will treat you better if you have more money" which is a classist approach that has no basis.
Not to mention the fact that most of our leading ISPs are directly tied to many media platforms, and the ones that aren't wish they were. The drawbacks are so plainly obvious that it's hard not to suspect that anyone who doesn't openly admit a nascent understanding of the issue around "net neutrality" is following a playbook given to them by employers.
> You don't understand how latency works at all. If latency to a location is bad, fix it -- that's what you are being paid for.
Are you serious? There are some cases where latency is a function of a malfunctioning circuit and can be improved, but in general the latency of a circuit for tcp/ip has to do with traffic shaping settings and physical layer technologies/protocols.
I understand how TCP/IP works. Are you saying that latency issues are something that cannot be fixed without creating something analogous to artificial scarcity on content that you stand to profit from?
In a data pipeline, that is not the case.
Most real world analogies for the internet are contrived and do more harm than good. We need to understand this technology is unlike anything we have had before, and its closest cousin is communications. And we have already qualified our communications pipelines as neutral infrastructure.
Please give your position on this matter more thought, without the harmful highway analogy.