[tcpm] Re: I-D Action: draft-ietf-tcpm-accurate-ecn-29.txt

Michael Tuexen <michael.tuexen@lurchi.franken.de> Tue, 20 August 2024 09:20 UTC

Return-Path: <michael.tuexen@lurchi.franken.de>
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 2D389C14F6E2 for <tcpm@ietfa.amsl.com>; Tue, 20 Aug 2024 02:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level:
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01] autolearn=no 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 oikTZj2Z535n for <tcpm@ietfa.amsl.com>; Tue, 20 Aug 2024 02:20:36 -0700 (PDT)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F82CC14F6A7 for <tcpm@ietf.org>; Tue, 20 Aug 2024 02:20:34 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:c1d6:55af:2ce0:e5b8]) (Authenticated sender: lurchi) by mail-n.franken.de (Postfix) with ESMTPSA id 95534721E280D; Tue, 20 Aug 2024 11:20:29 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <CE8A452B-7105-420F-86B9-1C5036070456@apple.com>
Date: Tue, 20 Aug 2024 11:20:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C070982-6A14-43CE-AA67-3E9AF41EFC9C@lurchi.franken.de>
References: <171932322224.146587.9557217748463927783@dt-datatracker-5864469bc9-n5hqk> <e67709b2-79e8-4530-b8c6-0b5736659826@gmx.at> <CE8A452B-7105-420F-86B9-1C5036070456@apple.com>
To: Stuart Cheshire <cheshire=40apple.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3776.700.51)
Message-ID-Hash: BL3KEYLB6UUSYSNQ2CHJSZVGBXR3AMWD
X-Message-ID-Hash: BL3KEYLB6UUSYSNQ2CHJSZVGBXR3AMWD
X-MailFrom: michael.tuexen@lurchi.franken.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tcpm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tcpm@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tcpm] Re: I-D Action: draft-ietf-tcpm-accurate-ecn-29.txt
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/kBOtf8IdlMnIeDqpU7SWyc2DqsM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Owner: <mailto:tcpm-owner@ietf.org>
List-Post: <mailto:tcpm@ietf.org>
List-Subscribe: <mailto:tcpm-join@ietf.org>
List-Unsubscribe: <mailto:tcpm-leave@ietf.org>

> On 23. Jul 2024, at 22:06, Stuart Cheshire <cheshire=40apple.com@dmarc.ietf.org> wrote:
> 
> On Jun 28, 2024, at 02:30, Richard Scheffenegger wrote:
> 
>> This version updates the text in section 3.3.4 to differentiate between
>> transmit and receive path TCP segmentation offload (TSO) and Large
>> Receive Offload (LRO). In particular, more specific guidance is given
>> what to consider when implementing AccEcn with TSO / LRO.
>> 
>> Best regards,
>>  Richard Scheffenegger
> 
> Last weekend I read draft-ietf-tcpm-accurate-ecn-29 from start to finish.
> 
> I want to start by congratulating and thanking the authors for an excellent document.
> 
> The idea of Accurate ECN could be described in one page; the rest of the document is a very thorough analysis of all the forwards- and backwards-compatibility issues -- legacy servers that don’t support Accurate ECN, buggy servers that don’t even implement classic ECN negotiation properly, poorly designed middleboxes that try to “help” TCP connections and actually mess them up.
> 
> This draft dates back to 2015. It is long overdue that we get it published. Apple has implemented Accurate ECN. Wireshark correctly decodes Accurate ECN. We’d love to see Accurate ECN supported in mainline Linux too, but the Linux networking maintainers are quite reasonably cautious about what they put in the Linux networking code. The want to see a Standards-Track RFC that shows it has received IETF review and consensus. CableLabs and Comcast are rolling out L4S, but TCP can’t use L4S without Accurate ECN. A lot of progress has been made here, but we’re starting to see progress being held up by the lack of RFC publication. What can I do to help?
> 
> I also have a couple of minor editorial comments which I will send in a separate email.
Hi Stuart,

it would be great, if you could provide your comments soon, since we have two
early reviews requested and it would be great to incorporate your comments in
combination with addressing any comments raised by the sec and int reviews.

Thank you very much in advance.

Best regards
Michael
> 
> Stuart Cheshire
> 
> _______________________________________________
> tcpm mailing list -- tcpm@ietf.org
> To unsubscribe send an email to tcpm-leave@ietf.org