Could someone elaborate on the "smallish technical errors" in Professor Fulton's paper?
MnZ
· 3 years ago
If VoIP and streaming video need a smarter network, companies can build that smarter network. They just cannot charge extra for delivery of those specific services.
Would free QoS even work if ISPs had to give them away for free? Businesses and users will lazily or greedily overstate the QoS that they need for their applications. If an ISP refuses their QoS requests, the ISP would probably be sued or prosecuted for a "violation of net neutrality." Futhermore, users would have little incentive to not overuse QoS connections. For example, they might leave their HDTVs on or leave their VVoIP connections open.
max
· 3 years ago
Could someone elaborate on the smallish technical errors in Professor Fultons paper?
One of them revolves around the difference between TCP and UDP.
In this example, he describes the behavior of TCP:
This is a very indirect way of coping with congestiondrop packets, wait for endpoint computers to notice the missing packets, and respond by slowing downbut it works pretty well.
But doesn't realize that not all applications use TCP, some use UDP where there are no backoff, sliding windows or other flow control mechanisms. Unfortunately, VOIP is an application that uses UDP primarily ;-)
Also take into consideration that the network community has realized for awhile the TCP is not very efficient and has many problems of it's own. It was built for a time when the Internet was much less reliable, and has been reworked frequently to deal with it's performance related shortcomings. It's sort of the X.25 of the IP world because of that.
He also seems at various times to confuse two different types of QoS. There are guaranteed services, and then there are priority/ differentiated services. He clarifies this somewhat by saying he's only talking about guaranteed services as being QoS, fair enough point.
But in the networking world, you can user either or both together to get the same practical effects, depending on the situation. There are variations in the QoS world that are more complicated than just switching it on or off.
Plus, the Internet is growing. Right now, Consumer grade VOIP is mostly a toy. People expect better reliablity out of their land lines than their Cellphones, and a Pizza Joint that relies heavily on delivery orders will require that same level of wireline reliability.
Ed Felten
· 3 years ago
The "error" you point to is just a decision on my part to simplify the explanation for nontechnical readers. If you want to write a short paper that nontechies will be willing and able to understand, you have to leave some things out. The congestion control discussion is about the cooperative nature of TCP backoff. For that purpose it's enough to know that TCP works that way, and there is lots of TCP traffic.
Richard Bennett
· 3 years ago
That's always a challenge, of course. Given that Snowe-Dorgan bans for-fee QoS, I would emphasize why that's a technically infeasible approach, Ed.
George Ou
· 3 years ago
"Would free QoS even work if ISPs had to give them away for free? Businesses and users will lazily or greedily overstate the QoS that they need for their applications. If an ISP refuses their QoS requests, the ISP would probably be sued or prosecuted for a violation of net neutrality. Furthermore, users would have little incentive to not overuse QoS connections. For example, they might leave their HDTVs on or leave their VVoIP connections open."
MnZ, you hit the nail on the head!
Oh but we can't be doing "deep packet inspection" now can we. Remember if we have to look at the source or destination and the routers interact (collude with BGP in any way), we can't call it the "Internet" according to DPSProject.
All Comments
Would free QoS even work if ISPs had to give them away for free? Businesses and users will lazily or greedily overstate the QoS that they need for their applications. If an ISP refuses their QoS requests, the ISP would probably be sued or prosecuted for a "violation of net neutrality." Futhermore, users would have little incentive to not overuse QoS connections. For example, they might leave their HDTVs on or leave their VVoIP connections open.
One of them revolves around the difference between TCP and UDP.
In this example, he describes the behavior of TCP:
But doesn't realize that not all applications use TCP, some use UDP where there are no backoff, sliding windows or other flow control mechanisms. Unfortunately, VOIP is an application that uses UDP primarily ;-)
Also take into consideration that the network community has realized for awhile the TCP is not very efficient and has many problems of it's own. It was built for a time when the Internet was much less reliable, and has been reworked frequently to deal with it's performance related shortcomings. It's sort of the X.25 of the IP world because of that.
He also seems at various times to confuse two different types of QoS. There are guaranteed services, and then there are priority/ differentiated services. He clarifies this somewhat by saying he's only talking about guaranteed services as being QoS, fair enough point.
But in the networking world, you can user either or both together to get the same practical effects, depending on the situation. There are variations in the QoS world that are more complicated than just switching it on or off.
Plus, the Internet is growing. Right now, Consumer grade VOIP is mostly a toy. People expect better reliablity out of their land lines than their Cellphones, and a Pizza Joint that relies heavily on delivery orders will require that same level of wireline reliability.
MnZ, you hit the nail on the head!
Oh but we can't be doing "deep packet inspection" now can we. Remember if we have to look at the source or destination and the routers interact (collude with BGP in any way), we can't call it the "Internet" according to DPSProject.