IETF Logo Mail Archive

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

Lars Eggert <lars@eggert.org> Tue, 20 September 2022 09:15 UTC

Return-Path: <lars@eggert.org>
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 95F6EC1522CD for <tcpm@ietfa.amsl.com>; Tue, 20 Sep 2022 02:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 h8E9HYkzE5u7 for <tcpm@ietfa.amsl.com>; Tue, 20 Sep 2022 02:15:46 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53B6AC1522BD for <tcpm@ietf.org>; Tue, 20 Sep 2022 02:15:46 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:5ddf:ece4:fa0b:539b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 0FEAA1DBD92; Tue, 20 Sep 2022 12:15:17 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1663665318; bh=tuYwDgkmMZI1fbl5b6zgiJnX/q1S3IegsfcaQUM8yx8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=c0nmpBYVTXw3SQMBOPEEvXui1AOGn2/cuZlKoIrVmY+Npk7FtUHQ7nJ2Ya98dME+Z 8I0DezgOeTsYxkujGxvpj5A/tHz3Pa8Q85HDIMvuWeq41pWzTj2AEs7z0EDoptjF3b yOEuQ/wQXGPCtQzEdXaxN9u/1nWNfcRCn70iwzuI=
Content-Type: multipart/signed; boundary="Apple-Mail=_2C6C41B4-7344-47F0-A2D0-F09BC121F6DE"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <D984C51C-4708-4CC9-99A8-CAF342BDEC03@lurchi.franken.de>
Date: Tue, 20 Sep 2022 12:15:16 +0300
Cc: Christian Huitema <huitema@huitema.net>, "tcpm@ietf.org Extensions" <tcpm@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Message-Id: <40FAA03F-CEC3-45E8-9925-54EBDBECF220@eggert.org>
References: <D364F578-5172-48A2-A8CD-BDC24CF2F983@lurchi.franken.de> <8317ED87-0689-42FD-AB0C-E5DD646B7C48@eggert.org> <D984C51C-4708-4CC9-99A8-CAF342BDEC03@lurchi.franken.de>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
X-MailScanner-ID: 0FEAA1DBD92.A6249
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/1h7xtudo5khnJGD5JRoJniqfSF4>
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 09:15:53 -0000

On 2022-9-20, at 10:11, Michael Tuexen <Michael.Tuexen@lurchi.franken.de> wrote:
> 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.

(b) and if the authors have the ability to do so for certain protocols - which they should if they author a CC doc - (c) for those.

Lars

v2.23.0 | Report a Bug | By Email