Return-Path: <moeller0@gmx.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id A44B7C14F6A7;
	Tue, 21 May 2024 08:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.845
X-Spam-Level: 
X-Spam-Status: No, score=-1.845 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,
	RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001,
	SPF_PASS=-0.001, 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 (2048-bit key)
	header.d=gmx.de
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 9Mw0hrZ6g-V4; Tue, 21 May 2024 08:01:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits)
 server-digest SHA256)
	(No client certificate requested)
	by ietfa.amsl.com (Postfix) with ESMTPS id 3A95EC14F61A;
	Tue, 21 May 2024 08:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de;
	s=s31663417; t=1716303644; x=1716908444; i=moeller0@gmx.de;
	bh=IOFyeLWkvzvLN9vkOyvkjjRGzXDfFrHEDUhDmXtTeio=;
	h=X-UI-Sender-Class:Content-Type:Mime-Version:Subject:From:
	 In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:
	 References:To:cc:content-transfer-encoding:content-type:date:from:
	 message-id:mime-version:reply-to:subject:to;
	b=TItATjbUTP7R6Kd27DRTDNc1H87GBMIFx8kHLizt4kR6op6YY77Q3mPirtWtrNx3
	 YS2Skn111wJwsUZEHk9qqfOgslXtJB+v30Exr50F/5DpeMt6rUXSdBHQJ8XjMZeWg
	 F3NkNAS5/V/D34YGSDj59QE7DL2xuCwraGftJAAYhC/Zo47grun3iq8SJb0iQaRD1
	 yFRO9CNdOQyzvn336j+dqDzZVm6qrptvcGM4yMP1T+MGtfCJYH2YTj1g/OPY01h7x
	 ycntT9PrZWktlntVXBLj+VOU1O99pFBpo0mxE/s1FNrNAKQA5iENDYSJdrZApIunG
	 TPQ5o3RA0gsAICd5dw==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from smtpclient.apple ([134.76.241.253]) by mail.gmx.net (mrgmx004
 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M6Ue3-1sBtob3l61-005r6Q; Tue, 21
 May 2024 17:00:44 +0200
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <3503D2F6-8EB1-4236-B1C8-0FA9459CF4AD@comcast.com>
Date: Tue, 21 May 2024 17:00:34 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B26CE814-2C54-4179-A8D5-5FF6D435C68D@gmx.de>
References: 
 <LV2PR01MB7622AB269736527A859CA8259FE92@LV2PR01MB7622.prod.exchangelabs.com>
 <EF9FC229-2CA8-4809-B554-9F67172F1A25@gmx.de>
 <3503D2F6-8EB1-4236-B1C8-0FA9459CF4AD@comcast.com>
To: "Livingood, Jason" <jason_livingood=40comcast.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.600.62)
X-Provags-ID: V03:K1:4y7RD7IebG57A909ibD7q1Ba0XkkKNKhv0g8kyY/xpLv20L2ReR
 PbJjNHUKc3xkx2hitnmjIq0AB0BR/LEVF5ivuW2wKmKG3uB1/ZmmRdVhhIoD8FWAd6PkeTt
 qRSmFygOgOf64ehbvkFZ3Gf955RPHGxHuvsTSzZFIyw9RcNc7IxIPCH3Uc0hZV9p5WZuQi7
 FJtYs6f+P7eVosjvaDnMg==
