There were no technical issues found. If anyone has any other issues such as
scheduling, or identifying data-limited intervals - then it would be good to
know.
Some NITs are listed below:
-----------------------------------
General changes:
Isn't -> is not
Don't -> do not
---------------------------------------
1. Introduction
TFRC is designed to be reasonably fair when competing for bandwidth
with TCP flows, where a flow is "reasonably fair" if its sending
rate is generally within a factor of two of the sending rate of a
TCP flow under the same conditions [ref?].
-----
3.1 TCP Throughput Equation
" Ideally we'd prefer a throughput equation based on
SACK TCP,"
-> Ideally we would prefer..
------
4. Data Sender Protocol
"If the sender does
not receive a feedback report for four round trip times, and the
sender has not been idle over that entire period, then it cuts its
sending rate in half."
It is to be noted that the sender cuts the rate into half during idle
periods too..so its better to avoid discrepancy..
-> If the sender does
not receive a feedback report for four round trip times then it cuts its
sending rate in half.
----
Section 4.3
"However, any interval that covers the
transmission of at least two data packets is not a data-limited
interval for this sender."
This is not clear.
`data-limited interval' -> 'data-limited'
``if'' -> "if"
-----
C.1
"..an idle period,
the first feedback packet receives reports a receive rate of one
packet per round-trip time, "
->
..an idle period,
the first feedback packet received reports a receive rate of one
packet per round-trip time,
"Standard TFRC after long data-limited periods: [RFC3448] does not
distinguish between data-limited and not-data-limited periods."
->
Standard TFRC after long data-limited periods: [RFC3448] does not
distinguish between data-limited and non-data-limited periods.
"For Revised TFRC, this
document distinguishes between data-limited and not-data-limited
periods."
-> For Revised TFRC, this
document distinguishes between data-limited and non-data-limited
periods.
-------
C.3
"For a moderate data-limited
period, Standard TCP would be limited by X_recv from the most recent
feedback packet. "
->
For a moderate data-limited
period, Standard TFRC would be limited by X_recv from the most recent
feedback packet.
------
C.4
" ...idle and data-limited periods, or with idle or data-limited periods
during Slow-Start,"
-> idle and data-limited periods, or with idle or data-limited periods
during Slow-Start.
------
C.5
"Work in progress such as Faster Restart [KFS07] can
also decrease a application's incentive to pad its sending rate,"
->
Work in progress such as Faster Restart [KFS07] can
also decrease an application's incentive to pad its sending rate,
"Revised TFRC's response to data-limited periods is less
conservative that those of Congestion Window Validation (and
Standard TFRC's response to data-limited periods was considerably
more conservative that those of Congestion Window Validation)."
->
Revised TFRC's response to data-limited periods is less
conservative than those of Congestion Window Validation (and
Standard TFRC's response to data-limited periods was considerably
more conservative than those of Congestion Window Validation).
Arjuna
-------------------------------
Dr.Arjuna Sathiaseelan
Electronics Research Group
University of Aberdeen
Aberdeen AB24 3UE
Email: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
Web: <http://www.erg.abdn.ac.uk/users/arjuna>
www.erg.abdn.ac.uk/users/arjuna
Phone : +44-1224-272780
Fax : +44-1224-272497
