Re: [tsvwg] draft-ietf-tsvwg-nqb, more questions

Greg White <g.white@CableLabs.com> Thu, 07 November 2019 21:12 UTC

Return-Path: <g.white@CableLabs.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 656E51209C9 for <tsvwg@ietfa.amsl.com>; Thu, 7 Nov 2019 13:12:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cablelabs.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 TicPzyckG1pb for <tsvwg@ietfa.amsl.com>; Thu, 7 Nov 2019 13:12:05 -0800 (PST)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-eopbgr790137.outbound.protection.outlook.com [40.107.79.137]) (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 308E012089B for <tsvwg@ietf.org>; Thu, 7 Nov 2019 13:12:03 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FVRm6XrYJX3/Zfr8/i1jMXB82St/q2lle7j6Up4ECr3t/4/yc326eZKrCiOf/Dom5gFPtSn47JfnIt+ATDTwUNlBGY5ORhqBqiyU7twdxcMfPHA5pFKmwEQizwCxJlzmpkGVaq2q/ak9Hy6Bg7Oet81bZhzvw9WKe/HFz3EF5On+M1MQB3npxCvA6nA6dnbxyF1UbAYfKt8eWtlnutftyOuyK7n8ymfiMMBixaBXIcwe2pF7ymNCdLNyrzY0vHigu0jx8zyAvCM6XORxHFXuZPsMcPloXwlTI5IZO/Iwxkwwq++XvXy/GWQqf1vDBDi07S7vd0fbWbq7j7Ty2J0rMQ==
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=bXMcSjlkXiwAoLd6zz42cKgBwleu3rwW7N7gnf283Qw=; b=PEk0Neh8atTbapF6y/xu+6y5mWz1EVrbpHZzUWD9gyfqcVapBmUqD3/Y1SGyyn7j4ggYlM6Iog/+wSqVqV3iaWdKYs6AyMek0abPXPKz8ZqILA6hpu++57M+dIaaY+fucm/dyPj2DGKgWgsUivUY7IUpDp6TJPwisHytuA0Rg0D8B5kUFjQWpdwFJu9ybaSfbXbu2/Q69CeM08GMfUUx6LnH7RKahHfmcBu0TFsmdVuAhznST3IRuzfVaGVZgSLjyhTQK67erBaCGE6wrNbzsZtUJEVMCR5nAzlMTNoxAHChtOKt4NAybsrQMcbdUxLSOEh5PO9tyRH7VrwtYo2AJA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cablelabs.com; dmarc=pass action=none header.from=cablelabs.com; dkim=pass header.d=cablelabs.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bXMcSjlkXiwAoLd6zz42cKgBwleu3rwW7N7gnf283Qw=; b=Ti/T3IayL9+FGC+Ti5Fnz8f+N8lpi74vbape8SMaihBF2D2c/KSMKG+v7Yg+Hrj16xGZgyjREDh5VEZjZ6kFpiKzo3p7CU3hm9C17twD3x+4NAo6eqoO7F8BvgiY/mxlDSXxP/e3sL7enfgZdzmg/4xh6E014YAy7YzbvaTsaBM=
Received: from SN6PR06MB4655.namprd06.prod.outlook.com (52.135.117.85) by SN6PR06MB4799.namprd06.prod.outlook.com (52.135.120.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.22; Thu, 7 Nov 2019 21:12:00 +0000
Received: from SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::cd06:3025:a8a3:f4bd]) by SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::cd06:3025:a8a3:f4bd%6]) with mapi id 15.20.2408.024; Thu, 7 Nov 2019 21:12:00 +0000
From: Greg White <g.white@CableLabs.com>
To: Sebastian Moeller <moeller0@gmx.de>
CC: tsvwg IETF list <tsvwg@ietf.org>
Thread-Topic: [tsvwg] draft-ietf-tsvwg-nqb, more questions
Thread-Index: AQHVk165eBM5r7+4T0OsGmssaWIedad7Q86AgAED3YCAA3w6gA==
Date: Thu, 7 Nov 2019 21:11:59 +0000
Message-ID: <FA5AC140-F5AA-410B-8067-1B042868049A@cablelabs.com>
References: <90ED003C-CC25-4ED4-90D8-BA572E39D852@gmx.de> <AC0FF00A-9AA7-4582-8F96-1E4E27AEB8D8@cablelabs.com> <20DE8A61-AD71-4C60-A90E-1CCB22E3C6BE@gmx.de>
In-Reply-To: <20DE8A61-AD71-4C60-A90E-1CCB22E3C6BE@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190812
authentication-results: spf=none (sender IP is ) smtp.mailfrom=g.white@CableLabs.com;
x-originating-ip: [2620:0:2b10:22:5c19:5b7e:b5ef:db9a]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5f8541bd-269e-4ddf-5331-08d763c72116
x-ms-traffictypediagnostic: SN6PR06MB4799:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <SN6PR06MB479905F55FD56B8DD6CF27E0EE780@SN6PR06MB4799.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-forefront-prvs: 0214EB3F68
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39840400004)(366004)(136003)(346002)(396003)(376002)(199004)(189003)(52314003)(6486002)(186003)(14444005)(8676002)(36756003)(8936002)(81156014)(76116006)(91956017)(966005)(256004)(478600001)(58126008)(229853002)(86362001)(46003)(99286004)(64756008)(66446008)(66556008)(66476007)(66946007)(486006)(2616005)(25786009)(476003)(2906002)(81166006)(446003)(305945005)(6116002)(102836004)(11346002)(6246003)(7736002)(4326008)(66574012)(6916009)(316002)(6436002)(76176011)(71200400001)(14454004)(71190400001)(561944003)(6512007)(6506007)(53546011)(6306002)(33656002)(5660300002)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB4799; H:SN6PR06MB4655.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: CableLabs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 95ftg9+3wjPn8onJgepaKx9ivS5UD0bO1myPJWl88i4HV6ScgxyizTKiJKYrOkhaEPYZM3hUVYs+8q57V91ok9xOLGRXTq1hEATgVA0b9qDlVYL63jRBRgaoCqzGwkcqUa5b/q6oNWhfZnlozBhmqAttAI2ag65Q9DDP3dEhVWYQJpI4J7LCws57yMh89AZELd+QNzko4HFdPilWaLiTCHAc8xQEF/E+mQ/dMVHLU/xcLo/Wv07Mhoa7WQ/MPLMkicJnd7PW+PvEnV3yhon1bOcFma8eY7qikHua3TaaPTcwtaDDWsWNtUOHw1Gpf+5k+iHGlz60kg+uruDl5dRJOt7lmF81msc3Xv+31PT++bF6QH2C8mbjq/T/tLZa1rywe8eSX7dO0CF0efEl+lzT5Rc8vm0Jjv85jvk+ZHMB29qhqTBk/zqnUpdQV+DZcBHM/p+f7sXWv+Cv31jGQ9I9U35hZ0BM82PgXECmC41uaSM=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <EFA1483FE7218C4CABB142BC25FA598F@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5f8541bd-269e-4ddf-5331-08d763c72116
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Nov 2019 21:11:59.9958 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 6Jyt3I7+OZThtmF0wcOeEGkdIQNfb09i2qEap3wjVYhI/g1Tpav0zYsfKwrXqGBY3VDS/gZczCrACMyNmo5OAQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB4799
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/eTIzDDvayGaCCck14Fa_WhGVk84>
Subject: Re: [tsvwg] draft-ietf-tsvwg-nqb, more questions
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: Thu, 07 Nov 2019 21:12:12 -0000

