3 ms·
Your #1 is about QoS, not net neutrality. You want to prioritize the remote surgery protocol above all others...net neutrality allows that. If, instead of proto
by curun1r 9y ago
Your #1 is about QoS, not net neutrality. You want to prioritize the remote surgery protocol above all others...net neutrality allows that. If, instead of protocol, you prioritize by source/destination, how can you ensure that the remote surgery protocol isn't disrupted by the transmission of high-resolution X-ray scans between the two hospitals? We already allow (and even encourage) ISPs to prioritize real-time protocols above those that aren't. VoIP is the oft-cited example because late packets are useless packets. Remote surgery can be handled the same way.
Would you really want your hospital to prioritize remote surgery from one hospital over another? When patients are choosing their remote surgery doctor, do you want them to have to worry about finding one at the top-priority hospital instead of one at a lower priority? What if the surgery is the result of an emergency and the doctor is on vacation? By using protocol as the prioritization instead of source/destination, that doctor can find a local hospital from which to perform the operation and doesn't have to worry about having a lower priority during the surgery.
- JoshTriplett 9y ago> You want to prioritize the remote surgery protocol above all others...net neutrality allows that. If, instead of protocol, you prioritize by source/destination Yes, I absolutely want the ability to prioritize remote-control packets between the hospital and the doctor actually performing the surgery, not any random other packets that happen to look similar. Such a priority channel could be set up on the fly, such as via software-defined networking.