From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
Received: from faui40.informatik.uni-erlangen.de
 (faui40.informatik.uni-erlangen.de [131.188.34.40])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 26C033CB37
 for <rpm@lists.bufferbloat.net>; Mon, 31 Jan 2022 10:27:40 -0500 (EST)
Received: from faui48e.informatik.uni-erlangen.de
 (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits))
 (No client certificate requested)
 by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id A7DC158C4B0
 for <rpm@lists.bufferbloat.net>; Mon, 31 Jan 2022 16:27:36 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463)
 id 9BB094EA503; Mon, 31 Jan 2022 16:27:36 +0100 (CET)
Date: Mon, 31 Jan 2022 16:27:36 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: rpm@lists.bufferbloat.net
Message-ID: <Yff/6L3gS4+qgOlx@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Spam-Status: No, score=0.9 required=5.0
 tests=HEADER_FROM_DIFFERENT_DOMAINS=0.248,RCVD_IN_DNSWL_NONE=-0.0001,
 SPF_HELO_NONE=0.001,SPF_NEUTRAL=0.652,T_SCC_BODY_TEXT_LINE=-0.01
 autolearn=disabled version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 faui40.informatik.uni-erlangen.de
Subject: [Rpm] Test procedures for TCP stacks ?
X-BeenThere: rpm@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: revolutions per minute - a new metric for measuring responsiveness
 <rpm.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/rpm>,
 <mailto:rpm-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/rpm>
List-Post: <mailto:rpm@lists.bufferbloat.net>
List-Help: <mailto:rpm-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/rpm>,
 <mailto:rpm-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Mon, 31 Jan 2022 15:27:40 -0000

Are thre any well defined (RFC or the like) test procedures for the "quality"
of TCP stacks ? I am especially thinking about measuring how good the
TCP stack behaves in the face of various path problems. Latency, loss,
reorder,.

Related:

How big a difference between goodput and throughput would one be able to
see anyhow between worst... best TCP stacks ?

Thanks!
    Toerless