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

<Ruediger.Geib@telekom.de> Fri, 15 November 2019 09:26 UTC

Return-Path: <Ruediger.Geib@telekom.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 21557120164 for <tsvwg@ietfa.amsl.com>; Fri, 15 Nov 2019 01:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 1fSEUJTo-9S1 for <tsvwg@ietfa.amsl.com>; Fri, 15 Nov 2019 01:26:57 -0800 (PST)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78B30120090 for <tsvwg@ietf.org>; Fri, 15 Nov 2019 01:26:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1573809687; x=1605345687; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=RNIWOh/MRxug5mqTd+XX4K4QH2HCog/vu+YTAya4vuQ=; b=JrIrX+DmWJhGNomtisQ9bBv10vwCbZ+RTzuPX3EJt318H0B9yqcAtjQe MRB1wEljJzKyR7yk96oRnOLHLSBlTXx1KOFOv+U2RMIj/4eoUvjUqcd/U C0cpwsW/GtJPa7fHls0W2hzejy00Y/YJICFII6cx1AEFU4tIl/9Vu6x6b UCNOVFNpW5DtYPXauWEWwNB5CGyrGHQ7CC/fRCOvpv2xjDqtBM+1HozQ0 EGG+I7lS9lFRqBAnLaBDO3ATScPFjCWONg/knqrANBkC40jSC7AQGs1Tv 2rWqjrJ++EnUCDwc6uktd7l6s1g0uDavyfQ87s935VNqVqp9waje8nOKD Q==;
IronPort-SDR: G+BBbuqmD/IgdrtyD3PGBlUPTUSCEYmJOl0PLjhT9lVw+hnBAcj4KNBP1FGaJmnd89NctF+HPk 0AXM03+0FGHA==
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Nov 2019 10:21:20 +0100
X-IronPort-AV: E=Sophos;i="5.68,307,1569276000"; d="scan'208";a="188940917"
X-MGA-submission: MDFwkgIpzj1W65R5SZudLvQnOWS6NEbHxSc9reww8bpkUoWiyM6/ifiO/k9jZL2g7hNZrp7mdi1AzGOYz0KPjCA/qsN/N8A45TdrL3nyb++u7WQckFkpewZuSdAylqdi0wkb/QWj++EcVzmutf1a+AmzOKu0Vec/CuzVH8Cgi5C3zw==
Received: from he105867.emea1.cds.t-internal.com ([10.169.119.44]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES256-SHA; 15 Nov 2019 10:26:48 +0100
Received: from HE199743.EMEA1.cds.t-internal.com (10.169.119.51) by HE105867.emea1.cds.t-internal.com (10.169.119.44) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 15 Nov 2019 10:26:40 +0100
Received: from HE104162.emea1.cds.t-internal.com (10.171.40.37) by HE199743.EMEA1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 15 Nov 2019 10:26:41 +0100
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.23) by O365mail04.telekom.de (172.30.0.231) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 15 Nov 2019 10:26:41 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iCKBQuPY8q2YikP9lJdXqwzPvrWeVmKZa8blwQu9xXi6b8mEFl7AelJbPO/GQEv9x5ez2ZUKuqvmmiCDyJOfBp01V36E6srG1ZDe++jvL1yjajYeNvN54e510kSuY1bxpeTd7o1BfbpmMl4vsX7wBPaPpy7FlA7o6Tlj+YV3MYJbFErUCr9fhscV+XdSLZUdH9j3h0viRCQPh9TNDSove8ilAQychsJD2E/eRMSzdZcBQucYWoav7U53/r1/NLkaouzs29Ecck2eXcxN5tzG/7x7dymv9oMxT7LbVBAdoJSYqmlhawX2yi3O+RUU4zs6T9BMxd17W5jSTxXVLUiBvA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RNIWOh/MRxug5mqTd+XX4K4QH2HCog/vu+YTAya4vuQ=; b=QAVpvQXG4b2gsXzJ1wXXJXwoV8hY49dcqAN1EPInEvVZWZD53x5gglZCVLttTPZiB1dPOVufnj/+6lPxOTGftNAHjvRprbe4YK3Y081AU4XMovv/kawvkoavc50e7UGOOQU2nH5oCjld210QZyZU7wpwj7FxjplDjr1Xm137xWTgMLzwx6apyQkqyQL12v8uuvOMoXHznmxDDBBZczekbSM5nBMMhqK7yfNAH9w48kvzRLyc6+gemOq8FNVv62s+OS+8jjy4zhU+TT++edGXulpfun1Ww5J40FyFF7Bgt/vfsgOt/G36tC7HXUYOqcD6JGlHipfad5CeP01hQWh8xw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from LEXPR01MB1183.DEUPRD01.PROD.OUTLOOK.DE (10.158.163.12) by LEXPR01MB0576.DEUPRD01.PROD.OUTLOOK.DE (10.158.166.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.27; Fri, 15 Nov 2019 09:26:37 +0000
Received: from LEXPR01MB1183.DEUPRD01.PROD.OUTLOOK.DE ([fe80::a1e4:499b:d9d2:b276]) by LEXPR01MB1183.DEUPRD01.PROD.OUTLOOK.DE ([fe80::a1e4:499b:d9d2:b276%5]) with mapi id 15.20.2430.029; Fri, 15 Nov 2019 09:26:37 +0000
From: Ruediger.Geib@telekom.de
To: moeller0@gmx.de, David.Black@dell.com
CC: tsvwg@ietf.org
Thread-Topic: [tsvwg] NQB - which DSCP to recommend?
Thread-Index: AdWbT7q4ff1pYakkSdOAEfQFvOmn0wAP+BAAAAGSpZA=
Date: Fri, 15 Nov 2019 09:26:37 +0000
Message-ID: <LEXPR01MB118358214565EA8E73B929539C700@LEXPR01MB1183.DEUPRD01.PROD.OUTLOOK.DE>
References: <MN2PR19MB404507EBF1C41E72A7930F0F83700@MN2PR19MB4045.namprd19.prod.outlook.com> <F1E4C0CC-EBA1-48B4-AA57-01D179521AEF@gmx.de>
In-Reply-To: <F1E4C0CC-EBA1-48B4-AA57-01D179521AEF@gmx.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Ruediger.Geib@telekom.de;
x-originating-ip: [164.19.4.232]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3bddbc4b-8229-423a-cec6-08d769adea29
x-ms-traffictypediagnostic: LEXPR01MB0576:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <LEXPR01MB057663ED7A82E33B861E39569C700@LEXPR01MB0576.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02229A4115
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(136003)(39860400002)(396003)(346002)(366004)(199004)(189003)(305945005)(14454004)(7736002)(4326008)(86362001)(66476007)(11346002)(446003)(476003)(186003)(26005)(85182001)(486006)(2906002)(110136005)(66446008)(64756008)(66556008)(66574012)(316002)(6306002)(8676002)(33656002)(14444005)(256004)(66066001)(76116006)(85202003)(66946007)(966005)(53546011)(6116002)(7696005)(76176011)(5660300002)(102836004)(71190400001)(81156014)(81166006)(71200400001)(55016002)(9686003)(478600001)(8936002)(3846002)(777600001); DIR:OUT; SFP:1101; SCL:1; SRVR:LEXPR01MB0576; H:LEXPR01MB1183.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FzrVKbOs7S8v21Mp9mzyg+qJcOYvhOomsvLoPy8wyk5E/0KK4v44o/8fBqZ0MRpVtBPf3MY+2i5h385DN0s5+WD1xMFQKJu5e/J31m7SXHvNqewE6JM0senCcgOWkzFffyQ8Ff2DIElQJzksEift09fwvWN5PC+/qslpgdIvPvyKAcK2RpOOQx06nJMBWlRdKbMyNj1/DEYN55kv0HKvO3zrcR8mb+aMzt35I/Gny0AHQuhS3/J5H9Dlss8xCFS2M8nNG0Nv7J8VyLQRPLwXz+1v+8EP/CwFHvt2P5g8vSrl1w4gOeX28hhtnxUOUcXw3JuZ4aV8nXZzJtYB55HxdXw//UyQtLhaeRgEfoC9vK4iT0s+pvgQb3I5R9qqXb2JrmGPnVayp2DpCinqzIhlONvYlxlkk2hf0bmh8DwY3LsR6HRmaWe66XfSnAkBnWHvZNDfJ4YIzBgmA37C40T/FIVJoHcYx6uufWvI1+OV32Y=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3bddbc4b-8229-423a-cec6-08d769adea29
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Nov 2019 09:26:37.3572 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DV948/0dMOCT+jZIMmd6+hjCxbkkqis7UHCoASNLuSKnp77h8BQB0NkTwGw82KRxrUokglRtqm6oB/OYQvYRhqeCDu86zSYhbYso//ihCxI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEXPR01MB0576
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Pk4nBgUP-9B1I4s0biOIIsv-Alc>
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: Fri, 15 Nov 2019 09:26:59 -0000

Hi Sebastian, hi David

I agree with your analysis. I don't object your proposed DSCP. Should there be a desire to circumvent the situation you describe, 000111 (or another spare 000dd1 DSCP) might be an option. As said, proposed only for the case that your suggestion doesn't reach consensus.

Regards,

Ruediger

-----Ursprüngliche Nachricht-----
Von: tsvwg <tsvwg-bounces@ietf.org> Im Auftrag von Sebastian Moeller
Gesendet: Freitag, 15. November 2019 09:35
An: Black, David <David.Black@dell.com>
Cc: tsvwg@ietf.org
Betreff: Re: [tsvwg] NQB - which DSCP to recommend?

Hi David,


> On Nov 15, 2019, at 01:58, Black, David <David.Black@dell.com> wrote:
> 
> Lurking in the lengthy discussion about NQB and existing WiFi is a topic that needs broader WG attention, please.   Sebastian wrote:
>  
> > IMHO the upshot of this should be to
> > 
> > a)  propose a DSCP for the NQB PHB that maps into AC_BE
>  
> The general topic is which DSCP should be the recommended DSCP for the  NQB PHB.  The NQB draft proposes 0x2A, but the WG may choose to select a different DSCP for this purpose.
>  
> Ok, please discuss …

	[SM] I propose to use 0x6 (000110) as DSCP for the NQB PHB on un-charcaterized networks, and to use 0x6A (101110) if the receiving network is known to contain NQB compatible wifi elements (or that network operator requested the re-mapping) as re-mapping to 0x6A (101110) will by default get packets into the desired AC_VI. 

	According to https://datatracker.ietf.org/meeting/99/materials/slides-99-tsvwg-sessb-31measurements-concerning-the-dscp-for-a-le-phb-00 partial bleaching can re-map a few common PHBs into the same DSCP (occurrence of partial bleach reported ~10%). But out of the "common" DSCPs only AF13, AF23, AF33, AF43, and EF carry 110 in their low three bits, and since all of the denote high priority (which partially indicates a request for low latency) this re-mapping does not see catastrophic and it certainly does carry the same cause priority inversion concerns that were relevant in selecting the LE PHB DSCP (https://tools.ietf.org/html/rfc8622). 

	I believe this to be a viable path forward that a) protects unsuspecting wifi networks from unintended side-effects of inceasing the use of AC_VI, yet b) allows ISPs to roll-out APs/wifi-routers equipped to handle NQB in the desired fashion. (By using a construct like hostapd's qos_map NQB-aware APs should even be able to instruct stations to map 0x6 into AC_VI if that should be desired).


Best Regards
	Sebastian


>  
> Thanks, --David
> ----------------------------------------------------------------
> David L. Black, Senior Distinguished Engineer Dell EMC, 176 South St., 
> Hopkinton, MA  01748
> +1 (774) 350-9323 New    Mobile: +1 (978) 394-7754
> David.Black@dell.com
> ----------------------------------------------------------------