[conex] Comments on ConEx TCP Modifications

Nandita Dukkipati <nanditad@google.com> Wed, 28 March 2012 12:07 UTC

Return-Path: <nanditad@google.com>
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 21D7121F8658 for <conex@ietfa.amsl.com>; Wed, 28 Mar 2012 05:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level:
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 j-b9NeGiDEWq for <conex@ietfa.amsl.com>; Wed, 28 Mar 2012 05:07:32 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5333821F85ED for <conex@ietf.org>; Wed, 28 Mar 2012 05:07:25 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so1489686obb.31 for <conex@ietf.org>; Wed, 28 Mar 2012 05:07:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type :x-system-of-record; bh=9X6hJ2gPyjt+LMalPzyq/10Gm1JC7XxAAWzrJ9cObCQ=; b=R/Qy+fyDm4gMiNF2qT80DpyVM0qRQ7EeRyh8TwXfa6wX3sKJ0IPHHI/4WHqMwDRrTi ikwju6JctxjpvnPxBqwrtevl2UFBG7nryzv/11TIFr4biGj7ftd4OQEH1kDfFLqKOvdg s/Ea01gjZWrfLzYtB2igTh9Ha/iulSJh2r1fYTz5GqBqRtNtcv9GnUKlykoUYIZIm5hg fq97uteEe8d8KZu75skrwUaNc9ZKgv+ddfeuGuXnNP1fCYaGGiAS9liuz7j4H8857/Ag KYo1L8IyWj2SxXZ0fXazVYFnMdOWoYCCOdn7DKn3LuvtIQItvPWhN/Nxf6Z20D56R9mi 63Lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type :x-system-of-record:x-gm-message-state; bh=9X6hJ2gPyjt+LMalPzyq/10Gm1JC7XxAAWzrJ9cObCQ=; b=GojUMbWj33Vz3r+kd+ooVvLFVJPwUhxA20gEP9AXx5zalImeWdYIx2G79jB3+9yZXL xaUap1Dgcyp/sZNj35RG9edk1e5i0Zztj1/TSoc/rjym/TVvLvmfIXQlR/g8n0434wrW LClC/cnJlN6SDMgZ4mEbzCiJ0YCHFZXK3JxiyPzBm5T3DrAPdzPsd2Mi2ZeHQKjHDWQ3 1tuWC3SsfGwZOxtUCeI7ICdNR183tx3Zxv1Y4yGy5lNUrWXKZcxImlsat8lP5Oka/Wvq HVHFc5AL7NKTQkuiIbMr/00Bdqay3MdyTt94Tfj1JH/ZhyPsN6ur8G8jlorOQz+VDMXj cNcg==
Received: by 10.182.202.69 with SMTP id kg5mr38162930obc.35.1332936444770; Wed, 28 Mar 2012 05:07:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.202.69 with SMTP id kg5mr38162912obc.35.1332936444653; Wed, 28 Mar 2012 05:07:24 -0700 (PDT)
Received: by 10.182.69.164 with HTTP; Wed, 28 Mar 2012 05:07:24 -0700 (PDT)
Date: Wed, 28 Mar 2012 14:07:24 +0200
Message-ID: <CAB_+Fg60jqfKs=Dk6VfhWFMNajty4T0Saeov4Sq6zGLzuOAiFg@mail.gmail.com>
From: Nandita Dukkipati <nanditad@google.com>
To: Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>, "Scheffenegger, Richard" <rs@netapp.com>
Content-Type: multipart/alternative; boundary="e89a8f6438c24ab0d404bc4c7375"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQnZ/68wh7QoBuyjADnApjilorGahLUuNsj0MplcNUh9Rz5HN1T3KTTPbFx+7Xg1OAk4ai664JlmV8FCtmx8256k1GezP7ojIh2clFtu/A/1+kBlxddHdz6P8isRBOww7679Bhie
Cc: conex@ietf.org
Subject: [conex] Comments on ConEx TCP Modifications
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: Wed, 28 Mar 2012 12:07:33 -0000

Following are a comments as individual contributor on
http://www.ietf.org/id/draft-ietf-conex-tcp-modifications-01.txt and one
comment as chair.

Nandita

1. What changes, if any, are required to accounting when ConEx marked
packets get lost?

2. Sec 3
"A sender which sends different sized packets with unequally distributed
packet sizes should know about reason to do so and thus may be able to
reconstruct the exact number of headers based on this information."
Sentence doesn't read well; please reword.

3. Sections 3.1.1 and 3.1.2
By acked_bytes I assume you mean the cumulatively acked bytes or the change
in snd.una. What happens when there is loss and snd.una does not advance?
Instead, I suggest that you consider using DeliveredData as defined in
http://datatracker.ietf.org/doc/draft-ietf-tcpm-proportional-rate-reduction/?include_text=1
-
it tracks precisely that amount of data delivered to the receiver for each
ACK even in the loss case.

4. Section 3.1.2
"Unfortunately, in a high congestion situation where all packets are CE
marled..."
marled -> marked

5. Section 3.1.2
On the use of 'M'
You won't require to use any variable 'M' when you track precisely the
bytes delivered per ACK using the DeliveredData that I mentioned above.

6. Sec 3.1.2
"In average the sender will sent..." -> "On average the sender will send..."

7. Advanced Compatibility mode
Not clear to me at all what this text is trying to say.

8. Sec 3.2
"Note that the above heuristics delays the ConEx signal by one segment, and
also..."
You mean delay by 1 RTT?

Comment as chair

Section 3 Accounting Congestion
bytes vs. packets: I would like to see consistency across the two drafts
(abstract mechanism, TCP modifications) on the issue of whether ConEx
marking and accounting should be in bytes or in packets. What are the
pros/cons and corner cases for each? What is the final recommendation that
you make? Which of these drafts should make this recommendation - I would
think it's the TCP modifications draft.

If you haven't already, could you please read up the latest Concepts and
Abstract Mechanism draft and communicate with the authors of that document
and make sure we have consistency on bytes vs. packets across the two I-Ds.