Re: [tcpm] 793bis ready to go?
Wesley Eddy <wes@mti-systems.com> Tue, 04 May 2021 02:32 UTC
Return-Path: <wes@mti-systems.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 E508D3A200B
for <tcpm@ietfa.amsl.com>; Mon, 3 May 2021 19:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
NICE_REPLY_A=-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=mti-systems-com.20150623.gappssmtp.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 y6o5PN63kF_F for <tcpm@ietfa.amsl.com>;
Mon, 3 May 2021 19:32:52 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com
[IPv6:2607:f8b0:4864:20::732])
(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 7F4E73A1F77
for <tcpm@ietf.org>; Mon, 3 May 2021 19:32:52 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id u20so7223718qku.10
for <tcpm@ietf.org>; Mon, 03 May 2021 19:32:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=mti-systems-com.20150623.gappssmtp.com; s=20150623;
h=subject:to:cc:references:from:message-id:date:user-agent
:mime-version:in-reply-to:content-transfer-encoding:content-language;
bh=6Gn9ktCLqYmNWfJdj3SVOKrkXdCShhtFy4YxMXo4Cmo=;
b=2NjmMNkzjgc+y/XP/XjI6dFjZFffYO6uutguMIVT2+aHfbaXCjt6wMjFsENBVS1rfl
krgoLrErBjbYLYLLVW481ky+j122qLfr2keo1zt9nJ2YdSDxQWvk616g1MslDLkWD9IT
kJ7wQzzu8dMeWQHzKNATm7Ndm1luXEAgtkmk4HJmYWoF/b/B9cLUEnprowM90bhzoZJK
ugTMpksGqCs8K52BgjvGgR5kf1nyIJXnnTLXH3jOALRVtNnF9/1wCnJGBaKb8hTg/oMM
eT6cP9rP7OiRNXV7B1zwxs55T+m9yutWPi8j9AlHrDzUwxUciX1YIrbVi/+ZdXTqY2AB
Am4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:cc:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-transfer-encoding
:content-language;
bh=6Gn9ktCLqYmNWfJdj3SVOKrkXdCShhtFy4YxMXo4Cmo=;
b=IazSN/UZdL2EfGZ4VGPy5lDtEuM9VymIkOk8Vx+9Mcm+6qH4Cku94Iev8D+cn/nZDe
1q1LB6Z5BWeCandSuD5rlcNnRqTnqFkVqq2s8TJAHaLyagddEzuIxV6ndTzp9/b9aMhg
QaSKt1Noo5C7BqVvk9luInh/6hy4cMSYmyw6DiorGrYO0JbUvoL/9ZZk/2RT+qfbPCVk
Qv8+u0XFcEXqIjn/1sUGxaqkOXde9fEZtnnNRD6cjO+4FllGHoiI0MIw/9ZBD42+vb5O
oykxm2uSico/D6bzzSOPSD7nDZwtXD9f+r1GPgfUWV1nwY/XHPuu+oWfC+A2rBgo6Z38
tJMw==
X-Gm-Message-State: AOAM533jBJnXUZcE3UC2tqll8xriJdfKRX0RdBfwXq0kaSV89szvVv2j
daTpxKhjHisp9MP4GKZ4nGn1ylOyPx5kTRwH
X-Google-Smtp-Source: ABdhPJy5q7L6SZOgE/GQeemzU31TCoAYYu1iBrgV2cM4DOChzuB6Yldo7r29ESVXce/c+sPj9eTDsg==
X-Received: by 2002:a37:7d84:: with SMTP id
y126mr21988603qkc.155.1620095570832;
Mon, 03 May 2021 19:32:50 -0700 (PDT)
Received: from [192.168.1.14] (cpe-174-102-117-3.columbus.res.rr.com.
[174.102.117.3])
by smtp.gmail.com with ESMTPSA id v127sm10143788qkh.37.2021.05.03.19.32.49
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Mon, 03 May 2021 19:32:50 -0700 (PDT)
To: Jonathan Morton <chromatix99@gmail.com>,
"Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
Cc: tcpm IETF list <tcpm@ietf.org>
References: <cd600644350847ef8415d21588d1e912@hs-esslingen.de>
<085E60F6-B396-4AB2-8BAE-BF615AD51825@gmail.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <675a7c26-bc1a-5cba-a55d-d06998fb0a02@mti-systems.com>
Date: Mon, 3 May 2021 22:32:47 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <085E60F6-B396-4AB2-8BAE-BF615AD51825@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/WMscWf93FHxUCbWFn0ny64lVvWo>
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, 04 May 2021 02:33:00 -0000
On 2/16/2021 4:40 AM, Jonathan Morton wrote: >> 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. ACK. This is now labelled as "MAY-18".
- [tcpm] 793bis ready to go? Scharf, Michael
- Re: [tcpm] 793bis ready to go? Yuchung Cheng
- Re: [tcpm] 793bis ready to go? Praveen Balasubramanian
- Re: [tcpm] 793bis ready to go? Neal Cardwell
- Re: [tcpm] 793bis ready to go? Michael Tuexen
- Re: [tcpm] 793bis ready to go? Martin Duke
- [tcpm] meaning of "idle" for TCP Keep-Alives (was… Neal Cardwell
- Re: [tcpm] 793bis ready to go? Scharf, Michael
- Re: [tcpm] meaning of "idle" for TCP Keep-Alives … Scharf, Michael
- Re: [tcpm] 793bis ready to go? Jonathan Morton
- Re: [tcpm] meaning of "idle" for TCP Keep-Alives … Scheffenegger, Richard
- Re: [tcpm] 793bis ready to go? Markku Kojo
- Re: [tcpm] 793bis ready to go? Scheffenegger, Richard
- Re: [tcpm] 793bis ready to go? tuexen
- Re: [tcpm] 793bis ready to go? Joseph Touch
- Re: [tcpm] 793bis ready to go? Michael Tuexen
- Re: [tcpm] 793bis ready to go? Scheffenegger, Richard
- Re: [tcpm] 793bis ready to go? Michael Tuexen
- Re: [tcpm] 793bis ready to go? Joseph Touch
- Re: [tcpm] 793bis ready to go? Michael Tuexen
- Re: [tcpm] 793bis ready to go? Joe Touch
- Re: [tcpm] 793bis ready to go? Scheffenegger, Richard
- Re: [tcpm] 793bis ready to go? Wesley Eddy
- Re: [tcpm] 793bis ready to go? Wesley Eddy
- Re: [tcpm] 793bis ready to go? Wesley Eddy
- Re: [tcpm] 793bis ready to go? Wesley Eddy
- Re: [tcpm] 793bis ready to go? Wesley Eddy
- Re: [tcpm] 793bis ready to go? Yuchung Cheng