Sebastian,

In the interest of moving this forward and not going in circles, I think you summarized your position as: "To be explicit, I do not object on principle to using AC_VI or even AC_VO as long as this does not eat significantly into the tx_ops for AC_BE, the current draft improves  in that direction. Would it be possible to make this point even stronger?"  

In my view, as long as the applications that we're recommending to be marked NQB are no more bandwidth intensive than video conferencing (the applications that the IETF already recommends be marked with a DSCP that maps to AC_VI), then we have achieved what is needed.  Do you agree?

-Greg





´╗┐On 11/5/19, 1:58 AM, "Sebastian Moeller" <moeller0@gmx.de> wrote:

    Hi Greg,
    
    
    > On Nov 5, 2019, at 01:28, Greg White <g.white@CableLabs.com> wrote:
    > 
    > Hi Sebastian,
    > 
    > Interoperability with existing WiFi equipment is an important aspect, since WiFi latency can be considerable. By default, many existing APs only support 4 priority queues, and thus it is not possible to meet all of the requirements of the NQB PHB (at least in this default configuration).
    
    	[SM] I agree the question is how to deal with that "impedance mismatch".
    
    >  Nonetheless, it is possible to utilize two of the four queues in order to meet some of the requirements, and thus provide some of the benefits of the NQB PHB.  
    
    	[SM] Unless you opt for selecting AC_BK for the NQB traffic, for most users the value of NQB will be mostly in the priority boost on wifi and the resulting air-time access advantage (which results in both lower latency and potentially higher bandwidth).
    
    > With proper configuration and/or policies, this can be done safely.  
    
    	[SM] Sure, I am concerned about the status quo wich does not entail "proper configuration and/or policies", and hence I believe the NQB special treatment on WIFI should be opt-in and not "opt-out" (in quotes as most endusers will not be able to opt-out). For thid reaon I believe that the proposal to use a code point that by default is mapped to AC_BK is the only correct solution (as a bonus it seems that such a code point also has a better chance to survive transit over the internet). NQB-aware APs then simply treat that NQB-codepoint however they want. If for example a priority boost is desired such an AP can easily implement the required rate-limiting so that AC_BE traffic does not get starved out. In short, I fully agree that special treatment requires "proper configuration and/or policies" and the desirable strategy if that can not guaranteed should be "do no harm".
    
    > The final SHOULD is intended to address your concern about prioritization (since it results in segregation without prioritization).
    
    	[SM] Ah, in that case the AP needs to be be NQB aware anyway, would it then not be better to use an appropriate scheduler/AQM in front of the AC_BE queue and keep all traffic in the same priority class? The disadvantage of setting AC_VI to the same EDCA values as AC_BE is then that applicatons that expect an airtime access boost from using AC_VI will not get it any more (not necessarily a deal-breaker but certainly unexpected enough to merit clear communication of that side-effect).
    
    > Absent this requirement (or the ability to comply with it operationally), the operator would need to consider (and perhaps limit) which applications are allowed to be marked as NQB.  This aspect isn't discussed in the draft, but I will add it based on your input.
    
    	[SM] Great! I would guess the safest would be to have the NQB-aware scheduler in an AP apply some (proportional) rate-limiting if NQB traffic is getting preferential air-time access.
    
    > 
    > Network operators understand the value of segregating NQB traffic on WiFi links, and will almost certainly select a DSCP in practice that achieves that goal.  
    
    	[SM] That is exactly part of my concern with the default mapping to AC_VI approach, I expect that very quickly a lot of traffic will utilize the AC_VI queue potentially starving normal AC_BE traffic in the process.
    
    > Assigning a different DSCP in this draft would do nothing to prevent them from doing so.
     
    	[SM] Sure, but is that really a good justification for proposing a DSCP with known side-effects? As far as I am concerned an RFC should propose sane defaults and hope for the best.
    
    >  Instead, what we need to do is clearly articulate how to make best use of the existing WiFi tools, and how to avoid conflicts. 
    
    	[SM] I believe the last two are mutually exclusive...
    
    > 
    > In existing RFCs, the IETF already recommends that video conferencing applications mark their traffic as either AF4x or CS4, all of which get mapped to AC_VI.  The remaining language in the NQB draft describes sparser flows than these.
    
    	[SM] as an implementer I read "relatively low data rates", without further guidance I have very little intuition what to use as reference. Could this be made more explicit? This is orthogonal to the question whether such a limit should be enforced in any way, here the question really is about getting a feel what is considered acceptable for NQB treatment.
    
    > 
    > Based on your comments, I attempted to remove all text that could be interpreted as recommending that high-data-rate traffic be marked NQB.  
    
    	[SM] Thanks, as long as the aggregate NQB traffic is relative sparse compared to the available WiFi bandwidth (or the number of tx_ops) most of my WiFi concerns get less and less relevant. To be explicit, I do not object on principle to using AC_VI or even AC_VO as long as this does not eat significantly into the tx_ops for AC_BE, the current draft improves  in that direction. Would it be possible to make this point even stronger?
    
    > It appears that I missed one instance (in the Introduction it gives "interactive voice and video" as an example). Aside from this (which I can correct), I think the draft currently recommends that NQB only be used for sparse traffic.  That said, the section where this guidance is intended to be given is still lacking in specificity, and poses some open questions that may need to be addressed in a subsequent revision.
    
    	[SM] Sounds great. Now this then cycles back to one of the other open topics, "enforcement". Ideally NQB-aware APs should monitor both queues and re-assign flows between them based on flow-behavior in relation to time-variant bandwidth experienced by that flow. 
    
    Best Regards
    	Sebastian
    
    > 
    > Best Regards,
    > Greg
    > 
    > 
    > On 11/4/19, 3:25 PM, "tsvwg on behalf of Sebastian Moeller" <tsvwg-bounces@ietf.org on behalf of moeller0@gmx.de> wrote:
    > 
    >    Regarding https://datatracker.ietf.org/doc/draft-ietf-tsvwg-nqb/?include_text=1
    > 
    >    7.3.  WiFi Networks
    > 
    >       WiFi networking equipment compliant with 802.11e generally supports
    >       either four or eight transmit queues and four sets of associated EDCA
    >       parameters (corresponding to the four WiFi Multimedia Access
    >       Categories) that are used to enable differentiated media access
    >       characteristics.  Implementations typically utilize the IP DSCP field
    >       to select a transmit queue, but should be considered as Non-
    >       Differentiated Services-Compliant Nodes as described in Section 4 of
    >       [RFC2475].  As a result this document discusses interoperability with
    >       WiFi networks, as opposed to PHB compliance.
    > 
    >       As discussed in [RFC8325], most existing implementations use a
    >       default DSCP to User Priority mapping that utilizes the most
    >       significant three bits of the DiffServ Field to select "User
    >       Priority" which is then mapped to the four WMM Access Categories.  In
    >       order to increase the likelihood that NQB traffic is provided a
    >       separate queue from QB traffic in existing WiFi equipment, the 0x2A
    >       codepoint is preferred for NQB.  This would map NQB to UP_5 which is
    >       in the "Video" Access Category.
    > 
    >       Systems that utilize [RFC8325], SHOULD map the NQB codepoint to UP_5
    >       in the "Video" Access Category.
    > 
    >       In order to preserve the incentives principle, WiFi systems SHOULD
    >       configure the EDCA parameters for the Video Access Category to match
    >       those of the Best Effort Access Category.
    > 
    > 
    >    [SM] This last section is puzzling: if the wifi system configures AC_VI with EDCA parameters that match the AC_BE parameters, AC_VI ceases to be different from AC_BE, in that case picking a codepoint that automatically maps to CS0 and hence to AC_BE  seems much safer, simpler and straight forward to me. 
    >    Especially since essentially none of the millions deployed WiFi APs out there will a) have this configured like proposed already and b) none of the consumer APs I know actually allow to easily adjust EDCA parameters at all. I guess I must be missing something and would be delighted to be shown why the proposed text is the right thing.
    >    My take on this still is, if NQB traffic is sufficiently sparse using AC_VI can be justified, but without any rate limits this has the potential of being quite unfair to concurrent APs on the same channel (as well as the neighboring channels that overlap with the selected). 
    >    I do not want to sound alarmist, but given the number of cable-ISP WiFi-APs (as indicated by a SSID containing the ISPs name) in my city, I believe making sure that those APs will not basically start hogging most airtime seems the prudent thing to do. If there are sufficient backstops in place (like rate limiting or automatic down-marking if the traffic is not sparse enough) to avoid the described situation, I am all for it.
    > 
    >    The text probably should also openly discuss that in WiFi/WMM the four available queues by design have different priorities, and by moving NQB out of the default AC_BE while leaving QB flows in there, this effectively runs against  the following text in the draft: "The NQB queue SHOULD be given equal priority compared to queue-building traffic of equivalent importance." (leaving alone the question how an AP or a station is supposed to measure importance)
    > 
    > 
    >    Sebastian
    > 
    >