Global Crossing has been using QoS effectively for years. We use it in two ways--first, two allow customers to prioritize their own traffic; second, to prioritize our backbone traffic, which carries voice, video, IP-VPN, and public Internet as separate logical overlays over the same physical core. The QoS in the second case doesn't come into play often, because we try to make sure there is always sufficient bandwidth. But fiber cuts and denial of service attacks occur, and when they do, we would rather drop packets from public Internet traffic than voice calls.
Tim
· 3 years ago
Does that technology also allow QoS for particular protocols/TCP streams within the public Internet traffic? And is it something that could be feasibly scaled to the Internet as a whole?
lippard
· 3 years ago
We don't do QoS within public Internet traffic--all public Internet traffic is classified as best effort, and there are no standards for inter-provider QoS (though we do map customer classes of service into our own, and maintain their markings across our network and across any partner networks that we use to reach locations where we don't have our own facilities, such as China and India).
Richard Bennett
· 3 years ago
QoS isn't a solution to persistent bandwidth scarcity, it's a solution to the effects that bursty traffic (such as file downloads) have on streams with modest bandwidth requirements but tight jitter requirements. And bandwidth isn't a solution to jitter, in many cases it makes it worse by dumping more traffic into the next segment. All you accomplish with over-provisioning is a relocation of the bottlenecks, and only that temporarily.
The Internet is more and more a mixed-use network, and that means QoS is increasingly important.
All Comments
The Internet is more and more a mixed-use network, and that means QoS is increasingly important.