Re: [Tsvwg] RE: HEADS UP: consensus call on draft-floyd-tsvwg-cc-alt
Sally Floyd <sallyfloyd@mac.com> Mon, 26 March 2007 01:22 UTC
Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVdv4-0003yY-Qp; Sun, 25 Mar 2007 21:22:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVdv3-0003yQ-K1 for tsvwg@ietf.org; Sun, 25 Mar 2007 21:22:45 -0400
Received: from smtpout.mac.com ([17.250.248.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVduy-0007Ms-7Y for tsvwg@ietf.org; Sun, 25 Mar 2007 21:22:45 -0400
Received: from mac.com (smtpin04-en2 [10.13.10.149]) by smtpout.mac.com (Xserve/smtpout03/MantshX 4.0) with ESMTP id l2Q1MNPm003098; Sun, 25 Mar 2007 18:22:23 -0700 (PDT)
Received: from [192.168.1.64] (adsl-70-132-15-34.dsl.snfc21.sbcglobal.net [70.132.15.34]) (authenticated bits=0) by mac.com (Xserve/smtpin04/MantshX 4.0) with ESMTP id l2Q1MKF6015767; Sun, 25 Mar 2007 18:22:21 -0700 (PDT)
In-Reply-To: <45E5F9C4.8FFE4F5@earthlink.net>
References: <200702240655.l1O6tkrI026247@erg.abdn.ac.uk> <10f6e4b46860e83f30ae4aed8bfe3552@mac.com> <45E5F9C4.8FFE4F5@earthlink.net>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <76e52cd8a1064e67bd851497be2344d5@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Subject: Re: [Tsvwg] RE: HEADS UP: consensus call on draft-floyd-tsvwg-cc-alt
Date: Sun, 25 Mar 2007 18:22:19 -0700
To: Erblichs <erblichs@earthlink.net>
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: gorry@erg.abdn.ac.uk, Arjuna Sathiaseelan <arjuna@erg.abdn.ac.uk>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org
Mitchell - My apologies for the delay in replying. > My two cents.. > > One cent > --------- > Is TCP fair? With two flows that start at the same time, with > at least 1 hop in common, doesn't a lower RTT flow, absorb > a greater amount of bandwidth? Of course it does.. > > Shouldn't TCP allow both, in this example, to achieve a > stasis window where both flows are using approximately > 50% of the available bandwidth on this common hop? > > There are more examples of where TCP isn't fair. However, > should TCP have a priority goal of fairness? If one flow > sees congestion before another and does a MD, where the > other flow keeps doing AI, then this does not violate the > TCP protocol. > > Maybe I missed it, but should the doc discuss the effects > of tail-drop versus RED on multiple flows? > > Thus, is it fair to measure different TCP implementations > in a heterogenous environment based on some set of criteria > of fairness?? Shouldn't we EXPECT some level of UNFAIRNESS > in heterogeneous environments (multiple different systems > using diifferent TCP implementations)? > > Two cent > -------- > Maybe I missed it, but should the doc discuss the effects > of tail-drop versus RED on TCP flows? Which one is > "more fair"? Does RED reduce congestion as it reduces > the effective size of the input buffers, which allows > for bursty traffic. Isn't the TCP protocol bursty in > nature due to the fact that no interpacket gap is > MANDATORY or even suggested between segments on > transmission? As I said in my earlier email: >> draft-floyd-tsvwg-cc-alt doesn't attempt to give detailed >> *requirements* >> for fairness, it just discusses fairness (flow-rate fairness) as one >> of the >> issues to be considered in evaluating new congestion control >> mechanisms. >> >> Detailed metrics on fairness, issues about fairness and packet size, >> etc., >> are discussed in draft-irtf-tmrg-metrics-07, Metrics for the >> Evaluation of >> Congestion Control Mechanisms. That draft, and an updated version >> in progress that has not yet been submitted, are available from >> "http://www.icir.org/floyd/papers.html". That seems to me the right document for a discussion of all of the intricacies of fairness as a metric. That document discusses issues about fairness and RTT, and a number of other issues. - Sally http://www.icir.org/floyd/
- [Tsvwg] HEADS UP: consensus call on draft-floyd-t… Lars Eggert
- Re: [Tsvwg] HEADS UP: consensus call on draft-flo… Bob Briscoe
- Re: [Tsvwg] HEADS UP: consensus call on draft-flo… Lars Eggert
- Re: [Tsvwg] HEADS UP: consensus call on draft-flo… Sally Floyd
- Re: [Tsvwg] HEADS UP: consensus call on draft-flo… Bob Briscoe
- [Tsvwg] RE: HEADS UP: consensus call on draft-flo… Arjuna Sathiaseelan
- Re: [Tsvwg] RE: HEADS UP: consensus call on draft… Bob Briscoe
- Re: [Tsvwg] RE: HEADS UP: consensus call on draft… Sally Floyd
- Re: [Tsvwg] RE: HEADS UP: consensus call on draft… Erblichs
- Re: [Tsvwg] HEADS UP: consensus call on draft-flo… Bob Briscoe
- Re: [Tsvwg] HEADS UP: consensus call ondraft-floy… Erblichs
- Re: [Tsvwg] HEADS UP: consensus call on draft-flo… Mark Allman
- Re: [Tsvwg] RE: HEADS UP: consensus call on draft… Sally Floyd