IETF Logo Mail Archive

Re: [tcpm] draft-ietf-tcpm-hystartplusplus and QUIC

Michael Tuexen <michael.tuexen@lurchi.franken.de> Tue, 20 September 2022 07:13 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 2BFB2C14CF1C for <tcpm@ietfa.amsl.com>; Tue, 20 Sep 2022 00:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.511
X-Spam-Level:
X-Spam-Status: No, score=-1.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.398, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-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 Wy2fPvMsWiMt for <tcpm@ietfa.amsl.com>; Tue, 20 Sep 2022 00:13:36 -0700 (PDT)
Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89901C14CF01 for <tcpm@ietf.org>; Tue, 20 Sep 2022 00:13:36 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1140:c3d:cda2:ff25:c167:c23]) (Authenticated sender: lurchi) by drew.franken.de (Postfix) with ESMTPSA id 95BE372243808; Tue, 20 Sep 2022 09:13:32 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <719333c2-43c9-6bc0-0c9c-a91b83fe74c7@huitema.net>
Date: Tue, 20 Sep 2022 09:13:32 +0200
Cc: Martin Duke <martin.h.duke@gmail.com>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD008DAC-663A-4100-97FD-A3B9E893A251@lurchi.franken.de>
References: <e0f16f9e-e16c-2194-bb1c-2afebde2aacc@huitema.net> <D364F578-5172-48A2-A8CD-BDC24CF2F983@lurchi.franken.de> <719333c2-43c9-6bc0-0c9c-a91b83fe74c7@huitema.net>
To: Christian Huitema <huitema@huitema.net>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/7AHLTNOvYKMAht2enCxeXWdtL_M>
Subject: Re: [tcpm] draft-ietf-tcpm-hystartplusplus and QUIC
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: Tue, 20 Sep 2022 07:13:42 -0000

> On 20. Sep 2022, at 08:39, Christian Huitema <huitema@huitema.net> wrote:
> 
> 
> 
> On 9/19/2022 3:08 PM, Michael Tuexen wrote:
>>> Should congestion control algorithm be specified in a transport protocol specific way, as for example "HyStart++ for QUIC", or should the specification be kept as generic as possible?
>>> 
>> Do you think QUIC specific text is needed in the document to know how to implement it
>> for QUIC? If yes, you can still suggest it.
>> 
> The draft is in state "submitted to the IETF for publication". I am not trying to slow down that publication, and the thread I started is more about the general process issue. That said, the next step is the IETF last call, and I suppose that I could send you a set of QUIC related comments as part of that last call. I will try to do that. Or maybe someone else will...
The AD requested some changes and there need to be an update of the document before it goes to the IETF LC anyway.
TCPM also has some history in receiving non trivial comments for document after the WGLC is over. SO I think
the earlier the comments are sent to the authors, the better.

Best regards
Michael
> 
> -- Christian Huitema
> 
> 
>

v2.23.0 | Report a Bug | By Email