Received-SPF: pass (google.com: domain of linux-wireless+bounces-691-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Message-ID: <71ab1f7295860699713a018c69503f63d903a0be.camel@sipsolutions.net>
Subject: Re: [PATCH 06/14] wifi: cfg80211: Update the default DSCP-to-UP
 mapping
From: Johannes Berg <johannes@sipsolutions.net>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Cc: linux-wireless@vger.kernel.org, Ilan Peer <ilan.peer@intel.com>, Gregory
	Greenman <gregory.greenman@intel.com>, Jouni Malinen <j@w1.fi>
Date: Tue, 12 Dec 2023 10:39:33 +0100
In-Reply-To: <20231211085121.8a1c7d1f0034.I50aed38be78ae9aea052938e2cb6b5800010ecd4@changeid>
References: <20231211070532.2458539-1-miriam.rachel.korenblit@intel.com>
	 <20231211085121.8a1c7d1f0034.I50aed38be78ae9aea052938e2cb6b5800010ecd4@changeid>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.50.2 (3.50.2-1.fc39) 
Precedence: bulk
MIME-Version: 1.0

>=20
> The default DSCP-to-UP mapping method defined in RFC8325
> applied to packets marked per recommendations in RFC4594 and
> destined to 802.11 WLAN clients will yield a number of inconsistent
> QoS mappings.
>=20
> To handle this, modify the mapping of specific DSCP values for
> which the default mapping will create inconsistencies, based on
> the recommendations in section 4 in RFC8325.
>=20

This breaks ap_qosmap_default_acm ap_qosmap_default test cases.

How should we handle that?

johannes