Re: [re-ECN] Complete draft Charter for proposed CONEX WG

John Leslie <john@jlc.net> Wed, 09 December 2009 11:30 UTC

Return-Path: <john@jlc.net>
X-Original-To: re-ecn@core3.amsl.com
Delivered-To: re-ecn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00D2A3A69C7 for <re-ecn@core3.amsl.com>; Wed, 9 Dec 2009 03:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.196
X-Spam-Level:
X-Spam-Status: No, score=-6.196 tagged_above=-999 required=5 tests=[AWL=0.403, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Lb7XQBXVok5g for <re-ecn@core3.amsl.com>; Wed, 9 Dec 2009 03:30:19 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by core3.amsl.com (Postfix) with ESMTP id E969C3A69C1 for <re-ecn@ietf.org>; Wed, 9 Dec 2009 03:30:18 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id DBB9A33C84; Wed, 9 Dec 2009 06:30:05 -0500 (EST)
Date: Wed, 9 Dec 2009 06:30:05 -0500
From: John Leslie <john@jlc.net>
To: toby.moncaster@bt.com
Message-ID: <20091209113005.GA24477@verdi>
References: <4A916DBC72536E419A0BD955EDECEDEC06363B66@E03MVB1-UKBR.domain1.systemhost.net> <AEDCAF87EEC94F49BA92EBDD49854CC70E4ED0CC@E03MVZ1-UKDY.domain1.systemhost.net> <AEDCAF87EEC94F49BA92EBDD49854CC70E4ED147@E03MVZ1-UKDY.domain1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AEDCAF87EEC94F49BA92EBDD49854CC70E4ED147@E03MVZ1-UKDY.domain1.systemhost.net>
User-Agent: Mutt/1.4.1i
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Complete draft Charter for proposed CONEX WG
X-BeenThere: re-ecn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: re-inserted explicit congestion notification <re-ecn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/re-ecn>
List-Post: <mailto:re-ecn@ietf.org>
List-Help: <mailto:re-ecn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Dec 2009 11:30:20 -0000

toby.moncaster@bt.com <toby.moncaster@bt.com> wrote:
> 
>> allow senders to inform the network of the level of congestion they
>> expect their packets to encounter. This information is currently only
>> visible at the transport layer. 
> 
> Although I agree with Mirja's comment, an argument that could be made to
> say the information is visible in the network if you use DPI equipment...

   That is an argument we need to rebut: Deep Packet Inspection is not
sufficient to show congestion management -- merely to infer reasonable
guesses from artifacts of congestion managment, which is not good
enough to act upon.

> However I think highlighting that only the end-systems are DESIGNED to
> see the info is a good thing...

   Even this is subtly wrong. There are many different congestion-control
schemes in current use. Most, but not all, are designed to infer packet
loss and interpret that as congestion. We are not talking about getting
every router along the path to have the same view of packet loss: we
are talking about getting every router along the way to have the same
view of expected congestion _whether_or_not_ any packets are ever
dropped.

> > With the output of CONEX, it will be
> > possible to provide sufficient information in each IP datagram so that
> > any node in the network can see the expected rest-of-path congestion.
> 
> I think I would prefer to say "The main output of CONEX will be a
> protocol that allows each IP datagram to carry sufficient information to
> allow any node in the network to see the whole path congestion."

   This is a good issue to raise.

   But I don't agree with Toby: any congestion _earlier_ in the path is
of no concern to a router -- there is nothing reasonable to _do_ about
it. Even if we don't actually design algorithms about what to do about
rest-of-path congestion, that remains the concern to consider. (Said
differently, there's no point in punishing congestion _after_ the last
bottleneck in the path.)

> I make the subtle distinction between rest of path and whole path so
> that we leave the door open for Matt Mathis's mark on drop suggestion...

   I'm happy to leave that door open, but I don't think Toby's suggestion
is necessary to do so.

--
John Leslie <john@jlc.net>