Re: [tcpPrague] [tcpm] Fwd: I-D Action: draft-bagnulo-tcpm-tcp-low-rtt-00.txt

Yuchung Cheng <ycheng@google.com> Fri, 12 August 2016 19:17 UTC

Return-Path: <ycheng@google.com>
X-Original-To: tcpprague@ietfa.amsl.com
Delivered-To: tcpprague@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A2512DA79 for <tcpprague@ietfa.amsl.com>; Fri, 12 Aug 2016 12:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9tjw0DVv0J0t for <tcpprague@ietfa.amsl.com>; Fri, 12 Aug 2016 12:17:39 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABAB712DA77 for <tcpPrague@ietf.org>; Fri, 12 Aug 2016 12:17:38 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id x130so22373574ite.1 for <tcpPrague@ietf.org>; Fri, 12 Aug 2016 12:17:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=atQvp5QLu9eHcACWMpKPdIBlW1Saxwbelb4UhU5bfE8=; b=DGgOLleQgI8VI5s9iJbu3gEndOf3QlmOLUTkcykYtb64XZb2hhinVA9JmkXaHdKdUz BDCo5ak7aOBLwz3cn5QHk0FrIShgKNUyqOtSxdVdlXCrCvaaW7rDZFMm+2AsxPS4HiLp 5sYC33V582aeqAD+V+IiharOBKAVb7KMu4HFXR61nYGm2QZq5hBqC+bBkFVeXy/8bDR1 DGL8bo6E4K9+DR+ZOq2b0feZaSgAYZf3mPGp5wJ+1pgEE8uxyetZ1TL1OukV8SWZXAIF /fbVmCmxJuVNmhS5lHxkUKF7k27YdpNj5yEKP4BrKfL+Fw3TXVn19m05C3sWudc8VSUq nt3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=atQvp5QLu9eHcACWMpKPdIBlW1Saxwbelb4UhU5bfE8=; b=MCy63l0sLyEdCB2zPuujxJIkuX81/uyiDEsTThNtSriL0kFB4bCkYPg8Ni7N8MQLYl Sjn/U3W3MCm1LtZ9qFSzTQK4EY1JOAVgvB6JMp7rnl4ZaeNmfXGVJD6So7IwIZiHyH0y y27sds4bNjGaoLA0esqOuo8nxqm1TXT9f8pHWfMMNLCG3pNBtx1z36gjXQeKppzCCigv QulwkqnHavC3SJO1vHTYAPHzjoqqVJALJmTE+MnvSLXVQsaZ2ItjB0fxE8PRXk5OTk/F OZlkwbx7IJsepO+6x0+qafSv3SlBFDCPWe730Be/GvRrqsKn5MVqacMULCGdHx8IwanM c5Bw==
X-Gm-Message-State: AEkoouulpbjtyOT2W8K+j+X6ycjPg4qPbY+VZcTeHxQNXNye4C4fwes/JUJhmOP49K0FTGjhTcgtyveOQ+ozqtUE
X-Received: by 10.36.150.70 with SMTP id z67mr516444itd.80.1471029450970; Fri, 12 Aug 2016 12:17:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.244.103 with HTTP; Fri, 12 Aug 2016 12:16:50 -0700 (PDT)
In-Reply-To: <a1f456db6e656785da8e356b9f530717@mail.gmail.com>
References: <20160708211635.32095.77047.idtracker@ietfa.amsl.com> <2f56d1b8-7450-42de-4a24-53df9cf4c045@it.uc3m.es> <a1f456db6e656785da8e356b9f530717@mail.gmail.com>
From: Yuchung Cheng <ycheng@google.com>
Date: Fri, 12 Aug 2016 12:16:50 -0700
Message-ID: <CAK6E8=etaxFSgBvQt27s=rB03rRQxQ_u43qWRExTVXys9A82wg@mail.gmail.com>
To: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpprague/Wp_IcTEFjmubNKbZsHd44aFKbDo>
Cc: marcelo bagnulo braun <marcelo@it.uc3m.es>, tcpm IETF list <tcpm@ietf.org>, TCP Prague List <tcpPrague@ietf.org>
Subject: Re: [tcpPrague] [tcpm] Fwd: I-D Action: draft-bagnulo-tcpm-tcp-low-rtt-00.txt
X-BeenThere: tcpprague@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "To coordinate implementation and standardisation of TCP Prague across platforms. TCP Prague will be an evolution of DCTCP designed to live alongside other TCP variants and derivatives." <tcpprague.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpprague>, <mailto:tcpprague-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpprague/>
List-Post: <mailto:tcpprague@ietf.org>
List-Help: <mailto:tcpprague-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpprague>, <mailto:tcpprague-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2016 19:17:40 -0000

