Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.txt ENDS 27 Jan 2006
Mark Allman <mallman@icir.org> Fri, 20 January 2006 20:17 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F02hh-0000VM-Uo; Fri, 20 Jan 2006 15:17:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F02hg-0000VG-Hd for tcpm@megatron.ietf.org; Fri, 20 Jan 2006 15:17:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16096 for <tcpm@ietf.org>; Fri, 20 Jan 2006 15:16:21 -0500 (EST)
Received: from wyvern.icir.org ([192.150.187.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F02qT-0001UA-7J for tcpm@ietf.org; Fri, 20 Jan 2006 15:26:54 -0500
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k0KKHht0055074; Fri, 20 Jan 2006 12:17:43 -0800 (PST) (envelope-from mallman@guns.icir.org)
Received: from guns.icir.org (localhost [127.0.0.1]) by guns.icir.org (Postfix) with ESMTP id 2F15777B063; Fri, 20 Jan 2006 15:17:41 -0500 (EST)
To: Lars Eggert <lars.eggert@netlab.nec.de>
From: Mark Allman <mallman@icir.org>
Subject: Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.txt ENDS 27 Jan 2006
In-Reply-To: <EF0728DF-6318-4937-AB48-49BE1381FA7A@netlab.nec.de>
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Just the Way You Are
MIME-Version: 1.0
Date: Fri, 20 Jan 2006 15:17:41 -0500
Message-Id: <20060120201741.2F15777B063@guns.icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: tcpm@ietf.org, Ted Faber <faber@isi.edu>
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1814389525=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org
Lars- Thanks for the comments. I'll fix up the nits, thanks! > Given that the text repeatedly states that the impact of this on the > general Internet is not really known, I assume this is going for the > "experimental in the sense that we want to experiment with it"-flavor > of Experimental? Yes. In fact, the really experimental part of it to me is that using Aggressive Limited Transmit delays the congestion response by an RTT. (To a lesser degree even the Careful variant of Limited Transmit removes the standard idle period between detecting "congestion" and resuming transmission. But, this seems sort of minor to me.) > If so, stating prominently in the abstract and maybe introduction that > this is not ready for production use may be a good idea. Good call. I'll add a note. > One question regarding fairness: I am confused about what you're reading here. I.e., the draft has no figures, the quote below isn't from the draft and I don't think we even discuss fairness in the i-d. > If there's a DCR flow and a non-DCR flow sharing a path that reorders > packets a bit, wouldn't the reordering tolerance of the DCR flow cause > it to steal bandwidth from the non-DCR flow? This is not clear to me. In fact, it's not clear to me exactly how fairness comes into this. If there were 2 flows over some path and no reordering then we'd expect them to see about the same performance (about half the bandwidth). Now, if there was reordering and neither did NCR then they would each get less than half the bandwidth -- say they each got 1/4 the bandwidth, just to put some numbers on things. So, now the reordering is causing a 50% slowdown in the flows and less than full utilization. Now, if one of the flows were to use NCR and it were to get more than 1/4 the bandwidth that would seem fine to me. And, in fact, the NCR flow could get up to 3/4 of the capacity and I wouldn't think that was unfair at all --- even though the rates are quite different. I.e., the NCR flow is using what is available. Now, if the NCR flow ended up with 7/8 of the capacity and drove the non-NCR flow to 1/8 of the capacity ... well, then there is a question. In some sense, the NCR flow is stealing from the non-NCR flow, for sure. Will this happen? I am not sure. Is there a way to minimize it? I don't know. Is this a natural part of trying to make progress and an incentive for stacks to combat reordering? Perhaps. This could all be part of the experiment. > The paper says "it is to be noted that the reason for TCP-DCR > realizing better throughputs (when packets are reordered) is not due > to unfairness, but due to correctly recovering from the reordering > events." Maybe I'm dense, but I don't see the experimental data to > back this up. Is the throughput for SACK shown in Figure 4 identical > when competing only against other SACK flows? Is the dynamic behavior > roughly the same? Where is this from? Thanks again! allman
_______________________________________________ tcpm mailing list tcpm@ietf.org https://www1.ietf.org/mailman/listinfo/tcpm
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Lars Eggert
- [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.txt E… Ted Faber
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Mark Allman
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Lars Eggert
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Jakob Heitz
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Jeremy Harris
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Mark Allman
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Mark Allman
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Mark Allman
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Wesley Eddy
- Re: [tcpm] WGLC: NCR draft-ietf-tcpm-tcp-dcr-06.t… Ted Faber