Re: [tsvwg] Re draft-kuhn-tsvwg-careful-resume-00

"touch@strayalpha.com" <touch@strayalpha.com> Mon, 27 March 2023 03:47 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D915CC1522D3 for <tsvwg@ietfa.amsl.com>; Sun, 26 Mar 2023 20:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.314
X-Spam-Level:
X-Spam-Status: No, score=-1.314 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t8e_0tM8sCgX for <tsvwg@ietfa.amsl.com>; Sun, 26 Mar 2023 20:47:34 -0700 (PDT)
Received: from server217-2.web-hosting.com (server217-2.web-hosting.com [198.54.115.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26397C151B10 for <tsvwg@ietf.org>; Sun, 26 Mar 2023 20:47:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=GnJtt8G9ckqgRtqd19gkOI1o1Ijt0H+vTl9GhXEOMd0=; b=CIYa3Zb8CfgslaBLuEzpdEczuD EpfIyJNOCG4eIP4U7a6bEeirDsyO2c7afk1C1mLrB6crEmQ0BakVkRZ0SUtADAbNhwQoi5OU/JbIt 1IEJ/N0kJx1VAjlJ2Yd83t1TEJnM29zTTVNjhcHbYwOrwpem5gm+DsPtTo6KkOYH5+rnaywH3PWwb QB5DLtHNWWx0K3sy+Tq4PqfRA6PhO5E/l+UUHojCe2WBCG7uC0Djfn8HTJKvd+UYOTp6L9IzIMX2E l+IvPj4MdMAbNPWP6e+20Hm7uK+mQ0XVV+Bx+nmDK2LXYUXMaI0impeR5prCl62MLrLWdEAL+G9Lw EoDzqnzw==;
Received: from [172.58.208.166] (port=28267 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <touch@strayalpha.com>) id 1pgdpQ-001HeR-Oa; Sun, 26 Mar 2023 23:47:33 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_1F23D72D-AAAE-43D5-B09F-FC10AF1576F2"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <MN2PR11MB3647649C6147ED39171099A590BF9@MN2PR11MB3647.namprd11.prod.outlook.com>
Date: Sun, 26 Mar 2023 20:47:06 -0700
Cc: "Gorry Fairhurst (gorry@erg.abdn.ac.uk)" <gorry@erg.abdn.ac.uk>, Nicolas Kuhn <nicolas.kuhn.ietf@gmail.com>, "emile.stephan@orange.com" <emile.stephan@orange.com>, Christian Huitema <huitema@huitema.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Message-Id: <89E3EBAE-2F68-483E-8DE9-CCE2D676CC37@strayalpha.com>
References: <MN2PR11MB3647649C6147ED39171099A590BF9@MN2PR11MB3647.namprd11.prod.outlook.com>
To: "Border, John" <John.Border=40hughes.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/XTBzPgOIYtp2fpzEIs6F5r6Z3j0>
Subject: Re: [tsvwg] Re draft-kuhn-tsvwg-careful-resume-00
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Mar 2023 03:47:37 -0000

FWIW, there is some long lost past work in this area for TCP:

https://www.ietf.org/archive/id/draft-hughes-restart-00.txt
draft-hughes-restart-00
Text Document · 43 KB

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Mar 15, 2023, at 11:05 AM, Border, John <John.Border=40hughes.com@dmarc.ietf.org> wrote:
> 
>  
>     I think we need little bit of discussion around the fact that RTT and BB can also vary during a connection, especially a long-lived connection, not just from one connection to the next.  Therefore, the saved RTT and BB values should be the RTT and BB near the end of the connection rather than earlier in the connection.  This might require that the values be save (and possibly sent in a BDP_FRAME) multiple times as things change.
>  
>     In Section 3, when I got to the Retreat Phase description, I paused because it seemed like more is needed.  I later found that more in Section 4.5.  I think it would be helpful, for all of the phases, to put pointers to the sections which have more discussion about them.  (Or maybe a blanket pointer to Section 4 for more details at the front of Section 3.)
>  
>     Re Section 4.4 and Section 4.4.1…  I think half of the capacity should be a good choice (although I am still thinking about it).  (Might need to be variable based upon some to be defined criteria.)  But it probably needs to take into account the capacity when compared to the IW.
>  
>  
> John
>  
>  
>  
> Minor comments and nits…
>  
> In the second sentence of the third paragraph of the Abstract…  “allowing then to” should be “allowing them to”.
>  
> In the first sentence of the Introduction…  “there” should be “their”.
>  
> Re Section 1.2…  
> In the second sentence, delete the duplicate “could”. 
> Add “is different” to the first clause of Example 1.
>  
> In the first sentence of Section 1.3…  “secion" should be “section”.
>  
> In Section 1.3.1…  Mention that this is a GEO satellite example.  Might be useful to explicitly state that the difference is the longer slow start time without the method.
>  
> Re Section 3…  
> In the first sentence, remove the first occurrence of the word “through” and change “uit” to “it”.  
> In the last sentence for the Observe Phase description, delete the word “are”. 
> In the Reconnaissance Phase description, “currnetly" should be “currently” and “iniial” should be “initial”.  And, the sentence “The sender is send iniial [sic] data, limited by the Initial Window.” needs rephrasing.
> In the second sentence of the Unvalidated Phase description, “This phase a rate…” should be “This phase allows a rate…” (or something like that).
> In the third sentence of the Retreat Phase description, “re-initialised” should be “re-initialise”. 
>  
> In the title of Section 4.1, “Determing” should be “Determining”.
>  
> In the first sentence of Section 4.3, “irelevant" should be “irrelevant”.
>  
> In the third bullet of Section A.1, “it should an interface…” should be “it should include an interface…”.  Except, the last statement of the third point about what the sender should ensure re the Endpoint Token indicates the “should” should be a “must”.