-
Website
http://techliberation.com/ -
Original page
http://techliberation.com/2007/03/30/network-neutrality-recommendations-needed/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
MikeRT
184 comments · 6 points
-
eee_eff
800 comments · 8 points
-
mwendy
73 comments · 2 points
-
Ryan Radia
176 comments · 5 points
-
Richard Bennett
612 comments · 1 points
-
-
Popular Threads
-
The Ugliness of Privacy Notices
3 days ago · 4 comments
-
Google’s Privacy Dashboard: Another Major Step Forward in User Empowerment & Transparency
2 days ago · 2 comments
-
Open Source is Not the Enemy
4 days ago · 3 comments
-
Broadband as a Human Right (and a short list of other things I am entitled to on your dime)
3 weeks ago · 18 comments
-
“Internet Freedom”: How Statists Corrupt Our Language
1 week ago · 7 comments
-
The Ugliness of Privacy Notices
If you're looking at packet shaping and prioritization as a handle on the smart network/dumb network debate, you might also consider a third technique which proved effective in practice: have your company connect to multiple service providers and steer outbound traffic down one link or the other. It takes advantage of the fact that traffic tends to be asymmetric, with most of outbound from the company. (Picture someone like YouTube using this stuff.) Routescience used to have some stuff called Adaptive Network Software that did that. (You can find a quick overview here, but it helps if you speak NANOG :-) . They've since been acquired by Avaya but might be willing to furnish whitepapers. I think Sockeye had something similar, too. A good general lesson to draw is that getting good performance across a wide range of applications without embedding intelligence in the network can be a difficult technical challenge.
For other references, I assume you've already gone trundling through the cites in Rob Frieden's Network Neutrality or Bias paper?
Also, anything you can find on 802.11e should be helpful. This amendment to the 802.11 standard incorporates priority-based QoS as well as parameterized QoS, and it's very widely used.
On the economics, your best source is Chris Yoo.
It's a "dumb QoS for dump pipes" method that preserves end-to-end.
Preservation of end-to-end, if it's important, isn't really affected by a QoS menu, however. End user packet streams choose from several transport options rather than being forced into one class all the time.