On Fri, Aug 12, 2016 at 4:30 AM, Karen Elisabeth Egede Nielsen
<karen.nielsen@tieto.com> wrote:
>
> Hi Marcello,
>
> I very much appreciate your draft.
>
> Even more so as it addresses one of the things I find to be a bit
> "disturbing"  in the l4s drafts - Namely the claim that the finer saw
> tooth functionality of l4s/DCTCP alone solves the latency problems (while
> DCTCP indeed also is tuning the RTO timeout aggressively).
> E.g., the formulation in  section 1.1 of
> https://datatracker.ietf.org/doc/draft-briscoe-tsvwg-ecn-l4s-id/?include_t
> ext=1
>
> It turns out that a TCP algorithm like DCTCP that solves TCP's
>    scalability problem also solves the latency problem, because the
>    finer sawteeth cause very little queuing delay.  A supporting paper
>    [DCttH15] gives the full explanation of why the design solves both
>    the latency and the scaling problems, both in plain English and in
>    more precise mathematical form.  The explanation is summarised
>    without the maths in [I-D.briscoe-aqm-dualq-coupled].
>
> could benefit from a reference to your draft or the issue that you
> addresses here (at least for comprehensiveness).
>
> An additional comment is  that new approaches to retransmissions - like
> TCP TLP and TCP RACK (also SCTP TLR which however is not progressing at
> the moment) might fundamentally alter the picture. I.e., if
> retransmissions are sent pro-actively in tail loss situations then more
> conservative RTOs may be kept for situations where it is prudent to wait
> longer. Don't know if TCP TLP is so widely deployed that it is something
> that you should relate to even if it may be superseded by RACK. Just a
> thought.
TLP and RACK help reduce timeout cases in DC environment for sure. But
still it can not completely avoid timeouts. So I agree we should keep
timeouts conservative, but the current RFCs are way too conservative:
min RTO of 1 second is 4-5 orders of magnitude of DC RTTs.

The issue is, the "right" min-RTO depends on the actual DC and stacks:
they all have different RTTs and timer granularity. The draft cites
Glenn's paper, but Morgan Stanley's DC could be different than others.


Other comments on the draft:

1. min ssthresh or cwnd: with very large incast ((tens of) thousands
of senders into one receiver), cwnd of 0.1 pkt can still be too big. the
only way is to pace the packets over N*RTT intervals.


2. delayed acks:
as mentioned the actual time depends a lot on the DC implementation,
which is really "vender/owner"-specific. instead of perhaps an option
during setup to inform the sender about the max delay in the ack works
better.



>
> BR, Karen
>
> > -----Original Message-----
> > From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of marcelo bagnulo
> > braun
> > Sent: 8. juli 2016 23:19
> > To: tcpm IETF list <tcpm@ietf.org>
> > Subject: [tcpm] Fwd: I-D Action: draft-bagnulo-tcpm-tcp-low-rtt-00.txt
> >
> > Hi,
> >
> > We just submitted this draft for consideration of the WG. Comments are
> > appreciated.
> >
> > Regards, marcelo
> >
> >
> >
> >
> > -------- Mensaje reenviado --------
> > Asunto:       I-D Action: draft-bagnulo-tcpm-tcp-low-rtt-00.txt
> > Fecha:        Fri, 08 Jul 2016 14:16:35 -0700
> > De:   internet-drafts@ietf.org
> > Responder a:  internet-drafts@ietf.org
> > Para:         i-d-announce@ietf.org
> >
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >
> >
> >          Title           : Recommendations for increasing TCP
> performance in low RTT
> > networks.
> >          Authors         : Marcelo Bagnulo
> >                            Koen De Schepper
> >                            Glenn Judd
> >       Filename        : draft-bagnulo-tcpm-tcp-low-rtt-00.txt
> >       Pages           : 7
> >       Date            : 2016-07-08
> >
> > Abstract:
> >     This documents compiles a set of issues that negatively affect TCP
> >     performance in low RTT networks as well as the recommendations to
> >     overcome them.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-bagnulo-tcpm-tcp-low-rtt/
> >
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-bagnulo-tcpm-tcp-low-rtt-00
> >
> >
> > Please note that it may take a couple of minutes from the time of
> submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > _______________________________________________
> > tcpm mailing list
> > tcpm@ietf.org
> > https://www.ietf.org/mailman/listinfo/tcpm