From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D98CD3CB37; Tue, 1 Aug 2023 03:51:40 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.de; s=s31663417; t=1690876297; x=1691481097; i=moeller0@gmx.de; bh=Yz37I2ySBuFxM1fk6Iaca7CQyy3GNtXFLs7XodjbiN8=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=s79TwPsUJSaVCIeufTYkGyIvtT1DMU7Ex+oDMJC1PkFWStaT516IRye7p7hXMbsW52Fx4Q7 3Z8okydPOJQ8pzvfm0kg8aq7hHS7v86rd5Ms3nuFL2RJEl62r0aB1AhitwCaMh9yc53RbsXO9 kpmBKUYrRwPSlTTLGmvbf0IN5E/dz2Oj066aHkFFrYUqn/40lszuMq0IGDtW+ZKYPckAp4OYV CC4n8rTyX0fnn+uM88Fblv1eSKyEL09ySRpdSzrDU/iL2qbDb7tPNlyp4RJ/pe2VINuRQSeBe +4g/LJw+EzISDvgtqwcC1BID0AwJod+ME+9oseok0aZOPxk3s8WA== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from smtpclient.apple ([134.76.241.253]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1M3lYB-1qRZNa3IeZ-000xL0; Tue, 01 Aug 2023 09:51:37 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) From: Sebastian Moeller In-Reply-To: <507f856e-486c-87ff-79a3-50eb47683557@uni-tuebingen.de> Date: Tue, 1 Aug 2023 09:51:37 +0200 Cc: =?utf-8?Q?Dave_T=C3=A4ht?= , bloat , codel@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <7FD3B872-7B3E-43E2-BC82-172E50C2C22C@gmx.de> References: <507f856e-486c-87ff-79a3-50eb47683557@uni-tuebingen.de> To: Michael Menth X-Mailer: Apple Mail (2.3696.120.41.1.4) X-Provags-ID: V03:K1:6vKRTRYaw1dwSXgEk6ggetSO2ZeV+exmX51GUFxPgar1fNGu/It pYeIX43LVl9KtnPgO5Sz81ZbEWFDiIlDh1FGplifrCfXbzN4Mz6kNCIvfucPPWy9JWMG+gX C1Uv4wQsuaz0M5P8DbfSMO06hBU5tb2K2cLuIC9wcq3Wyv5Dy6fS/AvOrG2N1MoIRwYd8V1 pKueU1lUhGceqdDx/H9FA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:22aSkaEET0U=;dKjDcIE6ZqTOWdQM0wqq/eAfo4K ER6UznJ1MSTm7wmjL/zehIWfh09qtQM2DYwH565zQBM8XDq6vXuOCiTv+QkZ3c6EwPHJ6mmvX j8il8qD2+Qutd93eGSGnlbopzKQ5aFuhRN2GqzaGkjHbrJbwF6qoHO1gBeaegBZfRaiAsChK6 BsAqbo7UpyTfwKtMAqZz8CskT46IulOT/ewRpNnNInVlOtw6DrSL2pVreRl3+tttli1576KSh G7c76Ct56Cz/hlcUSf6MRCcgmcAmm9QyKzHJotF0XssJBg12yXv39vKS2ifxhMEuFePL6sf2s p3FafkD+w11oQh/fR42DPqdm3osNKGYxY81QP5BdNm9NZRBh/BruGiMFN7Yse9TlVXko0gQFQ 9Aa2VZBW6pdK9gRYqEXKMsLDYgEmB+Bvm7VpauREhHl09tYMZVnaBI+5iVjkYSdwrt7CE1APS B43phcKy4Ob/Eq0rjO3T2oeb1Xt+5CsI5v42M9ubq5Z/f76onBGnt7wmpGPT9+vioVVtEy2GF Wvq97srCjWDxSaSm2aAv3TvdRVexSolF2Rq66cmgp8i6FvEqKTBEedYJ7OptYmIdtvx5hCiRk CjzzabZPgpgcrbmvWcltFXocYk6bnLcSRWZxRusV3JPVomUJZnbvoZHSvdV8BY7+dAw24JYgd KA4HAy+vrLWxWILjFpP8NxudUX9K4/g5bjDHFN+D0AjCPbVfVjQEGhnhRAmLkwMzQLv6/zX10 BqV/HcQFRun//uXKCbNTQvQvaGj+MK2T7V+Vgim+UX4BDBZgz04dm6KWBapEFpGYvAMaX4AJv kNUQmRS2tEGsQw6jy3SvzedVD4dzEMsD21FcPDGMPKdtUq8dr+tF2gZXaEeHG/5akkRR9aOOo z5yqLLquJDTKZXi2JCqNEGpMUydhKueZ74oUSXcLwr1moAVAemRET5cXyWwirWu3wVXZN96NX 9qLCMioVivcAg4Iwkar6R3JUIsw= Subject: Re: [Codel] [Bloat] Another passive bandwidth estimation method X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2023 07:51:41 -0000 Hi Michael, that "teaser" you wrote is certainly interesting. Would you be able to = distribute author copies to those of us that do not subscribe to = IEEExplore, please? Regards Sebastian > On Aug 1, 2023, at 09:32, Michael Menth via Bloat = wrote: >=20 > Hi all, >=20 > we've recently developed a passive method for finding a link's = capacity (in a different context). You find the algorithm in III.B.5 in > https://ieeexplore.ieee.org/document/9954450 > The approach ist tested in V.B for 1, 10, and 100 Gb/s links on a = Linux server and provides sufficiently accurate results for bandwidth = utilizations of 25%. The method is likely to work also for lower = utilizations, but this was not an issue in this work. The method is = applicable only by a link's head-end node. It does not work for end = systems to find the bottleneck bandwidth on some unknown intermediate = node. However, it can deliver useful information for scheduling = algorithms in forwarding nodes, which is the use case in this paper, and = which may be of interest to some readers on this list. >=20 > Kind regards >=20 > Michael >=20 >=20 > Am 01.08.2023 um 00:36 schrieb Dave Taht via Bloat: >> Promising approach: >>=20 >> https://ieeexplore.ieee.org/document/10188775 >=20 > --=20 > Prof. Dr. habil. Michael Menth > University of Tuebingen > Faculty of Science > Department of Computer Science > Chair of Communication Networks > Sand 13, 72076 Tuebingen, Germany > phone: (+49)-7071/29-70505 > fax: (+49)-7071/29-5220 > mailto:menth@uni-tuebingen.de > http://kn.inf.uni-tuebingen.de >=20 > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat