Re: [tcpm] [draft-ietf-tcpm-rto-consider-07] Interaction with other time-based recovery schemes?

"Mark Allman" <mallman@icir.org> Tue, 12 February 2019 14:05 UTC

Return-Path: <mallman@icir.org>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 935D112008A; Tue, 12 Feb 2019 06:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 YrjsMdHBfrXU; Tue, 12 Feb 2019 06:05:44 -0800 (PST)
Received: from rock.ICSI.Berkeley.EDU (rock.ICSI.Berkeley.EDU [192.150.186.19]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 177AE12867A; Tue, 12 Feb 2019 06:05:44 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id CEAF175864B; Tue, 12 Feb 2019 06:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at ICSI.Berkeley.EDU
Received: from rock.ICSI.Berkeley.EDU ([127.0.0.1]) by localhost (maihub.ICSI.Berkeley.EDU [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HdVfx-U8sYSZ; Tue, 12 Feb 2019 06:05:43 -0800 (PST)
Received: from lawyers.icir.org (scone [192.150.186.121]) by rock.ICSI.Berkeley.EDU (Postfix) with ESMTP id 5482E75864A; Tue, 12 Feb 2019 06:05:43 -0800 (PST)
Received: from [169.254.84.90] (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id F1F8DC885B6; Tue, 12 Feb 2019 09:05:42 -0500 (EST)
From: Mark Allman <mallman@icir.org>
To: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
Cc: draft-ietf-tcpm-rto-consider@ietf.org, tcpm@ietf.org
Date: Tue, 12 Feb 2019 09:05:42 -0500
X-Mailer: MailMate (1.12.4r5594)
Message-ID: <BF35282C-EE1D-49BA-8816-9662B61E5CBB@icir.org>
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF1EB8DCED@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <F3B0A07CFD358240926B78A680E166FF1EB8B9CE@TW-MBX-P03.cnesnet.ad.cnes.fr> <86798307-C256-4911-A4CB-0DDD2693175A@icsi.berkeley.edu> <F3B0A07CFD358240926B78A680E166FF1EB8DCED@TW-MBX-P03.cnesnet.ad.cnes.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_DB33E129-AF12-4258-BF64-AE5E49C029EC_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/3FE8KzmIh6u55bEZ8rgVFMqINbk>
Subject: Re: [tcpm] [draft-ietf-tcpm-rto-consider-07] Interaction with other time-based recovery schemes?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2019 14:05:46 -0000

Hi Nico!

> [NK] IMHO, if this is meant to be an umbrella under which
> timer-based retransmission live, this should be stated more
> clearly in the draft.

Can you give me suggestions?  I just re-read sections 1 & 2 and I'm
not sure I have better words in my head.  E.g., do you find the last
paragraph of the new context section unclear?

> The hierarchical view of
> timer that you mentioned here could be clearly stated in the
> document. Or you could try to harmonize it with the "PTO" notion
> in QUIC
> https://tools.ietf.org/html/draft-ietf-quic-recovery-18#section-6.2.2

(I don't follow this.  I don't think I sketched a "hierarchical
view".  So, I am confused.)

> [NK] This is the case when RACK and RTO are used conjointly in TCP.
>
> [...]
>
> And, you would like to see a note to that effect in
> S.6 (where we note that other reliability schemes could be in play)?
> If that is the point, sure, I buy that.
>
> [NK] This was my main point indeed.

So, does all this boil down to you want another example under S.6
that says (essentially) "multiple retransmission timers could be in
play"?  I.e., something analogous to the notion that is in there now
that "there may be timers and ACKs/SACKs in play" but explicitly
noting it could be more than one timer?  That sounds like a fine and
reasonable idea to me.  But, I am unclear on whether this covers
your entire comment or not.

Thanks!

allman