Re:FCC weakens net neutrality rule in a prelude to larger ro...
by wtallis on Friday February 24, 2017 @05:35PM
(#13728572)
> As long as that applied to all VoIP services and apps equally, though I'm not sure how you would be able to tell.
The only fair way to do this is to use port numbers and protocols and endpoint IP addresses only for the purpose of telling which packets belong to which traffic flow or customer. For deciding which flows get priority, you should look only at the actual pattern of traffic: sparse low-rate flows should be assumed to be interactive, in the same manner that your operating system's CPU scheduler assumes that processes with intermittent load are more latency-sensitive than long-running sustained loads. To see how this kind of packet scheduling works in the real world, look at the fq_codel and cake queue disciplines in Linux. The former has become the default for many Linux distributions and is used by some of the more modern commercial wireless routers.
This will have the side effect that my ssh session will get the same preferential treatment as your VoIP, unless I'm using it to tunnel rsync.
The only fair way to do this is to use port numbers and protocols and endpoint IP addresses only for the purpose of telling which packets belong to which traffic flow or customer. For deciding which flows get priority, you should look only at the actual pattern of traffic: sparse low-rate flows should be assumed to be interactive, in the same manner that your operating system's CPU scheduler assumes that processes with intermittent load are more latency-sensitive than long-running sustained loads. To see how this kind of packet scheduling works in the real world, look at the fq_codel and cake queue disciplines in Linux. The former has become the default for many Linux distributions and is used by some of the more modern commercial wireless routers.
This will have the side effect that my ssh session will get the same preferential treatment as your VoIP, unless I'm using it to tunnel rsync.