Re: [tcpm] 793bis ready to go?

Jonathan Morton <chromatix99@gmail.com> Tue, 16 February 2021 09:40 UTC

Return-Path: <chromatix99@gmail.com>
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 C1A963A1142 for <tcpm@ietfa.amsl.com>; Tue, 16 Feb 2021 01:40:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o975h7-TZv2y for <tcpm@ietfa.amsl.com>; Tue, 16 Feb 2021 01:40:45 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 6230F3A1141 for <tcpm@ietf.org>; Tue, 16 Feb 2021 01:40:45 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id u25so14792057lfc.2 for <tcpm@ietf.org>; Tue, 16 Feb 2021 01:40:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=A999Rv6RS2i3jJ0JBJ/4KsrqNMCKrfmfkaHfdTOTGYQ=; b=CEj3hNeAT/eL9ICn0gSUyidKp9rrjvG+mmJkSs2Jl2+xqwG+JJlu7nGReWF6Vqt2eJ yvqoBnawcHO7bNOKb3t+vCIk4ZmKYoNT3R5H++1xXiBeGqpzii+/E8duhEWLyk+h+vkV wEqt2R11WBARIGq4TKCqsdXv4CcGvfzA2Oam4YhAkerfNS2wcrZhduWJoil/uZUCcbpO whw1tu6hhJ0bxyA/03ZQ4MP/bSZxDemq4R95lPdwkKeeZ0opixA0ddwtPdsoMVmN4oFR YVLZcN4HPjwdw9BFmmxA7tpqQqmVi67MM33RJJQzv7HwZmOY3eaHBa+N76mQ9NBTYKqM aQ6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=A999Rv6RS2i3jJ0JBJ/4KsrqNMCKrfmfkaHfdTOTGYQ=; b=k+yBrPrd9iUTukBvgFkJHtgnT7AvZPhatpC9Aze7GMPUTTV1jWZ9IHH1XcLsrePEBT Nnb2soa0zfDB3Y5cXkcmfmz10zGdq8pnWtyY7fwWBconvee5fb6PGoruLnSqc/PzzQzy 5m9IBrHjkYEjzFL1tSq4mJuLJwie+r6XD42Xp6awUGZrjS8JpMJkATVNiXSbaMirZiBQ f/M1Uv/RUGptzIjNULr0NRXbY8x+m13Bh3dFkZuZG+3/K0CFrqM1RIOkxVb3Vr9HpGAW ji6hWHtR7PPMahkI2+rLe0lOR82OIM+gzMRH55zpNXhuSzanJAF1D9AvL7KAqq1Y9aok hdew==
X-Gm-Message-State: AOAM531FNQKakBCvd2SKsedtq5uwsU/MkBR9jJJ5ZHCxFl0lZhXbfNYH UY9lpZvA5PALoal5JXdPEPU=
X-Google-Smtp-Source: ABdhPJwDhwyAIwn43ctpyb5FBjZTvom7/ygSF9qzEGGYjKsVOVczBH12tCkEm5II8HLk+7Um8p4M7g==
X-Received: by 2002:ac2:5b89:: with SMTP id o9mr11596487lfn.54.1613468443542; Tue, 16 Feb 2021 01:40:43 -0800 (PST)
Received: from jonathartonsmbp.lan (188-67-254-178.bb.dnainternet.fi. [188.67.254.178]) by smtp.gmail.com with ESMTPSA id f20sm3093527lfk.188.2021.02.16.01.40.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Feb 2021 01:40:43 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <cd600644350847ef8415d21588d1e912@hs-esslingen.de>
Date: Tue, 16 Feb 2021 11:40:41 +0200
Cc: tcpm IETF list <tcpm@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <085E60F6-B396-4AB2-8BAE-BF615AD51825@gmail.com>
References: <cd600644350847ef8415d21588d1e912@hs-esslingen.de>
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/SE-10AUrQapFLp_FcKC-3d_7BA4>
Subject: Re: [tcpm] 793bis ready to go?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Feb 2021 09:40:47 -0000

> On 8 Feb, 2021, at 7:00 pm, Scharf, Michael <Michael.Scharf@hs-esslingen.de> wrote:
> 
>   A TCP endpoint MUST implement the basic congestion control algorithms
>   slow start, congestion avoidance, and exponential back-off of RTO to
>   avoid creating congestion collapse conditions (MUST-19).  RFC 5681
>   and RFC 6298 describe the basic algorithms on the IETF Standards
>   Track that are broadly applicable.  Multiple other suitable
>   algorithms exist and have been widely used.  Many TCP implementations
>   support a set of alternative algorithms that can be configured for
>   use on the endpoint.  An endpoint may implement such alternative
>   algorithms provided that the algorithms are conformant with the TCP
>   specifications from the IETF Standards Track as described in RFC
>   2914, RFC 5033 [10], and RFC 8961 [15].

I agree that this is substantially the right approach.  One quibble is that the word "may" is used, but not capitalised and given a corresponding MAY-X entry in Appendix B.  I think it would be appropriate to do so here, in the last sentence above.

 - Jonathan Morton