IETF Logo Mail Archive

Re: [tcpm] RFC3449 & AccECN

"Gorry (erg)" <gorry@erg.abdn.ac.uk> Wed, 06 July 2022 16:31 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 CC2B2C157B33 for <tcpm@ietfa.amsl.com>; Wed, 6 Jul 2022 09:31:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 2Xfhk6rinluO for <tcpm@ietfa.amsl.com>; Wed, 6 Jul 2022 09:31:40 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id A2860C157B32 for <tcpm@ietf.org>; Wed, 6 Jul 2022 09:31:37 -0700 (PDT)
Received: from smtpclient.apple (unknown [148.252.129.66]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 2ABD81B00049; Wed, 6 Jul 2022 17:31:00 +0100 (BST)
Content-Type: multipart/alternative; boundary="Apple-Mail-23C01333-43EC-4904-B80B-EC74C698BFC3"
Content-Transfer-Encoding: 7bit
From: "Gorry (erg)" <gorry@erg.abdn.ac.uk>
Mime-Version: 1.0 (1.0)
Date: Wed, 06 Jul 2022 17:30:58 +0100
Message-Id: <4A3BA7DE-BB0F-4693-9D04-AFE94AB8D96D@erg.abdn.ac.uk>
References: <9f51a991-3d30-8911-bc20-6b54ebea0203@bobbriscoe.net>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, Richard Scheffenegger <rs.ietf@gmx.at>, tcpm IETF list <tcpm@ietf.org>, Yoshifumi Nishida <nsd.ietf@gmail.com>
In-Reply-To: <9f51a991-3d30-8911-bc20-6b54ebea0203@bobbriscoe.net>
To: Bob Briscoe <ietf@bobbriscoe.net>
X-Mailer: iPhone Mail (19E258)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/jUUeI3hMKV47odc_qwDkF6CKJ_w>
Subject: Re: [tcpm] RFC3449 & AccECN
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 06 Jul 2022 16:31:41 -0000

I do think this is the correct direction with respect to How to handle this. I don’t have any further requests on the approach, but I would question whether the proposed text:

/feeding back  a run of packets/

Is actually clear - is something more like
/feed back about a received  run of packets /
Clearer … you will know what reads best.

Gorry 

> On 6 Jul 2022, at 17:04, Bob Briscoe <ietf@bobbriscoe.net> wrote:
> 
> feeding back a run of packets

v2.23.0 | Report a Bug | By Email