UI-OutboundReport: notjunk:1;M01:P0:WZLN5LU4hm4=;6kbmRGmcaTluIqiAp0eQLP8noux
 rxThX8qenqtCZDydiod97oSGU4sR1+SZ8mVQwCJqrTVdXpV1zLbQ0ZSDG3FO7gkFRgW9h5HZS
 rrz29XICKRuwLInG4wF6AddCzH47frISA9lb+4e1734mObu3nLmzw3OZ3FT5n3WBBOQanVUAY
 hH2QCg3Z2TsXk1K8iFpXh6RLlLMu5piD/w80wy+W3uIxf55UdqeMjjXfglEz5QZgVNDBT7Ic6
 R45T5U/FImLPdy3XKoLj10gxmjomVSOCOFXXcwpzAW+S9CpIdieah45QDJAePMIipNR1JvKOT
 Dm9l3zMMQ2et3gEKAd30Uey25tVW4ug/MRY061BQFNqXBxuj4bgeOaoqwpSVbbHNasLEoROo7
 Xo7vmZAzVH/WUviMXw9cMPTF7Q3+Lk558jl/dlHgqBsVa9coiA8qxAmf7NRzCqWc2CeGi65DV
 ET4hiL3zbVfXX16Tm/fz6qyC9UgV3KSHqRrcPh6D1SsJZ0qgtYcPOmgZqV5RegVbvv5aBxVuW
 3hMtuoBtoc0WLpmKupHQbVUdrnPlyTjUtJj0dIwryYVbZKGwLAdxlub8iHVr70g1A/cgHMK9a
 Pz6iNWcgPTGns86pZfQB8G/hC3IhMA9QzYC9WdWETlZhoySUFrmxcTIyPoDm7IYiwFxY3go/p
 Woz+TtRY3R7aqOLTaJC3AauLMb0BxAFIlarCHa5Uo1SMCjquSQl6dzE2cQ/h/JChu4T5OS0z0
 AhUipFEzhk0GaPuKibZiK1zuOJM+u5HRlEahuItJ5OdXZbyxyAgYNEvCxaygdKrqbhqQD1GJu
 Ozxpq7qcibpUtxPpkAp0zu+kasJ5YLwmEwSLy6UA+Ix2I=
Message-ID-Hash: DMTWCNNH2SRXA464PFIBFEXB6P5HCIBU
X-Message-ID-Hash: DMTWCNNH2SRXA464PFIBFEXB6P5HCIBU
X-MailFrom: moeller0@gmx.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0;
 nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size;
 news-moderation; no-subject; digests; suspicious-header
CC: "Overcash, Michael (CCI-Atlanta)" <michael.overcash@cox.com>,
 "tsvwg@ietf.org" <tsvwg@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: =?utf-8?q?=5Btsvwg=5D_Re=3A_WGLC_for_A_NQB_PHB_for_Differentiated_Services_?=
 =?utf-8?q?=28draft-ietf-tsvwg-nqb=29_to_end_27th_May_2024=2E?=
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/tsvwg/rSqx11J5cU-7Nax05nmXkOo6Y44>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>

Hi Jason,


> On 21. May 2024, at 15:57, Livingood, Jason =
<jason_livingood=3D40comcast.com@dmarc.ietf.org> wrote:
>=20
> On 5/21/24, 02:34, "Sebastian Moeller" wrote:
>=20
>> [SM] Could you be a bit more explicit, what exactly did you test, =
what was posiztive and did yu also look for side effects?
>=20
> While you directed this question to Michael, we have tested this as =
well in our field trials. We have for example, tested single queue with =
AQM and looked at p99 latency under load and jitter as well as median & =
max bitrate for different application flows - then turned on NQB LL and =
observed the same for the classic and LL queues. What we have found =
generally is that the bitrates, working latency, and jitter for classic =
traffic with single queue AQM and dual queue LL is the same; classic =
queue applications do not experience degradation.

[SM] Puzzled, how can the bitrate in the C-queue not change when there =
is also quantitative traffic in the L-queue?

> At the same time, the NQB flow experiences working latency that =
approaches idle latency, with consistently low latency.

[SM] Well, we know that priority scheduling does work and will give a =
sufficiently sparse traffic in the priority class shorter delays (and =
more potential throughput)... so that is not all that surprising.
Surprising is that according to your argument that improvement in =
service did not come at a cost for other traffic. And I question that, =
priority scheduling does not magically create more capacity or transmit =
opportunities, for every packet you treat to less delay, some other =
packet(s) will be treated to more delay. We can argue that the amount of =
this additional delay is insignificant, but that is a different claim =
than 'it does not exist' as you seem to be making above.


Regards
	Sebastian

>=20
> JL
>=20
>=20

