3 ms·
The problem occurs if I, an entrepreneur, want to solve the hospital's problem for them, and sell them a single connection that meets their application-specific
by gojomo 12y ago
The problem occurs if I, an entrepreneur, want to solve the hospital's problem for them, and sell them a single connection that meets their application-specific needs. I'd set it up so that I could always meet their demands, and a sensible way to do that would be with app-specific routing rules. Also, to help make that peak, application-specific offering possible, it would likely help for me to sell other nearby connections that have much softer throughput/lag requirements – users who don't mind if the hospital's needs occasionally stall their YouTube/Netflix, because they're getting such a good deal most of the time on most of what they use.
NN regulations make such economically-sensible, mutually-beneficial business arrangements illegal. Everyone's got to buy the mandated, "neutral" service tiers – rather than other cheaper mixed-traffic-treatment formulas that could meet their needs.
- AnthonyMouse 12y agoI don't understand why you think the rules need to be application-specific or why you think the alternative would be more expensive. If you want a high-bandwidth low-latency guaranteed-reliable fully-provisioned circuit then it's going to be expensive. Providing the same guarantees but only for a single application doesn't reduce the cost at all. If the customer is paying you to guarantee the delivery of packets, it doesn't cost you anything more if the customer then decides they're going to be YouTube packets rather than telemedicine packets. None of the things that cause that level of service to be expensive are application-specific so there is no savings to be had by treating applications differently.