Re: WG Review: Low Extra Delay Background Transport (ledbat)
Robert Elz <kre@munnari.OZ.AU> Fri, 31 October 2008 08:47 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67C1A28C25B; Fri, 31 Oct 2008 01:47:37 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC7A03A6BB8; Fri, 31 Oct 2008 01:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level:
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXVF0ij2Q2Di; Fri, 31 Oct 2008 01:47:34 -0700 (PDT)
Received: from jade.coe.psu.ac.th (unknown [202.28.99.196]) by core3.amsl.com (Postfix) with ESMTP id 3320428C10D; Fri, 31 Oct 2008 01:47:03 -0700 (PDT)
Received: from epsilon.noi.kre.to (jade.coe.psu.ac.th [202.28.99.196]) by jade.coe.psu.ac.th with ESMTP id m9V8jcXP010646; Fri, 31 Oct 2008 15:45:43 +0700 (ICT)
Received: from epsilon.noi.kre.to (localhost [127.0.0.1]) by epsilon.noi.kre.to (8.14.2/8.14.2) with ESMTP id m9V8jUd5002849; Fri, 31 Oct 2008 15:45:35 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: iesg@ietf.org
Subject: Re: WG Review: Low Extra Delay Background Transport (ledbat)
In-Reply-To: <20081030220230.7E6493A6906@core3.amsl.com>
References: <20081030220230.7E6493A6906@core3.amsl.com>
Mime-Version: 1.0
Date: Fri, 31 Oct 2008 15:45:30 +0700
Message-ID: <3077.1225442730@epsilon.noi.kre.to>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Date: Thu, 30 Oct 2008 15:02:30 -0700 (PDT) From: IESG Secretary <iesg-secretary@ietf.org> Message-ID: <20081030220230.7E6493A6906@core3.amsl.com> This looks like useful work to do, and to me, the charter mostly looks fine, just one point. The (proposed) charter says ... | * operate well in networks with FIFO queueing with drop-tail | discipline which in itself is OK, but doesn't say anything about links that don't have those characteristics. For different queueing strategies, I doubt there'd be a problem, but I might expect the charter to be explicit that for (what I will call here) intelligent queueing (almost anything other than FIFO that's useful) the resulting protocol from this group will at the very least be easily distinguishable (without necessarily resorting to DiffServ mechanisms) from regular traffic. Of course, is the result is an IP application protocol that is not TCP, that's not going to be an issue, but if it is a different behaviour of TCP stacks for background traffic, it might not be so easy for intermediate routers to be able to separate the background traffic from other traffic. Perhaps more difficult, I'm not sure, would be how well the protocol is to function with random drop, or RED, instead of drop tail. I'd hope it would be "at least as well as drop-tail", but I'm not sure, and the charter doesn't say. kre _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf