IETF Logo Mail Archive

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

Michael Tuexen <michael.tuexen@lurchi.franken.de> Tue, 20 September 2022 07:11 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 CC9CCC1522B3 for <tcpm@ietfa.amsl.com>; Tue, 20 Sep 2022 00:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level:
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.398, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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 t1EpQabA1LlR for <tcpm@ietfa.amsl.com>; Tue, 20 Sep 2022 00:11:55 -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 5D441C14F74C for <tcpm@ietf.org>; Tue, 20 Sep 2022 00:11:54 -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 8F49D72243808; Tue, 20 Sep 2022 09:11:48 +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: <8317ED87-0689-42FD-AB0C-E5DD646B7C48@eggert.org>
Date: Tue, 20 Sep 2022 09:11:47 +0200
Cc: Christian Huitema <huitema@huitema.net>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D984C51C-4708-4CC9-99A8-CAF342BDEC03@lurchi.franken.de>
References: <D364F578-5172-48A2-A8CD-BDC24CF2F983@lurchi.franken.de> <8317ED87-0689-42FD-AB0C-E5DD646B7C48@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/Q6gT9ED5lnOIlo5ke_idPBmrYl0>
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:11:59 -0000

> On 20. Sep 2022, at 08:03, Lars Eggert <lars@eggert.org> wrote:
> 
> On Sep 20, 2022, at 01:08, Michael Tuexen <Michael.Tuexen@lurchi.franken.de> wrote:
>> 
>> However, most
>> of the specs use a language specific to one transport protocol but you can easily
>> translate them to the other. So there is some transfer to be made by the reader.
> 
> I think that asking the reader to make that transfer is extra work and a potential source of ambiguities and errors. In the past, one could assume that everyone was deeply familiar with TCP, since that was by far the dominant protocol, but that situation is changing.
So are you suggesting to use

(a) QUIC and let people not using QUIC do the transfer
(b) use an abstract way of describing things covering DCCP, QUIC, SCTP, and TCP
(c) Cover in each document all relevant protocols explicitly

(b) doesn't exist yet. (c) requires knowledge about a set of protocols, even if
someone is focussing on one.

Best regards
Michael
> 
> Lars
> 
> -- 
> Sent from a mobile device; please excuse typos.

v2.23.0 | Report a Bug | By Email