Re: [re-ECN] Draft Agenda

Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de> Wed, 07 October 2009 15:27 UTC

Return-Path: <mirja.kuehlewind@ikr.uni-stuttgart.de>
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 5ACAB28C0E7 for <re-ecn@core3.amsl.com>; Wed, 7 Oct 2009 08:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.77
X-Spam-Level:
X-Spam-Status: No, score=-1.77 tagged_above=-999 required=5 tests=[AWL=0.479, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 YClq0m0GQkzD for <re-ecn@core3.amsl.com>; Wed, 7 Oct 2009 08:27:44 -0700 (PDT)
Received: from mailsrv.ikr.uni-stuttgart.de (mailsrv.ikr.uni-stuttgart.de [129.69.170.2]) by core3.amsl.com (Postfix) with ESMTP id 8788C28C172 for <re-ecn@ietf.org>; Wed, 7 Oct 2009 08:27:44 -0700 (PDT)
Received: from netsrv1.ikr.uni-stuttgart.de (netsrv1-c [10.11.12.12]) by mailsrv.ikr.uni-stuttgart.de (Postfix) with ESMTP id 597AC439F5; Wed, 7 Oct 2009 17:29:23 +0200 (CEST)
Received: from localhost (inode21 [10.21.18.11]) by netsrv1.ikr.uni-stuttgart.de (Postfix) with ESMTP id 46017BC07E; Wed, 7 Oct 2009 17:29:23 +0200 (CEST)
From: Mirja Kuehlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
Organization: University of Stuttgart (Germany), IKR
To: re-ecn@ietf.org
Date: Wed, 7 Oct 2009 17:29:42 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20090731.1005176)
References: <200909281832.n8SIWijX024923@bagheera.jungle.bt.co.uk> <4ACBC12A.3050507@thinkingcat.com> <AEDCAF87EEC94F49BA92EBDD49854CC70D5DCFEA@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <AEDCAF87EEC94F49BA92EBDD49854CC70D5DCFEA@E03MVZ1-UKDY.domain1.systemhost.net>
X-KMail-QuotePrefix: >
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200910071729.42797.mirja.kuehlewind@ikr.uni-stuttgart.de>
Subject: Re: [re-ECN] Draft Agenda
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, 07 Oct 2009 15:27:45 -0000

Hi,

some questions regarding the demonstration:

> >  > 10 mins     demonstration
> >
> > ?
>
> We are trying to put together a very simple demo of re-ECN to show that
> it is possible to reveal congestion both upstream and downstream at any
> point in the network. The idea was not to go into any technical detail
> (after all the BoF isn't here to rubberstamp a solution, but it will
> help people to see that a solution is possible and actually works...).

I not sure how you gone make a demo (of re-ECN) without any technical details 
of re-ECN. The mechanism that there are re-ECN markings which have been 
insert by  the sender into the network based on the number of ECN markings 
the receiver has seen and that ECN marking are set by a router to signal 
congestion (usually bases one the current queue length) needs to be 
mentioned. And than you basically explained Re-ECN....?

Then I would like to know if I understood the scenario right: There will be 
one (TCP)-connection (with some congestion control ?) and a way to insert 
congestion (just set marking with a certain probability or start some other 
transmissions...?). I have a couple of these simple scenarios in my 
simulation and either I define the congestion (=setting markings with a 
certain pattern, but what realistic here..?) or the congestion level is 
varying very strong (because of TCP congestion control and most of the time 
there might be no congestion in these simple scenarios).

And how do you actually calculating the current congestion level? Because 
usually there are a couple of markings at one time and than it take more than 
one RTT that the Re-ECN markings balance it. If the congestion level is 
varying strongly, the delay might be a problem for getting a concrete values 
for the current congestion level in one network component...? 
Please correct me if I'm wrong. 

Mirja