Traffic engineering attempts to improve networks by considering how it can be reallocated across a network.
FLICK: Developing and Running Application-Specific Network Services
This paper describes a system for middleboxes that process application level data -- that is reconstructed TCP flows not packets. The system consists of three parts:
1) A language specific to middleboxes that can quickly express data formats and how to process them but in a "safe" way that allows middleboxes to co-exist on the same physical hardware.
2) An abstraction, the task graph, that breaks middlebox logic into small, parallelisable logical units (tasks) connected by channels through which data flows.
3) A system that allows the compiled code to execute in a performant way.
Home is where the (fast) Internet is: Flat-rate compatible incentives for reducing peak load
Improving content delivery using provider-aided distance information
Time-Dependent Internet Pricing
Good things come to those who (can) wait: or how to handle Delay Tolerant traffic and make peace on the Internet
Balancing by PREFLEX: Congestion Aware Traffic Engineering
This paper considers the problem of balancing traffic across network egresses. It achieves a workable solution using a scalable packet market scheme which couples end-hosts controlling their own connection with an overall controller which can select routes appropriately for each flow.
The flows are balanced to seek paths which minimise loss.
This talk is based around the Transactions on Networking paper. We use 232 traffic traces to establish that for "mid-large" internet link (backbone links or ingress/egress links from reasonable sized institutions) the traffic is well-modelled by a log-normal distribution.
The associated paper is here: