We study the effects of tagging, per-VC buffer allocation, and per-VC scheduling on providing GFR to TCP/IP traffic. We conclude that per-VC scheduling is necessary to provide GFR guarantees to TCP traffic. Per-VC scheduling alone is sufficient to provide minimum rate guarantees to the CLP0+1 stream. If the source end systems perform tagging (but not the network), then per-VC scheduling and per-VC buffer allocation are both required to provide GFR guarantees to the CLP0 stream.

Contribution in Postscript (436,710 Bytes) | text *without* figures (28,220 bytes)

Presentation slides in Adobe Acrobat 3.0 Format (89,457 bytes)