Re: [tsvwg] NQB - which DSCP to recommend?

Jonathan Morton <chromatix99@gmail.com> Sun, 17 November 2019 01:51 UTC

Return-Path: <chromatix99@gmail.com>
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 3566912011F for <tsvwg@ietfa.amsl.com>; Sat, 16 Nov 2019 17:51:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 IB0Q2Gwkq00y for <tsvwg@ietfa.amsl.com>; Sat, 16 Nov 2019 17:51:31 -0800 (PST)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 039C4120041 for <tsvwg@ietf.org>; Sat, 16 Nov 2019 17:51:31 -0800 (PST)
Received: by mail-pl1-x636.google.com with SMTP id h13so7455265plr.1 for <tsvwg@ietf.org>; Sat, 16 Nov 2019 17:51:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LcY3v/K4LTnlzm1pyv4pSU9fVAQF2PLLFza5pFvCqcQ=; b=MG0hV4ZH1gS3FuIGhLlGng5B40E06rs0kBvT/EHDbBiUBVVy/T+kayY1Be3Ayn1tB1 bk2ylWVd1YSiWvtBefi6myKiIcp5w8PC54FLO1H9R2E1OUDJgUHtNTjKpgI3D/IjFkCK lmwslKCSDaRMfDMWcFE+lbP3IU2pj5SozWMTKekrj3fodlVuRGfel//vBqj8xGA5J0cr o7NR54e/Q9PAP4+ai77jdz+2l5Dr2Lc/D8v4L/txg3UV5T1RvtcpqmFV5so9xJ5ThwbE By7ZEr5Pg5EpiQaKWNcN2OXIm8FOH6oqbh6YDUeXfLoRgEShuhCA5FIXyeKLaFrWk9sW vnPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LcY3v/K4LTnlzm1pyv4pSU9fVAQF2PLLFza5pFvCqcQ=; b=MWanwkmDYT7yxCqSrR9z+fgnLHbLxmPWi1RADBn5BvsAhrFxgCnHiD9xut7VnzwSXu J3s032XCF5QlbSoi+v8esg8V4OrsKTW4d6pUs/YKkCBKIKdNQkJQRMl1AJPZMYbuRQxD QDb2cmKsPd9CeQ8ZpeMVEDHNlqiA3T1rDdRnZdZwpPNpM7lIipB3aFDjksz2/H2Ewj1p ohdk5CEAZNpb/r17jdOL+/6L+W6FyFphsoBchGaekEixJm2T3Gd7uis7U1p8vIGAU7l3 o3sixs9cAEDHumykbDYXF8s/DkJujdes8CsbSXrdq9sZG5PoE7AJNW/3bmTKraCXKraS G1mA==
X-Gm-Message-State: APjAAAUOJQw/QZu6wIHY1jHwondCf9sLaa7VnxP8nGKwsKknNKlr74MU rbf1mPPnk6UA4llOxNDbdN4nEZ2X
X-Google-Smtp-Source: APXvYqxW9oGmsCd8MvzOwbdaBR/3SiVqoERBedJu3Dsv8NSogU46dskxC4rFURv+MrJApAlpwF42Qg==
X-Received: by 2002:a17:902:b097:: with SMTP id p23mr22484891plr.92.1573955490314; Sat, 16 Nov 2019 17:51:30 -0800 (PST)
Received: from jonathartonsmbp.lan ([182.55.197.52]) by smtp.gmail.com with ESMTPSA id p18sm15658892pff.9.2019.11.16.17.51.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 16 Nov 2019 17:51:29 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <7EB6C87B-590C-449C-8DE4-BE6705E2C758@gmx.de>
Date: Sun, 17 Nov 2019 09:51:27 +0800
Cc: Greg White <g.white@CableLabs.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1A76CC9-A532-49C8-A768-3014E81282AD@gmail.com>
References: <MN2PR19MB404507EBF1C41E72A7930F0F83700@MN2PR19MB4045.namprd19.prod.outlook.com> <F1E4C0CC-EBA1-48B4-AA57-01D179521AEF@gmx.de> <LEXPR01MB118358214565EA8E73B929539C700@LEXPR01MB1183.DEUPRD01.PROD.OUTLOOK.DE> <A9E69EC8-1F4C-4A75-A0AF-7E51545703F9@cablelabs.com> <7EB6C87B-590C-449C-8DE4-BE6705E2C758@gmx.de>
To: Sebastian Moeller <moeller0@gmx.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/3qb8lE4sEPLlLGPOQJW0AJxHsQE>
Subject: Re: [tsvwg] NQB - which DSCP to recommend?
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Nov 2019 01:51:32 -0000

> On 16 Nov, 2019, at 11:27 pm, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> to cut though too many words and detailed arguments, the choice before us seems ultimately between:
> 
> A) a DSCP that will give NQB precedence on most existing wifi networks out there, like Greg's0x2A, on the hope that this will have no/little negative side-effects, but maximizing the number of users/networks that potentially can enjoy NQB's promise of low latency over wifi networks.
> 
> B) a DSCP that will map NQB into AC_BE and hence will not give NQB precedence over "normal traffic" by default, like my proposed 0x6, knowing that there will be no side-effects, but limiting the number of users seeing the "full potential" of the NQB PHB over wifi.
> 
> So it is effectively a decision between potential gain and risk. 
> IMHO the risk is substantial and easily confirmed in the lab (run flent's rrul_cs8 test through an WMM AP and see the higher AC's dominate AC_BE) but hard to diagnose in the field, while the gain is mostly based on lab experiments and not guaranteed to to actually work as designed out in the real world (at least I have not seen any published data). 
> 	So I vote for B), it does not necessarily be 0x6, as long as it by default stays in AC_BE. So Jeromes proposal of placing NQB "into CS3" is just as acceptable to me. 

I agree with Sebastian here.

To put a finer point on the argument, note that the negative effects on wifi performance are most likely to be noticeable to close *neighbours* of each subscriber using NQB traffic, if the latter falls into AC_VI.  This is simply due to the way that the wifi MAC contends for the shared RF medium.  This is technically known as an "externalised risk", and is something the IETF should be very concerned with avoiding.

 - Jonathan Morton