[conex] Accounting of ConEx signals

Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de> Thu, 06 October 2011 23:12 UTC

Return-Path: <mirja.kuehlewind@ikr.uni-stuttgart.de>
X-Original-To: conex@ietfa.amsl.com
Delivered-To: conex@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C75C21F86F6 for <conex@ietfa.amsl.com>; Thu, 6 Oct 2011 16:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.703
X-Spam-Level:
X-Spam-Status: No, score=-1.703 tagged_above=-999 required=5 tests=[AWL=0.246, BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oFJu1OTM05uN for <conex@ietfa.amsl.com>; Thu, 6 Oct 2011 16:12:18 -0700 (PDT)
Received: from mailsrv.ikr.uni-stuttgart.de (mailsrv.ikr.uni-stuttgart.de [129.69.170.2]) by ietfa.amsl.com (Postfix) with ESMTP id B22CE21F86EE for <conex@ietf.org>; Thu, 6 Oct 2011 16:12:18 -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 14499633B2; Fri, 7 Oct 2011 01:15:28 +0200 (CEST)
Received: from vpn-2-cl177 (vpn-2-cl177 [10.41.21.177]) by netsrv1.ikr.uni-stuttgart.de (Postfix) with ESMTP id E3F2259A8A; Fri, 7 Oct 2011 01:15:27 +0200 (CEST)
From: Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
To: conex@ietf.org
Date: Fri, 07 Oct 2011 01:15:27 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20101217.1207316)
MIME-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201110070115.27485.mkuehle@ikr.uni-stuttgart.de>
Subject: [conex] Accounting of ConEx signals
X-BeenThere: conex@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Congestion Exposure working group discussion list <conex.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/conex>, <mailto:conex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/conex>
List-Post: <mailto:conex@ietf.org>
List-Help: <mailto:conex-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/conex>, <mailto:conex-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2011 23:12:19 -0000

Hi everybody,

Richard and I are currently working on the TCP modifications draft. And we get 
always stocked at the same question how the accounting of the ConEx signal 
should be done. I believe we assume that the ConEx signal is counted 
byte-wise that means all bytes of a marked packet are assumed to expose the 
link congestion. First of all, I have to say hat this is nowhere officially 
defined. That lead to the following couple of questions:

1. Where do we need to define this? In the IPv6 doc? 
Because it might be a more general question and it must be clear to everyone 
that if we account the signal byte-wise this has to be done in the endsystem 
as well as in every network device using this information.

2. Which bytes of a packet do we take? The IP length incl header, the IP 
payload incl. TCP header or the actual payload?
In TCP if a packet get lost (with SACK) we only know how many payload got 
lost. We do not know the number of packets/headers that were used to transmit 
this data. If we would loose one big packet and then retransmit a large 
number of small packets instead (which are all ConEx marked) that might give 
quite a different ConEx signal. On the other hand, what causes the congestion 
is the whole packet incl header(s). What is the right thing to do?

Input is very welcome!

Thx,
Mirja