WG Internet Draft: draft-ietf-DCCP-tfrc-voip -05.txt
TCP Friendly Rate Control (TFRC):
the Small-Packet (SP) Variant
Dear DCCP WG,
The Chairs would like to say sorry for the long delay in processing the
I-D below, following its WGLC. We now intend to progress this.
While preparing the write-up of this I-D (that will request publication
as an Experimental RFC) a number of issues have been found that would
best be corrected (we will send these to the list). The authors have
therefore been requested to make a new revision of the I-D.
The current I-D has expired, but is available at:
http://tools.ietf.org/wg/dccp/draft-ietf-dccp-tfrc-voip/draft-ietf-dccp-tfrc-voip-05.txt
To enable this new I-D to be as correct as possible, We wish to allow
others to also ask for clarifications, and raise any issues they have.
This message therfore starts a new WGLC for this I-D.
This WGLC will close at midnight on:
9th October 2006.
Best wishes,
Gorry & Tom
(DCCP WG Chairs)
----
Summary
This document is a chartered item of the DCCP WG.
It proposes a mechanism for further experimentation, but
not for widespread deployment at this time in the global Internet.
TCP-Friendly Rate Control (TFRC) is a congestion control mechanism
for unicast flows operating in a best-effort Internet environment
[RFC 3448]. TFRC was intended for applications that use a fixed
packet size, and was designed to be reasonably fair when competing
for bandwidth with TCP connections using the same packet size. This
document proposes TFRC-SP, a Small-Packet (SP) variant of TFRC, that
is designed for applications that send small packets. The design
goal for TFRC-SP is to achieve the same bandwidth in bps as a TCP
flow using packets of up to 1500 bytes. TFRC-SP enforces a Min
Interval of 10 ms between data packets, to prevent a single flow
from sending small packets arbitrarily frequently.
Flows using TFRC-SP compete reasonably fairly with large-packet TCP
and TFRC flows in environments where large-packet flows and small-
packet flows experience similar packet drop rates. However, in
environments where small-packet flows experience lower packet drop
rates than large-packet flows (e.g., with Drop-Tail queues in units
of bytes), TFRC-SP can receive considerably more than its share of
the bandwidth.
