More Design Issues
A range of service assurance should be provided
A higher assurance service will cost more
Statistically provisioned service allocation profiles do not describe a strict guarantee
Different users should be allowed to have different expectations
It is not necessary to separate out each individual flow, e.g., use a couple of queues for different levels of assurance. Within each queue, provide preferential treatment using “in” and “out” tags
Statistical assurance is a matter of provisioning
Receiver-controlled bandwidth allocation relies on TCP-ECN
If receiver’s profile is exceeded, packets with ECN bit set are left unchanged or dropped to notify sender to slow down
Problematic in presence of malicious users