Re: [tcpm] Reminder: WGLC for draft-ietf-tcpm-accurate-ecn-26

tuexen@fh-muenster.de Mon, 06 November 2023 11:35 UTC

Return-Path: <tuexen@fh-muenster.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 15A25C1FB878 for <tcpm@ietfa.amsl.com>; Mon, 6 Nov 2023 03:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 oTAIctvzP3cF for <tcpm@ietfa.amsl.com>; Mon, 6 Nov 2023 03:34:59 -0800 (PST)
Received: from mx-out-01.fh-muenster.de (mx-out-01.fh-muenster.de [185.149.214.63]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 120E9C08F9CD for <tcpm@ietf.org>; Mon, 6 Nov 2023 03:34:43 -0800 (PST)
Received: from mail-director-01.fh-muenster.de (mail-director-01.fh-muenster.de [185.149.215.227]) by mx-out-01.fh-muenster.de (Postfix) with ESMTPS id 2CAFF20066; Mon, 6 Nov 2023 12:34:41 +0100 (CET)
Received: from smtpclient.apple (dhcp-9716.meeting.ietf.org [31.133.151.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tuexen) by mail-director-01.fh-muenster.de (Postfix) with ESMTPSA id C7A881A0064; Mon, 6 Nov 2023 12:34:40 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_1DA0E62E-6C3F-4033-98A4-408B828A540E"; protocol="application/pkcs7-signature"; micalg="sha-256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: tuexen@fh-muenster.de
In-Reply-To: <fffb488d-913c-4a01-b88b-f9dbb02f4a62@gmx.at>
Date: Mon, 06 Nov 2023 12:34:39 +0100
Cc: Markku Kojo <kojo=40cs.helsinki.fi@dmarc.ietf.org>, tcpm IETF list <tcpm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F99166D-0DF3-49E0-81A2-72FDD510DAFF@fh-muenster.de>
References: <1204E97B-9524-4C9F-8D06-7F81E1F28A6F@fh-muenster.de> <347C33E0-FDFD-4ED9-93FD-397AE361D6DE@cs.helsinki.fi> <fffb488d-913c-4a01-b88b-f9dbb02f4a62@gmx.at>
To: rs.ietf@gmx.at
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/amFVkmgvwkLi6g4ytV3_gW4ujs4>
Subject: Re: [tcpm] Reminder: WGLC for draft-ietf-tcpm-accurate-ecn-26
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: Mon, 06 Nov 2023 11:35:04 -0000

> On Nov 6, 2023, at 11:42, rs.ietf@gmx.at wrote:
> 
> 
> Hi Markku,
> 
> Can you please elaborate again why DSACK needs to be implemented for a SACK-enabled session, in order to detect and differentiate true loss (the core aspect of SACK itself) vs. spurious retransmissions (which are to be avoided, e.g. by not counting identical ACKs with different ACE values against the duplicate ACK threshold)?
> 
> 
> A worked example with / without DSACK and under what circumstances there may be a dramatic impact, would be indeed very helpful.
> 
> Thank you very much!
I would like to see concrete proposals from Markku how to fix the issues Markku has first.
That might help in understanding the issues in DSACK/RACK-TLP/F-RTO he is trying to
describe.

Best regards
Michael
> 
> Richard
> 
> 
> Am 06.11.2023 um 11:09 schrieb Markku Kojo:
>> Hi Michael,
>> 
>> catching up…
>> 
>> I am afraid that the crucial piece not addressed is that this approach assumes that by enabling SACK would also enable DSACK in full which is not the case. Therefore, the suggested rule in ECN++ does not result in correct operation for RACK-TLP and F-RTO. It requires correct impöementation at both ends.
>> 
>> I’ve already tried to explain this earlier but try to come up with a detailed list clarifying the actions needed at each end later today.
>> 
>> Thanks,
>> 
>> /Markku
>> 
>> 
>>> tuexen@fh-muenster.de kirjoitti 27.10.2023 kello 19.35:
>>> 
>>> 
>>>> 
>>>> On Sep 21, 2023, at 19:51, tuexen@fh-muenster.de wrote:
>>>> 
>>>> Dear all,
>>>> 
>>>> this e-mail is a gentle reminder for the 2nd working group last call for
>>>> draft-ietf-tcpm-accurate-ecn-26.
>>>> 
>>>> The WGLC runs until Friday, September 22nd 2023.
>>>> 
>>>> Please send any comments, including indications to support this document,
>>>> to the TCMP mailing list by then.
>>>> 
>>>> In particular, if you have made comments during the first WGLC, indicate whether
>>>> the comments have been addressed or not.
>>>> 
>>>> The ID is available at
>>>> https://www.ietf.org/archive/id/draft-ietf-tcpm-accurate-ecn-26.html
>>> Dear all,
>>> 
>>> based on the feedback, the WG chairs have declared consensus on this document.
>>> We do understand that not all all feedback provided was addressed in a way
>>> expected by the person giving the feedback.
>>> 
>>> Best regards
>>> Michael
>>>> 
>>>> Best regards
>>>> Michael
>>>> 
>>> 
>>> _______________________________________________
>>> tcpm mailing list
>>> tcpm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tcpm
>> 
>> _______________________________________________
>> tcpm mailing list
>> tcpm@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpm
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm