[tsvwg] Re: WGLC for A NQB PHB for Differentiated Services (draft-ietf-tsvwg-nqb) to end 27th May 2024.

Sebastian Moeller <moeller0@gmx.de> Tue, 21 May 2024 14:53 UTC

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 602EEC14F6E9; Tue, 21 May 2024 07:53:59 -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 pvVT4Mnl9xHL; Tue, 21 May 2024 07:53:54 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 DF4AFC14F603; Tue, 21 May 2024 07:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1716303232; x=1716908032; i=moeller0@gmx.de; bh=v3QiIvfe4titZPthc5kPaJ28dYMaeN/7tVn/ylLl0Nk=; 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=d3e+vchfyFh+zO+4UP13kJiBJXYqpYMCqV6mvEwYrRcXvOghY2bRaLK9ZbhN7QCF e1fwaa67u+JnYs/fRjdbyCXfoKCAGxnM7mm1l9NSR7y2Z7GZbACQvxvrn3oe9oxxO zi9AI316OZ9lhzxJsucYVfyN8YGb21UVDyiXn8kOfUGvmmTMWoNrL+XL4icaiwnco rF15cI2grcTYv2w6nTv/5Zpd8vymek7Dz8QgGsVwttA033V/R7J3tKjYLWAAjvscO bB8fJCIar4v0a0OAFSEqou7r/1skNlFNe6r1owey+Y2jyAv2diEOwhNHKr1eaKtmP a2bPDFvsnm/ilECsOA==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from smtpclient.apple ([134.76.241.253]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MbAh0-1sgIie0LPc-00bYhG; Tue, 21 May 2024 16:53:52 +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: <68972F81-7CAB-4EAE-99F5-943E1B9BFDE1@comcast.com>
Date: Tue, 21 May 2024 16:53:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CACACDAA-0B1C-40B9-A21C-F95783AEF618@gmx.de>
References: <8ca36c0a-bcc6-4bf0-86c4-8eb7f87c11fb@erg.abdn.ac.uk> <D01D1924-A72E-423A-B2F8-A797268A9B6A@comcast.com> <032C28F3-1C6E-487D-A462-12427A78ADDA@gmx.de> <68972F81-7CAB-4EAE-99F5-943E1B9BFDE1@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:BrrbpTGxVNzfkRHlfa8LGDYgsElmZvGpZfFxTKWm3lVS8urF9aE OhhPPed1KnocAssW6n3BlMxU1wv11BE0K/zLl1rvRJTC8zr/bf6Q++lsyE7byt0fLYyKw/S dGa0DnR8DarrBwvRbBsc+ODs0xAUWyKwOqgP2ZIYwnNApdUCCH6K3PB7RNRuu0TzdumgjdS dRsV2QFUYkOTpgqDE6Brw==
UI-OutboundReport: notjunk:1;M01:P0:2s3xmfncMnA=;3L9bQ/Mz7b0bofqJGirB550rqbn 9bqwt6ttuEKX/OTk+n6Dz5k46JZ+cgs24qG4p9kcpQYUY7erm2QzDNzhZ3bcAepr/CnkF5Ih8 h4tx2FofcQWIz6YK1W6nuO6vP++Qf6GpMS4N5o2NroH+NQ3rIzXBThiUNILMQNSll6fuGHqnq NP2x/465+aVCLNWhprVCTWxqyd/dJYINRPB03nWeZCBMBbNQ8kY8wZSfmh4UbGnKDUMzAA0e4 Cl7HGW0cFyDv/Kk23cGu8ooPeGeIlw4SMED3V5AiaYIpE56nUzSG/HTQengjB0x+GIYkQgKQ5 TAM0B6ezfnFn/EFbKsE+9+xefeN9p9pzlOY/dzgydDCrLAXvdqBZz5AXCDmEldg28fF4ZSJpj QAf+haG8GhykTzcuK2CCSUzgXPUCS9mLMHD0pvmv/g6ketcYX1SfV2B8L4P4ZIxv9J4EPqvP2 tQk7w4ELnAph6Gdv/XFxYUlv5hiEuUCFT3Onc4uCVOGVMeosE0B1d6f45J6PklangfPYlOAWo kkFkBm2XjJHwQ4FQogwhPuqk6ei2ztFqDtHJSoNTpEhJZLODY82vBVFVHk+lnws2wECkJryBc H4WKXJXZC6Uyv0KH0KZdimz/FhLacnFVFt75t7ONNLVrDzek3XsB+nWfYwTf1opvmNytJdw65 PzUNFugMVkCba1LV+Vd+3dwhFGtfeYtxFk25zA6R6G6rJMA0NeN5NUNtwyZ1ytnhVVFg+86dv A2oLSpv0la+Q266QFlX2bpGmZWLMRliAmhGCuxCkuZRXMfadKn22jj3Hg0bMAwi7P7HLwCy8W ly2mt2hREGfrsl4PFaKXEzK7qPW5mvTij4pMzsJMUX+/k=
Message-ID-Hash: EKXP54OUHFIEDDSKJWXXTUWDFU4IAJRY
X-Message-ID-Hash: EKXP54OUHFIEDDSKJWXXTUWDFU4IAJRY
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: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tsvwg] Re: WGLC for A NQB PHB for Differentiated Services (draft-ietf-tsvwg-nqb) to end 27th May 2024.
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/nplgHAVJ71EPJyTT57urPTsBFbE>
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:53, Livingood, Jason <jason_livingood=40comcast.com@dmarc.ietf.org> wrote:
> 
> On 5/21/24, 02:30, "Sebastian Moeller" wrote:
> 
>> [SM] Respectfully, how did you assess the potential harm done by using AC_VI to other traffic (e.g. other APs/SSIDs sharing the same channel)? If you relied on traffic shaping ingress NQB traffic at the CMTS/CPE level how did you assert that the NQB traffic did not exceed its acceptable share of the (variable) capacity/airtime of the WiFi link?
> 
> Comcast operates one of the world's largest Wi-Fi networks and we have extensive Wi-Fi labs and field testing programs. Separate from our low latency program, we have for some time tested the effects of user-directed per-device and app-based per-flow WMM priority. We certainly do focus on adjacent AP, as this is especially critical in the many multi-dwelling units (apartment buildings and the like) in which we operate. We have not observed any performance problems in such testing.

[SM] So you can remotely monitor the fraction of airtime in a channel used up by the different UP/ACs for the own SSID as well as SSID/Ps in the neighbourhood? Impressive!

> 
> In addition, many commercially available consumer routers and AP systems already offer similar prioritization for many years and I have not heard complaints in the marketplace about this (e.g., 'my neighbor is using a gaming AP and now my WiFi network doesn't work').  

[SM] That sounds like  the "but dad, the other kids do it too" defence members of my family sometimes try to employ... Not an acceptable excuse IMHO, e.g. when D-Link routers abused/overload public NTP servers, that was something worth fixing and not something for everybody else to emulate.

Actually diagnosing that "bad WiFi" is caused by some neighbour/station hogging inappropriate amounts of airtime/transmit opportunities due to using AC_VO or AC_VO is hard, let alone for normal users. At least that is my experience as a normal user. E.g. how would I even know that my neighbour uses a gaming router? 
Not getting such reports is not the strongest evidence for the absence of the underlaying issue.


Regards
	Sebastian


> 
> JL
>